We use iiQ Events for facility and building scheduling. Our building directors rely on the built-in Description field for event setup instructions, including room configuration, tables/chairs, equipment needs, and other preparation details.
Currently, the Description field is optional and appears to be a locked system field, so we cannot make it required. This creates a workflow issue because users can submit an event without providing the information the building director needs to prepare the space.
We would like administrators to have the ability to mark the built-in Event Description field as required, either globally or through an event type/template.
A required custom field is not an ideal workaround because our existing building-director workflow already uses the built-in Description field.
Requested enhancement:
Allow iiQ administrators to configure the Event Description field as required before an event can be submitted or saved.
