Glossary
| No | Term | Definition |
|---|---|---|
| 1. | Turbo Apps Builder | The online App that manages the forms, flows and its usage |
| 2. | Turbo Forms App | The Web and Mobile forms application that users can use to fill forms |
| 3. | Users | Provisioned users in the system who can be assigned forms to fill and use the application to fill forms |
| 4. | Roles | Users can have one of the following roles in the application Admin - These users can provision users, design forms and assign them, etc. Manager - Managers can access data filled by their team members and approve them User - Users who can fill and submit forms Note: Users of any role can use the Forms application and fill forms |
| 5. | Teams | Teams are a set of users belonging to a logical grouping. This can be corporate teams like HR or maintenance teams etc. Users can belong to multiple teams. |
| 6. | Category | Categories help to group Forms together. Each category can have as many forms as desired. |
| 7. | Forms | Forms are filled by users and capture data in the field. Completed forms can be submitted for review and other advanced flows by users. |
| 8. | Nested Forms | Reusable form snippets that are designed independently and can be embedded in other forms. Changes to nested forms can be simultaneoulsy published to forms embedding them. |
| 9. | Formsets | Formsets are a logical group or set of forms that belong together. For e.g. a stockbroker enrollment form and a bank mandate are two individual forms that need to be filled together and make a Formset. |
| 10. | Master Data | Master data are the fields/sets of data that do not change often and are referred to in forms. For e.g. in a maintenance form, equipment is referred to and comprises master data. This master data can be downloaded from external systems like SAP, Databases etc. |
| 11. | Flows | No code designer to generate flows to run approvals, read master data and publish data to systems like Sharepoint, SAP etc. Other systems include SQL compliant databases, OData, Microsoft Active Directory and many more. Flows can be run on form save, completion, fetch results online in forms and for downloading master data. |
| 12. | Flow Input | Flow Input a special input variable that can be used to pass in JSON data to Sub Flows. Also when barcode events are triggered in the form they are posted to Smart Data Component using Flow Input. Lastly when webhook calls are received by the flow, all data posted to the webhook im parameters and body are accessible via the Flow Input variable |
| 13. | Smart Data Component | Control that enables forms to read or write data online. Also called SDC |
| 14. | Environment | Key value pairs that can be associated with forms for use in the forms or flows like API tokens etc |
| 15. | Documents | Documents that can be uploaded and associated with forms. Users can access these documents like repair manuals, training videos etc while filling out the forms |