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. You can view an automation rule to understand its inputs, outputs, and implementation, and create new automation rules.
You can use automations in utilities in flows and as steps in Case Designer. When you are prompted to select an automation, all automations in your application are listed, not just automations for the applies to context that you are in. You can also use automations in activities by using the Call-Automation method.
You can call an automation in any rule from which you can call an activity, with the following limitations:
- The automation is called using a primary page, which limits the automations that you can select. For some rules, you can use the Pages & Classes tab to make a temporary page to work around this limitation. If you do use a temporary page, you must remember to delete it when you have finished.
- Input and output parameters are listed together and might all appear to be inputs. Open the rule form to determine which parameters are inputs and which are outputs.
- Not all rules that can call activities support outputs. Review the help for the rule form to determine if outputs are supported.
- Page type inputs and outputs are difficult to use. You can use page name type parameters and utility functions to make handling page type inputs easier.
- Email automations cannot be called from a flow.
- Pega-supplied automations
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.
- Viewing automations
You can view an automation rule to understand its inputs, outputs, and implementation.
- 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.
- Simulating a response for automation outputs
Ensure that your automation returns the expected results by simulating a response. You can define values for your automation outputs and then test them before running the automation in an application that you are developing.
- Simulating a JSON response in automations
See how an automation presents the content in your JSON response to users by simulating a JSON response in draft mode. Simulating the JSON response provides you with an opportunity to test the automation output and update the sample data as needed.
- Automation troubleshooting
Automation rules have defined errors codes and messages for problems that might occur when your application is using an automation. Use the following guidelines to understand and troubleshoot automation error handling and flow problems.
Previous topic Fields that support the Global Resource Settings syntax Next topic Pega-supplied automations