Precedents
The precedents grid allows to determine which are the objects that a specific Deyel object needs to execute.
The analysis of precedents is very useful to determine which objects are necessary for the Deyel selected object to execute correctly. Also, it allows to determine which objects are required to perform a complete export.
It may happen that one or more precedent objects are not found in the environment. In this case, the row is displayed in red with a warning icon.
Precedents may belong to the same object application or to other applications. Precedents show returns all precedent objects without applying security. It is possible that a user does not have permissions to see an object, but that does not prevent them from seeing the object as a precedent of another to which they have permission. The precedent objects on which the user does not have permission are displayed in the precedents grid without the possibility of executing any function on them (open, modify, export).
The precedents grid is very similar to the object's grid, but it has the following special features:
•The possibility of saving favorite searches is not available, as it is not necessary.
•In the event that a precedent is not found in the environment, it is displayed in red, with a warning icon and with the label “Nonexistent Object”. In this way, it is possible to determine which are the missing precedents of an object.
•It has 2 additional filters.
Additional Filters
The additional filters are "Level" and "Definition", they must always have a value and cannot be left blank. For this reason, the individual option to remove the filter is not available. However, you can use the option to remove all filters, which in the case of additional filters returns them to the initial value.
Level
It allows to filter the precedents of:
•1st Level: this value is taken as the initial value.
•All Levels: it is a recursive precedence.
Definition
It allows to filter the precedents of:
•Development: this value is taken as the initial value.
•Execution
The concept of definition is different from the concept of state. The concept of state of a Deyel object indicates the stage of development it is in and if it is operational. On the other hand, the concept of definition allows objects to be modified without affecting the execution version of the object that is operational.
Internally, Deyel objects have 2 definitions: development and execution, which is completely transparent to users. The development definition is the one used when modeling an object, while the execution definition is the one that is operational.
If an object is in the "Modified" state, it means that the development definition may be different from the execution definition. This means that a Deyel object can be modified without affecting the execution definition. As both definitions are different, precedents can also be different.
If an object is in the "Published" state, it means that the development definition and the execution definition match. This means that the object was modeled and is in use. So the precedents of both definitions are the same.
In this way, both definitions coexist, to allow new developments without affecting the published object that is operational. When an object is published and a change is made operational, the execution definition is updated with the changes coming from the development definition, making both definitions identical.
