Blocking points

Blocking points represent points in the job at which an issue can block progress of the job.

The blocking point values, listed in priority order from lowest to highest, are:

Value	Code	Description
Non-Blocking	`NonBlocking`	Sometimes referred to as informational issues. These issues do not block progress unless specifically rejected by a user.
Blocks Issuance	`BlocksIssuance`	Prevents issuance for submission policy transactions. Prevents binding for policy transactions that do not have a separate issuance step.
Blocks Bind	`BlocksBind`	The issue blocks binding the policy.
Blocks Quote Release	`BlocksQuoteRelease`	Allows quoting to be performed, but unauthorized users cannot view the quote until an underwriter has the opportunity to review and approve it. The job cannot progress further.
Blocks Rate Release	`BlocksRateRelease`	Block releasing a policy period rate. If two-step quoting is enabled in the policy line, this prevents the user from accessing the Quote screen. For example, although the policy is rated, you may not want the user to access the Quote screen until the policy has underwriting approval. In one-step quoting, this blocking point blocks quote release. The `BlocksRateRelease` blocking point is treated slightly differently from other blocking points. At the `BlocksRateRelease` blocking point, PolicyCenter only checks the `PreRateRelease` checking set, and does not check the `All` checking set. This is done for performance reasons, to make the first step of two step quoting execute quickly. If necessary, you can modify this behavior by making a change in the JobProcessUWIssueEvaluator class.
Blocks Quote	`BlocksQuote`	Prevents quoting and steps leading up to quoting. Use for issues that require intervention before the rating engine is called. You can use this blocking point for other types of issues, as well. However, if a policy transaction has a Blocks Quote issue, PolicyCenter will not call the rating engine, and the policy transactions remains in draft state. This blocking point also blocks rating, which is the first step in two-step quoting. Do not use for issues that need information from a valid quote. For example, do not use for issues related to total premium.
Rejected	`Rejected`	The most restrictive value. Rejects the issue. A rejected issue prevents the policy transaction from crossing any blocking point.

The blocking point corresponds to the UWIssueType.BlockingPoint property.

Blocking points are defined in the UWIssueBlockingPoint typelist. This typelist represents the places at which an issue can block. The priority of the typecode orders the blocking point, with larger numbers indicating a more restrictive blocking point. The blocking point of an issue is based on the combination of the blocking point and approval, if present.

The job process classes evaluate whether to raise underwriting issues and check for blocking issues in the evaluateAndCheckForBlockingUWIssues method. For example, the job process calls this method before binding a policy change. Before binding, the PolicyChangeProcess evaluates the all, pre-bind, and pre-issuance checking sets and then checks to see if any issues block issuance. PolicyCenter determines the current point at which an issue blocks both by its type and any associated approval or rejection. Thus, the issue blocks operation if the priority of the current point is greater than or equal to the priority of the operation. Therefore, a rejected issue blocks everything, a non-blocking issue blocks nothing. An issue that blocks bind also blocks issuance but does not block quoting.