Store Storable
Figure 1: Store Storable The Store Storable object is a Modeling Block to store a Storable instance. Dragging a Store Storable into a Workflow you can configure an instance of Data Type xnwh.persistence.Storable that shall be stored during the Workflow's execution.
It is also possible to change existing instances.
To insert a Store object into a Workflow, drag the Store Storable symbol 
out of the icon bar.
The Store Storable has two Input Parameters:
- Storable: Parameter for the Storable instance, that has to be stored. You can configure the values of the instance inside of a Mapping or by setting a constant, for example.
-
Store parameter: These parameters define how to deal with historization, referenced objects and others at storage.
-
Historize previous object: Can take the values true or false and indicates whether an already existing version of the passed instance shall be historized (backed up). The existing instance will then be marked as obsolete (Current Version Flag = false) and the new instance will be marked as current (Current Version Flag = true). The default setting is false (i.e. Historize previous object = false would override an existing instance, that would no longer be available then).
Please note: Only takes effect for Data Types flagged as Use historization (cf. Historization). - Keep meta field data: Can take the values true or false. This field specifies if meta data (e.g. Historization Time Stamp), which are normally assigned automatically, shall explicitly be overridden with own data. The default setting is false (for an example see below).
-
Force recursive store: Can take the values true or false and predetermines how to deal with references to child objects.
Set to false, data in referenced child objects are not overridden during set-up or modification of the parent object – even not if content for Member Variables of the child object is defined.
Set to true, all Member Variables of the child object are overridden – also if they are undefined.
The default setting is false.
-
Historize previous object: Can take the values true or false and indicates whether an already existing version of the passed instance shall be historized (backed up). The existing instance will then be marked as obsolete (Current Version Flag = false) and the new instance will be marked as current (Current Version Flag = true). The default setting is false (i.e. Historize previous object = false would override an existing instance, that would no longer be available then).
Modifications shall be made in a historized version (e.g. a status update). An appropriate Query Storable provides the searched instance including Historization Time Stamp and Current Version = false. The requested modifications are made and the instance shall be stored into historization again. If Store Storable was executed with Keep meta field data = false, the stored instance would automatically be set as new current version (Current Version Flag = true), what is not desired. Storage with Keep meta field data = true however leads to the desired result: The meta data submitted to Store Storable (i.e. the previously read out Historization Time Stamp and Current Version Flag = false) remain and are not overridden automatically.