Hi Maria,
Yes, if you wanted to change the email message in the example I used previously, you would need to update the process definition and reload it. With existing projects that are using that process definition, any notifications that were sent before you reloaded the definition are still saved in the project. New notifications will use the latest definition.
However, reloading a process definition might not always be desirable (for example, reloading also restarts the project workflow). To help minimize the chances of having to do that, there are a couple of ways you can set up your notification rules:
Instead of using the message attribute in the notification rule (as in the previous example), you can use the template attribute to specify a separate email template file that resides on the server. Then if you want to change the content of the email, you can simply change the template file directly, without requiring a change to the process definition itself. (See product doc on notification templates here.)
A similar idea applies to the recipient list. If you list individual email addresses in the toRecipients attribute and decide later you need to change that list, you will need to reload the process definition. To avoid that, you can just specify a group instead and manage the members of the group outside SAS Risk and Finance Workbench in SAS Management Console. If you change the group’s membership, you can refresh the user entitlements to pick up the changes immediately (In the version 3.2 UI, click Configuration > User Entitlements > Refresh User Entitlements.).
Here’s an example of how such a notification rule might look:
{"eventType":"TaskEnded","toRecipients":"Group A","subject":"Task $TASK_ID$ completed","template":"notify_complete.html"}
Regards,
Richard
... View more
