A request will automatically close after 30 days.
Flow for Approval Reminder Notifications
Three reminders will be sent before closure.
The initial approval triggered when the request is submitted is not considered the first reminder.
--- initial communication--- Day 1 ( Creation date )
1st Reminder: Sent after 3 days from submission. ---- Day 4
2nd Reminder: Sent 3 days after the 1st reminder. ---- Day 7
3rd Reminder: Sent 3 days after the 2nd reminder. ---- Day 10
Escalation Flow
then 1st reminder will be sent to the requester’s Manager. -- Day 13
2nd reminder: Sent 3 days after the 1st reminder. - Day 16
3rd reminder: Sent 3 days after the 2nd reminder. - Day 19
After 3rd reminder will escalate to the Manager’s Manager. --- Day 22
then 1st reminder will be sent to the Manager’s Manager. -- Day 22
2nd reminder: Sent 3 days after the 1st reminder. - Day 25
3rd reminder: Sent 3 days after the 2nd reminder. - Day 28
On Day 30 --- We will just mark Request cancelled ------
Q1)How can we achieve this by using flow designer?
Q2)Actually i have implemented by using flow. Can you please review the below mentioned flow images?
Q3)the remainder's are sending properly. but in the 8th step is through a error like as i mentioned img?
I have something similar build but mine only sends 2 additional reminder for a total of 6 days. Shouldn't be that hard to modify it for 30 days.
Start conditions for the flow:
Body of the flow: You will notice that I have the flow start off with Do the following in Parallel this way I do not have to check before I send the reminder if they state changes. Section 2-3 and 4 task care of monitoring the state of the approval and will end the flow if the state changes and it not requested. Also I'm using business days.
You are probably passing dot-walking the wrong thing into the record parameter on update record. Also there is not need to create an action to essentially dot walk to something you already have access to in the flow.
If I had to use flows for this use case I would probably do something like this. And avoid using waits.
There is no need to overcomplicate it by creating a lot of resource overhead with long running flows etc. I think process-wise it would be good to also aggregate all expiring approvals of the day for the user. I would personally much rather receive a digest email of all my approvals than multiple reminders.
It is also good to notice that the approval record has a due date field that you can utilise for this.
Hi @manojdatasc,
I have applied this similar use case; you can refer to it.
If you find my answer useful, please mark it as Helpful and Correct 😊
Regards,
Soham Tipnis
ServiceNow Developer || Technical Consultant
LinkedIn: www.linkedin.com/in/sohamtipnis10
