Automatic interplay of business policies and processes eliminates manual identification and integration of changes

Analysts now recognize the importance of rules capabilities within core Business Process Management Suite offerings. Pegasystems achieves this through the association of rules with each step of the process flow, integrating rules into the core execution model, repository, and tools.

Compared with a separate rules engine, the Pegasystems approach avoids the overhead of invoking a separate rules engine from your process engine. It also avoids dealing with two separate development environments and object models (not to mention two vendors).

Pegasystems organizes and manages rules along five dimensions: versioning, temporal (time-based), classification (inheritance), circumstance, and security (role and access). This allows an organization to maintain many rule variants for use in different situations. Pegasystems’ patented rule resolution engine always applies the right rule at the right time for the situation at hand.

Key features of Pegasystems’ rule-driven BPMS

• Task Assignment — Automatically identify the best person for a task based on skills, workload, performance, or availability
• Decisioning — A rich collection of decision rule types including decision trees, decision maps, and decision tables
• Service Level Agreements — Declarative rules define activities to perform when a task is not completed within the prescribed time.
• Declarative Expressions — The value of a property can be determined via an expression and can depend on a network of other properties and expressions. Expressions form a declarative network of response to changes in work
• Forward and Backward Chaining — This powerful capability provides tremendous performance advantages over conventional approaches
• Straight-Through Processing — Tightly integrated decisioning can replace routine human tasks with automated decisioning rules for significant productivity gains
• Rule-Driven Integration — Connections are multi-dimensional so the right connection for each instance is applied based on the situation