Resolve a contact's type and carbon-copy name¶
Translate policy-document contacts into service recipient codes and CC display text.
| Field | Value |
|---|---|
| Operation ID | OP-008 |
| Trigger | A caller or serializer reads ContactType, CCName, or IsValidContactType on the contact model. |
| Inputs | Contact state or a caller-supplied contact-type code. |
| Outputs | Recipient code validation or formatted CC text. |
| Primary components | Contact, PolicyHolderContact, AgentContact, ThirdPartyContact |
| Entry point | Business\SAIF.Business.Policy.Audit.ApiCalls\PolicyDocumentConfig.cs |
Steps¶
- Resolve recipient types through the
ValidContactTypesdictionary so policy holders map toPH, agents toAG, and third parties to3P(BR-AAC-019). - Validate caller-supplied contact-type codes by checking whether the provided value appears in
ValidContactTypes.Values(BR-AAC-020). - Format carbon-copy names according to contact role: empty for policy holders, formatted name or
name, agencyfor agents, and formatted name for third parties (BR-AAC-021).
Process flow¶
The following diagram visualizes this operation's control flow.
flowchart TD
Start([Read contact metadata]) --> Role[Resolve contact role]
Role --> Validate[Check valid code when requested]
Validate --> Name[Build CC display text]
Name --> Done([Return metadata])
Failure and edge-case behavior¶
- Unknown codes fail validation instead of being normalized.
- Agent CC formatting depends on whether
AgencyNameis empty.
Related documentation¶
Sources¶
Business\SAIF.Business.Policy.Audit.ApiCalls\PolicyDocumentConfig.cs