Importing and exporting versioned use case types
Use this section to understand how versioned use case types are exported and imported across tenants, including version handling, status behavior, and ownership considerations.
Exporting versioned use case types
When you export a versioned use case type, the export package includes this information for all versions associated with the namespace:
- Configuration details, including filters, categories, subcategories, document entities, and table schemas
- Version information
- Status information
- Available translations
Importing versioned use case types
When you import a versioned use case type, the system processes the use case type and version based on the availability in the target tenant.
| Scenario | Behavior |
|---|---|
| The use case type does not exist in the target tenant | The system creates the use case type with the imported version |
| The use case type exists, but the imported version does not exist | The system adds the imported version to the existing use case type |
| Both the use case type and the imported version already exist | The system skips the imported version. |
Status handling during import
The status of the imported version determines how the system updates the target tenant.
- If the imported version has an Active status, the system sets the imported version to Active in the target tenant and changes the previously active version to Inactive.
- If the imported version has an Inactive status, the system imports the version as Inactive and does not modify the existing active version.
Imported version ownership
All imported versions are created by the System User and are available as read-only versions in the target tenant.