I thought the condition would determine when the UI Action was visible, but 'Transfer to Incident' still shows when the Assignment Group changes and the state changes to 'Assigned.' Based on the criteria below only 'Work in Progress' and 'Planning' states should show the 'Transfer to Incident.' It works when I first bring up the ticket (so if Planning state it shows), but if the state changes to 'Assigned' and the ticket is not saved, then the Context Menu still appears and it should not. I would assume current is the new value and not previous.
I need to prevent users from having this option to 'Transfer to Incident' if the state is not 'Work in Progress' or 'Planning' and right now I have users that will change the Assignment Group/state and then click the 'Transfer to Incident', but the Assigned To is not populated and leaving the RITM workflow hung.
I'm thinking there is a couple ways to fix this - but I don't want to over engineer it either...
1. Add in a validation to the UI Action 'Transfer to Incident' to confirm the Assigned to is populated, if not pop a message and return false.
2. Update the client script that when an Assignment Group changes, that the state changes to Assigned (this is already there), but add in the removal of the 'Transfer to Incident' from the Context menu - can this even be done?
Ideas would be helpful...
