Setting Up the Authenticated Broker Portal

Introduction

After installing the Authenticated Broker Portal, you need to set it up before using it with your Connected Underwriting P&C 1.5 application. This guide walks you through the required incorporation steps, which include:

• Enable group management.
• Enable messaging.
• Configure broker-based record security.
• Add Broker Portal-specific actions.
• Enable the Broker Portal-specific summary interfaces.
• Show Record actions.
• Show Record views.
• Configure the internal and external user selection.

Step 1: Enable group management

Before you can start using the Authenticated Broker Portal with your Connected Underwriting P&C solution, you'll need to enable the Brokers groups to be managed from the Connected Underwriting Settings Set.

This section walks you through how to:

• Enable ISU Brokers group management.
• Enable Broker Portal group management.

Enable ISU Brokers group management

Append the ISU_BKP_GRP_BROKERS group constant to the array in the ISU_CONS_ROLE_GROUPS expression rule. This allows users to edit the group membership of the ISU Brokers Group from the front end.

Enable Broker Portal group management

1. Open the ISU_userSecurityWrapper interface.

2. Update the local variable local!tabs with the ISU_BKP_userSecurityTabMapBrokerGroups expression rule as shown.

   

3. Update the interface again with the ISU_BKP_groupsListBrokerGroups interface as shown.

   

4. Open the ISU_Record_DynamicContext record and add a new action for Link Users. Configure this action as shown below:

   

5. From the Icon dropdown menu, select +, then choose the icon size under Dialog Box Size.

   

6. Set the security of the Link Users action to the ISU_actionVisibilityUnderwritingSettings rule.

7. Navigate to the ISU_BKP_groupsListBrokerGroups interface and add the Link Users action as a recordActionItem as shown below:

   

Step 2: Enable messaging

Next, you will net to set up messaging in the Broker Portal to allow brokers to communicate with insurers and your internal teams.

This section walks you through how to:

• Check group membership when filtering message recipient queries.
• Add the search custom placeholder to the message recipient record.
• Set the Broker group as the thread recipient when applicable.

Check group membership when filtering message recipient queries

1. Open the ISU_returnUserGroupsForMessagingRecipientFilter expression rule.

2. Append an item to the within touniformstring() array by calling the ISU_BKP_returnUserGroupsForMessagingRecipientFilter expression rule, and pass in ri!user for the user input to this rule:

   

Add the search custom placeholder to the message recipient record

1. Open the ISU_Record_MSG_MessageRecipient record type.
2. Navigate to the Filters tab.
3. Check the Use Custom Placeholder checkbox.

4. Use existing translation set strings to set the expression of the custom placeholder as shown:

   

Set the Broker group as the thread recipient when applicable

1. Open the ISU_generateSubmissionThreadRecipients expression rule.

2. Replace rule!SU_returnBrokerThreadRecipientForSubmission with rule!ISU_BKP_returnBrokerThreadRecipient in the local!brokerEmail local variable as shown:

   

Step 3: Configure broker-based record security

This section walks you through the steps for configuring record security based on broker groups, including how to:

• Add the Broker-BrokerGroupMap record relationship.
• Update the record-level security on the Broker record.
• Update the record-level security on the Broker Custom Map record.
• Update the record-level security on the Customer Record.
• Update the record-level security on the Submission record.
• Update the record-level security on the Submission Note record.

Add the Broker-BrokerGroupMap record relationship

1. Open the ISU_Record_Broker record type.
2. Add a new 1:M record relationship called isuBkpRecordBrokerGroupMap to the ISU_BKP_Record_BrokerGroupMap record type. Both records should have the brokerId field in common.between both records.

3. Set the Write and Delete Related Records portion as Do not write or delete as shown:

   

Update the record-level security on the Broker record

1. Open the ISU_Record_Broker record type.
2. Navigate to the Record-Level Security tab.

3. Add a new security rule that allows users found in the ISU Internal Users group to view all records:

   

4. Add another security rule that allows users in the isuBkpRecordBrokerGroupMap.groupId field to view these records:

   

Update the record-level security on the Broker Customer Map record

1. Open the ISU_Record_BrokerCustomerMap record type.
2. Navigate to the Record-Level Security tab.

3. Add a new security rule that allows users found in the ISU Internal Users group to view all records:

   

4. Add a new security rule that allows users to see ISU_Record_BrokerCustomerMaps if they can see the related records from the broker relationship:

   

Update the record-level security on the Customer record

1. Open the ISU_Record_Customer record type.
2. Navigate to the Record-Level Security tab.

3. Add a new security rule that allows users found in the ISU Internal Users group to view all records:

   

4. Add a new security rule that allows users to see Customers if they can see at least one of the related records from the isuRecordBrokerCustomerMap relationship:

   

Update the record-level security on the Submission

1. Open the ISU_Record_Submission record type.
2. Navigate to the Record-Level Security tab.

3. Add a new security rule that allows users found in the ISU Internal Users group to view all records:

   

4. Add a new security rule that allows users to see ISU_Record_Submission if they can see the related records from the Broker relationship:

   

Update the record-level security on the Submission Note

1. Open the ISU_Record_SubmissionNote record type.
2. Navigate to the Record-Level Security tab.

3. Add a new security rule that allows users found in the ISU Internal Users group to view all records:

   

4. Add a new security rule that allows users to see ISU_Record_SubmissionNote if they created the note:

   

Step 4: Add Broker Portal-specific actions

Follow the steps in this section to add specific actions that you want to allow brokers to perform in the portal, including how to:

• Add the Broker Create Submission action.
• Add the Broker Portal Cancel Submission related action.
• Add the Broker Portal Upload Documents action to the Submission record.
• Replace the Validate Duplicate Customer Name and Duplicate Customer POC Email rules.
• Add the Broker Portal Create Customer action to the Customer record.

Add the Broker Create Submission action

1. Open the ISU_Record_Submission record type.
2. Click Actions.
3. Add a new List Action using the Create Submission Translation Key in ISU_BKP_Translations.

4. Configure the action as shown:

   

5. From the Icon dropdown menu, select +, then choose the icon size under Dialog Box Size.

6. Navigate to the Views and Actions Security page.
7. Locate the Create Submission action security and click the Edit icon.

8. Configure the record action’s security using the following expression:

   

9. Open the ISU_BKP_BrokerHomeSitePage interface.

10. In the Billboard section, add this action to the Create Submission card:

    

11. Open the ISU_BKP_MySubmissionsSitePage interface.

12. Add this action as an item in the headerRecordListActions input of the siteTabPageLayout rule as shown:

    

Add the Broker Portal Cancel Submission related action

1. Open the ISU_Record_Submission record type.
2. Navigate to the Actions tab.
3. Add a new record action for Cancel Submission.

4. Configure the record action as shown:

   

5. From the Icon dropdown menu, select x and select Large for the Dialog Box Size.

6. Navigate to the Views and Actions Security page.
7. Scroll down to the Broker Portal Cancel Submission action security and click the Edit icon.

8. Configure the record action’s security as shown:

   

9. Navigate to the Views page.
10. Click the Edit icon next to the Summary view.

11. Under the Related Actions Shortcuts list, select the Cancel Submission related action created in step 3 as shown:

    

12. Save the record type.

Add the Broker Portal Upload Documents action to the Submission record

1. Open the ISU_Record_Submission record type.
2. Navigate to the Actions tab.
3. Add a new record action for Upload Documents. This action will be used on the Broker Portal site.

4. Configure the record action as shown:

   

5. From the Icon dropdown menu, select , then choose the icon size under Dialog Box Size.

   

   • Note: You can also copy the expression for setting the process model context of the related action:

     1
     2
     3
     4
     5
     6
     7
     8
     9
     {
     creationPathId: cons!ISU_BKP_REFID_CREATION_PATH_BROKER_PORTAL,
     submission: rule!ISU_QR_getSubmissions(
     submissionId: rv!identifier,
     returnType: cons!ISU_CO_ENUM_QE_RETURN_TYPE_SINGLE_OBJECT
     ),
     submissionDocs: null,
     userAction: null
     }
     

6. Navigate to the Views and Actions Security page.
7. Locate the Broker Portal Upload Documents action security and click the Edit icon.

8. Configure the record action’s security as shown:

   

9. Save changes to the record type.
10. Open the ISU_BKP_SubmissionSummarySubmissionDocuments interface object.

11. Add the action you created in step 7 as a recordActionField as shown:

    

Replace the Validate Duplicate Customer Name and Duplicate Customer POC email rules

1. Find and replace dependents of the ISU_validateDuplicateCustomerName expression rule with ISU_BKP_validateDuplicateCustomerName. This includes the following objects:

   • ISU_submissionCustomerInformation
   • ISU_editCustomerGeneralInformation

2. Find and replace dependents of the ISU_validateDuplicateCustomerPOCEmail expression rule with ISU_BKP_validateDuplicatePOCEmail. This includes the following objects:

   • ISU_submissionCustomerInformation
   • ISU_editCustomerPointOfContactInformation

   Note: This will ensure that all customers, not just those the user has access to, are searched when conducting these validations.

Add the Broker Portal Create Customer action to Customer record

1. Open the ISU_Record_Customer record type.
2. Navigate to the Actions tab.
3. Add a new list record action for Create Customer. This action will be used on the Broker Portal site.

4. Configure the record action as shown:

   

   

5. Navigate to the Views and Actions Security page.
6. Locate the Broker Portal Create Customer action security and click the Edit icon.

7. Configure the record action’s security as shown:

   

8. Save changes to the record type.
9. Open the ISU_BKP_CustomerSitePage interface object.

10. Add the Create Customer record action created in step 3 under the headerRecordListActions key of the ISU_siteTabPageLayout rule as shown:

    

Step 5: Enable Broker Portal-specific summary interfaces

Follow the steps in this section to enable the summary interfaces that you want to allow brokers to view, including how to:

• Add the Broker Portal Summary page to the Submission Summary record view.
• Add the Broker Portal Summary page to the Customer Summary record view.

Add the Broker Portal Summary page to the Submission Summary record view

1. Open the ISU_Record_Submission record type.
2. Click Views.
3. Click the Edit icon next to the Summary record view.

4. Modify the Interface section of the Summary view to match the expression shown:

   

5. Save changes to the record type.

Add the Broker Portal Summary page to the Customer Summary record view

1. Open the ISU_Record_Customer record type.
2. Click Views.
3. Click the Edit icon next to the Summary record view.

4. Modify the Interface section of the Summary view to match the expression shown:

   

Step 6: Show record actions

Follow the steps in this section to enable specific record actions to show in the broker portal, including how to:

• Show the Resolve Task action.
• Show the Add Note Action.
• Show the Delete Note action.
• Show the Edit Note Aaction.
• Show the Compose Message on Submission action.
• Show the Compose Message action.
• Show the Reply to Thread action.
• Show the Mark Thread as Read action.
• Show the Preview Message Attachment action.

Show the Resolve Task action

1. Open the ISU_actionVisibilityResolveTask expression rule.

2. Within the or() statement that wraps this rule, add another and() condition that checks that the logged-in user is a member of the Brokers group, the task status is Open, and the task is assigned to the logged in user:

   

Show the Add Note action

1. Open the ISU_actionVisiblityAddNotes expression rule.

2. Within the or() statement that wraps this rule, add another and() condition that checks that the logged in user is a member of the Brokers group and that editing the Submission Note is allowed by status:

   

Show the Delete Note action

1. Open the ISU_actionVisibilityDeleteNotes expression rule.

2. Within the or() statement that wraps this rule, add another and() condition that checks that the logged in user is a member of the Brokers group, that editing the Submission Note is allowed by status, and that the logged in user created the note:

   

Show the Edit Note action

1. Open the ISU_actionVisibilityEditNotes expression rule.

2. Within the or() statement that wraps this rule, add another and() condition that checks that the logged in user is a member of the Brokers group, that editing the Submission Note is allowed by status, and that the logged in user created the note:

   

Show the Compose Message on Submission action

1. Open the ISU_MSG_actionVisiblitySubmissionComposeNewMessage expression rule.

2. Within the or() statement that wraps this rule, add another and() condition that checks that the logged in user is a member of the Brokers group using the ISU_BKP_isUserBroker rule and that no threads exist for the Submission:

   

Show the Compose Message action

1. Open the ISU_actionVisibilityComposeMessage expression rule.

2. Within the or() statement that wraps this rule, add another and() condition that checks that the logged in user is a member of the Brokers group using the ISU_BKP_isUserBroker rule:

   

Show the Reply to Thread action

1. Open the ISU_actionVisibilityForReplyThread expression rule.

2. Within the or() statement that wraps this rule, add another and() condition that checks that the logged in user is a member of the Brokers group using the ISU_BKP_isUserBroker rule and that a submission edit is allowed for the inputted submission’s status:

   

Show the Mark Thread as Read action

1. Open the ISU_actionVisibilityMarkThreadAsRead expression rule.

2. Within the or() statement that wraps this rule, add another and() condition that checks that the logged in user is a member of the Brokers group using the ISU_BKP_isUserBroker rule and that the user has not already read the thread:

   

Show the Preview Message Attachment action

1. Open the ISU_actionVisibilityPreviewMessageAttachment expression rule.

2. Within the or() statement that wraps this rule, add another and() condition that checks that the logged in user is a member of the Brokers group using the ISU_BKP_isUserBroker rule and that the attachment extension can be previewed by copying the existing code already contained in this rule:

   

Step 7: Show Record views

Follow the steps in this section to enable visibility on the review views you want brokers to view, including how to:

• Show the Submission Risk Details record view.
• Show the Submission Messages record view.

Show the Submission Risk Details record view

1. Open the ISU_recordViewVisibilitySubmissionRiskDetails expression rule.

2. Add a statement to the or() logical statement to check whether the logged in user is a member of the ISU Brokers group as shown:

   

Show the Submission Messages record view

1. Open the ISU_recordViewVisibilitySubmissionMessages expression rule.

2. Add a statement to the or() logical statement to check whether the logged in user is a member of the ISU Brokers group as shown:

   

Step 8: Configure internal and external user selection

Finally, you will need to configure the open tasking assignment for internal and external users.

To open tasking assignment to brokers:

1. Open the ISU_createTaskGeneric interface.

2. Remove the existing Assignee field by deleting the block of code shown:

   

3. In place of the Assignee field you removed, call ISU_BKP_taskAssigneeField and pass in local!task for the task input as shown:

   

4. Open the ISU_reassignTask interface.

5. Remove the existing Assignee field by deleting the block of code shown:

   

6. In place of the Assignee field you removed, call ISU_BKP_taskAssigneeField and pass in ri!task for the task input, as shown:

   

Feedback