Page tree
Skip to end of metadata
Go to start of metadata

For more information on Fonteva's new features for 2018-R1, please visit the 2018-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.

Important Before Updating

  • Before you upgrade, check Deploy Metadata from Non-Certified Package Version via Apex in Apex Settings.


Important Before Updating

2018 R1 introduces the use of the Custom Payment Type model for all payment types. When upgrading an existing environment, please ensure that the following payment types are created and enabled:

  • Credit_Card
  • ECheck
  • Offline
  • PayPal
  • Proforma Invoice
  • Saved Payment Methods


Important After Updating

  • Run Access Manager to enable access to new Objects.
  • Please ensure you also run Access Manager for Guests.
  • Please update your page layouts with the following buttons/actions and fields as recommended below.

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.

Note

You can name quick actions anything you want, but we recommend maintaining the name Fonteva has given so it’s as clear as possible what the quick action does.


Spark Admin

In Lightning, use a Lightning Tab for Spark Admin. Go to Setup>tabs>get Fonteva Framework Tab. Otherwise, Marketplace will not load in the Spark Admin tab.


Important

Adding buttons on Classic View does not carry over to Lightning Experience and vice versa. Add from Mobile and Lightning Actions on the Page Layout Editor to add to Classic and Lightning simultaneously from the selections available there.


Known Address Related List

The New button on the Known Address related list is a Javascript button that is not supported in Lightning Experience. Please remove the New button and add the Manage Known Addresses Lightning Action for all instances of the Known Address related list.


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.

Note

This object is only available if Directories is enabled. A 2018-R1 page layout is not available to assign to profiles for Directories, so the changes must be made manually.


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.

ObjectNew Fields
ePayment Line
  • Invoice Line (Invoice_line__c)
Item
  • Payment Priority (Invoice_Payment_Priority__c )

  • A/R Account (AR_Account__c )

Invoice Line
  • A/R Account (AR_Account__c )

  • Amount Paid( Amount_Paid__c )

  • Amount Refunded( Amount_Refunded__c)

  • Adjustments( Adjustments__c )

  • Balance Due( Balance_Due__c )

  • Parent Invoice Line( Invoice_Line__c)

  • Payment Priority( Payment_Priority__c)

  • Credit Memo( Credit_Memo__c )

  • Invoice_Line_Lookup__c

Known Address
  • Name (Name__c )

  • Street (Street__c)

  • City (City__c )

  • State (Province__c )

  • Country (Country__c )

  • Postal Code (postalcode__c )

  • Additional Details (Additional_Details__c )

  • Is Default (Is_Default__c )

Receipt Line
  • Contact (Contact__c)

  • Invoice Line (Invoice_Line__c)

Custom Payment Type
  • Instructions (Instructions__c )

  • Payment Gateway (Payment_Gateway__c )

Event Status Page
  • Enable Access Permissions (Enable_Access_Permissions__c )
Access Permissions
  • Event Status Page (Event_Status_Page__c )
Event
  • Logo Image (Logo_Image__c )
Schedule Item
  • Disable Registration (Disable_Registration__c)

  • Hide During Registration (Hide_During_Registration__c )

  • Required For Registration (Required_For_Registration__c )

  • Payment Priority (Payment_Priority__c )

  • A/R Account (AR_Account__c )

Sponsor
  • Is Featured (Is_Featured__c )
Sponsor Package
  • Payment Priority (Payment_Priority__c )

  • A/R Account (AR_Account__c )

Speaker
  • Is Featured (Is_Featured__c )
Ticket Type Schedule Item
  • Disable Registration (Disable_Registration__c)

  • Hide During Registration (Hide_During_Registration__c )

  • Required For Registration (Required_For_Registration__c )

  • Ticket Type (Ticket_Type__c )

  • Schedule Item (Schedule_Item__c )

  • A/R Account (AR_Account__c )

Ticket Type
  • Payment Priority (Payment_Priority__c )

  • Manage Agenda By Ticket Type (Manage_Agenda_By_Ticket_Type__c )

Track

  • Color (Color__c )
Venue
  • Description (html_description__c )

Deprecated Fields:

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

ObjectDeprecated Field
Community GroupEnable_Access_Permissions__c
SponsorIs_Featured__c
SpeakerIs_Featured__c
VenueDescription__c


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:

PackageObjectNew FieldNew Object
OrderApiePayment_Line__cInvoice Line( Invoice_line__c) 
OrderApiItem__c

Payment Priority( Invoice_Payment_Priority__c )

A/R Account( AR_Account__c )


OrderApiInvoice_Line__c

A/R Account( AR_Account__c )

Amount Paid( Amount_Paid__c )

Amount Refunded( Amount_Refunded__c),

Adjustments( Adjustments__c ),

Balance Due( Balance_Due__c ),

Parent Invoice Line( Invoice_Line__c),

Payment Priority( Payment_Priority__c),

Credit Memo( Credit_Memo__c ),

Invoice Line (Lookup) (Invoice_Line__c)


OrderApi

Name( Name__c ),

Street( Street__c),

City( City__c ),

State( Province__c ),

Country( Country__c ),

Postal Code( postalcode__c ),

Additional Details( Additional_Details__c ),

Is Default( Is_Default__c )
 Known_Address__c
OrderApiReceipt_Line__c

Contact( Contact__c)

Invoice Line (Invoice_Line__c)

 
OrderApiCustom_Payment_Type__c

Instructions( Instructions__c ),

Payment Gateway( Payment_Gateway__c )  

EventApiEvent_Status_Page__cEnable Access Permissions(  Enable_Access_Permissions__c ) 
EventApiAccess_Permissions__c Event Status Page( event_status_page__c )
EventApiEvent_Status__c SYSTEM(Filter_Transition_Criteria__c ) 
EventApiEvent__cLogo Image( Logo_Image__c ) 
EventApiPrice_Rule__cSYSTEM( Is_On_Site__c ) 
EventApiSales_Order_Line__cSYSTEM( Is_Required_Schedule_Item__c ) 
EventApiSchedule_Item__c

Disable Registration( Disable_Registration__c),

Hide During Registration( Hide_During_Registration__c ),

Required For Registration( Required_For_Registration__c ),

Payment Priority( Payment_Priority__c )

A/R Account( AR_Account__c )


EventApiSponsor__cIs Featured(Is_Featured__c ) 
EventApiSponsor_Package__c

Payment Priority( Payment_Priority__c )

A/R Account( AR_Account__c )


EventApiSpeaker__cIs Featured( Is_Featured__c ) 
EventApi

Disable Registration( Disable_Registration__c),

Hide During Registration( Hide_During_Registration__c ),

Required For Registration( Required_For_Registration__c ),

Ticket Type(Ticket_Type__c ),

Schedule Item( Schedule_Item__c )

A/R Account( AR_Account__c )

Ticket_Type_Schedule_Item__c
EventApiTicket_Type__c

Payment Priority( Payment_Priority__c ),

Manage Agenda By Ticket Type( Manage_Agenda_By_Ticket_Type__c )
 
EventApiTrack__cColor( Color__c ) 
EventApiVenue__cDescription( html_description__c ) 

Deprecated Schema:

PackageObjectDeprecated Field
PagesApiCommunity_Group__c 

Enable_Access_Permissions__c

LightningLens  Sponsor__c, Speaker__c

Is_Featured__c

EventApiVenue__cDescription__c

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.

Bug DescriptionComponent
When creating and/or editing a complex Join Process that stemmed from a marketing step with multi item-based navigation, users received the following error when they clicked Proceed to Next Step: "This page has an error. You might just need to refresh it. Assertion Failed!: ComponentService.createComponent(): 'type' must be a valid String. : false Callback failed: apex://joinapi.ItemFlowController/ACTION$updateItemPage Failing descriptor: {joinapi:JoinProcessBuilderTemplate}".

This has been resolved so the following step loads as normal when users proceed to the next step.

Join Process
When users ran the rollup parent OrderApi_Item_Classc and child OrderApiAssignment_c in a batch context, a System Log would be created with a validation error. This has been resolved so the batch runs without a System Log being created.Spark Framework
Junction Objects without a Name or AutoNumber field and set as a Related List for Directories would throw an unexpected token: 'null'Class.DRCTS.SearchDirectoriesController.getRelatedListObj: line 129, column 1.
Users can now view the account detail view along with the AccountContactRelation records in the Related List.
Directories
Users could not successfully change the Shipping Address on the Checkout Page. The Shipping Address will now successfully be updated when a user changes it on the Checkout Page.eStore
The system would try to update a Paid Invoice's Schedule Payment amount despite being already processed and try to update its amount, resulting in a System Log getting created. This has been resolved so a System Log is not created.eBusiness
A Subscription created via a renewal path did not carry forward Enable Auto-Renew details from the old Subscription. This has been resolved so the new Subscription carries forward the Auto-Renew capabilities form the previous Subscription.eBusiness
If a Subscription Plan gives users the option to Auto-Renew and the Payment Method is not required, the user had to remember to save the Payment Method. This has been resolved so the Payment Method is saved.eBusiness
Skip logic did not work when added to a Form for a Lightning Event and users could not complete the Form. The same Form worked fine in Visualforce. This has been resolved so Skip Logic works successfully and users can complete the Form.Engage: Communities
Internet Explorer 11 users could not see members assigned to their Subscriptions when they logged in to the Portal. IE11 users will now see the members assigned to their Subscriptions in the Portal.Salesforce General
When a Sponsor Package was purchased from the Store, the system would override field labels and effect the Store Frontend as well as Receipts. Field labels will no longer be overridden.ePackage, Events
The Expiration Date field for expired Subscriptions or those in Grace Periods would continue to be updated every night instead of not being updated. The Expiration date will no longer be populated for Subscriptions that are expired in a Grace Period.eBusiness
When users returned to change their payment method to an Invoice when creating an ROE, no Invoice or Invoice record would be created when the Sales Order is posted. This has been resolved so the Invoice and associated record are created successfully.Rapid Order Entry
The Lightning Force Checkout pages for frontend and backend have been improved so live gateway errors are more user friendly.eStore
When a Community user attempted to search for a member using the search term "Dr" in the new Directories functionality, an internal server error would result. Users can now search the term "Dr" and receive results.Directories
When adding an optional Package Item in Rapid Order Entry, the user would receive an error message. Users can now add optional Package Items to their Rapid Order Entries without receiving an error.Rapid Order Entry
The Preferred Phone and Home/Mobile Phone field values were removed when there was Skip Logic in the Form. This has been resolved so the Phone fields will be populated.Engage: Communities
When no Default Site was configured or Site URL Parameter provided for Join Process, Create Guest Login will fail without producing an error message. An error message will now launch successfully when this occurs.Join Process
After purchasing an Item from a Store, the Receipt did not always fully display due to the iFrame not resizing properly. This has been resolved so the iFrame resizes and displays the Receipt properly.eStore
In a Community with a site prefix, the Cover Photo did not always render. The Cover Photo now renders correctly.Engage: Communities
In Rapid Order Entry, users could not override the price to an amount over $5000.00. Users can now override the price to any amountRapid Order Entry
When a custom field matched the API name of a Fonteva managed package (excluding the Namespaceprefix) users would get a duplicate field selected error. Users will now be able to complete checkout without receiving an error.Spark Framework
When users changed a Subscription from a Termed Plan to a Calendar Plan, the charge total came from the previous Termed Plan Sales Order instead of the Calendar Plan and would not be prorated. When users change a Subscription from a Termed Plan to a Calendar Plan, the charge will be prorated.eBusiness
Featured Speakers would not display for Lightning Events if any library was added to Head Markup. Featured Speakers will now display if a library is added to the Head Markup.Events
In the Venue tab, only the Venue Map would show up. Now both the Primary Venue and the Venue Map will appear.Events
Users were unable to add links to Images in the Event Overview. Users would click the image, but the browser would not navigate to a link URL. This has been resolved to the Image URLs perform as expected when clicked.Events
When users clicked on a Badge to view it in the Contact detail view, the user would be taken to a blank Community page to the login page instead of to the Badge in the Partner Community with the site prefix. This has been resolved so clicking the Badge opens a page in the Partner Community with the Site Prefix.Engage: Communities
Users were unable to add a Banner Image into Event Builder in a Community with a site prefix. The image uploader would get stuck at the loading icon. Users are now able to add and load the Banner Image successfully.Events
The Form response for a Skip Logic question would be retained even after the user went back to change the answer. This has been resolved so the old response is no longer retained when it is changed.Engage: Communities
In orgs that have taken the Invoice/Receipt custom field Critical Update, if a partial payment is applied against an Invoice, the Total will display at the bottom of the Invoice instead of a Balance Due. This has been resolved so the Balance Due is displayed.eBusiness
When Allow Multiple Entries is checked on a Form with a Field Group mapped to a custom object, the hidden field value is not captured in the Form response. The hidden field value is now captured when Allow Multiple Entries is checked.Engage: Communities
When a Form was loaded from an already existing record, Fonteva attachment fields did not load the existing link. Instead, it was left blank. The attachment link now loads successfully.Engage: Communities
On Contact records, the Business Phone and Work Email fields would populate the Mobile Phone and Personal Email fields despite being left blank. The Mobile Phone and Personal Email fields will no longer automatically populate with the Business Phone and Work Email fields.eBusiness
When the Shipping Address was left blank for a Business Address for an Account, the system would automatically populate the Shipping Address fields to match the Billing Address fields. The Account addresses will now only be synced when blank and when Individual Accounts is enabled.eBusiness
Users could still accept an invitation to attend an invite-only event even after the user's invitation was cancelled. This has been resolved so invited users with cancelled invitations cannot register for the event.Events
When users purchased an event ticket through the Portal and then purchased a Session through Rapid Order Entry, the Registration Item for the Ticket Type would be created, but not for the Session. Registration Items are now successfully created for both the Ticket Type and the Session and attached under the same Attendee.Events

A previous limit prevented more than 100 Schedule Items from being created. This is resolved so users can surpass 100 Schedule Items.

Events
Auto-Renewal would not complete for a Sales Order of $0. The user would receive the following message "No API Response". The renewal process will now complete successfully and the Subscription will be extended per the Sales Order Line for a $0 SO and Schedule Payment.eBusiness
Users were not being redirected to the Receipt after a successful payment was processed for a Credit Card. Instead they were being redirected to the Sales Order. Users will now be redirected to the Receipt after a successful credit card payment.eBusiness
Users were unable to submit a Form with a required Date Field if they manually entered the date instead of using the date picker. Users are now able to successfully submit the Form.eBusiness
Error messaging has been improved for Rapid Order Entry so it is more consistent in appearance.ROE
If users attempted to process an ROE with an invalid Credit Card number, an error did not display. An error now successfully displays when users attempt to process an invalid Credit Card number.ROE
Users did not receive the Validation Rule message on receipts over 20 days old they attempted to refund. This has been resolved so users will receive the Validation Rule message when they attempt to refund a transaction older than 20 days.eBusiness
The Auto-Renewal Schedule Payment Lines were set to $0 Total instead of the price on the Sales Order Line, leading to incorrect Accounting entries. The Schedule Payment Lines Total will now match to the associated renewal Sales Order Line.eBusiness
When a user chose Enable Auto Renew upon renewing their Subscription, the Subscription would not have a Payment Method reference. The Payment Method will now be references on the Subscription.eBusiness
Members renewing Subscriptions would end up with 2 terms, and the incorrect term would be set as Is Active. This has been resolved so the correct term is set as Is Active.eBusiness
In the Event Builder, the Display Name field did not let users enter characters as designated in the field's settings. Users can now enter characters as defined through the field's settings.Events
Within the step Product Flow, when accessing a Filter Criteria, the value would display incorrectly. This has been resolved so the value displays correctly.Join Process
Product pages in Join Process displayed inactive Subscription Plans. This has been resolved so only active Subscription Plans will display.Join Process
When renewing a Subscription, the Subscription would set the current date as the Start Date instead of the correct Start Date. This has been resolved so the current date is not set as the Start Date.eBusiness
In an event with Search All Contacts enabled and member/non-member pricing rules, if a member purchased a ticket with an Attendee with a Member contact and during the process updated the Attendee to a Guest Contact, the price remained the same. This is resolved so the price will update according to the eligibility of the Attendee.Events
When an expired one year membership was renewed, the new term end date added one additional day. Renewing a one year membership will no longer add an extra day.eBusiness
Users were able to accept an invitation for an invitation-only event multiple times. This has been resolved so the user can only register once for an invite-only event and will receive notification that they are already registered if they attempt to register again.Events
The time for each Sessions in an event did not match with the Session times displayed in ROE. This has been resolved so the times for Sessions match.ROE
Rendering the OrderApi__Receipt page with the Virtualforce method getcontactAsPDF() included CSS in the PDF header and did not render the logo correctly. The PDF in the email now looks exactly the same to the Receipt page with CSS and with a correct logo.eBusiness
When a guest registered for an event, the Invitation Status and Last Invitation Email Sent fields would be populated on the Attendee record despite not being an Invitation Only event. These fields will no longer be populated for non-invitation events.Events
Community users without a Contact reference were not able to register for events. These users can now register successfully for events.Events
If a guest registered for more than one ticket for an event, duplicate Contacts would be created. Contacts will now be matched instead of creating duplicates.Events
After installing 2017-R2 packages, users could not install the DDapi package. This is resolved so the DDapi package install is successful.Direct Debits
On a Wizard-style Form with multiple field groups and fields,the data entered on the Form would be submitted every time the user clicked Next. This is resolved so the data is only updated when the user clicks Submit on the Form.Engage: Communities
Every tine a community user logged in to the system via cpbase__custom__login, a new Sales Order would be created on the Contact despite an SO created from a previous login. The existing SO will now be used instead of creating a new SO every time a user logs in.Engage: Communities
The Community's footer overlapped the Manage Registration tab, specifically the view when updating or viewing the Attendee Registration form. This is resolved so the page automatically lengthens to accommodate the form length.Engage: Communities
When adding a Form to a Ticket Type, the Form Heading text did not display anywhere for a Lightning Event. The Form Heading field now will only be available for Conference Events in the Event Builder.Events
Account Price Rule limits did not work across multiple orders when the first type of order was an Invoice.Account Price Rules will now apply correctly across multiple orders.eBusiness
When the number of characters entered into the Description field exceeded a limit, the way components render on the frontend were affected. This is resolved so no rendering issues are encountered.Events
Early-Bird and On-site Price Rules would deactivate other non-default Price Rules. Early-Bird and On-site Price Rules will no longer cause other Price Rules to deactivate.Events
When the Badges Visualforce component was added to the Page layout, staff users were unable to save the Contact Record and would receive and error. Users are now able to save the Contact Record upon editing if they remove the Visualforce Component.eBusiness
Users were unable to see the values selected via checkbox during Event Registration when viewing Registration Forms in Manage Registration. Users' submitted values will now display in Registration Forms.Events
When a Tribute option was added to a Campaign, the managed package Field Set DonorApi__Default_Donation_Memory_Fields did not include a Country field. The Country field is now included.Campaign Pages
Schedule Items would price by Registrant instead of by Attendee, resulting in incorrect pricing. Schedule Items will now be priced by Attendee.Events
Images for Shipping Items would display in different sizes in Checkout. Images for Shipping Items will now display in their correct sizes in Checkout.eStore





  • No labels