Similar questions have been asked about delaying workflows for similar reason - prevent duplicate emails. I have not seen a promising solution that can solve my problem.
In my case, I have a Parent record with three children. When a change is made i want to send an updated document reflecting the changes. As we all know, when saving a record with this structure, the Parent record is saved first and then the children.
I canโt trigger a Workflow email from the Parent changes because the children havenโt been saved and their changes are not reflected in the generated document.
I can assume Parent changes have been made when a child change triggers a Workflow BUT there is no guarantee of child order so its likely the other children have not yet been saved and the generated doc does not reflect those other child changes.
So I am looking to the communityโฆagainโฆfor suggestions. Ideally I would be able to trigger a workflow only after ALL parent and child changes are saved. We do not (yet) have that capability. Alternatively, it would be nice to send off some kind of delay that triggers the Workflow after some time allowing all Saves to have occurred. Last ditch solution is to just send the updated document through user action (button tap) once all changes are verified as saved. This is not very user friendly.
It is not acceptable to just allow multiple emails and the last one wins. Thats the quickest way to lose customers/users.
I have been working on this for a while and would appreciate any help in trying to get to a work around/solution.
Thanks in advance!
(BTW - If i could assume that the children were all saved when the Parent changes are saved, then I could trigger this off the Parent changes and problem solved.)
LinkedIn
Twitter
