Xanadu Patch 4a
We set up a before updated business rule for Change Request that prevents a change from proceeding if there is a blackout conflict. This seems to be working correctly except in one specific case.
- user creates a normal change; planned dates are entered when the change is created; the planned dates do not result in a conflict. the change is in the New state.
- the user then edits the change and modifies the planned dates to dates that are in a blackout window and then clicks the Request Approval button.
From what we see, conflict detection is run and the blackout conflict is detected but the change is not prevented from moving to the Assess state. It appears the business rule is not triggered in this case.
However, if the user edits the change and modifies the planned dates to dates that are in a blackout window, does a Save first then clicks the Request Approval button, the change is prevented from moving to the Assess state. The business rule is triggered in this case and prevents the change from moving forward.
From what I can tell, our Request Approval UI Action is OOB as is the change workflow.
Any suggestions on how to resolve this so that we can prevent the change from moving forward in the scenario I described?
Thank you
