Getting Started ID: PM-NV-GS

TLDR

• You can start a new draft version or resume the current draft from the package properties dialog
• Each version is composed of assets and dependencies
• Before users can install your package on their site, you have to activate the package version
• Activating a package version is final. You cannot edit a version after it has been activated.

Starting or Resuming a Draft Version

Open package properties and click the first button in the toolbar.

If you are drafting your first version you will not have any assets or dependencies intially. Otherwise the assets and dependencies will be copied from your previous version for you to start working with.

Managing Assets and Dependencies

As long as your version is a draft, you can modify assets and dependencies. The assets that you work with while drafting a new version are live, meaning that the assets that you see are how they are currently saved on the source site (not how they are published). Any changes you make on the source site will be visible in the draft version, although some changes might not be visible until the draft is either edited, activated, or pre-activated. We will cover this topic in more detail in a later lesson.

Activation

A draft version may only be installed on other sites after it has been activated. Activation is the process of finalizing a draft version so that:

1. No more assets or dependencies may be added, removed, or modified.
2. The version contains everything that is necessary for it to be installed on other sites.
3. The version contains all of the latest data from the source site.

Note that activating a draft version is immediate and final. After you activate a draft version, you will not be able to make any changes to it other than editing the changelog. For this reason, it is imperitive that you do not activate a package version until it is completely ready. It is also a good idea to test each package version on another site to make sure it works as anticipated.

---

---