In the Desktop Client, each form section displays the data containing EnumIsDisabled values in different ways. Some data may not be propagated throughout the system depending on the form type selected. Specific considerations for each form section are listed include the following:
-
Create forms suppress the display of all disabled UoMs or enums from menu lists, even if the default enum or UoM value is set to a disabled value.
-
Details forms allow the display of values containing disabled UoMs or enums so that data loaded with these values can still be reviewed.
-
Query forms allow the display of all disabled UoMs or enums so that these values are still visible as part of a query.
-
Update and Copy forms suppress all disabled UoMs or enums, except when a disabled value is used by the object being updated. For example, if a UoM is disabled, but the object uses it for a weight value, then it will be available until the value is changed. This also allows new instances of the disabled entry to propagate further in the system by copying an object that uses the disabled enum or UoM.
-
The object displays the current value, even though it may be flagged as disabled, but other disabled values in the same list are suppressed.
-
If the disabled value is cleared from a box or if a value is changed from a disabled entry to a different entry, the disabled entry remains in the list until the form is closed.
-
-
List Edit windows display any properties scoped by a disabled UoM or enum value with the same behavior as Update forms, except the drop-down columns show any disabled values that are used for any of the objects. This exception is a technical limitation.
-
Read-only columns support the display of any disabled UoM or enum.
-
Editable columns do not include disabled entries in the list.
-
The available entries for the same property can vary from row to row, based on whether different disabled entries are consumed by each data row.
-
A row that currently uses a disabled value is able to be updated with a different disabled value if that disabled value appears in the list.
-
You can view the enums in a List Edit window and disable them, but there is a condition on the List Edit to exclude enums and UoMs that originated in the integration schema.
-
List Edit windows for UoMs behave the same way as Update forms, but if you change an entry from a disabled UoM, it is no longer available. The UoM drop-down menu list shows only the disabled UoM used by an object on a specific row.
-
-
Datasheets do not allow the display of values containing disabled UoMs or enums. Any property that still uses a disabled value retains that value, but no property can be updated to use a disabled value.
-
If a disabled enum or UoM is defined as a default value for a display item, that display item will be blank when displayed on a form.
-
If an enum item is disabled when used in the structure behind a classification tree, such as on a branch node or leaf node, then the disabled flag will be ignored so that the necessary relationships to the classification tree are supported.
-
Where display items are scoped by corresponding levels of an enum hierarchy, if the parent level enum is set as disabled, the setting is not propagated to any child values, but they will not appear on the form.