One runtime. Business users author rules, developers author processes.
An embedded business process execution platform for Java application servers: process engine, rules engine, human workflow, events and analytics, with graphical authoring across all of it.
Why move work onto a process platform
Four reasons organizations do it, and what each one changes day to day.
Workflow automation & efficiency
- Governance and visibility across automated and human work
- A unified view of processes, cases and documents
- Control of actions driven by business events
- Higher productivity and better business outcomes
Reusability & flexibility
- Orchestrate automated and human functions as one model
- Standardized, reusable information models
- Flexibility and configurability through business rules
- Rapid deployment and responsiveness to change
Service integration & STP
- Process-driven applications that achieve STP
- Assemble apps from process models, rules and services
- Richer user interaction through composed interfaces
- Standards-based integration, internal and with partners
Analytics & insight
- Monitor metrics and display key performance indicators
- Analyze process data for continuous improvement
- Visibility into key transactions and their impact
- Use process data to spot opportunities and optimize
Five components, one runtime
Business users author rules, developers author processes, and both deploy against the same engine.
Process Platform: the core
Embedded process execution for all major Java application servers. A lightweight, low-footprint runtime with an integrated Drools-based rule engine, running both long-lived persistent processes and short-burst non-persistent ones, and extensible into a platform of your own.
Process Designer
BPMN-compliant graphical authoring. Orchestrate business functions into an executable model and expose processes through standard and extension APIs.
Business Rules Studio
Browser-based rule editor with guidance drawn from your business data, so business users create and maintain rules directly.
Human Task Manager
Integrated human workflow: task inbox, lifecycle management, role-based access control and form generation.
Event Manager
Events declared in the designer, emitted asynchronously, then persisted and aggregated for reporting and analytics.
Design-time authoring, a persistent runtime, REST over all of it
Modelled graphically, saved as standard BPMN XML
Tasks, connectors and routing artifacts, with properties specified per activity.
Activity types
- Service task: a Java implementation class for computational logic, or a web service call to an external unit
- Receive task: a web service endpoint that starts a process instance, or feeds one that is waiting
- Human task: an activity with a form, feeding a waiting instance via the Human Task API
- Business rule task: MVEL rules on the Drools engine, updated with zero deployment
Flow and routing
- Parallel paths: multiple sequence flows from one node, equivalent to a FORK
- Conditional paths: a flow qualified by a rule, taken only on a true evaluation
- Join sequencing: the JOIN for a FORK; halts until every inbound path completes
- Event emission: events declared in the modeler, emitted as the process runs
The model is the documentation. What operations agrees to in a workshop is the same artifact the engine executes, closing the usual gap between the process on the wall and the one in production.
Authored by the people who own them
Rules live outside the code. Underwriting, product and compliance logic changes without a release cycle.
Guided graphical authoring
A browser-based editor offers context-based guidance drawn from the modelled business data, so a business analyst composes valid rules against real product and application attributes.
Plain-text representation
Every rule has a readable text form kept synchronized with the guided view, which doubles as auto-generated documentation and makes business logic reviewable by non-developers.
Full technical view
An optional full-grammar view and Eclipse editor plugin for complex rules, with rules also maintainable as files for teams that prefer source control as the system of record.
Import and export APIs move rules out of an environment into an SCM and promote them into a target environment, so rule changes assimilate into existing build and deployment processes instead of bypassing them. Rules execute via the Business Rule Task and update without redeployment.
Automation handles the clean cases
The platform is judged on how well it handles the rest, and on whether you can see what happened.
Human task management
- Task inbox scoped to the user by the authorization model
- Custom forms to work and complete tasks in context
- Role-based access control over permissible actions
- Task lifecycle tied to the owning process instance
- Integrated auto and manual correspondence
Event management & analytics
- Events declared in the modeler, persisted asynchronously
- Custom KPI and event visualization for dashboards
- Deep execution analysis: where incomplete processes drop off
- Summary results of completed processes and final dispositions
- Metrics over REST for your own reporting stack
Where every case sits, what is blocking it, which rule sent it to manual review, and how long each step took. Answered by the runtime doing the work, not a warehouse a day later.
PSuite sits behind your portals, not in place of them
Everything the runtime does is reachable over REST.
APIs
- Process Manager API: create and interact with process instances
- Human Task API: inbox, claim, complete and route tasks
- Rule Manager API: build custom rule editors over the rule model
- Rule Import/Export API: promote rules across environments
- Metrics & Analytics API: event and KPI data for reporting
Deployment
- Embedded in all major Java application servers
- On-premise, or Wiztek-hosted managed services
- Low-footprint runtime for high-performance, adaptive applications
- Extension points for building a tailor-made process platform
- Conversational and natural-language interfaces
PSuite is designed to be extended into a custom process platform for your enterprise, which is why our customers end up owning a capability rather than a single application.
See PSuite against your own process
Bring a process that stalls, breaks at integration, or costs too much to change. We will walk it through the platform rather than through a slide.