Auto Closure of REQ and RITM when all the associated tasks are closed

[VipulM068601172]

I have a requirement to close the parent REQ and RITM when all the associated child tasks are Closed.
It looks like OOTB functionality as I verified in PDI as well but I am facing an issue that when the RITM has multiple tasks and when the last task to be closed is manually created then the parent REQ and RITM does not get closed.
Can anyone suggest me the approach to resolve this as I am not able to find the appropriate script or flow that runs commonly for all tasks.

[Ankur Bawiskar]

@VipulM068601172 

As informed there is nothing available OOTB

I already shared approach using BR and Flow

Please use that and enhance

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[VipulM068601172]

Hello @Ankur Bawiskar ,
Actually we have various flows attached to different catalogs that also has logic to set the RITM/REQ states accordingly. Also there is an existing functionality to set RITM and REQ closed when the request stage is completed.
Even without the BR, it is working as expected for all the records, I tried this in PDI as well and it works the same there for auto generated tasks. 
But if we are closing auto tasks first and manual tasks at the last, then it is not setting the values to closed.

[Ankur Bawiskar]

@VipulM068601172 

Flow Designer approach: I shared solution few years ago

I have shared solution below using flow designer to close parent INC when all child INCs are closed.

Enhance it for sc_req_item and sc_task table and to close REQ

If all child incident is closed then after Parent incident should be closed. How to achieve through....

💡 If my response helped, please mark it as correct ✅ and close the thread 🔒— this helps future readers find the solution faster! 🙏

[AndersBGS]

Hi @VipulM068601172 

As you clearly state, last task is manual created, hence not part of the workflow created through flow designer. According to this requirement, I don't see that you have a veldefined standard request item workflow, but more a generic workflow where additional tasks can be added. 

Based on above, there is no logic for this unless you do a scheduled iteration to look through the sc_task to see if there are any open associated with the workflow (this is not best practice). I would rather recommend you to take the dialogue with the fulfillers of the specific flow, and adjust the workflow behind so no additional tasks will be manually created.