I was wondering if there is a possibility to stop executing the outgoing task. Of course there is the conditional transformer and you can filter out unnecessary data, but in some use-cases it could be nice to have a other possibility. It would be nice to have a “stop processing transformer” that returns a failed or processed, based on a condition.
Or is there a nice work-around for this?
Welcome to our forum
Regarding your questions, could you please confirm my understanding that you expect a transformer or something to stop the execution process on outgoing based on a condition?
If that’s what you expect, we don’t have that kind of feature yet. But there is a possibility that makes the task will be skipped, so the process will not continue.
Welcome to the forum!
You can skip tasks, in the example configuration there’s an example transformer that skips them based on a condition.
Basically if the payload becomes null, the task will be skipped.
You can read the description in the ‘[EXAMPLE] Skip a task’ transfomer.
Hi sometime ago I’ve build this configuration to help new customers get started inside of their brand new Alumio environment.
It connects products from two of our
Alumio test interfaces.
This example configuration is shipped with new environments by default.
Well known as the “pre-configuration”.
Please read the pinned category topic on how to export share and import.
Last updated: 2022-09-07
Alumio version: 3.18.0
One route called “[example] System-B - update produc…
The ‘no action publisher’ in the outgoing configuration might also be interesting depending on the usecase.