Search: "support object"

All of them are pre-filled for you * Next to that you have all the support objects needed to run the flow. * One down we have the job launch configuration

It is up to the user what this point of time is. * In the left corner we have the job listener configuration * This piece of the flow waits for a signal that the job is complete and upon completion will refresh the materialized view (and therefore updating the overview we want). * In the bottom center we have some specific support objects that are relevant for this particular data pipeline implementation * Last but not least, on the right-hand bottom corner we have the functionality that automatically cleans up the job dashboard.

**Example** Flows containing a Jetty server (support object), primarily used to host REST and SOAP web services, require some special attention when deploying because not all combinations of build number 50 (and higher) and 48 (and lower) flows will work correctly: * After installing any build 50 (or higher) flow, build 48 (or lower) flows containing a Jetty server on the same runtime cannot be started anymore.

**Example** Flows containing a Jetty server (support object), primarily used to host REST and SOAP web services, require some special attention when deploying because not all combinations of build number 50 (and higher) and 48 (and lower) flows will work correctly: * After installing any build 50 (or higher) flow, build 48 (or lower) flows containing a Jetty server on the same runtime cannot be started anymore.

[[image:Main.Images.Microlearning.WebHome@crashcourse-messaging-pick-up-files--composite-file-list-filter-component.png]] In this filter, we use the following four criteria to filter our messages: * Regular files only * Size list filter (minimum 1 bytes, maximum 1048575) * Age file list filter (minimum 10000) * Simple pattern file list filter (${file.pickup.pattern}) The result of this configuration should be: [[image:Main.Images.Microlearning.WebHome@crashcourse-messaging-pick-up-files--composite-file-list-filter.png]] The next step would be to link this support object to the file inbound channel adapter (the starting point of our flow).

Here you need to select the correct filter to reference your support object. [[image:Main.Images.Microlearning.WebHome@crashcourse-messaging-pick-up-files--composite-file-list-filter-linked.png]] === 3.2 Frequency === Now that we have established the criteria that govern which messages can and which messages cannot pass the next thing we need to consider is with what frequency we are going to let eMagiz check for new files.

Or perhaps eMagiz has released a standardized template that will make your life easier (i.e. automatic generation of support objects for JSON transformations in messaging) and you want to benefit from those changes.

Besides the changed naming of the transformation, no JSON factory support objects are required in your flow in comparison with a JSON messaging format.

After dragging it onto the canvas, you need to give it a name and save the support object by double clicking on it without making any changes.

In the context of eMagiz, this means that every flow has its unique support object (that is generated by default) to support this functionality.

[[image:Main.Images.Microlearning.WebHome@expert-robotic-process-automation-call-a-robot--http-outbound-example.png]] {{info}}Note that you need a header mapper support object to send the correct headers towards dexi.

If you ever want to validate whether a support object is linked to your component, click on it once.