Introduction
With the correct permissions, you can create (add, edit, delete) custom attribute fields on rooms. These attributes can be visible to requestors if the "visible to requestor" checkbox is checked on the custom field definition.
Custom Fields can be added on rooms platform-wide. One use case for iiQ Events is that custom fields make it easier for event requestors to identify the best room for their event and save time for Admins by having information included in the room/location details instead of having to answer requestors' questions about this info manually, over and over again.
Custom Field Definitions
The first step in creating a custom field involves setting up a field definition. These ensure that the custom field that is created contains the type of data that the user would like to capture.
To create a new Custom Field, navigate to Administration > Custom Fields, click the Field Definitions tab, and + New Custom Field.
The required and optional fields for a New Custom Field Definition are listed below.
Name | Required | Display name of the field |
Description | Optional | Short description for added context |
Field Type | Required | Type of field to be displayed such as text, number, or on/off |
Contains Sensitive Info | Optional |
|
Required | Optional | Identifies if the field must be filled out for the Event to be saved |
Requestor Visible | Optional | Determines if the field will be displayed when requestors are searching for a room. |
Number of Instances | Required | This field will default to one |
Once complete, and Save is clicked, the New Custom Field Definition will be listed in the available field definitions.
Pagination and Search are available on all tabs on the Custom Fields page. Search makes created fields easier to locate—you can search for anything in a field definition name. For Pagination, the default number of fields per page is 100, but you can choose 10, 20, 50, 100, 200, or 1000 in the dropdown.
Creating Field Definition Groups
Once a field definition is created, it will need to be enabled. Currently, Incident IQ supports six types of custom fields:
Tickets: Applied to the ticket submission process to capture relevant data for agents or relay pertinent information to requestors
Assets: Applied to an asset’s details page and are editable by any user with the appropriate level of permissions
Users: Found in the profile section of a user’s profile page
Parts: Applied to any of the parts in the part list
Events: Applied to the Event Registration Ticket to capture relevant data for Approvers and to pass on for work order creation.
Rooms: Applied to the Room page to capture relevant information for the Room.
To enable a Custom Field in a Room, navigate to Administration > Custom Fields, click on the Rooms tab, and select Add Field with New Conditions.
A new window will be displayed, allowing the user to select the definition to be enabled.
The definition field will appear in a new section underneath the Custom Fields column. One or more definitions can be added as a group that shares the same conditions by clicking Add Field.
To narrow down where this custom field appears, add a condition(s). Click Add Condition, select a filter category, and narrow it down to the condition for that group. Click Save Filter, and the new condition will appear under the Conditions column.
After applying a custom field to rooms, it will be visible at the bottom of the Room Details page. If some conditions/filtering were applied, then it will show only on those rooms that fall under those conditions.
Deleting custom fields can severely impact the designed workflows utilizing them.
Removing custom field mapping will remove it from view, but it can be resurrected by re-mapping the custom field to the entity where it lived.
---
Hannah Bailey - Director, Customer Engagement