Question
Capgemini
MY
Last activity: 22 Jul 2020 11:07 EDT
Best practice in configuring Outbound email during assignment creation
Hi,
I would like to know the best practice in configuring the outbound email once assignment gets created.
Below is the requirement :
1. Once Requestor submits the application, the case will be routed to Manager for approval. We need to send an email notification to Manager and CC-Requestor.
2. Once Manager Approves, the case will be routed to Senior Manager for approval. We need to send an email notification to Senior Manager and CC-Requestor and Manager. Like this we have multiple flows close to 5.
In this scenario i used to follow below scenarios to achieve this requirement :
1. Use SendEmail shape before Assignment shape in the respective flows and pass the necessary parameters.
2. Create a centralized activity of type Notify and call the respective OOTB activitites(Call CorrNew or SendSimpleEmail or SendEmailNotifications) with in the activity and pass the necessary params as per the requirement. Based on the status of the case, capture the params and pass it to the OOTB activities (Call CorrNew or SendSimpleEmail or SendEmailNotifications). Call the Centralized activity under post processing actions of the Flow Action of Requestor & Manager. This centralized activity can also be called from Assignment shape -> properties -> Notifications.
So now, i would like to understand which one from the above two falls under best practice.
Hi,
I would like to know the best practice in configuring the outbound email once assignment gets created.
Below is the requirement :
1. Once Requestor submits the application, the case will be routed to Manager for approval. We need to send an email notification to Manager and CC-Requestor.
2. Once Manager Approves, the case will be routed to Senior Manager for approval. We need to send an email notification to Senior Manager and CC-Requestor and Manager. Like this we have multiple flows close to 5.
In this scenario i used to follow below scenarios to achieve this requirement :
1. Use SendEmail shape before Assignment shape in the respective flows and pass the necessary parameters.
2. Create a centralized activity of type Notify and call the respective OOTB activitites(Call CorrNew or SendSimpleEmail or SendEmailNotifications) with in the activity and pass the necessary params as per the requirement. Based on the status of the case, capture the params and pass it to the OOTB activities (Call CorrNew or SendSimpleEmail or SendEmailNotifications). Call the Centralized activity under post processing actions of the Flow Action of Requestor & Manager. This centralized activity can also be called from Assignment shape -> properties -> Notifications.
So now, i would like to understand which one from the above two falls under best practice.
I am strongly feeling that having a centralized activity(point 2) will be more useful for maintenance and readability as entire email send functionality will be there in one activity for the whole case type and can delegate this rule(if required).
Point 1 -> needs to be configured in all the flows and maintenance can be a overhead.
Kindly shed some light on these and let me know if there is any other best practice apart from above two.
Thank you.
Ramesh.
Incessant Technologies Pvt.Ltd
AU
Hello,
As per my knowledge Creating a centralized activity and parameterizing with main attributes that are required for sending the E-mail is the best approach as it has various advantages like below.
1. We can utilize the same generic activity as part of our flow processing to send the mails.
2. If there is any requirement to send Emails through any back ground processing activity we can leverage the same activity there as well.
Create the activity at the generic level so that it can be utilized across various functionalities for sending the E-mails.
Updated: 22 Jul 2020 11:07 EDT
Pegasystems Inc.
IN
Hi,
You can try creating a declare trigger (which gets triggered when pystatuswork changes). A generic activity can be called on the declare trigger. In the activity, you can call a decision table to map the pystatuswork with To Address,subject, and template. In the generic activity, you can use sendsimpleemail and input the out parameters from the decision table. In this approach, there will be less maintenance overhead because if anything needs to be changed, You can directly change in the decision table. And there is no need to change all the flow actions