Affected Items.Item Number not working as entry/exit required field in workflow
I’m setting up a new workflow for PSR objects where I’d like to require the object have an affected item and attachment before proceeding to the next status.
By setting the entry/exit required fields to include Class.Attachments.Filename, the user is required to add an attachment, and they get a nice message that tells exactly what’s missing if they try to proceed to the next status without an attachment.
I’d like to do the same thing with Affected Items, but setting the entry/exit required fields to include Class.Affected Items.Item Number doesn’t work. Users are able to push the object to the next status even if there is no affected item.
I can force the Affected Item by setting up criteria, but when the user tries to move forward without an affected item the error only says that they don’t meet criteria, and it isn’t very intuitive for them to check what’s actually missing.
Is there something I’m missing in the functionality of Affected Items.Item Number? Is there a way to set this up the same as I have with Attachments.Filename or will I just need to set it in criteria and try to train users?
As far as an Out-of-the-Box solution goes – I think setting the criteria and training users is going to be your best bet. Unfortunately – using Affected Item attributes (along with some other table attributes) in your exit required fields only seems to matter when there is an affected Item already present. If there are no affected items (or no table rows present) those particular exit required fields are ignored.