deserialize map/list(a,b,c)
|
Group |
This function can be used to deserialise maps (Named Map objects) and lists (Named List objects) that have previously been serialised with function serialize map/list(a,b).
Serialisation practically only means that objects are put into a form that allows these objects to be transferred to another place (e.g. another profile). There, these objects can then be restored (deserialisation).
Note: The concept is not intended for mass data.
Parameter Description
|
Parameter |
Description |
|
a |
The serialised data. See function serialize map/list(a,b). |
|
b |
Name of the map or list to be deserialised. |
|
c |
(optional) If true, the deserialised entries of maps and list are appended to already existing maps and lists with the same name, otherwise they are emptied beforehand. Default: false. |
Example
Please import the following two profiles and set them active: Profile-serialize.pak, Profile-deserialize.pak.
In profile serialize, the map mymap (with one entry) is serialised. The serialisation data is stored in variable var__SERIALIZED_DATA. The profile then calls the second profile deserialize via Message.
In the second profile, the variable MSG_CALL_var__SERIALIZED_DATA (passed via Message from profile serialize) is read, the deserialisation is executed and the entry is read from the map.
Automatic Serialisation/Deserialization
Serialisation and deserialization can also be carried out automatically.
If a new profile is created, the system variable VAR_AUTOSERIALIZE_DATA is automatically created (otherwise please create it manually in both profiles).
If you use the prefix autoserialize_ in names of maps or lists, they are automatically serialised (in the source profile) and deserialized (in the target profile).
Please import the following two profiles and set them active: Profile-auto_serialize.pak, Profile-auto_deserialize.pak. Important note: If you use automatic serialization and deserialization, you do not have to create the described system variable in either the calling or the called profile. In addition, the MSG_CALL_ prefix does not have to be used in the subsequent profile and no explicit deserialization has to be performed. You therefore always have direct and immediate access to automatically serialized maps and lists in the subsequent profile.
For using autoserialization/autodeserialization in workflows, see section Variables (Workflows).