At what point is a change considered finalized in Pega applications?

In Pega applications, a change is considered finalized when it is active for all users in the access group. This means that the change has been fully implemented and is now accessible to all intended users, allowing them to utilize the updated features or functionalities in their operational processes. Activating a change for all users indicates that the change has been deployed across the relevant environments and that end-users can leverage the modifications made, impacting their daily tasks and workflows.

While approval processes and testing are crucial steps in the development lifecycle, they do not in themselves finalize the change. Approvals from a System Architect or testing and validation ensure quality and correctness, but it is the activation for users in the access group that represents the culmination of these processes. Modified business rules may play a role in the changes, but simply modifying a rule does not lead to finalization until it is made active for users.