Forum Discussion
MarkShnier__You
Qrew Legend
5 years agoOK, I finally understand the question.
The references to APIs are a red herring.This kind of APIs are used for a user to click to cause an edit. Nothing to do with your use case.
Also, there is in fact a user causing a record to be edited to trigger a process, so these summary fields are not in fact changing due to the passage of time. They are changing because a User approved a record and hence edited a record.
So we do in fact have a clear trigger event. The event is an Approval Level 1 record being approved.
Notifications to the Approval Level 2 recipients can be done using an Automation.
We need to have a summary field of the [# of Level 2 Approvers already notified]. That will be the summary count of the # of Level 2 approvals where the [Level 2 Approver date/time Notified] is still blank. This date/time field is the one that will be updated by the Automation to trigger the Notification.
Let's make sure that we have a formula date/time field called [Current Date/time] with a formula of Now() on the Approval records. Also we will need to have the lookup of that parent field for [Ready to Notify Level 2 Approvers].
The Automation will Trigger when a Level 1 Approval is done, subject to the filter that [Ready to Notify Level 2 Approvers] is checked and [# of Level 2 Approvers already notified] =0. Presumably, this would then trigger when the last of the approval level one approvals was done.
The Action once triggered will be to Modify Records in the Approvals table , subject to the filter that they have the same [Related Proposal] as the trigger record.
I believe that the modify records action will be done slow enough that it will be seen as a single record notification update for Notifications. If you get this working but the Notification only fires a multi record change notification which would not be suitable for your needs, let me know and we will just daisy chain one automation to call the next and that will slow it down enough to make individual record change notifications.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
The references to APIs are a red herring.This kind of APIs are used for a user to click to cause an edit. Nothing to do with your use case.
Also, there is in fact a user causing a record to be edited to trigger a process, so these summary fields are not in fact changing due to the passage of time. They are changing because a User approved a record and hence edited a record.
So we do in fact have a clear trigger event. The event is an Approval Level 1 record being approved.
Notifications to the Approval Level 2 recipients can be done using an Automation.
We need to have a summary field of the [# of Level 2 Approvers already notified]. That will be the summary count of the # of Level 2 approvals where the [Level 2 Approver date/time Notified] is still blank. This date/time field is the one that will be updated by the Automation to trigger the Notification.
Let's make sure that we have a formula date/time field called [Current Date/time] with a formula of Now() on the Approval records. Also we will need to have the lookup of that parent field for [Ready to Notify Level 2 Approvers].
The Automation will Trigger when a Level 1 Approval is done, subject to the filter that [Ready to Notify Level 2 Approvers] is checked and [# of Level 2 Approvers already notified] =0. Presumably, this would then trigger when the last of the approval level one approvals was done.
The Action once triggered will be to Modify Records in the Approvals table , subject to the filter that they have the same [Related Proposal] as the trigger record.
I believe that the modify records action will be done slow enough that it will be seen as a single record notification update for Notifications. If you get this working but the Notification only fires a multi record change notification which would not be suitable for your needs, let me know and we will just daisy chain one automation to call the next and that will slow it down enough to make individual record change notifications.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
PaulStreit
5 years agoQrew Member
Good point regarding the approval response as a trigger. This may work. I’ll mess with it and report back. Might be a few days.
Thanks
Paul
Thanks
Paul