2018-R1 Release Notes

For more information on Fonteva's new features for 2018-R1, please visit the2018-R1 Release Guide for an overview of this release's new features.

Updating to 2018-R1:

It is recommended you test 2018-R1 in a sandbox before you upgrade in your environment.

Page Layout Updates:

Buttons:

The following buttons and actions were added in 2018-R1. Please assign the 2018-R1 page layout to the appropriate profile when updating to R1. Alternatively, if you have custom configurations on your page layouts, please add the new buttons and actions below manually. Make sure your buttons in Classic are also quick actions or Mobile & Lightning Actions in Lightning on the Object Record Layout.

Contact Object Record:

Classic Buttons: Change the New Address button to the Manage Addresses button in the Known Addresses related list. Change the New Payment Method button to the Manage Payment Methods button in the Payment Methods related list.

Lighting: Add the Rapid Order Entry, Manage Addresses, and the Manage Payment Methods actions.

Account Object Record:

Classic Buttons: Change the New Payment Method button to the Manage Payment Methods button in the Payment Methods related list.

Lightning: Add the Rapid Order Entry, Manage Addresses, and Manage Payment Methods actions.

Attendees Object Record:

Classic Buttons: Add the View Ticket button.

Lightning: Add the View Ticket action.

Business Groups Object Record:

Classic Buttons: Add the New Gateway button to the Payment Gateway related list.

Lightning: Add the Manage Payment Gateway action.

Event Categories - Events Related List:

Classic Buttons: Add the New Event button.

Lightning: Add the New Event action.

Events Object Record:

Classic Buttons: Replace the Event Builder button with the Edit button.

Lightning: Replace the Event Builder quick action with the Edit action.

Directories Object Record:

Classic Buttons: Replace the Directory Builder button with the Edit button.

Lightning: Replace the Directory Builder quick action with the Edit action.

Forms Object Record:

Classic Buttons: Add the Form Builder button.

Lightning: Add the Form Builder action.

Invoices Object Record:

Classic Buttons: In the List View, add the Apply Payment. In the Detail View add Apply Payment, View Invoice, Write Off Balance, and Create Credit Memo buttons.

Lightning: In the Detail View, add the Apply Payment, View Invoice, Write Off Balance, and Create Credit Memo actions.

Items:

Classic Buttons: Add the New Price Rule button to the Price Rules Related List, the New Package Items button to the Package Items related list, the New Subscription button to the Subscription Plans related list, and the New Renewal Path button to the Renewal Paths related list.

Lightning: Add the Manage Price Rules, New Package Items, Manage Subscription Plans, and Manage Renewal Paths actions.

Access Permissions:

Classic Buttons: Add the New Access Permission button to the Access Permissions related lists for all records with Enable Access Permissions status pages (Items, Schedule Items, Ticket Types, Sites, etc.) This button will have to be added manually instead of assigning 2018-R1 page layouts to profiles.

Lightning: Add the Manage Access Permissions action.

Media Collections: Media Assets:

Classic Buttons: Add the New Media Asset button.

Lightning: Add the New Media Asset action.

Subscriptions Object Record:

Classic Buttons: Add the Edit, Renew, and Amend Suspension buttons.

Lightning: Add the Edit, Renew, and Amend Suspension actions.

Receipts Object Record:

Classic Buttons: Add the Create Refund, Process Refund, and Customer Receipt buttons.

Lightning: Add the Create Refund, Process Refund, and Customer Receipt actions.

Sales Order Object Record:

Classic Buttons: Add the Process Payment, Rapid Order Entry, Send Proforma Invoice, and Direct Debit Checkout (if Direct Debit is installed) buttons.

Lightning: Add the Process Payment, Rapid Order Entry, Send Proforma Invoice, and Direct Debit Checkout (if Direct Debit is installed) actions.

Sites Object Record:

Classic Buttons: Add the New button to the List View. If already there, it will be automatically overwritten to Fonteva’s custom UI.

Lightning: Add the New quick action. If already there, it will be automatically overwritten to Fonteva’s custom UI.

Theme Object Record:

Classic Buttons: Add the Edit and New buttons to the List View. If already there, they will be automatically overwritten to Fonteva’s custom UI.

Lightning: Add the Edit and New actions to the List View. If already there, they will be automatically overwritten to Fonteva’s custom UI.

Fields:

The following fields were added in 2018-R1. Please assign the 2018-R1 page layout to the appropriate profile when updating to R1. Alternatively, if you have custom configurations on your page layouts, please add the new fields below manually.

Deprecated Fields:

Please ensure these deprecated fields are removed from the associated object’s page layout.

Performance of Lightning Components:

The performance of Lightning Components when called from Salesforce Classic is noticeably slower than in the Lightning Experience. Lightning Components will run faster in the Lightning Experience and once loaded the first time, will stay in the cache so they don't need to be loaded every time.

Events: Key Focus Area For Upgrade

Please note that special attention should be paid to the Events area of the product prior to upgrade. There are changes in 2018-R1 that will impact all events, including any that are currently "in-flight." It is highly recommend that you upgrade in a sandbox environment and do a thorough review of your events prior to moving forward with a production upgrade. The primary area of focus should be on the look and feel of the Event site. If you took advantage of the custom CSS feature to alter the look and feel of the site, it is likely that this CSS will need to be updated to work correctly with the updated site. All other changes, including updates to the Registration Flow and Event Builder, will also be immediately available on upgrade. So, if you have a live event in progress, those changes will be available to your attendees. Testing in a sandbox is always recommend, but in this case we wanted to stress the importance of it. If you do not have a sandbox environment, please try to work the timing of the upgrade so you do not have a live event in progress. If that is not possible, try for a time when traffic will be at its lightest.

Critical Update: Line Item Receivables

Line Item Receivables will require a Critical Update to apply this feature in 2018-R1. However, before applying the Critical Update, all Items should be updated to ensure they have the correct Accounts Receivable. Time should also be taken to define Payment Prioritization to Items before updating. Note that once a Critical Update is applied, only Invoices created post-update will start utilizing LIR.

Critical Update: Known Addresses

Upon updating to 2018-R1, Visualforce checkout pages will face updates in the portal for the Store. This critical update will enable the use of Known Addresses in the VisualForce checkout page. The scope of this update does not include the Events checkout page, and will only affect the VisualForce checkout page. This critical update is intended for customers with added customizations for the portal checkout page. Lightning and staff user interface checkout will remain automatic. A migration script is also included. It will run through all Contacts and create a Known Address for all Contacts. This script is located under Spark Admin: Charge. This migration script should be manually run off hours.

Developer Features and Improvements:

Developer Documentation:

New documentation is available geared towards developers. Developers will have in-depth instruction on Fonteva’s API Services, Framework Lightning Components, Registered Objects, Unit Testing, and more.

Developers also now have access to Fonteva’s Dev Docs. This is an extensive glossary of Lightning Components, Apex Classes, VisualForce Components, Custom sObjects, Custom Labels, and Modals used in Fonteva.

You can access the Developer Documentation here and Fonteva's Dev Docs here.

Secure Configuration Region for Amazon Web Services Content Storage:

Fonteva has moved to a new strategy for using Amazon Web Services for the storage and retrieval of Forms attachments. This updated design allows for the use of geographically located AWS S3 buckets to conform to local laws in certain countries and improves security through the use of the AWS "timed link" feature. A timed link is an artifact provided by Amazon to provide increased security when accessing S3 storage. Fonteva is now using timed links to secure the access to our content. The actual execution of the timed link technology is invisible to the user, providing a seamless experience.

Cookie Acceptance:

To support GDPR requirements, customers can now display a modal to Portal users ensuring they accept the use of cookies on the site. They can customize this message and designate a redirect URL for users that reply "No" to accepting cookie usage. Known users that reply with a positive response will have their response recorded so the modal will not appear for them.

Technical Improvements:

• InputFields will now auto-detect the field type entered and render it correctly. The user will provide the SObject name and the field name. InputFields will then autorender based on the type and pull any relevant information from the object. (For example, picklist values.)

• Developers can now disable or bypass triggering and routing rules on certain DMLs when it is not required to execute Framework triggers. This helps limit SOQL and prevents hitting the SOQL Governor Limit.

• The TinyMCE rich text editor has been replaced with the QuillJS rich text editor. File upload to S3 has been added to the QuillJS editor so uploaded files will display in the rich text.

• Users can configure a cookie acceptance message to display for Member Portal users. Customers can enter this message in any language and it can be configured to include a redirect URL.

• All Payment Types have custom metadata types.

• The script registry will track which scripts have run. Each time a script runs, an entry will be added to a custom setting logging that the script ran. This will prevent the script from running again after upgrading.

• All Fonteva Apps and Tabs will install with the Fonteva Platform and Lab Packages.

• New installs will now have the following critical updates enabled:

• Assemble : Enable String Date Time Fields

• Engage : Enable Extended Group Fields

• Spark : Dispatch API calls on triggers

• The Access Manager has been updated to be more granular.

• Jquery has been upgraded from v2.2.4 to v3.3.1 for Framework and PagesApi.

Schema Updates:

New Schema:

Deprecated Schema:

Bugs Resolved By 2018-R1:

The following bugs were resolved through 2018-R1. For information on previously resolved bugs, please refer to the 2017-R2 patch releases.