Override functionality allows you to change column values and attributes in child tables extended from base tables. For example, a column override changes the default value of the Impact field from Low in the Task table to Medium in the Incident table.
Role required: admin.
How to define a column override
- Navigate to System Definition → Column Overrides.
- Click New and fill in the fields.
- Click Save or Save and Exit to apply changes.
Override example
As an example, you may need to override some column where the base table and the child table are the same. This can help as a workaround in case if you need to change some protected column options before they are changed correctly.
When doing this, please keep in mind that inaccurate changes may harm your system, so check twice, and verify on some testing instance firstly if possible.
To perform such override, fill in the fields as described below:
- Base Table – select a base table.
- Table – select the same table.
- Column – select a column you need to override.
- Specify an attribute you are going to override. These column attributes can be overridden:
- Mandatory
- Read Only
- Display by Ref
- Reference Qualifier
- Dependent on Column
- Default Value.
- Specify new attribute value.
- Click Save or Save and Exit to apply changes.
To be more specific, have a look at the screenshot below. It shows the Mandatory attribute overriding of the IT Service column related to the Agreement table.
Defining an override for choice fields
When creating a field of the Choice-like type (for example, Choice), it is recommended to set text values in the Value field to increase code readability. For example, it can be Incoming, or Active, or Failed values.
Regarding task states, it makes sense to make values numerical. This can help with selection construction.
