1. Improved email filtering flexibility
Email filters can now have multiple values selected within the same drop down, whereas before multiple emails would have to be created e.g per session.
In the last release, we presented the list of options available to enumerated fields, we now allow these email filters to be multi selectable, applying an OR operator within the set of values selected.
We also added more operators to the Session filter - namely, contains and does not contains.
2. Improving published website performance
We are continuing to make steps forwards in hosting our published sites on AWS. This is not yet released globally and still being tested.
Tackled performance, hosting https and payment sites, bugs in switching languages, sessions not being displayed etc.
3. Published Website Validation UX
We no longer check multiple validation categories after another, forcing website visitors to go back and update various inputs repeatedly, instead we now validate all categories and present the list of issues at once.
4. Editing records no longer wipes their photos or waivers
Squashed a UI bug causing engagements to have photos or waivers wiped
5. Other Bug fixes
- Performance and Fine tuning with technologies
- Video settings getting mixed with other video fields
- Integration analytics showing deleted SSI's that haven't been run
- Session Filters not working on IE
Known Issues:
1) Email filters:
When adding fresh filters on toggle fields, or editing and converting a previously created filter from is blank/is not blank to equals/does not equals, either no options are presented or 'no results found' is presented respectively.
Workaround: Add the same filter rule again. Delete the first one.
2) If the email has only one filter, the "Send if" operator which is by default set to "All" changes to "One or More" automatically after save and refresh. This was an existing issue but got highlighted with email multi-select feature.
3)
Email filters UX:
Multi selecting filter values applies an OR operator. When used in conjunction with 'Does not equals' and 'does Not contains', this can be counterintuitive when thinking through the logic.
Note that as a result, multi-selecting Session id Not equals A,B,C can still send emails to engagements with a value of A.
Workaround: Create a separate filter for 'does not equals' or 'does not contains', do not use multi select.