Action Groups¶
Action groups are visual groupings that organise risk actions into sections on the risk record view. Two standard groups are required for document generation: rate and broker_response.
What action groups do¶
Without action groups, all risk actions appear in a single flat list. Action groups allow you to group related actions under a labelled heading — for example, grouping the quoting and document creation actions under a "Rate" section, and the broker response actions under a "Broker Response" section.
Defining action groups¶
Action groups are defined in business-constants/action_group.json:
[
{ "typeCode": "action_group", "itemCode": "rate", "value": "Rate" },
{ "typeCode": "action_group", "itemCode": "broker_response", "value": "Broker Response" },
{ "typeCode": "action_group", "itemCode": "bind", "value": "Bind" }
]
| Field | Description |
|---|---|
typeCode |
Always action_group |
itemCode |
The group code referenced in action files |
value |
The display label shown to users |
Important
Action groups must be defined in business-constants/action_group.json before they can be referenced in action files. If an action references a group code that does not exist in this file, the action may not display correctly.
Referencing groups in action files¶
In the risk action config, reference the group using actionGroupCode:
Standard groups for document generation¶
Document generation requires at minimum four actions across two groups:
| Group | Actions required |
|---|---|
rate |
structured_quote, document_creation |
broker_response |
structured_broker_response, br_document_creation |
This follows Approach B (the recommended two-action approach). The rate group covers the quote-side document generation, and broker_response covers the broker response document.
Custom action groups¶
You can define additional action groups beyond rate and broker_response. Common examples:
bind— for binding and post-bind actionsclaims— for claims-related actions on a riskcompliance— for sanctions, compliance, and regulatory steps
Simply add the group to action_group.json and reference it with actionGroupCode in the relevant action definitions.
Display order¶
Action groups and the actions within them are displayed in the order they are defined in the actions config file. To reorder groups or actions, change the order of the entries in the JSON array.