Workflow Automation Platform
(Redirected from workflow automation platform)
Jump to navigation
Jump to search
A Workflow Automation Platform is an automation platform that orchestrates workflow automation systems through integrated workflow components (to enable process automation and automated workflow orchestration).
- AKA: Process Automation Platform, Workflow Orchestration Platform, Business Process Automation Platform, BPM Platform, Workflow Management Platform.
- Context:
- It can (typically) compose Core Workflow Components through workflow architecture:
- Workflow Engine for workflow execution.
- Workflow Integration Hub for workflow connection.
- Workflow Task Manager for workflow orchestration.
- Workflow Visual Designer for workflow building.
- Workflow Rule Engine for workflow logic.
- Workflow Authentication Service for workflow access.
- Workflow Monitoring System for workflow tracking.
- Workflow Storage Service for workflow persistence.
- Workflow API Gateway for workflow external access.
- Workflow Notification Service for workflow alerting.
- Workflow Scheduler for workflow timing.
- Workflow Template Repository for workflow reusability.
- ...
- It can (typically) enable Workflow Design through workflow builder.
- It can (typically) manage Workflow Integration through workflow connector.
- It can (typically) handle Workflow Data Transform through workflow mapper.
- It can (typically) control Workflow Process through workflow engine.
- It can (typically) monitor Workflow Execution through workflow analytics.
- It can (typically) support Workflow Debugging through workflow testing tools.
- It can (typically) provide Workflow Documentation through workflow metadata.
- It can (typically) enforce Workflow Governance through workflow policy.
- ...
- It can (often) support Multi-Step Workflow through workflow editor.
- It can (often) provide Workflow Error Handling through workflow recovery.
- It can (often) enable Workflow Custom Logic through workflow code.
- It can (often) maintain Workflow Version Control through workflow history.
- It can (often) facilitate Workflow Collaboration through workflow sharing.
- It can (often) implement Workflow AI Integration through workflow AI nodes.
- It can (often) deliver Workflow Performance Optimization through workflow caching.
- It can (often) ensure Workflow Security through workflow encryption.
- It can (often) support Workflow Branching Logic through workflow conditionals.
- It can (often) enable Workflow Event Triggering through workflow webhooks.
- ...
- It can range from being a No-Code Workflow Platform to being a Low-Code Workflow Platform, depending on its automation approach.
- It can range from being a Small Business Workflow Platform to being an Enterprise Workflow Platform, depending on its automation scale.
- It can range from being an Open-Source Workflow Platform to being a Proprietary Workflow Platform, depending on its automation model.
- It can range from being a Single-Tenant Workflow Platform to being a Multi-Tenant Workflow Platform, depending on its automation deployment.
- It can range from being a Cloud Workflow Platform to being an On-Premise Workflow Platform, depending on its automation hosting.
- It can range from being a Simple Workflow Platform to being a Complex Workflow Platform, depending on its workflow feature sophistication.
- It can range from being a Domain-Specific Workflow Platform to being a General-Purpose Workflow Platform, depending on its workflow application scope.
- ...
- It can integrate with External Workflow Service for workflow integration.
- It can connect to Workflow Storage System for workflow management.
- It can support Workflow Analytics Tool for workflow monitoring.
- It can interface with Workflow Identity Provider for workflow security.
- It can communicate with Enterprise Resource Planning System for workflow business integration.
- It can synchronize with Customer Relationship Management System for workflow customer automation.
- It can interact with Human Resource Management System for workflow employee process.
- ...
- It can (typically) compose Core Workflow Components through workflow architecture:
- Example(s):
- Enterprise Workflow Platforms, such as:
- ProcessMaker Workflow Platforms, such as:
- Microsoft Workflow Platforms, such as:
- ServiceNow Workflow Platforms, such as:
- Pega Workflow Platforms, such as:
- Cloud Workflow Platforms, such as:
- Open-Source Workflow Platforms, such as: n8n, Apache Airflow, Temporal.io platforms, Node-RED.
- Specialized Workflow Platforms, such as:
- RPA Workflow Platforms, such as:
- Data Workflow Platforms, such as:
- DevOps Workflow Platforms, such as:
- Low-Code Workflow Platforms, such as:
- ...
- Enterprise Workflow Platforms, such as:
- Counter-Example(s):
- Manual Process System, which requires human intervention rather than workflow automation.
- Basic Task Tool, which lacks workflow orchestration and process automation.
- Custom Script System, which needs manual coding rather than workflow automation.
- Simple Scheduler, which handles time execution without workflow automation.
- Document Management System, which manages content flow without workflow automation.
- Project Management Platform, which tracks task progress without workflow automation.
- Static Form Builder, which collects data input without workflow automation.
- See: Business Process Management, Workflow Automation, Workflow Integration Platform, Workflow Engine, Workflow Orchestration, Process Automation, Automation Strategy, Digital Transformation Platform.
References
2020
- https://processmaker.gitbook.io/processmaker/json-the-foundation-of-request-data/what-is-request-data
- QUOTE: ... While ProcessMaker is a low-code, intelligent BPM platform for enterprises, our goal is to deliver simplicity, but to allow complexity. ProcessMaker is easy to use, and allows you to design customized processes and end-user experiences without understanding what data is. However, understanding how Requests are represented in ProcessMaker takes your designing potential to the next level. ...
... Before discussing the foundation for Request data, let's understand what Request data is. Each Request can be unique even though it was started from the same Process. Each Process is designed to determine business decisions based on information in each Request. ...
... As each Request routes, ProcessMaker accumulates data that represents and contains the information entered into each Request. As data accumulates for each Request, this data affects how each Request routes through the Process. ...
- QUOTE: ... While ProcessMaker is a low-code, intelligent BPM platform for enterprises, our goal is to deliver simplicity, but to allow complexity. ProcessMaker is easy to use, and allows you to design customized processes and end-user experiences without understanding what data is. However, understanding how Requests are represented in ProcessMaker takes your designing potential to the next level. ...