KI-15
MIRF Integration Automated User Fails Does Not Correctly Support Account Locking
Key/Summary | KI-15 MIRF Integration Automated User Fails Does Not Correctly Support Account Locking | Status | Done |
Created | 09/17/2019 | Updated | 12/19/2019 |
Description | The native MIRF integration processes inbound MIRFs in the context of an 'Automated Process' user context. This type of user context does not afford the ability to associate additional permissions to an associated user account like a normal Salesforce.com user. As a result, this user cannot be granted the 'Override Lock' permission to correctly operate on Accounts that reflect a locked status. This issue then prevents the Interactions associated to inbound MIRFs from being correctly associated to local Accounts that are locked. | ||
Impacted Capabilities | Affected Apps | Medical Information Cloud - Classic Medical Information Cloud - Lightning | |
Affects Versions | V7 | Fix Version | V8 |
Steps to Reproduce | 1. Enable the MIRF integration 2. Trigger the MIRF integration such that it attempts to find and associate an Account stored locally within MIC that has a locked (MED_Locked__c = true) status. 3. Observe that the newly created Interaction record that corresponds to the inbound MIRF does not have the Locked Account associated. | ||
Workaround | To workaround this issue update the MED_Locked__c formula field on the Account object to include an exception for the Automated Process leveraged for the MIRF integration. For example: $User.Username <> "Automated Process" Customers should be sure to verify the correct spelling of the first and last name of the particular user context leveraged by the MIRF Integration to create interactions / requests. To verify simply refer to the listed user within the 'Created By' field on the Interaction or Request | ||