Which type of action allows the user to change case information without interrupting case processing?

The ability to change case information without interrupting case processing is a key feature in Pega that enhances user experience and efficiency. Local actions are specifically designed for this purpose, allowing users to make modifications to the case data in a seamless manner. When a local action is triggered, it opens a user interface where users can input or alter information, and once they are done, they can resume the original case flow without any interruptions.

This approach is beneficial because it enables users to update case details on the fly or address specific needs without halting the progress of the case. Local actions do not disrupt the ongoing case workflow, making them a practical option for real-time data adjustments and ensuring continuity in case handling.

Other types of actions, such as optional processes, do not have the same focus on non-intrusive updates; they typically revolve around processes that can be selectively executed. Case updates are generally more permanent and involved, focusing on significant changes within the case structure. Workflow steps represent basic actions within a case flow but aren't specifically geared towards seamless information updates like local actions are. Hence, local actions stand out as the correct choice for changing case information in a non-disruptive manner.