Hmmm, I don't see the "Development Release" option in the drop down.
I do see an "unrelease". We already have an option for dba to "Remove status", but it does not work when the Item has been released, for tha twe have our TC admin run the other utility, and my hope is to make it easier for us semi-admin types to do that.
Then please create a new root template without using Development Release(since it is from Rapid Start templates).
Add a task.
Just set the handler on "Complete" --> EPM-set-status and "-action" "delete" (previous picture)
It may do that.
Another method is to create an "unrelease" folder in infodba's Home folder. Copy/paste the workspace objects (Item) you want the release status removed from into the "unrelease" folder.
Now open a teamcenter command prompt and run the release_man utility.
release_man -u=infodba -p=infodba -g=dba -unrelease -folder=unrelease
Note: you may want to add the "-spec" and "-status=Released" switches also.
Refresh the objects in the "unrelease" folder and the status should be removed.
A couple of the steps I may have screwed up. The "Draw Arrow" Step seemed unnecessary as I already had an arrow there. And the Delete "EPDM...." didn't look the same. I thought my end result was good, but here is the error I get when trying to run it:
So, I went into the Handlers for the Process and removed the start tasks that seemed to be creating objects, but that didn't fix anything. So, here is what the handlers look like for "Un-Release":
And handlers for "Status":
And, my overall workflow view:
What do I have wrong?
And, thank you very much for helping me with this.
From your screenshot the "add-status" argument "action" is missing the dash "-action". You are running an old version of Teamcenter. Newer versions use EPM-set-status (same arguments).
Okay I got the - in there ahead of action. Updated screen shot of that:
But it still yields the same error:
I suspect something still wrong in the handlers for the start of the process, but I'm not sure what to change or put back.
As the error implies, you should initiate workflows as a regular user and not infodba. Infodba has special permissions that a regular user doesn't. Try intiating the workflow as someone in the Engineering group. You may need to modify some access rules that allow a workspace object to be deleted as the Engineering user. I suggest you work with your CSR or through GTAC when creating an unrelease workflow as the ramifications can be far-reaching.
The safest approach is to use the release_man utility.
Yeah, I'm just looking to fix two Items and then hopefully never have to do this again. I'm not an admin, but only have admin privileges in the meantime until we update to a newer version and get an admin. I've heard of the utility, and the previous admin I believe used it, but I believe it was significantly more difficult in that he had to have access to the server where TcX is running....etc. etc. and that sounds like too much trouble. So, if we could, can we try to fix whatever issue is causing this to not work? I did log out and back in as myself (rather than DBA) and the workflow executed without error, but it did not do anything. What do you think?