Learn about the types of automations offered by Pega. Automations are Pega-supplied rules that you can use in Case Designer, flows, and activities to perform specific tasks, for example, to move a case to the next stage or send an email. As a best practice, use automations instead of activities.
The following is a list of Pega-supplied automations. You can view an automation rule to understand its inputs, outputs, and error classifications. For more information, see Viewing automations.
- Creates an email that can later be sent by using the pxSendEmail automation. For example, if you lack information that you need to send the email, such as the full list of recipients, you can create a draft of an email and send it later.
- Sends a previously created email by using a specified email account. For example, use this automation to send an email after your manager approves the draft of the email that you sent for review. You can also send emails in the foreground (synchronously) or queue them and send them later (asynchronously). If needed, you can persist emails in the Pega Platform database by setting the Persist minimal email input to true.
- Creates and sends an email from the specified email account. With this automation, you make one call to create and send an email. For example, after you resolve the approval stage of a case, you can use the pxCreateAndSendEmail automation to create an email approval notification, and then send it immediately.
- Obtains the status of emails that were previously sent by using the pxSendEmail or pxCreateAndSendEmail automations. For example, you can determine whether an email was sent or is queued for sending.
- Opens an existing email for viewing or editing by using the email message ID. For example, by using this automation, you can pass the email message to a manager for feedback. You can then send the email by using the pxSendEmail automation.
- Migrates case attachments to a repository.
- Moves a case to the next stage.
- Moves a case to a specified stage.