Fonteva 20Spring Bug Fixes
Auto-Renewal Bug Resolved:
Renewal proforma orders are created using the Invoice Days Variable field on the Subscription Plan. Proforma renewal orders are sent out prior to the subscription expiration date based on the value set in this field. If the subscription is also enabled for auto-renewal, Scheduled Payment Records are also created based on this date so customers can automatically be charged.
Fonteva 20Spring has resolved a bug that set the Next Scheduled Renewal Date on the Subscription record to the Invoice Days Variable. This allowed staff users to charge their customers early to renew a subscription instead of on the last day of the subscription.
The Next Scheduled Renewal Date now uses the Paid Through Date value from the Subscription record. Renewal will be charged on the last day of the subscription if it has not already been renewed.
Critical Bugs Resolved in Fonteva 20Spring:
On Directories for the Account object, images failed to display properly when there was a long description for an Account. Images will now display properly even when there is a long description field.
If an Item’s package items were changed, they failed to be added to the renewal Sales Order, and the original Sales Order Lines would get copied over. An Item’s current package items will now successfully get added to the Sales Order on renewal instead of copying over the Sales Order Lines from the original Sales Order.
When a Rich Content Editor component was inserted above the Navigation Bar on a Directory Lightning Page, the Geo View map came out of alignment. The Geo View map will now display properly when a Rich Content Editor is inserted above the Navigation Bar on a Directory Lightning Page.
When there were a large amount of System Logs, the System Log Shipper would fail and generate an error message. The System Log Shipper can now successfully handle large amounts of logs.
An incorrect line description displayed on the Invoice PDF when staff users purchased tickets in Rapid Order Entry from an event with multiple Ticket Types. The correct line description will now display on the Invoice PDF when staff users purchase tickets in Rapid Order Entry for an event with multiple ticket Types.
Receipt Lines for Invoices contained blank Activation Dates when a Sales Order was converted to an Invoice. The Activation Date will now be populated when a Sales Order is converted to an Invoice.
When a Scheduled Payment was cancelled in GoCardless, the Has Error field became checked. The Has Errors field will no longer get checked when a Scheduled Payment is cancelled in GoCardless.
When the Item Line Description field was left blank when creating an Item, it populated with the Item Class Description instead of remaining blank. The Item Line Description field will now remain blank if left blank when creating an Item.
When an event was updated to the Closed Status, the system kept Scheduled Items active, but changed Items related to Scheduled Items to inactive. Both Scheduled Items and related Items will now become inactive when an event is Closed.
When an attendee registered for a Free event, a registration email did not successfully get sent to the attendee. Registration emails will now successfully be sent to registering attendees of Free events.
When a credit card payment was made in Rapid Order Entry, the Receipt’s Payment Type was populated by “CC“ instead of “Credit Card“ on the record. The Receipt’s Payment Type will now read as “Credit Card“ on the record.
When no pages were published to an event, the Preview in the Event Builder immediately navigates to the Ticket Selection page with the Registration Timer running. When the timer ran out, the user would be required to exit the Event Builder. The Registration Timer will now be removed when in Preview.
When Contacts had over 100 Badges, the CPBase Profile page failed to load. The CPBase Profile page will now display correctly for Contacts with over 100 Badges.
Due to security vulnerabilities identified from the use of the shared library synk.io version 4.17.4, the library version has been upgraded to 4.17.15.
When a Site page was created, the Page URL was missing the Page ID. The Page ID will now be included in the Page URL.
The Create Adjustment button was missing from the Invoice object in freshly created 19-R1 orgs. The Create Adjustment button will now be available on the Invoice object in new 19-R1 orgs.
Page Layout, 19-R1
When creating an Item, if the Line Description field was left blank, it populated the with the Item Class' description. The Line Description field will no longer inherit the Item Class description if the field is left blank.
When Price Rules with criteria used a multi-select picklist field and the “includes“ operator, the Price Rule was applied incorrectly. The Price Rule will no longer get applied incorrectly.
When Enable Contact Restriction was checked for a Free Event, it failed to be applied to the event. Contact Restriction will now get successfully applied to the Free Event when enabled.
Custom picklists displayed with the first value in the picklist selected by default in the Event Builder. No values will be selected by default in custom picklists in the Event Builder until a value is selected by the staff user.
When a field was made required on the page layout for Speaker, it would not be required in the New/Edit Speaker window in the Event Builder. Fields made required on the Speaker page layout will now be required as well in the New/Edit Speaker window.
Tickets with long titles became unresponsive in the Event portal on mobile devices. Tickets with long titles will now wrap successfully and be responsive in the Event portal on mobile devices.
When users unchecked Group Ticket Type when creating a ticket previously saved as a Group Ticket Type, any previously entered values in the Group Name and Quantity fields remained uneditable. The values in the Group Name and Quantity fields will now remain empty after deleting the values prior to deselecting Group Ticket Type.
The Badge Image URL formula started with HTTP instead of HTTPS, resulting in an error message that the Badge Image was not secure. The Badge Image URL formula will now begin with HTTPS.
The Hide in Portal checkbox field on Subscriptions did not hide Subscriptions in the Lightning Community, only in the CPBase portal. Subscriptions will now be hidden from view in both the Lightning Community and in CPBas portal when Hide in Portal is enabled.
Users were unable to search for items within Rapid Order Entry using the item’s SKU field. Users can now search for items in Rapid Order Entry using the SKU field.
In Lightning Experience, clicking Show/Hide Instructions in Rapid Order Entry when a form was attached to an item resulted in a component error. Users can now click Show/Hide Instructions without receiving an error.
Custom Event Statuses failed to display in the Status dropdown in the Event Builder. Custom Statuses will now list successfully in the Status dropdown in the Event Builder.
Guest users were able to bypass required fields on a Single Ticket Type Event. Guest users will no longer be able to bypass required fields on Single Ticket Type Events.
When Guest users signed up via the Self Registration/Create Account page, their Preferred Email was not successfully populated on their My Info tab on their Profile. The Preferred Email will now successfully get populated.
The Account field on the Attendee record for a secondary Contact displayed the Primary Contact’s Account instead of the secondary Contact’s correct Account. The correct Account will now be applied to the secondary Contact on the Attendee record.
When registration was transferred for an event, the Account field on the Attendee record and on the Contact failed to update. The Account field will now successfully update when registration is transferred to a different Attendee.
When an event was in Planned Status, the Refresh and Preview buttons failed to work. The Preview button will now display and the Refresh button will refresh successfully in the Event Builder.
When users clicked Add to Calendar on the event site and selected Outlook or ical, the event was not successfully added to either calendar type. Users can now successfully add events to the Outlook or ical calendars.
Badges failed to receive updates to the Expired Date when Assignments were Unassigned. Badges will now receive the correct Expired Date when an Assignment is updated and marked as Unassigned.
The “three dot menu element“ failed to display on custom designed pages when using mobile. The “three dot menu element“ will now successfully display on custom pages when using mobile.
When duplicate Contacts with duplicate email matching rules were assigned to a subscription, blank rows displayed on the Manage Members page for a subscription without throwing an error. Blank rows will no longer be created and an error message will now alert the user when a Contact they are attempting to assign is a duplicate.
Registration instructions for tickets with a form attached did not display correctly for mobile devices. Registration instructions for tickets with forms attached will now display correctly for mobile devices.
The --Please Select-- value on a form attached to a Ticket Type could not be successfully translated. The --Please Select-- value can now be successfully translated via Custom Labels.
When trying to create an Invoice in Rapid Order Entry, buttons for completing Invoice creation were grayed out. These buttons will now function correctly and allow the Invoice to be created.
The Manage Payment Methods action had a set height of 0% when added to the page layout, preventing staff users from using the action. The height has not been set to a viewable height so the action can be seen and used.
Forms with required fields attached to Ticket Types for Private Events failed to auto-populate or present the form to the invitee. The form will now present to the invitee when the invitation is accepted, and a validation is now in place to prevent any required fields from not being completed.
Creating a custom Community Menu Item with three consecutive capital letters (ex. ABC,) caused the title to display with spaces between each letter (A B C). The Community Menu Item name will now display correctly without additional spaces.
Duplicate waitlist records were created for events. Duplicate waitlist records will no longer be created.
On events with waitlisting enabled that reached over capacity, invited attendees got stuck in a loop after accepting the invitation and duplicate waitlist records were created. Users will no longer get stuck in a loop and will successfully get waitlisted without creating duplicate records.
In the Event Builder, the Venue Image Cropping Tool cropped images to 400px by 600px instead of the 400px by 400px laid out in the help text. The help text has been updated to say 400px by 600px instead of 400px by 400px.
When staff users clicked Refresh or Preview In in the Event Builder, the page got stuck buffering. Clicking Refresh will now successfully refresh the page, and clicking Preview In will successfully show a preview.
The Description field on Sales Orders was incorrectly mapped and sent to GoCardless as part of the interface. The Description field has been updated so it will not be sent to GoCardless.
When the user had multiple tickets in the cart and then opened and closed the Attendee modal, all existing tickets were deleted from the cart. Tickets will no longer be deleted from the cart when the Attendee modal is closed.
When a custom field was marked as required on the Contact, the system threw an error when adding an Attendee for an event with Create Contact for Attendees enabled. The custom required Contact field will get added to the New Contact Fieldset(s) CSV and will now display in the Attendee modal, preventing an error.
Staff users received an error when they clicked the Credit Memo button on an overpaid Invoice record. Users will no longer receive an error message upon clicking Credit Memo.
Clicking the More or Less values under a filter field resulted in the inconsistent maximizing and minimizing values. The minimizing and maximizing values now work correctly.
Despite declining an invitation, invitees were still redirected to event registration. Declined reservations will not be allowed to proceed with event registration.
Custom lookup fields on the Event Builder displayed values that overlapped with other fields when clicked. Custom lookup field values will no longer overlap with other fields in the Event Builder when clicked.
Clicking the Accept button more than once on an event invitation generated more than one ticket. Users are no longer allowed to click the Accept button more than once on an event invitation.
When registering for an event, forms completed for Sessions failed to link to the Contact and Account that completed the form. Forms completed for Sessions will no link successfully to the Contact and Account that completed the form.
On the Checkout page, there was no space separating Custom Labels, resulting in labels running together. Spaces will now successfully separate Custom Labels on the Checkout page.
The rich text editor in the Event Builder failed to render bullet points properly. Bullet points will now display properly in the rich text editor.
The Community Group’s Activation Date field updated to the current date whenever the Community Group was edited. The Activated Date will no longer get updated when the Community Group is edited.
Attendees added to a Private Event in the Event Builder were prematurely given a status of Invited before receiving an invitation. Attendee status will now be Not Invited until an invitation is sent.
Custom event pages would not display in the Safari browser. Users can now navigate to custom event pages using the Safari browser.
When a user attempted to purchase an item from the portal, the Entity field was not populated. The Entity field will now be populated when a user attempts to make a purchase.
Previously blank custom fields on the Contact were filled in when the user clicked Change to edit the field set from the Community. Those fields then remained blank when edits were saved. Populated value results in custom fields will now successfully save when edited.
When registering in the Community for a multi-ticket event, the login page displayed a tab title of “undefined”. The login page will now display a tab title of “Login - [event name]”.
The text cursor became clickable when users hovered over the event name or date on an event’s listing page. The cursor will no longer be clickable on event listing pages.
Custom statuses did not appear in the dropdown field in the Event Builder and staff users could not move the event into those statuses. Custom statuses will now display in the Status dropdown in the Event Builder and staff users can successfully move their events into their custom statuses.
Fields marked as required on the Attendee object failed to show as required during event registration, allowing registrants to bypass them. Required fields will now show as such during event registration, and registrants will now be able to bypass them.
When an Attendee registered for an event, the Sent Notification checkbox would get set to false, and the workflow rule would fail to execute, resulting in the Attendee not receiving a registration email. The Sent Notification checkbox will now get set to true when an Attendee registers for an event, causing the workflow to successfully execute and the Attendee to receive a registration email.
When an event with Account Match Criteria = Domain Matching was marked as a Free Event, the domain matching method failed and users were added to a Fonteva Person Account or Bucket Account when registering. New Contacts will now be related to the relevant Account with a registered domain.
In Free Events with Enable Contact Restriction enabled, registrants were still able to register more than one Attendee per Contact due to no Sales Order or Sales Order Line being created for Free Events. Contact Restriction will now work as designed for Free Events when enabled, and registrants will only be able to register one Attendee per Contact.
When Venue addresses were in Denmark, which uses a different address format, the address format would change to an incorrect format when the event was added to the calendar. The correct format will now display for Denmark addresses when the event is added to the calendar.
When Ticket Types were grouped to a ticket block, images attached to the Ticket Types failed to display on the event page in the Community. Images attached to Ticket Types grouped to a ticket block will now successfully display in the Community.
Staff users received an error message in the Event Builder when the Agenda page had over 50 Schedule Items. Staff users will no longer receive an error message when the Agenda has over 50 Schedule Items.
When the Contact object had custom required fields, the system would throw an error during event registration when adding an Attendee if Create Contact for Attendees was enabled due to the custom required Contact field not displaying. The custom required field will now show as part of the fields to fill out for creating the Contact, and users will no longer receive an error.
The +Add button did not display consistently in the Attendee modal while adding a new Attendee in event registration. The +Add button will now display consistently in the Attendee modal during event registration.
When staff users renewed a subscription, the Sales Order Line End Date field failed to calculate correctly. The End Date field will now calculate correctly when a subscription is renewed.
Contact Restriction failed to prevent an invited Attendee from RSVPing multiple times for the same invitation when capacity was reached for the event and waitlisting was enabled. Duplicate waitlist entries will no longer get created for events.
Fonteva 20 Spring: Upgrade Checklist Part 1
Fonteva 20 Spring Release: Schema Updates