** 1st (Approval Process) - (Task: Task Record Type EQUALS Prime Brokerage) AND (Task: Status NOT EQUAL TO Completed) AND (Task: Approved by Management EQUALS null) AND (Task: Date of Approval EQUALS null)
** 2nd (Been Approved and Needs to go to the "Assigned To") - (Task: Task Record Type EQUALS Prime Brokerage) AND (Task: Status NOT EQUAL TO Completed) AND (Task: Approved by Management NOT EQUAL TO null) AND (Task: Date of Approval NOT EQUAL TO null)
** 3rd (Task Been Completed) - (Task: Task Record Type EQUALS Prime Brokerage) AND (Task: Status EQUALS Completed)
Please let me know the best process in executing this.
Thanks,
Mike
1 risposta
Unfortanetly this is going to be a very hard process to lock down because notifications are sent as soon as the assignment is completed. The only way around this is to allow the individual users to control their own notification settings and then you cannot guarantee a notice will go out at all. Best case (in my opinion) would be to do something like as follows:
- Assign task to a system user until after approval has been completed. This way the user will not be notified since they are not the "Assigned To"
- Once approved, assign the task out to the user and the notification will be sent since assignment is changing. It is important to note here that notification emails aren’t sent for tasks that you assign to yourself; or for tasks that are assigned to another user with the status already set to 'Completed.'
Depending on the assignment logic, you could put all of this inside of a process builder to keep the logic flow and criteria mapping in one location. At the assignment step - once approved - you could either set the user assignment manually as part of the approval process or by leveraging CMTs (Custom MetaData Types) to store the logic and automate the assignment.
Hope this helps.
--- If this answers your question, please select best answer to ensure it is found again in the future by others