Oomnitza allows for many degrees of customization. We've already looked into some of this when we configured Roles, set up the dashboard, and set up screens in the Mobile App. Now, we're going to look into how fields can be customized, and how to bring roles and screens together to afford complete control over asset access.
- The Customization Screen
- Screen Builder
- Customize Fields
The Customization Screen
All modules in Oomnitza allow customization of the fields available within the module. This allows for precise management of countless things. Instead of relying on Oomnitza to provide the appropriate fields, you can add your own to accommodate all of your most important data, and protect who has access to it.
The screen builder allows you to control exactly what fields each role has access to. To access the screen builder, navigate to the module of your choice, and navigate to "Customization". By default, you'll be taken to the Screen Builder, but if you find yourself on the Customize Fields screen, you can get back to the Screen Builder by clicking Screen in the upper right.
In the center of the screen select the role you wish to modify permissions for, make sure the second selection is on "Web," then click "Next" in the lower right.
Clicking next on the welcome screen will take you to a familiar-looking screen that mirrors the detailed asset screen you'd see when viewing, editing, or adding new assets.
Based on the role you selected, this screen allows you to toggle on and off the specific fields that they're able to see, and also allows you to change the default order of those fields.
Take note that if a role has the ability to customize a given module, they'll also be able to customize their own screens and the screens of others.
Once you've configured the fields to meet the needs of the role, click "Go Live!" to commit the changes. Users should see the changes applied upon their next login.
The second aspect of customization is the ability to add and edit fields in Oomnitza. Because Oomnitza can effectively track and manage anything that's uniquely identifiable in some way, it's important that you have the ability to track any element of that thing.
To add a new field, click "Add" in the upper right of the page, and you'll be presented with the following screen:
There are tabs for Information, Dropdown, and Relational Fields. Their functions are detailed below.
Name: The name under which the field appears.
Data type: What kind of data the field allows. The options are as follows:
- Short Text - Allows the user to enter text up to 256 characters.
- Long Text - Allows the user to enter text up to 1024 characters.
- Numeric - Allows for entry of integers up to 20 digits.
- Decimal - Allows for entry of decimals.
- Date - Allows for entry of dates, gives a date box when clicked.
- Checkbox - Allows for a checkbox or boolean field.
- Users List - Provides a list of users.
- Location - Provides a list of locations.
Editable: Determines whether or not the field is editable by the user. Uneditable fields can only be modified via the API or by a connector.
Unique: Forces data entered in the field to be unique.
Mandatory: Forces the user to enter something in the field before they're able to save or create the object.
Dropdown: Only available for short text fields. Will make the dropdown field available so you can use the newly created field as a dropdown.
Default Value: Allows you to set a default value for a field upon the creation of a new object.
If you've selected a short text data type, and indicated that the field is a dropdown, you'll subsequently be given access to a dropdown tab.
You can use this field to create either dynamic or enforced dropdowns.
Dynamic Dropdowns are created by checking the dropdown box on the previous page, then leaving the "Enter Options" field empty on the dropdowns page. Options will be added to the dynamic dropdown as other users set new options when creating and editing objects.
Enforced Dropdowns are created by entering specific options in the field on the dropdown page. If these were entered when customizing a field, only these options will be available and required, when filling in the dropdown.
Relational fields are a powerful tool that lets you specify that a field should appear only if another criterion has been met. For example, you could have fields that only appear for laptops, or for mobile devices, or possibly have fields that only appear at certain locations.
Relational fields can be created from any enforced dropdown field, or from fields that use Locations in Oomnitza, so you're free to create your own complex relations using custom fields.
If you've been going through Oomnitza's getting started guide, then you're probably beginning to notice that everything is coming together. You've learned how to use the general functions, and how to tune them for your organization. There are many advanced things Oomnitza can do, but for now, all that's left is setting up your Oomnitza Integrations —>