Create SCTASK in two separate RITMs when the second SCTASK of the respective RITM is closed.

HudyssonPOntes
Tera Expert

Good afternoon everyone, how are you? I have a scenario where two RITMs are created, and in each RITM there will be three SCTASKs. However, the third SCTASK can only be created after the second SCTASK is closed. So, I will have:

RITM01
   SCTASK101
   SCTASK102

RITM02
   SCTASK201
   SCTASK202

Currently, my flow waits for the closure of the second SCTASK in a dependent manner. If I close the second SCTASK of RITM02, it doesn't create the third one unless I also close the second SCTASK of RITM01. I need the flow to wait independently in each RITM. If I close the second SCTASK of RITM01, it should create the third SCTASK in RITM01. If it closes the second SCTASK of RITM02, it should create the third SCTASK in RITM02. Could you please help me? Thank you.

HudyssonPOntes_0-1744231196757.pngHudyssonPOntes_1-1744231216286.png

 

7 REPLIES 7

Brian Lancaster
Tera Sage

How is the wait for condition configured?

Wait for second TASK state is closed

HudyssonPOntes_0-1744250225904.png

I would need the wait for to be specifically for this TASK of this RITM, and that the other TASK of the other RITM has its own wait for.

RITM01
  TASK101
  TASK102

RITM02
  TASK201
  TASK202

If SCTASK102 is closed, create TASK103. If TASK202 is closed, create TASK203 — without the TASK from RITM02 depending on RITM01, and without the TASK from RITM01 depending on RITM02. Thank you very much for yout attention

Ankur Bawiskar
Tera Patron
Tera Patron

@HudyssonPOntes 

why it's waiting for task from other RITM?

Regards,
Ankur
Certified Technical Architect  ||  9x ServiceNow MVP  ||  ServiceNow Community Leader

Because I don't know how to do what I need to do, so I tried to do this way.

I need to create two RITMs within a single REQ, and then create three TASKs under each of the RITMs. The first two TASKs must always be created, but the third should only be created when the second TASK is closed. I need that the FLOW understands that these are different RITMs, and that the WAIT should only wait for the closure of the second TASK of its own RITM — the second TASK from the other RITM should not interfere in any way. Sorry my poor English