Timing constraints other than SLA on change Request.

[Dilip Choudhar1]

We have a changes request which creates two change tasks A and B. Both are created parallely and B task is dependant on A Task. So Task B should be closed only after A task is closed. Now since the change is open for only 7 days (this is a requirement so cannot add more days), "I want to make sure The team for Task B gets enough time for Resolving the task after the Task A is closed." We cannot create task B after task A is closed as the requirement is for both of them to be created parallely. How can we achieve this without SLA's? 

[Shubham_Jain]

@Dilip Choudhar1 

Here’s a concise approach to ensure Task B gets enough time after Task A is closed without SLAs:

1. Put Task B on Hold Initially

   • When Task B is created, set its state to "On Hold" with reason "Waiting for Task A" (via Business Rule or Flow Designer).

2. Release Task B When Task A is Closed

   • When Task A is closed, update Task B’s state to "Open" and extend its due date (via Business Rule or Flow).

3. Restrict Task B Closure Until Task A is Done

   • Use a UI Policy to prevent Task B from closing unless Task A is already Closed.

This ensures Task B exists in parallel but gets enough time after Task A is completed.