AgentOne Release Notes

AgentOne January 2021 Release Notes

UAT Release: January 8, 2021 ~noon ET
Production Release: January 22, 2021  ~10:00pm ET
version 24.x

The contents of the release notes are directed to orgs that are being upgraded directly from the immediate previous release of AgentOne to this new release of AgentOne.  For more details or for complete information for a new implementation, refer to the AgentOne Implementation Guide.

Fixes

iGO Agent e-Signature alerts were displaying cryptic text
​​​​​​Description:

An iGO Alert description shows a cryptic placeholder that should have been replaced with sensible English text as shown in italics. “The e-Signature link is about to expire. Please contact [AgentLinkAboutToExpire](Date: 10/29/2020 18:08:22} to remind him or her that the case is awaiting their signature. ”  Our Alert type rules properly translated the Consumer’s alerts but not the Agent’s alerts, so two new agent eSignature alert descriptions are now supported.

Solution:

AgentOne now supports two new alert types that are for the agents, with display for them.

Check the Sync record and if the Alert Type is Expired Signature || Signature Expiry Warnings and Alertdescription__c contains [AgentLinkAboutToExpire] or [AgentLinkHasExpired]​. Alert Type will be changed to be one of the two new Agent Alert types and it will use the Display text for the matching Agent Alert type in the Alert’s description.​

​​​​​Risk Analysis: Low

Affects which Fea​tures / Functionality:  Alerts

Availability: Automatic

Implementation Steps

None

How To Test

1. Ensure that the new Alert type AGENT_ALERT_SIGNATURE_EXPIRED exists in the org with a Display Text.

​2. Trigger a sync by cloning an INSERT_ALERT where Alert type text = AGENT_ALERT_SIGNATURE_EXPIRED and the alert description contains [AgentLinkHasExpired].

3. Open the Alert record that the sync record created.

4. Confirm that the text is “The agent’s e-Signature link has expired. <agent> will need a new e-signature link.”​ with <agent> as the name of the agent that this alert is for.​​​

Applied for fields were not updating for all forms of submissions supported by iGO
​​​​​​Description:

AgentOne retains the Applied for values for insurance cases that have been submitted to the carrier new business and underwriting processes. This allows future comparison of the applied for values, such as for the face amount at the time of application vs. the current or final face amount after the policy is underwrittend and issued. There are multiple ways for an e-app to be submitted, and the Applied For fields were only updated if the e-app was submitted with status “Application e-Submitted”.

AgentOne did not check if Applied for fields should be updated on the other submit statuses like “ESubmittedWithWetSignatures” and “PrintforWetSignature​”.

Solution:

The solution is to create new syncmapper entries that support four different methods of submitting an iGO e-App, including e-submitted, completed, e-submitted with wet signtaures, and printed for wet signatures. If the org is configured to allow insurance case updates after the application has proceeded past the application phase, the applied for fields are updated with any of these four e-app submissions methods.

​​​​​Risk Analysis: Low

Affects which Fea​tures / Functionality:  IGO Integration

Availability: Automatic

Implementation Steps

If your org contains any custom sync mapper entries for updating the Applied for fields​, you should review them and apply the same fix.

How To Test

1. Ensure ‘AgentOne__IGOAllowInsuranceCaseUpdatePassedApplicationPhase’ Feature Parameter is set to true in the org.

2. For a case in underwriting or delivery status, clone a sync record with either “ESubmittedWithWetSignatures” or”PrintforWetSignature​” submitted status.

3. Confirm the Applied for fields are updated.

 Applied for fields were not updated consistently
​​​​​​Description:

The Applied for fields were not updated consistently via the iGO Sync. They are supposed to be updated if the status is a Submitted status. Some of the fields were being updated if it detected a change in CASESTATUSTEXT and others were being updated if it detected a change in POLICYSTATUS_TC.  iGO sync events sometimes sent back a null for these fields.

Solution:

It was noticed that all sync events sent back a CASESTATUS value, so we modified all of the sync mappers to trigger off of this field instead of an update to the Applied for fields. This was modified for both DD and DD3 mappings​ for the below fields:

  • Applied for Annualized Premium
  • Applied for Carrier Class Table Rating
  • Applied for Carrier Class Name
  • Applied for Coverage Amount
  • Applied for Table Rating
  • Applied for Tobacco Basis
  • Applied for Underwriting Class
  • Applied for Temp Flat Extra Amount
  • Applied for Temp Flat Extra Duration
  • Applied for Perm Flat Extra Amount

​​​​​Risk Analysis: Low

Affects which Fea​tures / Functionality:  IGO Integration

Availability: Automatic

Implementation Steps

If you have any custom sync mapper entries for updating the Applied for fields, you should review them and apply the same fix.

How To Test

1. Submit an igo e-app.

2. Confirm the Applied for fields are updated.

Address checkmarx issues
​​​​​​Description:

Address security vulnerability issues identified by Checkmarx scanner.

Solution:

Modify code to fix security vulnerabilities. If issues are false positives, marked it as such in Checkmarx scanning tool.

​​​​​Risk Analysis: High

Affects which Fea​tures / Functionality: 

  • Start e-App​
  • Start/Open iGO page (Classic Experience)
  • Starting iGO from Opportunity
  • Alerts (iGO & Pending Case) Sync back
  • Insurance Case Sync​
  • Sync Record processing​​
  • Case Requirement Events Sync back​
  • Revise illustration
  • Duplicate Case
  • Case Copy, Transfer
  • Insertion of attachments (Content version) to illustration from sync records
  • Activity Processing(Tasks for iGO events)
  • At a Glance header (Classic Experience)
  • Home page (Classic Experience)
  • Resend Alerts
  • Sync back Custom Relationships​
  • Edit Relationships page
  • Admin app upload file functionality​

Availability: Automatic

Implementation Steps

None

How To Test

Steps R&D followed to test the fix or new feature.​​

Error when importing iGO Prefill Mapping
​​​​​​Description:

When importing iGO Prefill Mapping, there is an error “The field name entered does not exist in the Entity Field List, please make sure the field is registered with AgentOne by adding it to the Entity Field List.​” The import is throwing the error because the referenced field is disabled in the Entity Field List, so the import is disallowing import of it.

Solution:

On import, allow import even if the field is disabled.

​​​​​Risk Analysis: Low

Affects which Fea​tures / Functionality:  Admin import of iGO Prefill Mapping

Availability: Automatic

Implementation Steps

None

How To Test

Import prefill settings with corresponding disabled Entity Field List that previously failed and confirm it imports successfully.

Address locking issues with updating Sync fields on Insurance Case
​​​​​​Description:

The System Sync fields on Insurance Case are sometimes not updated and/or do not accurately reflect the latest sync record that updated the Insurance Case. as intended.

The System Sync fields are:

  • Sync_Fields_Last_Updated__c
  • Sync_Record_Id__c
  • Last_Sync_Request__c
  • Last_Sync_Source__c
  • Last_Sync_Exit_Code__c
  • Last_Sync_Error_Msg__c
  • Last_Sync_Tracking_Id__c

While updating the Sync fields on Insurance Case, if there is an update for the same Insurance Case by the real-time process, there would be a conflict and an exclusive ROW_LOCK issue would result.

Solution:

To resolve the ROW_LOCK issues, we added for update to the SOQL query, which should prevent locking of one record from one process with another. if locking happens, it will wait for 10 seconds to prevent locking and allow the Sync fields to be updated.

​​​​​Risk Analysis: Low

Affects which Fea​tures / Functionality: IGO Integration, Pending Case Feeds

Availability: Automatic

Implementation Steps

None

How To Test

Test organically by having pending case syncs and iGO syncs coming to the AgentOne org simultaneously. Review the insurance case records and confirm that it is pointing to the correct sync records.

Changes to support Salesforce Platform API versions 21.0 to 30.0 retirement in Summer 22
​​​​​​Description:

With the Summer ‘22 release, SOAP, REST, and Bulk API legacy versions 21 through 30 will be retired and no longer supported by Salesforce. When these legacy versions are retired, applications consuming impacted versions of the APIs will experience a disruption as the requests will fail and result in an error indicating that the requested endpoint has been deactivated.​ See the Salesforce Platform API Versions 21.0 thru 30.0 ** article for more information.​

Solution:

To resolve the ROW_LOCK issues, we added for update to the SOQL query, which should prevent locking of one record from one process with another. if locking happens, it will wait for 10 seconds to prevent locking and allow the Sync fields to be updated.

​​​​​Risk Analysis: Low

Affects which Fea​tures / Functionality: Quick Start Component

Availability: Automatic

Implementation Steps

None

How To Test

1. In Lightning UX, use Quick Start component

2. In the Quick Start component, search for Person Account.

3. Confirm the ​Search dialog loads the columns correctly and everything is working as expected.

January 2021 Deprecated and Deleted Items

AgentOne deletes metadata from the AgentOne Package in two phases, where the final/second phase is always in a subsequent release. This is to allow customers to plan for any changes in their orgs, if necessary.

Deprecate Sync Search Page
​​​​​​Description:

The custom sync search page Lightning Component needed security updates due to Salesforce enforced critical updates. It was determined that this page is no longer in use as Salesforce has significantly improved the out-of-the-box search functionality.

Solution:

Deprecate ​the sync search functionality.

​​​​​Risk Analysis: Low

Affects which Fea​tures / Functionality: IGO Integration, Pending Case Feeds

Availability: Automatic

Implementation Steps

Affects which Fea​tures / Functionality: IGO Integration, Pending Case Feeds

How To Test

 Confirm the Sync Search page previously added to tabs are now blank.

 

 

Leave A Comment