Deployed package stages

This list shows the progression of packages through deployment phases, detailing each stage's status, timestamps, durations, and associated metadata such as customer, request type, and package name.

• EXPORT_TARGET_TENANT: This stage involves creating a local package by exporting the necessary resources from the source tenant. It is skipped during deployment if the Generate Compare Report check box is cleared.
• COMPARE_SOURCE_TARGET: This stage involves comparing the items in the local package against the data in the target tenant. It is skipped during deployment if the Generate Compare Report check box is cleared.

  See Compare source and target data during deployment and Aborting the deployment.

• VALIDATE_IMPORT: The integrity and compatibility of the selected package is checked before proceeding with deployment. This step ensures that the package contents align with the target environment and that no critical issues disrupt the deployment. During validation, the system assigns one of several possible statuses to indicate the current state or outcome of the process.

  See Responses of the Validate step.

• IMPORT: This stage involves transferring the data from the local package into the target tenant. Once the validation step is successful, the import stage begins automatically. The system imports the data and configurations specified in the local package into the target tenant. During the import stage, the status can be monitored through the deployment interface. The status changes from Pending to In Progress and finally to Success or Error based on the outcome.
• POSTIMPORT: This stage involves finalizing the deployment and ensuring that all configurations and data have been successfully applied to the target tenant. In the context of WFM, this stage is always skipped. This means that no additional actions are performed during this stage for WFM local packages.