What is the status of change requests when a revision package is exported?

When a revision package is exported in Pega, the correct understanding is that all change requests must be approved prior to the export. This ensures that only validated and reviewed changes are included in the package, maintaining the integrity and reliability of the application once it is deployed. By requiring approval, the system confirms that the changes have met all necessary criteria and standards, mitigating the risk of deploying unstable or untested features.

The other options imply varying degrees of acceptance for change requests. The notion that change requests could be merely evaluated but not necessarily approved undermines the rigor of the release process, as unapproved changes could potentially lead to issues once deployed. Allowing change requests in any status could lead to unstable revisions being exported, which is not acceptable in a production environment. Lastly, the idea that only pending requests can be included would severely limit the scope of what can be packaged for export, excluding potentially vital updates that have already been approved. Thus, the requirement for all change requests to be approved is a key component in ensuring quality control during the export process.