The custom field section of admin settings allows admins to decide what fields to show. Map your custom fields to objects in the data model and choose when and where they are visible to schedulers and mobile users.
To view all the custom objects and fields defined in your web app, open Settings -> Data objects.
To create a new custom object:
-
Click the "Create custom object" button to launch the "Create Custom Object" modal.
In the following example, a text field will be created so that a resource or scheduler can record "the cause of the problem."
-
Click the "Create" button to launch the "Create Custom Field" modal.
-
From the options available, select "Text" then click "Next."
-
Select an object from the "Object" picklist. Here use "Jobs."
-
Complete the required fields highlighted red:
-
Enter a field name.
-
Enter a field label (this appears in both the job details views in the web app and the mobile app).
-
Option: Provide a meaningful description.
-
Enter the maximum number of characters (a numeric value up to 255).
-
-
Pick the display settings—choose where the field will be shown from the options available (multiple selections are permitted):
-
Show on Desktop.
-
Show on Mobile.
-
Editable on Mobile.
-
Required on Mobile.
-
-
Click "Save."
Each custom field is made up of the following properties:
Table 25. Custom field properties and their descriptions.
|
Property |
Description |
|---|---|
|
Object. |
An object from the Skedulo data model. |
|
Field Name. |
A name used to identify the field within the object. |
|
Field label. |
The display used whenever the field is shown in the app. |
|
Field type. |
This identifies the data type of the field. It will determine how the user can interact with the field within the rest of the app. See table 2 for details. |
|
API Name. |
This is the name given to the field by Skedulo. This value cannot be changed. |
|
Display Settings. |
These settings dictate whether the field will be visible on the mobile and desktop versions of the app. It also determines if the field is "required" as well as allowing the resource to edit the field when using the mobile app. |
Table 26. Custom field types and their descriptions.
|
Field Type |
Field Description |
Additional Fields To Define |
|---|---|---|
|
Text. |
A standard text field. |
Field length—set field length (up to a max of 255 characters). |
|
Text area (long). |
A long text field allowing line breaks. |
Field length—set field length (up to a max of 131,072 characters). |
|
Number. |
Enter any valid number (including decimals). |
Set field length and decimal places (requires a precision value and decimal points value). |
|
Date. |
Enter a date or pick a date from a calendar pop up. |
N/A |
|
Checkbox. |
A standard checkbox that can be selected (true) or deselected (false). |
Set the default behavior for the checkbox. Selected by default (Y/N). |
|
Picklist. |
Select a single value from a pre-defined list of options. |
Add picklist values. |
|
Picklist (with multi-select). |
Select one or more values from a pre-defined list of options. |
Add picklist values. |
|
URL. |
Enter a website URL. |
N/A |
|
Time (beta). |
Select the time of day from a picker (in 15-minute increments). |
N/A |
|
Lookup relationship. |
A lookup for a field in a related object. |
Object—set object. |
Using the "Display Settings" an admin can mark a custom field as "required." Doing so will automatically make that field editable on the mobile app, and the job cannot be completed until the field has been populated and saved.
Comments
0 comments
Article is closed for comments.