Skip to content

Releases: SFDO-Community/Summit-Events-App

0.41.0.1

02 Apr 16:42
14554dc

Choose a tag to compare

Changes

  • Custom meta data contact matching mapping in concert with matching rules were not honoring the matching only flag and were copying matching only data into the created new contact (lead/person account). matching only fields are now removed from created object
  • QR code in the formula for the field Registrant_Id_QR_Code__c was not rendering correctly in transactional email. This bug has been fixed

Issues Closed

#595: Should we align Summit Events Registration Address field text limits to Salesforce Contact field? It can create issues if Flows are involved.
#640: [BUG] - The Matching Only flag is not respected with the Summit Events Contact Matching Mappings within the Custom Metadata Types
#641: [BUG] QR code not rendering in transactional emails
#644: [BUG] - Contact User Mapping to Registration Error

Installation Info

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

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

0.41.0.1

02 Apr 16:28
14554dc

Choose a tag to compare

0.41.0.1 Pre-release
Pre-release

Changes

  • Custom meta data contact matching mapping in concert with matching rules were not honoring the matching only flag and were copying matching only data into the created new contact (lead/person account). matching only fields are now removed from created object [PR642]
  • QR code in the formula for the field Registrant_Id_QR_Code__c was not rendering correctly in transactional email. This bug has been fixed [PR642]

Issues Closed

#595: Should we align Summit Events Registration Address field text limits to Salesforce Contact field? It can create issues if Flows are involved. [PR642]
#640: [BUG] - The Matching Only flag is not respected with the Summit Events Contact Matching Mappings within the Custom Metadata Types [PR642]
#641: [BUG] QR code not rendering in transactional emails [PR642]
#644: [BUG] - Contact User Mapping to Registration Error [PR642]

Installation Info

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

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

0.40.0.1

08 Jan 19:47
c99ea4c

Choose a tag to compare

Changes

  • Fields added to Event object that mirror fields created for lead and contact matching to facilitate person account matching controls: Custom_Metadata_Person_Account_Matching__c, Person_Creation_Duplicate_Rule__c, Person_Matching_Duplicate_Rule__c, Person_Matching_No_Match_Behaviour__c, Person_Matching_Rules__c
  • A new field was added to the event object to control whether matching will happen for guest a registrant adds during registration: Use_Matching_for_Guest_Registrations__c
  • Person account field added to registration: Person_Account__c, New_Person_Account_Created__c
  • SummitEventsContactMatching class totally rewritten to bulkify queries better and to make more shared methods for all matching processes. The later became important to get test coverage in orgs whether they had person accounts active or not.
  • Apex Unit tests updated for new person account matching feature
  • Matching trigger now triggers on update as well as insert to facilitate guest registrant matching (guest registrations only are inputted at the end of the registration process).
  • scratch org structure added for education cloud so that you can define it in cumulusci.yml file
  • method added to SummitEventsShard to identify if an org has person account enabled
  • Rudimentary robot tests have been added for future expansion later
  • API updated to 64.0
  • Fixed Cancel closed event status so that it will not close event cancellation prematurely
  • Added a statement about connected apps to the documentation folder

Issues Closed

#481: [FEATURE] Add Person Account functionality so SEA works with new Education Cloud and Nonprofit Cloud
#616: [BUG] Canceling a guest does not update Event Instance capacity
#630: [BUG] - Portal User Unable to register with Custom Questions.

Installation Info

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

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

0.40.0.1

08 Jan 18:30
c99ea4c

Choose a tag to compare

0.40.0.1 Pre-release
Pre-release

Changes

  • Fields added to Event object that mirror fields created for lead and contact matching to facilitate person account matching controls: Custom_Metadata_Person_Account_Matching__c, Person_Creation_Duplicate_Rule__c, Person_Matching_Duplicate_Rule__c, Person_Matching_No_Match_Behaviour__c, Person_Matching_Rules__c [PR601]
  • A new field was added to the event object to control whether matching will happen for guest a registrant adds during registration: Use_Matching_for_Guest_Registrations__c [PR601]
  • Person account field added to registration: Person_Account__c, New_Person_Account_Created__c [PR601]
  • SummitEventsContactMatching class totally rewritten to bulkify queries better and to make more shared methods for all matching processes. The later became important to get test coverage in orgs whether they had person accounts active or not. [PR601]
  • Apex Unit tests updated for new person account matching feature [PR601]
  • Matching trigger now triggers on update as well as insert to facilitate guest registrant matching (guest registrations only are inputted at the end of the registration process). [PR601]
  • scratch org structure added for education cloud so that you can define it in cumulusci.yml file [PR601]
  • method added to SummitEventsShard to identify if an org has person account enabled [PR601]
  • Rudimentary robot tests have been added for future expansion later [PR601]
  • API updated to 64.0 [PR601]
  • Fixed Cancel closed event status so that it will not close event cancellation prematurely [PR601]
  • Added a statement about connected apps to the documentation folder [PR632]

Issues Closed

#481: [FEATURE] Add Person Account functionality so SEA works with new Education Cloud and Nonprofit Cloud [PR601]
#616: [BUG] Canceling a guest does not update Event Instance capacity [PR601]
#630: [BUG] - Portal User Unable to register with Custom Questions. [PR601]

Installation Info

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

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

Pull requests with no release notes

  • Update CODEOWNERS [PR631]

0.39.0.2

09 Dec 21:45
d7f0c33

Choose a tag to compare

0.39.0.2 Pre-release
Pre-release

Changes

  • Newer version of getDependentSelectOptions() properly gets the right picklist items for bug here: #587 [PR610]
  • Fields added to Event object that mirror fields created for lead and contact matching to facilitate person account matching controls: Custom_Metadata_Person_Account_Matching__c, Person_Creation_Duplicate_Rule__c, Person_Matching_Duplicate_Rule__c, Person_Matching_No_Match_Behaviour__c, Person_Matching_Rules__c
  • A new field was added to the event object to control whether matching will happen for guest a registrant adds during registration: Use_Matching_for_Guest_Registrations__c
  • Person account field added to registration: Person_Account__c, New_Person_Account_Created__c
  • SummitEventsContactMatching class totally rewritten to bulkify queries better and to make more shared methods for all matching processes. The later became important to get test coverage in orgs whether they had person accounts active or not.
  • Apex Unit tests updated for new person account matching feature
  • Matching trigger now triggers on update as well as insert to facilitate guest registrant matching (guest registrations only are inputted at the end of the registration process).
  • scratch org structure added for education cloud so that you can define it in cumulusci.yml file
  • method added to SummitEventsShard to identify if an org has person account enabled
  • Rudimentary robot tests have been added for future expansion later
  • API updated to 64.0
  • Fixed Cancel closed event status so that it will not close event cancellation prematurely

Installation Info

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

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

0.39.0.2

09 Dec 21:41
d7f0c33

Choose a tag to compare

0.39.0.2 Pre-release
Pre-release

Changes

  • Newer version of getDependentSelectOptions() properly gets the right picklist items for bug here: #587 [PR610]
  • Fields added to Event object that mirror fields created for lead and contact matching to facilitate person account matching controls: Custom_Metadata_Person_Account_Matching__c, Person_Creation_Duplicate_Rule__c, Person_Matching_Duplicate_Rule__c, Person_Matching_No_Match_Behaviour__c, Person_Matching_Rules__c
  • A new field was added to the event object to control whether matching will happen for guest a registrant adds during registration: Use_Matching_for_Guest_Registrations__c
  • Person account field added to registration: Person_Account__c, New_Person_Account_Created__c
  • SummitEventsContactMatching class totally rewritten to bulkify queries better and to make more shared methods for all matching processes. The later became important to get test coverage in orgs whether they had person accounts active or not.
  • Apex Unit tests updated for new person account matching feature
  • Matching trigger now triggers on update as well as insert to facilitate guest registrant matching (guest registrations only are inputted at the end of the registration process).
  • scratch org structure added for education cloud so that you can define it in cumulusci.yml file
  • method added to SummitEventsShard to identify if an org has person account enabled
  • Rudimentary robot tests have been added for future expansion later
  • API updated to 64.0
  • Fixed Cancel closed event status so that it will not close event cancellation prematurely

Installation Info

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

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

0.39.0.1

09 Dec 21:18

Choose a tag to compare

0.39.0.1 Pre-release
Pre-release

Changes

Installation Info

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

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

Pull requests with no release notes

  • Update CODEOWNERS [PR631]

0.38.0.1

05 Sep 13:24
917c112

Choose a tag to compare

Changes

  • Moved payment query when returning from payment gateway to shared read query. Payments were not completing upon return to SEA because payment record could not be found.
  • Moved auto add appointment query to shared read queries. 'Added', 'Added but not shown', and 'Added and required' appointment types were not receipting correctly as appointments.
  • Fixed reg id assignment to appointments
  • Added unit test to cover auto added appointments

Installation Info

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

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

0.38.0.1

03 Sep 23:39
917c112

Choose a tag to compare

0.38.0.1 Pre-release
Pre-release

Changes

  • Moved payment query when returning from payment gateway to shared read query. Payments were not completing upon return to SEA because payment record code not be found. [PR626]
  • Moved auto add appointment query to shared read queries. 'Added', 'Added but not shown', and 'Added and required' appointment types were not receipting correctly as appointments. [PR626]
  • Fixed reg id assignment to appointments [PR626]
  • Added unit test to cover auto added appointments [PR626]

Installation Info

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

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

0.37.0.2

14 Aug 17:06
246d855

Choose a tag to compare

Changes

  • Consolidated queries
  • Fixed a unit test that was failing do to correct deletion of fees
  • Fixed newly introduced bug that made a new registration when someone went back and changed their first/last/email on the registration
  • Used inline query for generated itinerary for registration record view
  • No longer deleting fees for garbage collection. Just updating and inserting

Installation Info

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

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