A collection of values that can be utilized as content in UI components or templates is managed using enumerations. Values can be defined for certain source systems or languages.
On the main screen inside Enumerations, you have the following elements:
Name - the name of the enumeration
Version - the version of the enumeration
Draft - switch button used to control the status of an enumeration, could be Draft or Published
Last Updated - the last time an enumeration has been updated
Open - button used to access an enumeration to configure it/ add more values, etc.
Delete - button used to delete an enumeration
New enumeration - button used to create a new enumeration
Breadcrumbs - Import/Export
For each entry (when you hit the Open button) inside an enumeration we have to define the following properties:
Code - not displayed in the end-user interface, but used to assure value uniqueness
Labels - strings that are displayed in the end-user interface, according to the language set for the generated solution
External source systems codes - values that are set for each external system that might consume data from the process; these codes are further used by connectors, in other to send to an external system a value that it can validate
Enumerations can also be defined as a hierarchy - for each entry, we can define a list of children values (for example, name of the countries defined under the continents’ enumeration values); hierarchies further enable cascading values in the end-user interface (for example, after selecting a continent in the first select UI component, the second select component will contain only the children of this continent).
Enumerations, for instance, can be used to build elaborate lists of values (with children). Assuming you wish to add enumerations for Activity Domain Companies, you can create children collections by grouping lists and other related domains and activities.We have the following example for Activity Domain Companies: