What is the convention for saving an enumeration to the reference architecture? Do you need to put N_ in front of it?
The reason I ask this is we had an enumeration called MigrationInsurancePropertyType which was not produced before. We used this enumeration in expression fields.
Later someone produced this enumeration and put N_ before it. Now all our expression fields which use this are wrong. Was the developer supposed to not put N_ before it? What is the convention for producing enumerations?
The following is taken from the training that is required before being allowed to request changes to the reference architecture:
Name starts with N_, followed by NameInPascalCase. The name is in English and may contain A-Z and a-z characters, and if necessary spaces and (braces).
A logical name that describes the values of the enumeration as a group is preferred. If that is not possible, and the number of values is limited (max. 3), the values may be concatenated to form the name of the enumeration (e.g. N_DebtorCreditor).
Only use enumerations for sets of values that are immutable. Once a reference architecture enumeration is used, it cannot be expanded.
The names of the values are free form, as long as they are in English and understandable in the context of the enumeration name.
These rules relate to the name of the registered name of the enumeration in the reference architecture. As with concepts, that is not how they should be named within the component. In the component they should have proper, translated names. Many examples for well-known enumerations are provided in the guidelines at Home | Inloggen. It is best practice to follow this pattern for all enumerations.
Ok thx for the documentation. This means that when you create an enumeration and use it in expressions it is fine. That is unitll you produce it, put N_ before it, then you need to go through the database to fix all those expressions? Sounds like an unwanted way of working…
No, there is no need to change the name of an enumeration in the component when mapping it to a reference architecture enumeration. As I mentioned above, the rules relate to the name of the registered name of the enumeration in the reference architecture. As with concepts, that is not how they should be named within the component. In the component they should have proper, translated names (probably like you named it before).