Administer Library Objects › How to Prepare the Production Environment for a New Release › Scenario: Export and Import Objects in a Content Package › About Release Versions

About Release Versions

Before you export a folder as a content package that contains a process and its component objects, the content designer takes the following actions:

• Sets the release version of each object(s)
• Sets the release version of the folder containing the object(s)

After import, objects have the same release version values you exported. When you export a folder as a content package, the imported content package is in nonmodifiable mode. The target users cannot modify the Release Version value that you set for this release. The Release Version value helps content designers, who work in the design environment, identify a specific version of an object in the production environment.

Note: CA Process Automation sets the Release Version attribute lock on both the object and the released version of the object. Therefore, users cannot modify the release version value for the imported object version or set release version values for new versions of the object.

Users cannot change nonmodifiable release version values after import. Consider the need for release versions based on what you are doing with the objects. For example:

• If you export from one design environment to another, (optionally) set Release Version attribute values and export the folder.
• If you export from a design environment to a production environment, then content designers are required to set Release Version attribute values for each object and the folder they are contained in. Designers then export that folder as a content package.

The following rules govern the export and import of Release Versions:

• If either of the following statements is true, Release Versions are nonmodifiable at import:
  • The objects are contained in a content package.
  • The object Release Version was nonmodifiable before export.
• CA Process Automation baselines imported versions when objects are imported as a content package (with nonmodifiable release versions).

  Note: If an object is imported again with the same release version, then that object is overwritten.

The following rules govern the copy and paste of imported objects:

• The first version of the object copy maintains the Release Version value and whether it is modifiable.
• If the current version of the original object is baselined and the object Release Version attribute is nonmodifiable, the object copy is also baselined.