Learn how to develop schemas by using the HCL Compass Designer.
You can develop or modify schemas with the HCL Compass Designer.
This topic explains the concepts of HCL Compass packages and integrations.
This topic provides an overview of the tasks typically performed by a schema developer.
The HCL Compass Designer includes several different windows, or views, that you will use to perform your schema development tasks.
This topic explains the concept of a HCL Compass schema.
To modify how change requests are handled, you need to use the Designer to customize the records and fields of a schema.
This topic explains the concept of using schemas and packages in HCL Compass.
Follow these guidelines when you apply a package to a schema.
This topic lists the HCL Compass packages that are currently available, grouped by category.
This topic explains the general steps involved in applying a package to a schema.
The most commonly used packages are Notes, Attachments, and Email.
Before you apply new packages or package versions, you can check which package versions have already been applied to a schema.
This topic explains the concept of upgrading packages in HCL Compass.
Use the AuditTrail package to specify which records are to be audited when they are created or changed. When you enable a record type for audit trailing, all changes to records of that type are audited. You can also disable audit trails for any record type for which they have been enabled.
Use the eSignature package to require users to add their electronic signatures to records under the circumstances that you specify.
The Attachments package stores record attachments on an external server instead of in the HCL Compass database.
You must create a record form for each record type in your schema. You can also define a submit form for each record type.
This topic provides an overview of the process to create a security model.
This topic provides guidelines for using hooks to implement your workflow.
When multiple users attempt to simultaneously update a record, the database locking model ensures that the update from each user succeeds as a unit, but each update overwrites the previous update.
The Designer provides many ways to customize the underlying schema and functionality that the HCL Compass Web client accesses.
This topic provides a description of the supported HCL Compass Web client email features.
This topic describes how to import and export data between HCL Compass databases, and how to import data into a HCL Compass database from another defect tracking system.
This section describes eSignature extensions.