Expedited field should be toggled if the change doesn't meet lead time of 24 Hours

[Muffin]

Hi All,

I need to create custom fields "Lead Time" and "Expedited" and Expedited field should be toggled if the change request doesn't meet its lead time of 24 Hours then update a reason on "expedited reason" (another custom field). Any suggestions on how to implement this ? Please help.

Thanks in advance.

[Mark Manders]

How do you calculate the lead time isn't met? Do you have a date/time field that sets the start? 

If so, you can create a flow on the change_request. Wait until that start time and then wait 24 hours. If change isn't closed, you update the 'expedited' field and do something with the expedited reason, although I'm not sure how you can automate that, because a reason is something manually, right?

[Muffin]

@Mark Manders Yes i have a custom field Lead Time with Date/Time type which will be auto populated with planned start date - 24 Hours (Written a business rule for this). The expedited filed should be toggled when the lead time is missed.

[Mark Manders]

Then the flow with wait condition should work.

[Jake Sadler · Accepted solution]

Hi @Muffin,

1> you can create a flow with a wait condition that waits for 24 hours after the lead time. Once 24 hours is up update the fields you need. If the reason is automated.

If you want the user to update the expedited reason field then you can use a client script to perform the checks and make the expedited reason field mandatory when true. This will only work when the user is looking at the record though.