Need help on to add safeguard condition to the flow designer

[sureshp89882164]

existing flow details

• Assignment Group / Tech Org: Release management

• Priority: 2

• Work note on incident: "This incident has been downgraded from Priority 2 (P2) to Priority 5 (P5). If escalation is required, the support engineer must follow standard escalation procedures. For incidents above Priority 3 (P3), Control Centre and Service Management involvement is required."

• Safeguard condition: If the incident is later manually escalated back to P2, the flow must not reapply. To enforce this, the rule will check for the presence of the above work note. If the note exists, the rule will not downgrade the incident again.

[Mark Manders]

What is your question? You aren't asking anything. You are just stating something and a (terrible) solution for this. And we are missing the business case/requirement. Is this for every downgrade/upgrade? Because if you set your trigger to 'once', it will only run once and never again.

[GlideFather]

Hi @sureshp89882164,

is this a question or knowledge share? it's not clear 😛

[Bhuvan]

@sureshp89882164 

Add a flag to the incident when incident is updated with the work notes in the initial flow call. Use any out of box fields that is not used if you do not want to create a new field especially considering this is for a subset of incidents. 

For example, create/use existing field and set the default value to 'false'. When you update the work notes in initial flow call for above conditions, set the field value to true [add a field mapping in your existing update record action]. In the flow trigger, set 'active' = 'false' so that it will not retrigger work notes is available.

If this helped to answer your query, please mark it helpful & accept the solution.

Thanks,

Bhuvan

[Bhuvan]

@sureshp89882164 

Did you get a chance to review this ?

If my response helped to answer your query, please mark it helpful & accept the solution.

Thanks,

Bhuvan