AgentOne Release Notes

AgentOne December 2019 Release Notes

UAT Release Group 1: Dec 6, 2019 ~noon ET
UAT Release Group 2: Dec 11, 2019 ~noon ET
Production Release: Dec 13, 2019 time ~10:00pm ET

New Features

Insurance  Tools Component – Copy Case


As an insurance agent, I want to be efficent when selling multiple products to the same customer, so that I can maximize my productivity and provide a good experience for my customers.
As an agent user using the Salesforce Lightning Experience, I want to copy an existing Insurance Case for the proposed insured from an existing Insurance Case or Opportunity, so that I don’t need to ask all of the same questions again when selling different insurance product (such as UL in addition to term insurance) to the same person.

Updated the existing AgentOne – Insurance Tools Lightning Web Component, and introduced two additional Lightning Components for Copy that can be added to a record home page in any of the following places:

  1. As a new button in the AgentOne – Insurance Tools Lightning Web Component
  2. As a stand-alone button using the AgentOne – Copy Case Lightning Component
  3. As a Lightning Action using the CopyInsuranceAction Lightning Component

When the Copy button is clicked, AgentOne will copy the current record (Insurance Case or other) and the linked Insurance Case, if applicable, then make the iGO request to copy the associated iGO case.

NOTE: There is no technical method to restrict where this component can be added but, as a general rule, it should not be added to packaged AgentOne child records of Insurance Case. (e.g. Alerts, Illustrations, Requirements, etc…).  It is intended for Insurance Case, Opportunity, or another custom object that has a 1:1 relationship with Insurance Case.
Risk Analysis: Low

Affects which Features / Functionality: AgentOne Lightning Components, Insurance Cases

Availability: Optional

Implementation Steps

Log in as an administrative user

Open the record home page using the Lightning App Builder then add the desired lightning component from either

  1. AgentOne – Insurance Tools‘ (enable the button)
  2. AgentOne – Copy Case‘​ (stand alone button), OR
  3. Create a new ‘Lightning Action’ with the following
    • Action Type = Lightning Component
    • Lightning Component = c:CopyInsuranceAction
    • Label = Copy Case (or any custom label you’d like)
    • Name = <leave system generated name as is
    • Edit the page layout and add the new lightning action to the ‘Salesforce Mobile and Lightning Experience Actions’

iGO web services must configured and enabled and duplicate case web service action must be enabled on iGO.  Please work with your Professional Services Account manager and refer to the following sections in the AgentOne Implementation guide:
  • iGO Web Service Configuration
  • ​Copy(Duplicate) Case
How To Test

From Insurance Case

  1. ​Add the desired lightning component or lightning action as mentioned above to Insurance Case record home page
  2. Create a new Insurance Case record and start iGO then trigger a sync back to AgentOne
  3. Open the insurance case record from step 2 and click the ‘Copy’ button
  4. Click OK to proceed then wait for the success toast message

​​From Opportunity (or another custom object):

  1. Add the desired lightning component or lightning action as mentioned above to Opportunity (or custom object record) home page
  2. Create a new Insurance Case record and start iGO then trigger a sync back to AgentOne
  3. Create a new Opportunity (or custom object record) and link it to the insurance case from step 2
  4. Open the record from step 3 and click the ‘Copy’ button
  5. Click OK to proceed then wait for the success toast message


Flow Template to Purge Old Dismissed Alerts

​​​​​​Description:  The AgentOne Alerts record count is getting high in some customer orgs, and we are starting to see limits errors related to the number of Alerts records.  This flow is intended to help auto-purge dismissed Alerts, as there is no intended purpose for retaining them long after they’ve been dismissed.​


Create a Flow Template called Purge Old Dismissed Alerts with the following default conditions (Dismissed alerts created more than 120 days ago)

  • Days_Since_Creation__c > 120
  • ShowAlert__c = false (AgentOne definition of a dismissed​ Alert)
  • Scheduled to run weekly

This flow is intended to be used to delete Alerts on an ongoing basis, in order to avoid future issues encountered due to excessive volumes of dismissed Alerts.  If you have built up many ​Alerts in your org, you may want to use an alternative approach to purge or archive most of your dismissed Alerts before scheduling this job.

​​​​​Risk Analysis: Low

Affects which Fea​tures / Functionality: Alerts

Availability: Optional (recommended for customers with significant volumes of historical alerts)

Implementation Steps


The Salesforce Release Note from Winter ’20, to Start a Flow on a Schedule identifies a limit for scheduled flows:
There’s a per-org 24-hour limit for the number of scheduled flow executions at the scheduled start time. The org limit is whichever is greater: 250,000 records or the combined total of 200 records per user license. When a flow is scheduled to start, make sure that its schedule and conditions don’t cause your org to go over the limit.

This means two things:

1. Before you can schedule this Flow, you should clean up your Alerts if you have a vast amount of dismissed Alerts that have built up over the years.  For example, if you have over 1 million dismissed Alerts that are over 120 days old, you may choose to delete those Alerts a different way, to get the total count down to a manageable size before the flow can be scheduled to run successfully.  You can use SOQL query or Workbench to mimic the query that you have in your scheduled flow to find the ideal conditions, to determine if this limitation will impact you.

2. If there are more than 250,000 Alerts that are dismissed on your org every week on an on-going basis​, you may want to schedule it to run more frequently, such as daily.


1. Go to Setups –> Flows
2. Edit the flow template – Template – Purge Old Dismissed Alerts.
3. Modify the default settings as desired.
4. Save the flow and activate.
How To Test
Start the Flow and confirm that after it is run, the Alerts have been deleted.





Leave A Comment