≡ Menu

How to Remove Status with a Workflow Process

new_process_none.png
Share the knowledge

Sometimes you need to remove status, or unstatus, something in Teamcenter.

Typically removing status from objects would be an administrator task to repair some sort of mistake. But you could have a standard workflow where objects go through state changes from statused to unstatused and back again.

Here’s how to do it.

release_man utility

One option is the release_man command line utility. However this can only be run by a DBA user and doesn’t leave any records behind. You can’t tell who used it to remove status, and you can’t build it into a workflow.

An Unstatus Workflow

Another option is to create a workflow that removes the status. This gives you the ability to provide the functionality to non-DBA users, perhaps after having passed certain validations by rule handlers or by human review and approval. An unstatusing workflow also leaves a record in the database of who ran it, and if necessary who approved it, etc.

Remove Status with set-status DELETE

Creating an unstatusing workflow is easy. Just add the set-status action-handler, with the argument DELETE, to a task in the workflow. If you want to delete only certain statuses add -f=status_name to the argument list. If you want to delete all statuses then use DELETE by itself. The handler is normally attached to the complete action of a task, but you can attach it anywhere.

The DELETE option has been available for a while but it wasn’t always documented. It used to be only mentioned in a IR that you could look up in the GTAC database. It is documented in TC 8.3, however.

Was this helpful? Please let me know!

  • Tobias Petersson

    Hi,
    Have also moved over to using a WF instead of “release_man”.The main reason was because “release_man” didn’t pick all objects under an item and you didn’t get any traceability of the action either.
    With a WF you can fix both of these  =)Thanks for a great site, keep up the good work!

    Br
    Tobbe

  • TeamcenterHeretic

    The ability to get an audit record is one of the most important reasons to implement such a workflow. 

    I cannot tell you the number of times I found unreleased data with absolutely no traceability on it because someone used release_man!
     

  • https://twitter.com/total_plm Ilya Chaykovsky

    Great thing! Didn’t know this. You’ve just saved me 4 hours today. Thanks.

    • http://plmdojo.com/ Scott Pigman

      Awesome! glad to hear it.

  • Mike Hallack

    the most common error for users is to forget to change the selection pulldown on the new workflow process dialog. In our case the first wf is ‘Archive’ which adds archive status.

    after umptine cmd prompt scripts I created the “Unrelease-Archive” wf to remove only the archive status, thus leaving other existing statuses.

    Has a been a huge time saver.

    Lastly, I leave the wf in construction state and offline, so only admins can see/use it.

    • http://plmdojo.com/ Scott Pigman

      Mike – instead of leaving it in construction & offline, you can also remove the ability of users to access it by setting up some wf filters and setting CR_allow_alternate_procedures to “none”. http://plmdojo.com/implementation/create-workflow-template-filters/#.UCmz32Oe49A

      • Teamcenter Heretic

        don’t also forget the ability to check the performer role of the user in the workflow.
        This is a second check that is easy to add.

        • rajasekharreddy kanchi

          EPM-check-action-performer-role

  • Menk Slot

    i would give this unrelease Workflow only to te DBA user, otherwise people start to abuse it. To be sure that people don’t use the wrong Workflow, use the template filter and check on status.

    • http://plmdojo.com/ Scott Pigman

      I absolutely agree.

  • Krishna Oza

    Could you elaborate more on Working , Frozen and Released Status.

    • Teamcenter Heretic

      Working, Frozen and Released are simply arbitrary names for Release Status Objects.
      Each carries with it a behavior defined in part by the Access Manager and in part by Workflow definitions and finally with your Business Processes.

      If you can elaborate a little on your question perhaps there might be a little more help found via a discussion here.

  • Hitarth Pathak

    How to prevent workflow initiation on already released object ?

Optimization WordPress Plugins & Solutions by W3 EDGE