DUA Submission Screen¶

The DUA submission form is configured separately from the Open Market submission config. It controls the fields shown when creating a new Master contract.

Config file¶

applicationconfig/master_submission_config.json

This file follows the same structure as open_market_submission_config.json. Use displayConditions.placingSubType to control which fields appear for each contract type (BINDING_AUTHORITY, BULKING_LINESLIP, NON_BULKING_LINESLIP, CONSORTIA, FACILITY).

Key fields¶

Field	Description
`coverholderAgreementId`	Coverholder agreement ID. Required for `BINDING_AUTHORITY`, hidden for lineslips.
`scheme`	The contract name. Required across all DUA sub-types. (Label often overridden to "Contract Name".)
`brokerParty`	Broker. Required across all DUA sub-types.
`yearOfAccount`	Year of account. `BINDING_AUTHORITY` only.
`authorityType`	Underwriting authority type. `BINDING_AUTHORITY` only.
`contractRenewalType`	Defaults to `ANNUAL` for binding authorities.
`umr`	Unique Market Reference. Available across all DUA sub-types.
`mtaReasonCode` / `mtaReasonDescription`	Shown only on MTA submissions.

Using displayConditions for sub-type¶

Use displayConditions.placingSubType to show different fields for different contract types:

{
  "name": "coverholderAgreementId",
  "displayConditions": [
    { "placingSubType": "BINDING_AUTHORITY" }
  ]
}

{
  "name": "yearOfAccount",
  "displayConditions": [
    { "placingSubType": "BINDING_AUTHORITY" }
  ]
}

Fields without a displayConditions.placingSubType will appear for all sub-types.

Scheme field label¶

The scheme field is the contract name. In most DUA implementations, the label is overridden to "Contract Name" or "Binder Name" for clarity:

{
  "name": "scheme",
  "label": "Contract Name",
  "mandatory": true
}

Validation¶

The same validation mechanisms available for Open Market forms apply here: mandatory fields, display conditions, and field-level validation. See Submission Forms: Overview for details.

Applying changes¶

Push the updated master_submission_config.json and raise a Client Build & Deploy request in the Send Partner Portal to deploy it
Wait for Workbench's next periodic configuration refresh
Create a new Master contract and verify the form fields appear as expected for each sub-type