These are the saved properties that are available for a form. To access the save properties, open the form and select its  name in the builder. From the form properties section, select the Save Properties tab.

To enable a save property, select the tick box next to the relevant property.

Types of save buttons:

  • Save and close: adds a button at the bottom of the form during data entry that saves the record and then redirects people to view a report of historical entries for that form.
  • Save and continue: adds a button at the bottom of the form during data entry that saves the record and then immediately opens the same record for further editing. This is useful for displaying historical calculations, charts and embedded events.
  • Save and enter another: adds a button at the bottom of the form during data entry that allows people to save and enter another record. If used by athletes, it will redirect them to a new record for the same form they just finished completing. If used by coaches, it will redirect them to a menu where they can select a new athlete and a new form.
  • Save and lock: adds a button at the bottom of the form during data entry that saves the record and locks it so it cannot be changed afterwards. Note: records updated using a quick edits pop-up cannot be locked. Additionally, records entered via group entry mode cannot be locked.
  • Save and redirect: adds a button at the bottom of the form during data entry that allows people to save the record and be redirected to either the homepage or a dashboard. Note: it is not possible to redirect to a dashboard on enterprise sites where the event form is linked to child sites.
  • Save and export PDF: adds a button at the bottom of the form during data entry that saves the form and creates a printable PDF.
  • Save as draft: adds a button at the bottom of the form during data entry that allows people to save the form as a draft.
  • Cancel: adds a button at the bottom of the form during data entry that cancels data entry without saving any changes to the record.

Save button properties:

  • Label (optional): this property renames the save button located at the bottom of the form during data entry. You can use this property on all types of save buttons.
  • Tooltip (optional): this property changes the text that pops up when the user hovers over the save button. You can use this property on all types of save buttons.
  • Restriction policies: this property allows a restriction policy to be selected from the dropdown list to make the save button visible only to users with access to that restriction policy. Note that role restricted save capabilities are not available across enterprise sites as roles cannot be shared. You can use this property on all types of save buttons.
  • Usage criteria: this property allows filter criteria to be applied to determine whether the save button can be selected or not. You can use this property on all types of save buttons.
  • Lock Delay: this property allows a lock delay period to be specified, giving people time to amend the data contained in the record. The delay period starts from when someone saves the record using the Save and lock button. The lock delay period restarts if further edits to the record are made during the delay period. This property only applies to the Save and lock button.
  • Redirect To: users can either be redirected to the homepage or to a dashboard. This property only applies to the Save and redirect button.
  • Redirect Applies To: the redirection can be enabled for all users, athlete only, coach only or different for coach and athlete. This property only applies to the Save and redirect button.
  • Dashboard: this property is only visible when redirecting to a dashboard and the redirect applies to all users. Select the relevant dashboard from the dropdown list. Dashboards will only appear in the list if the dashboard settings enable it to be viewed on event pages. This property only applies to the Save and redirect button.
    • Athlete Dashboard: this property is only visible when redirecting to a dashboard and the redirect applies to either athletes only or is different for athletes and coaches. Select the relevant dashboard from the dropdown list. Dashboards will only appear in the list if the dashboard settings enable it to be viewed on event pages. This property only applies to the Save and redirect button.
    • Coach Dashboard: this property is only visible when redirecting to a dashboard and the redirect applies to either coaches only or is different for athletes and coaches. Select the relevant dashboard from the dropdown list. Dashboards will only appear in the list if the dashboard settings enable it to be viewed on event pages. This property only applies to the Save and redirect button.
  • Conflict warnings: this property is used for appointments, scheduled event or regular events that require the athlete to be at one place at a time. The system will detect conflicts when two or more records are set to cause conflict overlap. A warning will be displayed when a conflict is found. This is useful because not all events should cause problems when they overlap with another event and this property gives the builder the power to decide.
  • Auto-save: this property causes records to be automatically saved during the data entry process.
    • Save as temporary record: records will be saved to the backend of the system and will not show in history or reports until a save button is used.
    • Save as real record: records will be saved and will show up in history and reports. The record will be updated every 30 seconds while the form is being filled out. Note: a record will be created 30 seconds after the form is opened. If the form is exited without a record being saved, the record will still exist. If the form includes a required field that has not been entered, the form will still be saved, bypassing this requirement.
  • Save audits: this property determines if an audit trail will be stored for this form. The audit trail keeps tracks of all the changes made to the form. This is only accessible to site administrators of self-hosted Smartabase sites. This should be set to Yes for most forms; the only types of form where it could be useful to turn this off would be on big summary reports with just linked values and calculations that are being saved very often for a lot of users.

Was this page helpful?