Calculation fields, maps/lists in source structure, serialized maps/lists

Calculation fields are not used for data output, but, as the name suggests, for calculating variable values and filling lists and maps. And since calculation fields have a value, you can also use them as parameters in functions. Outsource more complex calculations to calculation fields, making your target structure clearer.

Example 1

Profile-Init_node.pak

Example 2

In the previous example, we built a list and a map in a calculation field and then used them in the path of a node in the target structure to read out the data. In the following example, we now read in a list in a special node in the source structure.

Profile-copy_list_to_source_tree.pak (optionally set parameter d in function copy list(s) to source tree() to true.)

Example 3

If you do not want to use a generated list or map in the same profile, you can serialize them and pass them to a subsequent profile, a subprofile or a called workflow and use them there. We show this in the following example with a called subprofile and the autoserialization mechanism.

Profile-sub_profile_copy_deserialized_list_to_source_tree.pak (import first)

Profile-call_sub_profile_with_serialized_list.pak

Profile constants

Profile constants are a really convenient feature. Here, you can store a constant value with a description, which you can then simply select, just like a variable name. They are very practical if, for example, you want to use the same list in multiple functions. You can store the name of the list as a constant, and then there is no need for you to constantly remember the name and exact spelling. This also reduces possible typos. If you need to change the list name, you only need to do it once in the constant.

Example profile: Profile-Using_constants.pak