Steps 1 to 3 are per policy type, and a policy type belongs to one lines effective date.
- Every policy type in scope needs its own item and its own rule.
- Every new lines effective date needs the item added to it as it is published.
Put the second on your release checklist. Nothing errors when it is missed — renewals landing on the new effective date simply go quiet. It is the most likely way for this to stop working a year from now.
Behaviors worth knowing
Timing takes care of itself. The notice is stamped with the commit date, and on a normally-timed renewal the declaration carries the same date, so the two join the same print run with no intervention.
The figures settle on the first rating pass. An item already carrying a premium is not re-rated. In normal processing this is not a problem — creating a renewal does not rate it, and a revision cannot commit while Persistent Builder is unresolved — so by the time anything commits, the figures are correct.
The rule only looks forward. It fires when a renewal is committed, and only then.
Render the template once against a real policy before going live, and read the rendered page rather than copying text out of it. These notices often use a custom font that defeats text extraction, so extracted text can look wrong when the page is fine.
