Overview of LOB-specific business contexts

In PolicyCenter, some business contexts function differently based on the policy's line of business. One example of this is the context of creating a submission. Testing a personal auto submission has different requirements than testing a workers' compensation submission.

When a business context varies based on the lines of business:

• Some testing logic may be needed for all lines of business and is identical across all lines of business.
  • For example, creating an activity for a personal auto policy is identical to creating an activity for a workers' compensation policy.
• Some testing logic may be needed for all lines of business, but is different for each line of business.
  • For example, both personal auto and workers' compensation have costs. But, the logic to determine if a cost exists is different for each line of business.
• Some testing logic may be needed for only one line of business. For example:
  • Personal auto submissions require the ability to add a vehicle.
  • Workers' compensation submissions require the ability to add covered employees

When a business context has testing requirements that vary based on the line of business, they are referred to as LOB-specific business contexts. Behavior Testing Framework supports them using the LOB/Job Context API.

In the base configuration, the LOB/Job Context API provides support for two lines of business (personal auto and workers' compensation) and all of the jobs common to underwriting (submission, issuance, policy change, cancellation, reinstatement, rewrite, renewal, and audit). Testing requirements vary with each insurer, and therefore the LOB/Job Context API does not provide support for all possible combinations of these lines of business and jobs. Rather, the intention of the base configuration is to provide a wide breadth of examples. Based on these examples, insurers can extend the LOB/Job Context API to suit their specific needs.