Lessons

Starting point As you continue to click through the AWI, you set a complex workflow in motion. “Oops,” you say, as you realise that you have triggered a chain of commands. These workflow tasks are programmed in such a way that once one task has been completed, the next one – or even several at […]

Starting point Once you have successfully registered at the AWI, the next challenge awaits you: powering up Leon You start with the power supply. As you concentrate on the screen, you suddenly flinch as Leon floats through the air with a low hum. “Cool“, you think, impressed, feeling like you’re in a sci-fi movie. Motivated,

Starting point Your first practical task on the space station takes you to the library, where Felix introduces you to a robot called Leon. “Leon is something special“, says Felix with a smile. “He has an Automic agent installed that allows you to control him directly via the Automic Web Interface (AWI).“ Your eyes light

The initial situation: Some processes are planned to “block” in order to be released manually. For example, if operations have to work through a checklist before release. These planned breakpoints can be defined by a designer within the workflow or set dynamically with Automation Engine Script. The task that is blocked with a manual breakpoint

The initial situation: The JOBS.EXPORT_DATA#BWF task exports data. The follow-up jobs continue to work with the exported data. If an export fails, the follow-up jobs cannot be executed. The data export job must therefore be blocked in the event of an error so that the follow-up jobs are not executed. In this case, this is

The initial situation: You have now started several workflows and have repeatedly encountered blocks. But how do you find blocked workflows in your environment? We have our own “Process Monitoring Filter” lab on this topic, which I’m happy to recommend here 👍. Since it fits so well, we also do the same exercise here in

The initial situation: In some situations, the successor must determine whether the status of the predecessor is relevant. This allows you to create branches in workflows. The challenge in the analysis is that the report does not provide any information as to why the block occured. In the following example, data is imported using the

The initial situation: Imagine a resource-intensive processing. As long it is active, the associated application cannot be used. You therefore want to ensure that the processing does not start too late. For such requirements, it is possible to define a latest start time for a task. If the task attempts to start later, it is

The initial situation: At the beginning of this lab, you learnt about PostConditions. Now there are also PreConditions that you can use to block workflows. As with the PostConditions, complex logic can also be utilised here (Is it raining & is the moon full between 12:05 and 12:08 🤔? Then don’t start the task, block