Adding Configuration Overrides

Configuration override auxiliary table entries can be set up to enable overriding plugin configuration field values at the item or project level.

1. In Work Center, click the user icon in the upper right of the page, and then select Manage Data.
2. In the Table field, select Configuration Override.
3. Click Submit.
   Tip: If you want to see if an override already exists, select any filters needed to limit results and click Search to search for existing rules.
4. Enter a title and description.
5. Click Add Row.
6. Enter Property Name, which is the internal name of the field you want to override.
   Tip: In the plugin configuration Overrides view, click the copy icon next to the field name to copy the field's internal name to the clipboard.
7. Enter Property Value, which is the value for the field that you want to use instead of the one defined in Release Control Administration.
   Note:

   • For selection values, use true for selected and false for deselected.
   • The characters " and ' in a URL must be encoded correctly, see: https://www.w3schools.com/tags/ref_urlencode.asp
   • To set up environment-specific configuration overrides, some process app customization is required. See Configuring Environment-Specific Field Overrides. After the customization is completed, you must:
     1. Enter the configuration field internal name in Property Name and the environment database field you want to use to override it in Property Value. For example:
        • To limit selection of a ChangeMan ZMF environment to its matching Release Control environment, enter promotionSiteFilter for Property Name and ZMF_SITE for Property Value.
        • To limit selection of a Deployment Automation environment to its matching Release Control environment, enter environmentFilter for Property Name and SRA_ENVIRONMENT_UUID for Property Value.
        Tip: You can copy the field's internal filter name to the clipboard from the configuration Overrides page using the copy button next to the field.
     2. Select the Env checkbox so that it will use the environment database field rather than the property values.
8. Select Scope as follows:
   • Global: The override is applied to all same-named properties for all configurations.
   • By UUID: The override is applied only to a specific configuration. For this, you must specify the UUID of the configuration.
   • By Tags: The override is applied only to configurations with a specified tag. You must specify the internal name of the tag.
     Tip: In Release Control Administration in a Tags page, click the copy icon beside the tag definition to copy the field internal name to the clipboard.
9. Enter Scope Value. For example, if UUID is selected for Scope, enter the UUID from the configuration to which you want this override to apply.
   Tip: In Release Control Administration in the configuration view, click the copy icon beside the UUID field to copy the UUID to the clipboard. The UUID is not shown on the configuration edit page.
10. Click Submit.