Version 6.4 of Smartabase will shortly become available for you to explore. It builds on our recent security updates and ensures your systems are even more secure. Plus, there are quality-of-life improvements for administrators and builders. Here is a short overview of the main changes:

• New feature to re-save event form data for a selected period of time.
• New advanced form property for disabling event data conflict notification emails. 
• Improvements to how signature and entered on fields are handled within tables.

Re-save event form data for a selected period of time

Resaving an event form is an important step when you add or change calculations, but it can take a lot of server resources. Now, you can select a specific period when you begin a resave.

Only the records within that period will be recalculated. This can save you a lot of time when working with large volumes of data.

Performance tip: when you use this functionality, make sure to start with the oldest records first as it reduces the load that calculations have on your server.

Disable conflict notification emails using a new advanced form property

The data conflict management tool feature exists to protect your data – when a conflict occurs (for example, when two people overwrite each other’s changes to records on Smartabase) it sends an email to a nominated person, who can resolve the conflict. However, updates to data entered into Smartabase via an integration can also trigger unnecessary conflict notifications. To ensure you only get important conflict notifications, we suggest you disable event data conflict logging for any integration even forms that cause conflict. You can do this using a new advanced form property.

Improvements to how signature and entered on fields are handled within tables

The signature and entered on fields are an important component of forms which support medical and legal processes. We have improved them in several ways that make them more secure when used in tables or when you use group entry mode:

• When a table row is duplicated, neither the signature nor the entered on field will be duplicated with the rest of the data.
• A duplicated signature field will be blank and a duplicated entered on field will calculate the correct date for the new row.

In a table, once a signature field has been entered:

• You can’t use the Fill Down or Copy Last options to copy a signature from a previous table row.
• You can’t use the Fill Down Entire Row option to copy signatures from previous table rows.

Please note that if a row is overwritten by using the Fill Down Entire Row option, any signature fields in that row will be cleared.

General security improvements and bug fixes

• We continue to engage in regular code scans and penetration testing. This results in a more secure platform across the board. Moreover, many of our clients have specific security requirements. Our sports science service team can help to prepare your Smartabase site for the demands of your environment.
• People couldn’t access a file that was uploaded via a multi-file upload field that was entered using group entry mode or a multi-athlete selector field. This is now fixed.
• We’ve resolved an issue where linked calculation field sometimes did not respect the advanced field property setting the linked update range.
• The pop-up window for selecting multiple options now has the correct height (such as the systems permissions collection when modifying a role). Previously, the window height could be too small in specific instances.
• We’ve fixed a problem that meant the password criteria error message was wrong in certain cases.
• A rare issue with incorrect event dates for records created using group entry mode has been resolved.
• Changes to Chrome affected the ability to preview PDF files in Smartabase. We’ve updated Smartabase to account for this and PDFs can be previewed again.