What happens when a revision package is made available into production?

When a revision package is made available in production, all operators with an access group to the current application version experience the changes. This means that as soon as the revision package is deployed, the updated functionalities and configurations become visible and usable to the operators who are authorized to access that version of the application. This is essential for ensuring that the enhancements or fixes included in the revision package are immediately leveraged by the relevant users in their ongoing activities.

The ability for all relevant operators to access the changes without needing to log out or wait for specific permissions fosters agility and adaptability within the organization, allowing users to work with the most up-to-date version of the application right away. This aspect of Pega's deployment strategy helps streamline workflows and enhances productivity.

In contrast, other scenarios—such as only the visible changes being limited to certain users or requiring a logout—do not reflect the design of Pega's deployment process, where timely access to updates is crucial for efficient operation.