Pega Sales Automation for Insurance™ provides an interface into Pega Underwriting for Insurance™ to create new submission cases. Pega Sales Automation for Insurance and Pega Underwriting for Insurance have 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:

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

Federated Case Management in Sales Automation for Insurance

To configure Federated Case Management to support the Pega Sales Automation for Insurance to Pega Underwriting for Insurance integration, complete the following steps:

1. Ensure that Data-Admin-RemoteSystem instances are present for your organization’s lines of business.
   1. In the navigation panel of Dev Studio, click Records > SysAdmin > Remote 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 Sales Automation for Insurance application rule.
   1. In the navigation panel of Dev Studio, click Records > Application Definition > Application, and then select the appropriate implementation application instance for your organization.
   2. Click the Integration & security tab. In the 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, 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.

Pega Underwriting for Insurance setup

To configure Pega Underwriting for Insurance for the Pega Sales Automation for Insurance to Pega Underwriting for Insurance integration, complete the following steps:

1. Create or update the IP address for your Pega Sales Automation for Insurance application in your application rule.
   1. In the navigation panel of Dev Studio, click Records > Application Definition > Application, and then click the Pega Underwriting for Insurance application.
   2. Click the Integration & security tab. In the 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 panel of Dev Studio, click Records > SysAdmin > Requestor Type. 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 would be "PUI - BROWSER".

   2. 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 Configure > System > Settings > Search.
   2. Review the status of All data default index is available.

Customer data setup

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.

To ensure that contact data syncs among the Pega Sales Automation for Insurance, Pega Underwriting for Insurance, and Pega Customer Service for Insurance applications, complete the changes that are detailed in the following sections.

• CustomerData database rule
• PUICustomerSystem dynamic system setting

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 panel of Dev Studio, click Records > System Admin > Database.
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, 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.

PUICustomerSystem dynamic system setting

The PUICustomerSystem dynamic system setting holds the Pega Underwriting for Insurance customer system designation.

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.

1. In the navigation panel of Dev Studio, click Records > SysAdmin > Dynamic System Settings.
2. Click PUICustomerSystem. On the Settings tab, ensure that the entry in the Value field is CS.

Integration services setup

The following sections describe how to set up the integration services in Pega Sales Automation for Insurance.

• Quote integration
• Policy integration
• Quote action integration
• Business event notifications

Quote integration

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

To set up quote integration, complete the following steps:

1. Review the QuoteIntSource dynamic system setting.
   1. In the navigation panel of Dev Studio, click Records > SysAdmin > Dynamic System Settings.
   2. Click and open QuoteIntSource. 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 panel of Dev Studio, click Records > SysAdmin > Application 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: 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

Policy integration

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

To set up policy integration, complete the following steps:

1. Review the PolicyIntSource dynamic system setting.
   1. In the navigation panel of Dev Studio, click Records > SysAdmin > Dynamic System Settings.
   2. Click and open PolicyIntSource. 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 panel of Dev Studio, click Records > SysAdmin > Application 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, 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

Quote action integration

An operator can take action (Accept, Reject, Renegotiate and Withdraw) on Pega Underwriting for Insurance integrated quote from Sales Automation for Insurance application. To set up quote action integration, complete the following steps in Sales Automation for Insurance:

1. If the source system of the quote is a Pega Underwriting for Insurance application, set the PUIQUOTEACTIONWSURL endpoint URL for all active production levels.
2. In the navigation panel of Dev Studio, click Records > SysAdmin > Application Settings.
3. Click and open PUIQUOTEACTIONWSURL.
4. Update the Value field for the appropriate level to the Pega Underwriting for Insurance service endpoint.

For example, to invoke the API for Pega Underwriting for Insurance to to take action on quote, enter the following path: http://<host>:<port>/prweb/PRRestService/CustomerDecisionforProposal/v1/HandleCustomerApproval

Then, complete the following steps to set up quote action in Pega Underwriter for Insurance:

1. Review the CustomerDecisionforProposal service package.
2. In the navigation panel of Dev Studio, click Records > Integration-Resources > Service Package.
3. Click and open CustomerDecisionforProposal.
4. Ensure that the record has the appropriate access group for your Pega Underwriter for Insurance implementation application.
5. Optional – Operator can take action on those quotes from Sales Automation for Insurance application, which is initiated from Sales Automation for Insurance application via Federated Case Management. If you want to change this behavior to take action on all quote then change IsExternalCase when rule to return true always.

Business event notifications

The business events service is hosted by 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 panel of Dev Studio, click Records > Integration-Resources > Service 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 Configure > System > General > System Runtime Context.

   2. Click the Add application.

   3. Add the application which have ProcessPolicyEvents and ProcessUWEvents queue processor defined.

Then, complete the following steps to set up quote action in Pega Underwriter for Insurance:

1. Ensure that the NotifyBusinessEventURL application setting has the appropriate endpoint URL that specifies the Pega Sales Automation for Insurance instance.

   1. In the navigation panel of Dev Studio, click Records > SysAdmin > Application 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, 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

2. Ensure that the NotifyBusinessEvent toggle switch is on.

   1. In the header of Dev Studio, click Configure > System > Release > Toggles.

   2. Check status of toggle is on. If not then click on pencil icon to edit and click on Enable toggle for all.