Packages
The Packages tab displays a list of packages added to the workspace. A package is a ZIP archive containing a workspace template or a widget.
To view the Packages tab, the user must have the Workspace privilege with the W operation.
You can add a package to a workspace from the Marketplace or from local storage.
Adding a Package from Local Storage
To add a package from local storage, go to the Packages tab and click + Add. In the dialog box that appears, click the upload area and select an archive, or drag the archive into the area. Then click Import.
If the imported package does not contain connections, it is added immediately. If the package contains connections, a connection configuration panel appears on the left side of the screen when you switch to the Control Panel tab.
Configure all connections and click Continue.
- If connections are not configured, some features of the added component may not work.
- If the package includes scripts, they become visible in the workspace only after the package is unpacked.
- Unpacked packages cannot be updated.
Package Actions
For packages added from the Marketplace, the following actions are available in the context menu:
- Go to package (opens the package page in the Marketplace)
- Unpack (grants edit access to all objects stored in the package; not available for widgets)
- Update (updates the package to the version stored in the Marketplace)
- Delete (removes the package along with all objects stored in it)
For packages added from local storage, the following actions are available in the context menu:
- New version (uploads a new version of the package)
- Unpack (grants edit access to all objects stored in the package; not available for widgets)
- Delete (removes the package along with all objects stored in it)
When a package is unpacked, all its objects become editable in the workspace. If an object is included in multiple packages, it becomes editable only after all packages containing that object are unpacked.
Package Statuses
Packages added from the Marketplace can have the following statuses:
- Current version (the package version matches the version stored in the Marketplace)
- Update available (the package version differs from the version stored in the Marketplace)
Packages added from local storage are assigned the Custom status.
If a package contains widgets, after unpacking, the widgets appear in the general package list with the Custom status. The unpacked package is removed from the list.
Was the article helpful?