...
- Creating Underwriting Definitions
- Creating Underwriting Approval Dependencies
- ‘Accept’ the RFP Batch the first time
- 'Approve’ or ‘Decline’ Approval Records
- ‘Reprocess’ the Batch
- ‘Accept’ the RFP Batch on subsequent attempts
- ‘Submit’ the Renewal Batch
- ‘Approve’ the Renewal Batch Approval Records
- ‘Decline’ the Renewal Batch
- Changing Contract Types
- Additional Client Master RPF Actions that affect Approvals (Decline, ReActivate)
- Additional Renewal Batch Actions (Kill, Clone)
- Comparison Batches
- Approval State Diagrams
...
RFP Batch, Client Master Contract Type Change
- The Contract Type cannot be changed from the Client Master once the Contract Status = Submitted. The Batch will have to be Reprocessed to facilitate a Contract Type change
- After ‘Reprocess’, all Approvals are set to Status = ‘Reprocess’ [Db]. Those Approvals that applied to the current Contract Type are left IsActive = True
- While in ‘Prospect’ status, after the Contract Type change is saved from the Client Master, the Batch is saved [Pipeline] causing Pricing Batch business logic to execute.
- As described in the ‘Accept’ process, Underwriting Definitions are re-evaluated based on the Contract Type. New Approvals are generated as needed and existing Approvals which match the Contract Type (or have an empty Contract Type) are recycled. The status of all Approvals are reset to ‘Pending’ or ‘Waiting’ (based on dependencies)
- RFP Batch, Pricing Batch Contract Type Change
- The Contract Type on the Pricing Batch is Read-Only for RFP batch types. This will prevent Pricing Batch Contract Type changes from occurring from the Pricing Batch. The deal will have to be ‘Reprocessed’ before the Contract Type can be changed (from the Client Master)
- Renewal Batch
- The Contract Type cannot be changed once the Batch Status = Activated
- While the Batch Status = Underwriting, valid Approvals are in place. If the Contract Type is changed at this point:
- Those Approvals are inactivated and set Status = Reprocess [Db]
- New Underwriting Definitions are retrieved based on the Contract Type and new Approval records are created and existing Approval records which match the Contract Type (or have an empty Contract Type) are recycled
Anchor RPFActions RPFActions
Client Master RPF Actions
...
| Filter by label (Content by label) | ||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
...