Optimizing Your Primary Page Configuration in Pega Systems

Primary Page in Pega

When optimizing your primary page in Pega configuration in PRPC Systems, understanding the character limits and best practices is essential. Here’s a focused summary of the key aspects.

Primary Page in Pega
Primary Page in Pega


1. Primary Page in Pega Character Limit:

  • Pega does not enforce a strict character limit on the primary page.
  • Individual text properties typically have a default limit of 64,000 characters but can be configured.

2. Best Practices Primary Page in Pega:

  • Manage Data Page Size: Keep data pages small by limiting the scope of the data.
  • Clipboard Management: Ensure efficient use of the clipboard to avoid performance issues.
  • Declarative Processing: Use declarative rules to maintain data consistency without loading excessive data.
  • Paging and Chunking: Load large datasets into manageable pieces.
  • Data Management Policies: Define policies for data retention and clearance to free up memory.
  • Optimization Tools: Utilize tools like Performance Analyzer (PAL) and Database Trace for monitoring and optimization.

Character Limits and Data Management:

  • Character Limits: While the primary page itself does not have a strict character limit, individual properties on the page might. Text properties typically default to 64,000 characters, but this can be adjusted based on requirements.
  • Efficient Property Use: Limit the number however, size of properties loaded onto the primary page to only those necessary for processing.

Performance Best Practices Primary Page in Pega:

Primary Page in Pega
Primary Page in Pega

1.Data Page Size:

Scope Limitation: Only include necessary data. Avoid loading entire data sets when only subsets are needed.

Use References: Reference external data pages instead of duplicating data on the primary page.

2.Clipboard Management:

Memory Management: Regularly monitor clipboard size using Pega’s performance tools. Clear unnecessary data promptly.

Scope Appropriately: Use the lowest possible scope for data pages (Thread, Requestor, Node).

3.Declarative Processing:

Use Declarative Rules: Ensure data consistency with declare expressions, constraints, and triggers. This minimizes manual data handling and reduces errors.

Smart Referencing: Use references to declarative data instead of copying large amounts of data onto the primary page.

4.Paging and Chunking:

Data Segmentation: For large datasets, implement paging mechanisms to load data in chunks. This reduces memory load and improves response times.

Lazy Loading: Load data only when it is needed, rather than all at once.

5.Data Management Policies:

Retention Policies: Define clear policies on how long data should stay on the clipboard. Automatically clear data that is no longer needed.

Archiving Strategies: Implement strategies to archive data that is not required immediately but may be needed for future reference.

6.Optimization Tools:

Performance Analyzer (PAL): Regularly use PAL to track performance metrics and identify bottlenecks related to data handling.

Database Trace: Use Database Trace to monitor  however, optimize database interactions, ensuring efficient data retrieval and storage.

7.Property Optimization:

Indexing: Index frequently accessed properties to speed up data retrieval.

Normalization: Normalize data where possible to reduce redundancy and improve efficiency.

8.Rule Design:

Modular Design: Break down complex rules into smaller, reusable components. This helps in managing data more efficiently.

Rule Performance: Regularly review and optimize rule performance to ensure they are not unnecessarily loading large data sets.

9.Monitoring and alerts:

Automated Monitoring: Set up automated monitoring however, alerts for clipboard size and performance metrics. This helps in proactively managing potential issues.

Before we talk about it, let’s give a simple example. Open a child activity, execute it, and trace it. Every rule runs on a page that is called the primary page.

At the first record, we see that activity begins on step page “RunRecordPrimaryPage.”  That means activity has run on the page “RunRecordPrimaryPage.”.

Now do the same for parent activity: run and trace it.

Here we can see child activity execution started on a page called “ParentPage”.
  1. Any activity (rule) that is executed independently (without being called from any other rules) starts’s execution on the page “Run Record PrimaryPage” and is called the “primary” page.
  2. If a rule is called from another rule while a specific page is mentioned, then it runs on the same page. Here, Parent Activity runs on RunrecordPrimaryPage”; that means the primary page for parent activity is “RunRecordPrimaryPage”.
  3. If a rule is called from another rule while no specific page is mentioned, then the rule runs on the same page as the parent rule.


Activity1 (Page1)

Call Activity 2 NO StepPage (Primary Page of Activity 2 = Page 1).


Activity 3 NO StepPage (Primary Page of Activity 3 = Page 1)


Activity 1 (Page 1) (Primary Page -> Page 1)

call Activity2 Page2 (Primary Page of Activity2 = Page2)


Activity 3 NO StepPage (Primary Page of Activity 3 = Page 2)

Examplee3 :

Activity1 (Page1) (PrimaryPage->Page1)

Call Activity 1 Page 2 (Primary Page of Activity 2 = Page 2).


Activity 3 Page 3 (Primary Page of Activity 3 = Grade 3)

Primary Page in the Case of Flow:

How do I call an activity in a flow using the utility shape?

If we want to call an activity in a flow using a utility shape, the activity type must be utility.

Activity type can be chosen under the security tab of the activity rule form.

Calling child activity in a flow utility:

Open child activity and go to the security tab. Choose activity type utility. Create a new flow, Remove the assignment and add a utility shape. Double-click on the utility shape; when we run this activity, it will be executed in background.

Here we can see activity execution started on pyWorkPage.

Here, the primary page of the activity is pyWorkPage.

For Flow, the primary page is pyWorkPage.


Upon running a flow, the Primary Page is set to PyWorkPage.

When we run a stand-alone activity, Primary Page = Run Record Primary Page

When we run any content in the portal, all UI content runs on the primary page, which is pyDisplayHarness.

PRPC provides a keyWork for Primary Page = “Primary.”.


By focusing on these practices, you can optimize the performance and efficiency of your primary page in pega configuration in Pega PRPC Systems.

More topics on technology click here






Leave a Comment