Enterprise Workflow Connectors for Custom Trigger Automation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current workflow tools lack the ability to detect trigger events important to enterprise users, require integration of third-party software with limited options, and incur expensive licensing fees, failing to meet the specific needs of individual enterprises.
Innovation Solution
A customizable workflows tool that allows enterprise users to create personalized workflows through a GUI, selecting trigger events, actions, conditions, and filters, with backend connectors to execute these workflows across enrolled user devices, enabling cross-platform actions and group-based workflow creation.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If third-party workflow software is integrated, then workflow automation capability is provided, but the system becomes limited to predefine templates and incurs expensive licensing fees
Solution Approach 1:
The system enables enterprises to build their own workflow automation capabilities using native device features and APIs without requiring third-party software integration. Users can create custom workflows directly on enrolled devices, eliminating the need for external workflow tools and their associated licensing and integration complexities
Solution Approach 2:
The workflow automation system is built into the UEM platform itself, allowing the same system to provide both device management and workflow automation functions. This multi-functionality eliminates the need for separate third-party workflow tools, reducing integration complexity while maintaining customization capabilities
2Adaptability or versatility
If third-party workflow software is used, then workflow automation is achieved, but trigger event and action options are limited
Solution Approach 1:
The system leverages native device capabilities, operating system features, and application APIs to provide extensive trigger event and action options without requiring third-party software. Devices can detect native triggers (notifications, emails, calendar events, location changes) and perform native actions (launch apps, play sounds, vibrate, display notifications) directly through the UEM platform
3Difficulty of detecting and measuring
If current workflow tools are used, then some automation is provided, but they lack the ability to detect enterprise-specific trigger events
Solution Approach 1:
The system provides localized trigger detection capabilities tailored to each enterprise's specific needs. Enterprises can configure custom trigger events based on their unique workflows, such as detecting specific notification types, email patterns, calendar event properties, or location changes relevant to their operations, rather than being limited to generic trigger events
Solution Approach 2:
The system allows enterprises to customize trigger event parameters and action configurations to match their specific requirements. Users can modify trigger conditions, set custom time delays, choose from multiple action types, and configure filters to detect and respond to enterprise-specific events with precise parameter control
Data Source
AI summary
Systems and methods are described herein for creating enterprise workflows for an enterprise user. In an example, a user can access a workflows tool in a management application. The user can select a trigger event from a list of available trigger events. In response to the selection, the workflows tool can display a list of available actions. The user can select an action. The user can also select other enrolled user devices for executing the workflow. The management application can send the selections to a server. The server can send workflow connectors for the selected trigger event and action to the selected user devices. The workflow connections can include instructions for detecting the trigger event and instructions for performing the action. The management application can install the workflow connectors and begin executing the workflow.


