I think one of the revisions is checked out, you cant attach objects as targets if they are checked out.
I put ps-attach on a vailidate task with a failure path. Users get a condition task which prompts them to check in and continue or exit the workflow:
I actually tried it on a completely new BOM structure which i created to check, so they were not checked out. I was also wondering if i need to add any additional handlers to apply it on a BOP structure.
Your workflow is performing two different actions, and you will need two different permissions;
The error you got in your last post is from adding the attachments, not from trying to change the ownership.
Thanks for patiently replying to all my queries. I tried adding an additional workflow ACL before the PS-attach-assembly-components granting the CHAGNE authorisation, but I still get the same error. Also, one thing which i must add is that i create the BOM strcuture in infodba and send it to another user through an envolope and then apply the workflow process. Can this be the probelm?
Object owned by infodba have some specific access control entries in the access manager tree that deny certain privileges to general users. I suspect that this ownership is certainly not helping.
You should avoid having any non-system objects owned by infodba.
Try with an assembly owned by another user and see if your workflow works.
Well i am afraid i dont know how to do that. Is it just going to the temp folder and checking for a syslog file or something else . Doesnt closing the teamcenter and opening it again achieve this?