Phase 5 (introduction)
Although Lobster_data's configuration options are very extensive, there are sometimes special requirements that go beyond that. For this purpose, the optional Integration Unit was introduced.
Typically, an Integration Unit is used to bring the destination structure data into a particular format, such as EDIFACT or XML. However, there are also other possible applications (see examples below).
It is also possible to transfer the output data to third-party systems here, although phase 6 is actually intended for this purpose.
Instead of constant values, you can also use variables with the syntax @variable@ in parameter fields. If you use a variable that is not defined in the profile, the expression @variable@ is not resolved to the value of the variable, but is used as it is.
Field values cannot be used directly. You have to store them in variables first.
Postexecution in Phase 5
After the execution of the Integration Unit, a postexecution class can be executed. If you have multiple Response Routes that all use the same postexecuter, you only need to run the postexecuter once if it is called in phase 5, instead of running it in each Response Route.
Examples
For examples, see the documentation for the respective Integration Unit.
GUI
The description of the configuration of this phase in the GUI can be found in section Phase 5 (GUI).