Rendering common coverages

As PolicyCenter renders a page containing the common coverages, it does the following:

Determines which card or cards to render on the page. For example, for BOPScreen, PolicyCenter renders (among others) a detail view card named BOPLinePropertyDV.
Within each included card, PolicyCenter iterates across the coverage categories that are selected or available. For example, for BOPLinePropertyDV, PolicyCenter uses an input iterator with the following ID:
```
id = BOPPropertyRequiredCatIterator
```
This iterator has the following initialValue that determines whether to include a coverage:
```
bopPropertyRequiredCat.coveragePatternsForEntity(BusinessOwnersLine)
        .whereSelectedOrAvailable(bopLine, CurrentLocation.InEditMode)
```
Within the coverage category iterator, PolicyCenter uses an InputSetRef to render the resulting coverages in PolicyCenter. For example, BOPPropertyRequiredCatIterator contains an InputSetRef with the iterator CoverageInputSet() that iterates across each resulting coverage category and renders its coverages on the page.

You define this behavior in Studio in BOPLinePropertyDV.pcf. In the Variables tab of the Properties for the BOPLinePropertyDV.pcf, the bopPropertyRequiredCatCovCoveragePatterns variable selects the coverages to include in the initialValue.

As PolicyCenter builds the interface, in BOPLinePropertyDV it passes the categories for the common categories in the coveragePattern parameter to CoverageInputSet().

PolicyCenter renders a coverage on the screen only if you set the Exists bit on the Coverable. The allowToggle setting in the CoverageInputSet.BOPBuildingCov PCF file governs this bit. On the Input Group, the allowToggle property sets whether the coverage pattern exists on this particular LOB. If you select a coverage (check the check box), then this value toggles on.