System limits and maximums

By design, Process Commander is highly scalable. You can support one user or thousands of users. You can operate a Process Commander system on an inexpensive Windows laptop or on a collection of enterprise servers, each with multiple processors.

Similarly, there are no inherent restrictions on the size or number of work objects, assignments, history instances, data instances, and so on. Expanding your investment in disk space and database management facilities automatically expands the capacity of your Process Commander applications.

The following maximums and limitations are applicable to Version 5. Contact your Pegasystems Global Services representative if these affect your operation.

Column widths

• Generally, RuleSet names (pyRuleSetName property) may be up to 64 characters long. However, personal RuleSets used for checkout are named based on the Operator ID, which may be up to 128 characters long.
• An Operator ID value (pyUserName property) may be up to 128 characters long.
• The internal key of an object (pzInsKey property) may be up to 255 characters for most tables.
• A class name (pxObjClass property) for a class you create may be up to 56 characters long. System-created classes such as History- classes may be up to 64 characters long.
• The visible key (pxInsName property) may be up to 128 characters long.
• A Short Description for a rule or data form (pyLabel property) may be up to 64 characters long.
• A label in a layout cell on a work object form (pyLabel property) is limited to 64 character maximum. Use a paragraph rule (Rule-HTML-Paragraph rule type) to present longer read-only text in the cell.
• A work group name may be up to 64 characters long.
• A property name may be up to 64 characters long.
• The system name (key of the Data-Admin-System data instance) may be up to 32 characters long.
• The pzPVStream column or Storage Stream has a maximum of 2 gigabytes. This column typically has a data type of BLOB.
• A node name may be up to 32 characters long.
• The third key part of a field value rule is limited to 64 characters.
• For Declare Expression rules, the length of the Page Context field is limited to 64 characters.
• Organization identifiers, the key of Data-Admin-Organization instances, are limited to 32 characters. Likewise, division names — the second key part of Data-Admin-OrgDivision instances, and unit names — the third key part of Data-Admin-OrgUnit instances, are limited to 32 characters.
• The description text (Subject field) of a file attachment is limited to 60 characters.

Review the database schema of your system to learn the size limits of other properties. See Working with the PegaRULES database.

Other limits

• A work object can be processed by a single flow rule at most 500 times. By design, this limit prevents runaway looping. See More about Flow rules.
• You cannot attach a file larger than 25 megabytes to a work object. Similarly, this limit applies when using the Upload button on Rule-File-Text, Rule-File-Binary, and Rule-File-eForm rule forms, and with the Upload button on the Import Archive tool. You can enforce a higher or lower limit on your system with by changing the value for the Initialization/MaximumFileUploadSizeMB parameter in the prconfig.xml file. (The number of attachments you can associate with a single work object is not limited.)
• Broadcast messages are limited to 255 characters.
• The in-memory buffer for the Tracer tool is limited to 500 unprocessed events; the Tracer fails if this buffer overflows. You can configure a larger limit by directing unprocessed events to a temporary disk file. See Tracer — Saving unprocessed events in a temporary file.
• The rule cache is ordinarily limited to 10,000 entries. Contact Pegasystems Global Support if your production system needs a larger cache.
• The summary view and list view facilities operate best on searches that result in 9,999 or fewer rows. If report paging is enabled, the system enforces no limit, but each page is limited to 200 rows.
• The Split-forEach shape in a flow is by default limited to a maximum of starting 50 new flows. This limit is imposed to prevent infinite looping, but can be raised in specific situations. See Flow form — Editing in Visio — Split-ForEach tasks.
• The system is initially limited to 200 data tables created with the Data Table wizard. This limit can be increased if needed.
• Database software supporting your Process Commander system limits the number of columns that can occur in any database table. When creating or updating a Circumstance Definition rule, you may not exceed this limit. See Pega Developer Network article PRKB-25322 Troubleshooting: "Exceeds the maximum number of columns" when creating a Circumstance Definition rule.
• Each developer may define up to 1,000 shortcuts.

Concepts