How to limit items users can add to a change order
Hi,
I’m trying to figure out a way to limit what items users can add to a change order.
The specific instance is that we have a change order called AC (archive change) where we want to allow users to archive certain document type called Archive Document.
I want to limit the affected items to just archive document for that archive change.
I tried doing that with modify but modify privilege won’t allow me to use affected items criteria. I realize I could do it with discover but for this particular role we want the users to be able to discover everything but just not add everything to this change type.
I also tried it with workflow creating a criteria that says basically ‘affected items.item type in archive document’ and that is on all statuses with required fields at each status.
It seemed to work. When I added a document type that was not an archive document I got the ‘no exit criteria matches’ so the user wouldn’t be able to change status on the change.
But, when I removed that document and added the correct Archive document, I still am getting the ‘no exit criteria matches’ which doesn’t make sense now that the right document type is attached.
If anyone knows if that is a bug that would be great to know. I add an SR to oracle and my issue kind of looks like another known bug but not exactly.
And if anyone knows a different way to approach this issue I’d be most grateful.
Thank you,
Laura
Hi Laura,
it seems to me that your workflow criteria should work fine, The SR is definitely the best way to figure out if it is a bug or not.
But just to suggest you something different you can think about to create a Groovy Script that will warn, or even to forbid, users to add non Archive Document to the affected items tab. It’ll be more effective than the workflow criteria because the groovy’s rule will raise up before the criteria’s warning.
my best
Carlos
Thank you Carlos for that quick reply. Guess I need to learn Groovy scripting! I figured that would be the best way to get a good message.
It’ll be interesting to see if my issue is a bug. It sure looks like it should work.
Thanks,
Laura
Laura,
Oracle has some Groovy examples for a quick start.
http://www.oracle.com/technetwork/indexes/samplecode/agileplm-sample-520945.html
Good luck
Carlos
Hi Laura,
Have you got any feedback from the SR?? What´s the Agile version you´re using??
In my opinion, I guess there must be something else on your workflow criteria that´s causing the “No exit criteria..” error. Also, I generally create a workflow criteria like the one you mentioned and attach it to the first status of the workflow (Pending) only, I wonder why you would need to attach it to all workflow statuses, like you mentioned.
Hope that helps!! Please advise how your issue has evolved!!
Best regards,
Clovis Chenaud Jr.
