Dynamics 365 Sales is recommending Flow instead of Dynamics background processes. So, I'd like to migrate my current background workflow processes from legacy Dynamics solution explorer to Flow.
I have a workflow, which reminds my colleagues to add appointment notes after an appointment is over. Right now, the trigger is appointment creation, then a wait condition applies until the appointment is over (endtime is in the past). The Dynamics Workflow reacts to changes in endtime (e.g. when an appointment is rescheduled). The Delay step in Flow does not reflect an updated delay time. How could I build a flow which works in this situation?
My approach would be to add a condition after your delay to check if the original endtime equals the current/updated endtime. If that's true I will send a reminder. If this is not true I would terminate the flow.
I would also create another flow which is triggered When an appointment record is updated. I would add a attribute filter which is set the scheduledend attribute. So basically whenever somebody reschedules you will have a new flow instance. In this flow you can use the same logic.
Another reason why I would use this logic is because of the 30 days run limit:
Thank you very much for your answer.
If I understand it correctly, this won't work for appointments which are more than 30 days in the future?