Rules in PEGA

A rule is an instruction for describing a specific case behavior, such as a process or automated decision. A collection of rules is known as a ruleset. Rulesets can be shared and also can be reused in different applications. Instance of a ruleset is called a ruleset version.

To update the contents of the ruleset, you create a new ruleset version. The version number is divided into three segments: a major version, a minor version, and a patch version. Each segment is a two-digit number starting at 01 and increasing to 99. Ruleset version numbering starts at 01–01–01 and increments upward.

A major version change encompasses extensive changes to application functionality. For eg: the Accounting department uses an application to manage expense reports. If Accounting wants to extend the application to track employee time off for payroll accounting, you create a new major version of the ruleset. The minor version represents an interim release or enhancements to a major release. For example, you need to update an expense reporting application to make automatic audit travel reimbursements. You create a new minor version of the ruleset. The patch version consists of fixes to address bugs in an application. For example, you notice that a field in the current version of an application has an incorrect label. You create a new patch version to correct the field label.