Tasks can be created using arrays and if-then-else statements. Exceptions and errors can be logged to an e-mail address, log file or Windows event log or trigger another task. If a task ends in a failure or any step within a step fails, you define the corrective measures to take place, such as the initiation of another task. If a task fails, it appears in red in the management interface. Click down on the task to get information on the step that failed and why.
Unfortunately, you can't create dependencies before a task runs. For example, you can't check if a file is present or of a certain size, or if a task ended successfully.
Trigger Action
Although you can trigger all tasks manually, the real power of this product is in automatic triggers. You can set tasks to be triggered on certain days of the week, after an interval of time, upon start-up or when a user logs in. Other trigger options include when the endpoint is idle after a specified amount of time, when a system performance threshold is reached, at event log entry, at service starts or stops, at process initialization or termination, and when an SNMP trap is received.
For more granular control, you can set tasks to trigger when certain user and GUI activities take place. For example, you can specify tasks to occur when a window is opened, a key sequence or word is typed, or monitored files and directories are altered. You can even limit the key-sequence monitor to select applications. It's also possible to chain individual jobs together so that they all run sequentially if the previous one was ended successfully. However, you can't chain jobs across machines.
Bob Friday, Chief AI Officer for Juniper Networks, explains how the advanced technology is transforming operations.
Contact center leaders from 8x8, Awaken Intelligence, and 360insight discuss the importance of agent experience.
AI may force enterprises to rewire parts of their data centers so they are fully optimized to run such workloads. The question is do you use Ethernet or InfiniBand?
