Automations are Pega-supplied rules that you can use in Case Designer and flow actions instead of 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.

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 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.