Reduce complexity and activity dependencies with automations
Automations are APIs that follow a RESTful pattern and have a contract that clearly defines strongly-typed inputs, outputs, and error messages. Because this contract is separate from implementation, you can include automations in your case design to reduce complexity and replace dependencies on activities.
Pega Platform™ 8.1 introduces the new development model, delivers the Change stage and Change to next stage automations, and the new Automation rule. You can use the Change stage and Change to next stage automations in flows or in steps in the case life cycle. You cannot create new automations; you can only view the automations that Pega 8.1 delivers.
Future releases will enrich the core functionality of the automation rule and deliver additional automations.
The following figures illustrate the configuration of the Change Stage automation.
Input parameters and return values
Error codes and messages
For more information, see Viewing automations.
Published August 9, 2018 — Updated October 2, 2018