Note: This release is in preview. Features described here don’t become generally available until the latest general availability date that Salesforce announces for this release. Before then, and where features are noted as beta, pilot, or developer preview, we can’t guarantee general availability within any particular time frame or at all. Make your purchase decisions only on the basis of generally available products and features.
Issue Policy
This diagram outlines the sequence of issuing a policy without using Salesforce quote, rather by using the Rating API to generate a price-adjusted context that's used to issue a policy.
-
(Optional)Run Qualification Rules—If customers want to
determine the policyholder’s eligibility for a product, run the qualification rules either
by:
- Making a POST request on the Insurance Quote Connect API, or
- Using the Create Insurance Quote invocable action.
Set the saveQuote parameter to false. It doesn't save the quote and returns an updated context with the eligibility details. -
Generate Price-adjusted Context—Make a POST request on
the Insurance Product Ratings Connect API.
You must include additionalFields in the request payload with either a QuoteAccount or an Opportunity ID that's linked to an account to generate the context.
-
Issue Policy—Use the price-adjusted context record to
issue a policy either by:
- Making a POST request on the Issue Insurance Policy Connect API, or
- Using the Issue Insurance Policy invocable action.
You can override the context data, such as policy name, policy number, effective-from date, effective-to date, and any other additional fields to provide the values for the custom fields during the API call. You can also specify a name for the transaction record that’s created as part of the policy issuance process. This transaction record is used to track an audit or as a financial marker.This request creates a new policy record.
- A new policy record is created and saved in Salesforce. The policy record includes the details, such as the policy name, number (if provided or created during the API call), policy start date, the coverage you chose, and the price.
- Any custom field values that are provided during the API call are saved to the new policy record.
- A transaction record is created and linked to the policy.
