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
Announcement
AgentOne Chrome 80 Update
(added – Jan 31)
Description:
Risk Analysis: Low
Affects which Features / Functionality: IGO Integration
Availability: Automatic
Enhancements
AgentOne Quick Start Lightning Component – UI update
(updated with images and implementation steps – Jan 10)
Description:
Solution:
- 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 Features / 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
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 https://releasenotes.docs.salesforce.com/en-us/winter20/release-notes/rn_aura_ui_deprecate.htm.
Solution:
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.
Affects which Features / Functionality: AgentOne Admin App, AgentOne Lightning Components , Quick Start Component
Availability: Automatic
Enhancements – not yet enabled
(added with an update Jan 8 ~3pm ET)
Pending Case Alerts – move business logic to Salesforce
Description:
Solution:
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 approved, completed, 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
- triggers the Handle Pending Case Alerts Flow
The flows will call custom code to Create and Dismiss Alerts while respecting Alert Rules.
Affects which Features / Functionality: Alerts, Pending Case Status and Alerts
Availability: Required testing and coordination steps, before March 2020 release (tentative target)
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.