Deployment

The same application version must be deployed on both the source and target tenant, and the same features must be enabled on both tenants.

Only unlocked folders and unlocked CloudSuites can be included in a local package. If a folder or CloudSuite with the same name already exists and is locked on the target tenant, a validation error occurs, and the local package cannot be deployed.

When a main folder is added to a local package, all its subfolders and process models are included in the package. If process models contain several versions, only the latest approved version is added. Draft models and draft versions are not included in a local package export. When deploying the contents of a folder through a local package, all the folder contents and the referenced entities, such as registry entries, images, and attached documents, are imported to the target tenant as well. If the folder or its contents already exist on the target tenant, the local content is overwritten with the newer content from the local package. Document attachments are added to IDM as new documents.

When a CloudSuite is added to a local package, all its contents, such as processes, insights, and relations mapping are included in the local package. Referenced content, such as process models and registry entries, is included in the same package. When you deploy a local package that contains a Process Mining CloudSuite, the CloudSuite content and all referenced content are imported on the target tenant. If the same content already exists on the target tenant, the local content is overwritten with the newer content from the local package.