This checklist is designed to guide users in using the Form Builder, including creating new forms, using collections on forms, using actions on forms, using programming on forms, setting up headers and footers, and more. For a complete guide, see Form Builder.
For details on each of the Form Settings, see Form Builder > Creating a New Form.
For details on each of the Common Properties, see Form Builder > Adding Components and Presets to a Form.
For details on each of the setup options for each component and preset, see Form Builder > Adding Components and Presets to a Form.
The Collections tab in the Form Builder is used to set up SQL queries that can be used to populate computed tables, drop-down options, radio groups, text areas, and text boxes on a form.
For more information on using collections, see Form Builder.
The Actions tab in the Form Builder is used to designate a SQL query that will run when the form is approved or denied in SIS. Fields in the form can be used in the query with the {$fieldname} format. A certain value in a field on the form can cause a field in the student's record to be updated upon form approval. For example, an action can be set up so that when the school nurse approves a School Accident Report Form that has the Medical_Alert field on the form checked, the "Medical Alert Icon" field in the student's record is also checked. This will then trigger a medical alert icon to appear on the student, based on alert icon setup in Setup > Edit Rules & Workflow. The Actions tab is primarily used by Focus staff.
For more information on using actions, see Form Builder.
When there are multiple actions set up for a form, the priority dictates the order the actions run. The lowest number priority will run first.
The Programming feature allows you to apply custom behavior to fields on the form using JavaScript. For example, you could add programming to a Start Date field to restrict users to selecting only weekdays (Monday through Friday) in the future. Level 1 training is recommended before using this feature.
For more information on using programming, see Form Builder. For examples for using programming, see Form Builder > Programming Examples.
SSS forms can be cloned and translated into another language. Machine translations can be used for the initial setup (Bing translation), and additional translations can be made manually as needed. When printing forms for an event in SSS > Manage Student, users will be able to select which language of the form to print.
The SIS, ERP, and SSS tags are assigned to forms to make those forms available in those parts of Focus. The Focus tags cannot be edited. Additional custom tags can be added to the Tags tab and are used to organize forms within the Forms menu.
A form must be tagged with the module (SIS, ERP, or SSS) in order for it to be available for use in that part of the system. Forms will also be organized within the Forms menu by their tags.
For districts using the Document Management add-on module, SIS forms can be included on the Uploaded Files screen for students and users upon the form being finalized. In order for a form to be included on the Uploaded Files screen, the Academic Category must be set on the form in the Form Builder.
Selecting "Auto-Image" on a form sends a PDF of the form to a server. Server credentials are set in ERP > Setup > Settings > Integrations to store and archive PDFs.
See Form Builder for tips and more information on this process.
For details on each of the Common Properties, see Form Builder > Customizing Headers for Forms.
For details on each of the setup options for each header component, see Form Builder > Customizing Headers for Forms.
You are done. Great job!