We have had a few Items (circled in red) get released, instead of the Item Revision. Our TC admin has the process to remove the status from them, but is there something we can set in TC to prevent this from happening?
Use the rule handler, EPM-validate-target-objects, to exclude 'Item'.
In case if you dont want to modify workflow template itself, admin can use "Template Filter" feature to make Release-workflows available only on ItemRevisions.
I tried EPM-validate-target-objects,
-exlcude_type - Item
-include_type-ItemRevision,ItemRevision Master,SE Draft,PDF,BOMView Revision,SE Assembly,SE Part,SE SheetMetal.
See attached image.
scope- User should not release Item .
Still Item is getting released. Could you check and guide me what i am doing wrong.
If your user is selecting multiple objects to put in WF, TC allows Items to be grabbed and ignores the filter you set in the handler. This is why I add an "Item Revision" validation step in all of my WFs that verifies that none of the WF Targets include an Item.
It's automatic Condition Task with a Query that checks if the WF Target is an Item Revision only and routes accordingly.
I am not experienced in designing workflows, but we also don't set an status on the ITEM.
In our case the EPM-validate-target-objects also only include the ItemRevision and all Datasets.
Additionally we have added several "EPM-attach-realated-objects" handlers like in the attached picture.
For each relation another handler is necessary.
Maybe this can help you.