Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

The FlexFields page provides ability to configure user defined attributes for Deploy or Build Requests. When a Build or Deploy Request is submitted by a user, they will be prompted to enter values for the configured FlexFields. There are 10 FlexFields, for each scope, that are available for the user to setup additional properties that can be associated to a Build or Deploy Request. An example usage for a FlexField would be allowing the user to specify the change request number associated with the Deploy Request. These FlexFields can be viewed in the reports and tasks screen and could provide additional information about a specific Build or Deploy Request.


Build Request Scope

Build Request FlexFields are available through the lifecycle of your release. The value is set during the Build Request, and then is available to be used on subsequent deployments of that project version.


Deploy Request Scope

Deploy Request FlexFields are limited to only being used with the specific deployment being executed.

...


The active FlexFields will be available for users when submitting the Build or Deployment Request (see below). If the FlexField is configured as required, then the user must enter value. Other validations like Data Type, String length, Range check for numbers etc. are also performed as defined for a specific FlexField. Custom Groovy validations that are defined by the user in the administration page will be executed as well against the user input. FlexField values will be available in the Reports and Tasks to provide additional information regarding the Build or Deployment Request.


Build Request Form


Deployment Request Form