Stefanie has posted 11 posts at DZone. View Full User Profile

Visual Rules Enterprise Platform 4.5: Available now

07.02.2009
| 1173 views |
  • submit to reddit

Visual Rules now coordinates rule changes by multiple team members to secure rule quality and continuous traceability. Additionally, users may look forward to easily reusing rules.

What's New ?


Rule Change Management with Visual Rules 4.5
A new workflow of the Visual Rules Enterprise Platform 4.5 coordinates rule changes among mutliple team members. The process focuses on ensuring rule quality, continuous traceability of changes, and reuse.

Reuse: It's So Easy

Visual Rules 4.5 introduces the concept of rule artifacts containing rule models and executable rule code. Artifacts can be uniquely identified by an ID and a version number. Since Visual Rules Modeler 4.5 works directly with these artifacts, rule authors will be able to easily reuse existing rules or data models, including function and service libraries. If a rule project requires another artifact, Modeler automatically retrieves the correct version from the repository.

Using multiple Rule Versions

The integrated rule artifact concept also permits using multiple rule versions simultaneously. Visual Rules Execution Server 4.5 ensures that every request is handled by the correct rules, e.g., compliant to their effective date.

Rule Quality Secured
Visual Rules Team Server 4.5 ensures rule quality when multiple team members change rules. Each author sees all changes made by the other authors. Rule changes are logged, and stay traceable with every revision being restoreable and visualizable within the graphical model.

Traceability at Any Time

Being able to trace rules while editing is just one important facet. In addition, Visual Rules 4.5 makes sure that all decisions are fully transparent. All rule executions can be retraced in every detail, even years later.

Visual Rules Enterprise Platform 4.5 is now available, for a free evaluation.

 

New & Noteworthy | Download

0
Published at DZone with permission of its author, Stefanie Peitzker.

(Note: Opinions expressed in this article and its replies are the opinions of their respective authors and not those of DZone, Inc.)