Configuration field values can be overridden in several ways, depending
on your needs. Overrides are available as follows:
- Within a configuration, you can override base settings for fields
that have an Override checkbox beside them. See
Adding Plugin Configurations.
- These overrides are used to limit value selections when adding
objects in collections, such as requests, deployment units, and deployment
tasks.
- These overrides are also used by the system for validation and
execution.
- Using entries in the
Configuration Overrides table, you can pre-define sets of field
values for specific purposes, such as for a project, an application, or a
release.
- These overrides are used to limit value selections when adding
objects in collections, such as requests, deployment units, and deployment
tasks.
- You can define sets of overrides for all configurations or limit
them by configuration UUID or by a specified tag.
- 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, it must be used on a form.
- These overrides are not used when validating and executing
deployment tasks.
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 in an override has permission to make
selections but the user in the configuration or its internal override does not
have enough permissions to execute the deployment, the deployment may fail. The
user in the configuration or its internal override must have the permissions
necessary for validation and execution.
To override configuration settings:
- Select the fields for which overriding is allowed. See
Making Fields Eligible for Override.
- Add entries to the
Configuration Overrides table. See
Creating Configuration Overrides.
- Select an override entry in one of the following ways:
- In a release package or deployable release train, select an entry
in the
Configuration Override field. See
Release Control Getting Started
Guide
or online Help, "Creating Release Packages" or "Creating Deployable Release
Trains".
- In
SBM Composer,
process app designers can select the override entry for the project and hide
the field in the process app. This way the overrides are set automatically for
each new release package and deployable release train in that project.
For more details, see the following:
Copyright © 2012–2017 Serena Software, Inc. All rights reserved.