Pray patience while I try and explain this.
So we have change requests and change tasks. The idea of change tasks is to execute a specific piece of work to assist with the progression of a change request, such as a comms piece, or some testing by someone else.
I put in a UI policy recently that prevents change tasks from being amended once the parent change request has been approved. That works beautifully well, except when:
Let's say someone drafted a change request, added five change tasks through during the planned start and end date of the change request. All is gone through fine and dandy. However, the proposed change window wasn't suitable for whatever reason, so it's been delayed for a week. No problem, change is ultimately approved for the new window. However the change tasks are still scheduled for the week before and because the change is approved, the tasks aren't editable and, because of the OOB business rule, which doesn't allow them to be otherwise edited if the fall outside of the approved change window, they're effectively stuck. Now, I know I can temporarily disable the UI policy to update the change tasks, but that's not in the spirit of the UI policy in the first place.
So, what I'm trying to ask is, whether there's a way of checking any associated change tasks when proposing a new start/end date for the change request?
Phew!
