Home
Developing
Learn how to develop schemas by using the HCL Compass Designer.
Developing Schemas
You can develop or modify schemas with the HCL Compass Designer.
Creating a security model
This topic provides an overview of the process to create a security model.
Designing a security system
In a security system, user membership is defined by user groups. The user groups are associated with specific customers.

Developing
Learn how to develop schemas by using the HCL Compass Designer.
- Developing Schemas
  You can develop or modify schemas with the HCL Compass Designer.
  - Understanding the functions of the HCL Compass schema developer
    This topic provides an overview of the tasks typically performed by a schema developer.
  - Overview of the HCL Compass Designer interface
    The HCL Compass Designer includes several different windows, or views, that you will use to perform your schema development tasks.
  - HCL Compass schemas
    This topic explains the concept of a HCL Compass schema.
  - Customizing a schema
    To modify how change requests are handled, you need to use the Designer to customize the records and fields of a schema.
  - Schemas and packages
    This topic explains the concept of using schemas and packages in HCL Compass.
  - Packages and integrations
    This topic explains the concepts of HCL Compass packages and integrations.
  - Test Management and Requests
    You can use the Compass TestManagement and Requests feature to create and track test plans and add approval processes to the record.
  - Working with Forms
    You must create a record form for each record type in your schema. You can also define a submit form for each record type.
  - Creating a security model
    This topic provides an overview of the process to create a security model.
    - Hiding records
      This topic explains how to hide HCL Compass records.
    - Privileged Queries feature
      The Privileged Queries feature works in conjunction with the security context feature. For more information, review the Hiding records topic in the Creating a security model section.
    - Protecting from password attacks
      HCL Compass releases support enhanced security for HCL Compass authenticated users. HCL Compass can now limit the number of login attempts for a user before the user becomes locked out. HCL Compass can also limit the number login attempts from a host connecting through HCL Compass Web.
    - Password protection scenarios
      The system uses the configuration options to govern how it protects from brute force attacks.
    - Designing a security system
      In a security system, user membership is defined by user groups. The user groups are associated with specific customers.
    - Security example
      This topic provides a HCL Compass security example based on hiding records.
    - Using other HCL Compass security features
      This topic provides information about available HCL Compass security features.
  - Using hooks to customize your workflow
    This topic provides guidelines for using hooks to implement your workflow.
  - Record locking
    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.
  - Customizing the Web
    The Designer provides many ways to customize the underlying schema and functionality that the HCL Compass Web client accesses.
  - HCL Compass email
    This topic provides a description of the supported HCL Compass Web client email features.
  - Importing and exporting data
    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.

Designing a security system

In a security system, user membership is defined by user groups. The user groups are associated with specific customers.

Elements of a security system shows the elements used to design a security system. Each defect record in a security system references one or many customer records.

The image illustrates the use of a security context to control which records a user group can view. — Figure 1. Elements of a security system

The security design in Elements of a security system works in this way: User A logs in to the HCL Compass environment. User A is a member of Group A, which is associated with Customer A. When User A runs a query or requests a record, all defects are filtered on the security context of Customer A. Only defects that belong to Customer A are included in the result set.