Custom Field Options
Control which Inquiry and Evidence custom fields appear in Relay and map Inquiry responses into Monolith case fields.
Relay Custom Field Options control which custom fields are shown to requestors when they submit a request through Relay.
Custom fields can be used to collect additional information from requestors during the intake process. These fields can apply to the overall inquiry or to evidence items included in the request.
Inquiry custom fields can also be mapped to Monolith case custom fields. These mappings allow information submitted through Relay to carry forward when an Inquiry is used to create a new Monolith Case.
When merging an Inquiry into an existing Case, Case-level metadata does not carry forward in the same way. Review important Inquiry Custom Field values before completing the merge and manually update the existing Case when needed.
Custom Inquiry Fields
Custom Inquiry Fields collect additional information about the overall Relay request.
Examples may include:
Legal authority provided
Request priority
Internal department
Case subtype
Requested service type
Special handling instructions
When enabled for Relay, these fields are shown to requestors as part of the request form.
Custom Evidence Fields
Custom Evidence Fields collect additional information about evidence items submitted with a Relay request.
Examples may include:
Device condition
Collection location
Known passcode
Search authority notes
Requested extraction type
Evidence-specific handling instructions
When enabled for Relay, these fields are shown when requestors add evidence items to their request.
Mapping Inquiry Fields to Case Custom Fields
Inquiry custom fields can be mapped to Monolith case custom fields.
This is useful when information collected during the Relay request should become part of the Monolith Case record when the Inquiry is used to create a new Case.
Merge Inquiry does not carry forward Case-level metadata in the same way as Create Case. If the request is being merged into an existing Case, review important Inquiry Custom Field values and update the Case manually when needed.
For example, your Relay request form may include a field called Legal Authority Provided. If your Monolith cases also have a matching case custom field, the inquiry response can be mapped into that case field so the information remains available on the case after intake.
Recommended Setup Workflow
To map a Relay inquiry field into a Monolith case custom field:
Create the Custom Inquiry Field.
Create the matching Custom Case Field.
Edit the Custom Inquiry Field and map it to the Custom Case Field.
Settings > Relay Settings > Custom Field Options
Enable the Custom Inquiry Field for Relay.
When an Inquiry is used to create a new Monolith Case, the mapped Inquiry field value is carried into the selected Case Custom Field.
When an Inquiry is merged into an existing Case, mapped Inquiry Custom Fields should not be assumed to populate or overwrite the existing Case Custom Fields. Review those values before completing the merge and update the Case manually when needed.
Create the Custom Inquiry Field
To create a Custom Inquiry Field:
Open Settings.
Select Custom Fields.
Open the Custom Inquiry Fields section.
Click Create Field.
Enter the field name.
Select the editor type.
Configure any required options, such as selection options for a drop-down field.
Add a description if helpful.
Save the field.
The field description can help requestors understand what information they should provide.
Create the Custom Case Field
To create the matching Custom Case Field:
Open Settings.
Select Custom Fields.
Open the Custom Case Fields section.
Click Create Field.
Create the case field that should store the information from the Relay inquiry.
Save the field.
The Custom Case Field is where the mapped Inquiry response can be stored when the Relay Inquiry is used to create a new Monolith Case.
Map the Inquiry Field to the Case Field
After both fields have been created, edit the Custom Inquiry Field.
To map the inquiry field:
Open Settings.
Select Custom Fields.
Open the Custom Inquiry Fields section.
Find the inquiry field you want to map.
Click Edit.
Find the Case Field Mapping option.
Select the appropriate mapping option.
Choose the Custom Case Field that should receive the inquiry response.
Save the field.
If the inquiry field should not map to a case field, leave the mapping set to None.
Enable the Field for Relay
Creating and mapping a custom field does not automatically make it visible to Relay requestors.
To show the field on the Relay request form:
Open Settings.
Select Relay Settings.
Select Custom Field Options.
Find the custom field you want to show in Relay.
Enable the field.
After the field is enabled, requestors can complete it when submitting a Relay request.
Only enable fields that requestors should see and complete in Relay. Enabled fields are available on the Relay request form.
Example: Legal Authority Provided
A lab may want requestors to confirm whether legal authority documents have been attached to the request.
Example setup:
Inquiry Field Name
Legal Authority Provided
Editor Type
Drop Down Menu
Selection Options
Yes, No
Required
Yes
Description
Have the proper authority documents been attached to this request?
Case Field Mapping
Custom Case Field
Mapped Inquiry Custom Fields can populate corresponding Case Custom Fields when the Inquiry is used to create a new Case.
When an Inquiry is merged into an existing Case, the merge should not be treated as a Case metadata update workflow. Review important Inquiry Custom Field values and manually update the existing Case when needed.
Best Practices
Create the Monolith case custom field before mapping the inquiry field.
Use clear field names that requestors will understand.
Add descriptions when a field needs additional context.
Mark fields as required only when the requestor must provide the information before submitting.
Map inquiry fields to case custom fields when the information should remain part of the case record.
Review enabled Relay fields periodically to make sure the request form stays clear and relevant.
Related Documentation
Last updated
Was this helpful?