Clipboard

Clipboard: is a tool used for debugging and troubleshooting aid for application developers. Is an temporary memory area on server. Its an hierarchy structure consisting of nodes known as pages most of which have a name and an associated class.

Pages act as a buffers or temporary copies of object instance that are copied from, or may later be stored into, the PRPC DB or another DB.

Clipboard tool is used for developing and debugging to:

Examine property values and messages

Quickly create, update, delete and modify pages using Action menu

Quickly execute activities and start flows using action menu

We can find pages and we can Refresh or only refresh current page.

The clipboard contains three broad categories of top-level pages:

1. User Pages

2. Declared pages

3. System managed pages: requestor page, process page, and application pages, Thread page, Operator ID, organization, orgDivision.

User Page: is a top level clipboard page that an activity creates pages using the methods like Page-New. All the user pages will appear here once we log off, all the user pages will be removed from the memory i.e. will not be saved to Pega DB.

If your requestor session times out, user pages may be lost, or may be saved for up to 3 days

Thread page—pxThread page is a top level clipboard page known as Thread page. The page has a class of Code-Pega-Thread

Process Page—pxProcess page is a top level clipboard page known as Process page. The page has a class of Code-Pega-Process. This page Contains information from the Data-Admin-System instance.

Declare Page-is a clipboard page created by execution of a declare page rules (Rule-Declare-Pages rule type. The name of the declarative pages start with Declare_. The content of these pages are visible but Read-Only to the requestors. Such pages are created and updated only through activities identified in a Declare Pages rule.

Declarative pages can improve performance and reduce memory requirement issues when all or many requestors in an application need to access static information or slowly changing information.

Requestor Page- pxRequestor page is a top level clipboard page known as Requestor page. The page has a class of Code-Pega-Requestor. The system creates a page during at login time and contains information about our Access roles, Security, Ruleset list and HTTP protocol parameters, Work pools available details, workbasket that we can access, connection session, Login Date and Time details and previous login Date and time details etc.

This page context is useful for troubleshooting and debugging.

Page Context is a property is a pageList or Page Group property reference

property has mode Single Value and appears directly on a page of the Applies To class, or if creating a context-free expression.

User Interface

A harness rule defines a runtime form that supports application users as they enter, review, update, and resolve work objects. Harnesses rules support the display of work object forms.

Developers define work object forms through harness rules (Rule-HTML-Harness rule type) and section rules (Rule-HTML-Section rule type).

standard harness forms are New, Perform, Review, Confirm, Reopen, PrintReview

• New — Support initial entry (creation) of the object.
• Perform — Support users completion of assignments.
• Review — Display the work objects in display-only mode, with no fields changeable.
• Confirm — Accept a text note explaining a user's reasoning about a recently completed assignment.
• Reopen — Support reopening a previously resolved work object.
• PrintReview — Support printing of all the fields.

A section is a portion or area of a standard work object form that is incorporated on a harness form. Sections may contain other sections, informally called subsections.

The appearance, behavior, and contents of a section are defined by a section rule (Rule-HTML-Section rule type). Section rules are referenced in:

• Harness rules
• Other section rules
• Flow action rules
• Paragraph rules with SmartInfo pop-ups

Diff b/w Blocked and Withdrawn Rules

A blocked rule and a withdrawn rule are both invisible to rule resolution. Similarly, both blocked rules and withdrawn rules prevent lower-version rules with the same RuleSet and visible key from being selected by rule resolution. However, a blocked rule may block other rules in any RuleSet, and a blocked rule stops rule resolution from finding rules in higher Applies To classes. A withdrawn rule affects other rules only in one RuleSet and one Applies To class.

When you skim a RuleSet version that contains a blocked rule, the resulting RuleSet version does not contain the blocked rule or any rules that the blocked rule blocks. When you skim a RuleSet version that contains a withdrawn rule, the resulting RuleSet version contains the withdrawn rule.

Diff b/w Blocked and Withdrawn Rules

A blocked rule and a withdrawn rule are both invisible to rule resolution. Similarly, both blocked rules and withdrawn rules prevent lower-version rules with the same RuleSet and visible key from being selected by rule resolution. However, a blocked rule may block other rules in any RuleSet, and a blocked rule stops rule resolution from finding rules in higher Applies To classes. A withdrawn rule affects other rules only in one RuleSet and one Applies To class.

When you skim a RuleSet version that contains a blocked rule, the resulting RuleSet version does not contain the blocked rule or any rules that the blocked rule blocks. When you skim a RuleSet version that contains a withdrawn rule, the resulting RuleSet version contains the withdrawn rule.