Pega CSSA 8.5

Inputs to the rule resolution algorithm:

- Predefined rule keys that are used as a unique identifier, such as Apply to: class, rule name, and rule type. - User's ruleset list - Class hierarchy of the rule in question - Circumstances - Availability - User's access roles and privileges

Three ways to manually adjust urgency:

- UrgencyUpdate flow action - pyUrgencyWorkAdjust property - pyUrgencyAssignAdjust property

UrgencyUpdate

A flow action that you can call while processing a case which takes a provided integer and adds it to the current urgency of the case.

pyUrgencyAssignAdjust

A property that you can adjust to increase or decrease the assignment urgency.

pyUrgencyWorkAdjust

A property that you can set to increase or decrease the current urgency of the case. The value that you provide is evaluated by the pxUrgencyWork declare expression when the assignment is created.

Delegated rules

A rule that appears for a specific group of users so that they may manage these rules outside the development environment.

Pega-ProcessCommander

A ruleset that lists all product rulesets. Used as a prerequisite if there is no other prerequisite.

Rule availability

A setting that governs the usability of a rule at runtime

Availability

A setting used to determine if a rule is available for use during rule resolution. Determines if you can view, copy, edit, or execute a rule in Dev Studio.

Benefit of parallel development

A team of developers can implement application functionality without impacting other developers.

Spinoff

An option in the Subprocesses shape allows you to run the subprocess in parallel with the main flow. The main process does not wait for the subprocess to complete before proceeding. The subprocess does not rejoin the main process.

Assignment Ready: Immediately

Assignments that are associated with this SLA are immediately sent to a worklist or a work queue, and users can begin work immediately.

Assignment Ready: Timed delay

Assignments that are associated with this SLA start the assignment after a period of time. You define the delay period (in Days, Hours, and Minutes) before users are expected to begin work on assignments.

Assignment Ready: Dynamically defined on a property

Assignments that are associated with this SLA use a DateTime property value that you define to determine when users are expected to start work assignments.

Branch ruleset

Based on (branched from) another ruleset and contains rulers that are in active development in the associated branch.

Availability of Withdrawn

Indicates all the rules that are in the current version ruleset and previous version ruleset and have the same purpose (or rule type) and Apply to: class are hidden and no longer checked during the rule resolution process. Withdrawn rules do not impact lower circumstanced rules as circumstanced rules have their own availability value.

Urgency

Indicates assignment priority. A numeric value (0 to 100) displayed in worklists and cases.

Availability of Not Available

Indicates that the rule may not be used during rule resolution. Next highest version of rule is considered.

Availability of Blocked

Indicates the rule may be used during the rule resolution process, but if the rule is selected, execution is halted and an error message is added to the log file.

Availability of Final

Indicates the rule may be used during the rule resolution process.

Which rules does rule resolution NOT apply to?

Instances of classes derived from any other abstract base class such as Data-, System-, or Work- (operator IDs, email listeners, operator's favorites).

Ruleset Stack tab

Lists the rulesets and ruleset versions that make up your current application including those from any built-on application.

Some join condition: Exit iteration options:

Specify the either a "On when" when condition or "On count" integer.

Join conditions

Split for Each and Split Join shapes require that you specify a join condition that controls when the main flow resumes.

Rule resolution

The algorithm used to find the best or most appropriate rule instance to apply in a situation. Rule resolution applies to most, but not all, classes derived from the Rule- base class.

Skimming

The process of saving the highest version of a rule into a new, higher ruleset version.

Steps to populate the rules cache:

1. Choose rules with correct purpose. 2. Discard rules that are Not Available. 3. Filter rulesets and versions user has access to 4. Discard rules not in the inheritance path. 5. Rank remaining rules. 6. Set rules cache.

Steps to set up parallel development

1. Create a team application built on the main application 2. Create one or more development branches in the team application 3. Grant access to team application

Steps to set up branch development

1. create a team application 2. create an access group that references the team application. add developers to the access group.

Some join condition: Number of paths

An integer that determines how many subprocesses need to reach a certain status to resume processing.

Highest possible urgency

100. Any adjustments that set urgency over 100 are ignored.

Application versioning

A way to differentiate current and past application configurations.

Withdrawing a rule

All previous occurrences of this rule in the same major version, but lower and minor and patch versions having the same circumstance type get withdrawn. Rule resolution then selects the base rule despite meeting the circumstanced condition.

Case locking strategies

Allow one user and allow multiple users

Allow one user

An application applies an exclusive lock when opening an item, such as a case. The user or system who opens the object gains exclusive access to the object until the application releases the lock.

Flagging a base rule

By selecting the "Base" check box, you are indicating that the rule resolution algorithm should ignore all previous occurrences of this rule in the same major version. Any previous circumstances no longer apply.

Application rulesets

Contain application information.

Organizational rulesets

Contain reusable organizational assets, such as data structures.

Branch

Container for rulesets with records that undergo rapid change and development.

Framework layer

Contains generalized assets that are then extended by specific implementations.

Production rulesets

Contains rules that can be updated in a production environment. Commonly used for delegates rules.

When to set an availability of Not Available:

During development, you can save a rule without validation.

Initial urgency

Default is 10. Can be adjusted on the case type settings.

Purpose of a rule

Defined by the combination of the rule name and rule type.

Circumstance definition

Defines the combination of conditions in which a property uses a variant of a rule.

Circumstance template

Defines the properties on which to circumstance a rule.

Ruleset validation mode

Each ruleset version defines one or more ruleset versions on which the ruleset version depends.

Rules cache

Ensures rule resolution operates efficiently. When your app references a rule, Pega Platform checks the rules cache for the referenced rule.

The first step of Rule resolution:

Find rules in Rules cache

How to override a circumstanced rule:

Flagging a base rule or withdrawing a rule.

Case locking

How an application supports concurrent users to prevent overwrites as a result of two or more actions attempting to update a case.

Personal ruleset

If an operator has permission to check out rules, this will be at the top of their ruleset list.

Versioning methods

Lock and roll, and skimming.

Which rules does rule resolution apply to?

Most instances of classes derived from the abstract Rule- class (case types, properties, sections, data pages).

Ruleset validation

Performed every time a rule is saved. It guarantees that referenced rules are available on the target system when the ruleset it promoted.

-Int

Post-fix for rulesets generated with the New Application wizard that are used for rules related to integration.

Join condition: All

Resume processing after all subprocesses are complete.

Join condition: Any

Resume processing after any processes are complete. After any of the subprocesses are complete, processing of the remaining subprocesses stops and the system cancels open assignments.

Join condition: Some

Resume processing after either a specified number of subprocesses is complete or a when condition is true.

As-of date circumstancing

Rule variant is effective after a certain date, or during a range of dates.

Multi-variant circumstancing

Rule variant is effective when a combination of property values satisfies the circumstancing condition. Requires a circumstance template and a circumstance definition.

Date property circumstancing

Rule variant is effective when the value of a date property satisfies the circumstancing condition. This condition can be either a single date or a range of dates.

Single variant circumstancing

Rule variant is effective when the value of a single property satisfies the circumstancing condition.

Major skim

Rules are stored in a higher major version. Withdrawn rules are NOT carried forward.

Minor skim

Rules are stored in a higher minor version. Withdrawn rules are carried forward.

Application validation mode

Rules in the ruleset can reference all rules defined in the same application and rulesets belonging to any built-on application.

Define subprocess flow: On specific work item

The subprocess works on a specific case

Define subprocess flow: On embedded page

The subprocess works on an embedded page

Define subprocess flow: On current page

The subprocess works on the current case

pxUrgencyAssign

The sum of: - pxUrgencyWork - pxUrgencyAssignSLA - pyUrgencyAssignAdjust

pyUrgencyWork

The urgency of the case at the time the assignment is created.

Circumstancing

To create a variant of a rule tailored to a specific circumstance. Allows you to customize the behavior of your application to address each exception.

Lock and roll

You create a new empty ruleset version, then update the configuration, only copying the necessary rules into the new ruleset version. Best for small changes or patches.

Filter flow by: Process flow

To start a subprocesses that is a series of actions to complete.

Filter flow by: Screen flow

To start a subprocesses that is a series of forms to complete.

pxUrgencyAssignSLA

Urgency from the assignment SLA. The value is the sum of the initial urgency and the urgency increments for the goal, deadline, and passed deadline intervals.

When to set an availability of Final:

Used by Pega Platform to indicate that Pega-provided rules might change in subsequent releases.

Availability of Withdrawn permissions

View, copy, edit. Executes the instance of the rule in the parent class or next highest.

Availability of Blocked permissions

View, copy, edit. Halts execution.

Availability of Not Available permissions

View, copy, edit. The rule in the next highest version is considered for rule resolution

Availability of Final permissions

View, execute.

When to set an availability of Blocked:

When access to the rule must not be used and you need more time to develop and release the updated rule.

When to set an availability of Withdrawn:

When you don't want the current and lower versions of that rule (with the same purpose) to be executed, and you want to force the system to look for an instance of the rule in the highest class or ruleset.

Split for Each

a parallel processing shape to run one subprocess multiple times by iterating through a set of records in a page list or page group. When all items on the list have been processed, the main flow continues.

Split Join

a parallel processing shape used to call multiple independent processes that operate in parallel and later rejoin.

GetNextWork

a selection algorithm that identifies the next assignment on which users can work by finding the assignment with the highest urgency.

Before merging a ruleset:

check in rules and review conflicts and warnings

Division layer

contains assets that apply to a line of business, region, or brand

Organization layer

contains assets used on an enterprise-wide basis. Contains both business logic rules such as properties and decision tables, and data-assets such as classes and rules for data stored in the system and external systems.

Pega Platform layer

contains the built-in assets necessary for processing cases

Implementation layer

defines an application customized for a specific division or line of business. This may extend a Framework layer application.