Since the StartJobs API doesn’t support directly passing a stop strategy, you’ll need to implement custom logic within your robots using arguments or triggers to manage stopping the job. You can also manually stop the job later if needed via the Orchestrator API.
Sure.
First of all, Orchestrator is a great platform that make it easy to do the source code management, orchestration of jobs, asset management and providing other awesome capabilities.
While due to the complexity of process environments, inconsistent personnel capabilities, along with continuous changes/human typos, our RPA operations and maintenance is facing various challenges.
That’s why we need to optimize the ops, and we are planning:
Expose gateway for 3rd party platform to trigger job with specified arguments;
Monitor the running status and auto rerun with same setting;
Release customized notifications via webhook;
DIY dashboard for the SLA of specific package;
Check the resources assigned to specified project which has many packages real-time;
Setup workflow that make the addition of robot/process/asset could be under management.