We’ve been working hard getting version 6.7 of Smartabase ready for you to use. This release includes more ways to give the right people relevant information, new options to encourage good password habits and user experience improvements. Here’s a short list of what’s new:

  • Administration tool for more granular control of form components
  • Ability to ban the use of specific passwords or password patterns
  • Re-styled notifications for the Smartabase web app
  • The login screen automatically reloads after logout

Set up restriction policies to prevent editing of selected fields and sections

In this release, you’ll find a new administration tool for Restriction policies. We designed this tool so that administrators can make more granular decisions about which parts of event forms and profile forms people can edit. Previously this could only be set directly via someone’s role, which was limited to giving access on a form by form basis. Now you can apply restriction policies to roles, and then assign that restriction policy to individual questions and sections within a form.

A screenshot showing an example of a restriction policy selected in the section properties of an event form

In this example we’re looking at an event form used to collect a brief summary of a new injury. We’ve assigned a restriction policy called Physio Policy to the Physio Details section of the form, which means only people with a role that includes this policy will be able to edit the fields in this section. The policy would be assigned to a role for physiotherapists, so the athlete and other staff members couldn’t update this section of the form. A similar restriction policy could be set up for a coaching role, so only coaches could edit the Coach Details section.

Ban specific passwords and password patterns

As part of ongoing enhancements to password management, we’ve added two new configuration options when managing password policies. Now you can upload lists of custom patterns and passwords, which will stop people from creating insecure passwords. In addition to the option to ban common patterns like 12345 and qwerty, the custom patterns option lets you add items of your choice, so, for example, you can prevent people from using your organisation’s name or their team name in their password.

When you ban passwords, only the exact items that you’ve included in the file will be banned; people can still use these items as a part of their password or with different capitalisation. For example, if you add Pineapple!! as a banned password, someone would still be permitted to use Pineapple!!1, pineapple!! or Pineapple! when setting up their password.

A screenshot showing an example of a password policy

Quickly view and dismiss system notifications

System notifications commonly appear when you complete an action or an error occurs when you’re using Smartabase in your browser. We received feedback that system notifications sometimes interfered with navigating through Smartabase, and it wasn’t clear that clicking on a notification would close it. As part of this release, we’ve moved system notifications to the bottom right-hand corner of the screen, which keeps the rest of your screen clear to use other Smartabase tools. We’ve also added a close icon to the notification box, so it’s even easier to dismiss the message once you’ve seen it.

A screenshot showing an example of how the updated system notification appears

We’ve also added the ability to customise the message duration. If you’d like to change the default notification duration time on your site, please get in touch with your Fusion Sport representative.

Come back to Smartabase more easily

Like the enhancements to system notifications, this update focused on improving the look and feel of Smartabase. Now when you log out of your account you will be automatically taken back to the log-in screen, instead of having to click to reload the page.

General improvements and bug fixes

  • We’ve updated the licence audit tool to include the email address for each user account on your Smartabase site. This means administrators can easily create a CSV file that includes user account information (username, name, email, date of birth etc) alongside Smartabase access details (builder, administrator, team administrator and coach permissions, group membership, roles and last login date).
  • All Smartabase notification emails (such as password resets, performance alerts, daily reminders and more) now come from noreply@smartabase.com. We made this change to reduce unnecessary responses to our support email and to encourage members of your organisation to reach out to you for support that’s specific to your Smartabase site.
  • When you update account details via the user account page (either for your own account or as a coach with the required access to update someone else’s details), you’re required to enter your password to confirm the updates. Now, if you accidentally enter the wrong password, you’ll be able to try again instead of being logged out of the system.
  • To support upcoming functionality for the Smartabase Athlete app, we’ve added the ability for administrators to see which devices are currently logged in (via single sign-on) to the Athlete app for each person’s user account . This information can be seen when viewing a user account from the people tool.
  • We’ve increased our support for people using Smartabase in Simplified Chinese, Dutch, French, German, Spanish and Korean. More of the Smartabase elements that you interact with have been professionally translated. Please remember that anything you build or set up in Smartabase yourself (such as event form names, dashboard instructions or performance alert messages) needs to be translated separately from the default Smartabase labels. You can get in touch with your lead consultant from our sport science team to assist with this process.
  • If your Smartabase site has registration enabled, people will now see the list of default roles displayed in alphabetical order.
  • We’ve made improvements to Smartabase’s queuing system to decrease the processing time when historical calculations are used.
  • We’ve removed an obsolete site theming tool from the builder interface. The ability to adjust your Smartabase site’s default colours, styling, log-in screen images and logos has been entirely built into the application details module for several years now. Please contact your lead consultant if any changes are needed to your site’s appearance.
  • We’ve reinstated the ability to delete individual database records from the builder interface.
  • We’ve fixed an issue where, in some instances, storing images in database records caused an authorisation error message when trying to select that record via an event form.
  • We’ve removed the Delete button for user accounts that team administrators are not permitted to edit.
  • We’ve also removed the Clear button for signature fields if the viewer’s role only has Read data permission for the form.
  • We’ve made improvements to validation checks, which fixed an issue where required fields in tables were being treated as required when they weren’t visible.
  • We’ve fixed an issue where icons weren’t displaying correctly when selecting options in an OSICS injury diagram.
  • We’ve updated the Related event pull through advanced form property so it’s always visible in the advanced form property list. It’s no longer dependent on the Enable related events advanced form property being set to True. This change means that it’s easier to auto-populate event forms that are set up as embedded events.
  • We resolved a problem affecting the event dates of records that were created using the training blocks tool. This fix ensures that newly created training blocks will be unaffected by a time zone related bug. If you’ve experienced any date-related irregularities with your existing training blocks, please contact your lead consultant who can help you update your training blocks.
  • We’ve also fixed a bug that affected the finish time of records created in the one-hour window between 11 PM and 12 AM. Records created in this time period now have an AM finish time, not a PM finish time (unless the event duration is manually adjusted such that, for example, the start time is 11 PM and the finish time is 11.30 PM).
  • We’ve resolved an issue that prevented the Show all tick box for tables in forms from working correctly. When a table has the Optionally hide rows property set to Yes, the Show all tick box lets people choose whether to display all rows or the two most recently entered rows.
  • We fixed an issue where the lastvalue aggregation type in table calculations was ignoring the last table row if it had a blank value. You can still use the lastenteredvalue to find the last non-blank value in a table field.
  • We’ve updated the data specification tool to display the correct details for any database fields in event and profile forms.
  • We’ve fixed an issue that prevented option calculations using the dateformat function and day of week parameter (“DDDD”) from working correctly. An option calculation that has each day of the week in the option list and uses the following formula: dateformat(Event Date, “DDDD”) will now return the day of the week (Monday, Tuesday, etc) corresponding with the date of the record.
  • We identified an issue when referencing time zones in dateformat functions, which resulted in New Zealand Standard Time showing up regardless of the viewer’s actual time zone. Using ‘ZZ’ in a dateformat calculation will return the correct time zone.
  • We’ve fixed an issue that caused daily reminders to be sent at midnight on the first day after they’d been set up. Now they’ll be sent at the designated time or 15 minutes after being set up if the designated time is earlier in the day than the time you created it.
  • For anyone using Mozilla Firefox as their browser, we’ve fixed the display of body area diagrams to ensure you can always see which body area you’ve selected. A bug meant that any body area you selected didn’t get highlighted, although your selection was recorded and saved as data.
  • We’ve addressed an issue that was slowing down smart flows with the Date type set to Period.

Highlights from your last Smartabase release notes

In the last release notes, for Smartabase version 6.6, we announced:

  • The option to send daily reminders according to the recipient’s time zone.
  • The ability to reference more information from Smartabase accounts in event and profile forms.
  • A feature for bulk downloading files from the reports and history modules.
  • The ability to disable PIN use as a password policy option.
  • Improvements to the handling of multi-factor authentication codes sent via SMS.
  • The ability to export and import dashboards created using the dashboard builder.
  • A new workflow for enterprise servers that improves the process of switching between sites.
  • Improved support for using Smartabase in three new languages: Dutch, Spanish and French.
  • Ongoing improvements and bug fixes.

If you missed those release notes, you can read them here.