Usage as Dynamic Enumeration

It is possible to use lookups as enumeration for fields outside of the characteristic and characteristic value entities.

You have to create a new enumeration in the custom area of the repository provided with the enum param "lookupIdentifier" and add it to the desired field as usual. Then you have to create the enum entries respectively lookup values in the UI and you're good to go. The order in which you do these two steps doesn't matter.

For a more detailed explanation see "Lookups aka Dynamic Enumerations" in the Customization Guide which is also part of the SDK

Maintenance in Desktop UI

Lookups and their values can be created, edited and deleted in the Product 360 Desktop UI.

Lookups are maintained in the Lookups perspective.

Lookups have a

• unique identifier

• label

• description

• label pattern

The label pattern will influence the representation of lookup values when used in a drop down list. Options are:

• Name

• Code

• Code - Name

• Name (Code)

Lookup values have a

• unique code (in the lookup)

• label

• description

• external code
  The external code is system specific and allows to reference the lookup value with different names. This comes in handy when you have multiple different external systems (like GDSN) that have their own names for something in your system.

• order

• state (active or inactive)
  The active state defines the visibility of the lookup value when used as value list on a field.

Referential Integrity

The deletion of lookups is prohibited when the lookup is used as enumeration outside the characteristics or when it is referenced from the characteristics.

Lookup values can not be deleted if their corresponding lookup is used as enumeration in the repository outside the characteristics, or when the lookup value is referenced by either the characteristic model or a characteristic record.

The code of a lookup value can not be modified when the lookup is used as an enumeration in the repository with String as key class.
In this case the code of a lookup value is actually stored inside of another entity and you no longer can change this code. You would need to deactivate and lookup value and create a new one.

Maintenance in Web UI

Lookups themselves can only be maintained in the Desktop UI. Lookup values can be maintained in the context of the selected lookup also in the Web UI.

They can be created and deleted by means of the Action menu of the Table View. Editing and activation/deactivation can be performed in the Lookup value details view of the selected lookup value.

Access rights

Lookups and lookup values are protected by the following set of access rights:

Initialization of repository based lookups

There are some enumerations with a new enum param named "lookupIdentifier". One of these is the Enum.CharacteristicPurposes

As you can see, it is defined as any other enum with some enum entries.

During the server start, the server checks if there is already a lookup with the defined "lookupIdentifier" in the system. If it is already existent no further action will be done. In case it is not existent, a new lookup with the given identifier will be created and all active enum entries will become (active) lookup values in this lookup.

You can add the enum param to your own enumerations as well.

Data model