These are the advanced properties that are available for an entire event form. To access the form properties, select the event form name in the event form builder. From the form properties section, select the Advanced Properties tab.

  • Form Positioning: This property allows builders to manually drag and drop sections in order to position them on the form. The height and width of sections can be set on the advanced properties of the sections. Be mindful of overlaps between section and always check the results not only on preview mode but also on the actual application.
    • Width: if the form positioning is set to Positioned, builders can specify the width of the form using this property. Usually pages are 800 pixels wide.
    • Length: if the form positioning is set to Positioned, builders can specify the length of the form using this property. The usual length of forms varies depending on the number of fields in them, but usually they are around 400 to 1200 pixels long.
  • Plural Name: this property allows the builder to specify the plural name of the form. The system by default adds an “s” at the end of the name, but, for example, Daily Availabilities would need to be specified here to avoid a misspelling (Daily Availabilitys).
  • Lockable: if set to Yes, it adds a button at the bottom of the form during data entry that allows the users to save the record and lock it so it cannot be changed afterwards. Note: records updated using a quick edits pop-up cannot be locked.
    • Save And Lock Text: this property renames the Save & Lock button located at the bottom of the form during data entry. (Lockable needs to be set to Yes).
    • Save As Lock Tooltip: this property changes the text that pops up when the user hovers over the Save & Lock button.
  • Cancel Text: this property renames the button Cancel located at the bottom of the form during data entry.
  • Cancel Tooltip: this property changes the text that pops up when the user hovers over the Cancel button.
  • Save And Close Text: this property renames the Save & Close button located at the bottom of the form during data entry. Is not possible to hide this button, only rename it.
  • Save And Close Tooltip: this property changes the text that pops up when the user hovers over the Save & Close button.
  • Save And Print: if set to Yes, it adds a button at the bottom of the form during data entry that saves the form and creates a printable PDF.
    • Save And Print Text: this property renames the Save And Print button located at the button of the form during data entry (Save and Print needs to be set to Yes).
    • Save And Print Tooltip: this property changes the text that pops up when the user hovers over the Save And Print button.
  • Save As Draft: if set to Yes, it adds a button at the bottom of the form during data entry that allows the users to save the form as a draft.
    • Save As Draft Text: this property renames the button Save Draft located at the bottom of the form during data entry (Save as Draft needs set to Yes).
    • Save As Draft Tooltip: this property changes the text that pops up when the user hovers over the Save Draft Button.
  • Save and Enter Another: if set to Yes it adds a button at the bottom of the form during data entry that allows users to save and enter another record. If clicked by athletes, it will redirect them to a new record for the same form they just finished completing. If clicked by coaches, it will redirect them to a menu where they can select a new athlete and a new form.
    • Save And Enter Another Text: this property renames the button Save And Enter Another located at the bottom of the form during data entry (Save and Enter Another needs to be set to Yes).
    • Save And Enter Another Tooltip: this property changes the text that pops up when the user hovers over the Save And Enter Another Button.
  • Save And Continue: if set to Yes it adds a button at the bottom of the form during data entry that allows the users to save the record and then be immediately taken to the same record for further editing. This is useful for displaying historical calculations, charts and related events.
    • Save And Continue Text: this property renames the button Save And Continue located at the bottom of the form during data entry (Save And Continue needs to be set to Yes).
    • Save And Continue Tooltip: this property changes the text that pops up when the user hovers over the Save And Continue Button.
  • Allow Copy To Clipboard: if set to Yes it allows users to copy all the data that has been entered into a record and pasted into a new record for the same form. This new record can be for the same athlete or a different one. When this is enabled three new buttons will appear at the top of the form during data entry:
    • Copy To Clipboard: this allows a user to paste the information stored in the clipboard multiple times. The data remains stored until a new record is copied or Clear Data is clicked.
    • Copy For Next Entry: this auto fills the next entry, but once it has auto filled the form the clipboard is emptied and it cannot be used again.
    • Clear Data.
  • Enable Group Entry: if set to True, it allows the form to be filled for multiple athletes using the enter data for group module. If set to False, the form will not appear on it.
  • Can Cause Conflict: 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.
  • Event Type: this property allows the user to specify which type of event the form is. The different event types offer different functionality so this should be chosen carefully according to what the form is meant to do. The options are:
    • Event
    • Scheduled Event
    • Appointment
  • Athlete Field: this property determines how the system will treat single athlete and multiple athlete selection fields. If set to None, as the name suggests, nothing special will happen after selecting an athlete. If set to Show In Calendar, the record will show on the selected athlete’s calendar but it won’t create a record for him/her. If set to Create Event For Athlete, it will do exactly that, essentially creating an alternative for group entry.
  • Enable Related Events: related events are a workflow that allows to link events, the end result is similar to having an inForm report but it has the functionality to pull data across the forms and it can restrict the entry mode of the linked forms (see Entry Mode property for more details). For related events to work the form has to be saved first, Save And Continue buttons are useful for this.
    • Related Event Forms: with this property the user can select the forms that will be linked as related events.
    • Expand Related On Sidebar: related events appear on the sidebar when you clicked on the form they are related to. If this property is set to Yes, the individual records of the related events will be visible as well.
    • Related Events Position: with this property it is possible to choose if the related event section will be displayed above the Save & Close button or under it.
    • Related Event Selector: The buttons linking to the related events can be set up as a Body diagram as well. If set to Normal it will just show buttons. If set to to Body Diagram (If Possible) instead of a button some of the related events will be accessible through clicking on a Body diagram (only if they were correctly set up for this, if not they will show as buttons). If set to Both the related events that are accessible via the Body diagram will also have a button underneath it.
    • Related Event Bodyparts: this property is the continuation of setting related events to be accessible through a body diagram type field. On the form the events are being linked to this would be left blank. Then the user would have to go to each of the individual forms being linked and select which body part will correspond to that form. For example, if an Ankle Assessment form is a related event of a form called Physiotherapy Session, the user would have to go to Ankle Assessment and set the Related Event Body Part to Ankles. The result would be that if somebody clicks on the ankles in the related event body diagram in Physiotherapy Session the system will redirect them to the Ankle Assessment form.
  • Sidebar Auto History: if set to Yes, when a user clicks on the form name on the sidebar the system will automatically go to the history for that form.
  • Linked Record Pullthrough: if set to Yes, the system will allow completed fields on the form to be pulled through to the related events, as long as the field name, type and options are set up exactly the same on both forms.
  • Enable Comments: this property turns on and off the comment box that appears at the bottom of the form (below the Save & Close button) when reviewing a previously entered record.
  • Enable Deleting Comments: this property determines if users will be able to delete previous comments made on the comment box mentioned above.
  • Print All: If related events are enabled, this property allows the user to decide if the related events will be included when printing the form. If set to No, only the form will be printed. If set to Yes, all the related events will be included.
  • Print Page Format: this property allows the user to choose the orientation of the page when printing a record. The options are:
    • Portrait
    • Landscape
  • Expand Into Calendar Finish/Start: this property allows the user to expand a record in the calendar into its individual components. For example, a training session could be divided into Warm up, Drill 1, Drill 2, Cool Down, Recovery. Regularly this would show as one block called training session, but with Expand Into Calendar the user can specify a start and finish time for each component and show those components on the calendar view. (It only works with time fields in a table). The new start and finish times overwrite the time the record was saved on the calendar view, however the time the actual record was saved does not change. E.g. if a record was saved at 2pm outlining what was done that morning between 7 and 11am, the time the record was entered stays at 2pm even though the calendar view shows everything in between 7 and 11am and nothing at 2.
  • Show Event In Calendar: this property allows the builder to show/hide events on the schedule and calendar view. This will not affect any other aspect of the system (history, reports, sidebar). This property has the potential to declutter the calendar, making the system more user friendly.
  • Show Event In Ical: this property has a similar functionality as the one directly above but this time it shows/hide the event from a ical download or calendar subscription. This does not affect the calendar view in Smartabase.
  • Ical Subject: this property allows the builder to control the name that the event will have in an iCal download or calendar subscription.
  • Ical Location: this property allows the builder to control the location of the event in an iCal download or calendar subscription (i.e. where the event is taking place).
  • Show History: this property allows the user to show/hide the athlete’s history section at the bottom of the page during data entry (below the Save & Close button). This has no effect on the history or reports modules, it only affects the history section at the bottom of the form during data entry.
  • History Columns: this property limits how many columns will show on the athlete’s history and the history section at the bottom of the forms during data entry (only if Show History is set to Yes).
  • Name Column Width: this property allows the user to specify how wide the name column should be in reports and history.
  • Show Last Record: if set to Yes, this property allows the user to show the data from the athlete’s previous record to the right of the data entry fields. If this would be beneficial or not should be decided on a case by case basis.
  • Show Templates: When templates are enabled it is possible to store information entered in a form and apply it to another entry later. The difference between this and the clipboard is that templates are permanently stored on the system and users can have more than one saved. This could be useful for example on strength and conditioning forms were the sessions are repeated frequently. Templates only work when both properties are set to Yes.
  • Show Right Sidebar: this advanced form property is obsolete and has no effect.
  • Show Entered By: if set to Yes, the history and reports modules will include an Entered By column by default. Using the reports module, it is possible to exclude or include this column manually as the report is created (effectively overriding this property). However, on the history there is no way of changing this.
  • Category Icon: this property allows the user to choose the icon that will be displayed next to the event form name on the mobile app.
  • Lock Delay: if Lockable is set to Yes, it is possible to set a delay for a record to lock, giving users time to amend entries within the delay period you specify. The delay period starts from when a user selects the save and lock option. It does not re-start if further edits to the record are made during the delay period.
  • Compressed Summary Field: the compressed field functionality allows the user to create a summary of a set of fields. This property is aimed at improving the usability of the system because it hides all the fields that are part of the summary. Then, when the summary field is clicked, a little pop up box appears with all the fields that are being summarised. Once that pop up box is finished, it disappears and the event form only displays the summary field. For this functionality to work the calculation field that contains the summary must be selected as the Compressed Summary Field. Each individual field that will be summarised has to be set up with the right field properties too (Compressed Data Entry set to True).
  • Default Next Cell: this property allows the user to select the direction tables will be filled (i.e. after a field is filled where should Smartabase go next). It can be set to go to the cell on the right, to the cell directly below or to just stay on the cell that was just filled, without moving automatically to another one.
  • Expand Sidebar: this property can add functionality to the sidebar. If Expand Sidebar is set to True, when a user clicks on a record a little menu will show up asking if he/she would like to open the form, print a pdf, or duplicate the form (only if duplication is enabled).
  • Attachments: this property allows users to attach files to the form. This is different from the document upload field. On this case the attachment is not made against a field inside the form, it is made against the form itself. It is important to mention that anybody with access to the form will have access to the attachment as well.
    • Always Edit Attachments: this property defines if users will be able to edit or delete attachments. If set to No, they will only be able to download it.
    • Attachments Are Resources: this property was developed as a workaround for the security issue with attachments made against the form. If set to True, all attachments will be turn into resources as well, effectively limiting the access to them based on categories (access to categories are given on the admin site). If this property is changed once there is data on the form, all the attachments already in it will be automatically added to the Attachment sidebar category. When adding new attachments, the users can choose any category available to them.
  • Enable Duplication: if set to True, the user will be able to duplicate the entry from the sidebar (only if Expand Sidebar is enabled).
  • Date Override: this property allows builders to specify a date field within the form for a user to override the actual date of entry. For example, if a record is saved on 3/03/2019 but has a date override set to a date field where the user selects 28/02/2019, the date for the record will be set as 28/02/2019. When the date override property is used, the record date and time selector that usually appears above a form will not be shown to the user.
  • Show Tooltip In Sidebar: if set to True, every time a user hovers over a record on the sidebar a tool-tip will pop up showing a preview of the information on the record.
  • Show Tooltip In Calendar: If set to True, every time a user hovers over a record on the calendar a tool-tip will pop up showing a preview of the information on the record.
  • Show Tooltip In Tables: if set to True, every time a user hovers over a record on the history or reports module a tool-tip will pop up showing a preview of the information on the record.
  • Recalculation Delay: this property allows the users to delay running the calculations on the form. This could be useful when there are too many calculations on the form and data entry is running a bit slow because the system keeps re-evaluating all calculations as new data is being entered. There are options that allow builders to set different delay durations. However, in most cases the results will be needed immediately.
  • Derive Form By: Allows builders to create different versions of a form based on visibility settings. For example, a Musculoskeletal Evaluation form might have a field called Evaluation Type, with the options Full Evaluation and Basic Evaluation. If the form is set to be derived by Evaluation Type, Smartabase will essentially create two sub-forms for the Musculoskeletal Evaluation, one called Full Evaluation and the other called Basic Evaluation. The fields on those two sub-forms will be set based on the visibility settings that use the Evaluation Type field as a condition. The information on both sub-forms will be stored together, allowing reporting to include everything.
  • Entry Mode: this property is relevant mainly to related events. If Entry Mode is set to Linked Entry Only, new data will have to be entered through the form it is related to. For example, if a form called Medications is a related event of Medical Consult, it would only be possible to add a new medication record if the users go through Medical Consult first.
  • Auto Colour: this property controls whether performance standards are applied automatically during data entry.
  • Auto Shorten: when fields are organised in columns and their names start with the same words, it is possible to change the way they are displayed. If None is selected, the whole name will be displayed (for example, Test 1, Test 1 Comments, Test 1 Score). If Shorten is selected, only the difference between the names will be displayed (Test 1, Comments, Score). If Full is selected, only the first field name will be displayed (Test 1, [no name], [no name]).
  • Compare To: this property allows the builders to compare the values from the form against another form. This functionality only works for fields with exactly the same name across the two forms. The values will appear to the right of the data entry fields, similar to when Show Last Record is enabled. It is possible to individually select which fields will appear in the comparison with the advanced field property called Comparison. If this is set to No, the field will not appear in the comparisons.
  • Hide Rows: this property allows the builder to hide fields on the form that are not important. For this to work properly, tick boxes need to be set up as importance selectors and given the options No and Important. The sections should be set up in a column format (user friendly), with one tick box per line. During data entry a tick box will appear at the top of the page asking if the user wants the system to show only the important rows. If that is ticked, only the rows of fields that have the importance selector field ticked will show.
  • Rows In History: this property sets the amount of rows that will show by default on the history.
  • Rows In Reports: this property sets the amount of rows that will show by default on reports.
  • Auto Save: if set, automatically saves the form periodically while it is being filled out.
  • Ranking Method: obsolete.
  • Send Emails After Time Series Processing: This property turns on and off the notification email a user receives after a time series file has been processed by the system.
  • Calendar Saved Colours: this property allows the user to specify the colour of saved records on the calendar. The colour needs to be in Hex code.
  • Calendar Planned Colours: This property allows the user to specify the colour of planned/draft records on the calendar. The colour needs to be in Hex code.
  • Calendar Auto Colour: this property allows builders to set the colour of the event on the calendar based on the performance standard for a specific field. E.g. A 40m sprint was extremely slow and the field is coloured red, if this field is selected as the calendar auto colour, the event on the calendar would look red as well. This takes precedence over other colours.
  • Calendar Css: if a user has experience with CSS coding, lines of code can be added to the base CSS file creating a class for the record in the calendar and applying a particular formatting to it. Once the class is created, the name of it can be specified with this property, so the new formatting is applied whenever it shows up on the calendar.
  • Calendar Block Details: this property allows users to include/exclude information from training blocks (e.g. week 1 session1) on the calendar.
  • Focus Field On Open: if this is set to Yes the first field will be selected automatically (ready to edit) when a new record is created and also when an old one is accessed.
  • Form Entry Width: this property allows builders to specify the width of the form during data entry, this is set in pixels. If left blank it defaults to 100%. Keep in mind that the actual questions are wider than 100px so be mindful of the number selected, especially if it is small.
  • 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.
  • Linked Calculations: or most use cases this property should be set to No. This property should only be set to Yes if new entries of a form containing linked calculations will be backdated, meaning that the linked calculations have to identify the current state on the date the record is being created. There are performance implications for enabling this property.
  • Allow Imports: setting this property to No prevents users from using the import data tool to import records for this form.