Resource Package Overview

Use cases

1. Enterprise version management.

   1. Within the same environment, importing assets from one workspace (Workspace A) to another (Workspace B) lets you manage versions, enabling version releases and isolation.

   2. Across different environments, the same principle applies when promoting assets, for example, from a development environment to a production environment.

   Note

   For managing assets across multiple environments, we recommend using the multi-environment migration feature, which supports asset cloning and user group permissions. For details, contact our sales team.

2. One-time asset replication.

   1. Reuse existing assets across workspaces to accelerate your workflow.

   2. Migrate all assets at once during an environment upgrade, such as moving from a public cloud environment to a private deployment.

How it works

Rather than simply copying assets, a resource package creates a one-way import mapping to support version control. For example, when you import dashboard 'a' from Workspace A to Workspace B, a new dashboard 'b' is created. The system records a mapping from the unique ID of 'a' to 'b' (a -> b). If you later edit dashboard 'a' and re-import it in replace mode, the system automatically overwrites dashboard 'b', eliminating the need to manually delete the old asset in Workspace B.

Limitations

• Resource packages are available only in the Professional Edition.

• Only an organization administrator can view and manage resource packages.

• Online imports are restricted to resource packages from the same organization. Offline imports do not have this restriction.

• Importing a resource package from a newer product version to an older version is not supported. For example, you cannot import a package from public cloud version 5.0 to a private deployment running version 4.0.

• A resource package includes only published assets and does not contain all metadata. The following table details what is and is not included.