This content has been archived and is no longer being maintained.

Table of Contents


Introducing PegaRULES Process Commander 6.2 - Designer Studio

A variety of Designer Studio enhancements allow application designers and developers to produce applications faster. You can directly configure many capabilities that in previous releases required activities, custom JavaScript, or custom SQL statements. An application created in 6.2 using best practices will require creating and testing significantly fewer activities than the same application if implemented in 6.1 or an older release.

This topic summarizes several of the many new features.

  • Run rules directly from Application Explorer — In the Application Explorer tree, a Run icon (Run) appears next to activities, report definition rules, list view rules, and summary views. Click the button to run the rule.
  • Model rules enhanced to support data transformations — Model rules have been enhanced and renamed to Data Transformation rules. In many situations, you can use a 6.2 data transformation rule rather than create an activity. A data transformation rule can perform a variety of operations on values, in addition to setting values for properties. As in earlier releases, at runtime a data transformation rule executes a sequence of actions that affect properties on a page, but in 6.2 the rule can include simple iterations for Page List and Page Group properties, delete properties and values, or update more than a single page. See Introduction to data transforms. Data TransformIn several situations, you can call a data transform rule, rather than an activity, to accomplish needed property updates. Using a data transform rule is often simpler than using an activity. For example, on the Action tab of the Flow Action form, you can optionally identify a data transformation rule to apply before the action, and another data transformation rule to apply after the action is selected. See Using a data transform rule in a flow action. You can unit test a data transformation rule using the Run toolbar button (Run), as with many other rule types. Models created in versions before 6.2 operate as before.
  • My Rules explorer — The My Rules list of favorite rules appears in the Explorer area of the Designer Studio for quick access.
  • Message display at top of rule form — For many rule forms, warning and error messages appear at the top when you save a rule, eliminating the need to scroll.
  • Declare pages visible to all Threads — A Declare Page may now have a scope of Requestor, so that all Threads in the current requestor can read from the page.

These enhancements help developers test and debug applications faster:

  • Tracer scope — Tracer output can include messages from the Pega log and from the Alert log, information about SQL queries sent to the PegaRULES database, SQL responses, and hits/misses for the rule cache and conclusion cache.
    Tracer output database
  • Tracer output color coding — Tracer output for activities uses a dark orange background in the Step Page column to allow you to quickly identify those pages which contain a message. Output corresponding to PegaRULES database operations has a light blue background.
  • White-list testing for activities — Optionally, you can perform white list testing, meaning that only an explicit list of property values are tracked; differences in all other properties are ignored.

A report definition rule, rather than an activity, can be the source of data for various controls and operations. These changes further reduce the need to build and maintain activities. You can use a report definition rule in these settings:

  • Declare Page rules
  • Autocomplete controls
  • Dynamic Select control
  • Repeating rows
  • Repeating columns
  • Tree Grid
  • Tabs


Published August 1, 2011 — Updated February 16, 2016

Have a question? Get answers now.

Visit the Pega Support Community to ask questions, engage in discussions, and help others.