It states "inheritance + additivity" for "fields".
Now, I assume this means it will inherit fields and it's possible to add new ones.
But is it also possible to be more strict?
Use case:
In our production environment, I'd like to reverse "Caller" and "Organization" - only for UserRequests. New colleagues usually don't know to which organization a person belongs; so they would look up this person and then select a pre-filtered org_id list (which will only contain one item. This as a work-around for the fact that I can't change org_id to become an AttributeExternalField, since it inherits the AttributeExternalKey type from Ticket).
I'd rather not have to change this for Incidents and Changes
Update: actually I realized it's probably not possible any way since it also inherits the dependencies from higher classes.
Last edit: Jeffrey Bostoen 2021-10-20
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Jeffrey,
No, it's not possible to modify the definition of a field attribute defined in a parent class. Some of the current changes that are required are the filter, sometimes the default value. The only thing which can be overwritten is the label.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I checked https://www.itophub.io/wiki/page?id=latest%3Acustomization%3Aclass_properties_inheritance
It states "inheritance + additivity" for "fields".
Now, I assume this means it will inherit fields and it's possible to add new ones.
But is it also possible to be more strict?
Use case:
In our production environment, I'd like to reverse "Caller" and "Organization" - only for UserRequests. New colleagues usually don't know to which organization a person belongs; so they would look up this person and then select a pre-filtered org_id list (which will only contain one item. This as a work-around for the fact that I can't change org_id to become an AttributeExternalField, since it inherits the AttributeExternalKey type from Ticket).
I'd rather not have to change this for Incidents and Changes
Update: actually I realized it's probably not possible any way since it also inherits the dependencies from higher classes.
Last edit: Jeffrey Bostoen 2021-10-20
Hi Jeffrey,
No, it's not possible to modify the definition of a field attribute defined in a parent class. Some of the current changes that are required are the filter, sometimes the default value. The only thing which can be overwritten is the label.