Version 1.6 was released to the AppExchange on 6/18.
With this release we added new performance and UX enhancements as outlined below.
Salesforce does not allow batches to be triggered from future methods for third party applications. We have updated our application to delay the batch updates from the Boomtown app until after the future method is completed in order to avoid these errors.
We added a performance enhancement that is an additional check on the workflow rules to first check if any of the mapped fields changed. We will only call the data sync if the change on the record is for a field that is mapped. Otherwise, we skip the sync since no data will transfer between systems.
We updated the Account Name mapping to update both the Boomtown Customer Name and the Boomtown Location name. If the Salesforce Account Name changes, the Customer Name and Location Name will remain in sync between Salesforce and Boomtown.
We enhanced our Contact mapping for when Cases are synced from Boomtown to Salesforce and Contact record are not synced. If the Boomtown Case is related to a Contact that is not synced, we will check the email, phone number, and name of the Contacts on the related Account to see if we can find a matching Contact. If one is found, we will relate that Contact to the Case in Salesforce. This increases the likelihood that Contacts in Salesforce will be appropriately tagged even when Contact data syncing is turned off.
We added an additional field on the Mappings tab that allows users to select the direction of how Case Comments get synced. You can set comments to not sync, unidirectional, and bidirectional. Case Comment syncs are still only triggered when Case Workflow Rules evaluate to true.
You can now use Lookup Fields in your Workflow Rules (previously hidden). This will provide additional flexibility for building custom Workflow Rule logic.
Version 1.7.0 was released to the AppExchange on 7/14.
This is a minor release that had a few bug and performance enhancements.
Previously custom field data would only sync after the record was created and then updated. We updated this workflow so custom field data syncs from Salesforce to Boomtown on initial record creation. We also fixed a bug where this was causing fields in Salesforce to become blank after the sync back from Boomtown.
We added an extra check on the data sync to make sure that adding the batch job to the flex queue will not push it over the 100 job limit that Salesforce imposes. If we find that the batch job will push the Flex Queue past 100 jobs, we will skip the sync for those records. In the future we will add a queue mechanism to hold those syncs until after the Flex Queue has returned to lower levels.
We updated our app for test classes. We added a check for the existence of custom settings in our code and test environment. This will allow organizations to run automated tests that include our managed package.
Version 1.7.2 was released to the AppExchange on 8/4.
Version 1.8.0 was released to the AppExchange on 8/11.
Version 1.9.1 was released to the AppExchange on 8/31.
As always, if you have any questions please email us at email@example.com
What is a customer journey map? And why should companies invest the time and the resources to map their customers' experiences within their organization?
Today we are pleased to announce that Aevi is expanding into North America and has selected OvationCXM as its CXM provider.