Creating a Change Package

User Help > Grouping Units of Work in Change Packages > Creating a Change Package

CLI	si createcp

You can create a change package in PTC RV&S in one of the following ways:

• Select Change Package > Create or File > New > Change Package

• When performing a member operation, in the Change Package portion of the dialog box that displays, click Create.

If workflows are enabled, when creating a change package you can choose a PTC RV&S item as well as populate Description template content to associate with the change package.

Your ability to create a change package associated with an item is based on the change package creation policy for the item type.

The Create Change Package dialog box includes a data filter panel that allows to you search the list of eligible items using a text string. When creating a change package, enter your search text in the Show items containing field and the list of items is filtered against all visible columns according to the specified text.

Working With Change Package Entries

Once a change package is created, you can add entries to that change package by selecting it in the Change Package portion of the dialog box or wizard when performing member and subproject operations. To add change package entries to a change package, the PTC RV&S client must be connected to the server the change package resides on.

When performing an operation that can add entries to a change package, keep the following in mind:

• A change package can only be specified if your administrator has enabled the use of change packages.

• You must specify a change package if your administrator has made change packages mandatory.

• If change packages are not mandatory, and if no change package is applicable, you can select <none> in the Change Package field.

• If change packages are mandatory, depending on change package configuration set by your administrator, you can bypass the change package requirement by selecting bypass in the change package field.

• You cannot commit a change package entry that has an invalid project configuration path. Instead, you must discard the change package entry and recreate it in the correct context. For example, if a subproject at a higher level was moved, the same operation can be created under the context of that new subproject.

You can also add an entry to a change package by dragging the member from a Sandbox view to a Change Package view (or change package in the Change Packages view). The Check Out dialog box displays with the change package selected.

After the operation is completed, the entry is added to the change package. In the Project or Sandbox view, the change package’s ID displays in one of the member’s CPID (change package ID) columns depending on the operation, though not all CPID columns appear by default. In the Working File Changes view, the change package’s ID displays in the CP ID column.

If the change package contains deferred operations or lock entries, a

icon displays beside the change package ID in the Working CPID column of the Sandbox view.

Change Package Entry Types

The following table displays change package entry types and the operation that creates them.

Change Package Entry Types

Operation

Add

Add Member

AddFromArchive

Add Member From Archive

AddSubproject

Add Subproject

AddSharedSubproject

Add Subproject, Share Subproject

ConfigureSubproject

Configure Subproject

CreateSubproject

Create Subproject

Drop

Drop Member

DropSubproject

Drop Subproject

Import

Import Member

This entry is no longer supported but may appear in change packages created from earlier versions of Integrity.

Lock

Lock Member, Check Out

This entry is used for exclusive locks.

NonExclusiveLock

Lock Member, Check Out

MoveMember

Move Member

MoveSubproject

Move Subproject

Rename

Rename Member

Update

Check In (with updating member revision)

UpdateRevision

Update Member Revision

UpdateArchive

Check In (without updating member revision)

Was this helpful?