Cloud Trigger Engine for Flexible Robot Scheduling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional trigger services are not integrated within software ecosystems, limiting their ability to call back into external systems and validate automation processes, and are typically one-to-one in operation, lacking flexibility and efficiency.
Innovation Solution
A trigger engine operates as an intermediary, tracking operations across external systems, registering events in a database, and enabling these events to be visible to robotic process automations, providing a cloud triggering mechanism for scheduling robots across diverse software platforms.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional trigger services operate outside the software ecosystem, then they can monitor external system operations, but they cannot call back into external systems or validate automation processes
Solution Approach 1:
The trigger service acts as an intermediary component integrated within the software ecosystem, positioned between external systems and the software platform. This intermediary role enables the trigger service to both monitor external system operations and initiate callback actions, while the software platform validates automation processes through integrated authentication mechanisms. This resolves the contradiction by allowing monitoring and validation capabilities without requiring the trigger service to operate in isolation.
2Adaptability or versatility
If conventional trigger services operate one-to-one, then they can start or stop specific operations, but they lack flexibility and efficiency
Solution Approach 1:
The trigger service is designed with multi-functionality to handle diverse trigger types including one-to-one triggers, one-to-many triggers, and scheduled triggers. This universal design allows a single trigger service instance to manage multiple automation processes simultaneously, improving flexibility while enhancing productivity through efficient resource utilization and consolidated management of multiple trigger operations.
Solution Approach 2:
The trigger service implements dynamic configuration capabilities that allow trigger behaviors to be adjusted at runtime. Triggers can be enabled or disabled, modified, or deleted based on changing requirements. The service dynamically manages trigger states and can adapt to different operational scenarios, providing both flexibility for customization and efficiency through automated trigger management without requiring manual intervention for each trigger configuration.
Data Source
AI summary
According to one or more embodiments, a method is provided. The method is implemented by a trigger engine stored on a memory as processor executable instructions. The processor executable instructions being executed by a processor. The trigger engine operates as an intermediary for robotic process automations of a software platform. The method includes tracking operations within external systems and registering available events with respect to the operations into a database accessible by the robotic process automations. The method also includes enabling an active event of the external systems to be visible via a trigger of the trigger engine to the robotic process automations.