LinkedIn
Copied!

Table of Contents

Creating an automation

Create an automation that you can use in Case Designer, flows, REST services, and activities to perform specific tasks. For example, you can configure an automation to move a case to the next stage, or to create a new case.

  1. In the header of Dev Studio, click Create Technical Activity .

  2. On the Activity Record Configuration page, in the Type field, select Automation.

  3. In the Operation field, choose the operation that you want this automation to perform:

    • To move a case to the next stage, select Change stage.
    • To create a new case, select Create.
    • To delete a case, select Delete.
    • To read the data stored in a case, select Read.
    • To update data stored in a case, select Update.
    • To specify an operation that is not included in the Pega-provided list, select Other, and then in the New operation type field, enter the new operation.
  4. In the Label field, enter a description of the purpose of the automation.

  5. To change the default identifier, in the Identifier field, click Edit and then enter a unique value.

  6. In the Context section, in the Apply to field, press the Down Arrow key and select the class that defines the scope of the automation rule.

  7. In the Add to ruleset field, select the name and version of a ruleset that stores the automation rule.

  8. Click Create and open.

Configure the inputs and outputs that this automation requires. For more information, see Configuring validation for text inputs and outputs in automations.
  • Configuring inputs for an automation

    Define specific inputs in an automation rule to create a contract so that users understand how to use your API. The inputs define the data that the system expects to receive from an external application.

  • Configuring outputs for an automation

    Define specific outputs in an automation rule to create a contract so that users understand how to use your API. The outputs define the data that the system returns to an external application.

  • Configuring validation for text inputs and outputs in automations

    You can validate text type inputs and outputs by configuring a JSON schema and then uploading a .yaml file. The JSON schema easily transfers the data to the REST service from the automation rule. The .yaml file generates the Swagger documentation with the sample JSON request and response.

  • Configuring errors for an automation

    Define a set of the most probable errors that your automation can return to an external application. By specifying these errors in the automation, the application consuming your API can determine how to handle each possible error scenario.

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.