Accessing packages

Packages are accessible to any admin account in Dawiso.

To work with them, navigate to Settings inline-svg-1 > Packages.

The Packages Settings is divided into two sections:

  • Marketplace: Our app store with ready-to-use packages.
  • Resources: A list of all packages installed in your Dawiso environment. Here, you can also configure packages to your needs.

Installing a new package

Installing a new package can add new functionality to your Dawiso environment or modify current settings to better suit your needs.

Install via Marketplace

  1. Navigate to Settings inline-svg-2 > Packages > Marketplace.
  2. Find your package and click the Install button.
  3. The package switches to Installed mode, allowing you to view it in the Resources section. Installed packages update automatically whenever a new version is published.

For more information, see Marketplace.

Tip

For on-premises deployments, the Marketplace is not available. Instead, refer to the GIT repository containing all standard Dawiso packages.

Install manually

  1. Navigate to Settings inline-svg-3 > Packages > Resources.
  2. In the top-right corner, click + New package.
  3. Give your package a key, a unique identifier for each package. Choose a key that reflects your package’s function. Keys must follow these requirements:
    1. It must be one string, meaning no spaces are allowed.
    2. DO NOT start your key with core_. This prefix is reserved for default Dawiso applications. When the Marketplace is enabled, Dawiso rejects any key beginning with core, in any letter case — when you create the package, when you rename it, and when you validate or install a version whose JSON declares such a key.
  4. Name your package, e.g., cust_business_glossary.
  5. Save your package.

Editing a package version

Open a package version to review or change its JSON definition, name, or description.

  1. Navigate to Settings > Packages > Resources.
  2. Click the package key to open its draft, or the latest installed version when there is no draft. To open a different version, choose Version history from the row menu and click the version.
  3. In the top-right corner, click Edit package definition to change the package name or description.
Warning

The package key can be changed only before the package is installed for the first time. Afterwards the key field is disabled.

The editor header shows the version number (or Draft for an unpublished version), the package key, and a Current version mark on the latest installed version.

Above the JSON code, the Version description panel is collapsible. Fill it in whenever you change a version. See Best Practices for why this matters.

A package has at most one draft at a time. Click + New version on the version history page to create one. You can also edit an installed or historical version directly and click Save: doing so creates the draft from your changes and opens it.

While a draft exists, installed and historical versions become read-only: typing into their JSON shows a notice with an Open draft link instead.

The JSON panel has:

  • Tabs: Code, Errors, Warnings, Applied Preview, and Applied Preview Graph.
  • Actions: Download, Copy to clipboard, and Fullscreen.

The footer has two buttons, both disabled until you make a change:

ButtonEffect
SaveStores the draft and validates it.
Save & InstallStores and installs it.

After a plain save, Install replaces Save & Install. You can also save with Ctrl+S.

If you leave the page with unsaved changes, a Save changes? prompt appears with Save, Discard changes, and Cancel options.

Downloading all packages

Download every package at once when you want a snapshot of your environment’s whole configuration — to archive it, to review it outside Dawiso, or to move it to another environment. To download a single package version instead, use the Download action in that package’s version list.

  1. Navigate to Settings > Packages > Resources.
  2. In the top-right corner, click Download all.
  3. The button shows a spinner while Dawiso prepares the archive in the background. You can leave the page — the export keeps running.
  4. When it finishes, a notification appears in the bottom-right corner with two links: Download file saves the archive, and View task opens the export task’s detail. The notification stays until you close it, and it is also added to your notification bell, so you can pick the file up later.

The archive is named all-packages-<environment>-<timestamp>.zip, where <environment> is your instance name and <timestamp> is the UTC time the export started.

The archive holds one JSON file per package, named <package-key>_<version>.json. Each file contains the latest versioned or installed version of that package.

Packages that only have a draft version are not included, because a draft is not yet a complete package. Data packages and automation packages are also excluded — download those from their own sections.