Notes on Assigning of Init Values for Attributes
When working with HELiOS, there are various ways and possibilities to fill in database attributes and corresponding fields of the interface with init values.
For example, you can use the possibility of individual initialisations of fields in masks via the Mask Editor:
Attribute fields can also be initialised with automatically transferred entries during operations such as indexing or derivation, which you can set via the Attribute Editor.
Through corresponding settings in EDBSETUP, attribute fields can also be initialized via action lists.
Therefore, it is important to observe a prioritisation sequence in which already initialized attributes may be overwritten by the automated initialisation of another action.
The following list should be read in such a way that the next step can override the previous one:
-
Initialisation in the Mask Editor
-
Initialisation by content of an original object during indexing or derivation, definable in the Attribute Editor
-
Initialisations through attribute assignments, e.g. by exporting documents or output by the Spooler.
-
Action list initialisation using EDBSETUP
-
External initialisation, e.g. through API functions or indirectly from interfaced applications such as HiCAD
-
Initialisations by customer-specific KST modules, if corresponding adaptations of HELiOS exist.
-
Initialisations of certain attributes determined by HELiOS, such as the creation date or the creator of a data record.
-
Restrictions and initialisations by the attribute links.
This means: Initialisations manually assigned in the mask editor for certain fields can possibly be overwritten, a certain automated initialisation is provided in the Attribute Editor for a certain operation in which a new object emerges from the original one, or if a certain initialisation is set in a certain workflow step. In turn, a workflow action list of EDBSETUP may also override initialisations by the attribute editor or from set attribute assignments. Attribute assignment with an external application such as HiCAD may overwrite initialisations previously set by HELiOS. While certain data, such as dates and user credentials set during creation, are fixed, changes written to database fields by KST functions can in turn overwrite contents also initialised by HELiOS.
Other user initialisations are not captured, they are updated by attribute mapping or attributes changed by the workflow.
