Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Integration with Pega Underwriting for Insurance

Updated on December 22, 2021

Pega Sales Automation for Insurance provides an interface into Pega Underwriting for Insurance to create new submission cases.

Pega Sales Automation Implementation Guide Pega Sales Automation Implementation Guide Pega Sales Automation Implementation Guide Pega Sales Automation Implementation Guide Pega Sales Automation Implementation Guide Pega Sales Automation Implementation Guide Pega Sales Automation Implementation Guide Pega Sales Automation Implementation Guide Pega Sales Automation Implementation Guide Pega Sales Automation Implementation Guide Pega Sales Automation Implementation Guide Pega Sales Automation Implementation Guide Pega Sales Automation Implementation Guide Pega Sales Automation Implementation Guide

Pega Sales Automation for Insurance and Pega Underwriting for Insurancehave been designed to communicate by using Federated Case Management. One feature of Federated Case Management provides an Internet Application Composer (IAC) interface that allows one application to work directly with the second application.

Pega Underwriting for Insurance has enhanced the following lines of business flows to provide limited access for Federated Case Management operators:

  • Commercial - Auto
  • Commercial - General Liability
  • Commercial - Property
  • Commercial - Workers Compensation
  • Personal - Auto
  • Personal - Umbrella

The following sections detail the required steps for the Pega Sales Automation for Insurance to Pega Underwriting for Insurance integration:

  • Configuring Federated Case Management in Pega Sales Automation for Insurance
  • Configuring Pega Underwriting for Insurance
  • Customer data setup
  • Integration services setup
  • Web mashup channel setup

Configuring Federated Case Management

Configure Federated Case Management to support the Pega Sales Automation for Insurance to Pega Underwriting for Insurance integration.

  1. Ensure that Data-Admin-RemoteSystem instances are present for your organization’s lines of business.
    1. In the navigation pane of Dev Studio, click RecordsSysAdminRemote System.
    2. Create or update the following instances with the values that correspond to your environment.
    • PUIPersonalLines
      • Select Connect using mashup
      • System URL – Enter the path, for example: http://{host}:{port}/prweb/IAC
      • Application Name – Specify the PUI implementation layer application name for personal lines, for example: PegaInsurancePAPLVerify
    • PUICommercialLines
      • Select Connect using mashup
      • System URL value – Enter the path, for example: http://{host}:{port}/prweb/IAC
      • Application Name – Specify the PUI implementation layer application name for commercial lines, for example: PegaInsurePACLVerify
  2. Create or update the IP address for the Pega Underwriting for Insurance application in your Pega Sales Automation for Insurance application rule.
    1. In the navigation pane of Dev Studio, click RecordsApplication DefinitionApplication, and then select the appropriate implementation application instance for your organization.
    2. Click the Integration & security tab.
    3. In the Mashup security section, update the following fields:
      • Trusted origin – Enter the path, for example: http://{localhost}:port
      • Note – Enter a text description of the target application, for example: UW Remote App
  3. Ensure that the operators requiring access to Pega Underwriting for Insurance to initiate submissions from Pega Sales Automation for Insurance also exists in the Pega Underwriting for Insurance application. Ensure that these operators also have valid access permissions for processing submissions for the appropriate lines of business in Pega Underwriting for Insurance.
    For example: For example, if the [email protected] operator in Pega Sales Automation for Insurance is needed to create a remote submission case for this Pega Underwriting for Insurance application, this same operator should also exist in the Pega Underwriting for Insurance application. The Pega Underwriting for Insurance operator [email protected] should also have access to the applications that are mentioned in the PUIPersonalLines and PUICommercialLines remote systems.

    In addition, the Pega Sales Automation for Insurance operator that is being used to initiate the remote submission case should have the Pega Underwriting for Insurance application agent ID in the ExternalID property of the operator record.

    For example, if an operator in Pega Sales Automation for Insurance is mapped to AGT-xxx in Pega Underwriting for Insurance, store this AGT-xxx value in the ExternalID property in the Pega Sales Automation for Insurance operator record.

    Note: The ExternalID is stored in the operator record. To see whether an ExternalID exists for an operator, access the D_ExternalOperatorDetails data page and refer to the pxResults property.

Configuring Pega Underwriting for Insurance

Configure Pega Underwriting for Insurance to integrate with Pega Sales Automation for Insurance..

  1. Create or update the IP address for your Pega Sales Automation for Insurance application in your application rule.
    1. In the navigation pane of Dev Studio, click RecordsApplication DefinitionApplication, and then click the Pega Underwriting for Insurance application.
    2. Click the Integration & security tab. In the Mashup security section, update the following fields:
      • Trusted origin – Enter the path, for example: http://{host}:{port}
      • Note – Enter a description of the master application, for example: SAI App
  2. Ensure that the IAC URL pattern servlet mapping is present in web.xml. Update the IAC authentication service API to allow direct authentication for IAC.
    The authentication activity of IACAuthentication service exists in the Pega-RULES and PBISampleData rulesets.
    • For Pega internal implementations, use the PBISampleData version.
    • For customer implementations, create a new version of the activity.
    1. In Dev Studio, open the IACAuthentication activity.
    2. On the Security tab, select the Allow direct invocation from the client or a service check box.
      Note: If the Allow direct invocation from the client or a service check box is cleared, when a remote case is initiated from Pega Sales Automation for Insurance, the login screen displays instead of the case initiation screen.
  3. Review the BROWSER requestor type.
    1. In the navigation pane of Dev Studio, click RecordsSysAdminRequestor Type.
    2. Click the row that corresponds to the Pega Underwriting for Insurance application system name BROWSER requestor type.
      Pega Underwriting for Insurance is usually deployed with a system name of "PUI". For an internal deployment, the appropriate requestor type is "PUI - BROWSER".
    3. Ensure that the access group specified in the Access Group Name field, which is usually PRPC:Unauthenticated, has access to the IACAuthentication activity changed in Step 2.
      To obtain the system name, in Admin Studio, click Nodes running, click the node name, and then refer to the System name field.
  4. Ensure that the operator that is used to initiate a remote case from the Pega Sales Automation for Insurance application also exists in the Pega Underwriting for Insurance application. In addition, ensure that this operator has valid access permissions for processing submissions for the appropriate lines of business in Pega Underwriting for Insurance.
  5. Ensure that the search index is complete and active.
    1. In the header of Dev Studio, click ConfigureSystemSettingsSearch.
    2. Review the status of All data default index is available.

Customer data setup

Set up the customer data to ensure that contact data syncs among the Pega Sales Automation for Insurance, Pega Underwriting for Insurance, and Pega Customer Service for Insurance applications.

Customer sample data is maintained in Pega Foundation for Insurance for both the Pega Customer Service for Insurance and Pega Underwriting for Insurance applications. Pega Underwriting for Insurance is usually deployed independently of Pega Customer Service for Insurance.

Both Pega Underwriting for Insurance and Pega Customer Service for Insurance maintain the Pega Foundation for Insurance data structures, and have similar but separate sample data instances. When deployed, sample data for Pega Underwriting for Insurance and Pega Customer Service for Insurance should remain in sync. This is accomplished by redirecting the Pega Underwriting for Insurance CustomerData schema to the CustomerData schema in the Pega Customer Service for Insurance database.

Configuring CustomerData database rule

Sample data for Pega Customer Relationship Management for Insurance and Pega Underwriting for Insurance is initially identical because both applications deploy common Pega Foundation for Insurance sample data objects. Configuring the CustomerData schema to use a common database eliminates the need to manually synchronize the customer sample data that is used by Pega Customer Service for Insurance and Pega Underwriting for Insurance when Pega Sales Automation for Insurance is also using the same data.

To delete the existing CustomerData database rule and create a CustomerData record for Pega Underwriting for Insurance, complete the following steps:

  1. In the navigation pane of Dev Studio, click RecordsSystem AdminDatabase.
  2. Click the CustomerData record and then click Delete.
  3. Create a database record to direct the CustomerData schema to the Pega Sales Automation for Insurance or Pega Customer Service for Insurance instance. Update the database record fields with the following text:
    • Database: CustomerData
    • Short Description: CustomerData
  4. Click Create and open.
  5. On the Database tab, in the JDBC definition section, update the JBDC URL field by using the following path structure:
    jdbc:postgresql://<ip-address>:<port>/<dbname>?currentSchema=<customer SOR schema name>
    For example: For example, if Pega Sales Automation for Insurance is a Postgres instance, use a CustomerData schema similar to the following example:
    jdbc:postgresql://<ipaddress>:5432/pega?currentSchema=pegadata
  6. In the Authentication section, enter the username and password for the database schema owner.

Updating PUICustomerSystem dynamic system setting

If the Pega Underwriting for Insurance CustomerData schema is pointing to a Pega Customer Service for Insurance instance, update the PUICustomerSystem dynamic system setting in Pega Sales Automation for Insurance. The PUICustomerSystem dynamic system setting holds the Pega Underwriting for Insurance customer system designation.

  1. In the navigation pane of Dev Studio, click RecordsSysAdminDynamic System Settings.
  2. Click PUICustomerSystem.
  3. On the Settings tab, ensure that the entry in the Value field is CS.

Integration services setup

Set up the integration services in Pega Sales Automation for Insurance.

Perform the following procedures:

  • Configuring quote integration
  • Configuring policy integration
  • Configuring quote action integration
  • Configuring business event notifications

Configuring quote integration

Quote integration utilizes an inquiry service that is hosted by Pega Underwriting for Insurance to provide submission and quote status and details.

  1. Review the QuoteIntSource dynamic system setting.
    1. In the navigation pane of Dev Studio, click RecordsSysAdminDynamic System Settings.
    2. Click and open QuoteIntSource.
    3. On the Settings tab, ensure that the Value field is set to true.
  2. If the source system of the quote is a Pega Underwriting for Insurance application, set endpoint URLs.
    1. In the navigation pane of Dev Studio, click RecordsSysAdminApplication Settings.
    2. Click and open QuoteSourceSystemURI.
    3. Update the Value field for the appropriate level to the Pega Underwriting for Insurance service endpoint.
      For example: For example: to invoke the API for Pega Underwriting for Insurance to obtain quote data, enter the following path:
      http://{host}:{port}/prweb/PRRestService/PUI_API/0740/Cases/{LineOfBusiness}/Get

Configuring policy integration

The Pega Underwriting for Insurance application is used as a simulation for a Policy Administration system.

  1. Review the PolicyIntSource dynamic system setting.
    1. In the navigation pane of Dev Studio, click RecordsSysAdminDynamic System Settings.
    2. Click and open PolicyIntSource.
    3. On the Settings tab, ensure that the Value field is set to true.
  2. If the source system of the quote is a Pega Underwriting for Insurance application, set the PUISourceSystemURI endpoint URL for all active production levels.
    1. In the navigation pane of Dev Studio, click RecordsSysAdminApplication Settings.
    2. Click and open PUISourceSystemURI.
    3. Update the Value field for the appropriate level to the Pega Underwriting for Insurance service endpoint.
      For example: For example, to invoke the API for Pega Underwriting for Insurance to obtain policy data, enter the following path:
      http://localhost:port/prweb/PRSOAPServlet/SOAP/GetPolicyDetailsByID/Services

Configuring quote action integration

An operator can take action (Accept, Reject, Renegotiate and Withdraw) on Pega Underwriting for Insurance integrated quote from Pega Sales Automation for Insurance application.

  1. In Pega Sales Automation for Insurance, if the source system of the quote is a Pega Underwriting for Insurance application, set the PUIQUOTEACTIONWSURL endpoint URL for all active production levels.
    1. In the navigation pane of Dev Studio, click RecordsSysAdminApplication Settings.
    2. Click and open PUIQUOTEACTIONWSURL.
    3. Update the Value field for the appropriate level to the Pega Underwriting for Insurance service endpoint.
      For example: For example, to invoke the API for Pega Underwriting for Insurance to take action on quote, enter the following path:
      http://<host>:<port>/prweb/PRRestService/CustomerDecisionforProposal/v1/HandleCustomerApproval
  2. In Pega Underwriter for Insurance, review the CustomerDecisionforProposal service package.
    1. In the navigation pane of Dev Studio, click RecordsIntegration-ResourcesService Package.
    2. Click and open CustomerDecisionforProposal.
    3. Ensure that the record has the appropriate access group for your Pega Underwriter for Insurance implementation application.
    4. Optional: Operator can take action on those quotes from Pega Sales Automation for Insurance application, which is initiated from Pega Sales Automation for Insurance application via Federated Case Management. If you want to change this behavior to take action on all quote then change the IsExternalCase when rule to return true always.

Configuring business event notifications

The business events service is hosted by Pega Sales Automation for Insurance. The service receives business events from any application that is configured to connect to the application.

To set up background business event notifications, complete the following steps:
  1. Review the BusinessEventNotifications service package.
    1. In the navigation pane of Dev Studio, click RecordsIntegration-ResourcesService Package.
    2. Click and open BusinessEventNotifications.
    3. Ensure that the record has the appropriate access group for your Sales Automation for Insurance implementation application.
  2. If the source system is Pega Underwriting for Insurance, ensure that policies and quotes automatically update.
    1. In Admin Studio, click Queue processors.
    2. Ensure that ProcessPolicyEvents and ProcessUWEvents are listed and running.
  3. If the queue processors in step 2 are not listed in Admin Studio, it means that the System Runtime Context does not have queue processors application listed in Applications.
    1. In the header of Dev Studio, click ConfigureSystemGeneralSystem Runtime Context.
    2. Click the Add application.
    3. Add the application that has ProcessPolicyEvents and ProcessUWEvents queue processor defined.
  4. Configure quote action in Pega Underwriter for Insurance. To do this, ensure that the NotifyBusinessEventURL application setting has the appropriate endpoint URL that specifies the Pega Sales Automation for Insurance instance.
    1. In the navigation pane of Dev Studio, click RecordsSysAdminApplication Settings.
    2. Click and open NotifyBusinessEventURL.
    3. Update the Value field for the appropriate level to the Pega Sales Automation for Insurance service endpoint.
      For example: For example, to send business event notification to Pega Sales Automation for Insurance about quote or policy update in Pega Underwriter for Insurance:
      https://<host>:<port>/prweb/PRRestService/{BusinessEventNotifications}/v1/BusinessEventNotificationListener
  5. Ensure that the NotifyBusinessEvent toggle switch is on.
    1. In the header of Dev Studio, click ConfigureSystemReleaseToggles.
    2. Check whether the status of the toggle is set to On. If not, click the pencil icon to edit the status, and then click Enable toggle for all.

Web mashup channel setup

To load the Pega Web Mashup gadget in a secure way, you generate a channel ID and pass it to the request for validation.

The following sections describe how to set up web mashup channel in Pega Underwriter for Insurance and pass this channel id in request from Pega Sales Automation for Insurance application to Pega Underwrite for Insurance to make this as genuine request.

  • Configuring channel to create new case
  • Configuring channel for open case

Configuring channel to create new case

  1. Click Application nameChannel and interfacesWeb mashup.
  2. In the New Web mashup interface, compelte the following fields:
    • Name: Enter name, for example, Create Commercial GL Submission
    • Action: Select Create a new case
    • Case type: Select the case type that you want to create, for example, Start Commercial GL submission
    • Allow passing dynamic parameters: Switch toggle button to true
  3. Click on Generate mashup code button.
    Result: The system displays a pop-up window.
  4. Copy the data-pega-channelID value from Mashup code and keep it for later use in Sales Automation for Insurance.
  5. Click Save.

Configuring channel for open case

  1. Click Application nameChannel and interfacesWeb mashup.
  2. In New Web mashup interface, fill the fields below:
    • Name: Enter name, for example, Open Commercial GL Submission
    • Action: Select Open a case by handle
    • Param key: Provide a unique property of the case, for example, pzInsKey
    • Case type: Select the case type that you want to create, for example, Start Commercial GL submission
    • Allow passing dynamic parameters: Switch toggle button to true
  3. Click the Generate mashup code button.
    Result: The system displays a pop-up window.
  4. Copy the data-pega-channelID value from Mashup code and keep it for later use in Pega Sales Automation for Insurance.
  5. Click Save.
  6. In Pega Sales Automation for Insurance, pass the channel id in request to Pega Underwriter for Insurance:
    1. Search for and open the pySetFCMMashupChannelMeta data transform present in Work- class.
    2. Click Save as and then select Apply to as client class, for example: PegaInsCRM-Work-Submission-Commercial.
    3. Click Create and open.
    4. Set pyChannelIDCreateNewWork property value to the data-pega-channelID value copied in the "Configuring channel to create a new case" procedure.
    5. Set pyChannelIDOpenWorkByHandle property value to the data-pega-channelID value copied in step 4.
  7. Complete Web mashup channel setup for all products that you want to integrate with Pega Underwriter for Insurance.
  • Previous topic Next best action in Pega Sales Automation for Insurance
  • Next topic Deprecated and withdrawn rules and table changes

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us