From process items to change packages



Process Items

StarTeam 2009 and StarTeam 12.0

Process Items in StarTeam 2009 - using Process Tasks


Up until the 2009 Client release, if a Process Item was specified for file check-in, the SDK created a Process Task, created a link from the selected Process Item to the Process Task and then created links from the Process Task to the files.

Process Items in StarTeam 12.0 – using Change Packages


StarTeam 12.0 moved away from Process Tasks for Check-in and instead using Change Packages.  Links and Process Tasks are no longer created. Instead, a Trace records the relationship between the Process Item and the Change Package. The Change Package records the relationships to the checked in items (at their relevant versions) using Changes. Check-in Change Packages also support in-view moves and deletes.


Using the Replay viewer, Check-in Chance Packages can be replayed to other views, as standard PROMOTE, REBASE or REPLICATE VCM operations.


Finally, Check-in Change Packages provides both Audit & Historical context of the set of aggregated changes in a transacted commit.



Advanced Settings for Check-in Change Packages


The creation of Check-in Change Packages may be potentially expensive, particularly for organisations that have daily bulk check-ins.  A single Change Package may have numerous associated changes. 

For these customers, a new server configuration parameter has been introduced:


<option name="CheckinChangePackages" value="0"/>


Specifying the entry in the starteam-server-configs.xml file turns OFF the creation of Check-in Change Packages, but if and only if there is no process item associated with the check-in. Otherwise, this flag is ignored.

Parity & Compatibility


StarTeam traditionally supports a 1 forward, 1 backward compatibility policy with regards to all of its products. StarTeam have traditionally supported cross client server compatibility, so that, for example, a 2008R2 CPC/SDK would work against a 2009 server, a 2009 CPC/SDK would work against a 12.0 server and vice-versa, i.e. a 12.0 CPC/SDK would work against a 2009 server.

 However, MicroFocus does not recommend  mixed client environments. You should avoid a 2009 CPC/SDK and a 12.0 CPC/SDK both running side by side against a 2009 server or a 12.0 server.  The reason that we do not recommend multiple versions of the client connecting to the same server is that it can avoid and prevent users getting into an odd state by mixing capabilities (ie, certain features not being visible or being affected differently).

In the case of Process Tasks / Check-in Change Packages StarTeam would now have two clients providing two different check-in models on servers that support both models. As a consequence, it is therefore imperative mixed clients are not in use.


The StarTeam Server does provide a mechanism to ensure that all clients are at the same version.

The app-control.xml file in the server configuration install directory can be primed to require a specific SDK version by application name. e.g.

    <AllowedApp Name="CPC*" MinimumSDKVersion="12.0" />

## Accepts applications starting with pattern CPC with minimum version first part of 12.0 or greater

When app-control.xml is turned on, the server automatically rejects applications (by name) that are at lesser versions of the SDK than is allowed.


How To-Best Practice
Comment List