Which statement is correct regarding automation shapes in Pega?

An Automation shape is indeed designed to manage various aspects of case processing in Pega, including the ability to change the stage of a case. This capability allows for automation in workflows, enabling a smoother transition between different stages as the case progresses. By using automation, business architects can encapsulate complex processes into a single shape, enhancing efficiency and reducing the need for manual intervention.

The option stating that an Automation shape can only create a new case is limiting and does not encompass the full functionality provided by automation capabilities in Pega. Furthermore, the claim that an Automation shape cannot be used in a workflow disregards its core purpose, which is to enhance workflows and automate repetitive tasks. Lastly, while data processing can be a function of an Automation shape, stating it is used solely for that purpose overlooks the broader scope of actions and modifications that can occur within a case lifecycle. Therefore, the assertion regarding the ability of an Automation shape to change the stage of a case accurately reflects its role within Pega's workflow automation framework.