DispatchProEventPreParser – Dispatch event (Preprocessing)

When executing a profile, the received data can be transferred directly to the Lobster_pro system via the pre-processing (extension) event. There, the data can be further manipulated or completely different data can be returned to the output paths.
The event is executed in the context of a Lobster_pro user, which must be specified in the configuration.

If the incoming data is a known entity in the Lobster_pro system, it is loaded and transferred to event handling as input data. Otherwise, the data is written to the 'data' event handling variable.

Data that is transferred to the mapping or the output paths must be written to the 'result' variable.
Result types are handled as follows:

String – Forwards this in text format
Content – Forwards this in binary format
Other – An attempt is made to serialize as XML or JSON. The format depends on the Integration Unit or the targetFormat parameter (see configuration).

In the 'Configuration file' field, both the path to a file and the configuration can be specified directly in 'Name=Value' pairs, separated by semicolons (Name1=Value1;Name2=Value2).
The following configuration parameters are supported:

Parameter name	Optional	Description
eventName		The name of the Custom action events to be triggered.
userName		The name of the Lobster_pro user in whose context the event is processed.
selectedRole	If the user has only one role assigned.	The ID of the role used by the user.
selectedCompany	If the user has only one company assigned.	The ID of the company used by the user.
locale	Yes	The language of the user as a locale code (e.g. 'de_DE'). Default: User locale.
useRaw	Yes	true or false (default): If true, the data is passed directly in raw form (binary, as a content object) to event handling. Tip: A content object can also be read directly as a string by value resolvers and actions (e.g. set value to string variable). If false, an attempt is made to read the data as text and to read it as an object. JSON and XML are supported.
charSet	Yes	The character coding of the integration unit and the output format. If useRaw=true, the character encoding for reading in the data is ignored. If a content object is returned by event handling, the encoding for the output data is ignored.
targetFormat	Yes	XML or JSON Specifies the format in which output data that is not of the string or content type is written.