YesNoFlag¶
YesNoFlag gives the library a small enum for address-related fields that are stored as yes/no indicators rather than as Boolean properties. In clsPolicyAddress, this kind of flag is used where the address projection carries binary business facts such as the officer-of-notice indicator.*
Purpose¶
- Represent two-state address indicators in the policy-address projection.
- Preserve the source system's explicit yes/no coding model instead of collapsing those fields directly to Boolean values.*
- Provide a readable type for address fields whose values are interpreted as binary business flags.
Context¶
- Namespace:
SAIF.Business.View.Policy - Assembly/package:
SAIF.Business.View.Policy(embedded)
Public members¶
| Member | Signature | Purpose |
|---|---|---|
| Yes* | Yes |
Indicates that the associated address-level condition or flag is present or affirmed. |
| No* | No |
Indicates that the associated address-level condition or flag is absent or not affirmed. |
Behavioral notes¶
- The analysis identifies this enum as a yes/no indicator declared in
clsPolicyAddress.vb. - Officer-of-notice retrieval is one address-related scenario where this binary semantics appears in the library's address workflow.*
- The exact underlying numeric values were not provided in the analysis, but the two-state meaning is clear from the enum's declared purpose.*
Constraints and usage notes¶
- Treat the member names above as inferred semantic labels unless source inspection is needed for exact declaration details.*
- Use the enum where the address model preserves legacy yes/no coding rather than assuming all binary fields are plain Booleans.*
Note: Statements marked with * were inferred from code structure, naming conventions, or contextual evidence where direct confirmation was not available in source artifacts. Statements marked with ** could not be confirmed; treat as unknown until verified.
Sources¶
SAIF.Business.View.Policy/clsPolicyAddress.vb