- SAP Managed Tags:
In this blog post, we will see the best practice for when to use certain alerting activities. In SAP Intelligent RPA 2.0 you can have three ways to send alerts, information. There are the notifiers, the custom alerts and the outlook activities.
To create a notifier, you need to have a trigger created for a package in your environment. Then by clicking on the three dots you can click on Add Notifier to create one.
The notifier can be by an Email, API or CAI. The purpose of this alert is to send a notification on each state of the automation. For example, if you want to receive an email when the automation has stopped because there was an error, you can choose the Email notifier and click on Next.
Then, you can precise if you want the notifier to send an alert if the automation has started, has been a success, has failed, has been canceled or has expired. And you can setup the name, the recipients, and the content of the alert.
The notifier is useful to notify when there has been some kind of execution issue in the automation, or in a CAI integration, notify to the CAI when the automation has finished. Which is different from the custom alerts.
Custom alerts are created by adding the activity Raise Alert in the workflow and creating an alert in your project.
Here in this example, we raise the Alert Status when an order is “Too late”.
The alerts are customizable, you can pass the parameters you want from your automation and setup the message as well as the name and the severity of your alert.
In other words, the custom alerts are here to allow the user to send information from the automation to inform the user. Alerts are sent by the factory, so there is no need to configure outlook on the desktop agent, but you need to configure the smtp configuration in the factory (Here is a link to more information on the configuration of the smtp in the factory link)
Lastly, we have the outlook activities.
The outlook activities are not alert activities. They allow the user to send mails and to attach documents to them. There are not here to send alerts with information on the workflow but are part of the workflow when the automation needs to send a mail.
In this workflow, we want to send an excel file that has some order information that we got from a website. In order to send the excel we use outlook activities to open an instance, send a mail with attachments and close the outlook instance.
The alerting activities have different usage and allow the user to send different form of information from the automation.
To sum up, here is a comparative table of the difference between the three alerting types.
Notifiers
To create a notifier, you need to have a trigger created for a package in your environment. Then by clicking on the three dots you can click on Add Notifier to create one.
The notifier can be by an Email, API or CAI. The purpose of this alert is to send a notification on each state of the automation. For example, if you want to receive an email when the automation has stopped because there was an error, you can choose the Email notifier and click on Next.
Then, you can precise if you want the notifier to send an alert if the automation has started, has been a success, has failed, has been canceled or has expired. And you can setup the name, the recipients, and the content of the alert.
The notifier is useful to notify when there has been some kind of execution issue in the automation, or in a CAI integration, notify to the CAI when the automation has finished. Which is different from the custom alerts.
Custom alerts
Custom alerts are created by adding the activity Raise Alert in the workflow and creating an alert in your project.
Here in this example, we raise the Alert Status when an order is “Too late”.
The alerts are customizable, you can pass the parameters you want from your automation and setup the message as well as the name and the severity of your alert.
In other words, the custom alerts are here to allow the user to send information from the automation to inform the user. Alerts are sent by the factory, so there is no need to configure outlook on the desktop agent, but you need to configure the smtp configuration in the factory (Here is a link to more information on the configuration of the smtp in the factory link)
Lastly, we have the outlook activities.
Outlook
The outlook activities are not alert activities. They allow the user to send mails and to attach documents to them. There are not here to send alerts with information on the workflow but are part of the workflow when the automation needs to send a mail.
In this workflow, we want to send an excel file that has some order information that we got from a website. In order to send the excel we use outlook activities to open an instance, send a mail with attachments and close the outlook instance.
Conclusion
The alerting activities have different usage and allow the user to send different form of information from the automation.
To sum up, here is a comparative table of the difference between the three alerting types.
5 Comments
