Viewing automations
You can view an automation rule to understand its inputs, outputs, and implementation.
- In the navigation panel of Dev Studio, click .
- Locate the automation that you want to view and click in its row. Automations have the activity type AUTOMATION.
- On the Definition tab, you can view the following information:
- Overview – A description of the automation and how to use it.
- Inputs – Each input to the automation, with its name, ID,
description, data type, page class, and whether it is required.
If a specified list of input values is required, the included values are validated. This means that the automation will not run if you skip a required parameter or pass in a value that is of an incorrect type, for example, if you pass in a string to an integer type parameter. If the inputs are not valid, an “Invalid Inputs” error occurs.
Page type inputs and Resource Page type inputs expect a page reference, that is, a string used to find the page on the clipboard. If you do not pass in a page reference or if there is no page at that reference, an error is returned. If a page is found, its object class must match the input page class or inherit from it; otherwise, an invalid input error is returned.
- Outputs – Each output from the automation, with its name, ID,
description, data type, and page class.
You do not have to use all the outputs. To use an output, you must provide a property reference that can hold that type of output, for example, a string property for a string output. Like inputs, outputs are also validated.
- Errors – Page type outputs expect a property of type string. A
page reference is stored in that property so that you can return to the page later.
The page disappears at the next interaction boundary, so if you want to use it outside
of the rule from which you called the automation, you must make a copy. Displays a
list of error codes and descriptions.
Errors that occur when the automation runs are returned in the Automation Errors output. If an error occurs that is not in the automation rule, it is converted to a run-time error before being returned.
All automation errors require a category. Categories are created using a message. For more information, see Creating a message.
- Optional: Click the Implementation tab to view the following information:
- Implementation rule – The implementation rule and type.
- Parameters mapping – The mapping between the inputs, implementation rule and outputs.
Previous topic Pega-supplied automations Next topic Creating an automation