The AccuWork Schema Editor

(Change Packages subtab)

Change Packages Subtab Layout

Working in the Change Package Results Section

Working in the Change Package Triggers Section

Composing a Condition

Composing a Query

Formatting the Table Displayed by the Change Package Trigger

AccuRev Enterprise supports an enhanced integration between AccuRev and AccuWork: any AccuWork issue record (AccuWork) A data record, consisting of values of data fields, stored in an issue database. can act as a change package A set of entries, each in the form of a basis-version/head-version pair, recorded on the Changes tab of an issue record. The change package records the changes to one or more elements, made to implement the feature or bugfix described in that issue record. Each entry in the change package describes changes to one element: the changes between the basis version and the head version. See patch., keeping track of which versions A particular revision of an element, reflecting a content change (files only) or a namespace change (files and directories). All versions are originally created in workspaces, and can subsequently be promoted to dynamic streams. The original (workspace) version is termed a 'real version'. Each promotion to a dynamic stream creates a 'virtual version', which serves as an alias for (pointer to) the original real version. were created to fix the bug (or implement the new feature) described in that issue record. For a thorough discussion, see the topic Change-Package-Level Integration between AccuRev and AccuWork.

The Change Packages subtab configures the way in which change packages are reported and updated, on a depot-by-depot basis.

See Also:

Schema Editor Overview

Change Packages Subtab Layout

The Change Packages subtab specifies the change-package configuration for the current depot. It is organized as follows:

Working in the Change Package Results Section

Click the Setup Columns button to bring up a dialog box in which you select a set of database fields, to be displayed as table columns. You can also specify the order of the fields.

After closing this dialog box, you can adjust column widths and change the order of columns using the techniques that work with all GUI tables.

Working in the Change Package Triggers Section

This section contains a set of condition/query pairs, one of which will be executed at Promote-time. If the first condition is satisfied, the first query will be executed; otherwise the second condition will be evaluated, and if it's satisfied, the second query will be executed; and so on. No error occurs if no condition is satisfied; the Promote command proceeds without triggering any change-package-level activity.

Note that there is no checkbox or button to enable the change-package-level integration. Rather, the existence of one or more condition/query pairs in this section implicitly enables the integration.

Composing a Condition

Each clause of a condition performs a test on the Promote destination stream (indicated by the keyword PROMOTE_DEST_STREAM). For example, this condition is satisfied if the user is promoting to either of the streams brass_dvt or brass_mnt:

 


The mechanics of composing the condition are similar to that of composing an AccuWork query.

Composing a Query

Corresponding to each Promote-destination condition is any AccuWork query, to selects a set of issue records. For the mechanics of composing the query, see the AccuWork Query Editor help topic.

Formatting the Table Displayed by the Change Package Trigger

To specify the format of the table displayed by the Promote command when it invokes the change-package-level integration between AccuRev and AccuWork, click the Setup Columns button to bring up a dialog box. Use this dialog box to select fields to appear as columns, the order of the columns (fields), and the sort order of the rows (records). After closing this dialog box, you can adjust the column widths and rearrange the columns.