Skip to content

0.36.0.5

Choose a tag to compare

@tcdahlberg tcdahlberg released this 22 May 22:00
· 80 commits to master since this release
7b55643

Critical Changes

  • populateAppJSON() method in options.js now is not executed when SummitEventsRegisterAppointments vf page renders
    N/A
  • None

Changes

The issue of having the page blocked after it rendered it's because "fadein()" method was throwing an error (basically a null pointer exception). The "SummitEventsRegisterAppointments" vf page has no any element with id as "backpage" and fadein method was depended on getting at least one element to assing style.display to it.
This is the current order of execution:

  • appointmentsReady()
    • populateAppJSON()
      • checkForRequiredAppointments()
        • fadeIn()
    • InitiationOfAddButtons()
      Notes:
  • fadeIn() error was not letting InitiationOfAddButtons to execute
  • I'm calling InitiationOfAddButtons() the if block located from line 46 in options.js
    There are 2 ways to fix it:
    1 - Change the order of execution where populateAppJSON() is executed after InitiationOfAddButtons()
    2 - Do not call populateAppJSON in the rendering process.
    Since the expectation is not having it open when the page renders, the 2nd option fits better and the accordion will open automatically if it was missed and the user clicked next.
  • Took field accessibility check off test data factory
  • Fix a small typo for the word "Registration".
  • Mimicking usage of "regularLists" from SummitEventsRegister. "regularLists" css selector is applied to a div component, not directly to a "p" tag. (Reference line 89 from SummitEventsRegister)
  • Guest records are now populated with event instance time formatted
  • Fixed bug in letterhead where image urls were not being generated correctly resulting in missing images
  • Moved accessibility and dietary questions above address fields
  • Added "no-show" status for calculating if registrant can re-register for an event when one reg per registrant is set
  • Added feature to lookup custom questions where you can order by your record results
  • Added a text field version of birthdate so that matching rules can use it for matching (since date isn't part of Salesforce matching abilities)
  • Fixed qr code formula to use new service https://api.qrserver.com . In order for qr codes to appear https://api.qrserver.com needs to be added to an orgs trusted urls.
  • Added a qr code of reg id to registration record for checking flow possibilities
  • Changed var to let in registration.js for small change for packaging

Issues Closed

#533: [BUG] - Required Appointment Error
#562: [BUG] Registration QR image broken
#580: Convert Registrant Date of Birth field to a Registrant Birthdate Text field so we can leverage Birthdate as part of Salesforce Duplicate Matching criteria.
#582: Add Order By ability for custom questions
#586: [FEATURE] Enhancement to One registration per event adding no-show status to free registration
#592: Move new Accessibility and Dietary need fields above the Address fields.
#593: [BUG] Letterheads not generating correct links to header and footer images
#597: The summit__Event_Instance_Date_Time_Formatted__c field is not being populated for Hosted Guest Summit Events Registration records.

Installation Info

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

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