You've all heard of the GDPR, right?  New laws in certain countries making sure that websites alert users when cookies are being used, privacy policies, etc.

We've now added to the CMS options, the ability to place a cookie consent banner on your site!  You've seen these - they are popping up on websites all over letting you know the site is using cookies. Then users dismiss them, and at least know that this site (like almost all sites these days) is using cookies to store information :-)

In your CMS, you'll now see a new option:

Go to Blocks / System Forms / Cookie Consent Banner if you wish to activate the banner:

This is off by default, but you can click 'enable cookie consent" to turn it on.  You can set the background color and the text color as you wish.  

We pre-populate a default cookie consent policy which is:

"Our website uses cookies to improve your user experience. If you continue browsing, we assume that you consent to our use of cookies. More information can be found in our Privacy Policy."  The words 'privacy policy' are linked to the page /privacy-policy on your site.

You can edit the text that appears as you wish.  (Note however that if you edit it, you can't restore the original text, so keep a copy of it.

Here's what the banner looks like on your site when its enabled. It appears on the bottom of the page and once dismissed (by clicking the x) it will not appear again in that browser for about a year.  So its a one-time notification.

When adding a date or date/time field to a HOC form (standalone or as part of the ARS), you now have additional validation options for the dates that can be entered into the form:

1. Allow Time  (select Yes if you wish both a date and time to be supplied)

• You can choose the format you wish the time to be entered in if you select 'yes

2. Assign Current date/time by default   (will pre-enter today's date in the form).  Can be edited by the user if they don't wish to use today's date.

3. Allow only Future Dates.   When selected, you also have the option of allowing the current date as well

You can also set a limit to the maximum days in the future that can be entered.  

4. Allow only past dates.   This offers the same options when selected....

5. Validation depends on another date field

You can make a date field in the form dependent on the answer given to another date field in the form.   If enabled, you select a logical operator (i.e. greater than, less than or equal), and which field it is dependent on:

These validation options give you greater control over what dates can be entered into a form you create, and allow for much more robust forms that use dates.

ARS workflows previously weren't mapping to SF when a team signed up (because you were actually signing up many people.  So the mapping info was lost.  Now, if a team captain signs up a team to an opportunity with an ARS workflow associated with it - the info captured in a form will be mapped to the team captain's connection.

For clients who have set the registration minimum age to an age above 13 -- the check-in kiosk will respect that age validation if you are using guest registration configuration 4. (allow guests to register themselves).