Skip to content

Releases: SalesforceFoundation/EDA

1.116

21 Jul 16:25
87d3a32
Compare
Choose a tag to compare

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

1.116 (Beta 1)

16 Jul 18:40
87d3a32
Compare
Choose a tag to compare
1.116 (Beta 1) Pre-release
Pre-release

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. [PR1810]
  • 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. [PR1810]
  • We fixed a problem that prevented Auto Enrollment from working when an Account Record Type API name was used in an Auto Enrollment Mapping. [PR1810]

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. [PR1810]

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. [PR1810]

Issues Closed

#1327: If the API/Developer Name of the Household Account is not 'HH_Account' Account Naming does not work properly [PR1810]

Installation Info

Sandbox & Scratch Orgs:
https://test.salesforce.com/packaging/installPackage.apexp?p0=04t1R000001IGrzQAG

Production & Developer Edition Orgs:
https://login.salesforce.com/packaging/installPackage.apexp?p0=04t1R000001IGrzQAG

Trialforce Template ID

TBD

1.115

04 Jul 01:08
b2d941c
Compare
Choose a tag to compare

Changes

  • We fixed a problem that made the new EDA Settings require Chatter.

Installation Info

Push Schedule

Sandbox orgs: 2021-07-03
Production orgs: 2021-07-13

Sandbox & Scratch Orgs:
https://test.salesforce.com/packaging/installPackage.apexp?p0=04t1R000001IGruQAG

Production & Developer Edition Orgs:
https://login.salesforce.com/packaging/installPackage.apexp?p0=04t1R000001IGruQAG

Trialforce Template ID

TBD

1.115 (Beta 2)

03 Jul 23:23
b2d941c
Compare
Choose a tag to compare
1.115 (Beta 2) Pre-release
Pre-release

Changes

  • We fixed a problem that made the new EDA Settings require Chatter. [PR1812]

Installation Info

Sandbox & Scratch Orgs:
https://test.salesforce.com/packaging/installPackage.apexp?p0=04t1R000001IGraQAG

Production & Developer Edition Orgs:
https://login.salesforce.com/packaging/installPackage.apexp?p0=04t1R000001IGraQAG

Trialforce Template ID

TBD

Pull requests with no release notes

  • Update installer strings [PR1809]

1.115 (Beta 1)

01 Jul 23:20
0a426b1
Compare
Choose a tag to compare
1.115 (Beta 1) Pre-release
Pre-release

Installation Info

Sandbox & Scratch Orgs:
https://test.salesforce.com/packaging/installPackage.apexp?p0=04t1R000001IGqmQAG

Production & Developer Edition Orgs:
https://login.salesforce.com/packaging/installPackage.apexp?p0=04t1R000001IGqmQAG

Trialforce Template ID

TBD

Pull requests with no release notes

  • Update installer strings [PR1809]

1.114

26 Jun 02:39
f536810
Compare
Choose a tag to compare

Changes

New Education Cloud Settings and EDA Settings

You asked and we listened. Welcome to the new Education Cloud Settings page, a new experience that provides entry points to valuable resources like Settings Health Check, product documentation, Trailhead modules, and more. In addition to these resources, the new page now serves as your entry point for EDA Settings, where you’ll see these great new enhancements:

  • New task-based navigation that’s presented in a table of contents view to make it easier to find the settings you need.

  • Popup windows and additional validation for specific settings to increase accessibility and reduce the potential of incorrectly configuring settings.

  • Updated labels that provide a unified, consistent user experience, making the tasks you can perform more clear.

  • Links from the UI to the EDA product documentation when settings warrant increased understanding before you implement them.

If you're starting with the trial version of EDA 1.114 (Summer ‘21), the Education Cloud Settings tab is enabled for the System Administrator profile by default. If you started with an earlier version or you're starting with EDA 1.114 through the installer, the previous version of EDA Settings has been retired, so you’ll need to visit Education Cloud Settings in the EDA Documentation for information on setting up the new tab and removing the old one.

New Fields on Lead Object for Prospect Management

To help your recruiting and admissions team track suspect and prospect data for your institution, we added new fields to the Lead object. For more information review the EDA Data Dictionary and Lead object reference in the EDA Documentation.

Control How Lead-Converted Accounts are Named

We added a new EDA Setting called Automatically Rename Lead-Converted Accounts. Now, you can choose to automatically rename Accounts created when a Lead is converted to use the account naming format that's associated with its record type in EDA Settings. When this setting isn’t configured, the Account name is determined by the Company field on the Lead record.

For example, let’s say you selected the Administrative record type in Automatically Rename Lead-Converted Accounts. When you convert a Lead and specify the Administrative record type, the Account record is renamed to use the Administrative Account Name Format specified in EDA Settings. An Account for a Lead named Louis Lombard is automatically renamed Lombard Administrative Account.

Starting with the trial version of EDA 1.114, this setting is configured to specify the Administrative and Household Account record types by default. If you started with a version of EDA earlier than 1.114 or you're starting with EDA 1.114 with the installer, no default record types are specified.

For more information about working with Leads, see Configure Leads Settings and Lead in the EDA Documentation.

Trigger Handler for Lead-Converted Account Naming

We added a new Trigger Handler, ACCT_RenameLeadConvertedAccounts_TDTM. If the Automatically Rename Lead-Converted Accounts setting is enabled in EDA Settings, this class automatically renames Accounts created when a Lead is converted to use the Account naming format associated with its record type in EDA. This Trigger Handler is enabled by default.

For information about the EDA setting, see Customize Administrative and Household Account Names.

Trigger for the ContentVersion Object

We added a new Trigger for the ContentVersion object. This Trigger doesn't contain logic and doesn't appear in the Trigger Handlers tab. It triggers the product-specific TDTM handlers that are marked Active in the product where the logic is executed. EDA doesn't have product-specific TDTM handlers for this object.

Installation Info

Push Schedule

Sandbox orgs: 2021-07-01
Production orgs: 2021-07-13

Sandbox & Scratch Orgs:
https://test.salesforce.com/packaging/installPackage.apexp?p0=04t1R000001IGqhQAG

Production & Developer Edition Orgs:
https://login.salesforce.com/packaging/installPackage.apexp?p0=04t1R000001IGqhQAG

Trialforce Template ID

TBD

1.114 (Beta 7)

26 Jun 00:06
f536810
Compare
Choose a tag to compare
1.114 (Beta 7) Pre-release
Pre-release

Critical Changes

Minor fixes to translation files [PR1807]

Installation Info

Sandbox & Scratch Orgs:
https://test.salesforce.com/packaging/installPackage.apexp?p0=04t1R000001IGqXQAW

Production & Developer Edition Orgs:
https://login.salesforce.com/packaging/installPackage.apexp?p0=04t1R000001IGqXQAW

Trialforce Template ID

TBD

Pull requests with no release notes

  • [EDA] Refactoring admin profile for proper EDA TSO application visibilities. [PR1537]

  • Summer '21 Release [PR1577]

  • Bump lodash from 4.17.20 to 4.17.21 [PR1765]

  • Add update installer [PR1771]

  • Add My Domain preflight [PR1794]

  • Fixing duplicate label name issue for upload beta build failure [PR1800]

  • Commenting out failing PermissionsManageTranslation [PR1803]

  • Account Naming and Multi Address Fixes [PR1806]

1.114 (Beta 5)

25 Jun 14:29
2f5aad0
Compare
Choose a tag to compare
1.114 (Beta 5) Pre-release
Pre-release

Installation Info

Sandbox & Scratch Orgs:
https://test.salesforce.com/packaging/installPackage.apexp?p0=04t1R000001IGpoQAG

Production & Developer Edition Orgs:
https://login.salesforce.com/packaging/installPackage.apexp?p0=04t1R000001IGpoQAG

Trialforce Template ID

TBD

Pull requests with no release notes

  • [EDA] Refactoring admin profile for proper EDA TSO application visibilities. [PR1537]

  • Summer '21 Release [PR1577]

  • Bump lodash from 4.17.20 to 4.17.21 [PR1765]

  • Add update installer [PR1771]

  • Add My Domain preflight [PR1794]

  • Fixing duplicate label name issue for upload beta build failure [PR1800]

  • Commenting out failing PermissionsManageTranslation [PR1803]

1.114 (Beta 4)

24 Jun 13:53
ddf67d9
Compare
Choose a tag to compare
1.114 (Beta 4) Pre-release
Pre-release

Installation Info

Sandbox & Scratch Orgs:
https://test.salesforce.com/packaging/installPackage.apexp?p0=04t1R000001IGgRQAW

Production & Developer Edition Orgs:
https://login.salesforce.com/packaging/installPackage.apexp?p0=04t1R000001IGgRQAW

Trialforce Template ID

TBD

Pull requests with no release notes

  • [EDA] Refactoring admin profile for proper EDA TSO application visibilities. [PR1537]

  • Summer '21 Release [PR1577]

  • Bump lodash from 4.17.20 to 4.17.21 [PR1765]

  • Add update installer [PR1771]

  • Add My Domain preflight [PR1794]

  • Fixing duplicate label name issue for upload beta build failure [PR1800]

1.114 (Beta 3)

27 May 16:53
bbb312c
Compare
Choose a tag to compare
1.114 (Beta 3) Pre-release
Pre-release

Installation Info

Sandbox & Scratch Orgs:
https://test.salesforce.com/packaging/installPackage.apexp?p0=04t1R000001IGfsQAG

Production & Developer Edition Orgs:
https://login.salesforce.com/packaging/installPackage.apexp?p0=04t1R000001IGfsQAG

Trialforce Template ID

TBD

Pull requests with no release notes

  • [EDA] Refactoring admin profile for proper EDA TSO application visibilities. [PR1537]

  • Bump lodash from 4.17.20 to 4.17.21 [PR1765]

  • Add update installer [PR1771]