Values Constraint
NOTE: All relations between Properties and Values have to be documented in the table properties_values. They are global changes, i.e. the relation is valid in whichever context the Property is used. The Constraint-function gives you the possibility to make a local change. Global change means that a Value is assigned to or withdrawn from a Property in any context, i.e. class where the Property is used. Local change (constraint) means that a Value is only assigned to or withdrawn from a Property in the context of a certain class.
Example 1: A BOOLEAN Property always has the same Value List in any context {true; false} for every Property assigned to any Class. A constraint cannot be applied to a BOOLEAN Property, as the Value List cannot be limited.
Example 2: A Value List of {red, green, yellow} might be valid for a Property “color of traffic lights” for a Class “car traffic light”. But maybe it should be limited (“constrained”) for the Property “color of traffic light” in the context of the Class “pedestrian traffic light” to only {red, green}.
Each line is the relationship of one Property to one Value for one Class. If you would like to limit Values of a Property in a specific Class, you have to fill out x lines for each Value with the same Property identifier and the same Class identifier. If you would like to activate a Value that was once constrained, you have to fill out x lines for each Value with the same Property identifier and the same Class identifier. The connection is related by either the id_class_non-existing (if Class is new) or id_class_existing (if Class is existing) of the Class and either the id_pr_non-existing (if PR is new) or id_pr_existing (if PR is existing) of the Property and either the id_va_non-existing (if VA is new) or id_va_existing (if VA is existing) of the Value.
NOTE: All relations between Properties and Values have to be documented in the table properties_values first. If a relation was not defined in that table, then no constraint can be defined either. In this case every Value of the used existing property will be shown. A constraint can only be placed on an existing relation that is documented in table properties_values.
ENABLE VA
ENABLE VA = A VA (new or existing) shall be related to a PR (new or existing) in the context of a certain Class (new or existing).
Mandatory fields:
| CR type | ENABLE VA |
| id_class_non-existing or id_class_existing | in case of a new CC, insert the unique internal ID mentioned in table Classes or the 8-digit CR ID in case of an existing CC, it is the 6-digit identifier |
| class coded name | 8-digit ECLASS identifier |
| preferred name class | the CC’s name |
| id_pr_non-existing or id_pr_existing | in case of a new PR, insert the unique internal ID mentioned in table Properties or the 8-digit CR ID in case of an existing PR, it is the 6-digit identifier |
| preferred name PR | the PR’s name |
| id_va_non-existing or id_va_existing | in case of a new VA, insert the unique internal ID mentioned in table values or the 8-digit CR ID in case of an existing VA, it is the 6-digit identifier |
| preferred name VA | the VA’s name |
| CR Proposer | CDP user name |
| Reason for request | Your reason for the change |
DISABLE VA
DISABLE VA = The existing relation between a CC, a PR and a VA shall be deleted
Mandatory fields:
| CR type | DISABLE VA |
| id_class_existing | the 6-digit identifier mentioned in table Classes |
| class coded name | 8-digit ECLASS identifier |
| preferred name class | the CC’s name |
| id_pr_existing | the 6-digit identifier mentioned in table Properties |
| preferred name PR | the PR’s name |
| id_va_existing | the 6-digit identifier mentioned in table Values |
| preferred name VA | the VA’s name |
| CR Proposer | CDP user name |
| Reason for request | Your reason for the change |
NOTE: The EXCEL Sheet provides the possibility to choose between ENABLE and DISABLE VA. In case only a few Values of a long Value List are valid for a certain Class, then it is easier to name only those Values that shall be valid, i.e. ENABLED. Then please fill out one line ENABLE VA for each Value that is valid. This is the preferred Change Request type as you most certainly know better the valid Values.
Example 1: ENABLE VA
Class “pedestrian traffic light” (CC01)
Property “colour” (PR01)
Value list {red (VA01), yellow (VA02), green (VA03), blue (VA04), pink (VA05), white (VA06), brown (VA07)}
Red and green shall be the only valid Values.
Two ENABLE VA Change Requests are necessary:
ENABLE VA CC01 PR01 VA01
ENABLE VA CC01 PR01 VA03
In case most of the Values of a long Value List are valid for a certain Class, then it might be easier to name only those that shall be invalid, i.e. DISABLED. Then please fill out one line DISABLE VA for each Value that is invalid. The database knows only ENABLE VA and will automatically create ENABLE VA for all Values that are not listed with a DISABLE VA line.
Example 2: DISABLE VA
Class “light bulb” (CC02)
Property “colour” (PR01)
Value list {red (VA01), yellow (VA02), green (VA03), blue (VA04), pink (VA05), white (VA06), brown (VA07)}
Brown shall be the only invalid Values
One DISABLE VA Change Request is necessary:
DISABLE VA CC02 PR01 VA07
(The database will automatically create ENABLE VA Change Requests for all other Values.)