Glossary¶
Full alphabetical glossary of terms used in Send Workbench documentation and configuration.
Action group — a named grouping that organises related risk actions into a visual section on the risk record view. Defined in business-constants/action_group.json. Example groups: rate, broker_response, bind.
Asset management — the feature that handles upload and validation of Schedule of Values (SOV) spreadsheets. Supports LOCATION (address) and CUSTOM (vessels, aircraft, etc.) asset types.
be_config.json — the master backend configuration file. Sits in the config/ directory tree — it is S3 business config, not a DynamoDB record. Controls feature switches, application settings, DUA config, and the homePartyId.
Bordereau — a spreadsheet of risk, premium, or claims data submitted by a coverholder under a DUA contract. Ingested by Workbench to create Certificate risks.
Business class — the top-level product category (Line of Business). Examples: Property, Casualty, Professional Lines. Defined in business-class/{name}.json.
Business config — the set of JSON configuration files under config/ in the repository. Includes business classes, workflow, forms, documents, rules, and roles. Deployed via the Send Partner Portal on request.
Business constant — a shared lookup dictionary mapping item codes to display labels. Stored in business-constants/{name}.json. Used for dropdowns, classifications, and display labels.
Certificate — an auto-generated risk record created from bordereau processing. Represents one insured item from a bordereau spreadsheet.
classConstantLists — a filter in the business class file that restricts which business constant values are visible for a specific LOB. Does not define new values — filters existing ones.
Client microservice — the Spring Boot application specific to each client. Contains client-specific endpoints, custom business logic, and the implementation of interface extensions from riskwire-extensions.
Clause library — an admin feature allowing DOC_ADMIN users to manage document clauses without code deployment. Enabled via features.clauseLibrary: true in ui_config.json.
Completion pipeline — a pipeline triggered when a user completes (submits) a risk action. Configured on the action as completionPipeline.
computationConfig — configuration on a screen meta data element that enables dynamic computation. Uses emitter/subscriber pattern to auto-calculate values from repeatable sections.
Contract structure — the contract_structure risk action that defines the sections (policies) and coverages (product covers) of a DUA Master contract.
Coverage — in the DUA/asset management context, a data field captured per asset row (e.g. COV_DUA_INCEPTION_DATE, COV_DUA_PREMIUM_AMOUNT). Defined in business-constants/coverage.json.
Declaration — a child risk under a DUA Master contract. Placing type DEC. Can be individual (INDIVIDUAL_DEC) or bordereau-based (INBOUND_BORDEREAU).
displayCriteriaExpression — a JSONPath expression evaluated against the risk context (ExpressionDO.jsonPathExpression + operatorType + testValue). Controls whether a risk action is visible to the user. true = show, false = hide.
displayExpression — a JavaScript expression evaluated against GET /v2/risks/{id}. Controls whether individual fields are shown on the risk record view.
DTC (Dec Type Code) — declaration type code: 1 = individual declaration, 2 = bulked (bordereau) declaration.
DUA — Delegated Underwriting Authority. A contract where an insurer delegates underwriting to a coverholder or MGA.
DynamoDB — AWS key-value store used for the environment configuration profile. The only DynamoDB record in the config repository is dynamodb/{env}/data.json, which holds environment-specific settings: service URLs, queue names, database endpoints, credentials, and similar.
Emitter — in computationConfig, the source element (within a repeatable section) that publishes its value when it changes.
Environment config — JSON files in dynamodb/{env}/ that control environment-specific settings: feature flags, credentials, external service URLs.
Exemption — an ad hoc override to a bordereau validation rule. Follows a governance lifecycle: PENDING → APPROVED / DECLINED → REMOVED.
Handlebars — the templating engine used to render HTML document templates. Placeholders like {{risk.inceptionDate}} are replaced with risk data at render time.
homePartyId — the insurer's party identifier in be_config.json. Must match the partyId in the trading party file. Mandatory — Workbench will not start without it.
Initial pipeline — a pipeline triggered when a risk action first becomes available (not when completed). Used to pre-populate data.
JDWP — Java Debug Wire Protocol. The mechanism for remote debugging of Docker-hosted services from IntelliJ IDE.
LOB — Line of Business. Synonymous with Business Class.
LOI (Limit of Indemnity) — the maximum amount the insurer will pay under a policy. Configured in business-constants/limit_of_indemnity.json.
Master — a DUA framework contract risk (binding authority, lineslip). Uses MASTER placing type. Contains the contract terms and sections.
MTA — Mid-Term Adjustment. An amendment to an in-force risk. Creates a new version linked to the original.
Operation — one of the buttons within a risk action pop-up. A single action may have multiple operations.
Partial template — a reusable HTML snippet stored in document-template/files/common/ and referenced in full templates via {{>partialName}}.
Pipeline — a sequence of REST endpoint calls triggered at a specific point in the risk action lifecycle.
Placing type — the type of insurance transaction. The full set of values in the PlacingType enum is: BROKER_OPEN_MARKET, FAC_RI, DEC, CLAIM, OPEN_MARKET, MASTER, COVERHOLDER, CERTIFICATE, SKELETON, EMAIL, CLAIM_CERTIFICATE.
Risk — the central record in Workbench. Represents one insurance submission or transaction.
Risk action — a discrete step in the underwriting workflow (e.g. appetite check, structured quote, document creation).
Risk processing status — the high-level status of a risk. The RiskProcessingStatus enum values are: PRE_SUBMISSION, LOGGED, WORK_IN_PROGRESS, QUOTE, QUOTED, BOUND, BOUND_NOT_BOOKED, COMPLETE.
Risk value — a custom field value stored in the risk_value table. Read/written via RiskValueService.
Rules engine — a separate service that validates risks against configured rule groups. Produces ERROR (blocking) or WARNING (informational) results.
Screen meta data — JSON files defining the layout and fields of custom risk action pop-ups. Two-file pattern: config file + layout file.
PDE (Personal Development Environment) — the local development environment. Runs all Workbench services as Docker containers and mocks AWS services. Configured locally via pde.dev.json.
Smart Submissions (Send Flow) — a module that monitors a shared email mailbox, extracts submission data using AI/OCR, and pre-populates the risk form.
Sub-placing type — a further refinement of a placing type (e.g. FACILITY, SCHEME, INBOUND_BORDEREAU, INDIVIDUAL_DEC).
Sub-status — a more granular status applied to a risk action instance, beyond the top-level action status.
Subscriber — in computationConfig, the target element that receives emitted values and applies a transformation to compute a result.
Trading party — the insurer organisation definition. Mandatory for Workbench to start.
UMR — Unique Market Reference. The identifier for a risk in the Lloyd's market.
ui_config.json — the master frontend configuration file. Sits in applicationconfig/ alongside be_config.json — it is business config (not environment config). Controls UI feature flags, auto-logout, clause library, and exemptions. Deployed via the Send Partner Portal on request.
WebSocket — the mechanism by which backend data changes are pushed to the front end in real time. Inject WebSocketService and publish events after backend updates to keep the UI current.