Certain steps, such as collecting identifying information from a customer, require user action, while other steps can be performed automatically by the system, such as sending a confirmation email to a customer.
Pega Platform™ provides automations to perform specific actions automatically. For example, you can use automations to send an email to a job candidate to extend them a job offer and provide the candidate with an offer letter in PDF format. Leveraging automations saves development time and enables you to design business processes more efficiently. Automations provide flexibility because each automation has unique parameters that you can configure based on your business requirements. Additionally, utilizing automations reduces possible human error by reducing the amount of human interaction.
Consider a scenario of an online bookseller. Once a customer places an order, the company needs to send an email with an invoice summary.
In the following image, click the + icons to understand how to configure a process with automations to achieve the desired behavior in the online bookseller example.
Note: In the case life cycle, click Step > More > Automations to add an automation. In the process modeler, click Add > Automations to add an automation.
Pega Platform provides a wide variety of automation shapes that a developer can use to achieve business requirements. Automation shapes in a flow represent a task that a user or application completes as part of a business process.
The following table describes all automation shapes available in App Studio.
||Attaches a file, URL, or note to a case.|
|Change to a stage||
||Change to a specific stage of a case.|
|Change to next stage||
||Change to the next stage of a case automatically.|
||Creates one or more cases from the current case.|
||Creates a PDF file from a specified section and attaches it to the case.|
||Generates a document from a Word template and attaches it to the case.|
||Converts a temporary case to a permanent object in the database.|
|Post to pulse||
||Creates a message and sends it to the Pulse social stream.|
||Sends a notification to an iOS or Android mobile device to indicate that a case requires user action.|
|Run data transform||
||Runs a data transform.|
||Send formatted emails to custom recipients.|
||Sends a notification to recipients over multiple channels.|
|Update a case||
||Updates the current case or all child cases and descendants.|
|Search duplicate cases||
||Automatically searches for duplicate cases using set conditions.|
||Pauses a case until a specified condition is fulfilled, such as timer or case status.|
||Asks the user to complete a questionnaire.|
Note: To learn more about flow shapes, see the Pega Community article Flow shapes.
Send email automation use case
The Send email automation helps to send automated email correspondence to all relevant parties.
For example, consider an online shopping website. You can use the Send email automation to send an email to the customer informing them about new offers without any user interaction. You can configure how your application determines the recipient and compose the email content.
Create PDF automation use case
The Create PDF automation helps to create and attach a screenshot of a view to the case in the PDF format. The view in use must exist before configuring the automation. During execution, the view is rendered, and the screen is captured and converted to a PDF file.
For example, consider a customer who fills out an application for a travel visa. The customer is presented with a series of views to enter their personal information, travel history, the reason for the upcoming visit, and a summary view to review their selections before submitting the visa application. After submitting the application, the customer receives a PDF screenshot of the summary view of their visa application.
Run data transform automation use case
The Run data transform automation helps to run the selected data transform rule at run time.
For example, consider a checkout process of a purchasing application. The customer provides a shipping address and is prompted for the billing address. If the shipping address is the same as the billing address, it is efficient to use a data transform to copy the shipping address to the billing address rather than have the customer reenter the same address. To learn more about data transforms, see the Pega Community article Data transforms.
Check your knowledge with the following interaction.