What's New?

New Features, Minor Changes, and Version History

New Features

Better name conflict handling

Custom objects and fields whose names match managed package components will behave correctly in all Core functions. For example, in previous releases, a custom field on the Application object named Applicant_Type__c would conflict with the managed package field named EnrollmentrxRx__Applicant_Type__c, and Super Clone would fail when trying to clone these fields.

As of the Winter 21 release, these fields can coexist and Super Clone behaves as expected, cloning both fields. Also, in previous releases, you could not create a custom object named Education_History__c and configure it as a requirement item object because this name is already taken by the managed package object named EnrollmentrxRx__Education_History__c. In the Winter 21 release, there is no problem using such a custom object as Education_History__c as a requirement item object.

If you have a name conflict(s), simply click the “Configure Name Conflict” button in the Admin Panel, which will cause ERx Core to configure itself automatically to handle the conflict(s).

  • If you are running Erx Core version 5.9.12 or later, that is all you need to do
  • However, If you are running Erx Core version v5.9.10 or earlier, then you will need to create two Apex classes in a sandbox and deploy these via a change set to production
    • In a sandbox, create an Apex Class called “ERx_ExecuteLocal” and put the contents of this file inside it.
    • In the same sandbox, create a second Apex Class called “Erx_ExecuteLocalTest” and put the contents of this other file inside it.
    • Now deploy these two classes to your production org.

New UI for custom setting Allow Object Access

Gives you a familiar interface of checkboxes to grant CRUD (Create, Read, Update, Delete) object level access to site guest users who can trigger Core functions, such as Lead Conversion, Assignment Manager, Field Sync, creation of Application, etc. You no longer need to type the names of objects into a field on the custom setting record. Access this through the “Allow Object Access” item at the top of the Admin Panel.

Minor Changes

  • Security enhancements to align with Salesforce security standards

Version History

Version 5.9.22 – Released: May 6, 2021

Bug Fixes

When Application Object Configuration was set to a new object, applications redirect to a wrong page

Assignment Manager was failing with Lead object

Version 5.9.20 – Released: April 28, 2021

Bug Fixes
Pardot Touchpoint Connector was failing after upgrade
Documents Missing was not working after upgrade

Version 5.9.6 – Released: March 18, 2021

Bug Fix Allow Object Access now enforced when calculating Documents Missing

Version 5.9.5 – Released: March 11, 2021

Improvements Bug Fixes
Implemented OAuth for Pardot API Authentication and changed our integration with the Pardot API to use a Salesforce user (SSO) instead of a Pardot user. Fixed problem with error when Debug Mode is engaged
Admin Panel, Allow Object Access can now accomodate any number of users Fixed out-of-order firing of Field Sync steps