AgentOne Release Notes

AgentOne August 2020 Release Notes

UAT Release: Aug 19, 2020 ~noon ET  (completed)
Production Release: Aug 28, 2020  ~10:00pm ET (completed)
version 21.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.

Features

Enable Pending Case Alerts – move business logic to Salesforce for all remaining orgs
Update Aug 28 2020 – This feature will be enabled the evening of Tue Sept 1 at approximately 11pm ET, rather than Fri Aug 28 with the AgentOne August 2020 managed package production deployment that contains all other items in these notes.
​​​​​​Description:

All remaining customer orgs will switch to generate Pending Case Alerts in AgentOne instead of via the AgentOne data integration layer. This feature was released in AgentOne February 2020, with an extended time window provided for testing on QA and UAT environments.

Solution:
  1. iPipeline will update all AgentOne orgs to set the related parameter to true. This will take a few minutes to update to customer orgs.
  2. ESB release will disable creation of Pending Case Alerts for all customers.

​​​​​Risk Analysis: Medium

Affects which Fea​tures / Functionality:  Pending Case Feeds

Availability: Managed by iPipeline

Implementation Steps

N/A

How To Test

Sync a Pending Case with a status change or requirement that will generate an alert. Confirm that an alert is created.

Support for the next generation iGO Data Dictionary (DD3)
​​​​​​Description:

​iGO implementations need to adhere to the same, next generation (DD3) standard fields so that there is no need to map individual iGO project-specific fields to the data dictionary. We require a single set of pre-fill and sync mapper settings in AgentOne so that we can deliver consistent pre-fill and sync behavior for all of the carriers. The default pre-fill and sync settings should work for most carriers, so that there is minimal configuration work to support a new AgentOne carrier.

This new feature is only available for implementations that integrate with iGO projects that are completely migrated to the new IGO next generation screen designer, with full support for the next-generation data dictionary (DD3). If some products or carriers are not yet upgraded to this new technology, the feature is not available.

Solution:
  • Installation and logic based on an org-wide setting to indicate that that org uses the next generation data dictionary (DD3)
  • Template for the internal iPipeline mapping utility for new AgentOne implementations.
  • Pre-fill and sync mapper settings designated for the previous data dictionary, the new data dictionary or both
  • New default pre-fill and sync mapper settings for the next generation data dictionary
  • For the next generation standard fields (DD3):
    • Date fields have been changed to the following date format yyyy-mm-dd
    • Picklists will send/receive the picklist value instead of the respective ACORD code
    • Phone fields have been changed to include the area code and dial number into a single field and have the phone formatting removed (e.g. “(555) 123 4567” will be sent to iGO as “5551234567”)
    • State fields have been changed to send/receive the 2 letter abbreviated state instead of the ACORD code (e.g. California will be sent to iGO as “CA” instead of the ACORD code “6”)​​
  • Unique and specific rider mappings, as defined by the next generation data dictionary (DD3)

​​​​​Risk Analysis: Low

Affects which Fea​tures / Functionality:  IGO IntegrationIllustration Integration

Availability: Optional, available for new or migrating AgentOne orgs only

Implementation Steps

Engagement with the your AgentOne professional services project manager is required to set up a new carrier or migrate an existing carrier to the next generation iGO data dictionary (DD3).  They will be performing the following steps to prepare for your AgentOne implementation with out-of-the-box iGO pre-fill and sync mapping.

  1. Create a new mapping utility package (copied from the DD3 Mapping – Template) for the new carrier.​
  2. Add the carrier’s products to the mapping package
  3. If necessary, add, edit, or remove mapped fields
  4. ​​Submit the IT request to deploy the package to QA/UAT/Prod
How To Test

In an org that is configured for the next generation data dictionary (with a feature parameter managed by iPipeline), install the AgentOne package and:

  1. Confirm that the appropriate DD3 prefill settings are installed.
  2. Confirm that the appropriate DD3 sync mapper settings are retrieved in AgentOne Admin sync mapper.
  3. Start a new iGO case from AgentOne and confirm prefill to iGO works for Date, Phone, Picklists, and State or Country fields (see DD3 prefill settings identified above).
  4. Trigger a sync back to AgentOne and confirm iGO fields update the AgentOne records appropriately.  To reference the installed sync or prefill settings search by ‘DD3’ in the Admin App prefill or sync mapper sections.

Enhancements

iGO Lightning Component Usability Enhancements – UX and Refresh
​​​​​​Description:

The iGO Lightning component was refreshing the entire page when you closed it. When the Insurance Tools Component and the IGO Lightning Component were used on the same record home page, the “close iGO” button appeared immediately, when you clicked the button to start or open iGO, but there was no other indication that the application was responding.

Solution:

Improvements to the IGO Application Lightning component:

  • Add spinner during load time.
  • Refresh after clicking close button to update buttons.
  • Close button won’t refresh the page.
  • Error messages will display directly on the IGO component.

​​​​​Risk Analysis: Low

Affects which Fea​tures / Functionality:  Lightning Components, IGO Integration

Availability: Automatic

Implementation Steps

N/A

How To Test
  1. Add the iGO Lightning Component and Insurance Tools to the Insurance Case or Opportunity record home page.
  2. Click the Insurance Tool to Open iGO.
  3. Confirm you see the spinner before iGO displays.
  4. Click Close iGO, and confirm the whole page does not refresh.
Insurance Tools Support for Opportunity Integration
​​​​​​Description:

The AgentOne Insurance Tools should automatically create a behind-the-scenes Insurance Case with Opportunity integration enabled, provided all the information needed to create the case and start the iGO eApp or Illustration is available on the Opportunity.​

​​​​​​Solution:

Added logic to do the following:
1. Show the Insurance Tools buttons as enabled if the Product Type on the Opportunity record matches a Product Type that is configured with an AgentOne Insurance Tool, such as iGO or iPipeline Illustrations.

2.  Once the Insurance Tool is clicked, AgentOne will create a behind-the-scenes Insurance Case that is required to leverage AgentOne features, with fields from the Opportunity record as listed below.

  • Opp Object –> Insurance Case object
  • Account –> Primary Insured
  • Opp. Name –> Insurance Case Name
  • Product Type –> Product type

3. The user will see a success toast message indicating that the insruance tool has started. The toast message is dynamically generated – Started an [Tool’s Display name from Admin App –> Insurance Tool] for [Account Full Name].

4. If an existing associated Insurance Case is still in New Status, and the user edits the associated Opportunity’s Product Type, AgentOne will check if it’s a valid product type configured tool, and update the Insurance Case with new product type, if so. Otherwise, the product type is not updated on the Insurance Case, and the AgentOne Insurance Tools buttons will be disabled. Ideally, the implementation team will use the Lighting Component visibility rules to hide the Insurance Tools component for non-AgentOne product types.​

Created a new picklist field called Product Type (AgentOne__AO_Product_Type) on Opportunity, with approximately 35 default picklist options for new AgentOne implementations. This field will be used by default to map to Insurance Case Product Type.

The below is default list of Product Types for new implementations.

Accidental Death & Dismemberment
Credit Mortgage
Critical Illness
Disability Buy-Out
Disability Income Replacement Long Term
Disability Income Replacement Short Term
Dread Disease
Endowment
Excess Interest Life
Fixed Annuity
Fixed Indexed Annuity
Funeral Policy
Home Health Care
Income Replacement
Indexed Annuity – not otherwise specified
Indexed Universal Life
Interest Sensitive Whole Life
Long Term Care
Long Term Disability
Medicare Supplement
Nursing Home
Other
Overhead Expense
Registered Indexed Annuity
Short Term Care
Short Term Disability
Term
Term with Cash Value
Travel Accident
Universal Life
Variable Annuity
Variable Indexed Annuity
Variable Universal Life
Variable Whole Life
Whole Life

​AgentOne also supports the admin to configure their own Product Type field (must be type text or picklist) to be mapped to Insurance Case Product Type.

​Assumptions/Known Behavior:

  • ​​Currently, if the Opportunity does not have Account, the Insurance Tools component will not show. This behavior remains the same.
  • Product Type will be a required field on Opportunity, or a validation rule will be added for record types that will show the AgentOne insurance tool to require Product Type to be populated.
  • The Product Type picklist value on Opportunity must match the iGO product type that is configured for the iGO tools.
  • There is only ONE tool possible per product type/product line config.
  • The primary insured and product type will not typically change after a sync back from iGO, or when the case is no longer New status and you see Open case. If these values are modified, AgentOne does not update the Insurance Case automatically.

Risk Analysis: Medium

Affects which Fea​tures / Functionality:  Opportunity Integration, Insurance Tools Lightning Component, IGO Integration, Lightning Components

Availability: Optional

​​

Implementation Steps

To use this feature on the Opportunity:

  1. Add the Insurance Tools and iGO Lightning Compoonent to Opportunity record home page.
  2. Add AgentOne’s Product Type (AgentOne__AO_Product_Type) field on Opportunity (if you are using the AgentOne field). Remove the Product Types that do not apply.
  3. Or, use a custom Product Type field.
    • As an AgentOne Admin, navigate to the AgentOne Admin App.
    • Click on Application Configuration.
    • Click New and create the following entry
      Name: Opp Integration Product Type
      Key: IC.Opp.Integration.ProductType ​
      Value: [Metadata Name of Product Type field on Opportunity that will have values to map to Insurance Case Product TYpe] Category: Opportunity Integration
How To Test
  1. ​​​Create a new Opportunity and select a Product Type that is mapped to AgentOne tool like “Term.”
  2. Confirm that the Insurance tool button is enabled.
  3. Click Start Application and confirm that it launches iGO.

Fixes

None

Profile and Permission Set Changes

The​ following changes have been made to AgentOne permissions with the August 2020 release.

How to use this Info​​​​​
  • Since January 2019, iPipeline has highly recommended that all AgentOne customers use permission sets to assign AgentOne permissions to their users.
  • All new implementations should rely on Permission sets as the primary means of assigning AgentOne permissions.
  • We continue to support orgs that do not currently use permission sets by documenting all the permission changes here in the release notes.  The release notes only reflect the changes since the immediate previous release.  Complete permission set permissions are documented in the AgentOne Implementation Guide.
  • If you are not using the out of the box AgentOne Agent Permission set, then please reference the below changes to manually apply it to your cloned Permission Set or Profile as needed, following the respective AgentOne upgrade to the org.
​IMPORTANT: If your org is updated via Push Upgrade, then your Profiles will not get updated. Push upgrades do not give iPipeline the option to select Profiles to copy permissions to. If you are still relying on Profiles, then you will need to manually make Permissions changes to your Profiles. ​
AgentOne Agent Profile
  • ​​Added Edit Permission: ​Opportunity –> Product Type (AO_Product_Type__c)​
    • Related to: Insurance Tools Support for Opportunity Integration
  • ​​Added Edit Permission:  ​​Insurance Case Coverage –> Product Type (Product_Type__c)​​
    • Related to: Support for the next generation iGO Data Dictionary (DD3)
AgentOne Agent Permission Set
  • ​​Added Edit Permission: ​Opportunity –> Product Type (AO_Product_Type__c)​
    • Related to: Insurance Tools Support for Opportunity Integration
  • ​​Added Edit Permission:  ​​Insurance Case Coverage –> Product Type (Product_Type__c)​​
    • Related to: Support for the next generation iGO Data Dictionary (DD3)
AgentOne Admin Permission Set
  • None
AgentOne System User Permission Set
  • None
AgentOne Support Permission Set
  • None
AgentOne Tabs Permission Set
  • None

August 2020 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.

How to use this Info​​​​​

Phase 1 – Deprecation​ iPipeline plans to delete it from the AgentOne package in a subsequent phase because it is no longer required or used by the AgentOne package.

  • The purpose of announcing that it will be deprecated is to allow customers the opportunity to do any planning, cleanup, or migration if they happen to be using the item.
  • The recommendation for items listed in this phase is to update any processes or perform any configurations needed to no longer used the deprecated item, if it is being used.

Phase 2 – Deletion​​ – iPipeline has deleted the item from the AgentOne package.  It is no longer referenced, but could exist on your org.

  • ​The purpose of announcing this phase is to let you know that the deleted item will still exist in your org, but you have the option to clean it up and delete it.
  • The recommendations at this phase include optional cleanup to delete the deprecated items from your orgs.  It typically is not a required step.
Deprecated Items

None

Deleted Items

None

 

 

Leave A Comment