Comparing window mode edits to slice edits

If you directly edit an entity instance in window mode, the changes affect the full effective period only of that one entity instance.

In contrast, a slice mode edit using the default split-on-edit approach, in which changes affect the entity instance from the edit date forward. Unlike slice editing, window mode changes do not merge changes forward when the object is edited in window mode. For example, when an out-of-sequence policy change is merged forward, the window mode edits do not merge forward in effective time. For more information about out-of-sequence changes, see Out-of-sequence jobs.

For example, Workers’ Compensation line of business includes Workers’ Compensation payroll amounts that do not change across effective time. A change to these amounts applies to the entire contractual period. People need to provide the amount of payroll that they had for a class of workers within a couple of separate date ranges. They need to edit these numbers directly, not partway through the period. They need to see all date ranges at once, not just the ones effective as of a given date. It would make no sense to merge a change made to the first date range forward to a later one. You must edit each one separately.

Also note that editing in window mode disables automatic scaling and splitting behaviors that would normally happen in slice mode.

Other objects that PolicyCenter edits in window mode include RatingPeriodStartDates and WCCoveredEmployees.