The settings for the regular requests feature can be found under Global Settings → Requests → Regular Requests. Only users with administrator permissions can access these settings; other users can only access them if they have the relevant permissions. The settings allow you to customise the generation process itself and also include the option to extend the regular request form with custom fields.
The basic settings include the following parameters:
- Generate in advance – when enabled, requests are created in advance, before the date on which they are scheduled to be generated. Furthermore, when ‘Generate in advance’ is enabled, the combination of the ‘According to schedule’ and ‘According to parameter’ settings is treated solely as the ‘According to parameter’ option.
- The ‘Number of days’ field determines how many days before the scheduled generation date the request should be created. For example, if the value is 30, the request will be created 30 days before the scheduled date, rather than on the day of generation itself. This means that upcoming requests are visible in advance, allowing time to prepare for them.
- Include a serial number for the year in the name – when this option is enabled, a serial number in the format (year/order) is added to the end of the generated request’s name. The order indicates the order in which the request was generated from the given rule in the relevant calendar year. At the start of a new year, the counter resets. This order number is independent of the request number (ID) and the configured request numbering format — it is added separately to the name. Example: a regular request named ‘Monthly server maintenance’ will generate requests with the names ‘Monthly server maintenance (2026/1)’, ‘Monthly server maintenance (2026/2)’ etc., whilst in the new year the numbering will start with ‘Monthly server maintenance (2027/1)’. If you leave this option disabled, the name will remain without a suffix, i.e. simply “Monthly Server Maintenance”.
- Maximum quantity of CIs automatically attached based on a condition – an option to limit the quantity of CIs attached to a request once the condition of generation is done
Custom fields on a regular request
In the ‘User-defined fields’ section, you can add custom fields to the regular request form. To add custom fields, click the ‘+ Add custom field’ button at the bottom of the settings page.
Recommendation: Consider whether the selected custom fields should be included in all regular requests. Fields assigned in this section (in the global settings) will be added to every regular request. If you do not need them in all requests, do not include them here, but assign them individually to specific regular requests.
Clicking this opens a new window containing a list of custom fields stored under the CMDB configuration database module. Next to each property is a tick box which you can use to select the required property. You can add the selected properties by clicking the ‘Assign Selected’ button. If the list does not contain the property you require, you can also define it directly in the property selection window using the ‘+Simple Custom Field’ and ‘+Complex Custom Field’ buttons. Selecting the +Simple Custom Field option creates a basic property. Use the +Complex Custom Field button to add a complex property that contains several basic properties.
Customising custom fields on a regular request
The selected fields will be added to the Custom Fields list. The fields will appear in the request form in the same order as they are included here. You can change the order of the items by dragging the 
icon. To delete any custom fields you have already added but no longer wish to use, click the Delete button, which can be found in the context menu 
in the row of the relevant field. Using the Edit button in the context menu, you can edit the values directly whilst creating a new request template record.
Above the list is a search bar, which makes it easy to quickly find a specific field. There are also buttons here for customising the list presentation. If the list of custom fields on a regular request is too long and no further property configurations are required, you can apply the Location option. Ticking this option hides the settings and displays only the field names and the icon for changing the order. Ticking the List with settings option will once again view a detailed list of settings for individual custom fields.
You can configure any of the custom fields in the list as you wish. The following options are available:
- View collapsed – if this option is ticked, the entire field will not be displayed in the request form; only the tick box will appear. The field will expand once this box is ticked.
- Required field – if you tick the Required field option, the field in question will be selected as mandatory on the request form. You will not be able to save the request unless you complete this field.
- Multiple values – if you tick this option, you will be able to fill in the field more than once. Selecting this option will make the Limit field available, where you can set a limit on the quantity of entries.
- Subject to approval – allows the value of the selected custom field to be subject to approval. Once ticked, an icon will appear next to the field, which you can use to set the approver. This requires the template to have an approval rule assigned from the Dynamic Requirement Approval Based on Custom Fields group. For details, see the section on Setting up requirement approval via custom fields.
- View in the request list – ticking this option allows you to view the relevant custom field as a separate column in the request list.
- Pre-fill – allows you to define a value that will be automatically pre-filled when you open the form to create a new request from a template.