(updated Profile and Permission Set Changes – Feb 21 2020)
UAT Release: Feb 12, 2020 ~noon ET (completed)
Production Release: Feb 21, 2020 ~10:00pm ET
version 16.x
Announcement
AgentOne Chrome 80 Update
(Deployed with iGO 9.2 Feb 1, 2020)
Description:
Risk Analysis: Low
Affects which Features / Functionality: IGO Integration
Availability: Automatic
Enhancements
Flexible Filter for Case Requirements on the Requirements Lightning Component
Description:
Solution:
Affects which Features / Functionality: Underwriting Requirements and Alerts , Lightning Components
Availability: Optional
Map Fulfilled Date from Case Requirement for Pending Case
Description:
Resonant identifies non-outstanding requirements with a completed date, that indicates if the Case Requirement has been either fulfilled or cancelled. A customer requested to be able to filter their Case Requirements by the Completed Date, rather than the Received Date, but this field was not yet mapped into AgentOne from the Pending Case Feed.
Solution:
AgentOne now supports a new field on Case Requirement for Completed Date (Fulfilleddate__c), and a new entry in the Entity Field List, to represent the date on which the requirement was fulfilled (for completed status) or cancelled (for cancelled status). The new field is included on the Case Requirement layout. The Resonant pending case feeds now include the new field, which is mapped to AgentOne via the data integration layer. In addition, AgentOne now also allows admins and implementers to specify custom filters of requirements to display on the Requirements Lightning Component. See feature Flexible Filter for Case Requirements on Requirements Lightning Component, above.
Affects which Features / Functionality: Underwriting Requirements and Alerts
Availability: Automatic
Auditing and Logging for Transfer Scenarios
Description: Allow support users to troubleshoot issues related to Opp record ownership, iGO case ownership, and results of iGo case transfers.
Solution:
Introduced a Transfer Reason field on Insurance Case, plus logging for transfer that will identify 1) what triggered the transfer, 2) the transfer status, 3) results of the transfer [including previous and new iGO case owner], and 4) added history tracking on the fields (iGO User, Stransfer Status, and Transfer Reason).
Update AgentOne Page Layouts to Use Files Instead of Notes and Attachment Related Lists
Description: AgentOne default page layouts still have Notes and Attachments in our related lists, when we have updated all of our code to use Files instead.
Solution:
Updated the following Page Layouts to replace Notes and Attachments in Related List with Files:
- Account –> Account-AgentOne Business Account Layout.layout-meta.xml
- Account-Individual Account.layout-meta.xml
- Insurance Case Agent –> Agent__c-Agent Layout.layout-meta.xml
- Illustration –> Illustration__c-Illustrations_Layout.layout-meta.xml
- Policy Agent –>Inforce_Policy_Agent__c-Inforce Policy Agent Layout.layout-meta.xml
- Insurance Case –>InsuranceCase__c-Insurance_Case In Phase Layout.layout-meta.xml
- Insurance_Case Layout.layout-meta.xml
- Policy Service Request –> Policy_Request__c-Policy Request Layout.layout-meta.xml
- Trace –> Trace_Log__c-Trace Log Layout.layout-meta.xml
Affects which Features / Functionality: default AgentOne page layouts
Availability: Automatic for new installs; Optional Implementation Steps for existing orgs
Enhancement and Fixes – enable by April 2020 release
Pending Case Alerts – move business logic to Salesforce
Description:
Migrate the Pending Case Alerts logic from the AgentOne data integration layer into Salesforce triggers.
The AgentOne January 2020 release included flow templates and process builder templates which were intended to provide the Pending Case Alerts logic on Salesforce.
In the February 2020 release, the business logic was removed from flow templates and process builder templates and moved into code. This is mainly due to the fact that it is not ideal to support all customer scenarios and be able to push out upgrades that will work for all customers. Therefore, the decision was to not use flow templates and process builder templates.
For the February 2020 release, the flow templates and process builder templates are intentionally left to be active but have been modified to exit and do nothing (empty). This is intended because we would like the February 2020 active version of the flows and process builders to replace the January 2020 active version. Eventually, the AgentOne package will deprecate the flow templates and process builder templates.
The following Flows are active and empty:
- DEPRECATED – AgentOne: Create requirement Received Alert
- DEPRECATED – AgentOne: Handle Pending Case Alerts
The following Process builders are active and empty:
- DEPRECATED – AgentOne: Create Requirements Alerts
- DEPRECATED – AgentOne: Insurance Case Record Create or Update
Special deployment and QA notes for this enhancement and the relevant fixes that follow:
- Packaged In February 2020 release – but not automatically enabled.
- Flexibility is provided to so customers can enable it and schedule it into UAT testing when ready.
- HIGHLY RECOMMENDED to enable this feature as soon as possible after Feb 12 on UAT, to allow for plenty of time to validate it.
- Regression around Pending Case Feed testing is recommended if you have custom logic, post processing of Pending Case syncs.
- Coordinate with PS Account Manager/Product Manager to enable feature.
- This feature is targeted to be enabled with the AgentOne April 2020 release dates for any/all orgs that were not previously upgraded per the customer’s coordinated timeline.
Affects which Features / Functionality: Alerts, Pending Case Status and Alerts
Availability: Coordination (to enable) and testing steps, required before April 2020 production release
Pending Case Status Alerts were only created once per unique status
Description: AgentOne should create the alert again if there is currently no active alert for Issued and Ready for Delivery, Concluded, or Delivered and the Insurance Case reaches that same status on a subsequent status update.
Solution:
Change the check for existing alerts to search only active alerts.
Affects which Features / Functionality: Alerts, Pending Case Status and Alerts
Availability: See Pending Case Alerts – Move Business Logic to Salesforce
New requirements for a delivered or concluded case were automatically dismissed
Description: New requirements that came with a concluded or delivered status were inadvertently dismissed immediately because the previous business logic dismissed all previous alerts, and the new alert was not distinguished from the previous alerts.
Scenario:
Update for Policy 123 comes to AgentOne: Policy Number 123 comes in with pending or issued status.
- New Req A
- New Req B
Actual behavior: Alert for Req A and B is created.
Second Update for Policy 123: Policy Number 123 comes in with delivered or concluded status, with a new requirement.
- Update Req A
- Update Req B
- New Req C
Actual Behavior: Alert for Req C is created. Alerts for Req A, B and C are all dismissed.
Expected Behavior: Only alerts for Req A and B should get dismissed, and alert for Req C should be active (show alert = true).
Solution:
The action to dismiss previous alerts will occur first, then create any new alerts that were not previously created. New requirements are identified by requirements that did not have a matching ExternalID already in the system. ExternalID is the RequirementUniqueInfoID for the related Case Requirement.
Affects which Features / Functionality: Alerts, Pending Case Status and Alerts
Availability: See Pending Case Alerts – Move Business Logic to Salesforce
Alerts for new requirements that accompany a case in a concluded or delivered status were dismissed immediately
Description:
Alerts for new requirements that accompany a case in CONCLUDED/DELIVERED status were dismissed immediately. AgentOne was dismissing all previous alerts, and was erroneously treating the new alert as a previous alert.
Solution:
Update for Policy 123 comes to AgentOne: Policy Number 123 comes in with Pending or Issued Status.
- Open Req A
- Open Req B
Actual Behaviour: Alert for Requirements A and B is created.
Second Update for Policy 123: Policy Number 123 comes in with Pending or Issued Status.
- Open Req A
- Open Req B
- Open Req C
Actual Behavior: Alert A and B and C is created then dismissed.
Expected Behavior: Only alerts for Requirement A and B should get dismissed. Alert for Requirement C should be Active.
Risk Analysis: Low
Affects which Features / Functionality: Underwriting Requirements and Alerts
Availability: Enabled with Pending Case Alerts – move business logic to Salesforce
Requirement alert is not created when relationrolecode for the fulfiller party is 11 – agent
Description:
Requirement alert was not created when RelationRoleCode for the fulfiller party type is a non-specific agent type role (tc=11 “agent”).
Solution:
New business logic was introduced in the data integration layer. If the pending case includes a requirement that has no Responsible Party Type but the specified fulfiller Party has the Relation Role type code of 11 (non-specific agent type), then it will set the Responsible Party Type to 1 (agent).
Risk Analysis: Low
Affects which Features / Functionality: Underwriting Requirements and Alerts
Availability: Enabled with Pending Case Alerts – move business logic to Salesforce
Profile and Permission Set Changes
The following changes have been made to AgentOne permissions with the February 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.
February 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.