Enabling DUA

Several feature switches must be enabled for DUA functionality. These are set in applicationconfig/be_config.json, which is S3 business config — it sits in config/, not in the dynamodb/ directory.

Required feature switches

Switch / Config	Description
featureSwitches.DUA: true	Enables DUA features for this client implementation
configurations.DEC_CONFIG_V2.value: true	Enables the v2 declaration configuration, allowing different Placing Sub Types for declarations
homePartyId	Must match the partyId in trading-parties/{client}-insurer.json. Required for Workbench to start.

DUA config block

featureSwitches in be_config.json is a JSON-encoded string, so DUA is enabled by editing the embedded JSON inside the string:

"featureSwitches": "{\"DUA\": true,\"PAS\" : true}"

The verified shape of duaConfig in the base repository is:

{
  "duaConfig": {
    "duaImplementationDir": "dua",
    "masterBordereauReportingConfiguration": {
      "defaultValues": {
        "bordereauType": "RISK",
        "frequencyCode": "MONTHLY",
        "expectedBordereaux": 12,
        "maxReportingReturnTermDays": 14,
        "dateFormatType": "DAY_MONTH_YEAR"
      }
    }
  }
}

Config	Description
duaConfig.duaImplementationDir	The subdirectory under config/{client}/ that holds DUA-specific JSON (typically dua).
duaConfig.masterBordereauReportingConfiguration.defaultValues	Default values applied to new master bordereau reporting records (bordereau type, frequency, expected bordereau count, etc.).

Other duaConfig keys (such as bordereauInboundMailbox, bordereauRiskGenerationMode, duaValidationExecutionMode) have appeared in older or client-specific configurations. They are not present in the base repository's duaConfig block — confirm with your delivery lead whether any of these apply on your active core platform version before adding them.

bordereauRiskGenerationMode (where present)

Some implementations define a bordereauRiskGenerationMode setting that controls how certificate risks are versioned when a new bordereau arrives. Confirm whether this is honoured on your platform version.

Value	Behaviour
NEW_VERSION_WITH_MTA	Creates full MTAs when differences are detected between bordereau versions
NEW_VERSION_WITHOUT_MTA	Creates new versions without MTAs. Tracks history via RiskDecLink. Simpler and produces less data noise.

duaValidationExecutionMode (where present)

Where supported, this setting controls whether bordereau validation runs directly (DIRECT) or via a pipeline (PIPELINE).

Enabling the Risks/Certs tab

For bulked declarations (bordereau), the Risks/Certs tab must be enabled in ui_config.json:

{
  "riskDetails": {
    "tabs": {
      "risksAndCertificates": true
    }
  }
}

Enabling placing sub-type selection

To allow users to select the placing sub-type when creating a new declaration from a master risk, enable in ui_config.json:

{
  "submissionFormMeta": {
    "newInModal": {
      "enablePlacingSubTypeSelection": true
    }
  }
}

Validating the setup

After enabling DUA config:

1. Raise a Client Build & Deploy request in the Send Partner Portal to deploy the updated be_config.json
2. Wait for Workbench's next periodic configuration refresh — no manual base-data reload is required
3. Verify that the MASTER placing type appears in the business class
4. Create a test Master risk and confirm the DUA workflow actions appear

Note

DUA features do not appear in the UI until both featureSwitches.DUA: true is set in be_config.json and the business class has MASTER in enabledPlacingTypes. Both are required.