Case management, not just workflow
Process Automation handles case-centric work where cases have their own data models, document bundles, and SLAs.
OpenText • Process automation
Process Automation (AppWorks lineage) is the low-code process platform for content-driven workflows, case management, and long-running approvals.
Process Automation projects with Merito start with the process and case model, then build the workflows and bind them to Content Management or Documentum and to the system of record behind each case.
What it is
OpenText Process Automation is the process-automation product carried from the AppWorks lineage. It targets content-driven workflows where documents, cases, and long-running approvals are central. It is not a consumer-facing RPA product; it is a BPM and case management platform for enterprise processes where content governance matters as much as process automation.
Process Automation pairs deeply with the Content catalog. Cases, workflows, and approvals reference controlled documents stored in Content Management or Documentum, with retention and audit trails continuous across the process and content layers. That integration is the reason OpenText content customers pick Process Automation over generic BPM tools.
Implementation is a design problem. Workflow discipline (who approves what, on what evidence, in what SLA), case definition (what data fields and documents define each case type), and integration to the systems of record drive success. Merito's engagements start with process design before configuring the product.
Ideal use cases
What it is best at
Process Automation handles case-centric work where cases have their own data models, document bundles, and SLAs.
Workflows reference controlled documents with retention and audit continuity. Process and content live in the same governance model.
Business analysts configure workflows and case types through the low-code surface; developer effort reserves for custom integration.
Core capabilities
Low-code case definition and workflow authoring for content-driven processes.
Case type design
Data models, document bundles, and SLAs per case type.
Workflow authoring
Low-code process modeling with human tasks, service tasks, and decision points.
Rules and decision tables
Business rule authoring for routing, eligibility, and exception logic.
Workflow execution with SLA tracking, escalation, and exception handling.
Human task queues
Task inboxes with SLA tracking and escalation for long-running processes.
Event-driven orchestration
Workflows respond to content, capture, and system events for event-driven automation.
Long-running process support
Persistence and recovery for processes that span days or months.
Connect workflows to controlled content and systems of record.
Content catalog binding
Cases and workflows reference documents stored in Content Management or Documentum.
System-of-record integration
Integration with SAP, Salesforce, Guidewire, and custom systems through APIs.
Audit trail continuity
Process and content audit trails merged for compliance evidence.
Where it fits in the stack
Deployment and implementation
Licensing and packaging
Process Automation standard
Low-code process and case management with Content catalog integration.
Best for: Enterprises automating content-driven processes.
Merito services
Pick the engagement that matches where you are in the lifecycle.
Process design, case modeling, workflow authoring, Content catalog integration, and system-of-record wiring.
Explore serviceLegacy AppWorks and BPM platform transitions into current Process Automation.
Explore serviceProcess Automation integrated with CI/CD for workflow version management.
Explore serviceNamed engineer, priority SLAs, and release-time coverage for Process Automation in production.
Explore serviceLong-term run support for Process Automation including workflow evolution.
Explore serviceBusiness analyst, process owner, and administrator training.
Explore serviceProcess Automation licensing
Describe the case type and the documents that travel with it. What sets Process Automation apart is the binding between a workflow and the content it acts on.
Merito point of view
Process Automation is more than a process needs when there is no real content spine. Process Automation's strength is the integration with Content Management and Documentum. For processes that are pure workflow without meaningful content governance, lighter BPM or workflow products often fit better.
For insurance claims, regulated case management, contract lifecycle, and HR cases, Process Automation could be the right call. The content binding is the value; the workflow surface is how teams interact with it.
AppWorks to Process Automation transitions are primarily version upgrades. Existing customers modernize the platform without re-platforming processes. Merito's transition engagements preserve workflow investment.
What buyers usually underestimate
Related from Merito
Related solutions
Related services
Related products
Frequently Asked Questions
Consultation request
Share the process or case type you need to automate and the Content catalog repository it lives in. A Merito process specialist follows up within one business day.
Content-driven
Process Automation's integration with Content Management and Documentum is the reason to pick it over generic BPM.
Low-code for analysts
Low-code surface means business analysts configure workflows and case types without waiting on developer queues.
Next step
A Merito Process Automation engagement starts with process design and case modeling before configuring the platform.