The Schema tab of the Schema Editor contains a table that details all the data fields defined for AccuWork in the current depot.If you are not using the repository's default schema, AccuWork initializes the Schema Fields table with two fields.
• issueNum: An integer-valued field that records the position of the issue record in the depot. This number is assigned when a user creates the record (i.e. at the first Save on the edit form), and it never changes.
• transNum: An integer-valued field that records the transaction number of the most recent update to the issue record. The transaction appears in the depot's transaction log -- the same log that records AccuRev transactions, such as keep and promote. The type of the issue-record-update transaction is dispatch.A record's issueNum value never changes, but its transNum value changes each time a user Save's the record. issueNum and transNum are indexes into two different databases.The change-package-level and transaction-level between AccuRev and AccuWork also update issue records, and so changes the value of the transNum field. (See Change-Package-Level Integration between AccuRev and AccuWork on page 326 and Transaction-Level Integration between AccuRev and AccuWork on page 329.)You can define any number of additional fields in the schema. Follow these steps for each new field:
1. Click the Add button at the bottom of the Schema subtab.
2.
• Name: The official field-name of the field. AccuWork users don't ever need to know this name -- they know the field by its label. The field-name must not contain any SPACE characters. Validations must be expressed in terms of the field's name, not its label.
• Type: One of the data types supported by AccuWork.
• Label: The field-label character string that identifies the field on the edit form. A field-label can contain SPACE characters (e.g. Last Name ).
• Report Width: An integer that determines the relative width of the field in the HTML table created when the user clicks Export on the edit form of an individual issue record.
3.
4. In the Field Values box to the right of the Schema Fields table, specify additional information about the field. The kind of information required varies with the data type.Repeat the steps above as often as required to create new fields. Your field definitions are not saved until you click the Save button in the lower-right corner of the Schema Editor tab. You cannot save your work until you place at least one field in the edit form (Layout subtab).To remove an existing field (except for issueNum and transNum), select it and click the Remove button. The field disappears from the Schema tab and can no longer be used in the edit form. But any data stored in existing issue records is preserved.When you remove a field from the schema, AccuWork checks whether the field is used in the edit form. If so, it removes the field from the edit form
1. Check the Show Including Hidden checkbox. All removed fields appear in the list, with a gray background.
2. Select the field to be restored, and click the Reactivate button.TheIssues > Look Up command prompts the user to enter a value, then uses that value to locate an issue record.
You can configure another field to be used for issue-record lookups, using the 3pty ITS Key listbox. (This feature is designed to facilitate AccuBridge integrations with third-party issue-tracking systems.)Thereafter, the Issues > Look Up command will prompt for a value to be matched against the specified field.The Issues > Look Up command requires an exact match between the user's entry and the value in the issue-record field. Exception: upper-case/lowercase differences are ignored. This can cause problems if the lookup field is a Text field.AccuRev guarantees uniqueness of the issueNum field value only. It allows duplicate values in all other fields. Be sure to specify an alternative lookup field whose values are rendered unique by some other mechanism. If a user performs a lookup on a non-unique value, an error occurs:Integrating Configuration Management and Issue Management: the `affectedFiles' Field and Change PackagesIf you wish to enable the integration of a depot's version-controlled files and its AccuWork issue records, define a field whose name is affectedFiles. The field's data type must be Text. You can choose any label for the field. (Such a definition is included in the default AccuWork schema.)accurev mktrig -p <depot-name> pre-promote-trig client_dispatch_promoteThe integration routine writes the transaction number of each promote command to the affectedFiles field of a particular issue record. Alternatively, in the AccuRev Enterprise version of AccuWork, the integration routine records each promoted version in the issue record, in a special section named Changes . This section is maintained automatically by AccuWork -- you don't need to define any fields to enable this additional aspect of the integration.Each field you define in the Create New Field window must have one of the AccuWork data types listed in the table below.
Any character string. For multiple-line fields, the string can include line-terminators. Height: number of lines displayed for the field in the edit form (default: 1). For multiple-line fields (height > 1), the edit form includes an expand/contract button to increase/decrease the number of lines displayed.Width: relative width of field in the edit form. One of the strings specified in the Field Values box for this field. In the edit form, a list-box containing this set of strings is offered to the user. In the edit form, the user fills in fields that indicate a time, to the granularity you specify here. One of the principal-names in the user registry maintained by the AccuRev server. In the edit form, a list-box is offered to the user, containing the names of all registered AccuRev users. A Project stream name in the current depot. A numeric value, indicating a number of hours. Decimal values (e.g. 4.5) are allowed. One of the strings specified in the definition of a particular named list. The name of an existing list, defined on the Lists subtab.In the edit form, a list-box containing the set of strings defined in the named list is offered to the user. Any character string (variant of text field type) In the edit form, an Add Text control appears above the input field. The user can type directly into the input field, or can click the Add Text control and create a "log entry" in the popup window that appears. A set of attachment definitions. Height, Width: the height (number of lines) and width (approximate number of characters) of the edit-form field that lists the attachment definitions. You cannot create a field with this data type; it is used only by the built-in fields issueNum and transNum .
• For a choose field, the set of possible values -- an ordered list of strings -- is part of the individual field definition. You enter the possible-values list in the Field Values box for that field.
• For a list field, the set of possible values is also an ordered list, but it is not part of the individual field definition. In the Field Values box, you specify the name of one of the lists created on the Lists subtab. Any number of list fields in AccuWork (within a single depot) can use the same named list.The mechanics of defining the ordered list is similar in the "local" case (for an individual choose field) and in the "global" case (on the Lists subtab, for use by any number of list fields). On the Lists subtab, you must supply a ListName for the list; for an individual choose field, the possible-values list doesn't need or have a name.When you create a field of type Relationship, you must select the Duplicate, Subtask, or Dependency relationship type for the field. On an edit form, the field's edit-widget is a pair of tables. The upper table displays "inward" or "child" relationship links -- that is, links from other issue records to the current record. The lower table displays "outward" or "parent" relationship links -- that is, links to other issue records from the current record. (Multiple-link chains are not allowed -- each issue record can be related to others by child links or parent links, but not both.)The figure below show how a Duplicate relationship field appears in an edit form. A relationship field of type Subtask or Dependency appears similarly.
AccuRev, Inc. |
Phone: 781-861-8700 |
Fax: 781-861-8704 |
support@accurev.com |