How to add wait condition in flow designer until variable in sc_task table get updated?

Gopinath Krish1
Tera Contributor

Hi,

I have requirement to generate approval for sc_task, if variable in sc_task updated as 'true' then I should generate group approval for that task using flow designer. Can anyone help me to add wait condition until  variable got updated in sc_task?

Thanks in advance.

7 REPLIES 7

OlaN
Giga Sage
Giga Sage

Hi,

That's not how a wait for condition action works.
It is meant to use to wait for when a specific action happens, like a record turning into a specific state or similar.
Just to say a "variable is updated" is not specific enough. You will need to specify how it should be updated, and to what value.

Also, you might reconsider your process. Shouldn't the approval happen before the task is generated?
You might want to skip creating the task if the approval is rejected.

I have a similar(ish) ask. I was using an sctask to sequence catalog item variables being updated. I WAS (but can no longer use SCTasks as my client refuses to use them) using that SCTask to effectively pause the flow until these variables are filled out (not done by the end user but by a manager after form submittal). After the Sctask step I had a few different if and else if flow logics to control approval generation and email notification triggers. But without the sctask my sequencing is off. Now if it just skipping over all of my if and else if flow logics completely. How can I pause (in effect) the flow while waiting on these ritm variables to be updated? Thanks!

maybe a BR that monitors for changes on the variable, and then updates the item in some way the flow can look for? 

 

in your flow you add a 'wait for condition' on whatever field you pick. When the manager fills out the variable, you have an business rule that sets your field to whatever the flow is looking for, and at that point the flow adds the approval. You can use the flow to set the field back to it's initial state and then repeat the process for the subsequent variables.

 

just a thought

Did you find a solution for this Flow designer limitation?