Released in July 2007, Process Commander V5.3 offers dozens of new capabilities for developers, application users, and system administrators, and resolves issues found in earlier versions. For an overview, see What's new in Process Commander 5.3.
These features provide additional support to the developer or system administrator in the management, and migration of rules and RuleSets to target environments. They also support database indices and library maintenance.
- New Product Migration wizard
- Command line migration
- New Package Work wizard
- Skim to Minor Version
- New tools to delete and merge RuleSets
- Scheduled archive or purge of work objects
- Compile libraries across all nodes of a cluster
- Global resource settings simplify connector rule maintenance
A new Product Migration wizard provides:
- Ability to deploy to multiple targeted environments at the same time
- Confirmation of migration to each target environment
With appropriate configuration, a system administrator familiar with UNIX shell or Windows command line operations can perform ZIP archive migrations using an Apache ANT script. This approach transfers rules (or other objects) directly from a source PegaRULES database into a destination PegaRULES database. It uses engine code and JDBC connections, and does not require that either system be running.
A new wizard allows you to move work objects, assignments, work object history, and attachments from a source Process Commander system to a destination system. Complete the initial form to identify a a product rule to be created.
Complete later wizard forms to define the contents of the ZIP file created by the product rule.
In releases before 5.3, the skim operation always created a new major version, such as 04-01-01. In 5.3, you can option to skim rules to a new minor version, such as 04-15-01.
You can delete a RuleSet (or a single version) and all the rules it contains directly from the Tools menu.
Similarly, you can merge two RuleSets into one from the Tools menu.
You can purge work objects (with associated attachments and history) from your system. Two wizards support this new capability. The first wizard defines the purge criteria.
A second wizard defines a schedule for purging. Optionally, you can save all purged objects in a ZIP archive.
The Pega-ProCom agent performs purging as a background process, according to the schedule you define.
A developer can compile a library (from the Packages tab of the Library form or the Parameters tab of the Function form), after updating a library or any function in the library.
In a multinode 5.3 cluster, the Pega-RULES agent on each other node of the cluster promptly compiles the same library, ensuring that uniform Java code for all functions in the library exists on each node. In versions before 5.3, this task was manual.
A global resource setting is a property value on a declarative page that is referenced through a special syntax on a connector rule, or a data instance that supports a connector.
Use of global resources settings rather than fixed text values in rule forms allows greater flexibility in maintaining such values as port numbers, addresses, URLs, and similar values between development systems. A special property reference notation starting with an equal sign character supports this feature.
To download the latest 5.3 product documentation, see PRPC 5.3 Release Announcement.
To request an installation kit for the V5.3 release see Process Commander V5.3 is Available.
* * * * *