The AccuWork Schema Editor -- Overview
Using the AccuWork Schema Editor, you define an AccuWork issue database (AccuWork) A set of issue records, each of which implements a bug report, feature description, etc. Each depot can have its own issue database. Each issue database has its own schema., which will contain a collection of issue records (AccuWork) A data record, consisting of values of data fields, stored in an issue database.. Each depot The portion of the AccuRev repository that stores the entire history of a particular directory tree. See element, version. can contain one issue database, along with a custom-designed edit form (AccuWork) A fill-in-the-blanks form for displaying and changing the field values of issue records., through which users create and modify the issue records. You can make the edit form "smart" by defining validations (AccuWork) A rule, specified on the Validations subtab of the Schema Editor, that controls a particular edit-form field. This can take various forms, including specifying a default value, making a field required, and modifying the list of choices in a multiple-choice listbox. (edit checks) that specify default values, required fields, and interrelationships among multiple fields.
An issue database's workflow A directed graph, defined in the Workflow subtab of the AccuWork Schema Editor. The graph's nodes are the 'workflow stages' that an AccuWork issue record can pass through. The graph's arrows are the 'workflow transitions' that users invoke to migrate issue records from stage to stage. (AccuWorkflow configuration) is defined on the Schema Editor's Validation and Workflow subtabs.
Choose Admin > Schema Editor from the GUI main menu. The first time you invoke this command in a particular depot, AccuWork offers to use the repository's default schema. Accepting this offer copies a set of XML-format configuration files from the site_slice/ dispatch/config subdirectory to this depot. [note ]
The Schema Editor tab includes these subtabs:
At any time while working in the Schema Editor, you can click the Save button in the lower right corner of the Schema Editor tab. This saves the current state of the schema to a set of XML-format files in subdirectory dispatch/config of the depot directory (slice) in the AccuRev repository :
Contents of the Schema subtab: schema.xml
Contents of the Layout subtab: layout.xml
Contents of the Lists subtab: lists.xml
Contents of the Relationship Types subtab: relation_types.xml
Contents of the Validation subtab: logic.xml
Contents of the Workflow subtab: custom_actions.xml and logic.xml
Contents of the Change Package Results section of the Change Packages subtab: cpk_fields.xml
Contents of the Change Package Triggers section of the Change Packages subtab: cpk_promote_queries.xml