Every Fulcrum organization consists of a collection of apps (forms). Apps can be created from scratch or added from our comprehensive gallery of existing app templates and modified. The Fulcrum App Gallery includes hundreds of ready-made form templates from a variety of industries, and we encourage users to submit their own apps to share with other Fulcrum users.
The Fulcrum App Builder
The drag-and-drop app builder is comprised of three columns:
Add Fields: The field type components available for your plan are grouped into categories. You can get more information on each individual component by hovering over the “i” (info) icon. To add a field to your app, click and hold on the field type component, drag it over to the app canvas, and release the mouse where you want it to be placed. Once placed, the field settings will open for you to complete.
Field Settings: This is the app canvas where you drag field components. You can rearrange fields by clicking, holding, and dragging the component around the canvas. Rearranging fields is not destructive, but deleting a field will destroy any data associated with that field. You can change field labels, descriptions, defaults, data names, requirement and visibility settings without harming any existing data. Field types cannot be changed. Every field requires a Label and Data Name. Different field types have different settings options, but all fields have the following common settings:
- Label: Label of the field when collecting data (required)
- Description: Additional descriptive information about the field. Accessed by tapping the “i” info button on mobile. (optional)
- Default Value: Default value to prefill the input. Can improve efficiency but all may encourage skipping over field completely. (optional)
- Data Name: Database-friendly property name, used as the column name for exports and data shares (required). Note: shapefile exports may trim data name.
- Required Field: Is an input required in order to submit the record?
- Hidden: Hidden fields can store imported data without being visible to users.
- Read-only Field?: Read-only fields are visible but cannot be modified by users.
- Default to previous value?: Use the input from the last record as the default value.
App Settings: This is where you assign the basic settings for the app.
Standard App Settings
- Name: Every app requires a name. This should be short but descriptive so users can quickly navigate to it from the app picker.
- Description: Optional descriptive text to display below the app name.
- App Status: Inactive apps are not accessible from the mobile device and are used for archiving purposes.
- Record Title: The field(s) used to determine the record title. Can be a single field or concatenation of multiple fields. Title is displayed in the record list view and marker popup. Note: changing the title configuration after data has been collected requires clearing the mobile cache.
- Status Field: The status field is a special field used for color coding and data filtering.
- Location Settings: Set whether location geotagging is enabled / required for records.
- Data Events: Data events allow users to script actions when certain events are triggered.
Advanced App Settings
- Icon: Optional app icon to display next to the app name. Can be used for branding.
- Projects Enabled: Allow users to tag records with projects that they have access to.
- Assignment Enabled: Allow records to be assigned to individual users.
- Auto Assign Records: Assign records to the user that creates them.
- Hidden on Dashboard: Make reference apps hidden but still active for use with record linking.
Field Types and Settings
- Text: General free text entry. Launches the standard alphanumeric keyboard on mobile. Additional settings include: min/max length and regular expression pattern validation.
- Numeric: For entering numbers. Launches the numeric keyboard on mobile. Additional settings include: integer or decimal, numeric min/max validation.
- Yes/No: For simple yes/no questions. Additional settings include: optional 3rd N/A value, label / value inputs.
- Date: Formatted date entry. Launches the native calendar picker on mobile. Format for import is
- Time: Formatted time entry. Launches the native time picker on mobile. Format for import is
- Single Choice: Choice list which supports only one selection. Choices can be specified inline or referenced from a predefined choice list. Additional options include: Allowing “Other” to allow user to enter item if not in choice list.
- Multiple Choice: Choice list which supports multiple selections. Choices can be specified inline or referenced from a predefined choice list. Additional options include: Allowing “Other” to allow user to enter item if not in choice list.
- Classification Field: Similar to single choice field, but can have nested choices to give a logical grouping or hierarchy to the choices. Additional options include: Allowing “Other” to allow user to enter item if not in choice list.
- Section: Use sections to group fields together to better organize your form for presentation to the user. Also includes display options: inline display simply provides a group heading while drill-down display makes the section display in a separate page.
- Repeatable: Create multiple one-to-many relations. Additional options include: Title, Location Enabled, Location Required, min/max count. Repeatables must have at least one field within.
- Label: Simple fields for displaying text on the form.
- Signature: Capture electronic signatures to attach to the record. Additional options include: Agreement Text.
- Photos: Associate photos with this field by launching the camera or selecting from the camera roll. Additional options include: min/max Photos.
- Videos: Associate videos with this field by launching the camera or selecting from the camera roll. Additional options include: Audio enabled?, GPS Track enabled?, min/max Videos. Enabling the GPS track allows for spatial video playback with synced map.
- Audio: Associate audio recordings with this field by launching the microphone or selecting from the camera roll. Additional options include: GPS Track enabled?, min/max Audio Files. Enabling the GPS track allows for spatial audio playback with synced map.
- Address: Store a single street address. Can autopopulate on mobile devices by reverse geocoding the record’s location coordinates to determine nearest address. Additional options include: Autopopulate?
- Hyperlink: Include a link to open a URL in the browser. Can also be used as an action button with data events. Additional options include: Default URL.
- Barcode: Scan a barcode and store the text value.
- Record Link: Select or create records from other apps you have access to. Additional options include: Linked App, Allow Selection of Existing Records, Allow Creation of New Records, Allow Updating of Existing Records, Allow Multiple Records, Selection Filters, Autopopulate Fields.
You can preview your app as you are building it by clicking the yellow “Preview App” button. This will preview the app in its current draft state, so you can confirm it is functioning properly before saving any changes. This is particularly helpful for testing and debugging data events.
Saving Your App
When you build or edit an app, you are working on a local draft of the app schema. These edits are not available for other users until you click either the “Save and Continue” or “Save and Exit” button. Once saved, users need to sync their mobile device or refresh their web browser if they are on the app builder page in order to pull down the changes. Multiple users should not edit the same app in different browsers at the same time, as subsequent saves will overwrite the entire app schema, potentially overwriting any unsaved changes.
Managing Additional Resources
The “Setup” button on the main Fulcrum dashboard screen is used to manage additional Fulcrum resources, including:
- Projects: Projects are used to separate data into different groups. Once projects have been created and permissions granted to members, members can tag a record with one of the created projects. Records can be filtered by projects and only members with permissions to a project can access records tagged with that particular project.
- Choice Lists: Choice lists can be defined directly within a field, or predefined for use across multiple apps. Predefined choice lists can be created manually or from an imported CSV file. Choice options have Label (what the user sees) and Value (value stored in the database/export) settings.
- Classification Sets: Classification sets are similar to single choice fields, but can have nested choices to give a logical grouping or hierarchy to the choices. These cannot be defined directly within the field and must be predefined here. Predefined classification sets can be created manually or from an imported CSV file.
- Layers: Map layers are external map resources, which can be added to the Fulcrum map view. While Fulcrum supports several different layer formats, only the MBTiles and Tile XYZ formats are supported on both the mobile and web platforms.
Changes to these Fulcrum resources require a sync to be pulled down to the mobile clients. Be careful making changes to choice lists, classification sets, and projects which are used in existing apps. If you change or remove an option from one of these resources which are referenced by existing records, the data may not display properly.