Hide or disable form options when the request Life Cycle would disable them
I have some statuses in RLCs that I plan to remove, so I have added 'before' transitions to them that limit access to admins, so that technicians are forced to use the new RLC transitions we've added instead of the old ones for requests they create going forward. We've just had some small hiccups with this.
We have noticed that when an RLC 'before' clause invalidates the transition, the following happens:
- The blue transition button disappears, as intended
- The status that the transition moves the request to is still present in the 'status' drop-down menu when editing the request
- Technicians without permission to initiate that transition are still able to see and select that status manually
- This leads to some confusing error messages, as I'm not able to customize the negation message for the 'before' transition
Just a thought, but I would be a great quality of life improvement to have transitions that are invalid according to the RLC also hide the currently invalid statuses from the status drop down.
Currently my work around is to also implement a form and field rule on the request template to hide the status for it, but the duplicate work doesn't feel great and is harder to maintain long term.