Pre-Activate ID: PM-NV-PA

TLDR

• Pre-activating a draft version prepares it for activation by running a series of tests and modifying assets in the package as needed.
• If pre-activating a draft version causes any changes to the package, you should review the changes before activating it.

What is Pre-Activation

Before you can activate a package version, there are a number of tests that it must pass - which may modify the version in the process:

1. Each asset may only belong to package. Assets belonging to another package will automatically be removed. This should be rare except in the case where you attempt to author multiple packages on the same site at the same time with one or more overlapping assets.
2. Any assets that are marked as trashed but are no longer trashed on the source site will be changed to Install and Update.
3. Any assets that are trashed or no longer exist on the source site will either be removed (if they are mapped or ignored) or set to trashed.
4. All mappings will be updated in the package version:
   1. Any required assets referenced from InstallOnly or Update assets in the version will be set to MapRequired
   2. Any "optional" assets referenced from InstallOnly or Update assets in the version will be set to MapOptional
   3. Any existing mapped assets in the package version that are no longer necessary will either be set to ignored if you have already assigned it a description or removed if you have not assigned it a description.
5. All asset names will be updated where possible

When to Pre-Activate

Your package version will automatically be pre-activated for your when you attempt to activate it, so you may not always need to manually pre-activate your packages. However, if you have made significant changes to your package - such as adding new pages or other objects that have a lot of dependencies - it may be beneficial to manually pre-activate your package and review the affects of your changes. Generally speaking this will be most valuable directly before beginning your internal review process or activing the new version.

Following pre-activation, you should pay particular attention to the mapped assets. Users will not be able to install your package until they have either selected mappings for all of the assets that require mapping or have ignored them. Furthermore it can be helpful for them to select values for most of the optional mappings as well. Providing a description for mapped assets can help users significantly in their determination of how to handle them. The best practice for asset descriptions is to write descriptions for all required and recommended mappings where the description is as short as necessary to accurately communicate both the purpose of the mapped asset and how it is used in the package.

How to Pre-Activate

There are two ways to pre-activate your package version:

The first way to pre-activate your package version is to attempt to activate it. Before activating a version, Marketpath automatically pre-activates it. If there are any changes during pre-activation, you will be prompted to review the changes before re-activating the package.

The second way to pre-activate your package is to click the "Pre-Activate" button in the Assets & Dependencies toolbar.

---

---