Available in March 2009, Process Commander V5.5 offers hundreds of new capabilities for developers, application users, and system administrators, and resolves issues found in earlier versions.
This topic describes enhancements in these areas:
To learn about V5.5 features in other areas, see What's New in Version 5.5.
Version 5.5 introduces six new alerts that provide insight into system conditions that may hurt performance. Developers are notified immediately when the application rules they run produce an alert.
The new alerts are named PEGA0030 to PEG0035. See:
- Understanding the PEGA0030 alert - The number of requestors for the system exceeds limit
- Understanding the PEGA0031 alert - Generated stream overwritten and not sent to client
- Understanding the PEGA0032 Alert - Rule change invalidated the specified threshold of entries in the Rule Assembly cache
- Understanding the PEGA0033 alert - Database query length has exceeded a specified threshold
- Understanding the PEGA0034 alert - The number of declare indexes from a single interaction exceeds a threshold
- Understanding the PEGA0035 Alert - A Page List property has a number of elements that exceed a threshold
System Management Application
The System Management Application now provides detailed information about requestor clipboard sizes. See Use SMA to identify the largest requestor clipboards and clipboard pages.
Easier specification of product rule contents
Product rules can be based on an application rule rather than an explicit list of RuleSet versions. See How to specify application RuleSets in a product rule.
Rule management tools are more consolidated and offer more flexibility in handling checked-out rules To start these tools select the Tools > Rule Management menu item See:
- How to refactor RuleSet Versions
- How to rename a class
- How to delete a class (V5.5)
- How to use the Search/Replace a String wizard (v5.5)
- How to refactor class-based rules into a different class or RuleSet Version
Security for work object categories
New facilities simplify defining work object attachment categories, and controlling security for attachments. See How to control access to individual categorized attachments and How to enable attachment security using attachment categories.
Detailed logging of use of harness rules and flow action rules
When required by regulations or highly-sensitive data, your application can log each use of a work object form or flow action by user, date and time, and work object ID, even if the user was only reviewing, not updating, the work object. See How to log each use of harness and flow actions.
Control which work classes are indexed for full-text search
For security or performance reasons, you can exclude instances of specific classes (such as Work- or Data- classes) from the Advanced Search facility. How to limit text search to instances of specific classes.
Optionally, your application's SOAP connectors can be encrypted and reference a keystore, in compliance with WSS and X.509 standards for public key encryption of digital certificates. See How to create SOAP connectors that use WSS username tokens and timestamps.