1.116
Changes
- We fixed an issue that caused Lead-converted Account naming not to work as expected when you select an existing Administrative or Household Account during conversion. Now, if you select an existing Administrative Account when converting a Lead, the Account name doesn’t change. If you select an existing Household Account, the Account name changes according to EDA Settings.
- We fixed an issue that caused Household Account Naming not to work as expected when you select a custom Account Record Type as your Household Account Record Type.
- We fixed a problem that prevented Auto Enrollment from working when an Account Record Type API name was used in an Auto Enrollment Mapping.
New Fields on the Application Object
To make it easy for you to track the date when an applicant is able to submit an application and the date by which they must submit one, we added the Open Date and Due Date fields to the Application object.
New Trigger Handler
We added a trigger handler, Application_TDTM, that verifies that the Application Due Date follows the Application Open Date. At this time, if you need to disable it, do so from Trigger Handlers. In an upcoming release, you'll be able to manage the trigger handler from EDA Settings.
Issues Closed
#1327: If the API/Developer Name of the Household Account is not 'HH_Account' Account Naming does not work properly
Installation Info
Push Schedule
Sandbox orgs: 2021-07-21
Production orgs: 2021-07-27
Sandbox & Scratch Orgs:
https://test.salesforce.com/packaging/installPackage.apexp?p0=04t1R000001IGuAQAW
Production & Developer Edition Orgs:
https://login.salesforce.com/packaging/installPackage.apexp?p0=04t1R000001IGuAQAW
Trialforce Template ID
0TT4W000007A4Qe