Scheduled items
Scheduled items are the individual rows
of a schedule, one row per item to be captured by the schedule. The data
captured for each scheduled item is defined in columns that appear in
the schedule user interface. The Scheduled Items portion of the data
model defines the ScheduledItem
delegate that describes the columns of the schedule that are not related
to coverage terms.
When viewed in the user interface, some columns will come from the scheduled item definition. Other columns will come from the coverage terms on the scheduled item coverage, if the schedule item has an associated coverage. For schedules with coverages, the coverage terms created on the associated coverage define the columns.
In the
illustration above, XX is
an abbreviation for the policy line. Coverable
is a placeholder for the name of the coverable. Replace Cov with the clause type: Cov for coverage, Cond for condition, and Excl for exclusion.
All generic schedules include:
XXCoverableScheduleCovItem– A scheduled item to be defined.
Generic schedules with coverage terms include:
XXCoverableScheduleCovItemCov– Coverage associated with a scheduled item. Available only on a scheduled coverage item.CoverageTerm– One or more coverage terms. Examples are limits and deductibles.
Scheduled items are the individual rows of a schedule,
one row per item to be captured by the schedule. The data captured for
each scheduled item is defined in columns that appear in the schedule
user interface. The Scheduled Items portion of the data model defines
the ScheduledItem delegate,
which defines the following set of column types that are common to most
schedules:
Column |
Description |
|---|---|
|
Column of type |
|
Instances of a |
|
Column of type |
|
Column of type |
|
Two instances of a
|
|
Column of type |
|
Two instances of a
|
|
Foreign key to a policy named insured. |
|
Foreign key to a policy location. |
If any schedules within a coverage, condition,
or exclusion requires other column types, you can extend the scheduled
item delegate that defines those column types or create your own delegate.
To see an example of column type definitions, in Studio navigate to
and open ScheduledItem.eti.
This example shows how to define a PolicyLocation
foreign key that can be used as a column in a schedule.
For each coverage, condition, or exclusion in which you want to define one or more schedules, you must define new entities that implement the patterns in the delegates. To see an example of implementing the delegates for homeowners, in the Studio Project window, navigate to and open HOPLineScheduleCovItem.eti.
See also
