The builder interface gives you access to builder tools to help you create the structure and properties of a Smartabase site. You can mainly achieve this using the event form, profile form, database form and Dashboard builder tools. Using these tools effectively is essential for a successful Smartabase site.
Some of the tools are simple to use (for example, performance standards and performance explanations) and how they are used is described in a single article. The event form, profile form, database form and Dashboard builder tools are each described in their own series.
Your Smartabase administrator is responsible for making sure that you've got the right information to log into Smartabase - your site URL and username. You'll also need to know your password.
The URL for accessing the builder interface follows this format:
https://servername.smartabase.com/sitename/builder
Access to the builder interface is controlled by the site owner, who can assign builder (and administrator) access permission to authorized user accounts.
With access to the builder tools, you are able to make and implement decisions that affect data protection and privacy. It is critical that you take data protection and privacy considerations into account when designing, creating and maintaining a Smartabase site.
The sections below briefly describe the purpose of each of the site builder's homepage tools.
Edit application details
Used to edit a Smartabase site's details and general preferences. It is also where site-wide theming can be configured by using logo, banner and background images as well as customized CSS files. This tool can only be accessed by the site owner.
Event forms
Used to build event forms. Event forms collect and store chronological records with information about people.
Database forms
Used to build database forms. Database forms collect and store data which can be used to fill out a database field in an event form. For example, a strength database may contain hundreds of exercises, each of which can have additional information about the exercise. A food database could contain macro and micro-nutrient values for thousands of food items.
Profile forms
Used to build profile forms. Profile forms collect and store data about people that is not tracked over time and is not date sensitive. Profile forms can only be updated to current values and no record of previous values is kept.
Related entity forms
Used to build related entity forms. Related entity forms collect and store data which can be used to fill out a related entity field in a scheduling or appointment form.
User defined property schemas
Used to configure user-defined property schemas which are custom properties for Smartabase applications. This tool was developed to give Smartabase builders more configuration options when building event forms for applications such as the Smartabase Athlete and Smartabase Kiosk apps.
Performance standards
Used to build, edit and apply performance standards. Performance standards are a means of giving instant visual feedback to people by applying different colors to data entered for numbers and options depending on what criteria is matched. This concept is similar to conditional formatting used by MS Excel.
Performance explanations
Used to build, edit and apply performance explanations. Performance explanations are a means of giving instant textual feedback to people. Their purpose and function is essentially the same as that of a performance standard except that instead of applying a color to a field depending on what is entered by the person, the performance explanation is shown immediately after the event form is saved.
Performance summary reports set up
Used to build performance summary reports for performance summary dashboards. A performance summary report is a selection of important metrics from multiple event forms displayed as a table.
Module store
Used to create or install pre-built tools of event, profile and database forms, performance standards and performance explanations. The Module store tool is only used in highly specialized circumstances. We recommend that you speak to your Smartabase consultant to determine whether it is appropriate for your organization.
Data specification
Used to create a specification for data entered in the Smartabase application.
Chart properties
Used to create templates for styling and formatting embedded charts.
Dashboard builder
Used to create and edit dashboards.
Dashboard builder scripts
Used by Smartabase developers to manage the Dashboard builder tool.
Translation
Used to generate a blank translation file in CSV format. This tool can only be accessed by the site owner.
Translation files
Used to upload completed translation files. This tool can only be accessed by the site owner.
Create new application
Used to create a new site on the current server. This tool can only be accessed by the site owner.