AgentOne Release Notes

AgentOne January 2020 Release Notes

Updated Jan 31

UAT Release Group 1: Jan 8, 2020 ~noon ET (completed)
UAT Release Group 2: Jan 15, 2020 ~noon ET (completed)
Production Release: Jan 17, 2020  ~10:00pm ET

version 15.x


AgentOne Chrome 80 Update

(added – Jan 31)


iGO fails to load from the AgentOne Canvas app or Lightning Component, or when attempting to e-Sign from an alert, when the Chrome settings (to simulate the default Chrome 80 increased security measures rolling out starting Feb 17) for ‘​​SameSite by default cookies’ and ​’Cookies without same site must be secure’ are enabled.
Fixed to coincide with iGO January 2020 (9.2): Cookies that may be used in a 3rd party context are now being set with a SameSite attribute of “None”.
If the domain associated with a cookie matches an external service and not the website in the user’s address bar, this is considered a cross-site (or “third party”) context. The Chrome 80 release (scheduled for February 2020) changes the default cross-domain (SameSite) behavior of cookies from the default attribute of “Lax” to “None”. The change in the default attribute means that an iGO domain in the cookie, which doesn’t match the website in the address bar, can not be loaded. See the links below to the Salesforce KB article and Chrome blog for more details.

​​​​​Risk Analysis: Low

Affects which Fea​tures / Functionality: IGO Integration

Availability: Automatic

Implementation Steps


How iPipeline Tested

The following represents the progression of related product deployment events through at least February 17, when the Chrome 80 Same Settings begin rolling out for an initial limited population. iPipeline has validated all of these scenarios to ensure that iGO integration from AgentOne will be operational under all expected scenarios, and is well positioned to support the Chrome 80 launch without issue. Customer UAT validation is not required or expected, but iPipeline testing steps are provided should customers with to perform their own tests.

When​ Salesforce Release Google Chrome SameSite enabled iGO release
Today – Feb 1 Winter ’20 79 Off 9.1.x
Feb 1 – Feb 4 Winter ’20 79 Off 9.2
Starting Feb 4 Winter ’20 80 Off 9.2
Starting Feb 7 Spring ’20 80 Off 9.2
Starting Feb 7 Spring ’20 79, if not auto-updated Off 9.2​
​Starting Feb 17 ​Spring ’20 ​80 ​On ​9.2

​Enable SameSite – Simulate the Chrome 80 SameSite settings Feb 17+, using Chrome 79:

Note: To simulate the default Chrome 80 security settings, you will need to use a recent version of Chrome (e.g. 79.x), and to enable the SameSite settings below. These settings should only be tested against orgs running the Salesforce Spring ’20 release or prerelease (sandbox orgs with Spring ’20). If you have the Chrome 80 beta, these settings are already enabled by default.
  1. ​Open Chrome and go to the following page chrome://flags
  2. Search for ‘SameSite’
  3. ​Change the following settings to Enabled
    • SameSite by default cookies
    • Cookies without SameSite must be secure
  4. ​Restart Chrome


Launch iGO

  1. ​Open or create a client record
  2. Start a new case and proceed through the quick start component
    Open an existing insurance case
  3. Start or open iGO

Sign from Alert (if enabled on your org)

  1. Create or open an insurance case
  2. Launch iGO and complete and lock the case
  3. Select ClickWrap (signature via email)
  4. Sign by all participants except the agent
  5. Confirm the signature required alert is synchronized and created in AgentOne
  6. Click the [Sign] action in Alert (either from the alerts Lightning Component, related list, or AgentOne home page)​

Disable SameSite – ​Simulate Chrome 79, or Chrome 80 state from Feb 4 through at least Feb 17

Note: If you have the Chrome 79 or previous, and have not enabled SameSite per the instructions above, these settings are already disabled by default. If the settings have already been enabled or you have Chrome 80 beta, disable them to test other scenarios. These settings must be disabled when testing with Salesforce Winter ’20.
  1. ​​Open Chrome and go to the following page chrome://flags
  2. Search for ‘SameSite’
  3. ​Change the following settings to Disabled
    • SameSite by default cookies
    • Cookies without SameSite must be secure
  4. ​Restart Chrome
  5. Repeat Launch iGO & Sign from Alert steps above
Important: If you are testing with the ‘SameSite’ settings enabled, then later disable the settings, you may be required to delete cookies before loading iGO. For example: If the user enables SameSite settings then launches SF Spring ’20 and starts a case If the user later disables SameSite settings and attempts to load iGO it could result in failure loading iGO. ​The solution is to delete cookies that were created while SameSite settings were enabled.


AgentOne Quick Start Lightning Component – UI update

(updated with images and implementation steps – Jan 10)


The iPipeline User Experience team recommended changes to the AgentOne Quick Start component, to better match the Opportunity record homepage when triggering the Start/Open iGO lightning component.


User interface changes to the component include:
  • Header color change (previously green)
  • Background (white)
  • Font/spacing/formatting

AgentOne Home (collapsed):

AgentOne Home (expanded):

New Insurance Case (Classic – from Client record or Insurance Case):

Lightning Component (on Opportunity record home page):

​​​​​Risk Analysis: Low

Affects which Fea​tures / Functionality: Quick Start Component

Availability: Automatic, if not previously leveraging custom XML for Add Client modal dialog

Required Manual Steps, if custom XML is used for the Add Client modal dialog

Implementation Steps

None, if not previously leveraging custom XML for Add Client modal dialog

If the ‘Cancel’ and ‘Save’ buttons from the Add Account dialog in the Quick Start component do not work it is likely caused by the fact that the org is setup to use a custom config file for the dialog and the button actions are setup to use the original ‘Aura’ action “press”. If this is true then the following manual post deployment steps are required to change the button action to “onclick”.

Steps (if custom XML is used for the Add Client modal dialog):

  1. Login as an administrative user and go to Setup
  2. Enter “Static” in the setup Quick find box and click ‘Static Resources’
  3. Find and click on the ‘PL_Lookup_Account_Page’ static resource
  4. Right click on ‘View File’ and select ‘Save link as’
  5. Save the XML file to your HD and open the XML file to edit
  6. Find and replace all instances of “press” with “onclick” then save the changes
  7. Go back to the PL_Lookup_Account_Page static resource in Salesforce and click the Edit button
  8. Click ‘Choose File’ and search for and select the XML file edited in step 6 then save
How To Test
  1. Ensure Quick Start component is loading and saving correctly.​
Aura Components in UI namespace being retired in Salesforce Summer ’21

​​​​​​Description: Salesforce is deprecating Aura components in the UI namespace in Summer ’21.  AgentOne is now using similar components in the Lightning namespace instead, as recommended by Salesforce in the Winter ’20 Release Notes here​.


All the UI tags are replaced with Lightning tags.  Removed unwanted CSS classes around UI elements and changed some js files based on tag changes.  Changed press to onclick for lightning:button.

​​​​​Risk Analysis: Medium

Affects which Fea​tures / Functionality: AgentOne Admin App,  AgentOne Lightning Components , Quick Start Component

Availability: Automatic

Implementation Steps


How To Test
  1. Confirm no errors in AgentOne Admin App for regular operations of creating, updating and saving settings.
  2. Confirm no errors occur where using the AgentOne Lightning IGO and AgentOne Quick Start Lightning Components

Enhancements – not yet enabled

(added with an update Jan 8 ~3pm ET)

Pending Case Alerts – move business logic to Salesforce


AgentOne pending case alerts are currently generated via business logic in the AgentOne data layer.  In order to address timing issues and extraneous (many false) sync errors between the data layer queues, source applications and Salesforce, the pending case alerts business logic has been moved to Salesforce.
Since the Pending Case processing and Pending case Alerts processing were separate disjointed processes, the pending case alert did not know when pending case processing was complete.


Migrate the Pending Case Alerts logic from the AgentOne data integration layer into Salesforce, as Processes and Flows.  This alternative implementation is only leveraged for orgs that have it enabled by iPipeline.  The flow will be installed as active, but the first check is to ensure that this feature is enabled.  If it is not enabled, the flow will exit immediately.

Three Flows were created as templates, and packaged as active flows:

  • Create Requirement Received Alert
    • Proceed only if Requirement is for an Agent, and that requirement isn’t in approvedcompleted, or cancelled status.
    • Proceed if a similar active alert doesn’t already exist and if not, then create an alert.
  • Handle Pending Case Alerts  (status changes)
    • Proceed only if the Insurance Case is Active.
    • Proceed If the Insurance Case status is in 1) Issued & Ready for Delivery, or 2) Delivered, or 3) Concluded status.
    • Proceed only if the active alert doesn’t already exist.
    • Dismiss all alerts associated with the Insurance Case.
    • Check if there is an existing dismissed alert.  If so, update it to active (non-dismissed) and change alert creation time to now.   Otherwise create new alert.
  • Create Logs for Flows (Create_Logs_for_Flows)
    • Called by the first 2 flows to log flow error handling

Two Processes created as templates, and packaged as active flows:

  • Create Requirements Alerts
    • triggers the Create Requirement Received Alert Flow upon Create of Requirement
  • Insurance Case Record Create or Update
    • triggers the Handle Pending Case Alerts Flow ​

The flows will call custom code to Create and Dismiss Alerts while respecting Alert Rules.

​This enhancement will require more significant validation testing than most low-risk features included in the monthly AgentOne release.  Consequently, it will be delivered but disabled for all orgs with the January 2020 release.  Customers and implementation teams can begin testing with the feature enabled as soon as Jan 22, and choose when to enable it on production orgs, anytime on or before the AgentOne March 2020 release.  This flexible window essentially provides two months for customer-specific UAT regression testing for any pending case alert generation that is identified.     ​
​​​​Risk Analysis: Low for Jan 2020 while disabled; Medium when enabled

Affects which Features / Functionality: Alerts, Pending Case Status and Alerts

Availability: Required testing and coordination steps, before March 2020 release (tentative target)

Implementation Steps
  1. This step can be done anytime after the January 2020 managed package (v15.x) is installed on the org (i.e. UAT or PROD push upgrade), and must be done on production orgs before the deadline (i.e. March 2020 Prod release date).  This step alone will not enable the feature unless step 2 is done.  In the org,
    • Confirm the following Flows are active:
      • ​Create requirement Received Alert​
      • Handle Pending Case Alerts
      • Create Logs for FLow (Create_Logs_for_Flows)
    • Confirm the following Process builders are active:
      • Create Requirements Alerts
      • Insurance Case Record Create or Update
  2. Coordinate with iPipeline to enable the Create Pending Case Alerts​ Feature Parameter for the specified org, at the desired day and time on or before the deadline. (i.e. March 2020 Prod release date)
  3. Coordinate with iPipeline to disable Pending Case Alerts in the AgentOne data layer, at the same day and time as Step 2.
How To Test
  1. Run all tests that create Pending Case Alerts in an org with the old data layer method.
  2. Enable and repeat tests.
  3. Confirm that alerts creation and dismissal behavior ​are the same (other than noted exceptions).

Profile and Permission Set Changes

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

How to use this Info​​​​​
  • It is highly recommended that going forward 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.
  • 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 permissions to ReviseIllustratonController class
    • ​Reason: Revise Illustration for Insurance Tools LWC
  • ​Added permissions to CopyInsuranceCaseAura​​ class
    • ​Reason: Insurance Tool Lightning Component for Copy Insurance Case
  • Added permissions to DismissAlertsForPendingCase​, CreateRequirementAlerts, CreateAlertsForPendingCase, FeatureParameterForFlow​​ class (added to notes Jan 15)
AgentOne Agent Permission Set
  • Added permissions to ReviseIllustratonController class
    • ​Reason: Revise Illustration for Insurance Tools LWC
  • ​Added permissions to CopyInsuranceCaseAura​​ class
    • ​Reason: Insurance Tool Lightning Component for Copy Insurance Case
  • Added permissions to DismissAlertsForPendingCase​, CreateRequirementAlerts, CreateAlertsForPendingCase, FeatureParameterForFlow​​ class (added to notes Jan 15)
AgentOne Admin Permission Set
  • None
AgentOne Support Permission Set
  • None
AgentOne Tabs Permission Set
  • None




Leave A Comment