Workflow Orchestration for Automated Onboarding State Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The onboarding process for customers to technology platforms requires significant manual intervention due to the sequential and interrupted nature of activities, posing challenges in maintaining and communicating the state of included activities across various components of the technological infrastructure.
Innovation Solution
A system and method for automated state management and workflow completion, utilizing an initiator service, workflow orchestration engine, and worker instances to manage and execute workflows in a unique namespace, enabling concurrent execution and maintaining the state of activities through a centralized datastore.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Extent of automation
If manual involvement is used to manage onboarding activities, then the state of activities can be tracked, but the process requires high levels of manual intervention and is time-consuming
Solution Approach 1:
The system performs preliminary actions by pre-defining workflow templates with all necessary activities, transitions, and state management logic before onboarding begins. This allows the automated workflow engine to execute predefined sequences without manual intervention, significantly reducing onboarding time while maintaining proper state tracking.
Solution Approach 2:
The patent introduces a workflow orchestration engine as an intermediary between manual onboarding requests and system execution. This engine automatically manages activity states, transitions, and communications between components, replacing manual tracking with automated state management while preserving the sequential nature of onboarding activities.
2Ease of operation
If activities are executed in sequence with interruptions, then proper ordering is maintained, but state management and communication across components becomes complex
Solution Approach 1:
The patent segments the onboarding process into discrete, manageable activities within workflow templates. Each activity represents a specific task with defined inputs, outputs, and state transitions. This segmentation simplifies state management by breaking down complex processes into atomic units that can be independently tracked and managed, reducing the complexity of maintaining state across multiple components.
Solution Approach 2:
The system implements feedback mechanisms where the workflow orchestration engine continuously monitors activity completion states and automatically triggers transitions based on predefined conditions. This automated feedback loop simplifies state management by eliminating manual state tracking while maintaining proper sequencing, as the engine automatically responds to state changes and coordinates communications between components.
3Productivity
If automated workflows are implemented, then manual intervention is reduced, but maintaining workflow state across distributed components becomes challenging
Solution Approach 1:
The patent implements a universal workflow state management system that handles multiple workflow types and activities through a single centralized engine. This universal state store maintains information for all workflows concurrently, ensuring that state data is preserved and accessible across distributed components. The engine can manage any workflow template activity while maintaining a unified view of all state information, preventing loss of workflow state in automated environments.
Data Source
AI summary
Systems and methods for state management and workflow completion are disclosed. An exemplary method may include receiving a request and data at an onboarding service; sending the request and data to an initiator service; initiating, by the initiator service and at a workflow orchestration engine, a workflow, wherein the workflow is initiated based on the request, and wherein the workflow includes a plurality of activities; registering, by the workflow orchestration engine, the workflow in a unique namespace; generating a worker instance in an application-level container at a compute node; sending, to the worker instance, an activity of the plurality of activities for completion of the activity by the worker instance; communicating, by the worker instance with at least one service, indicating, by the worker instance and to the workflow orchestration engine, that the activity is complete; and persisting, by the workflow orchestration engine, state data for the workflow.