Auxiliary Table Level Configuration Overrides

Using entries in the RLC Configuration Overrides table, you can pre-define sets of field values for specific purposes, such as for a project, an application, or a release.

Auxiliary table level configuration overrides are used to:

Note: These overrides are not used when validating and executing tasks. Overrides available at the configuration level, which override base configuration settings, are used when validating and executing tasks. See Adding Action and Item Configurations.
CAUTION:
It is not recommended to override connection information this way unless you are doing it only to restrict the selections for objects such as requests. If a user ID specified in an override has permission to make selections but the user ID specified in the configuration or its internal override does not have enough permissions to execute the deployment, the deployment may fail. The user ID in the configuration or its internal override must have the permissions necessary for validation and execution.

To override configuration settings:

  1. Select the fields for which overriding is allowed. See Making Fields Eligible for Override.

    image

  2. Add entries to the Configuration Overrides table. See Adding Configuration Overrides.

    You can use dynamic values in the Configuration Overrides table to access the exact values for fields set within an item, such as a release package or deployable release train. To dynamically override the field value, the field must be used on a form.

    The following figure shows property value overrides for Environment Filter. For information on using environment-specific overrides, see Configuring Environment-Specific Field Overrides.

    image

  3. Apply the configuration override entry in release items. See Applying Configuration Overrides.

    image

For more details, see the following: