AccuWork issue records are used to implement the change package facility. The set of changes in a change package is indicated by a set of “Versions”, listed on the Changes subtab of an issue record, each with a corresponding “Basis Version”:
Each Version / Basis Version pair defines a set of changes to the element: the changes made since the Basis Version was created, up to and including the Version. The change package consists of such Version / Basis Version “patches” for any number of elements.
Various user commands and triggers maintain the contents of a change package: adding new versions and removing existing versions. There are also commands for comparing the contents of a change package to the contents of a stream, enabling you to easily answer the question, “Have all the changes made for Task A been propagated to Stream B?”
The following XML document requests the adding of two entries to the change package of issue record #433: for the element with element-ID 3, record the series of versions between Basis Version 4/3 and Version 4/6; for the element with element-ID 7, record the series of versions between Basis Version 4/2 and Version 4/9.
<acRequest> <cpkadd>
<user>john</user>
<depot>etna</depot>
<stream1>etna_dvt</stream1>
<issues>
<issue>
<issueNum>433</issueNum>
<elements>
<element
id="3"
real_version="4/6" basis_version="4/3">
<element
id="7"
real_version="4/9" basis_version="4/2">
</element>
</elements>
</issue>
</issues>
</cpkadd>
</acRequest>
Note that a <cpkdescribe> query is the only way to retrieve an issue record’s change package data. A
<queryIssue> query retrieves all the other fields, but not the change package data.
The following XML document requests the listing of certain transactions in the range 488–569, including the numbers of the change packages (issue records) modified by those transactions.
The transactions listed include explicit change-package requests (kind=dispatch, operation=
cpkadd or
cpkremove). Also included are
promote transactions that triggered
cpkadd operations.