The payment component in custom forms now allows recurring billing or auto renewal when using Stripe or PayPal.  You'll now see an option to set up recurring billing and the frequency. The frequency can be the following:

• Day
• Week
• Month
• Year

You'll also see an option to map the subscription information to a text field in Salesforce.

The end user will see a checkbox field that allows them to indicate if they want to opt into a recurring billing.

This is typically useful when collecting payments for memberships, but can easily be applied to other use cases.

Changed the message: "The action cannot be completed because there is at least 1 member that requires an adult participation" to "The action could not be completed because one or more minors participating require an adult to participate."

The message applies to when a team captain attempts to remove all of the adult team members from a  volunteer opportunity with minor team members.

1. Changed the tooltip from "Indicates multiple events" to "Indicates multiple locations"
2. Improved how Google Maps loads to prevent display errors.

Custom Session Variables page visibility is now accessible to all CMS admins. Now you can configure page visibility based on custom variables that you create from Salesforce. A Custom Session Variable can essentially be any field on a Salesforce Object.

Added the transaction amount and label to the payment component's transaction page. This improvement provides clarity and consistency throughout the payment process and receipt.

Improved custom forms to allow the keyboard tab function to direct users to the next field instead of having to double press the tab key.

The date placeholder defaults to the current date. In some cases this may be confusing so we implemented an option to hide the placeholder in custom forms.

Fixed an issue that caused sections in a form with logic to remain hidden after criteria was cleared.

Fixed an issue in the sharing portal that caused the start date and time of a connection to change after selecting the end date and time field. This issue occurred when the time in the start date and time field was changed.

Fixed the error message when entering a different password on the registration page. The error will say "This field must be equal to the field Password. "

Fixed an issue that prevented custom forms from loading the correct object that's associated with mapped fields.

Fixed an issue that caused the error messages on mobile to overlap the corresponding field.

Fixed an issue that prevented the selection of the current date in a form.

Fixed an issue that prevented CMS Admins from changing an existing label and value in the payment component.

Fixed an issue that caused filtering by a p parameter to fail.