Back Forward Landing PagesSystem category — Static Assembler page

Access

Category

Page

System

Tools > Static Assembler

Usage

The Static Assembler allows you to pre-assemble and cache the rules of an application. 6.3 Such pre-assembly is optional, but improves the response time for interactive users after system startup, especially after new RuleSet versions are imported into a system, many rules have changed, or user profiles have changed to allow new or different RuleSet versions.

To assemble an application, select the application from the list available in the Application Name dropdown.

Click Start Assembly to begin processing. The page changes to show progress. Processing may take several minutes or more, depending on the size of the application and other system demands.

Click Stop Assembly if you want to abandon this process. No assembled rules are retained.

History of Assembled rules

The history display summarizes past use of this facility.

Field

Description
Application Application name.
Assembled at Time Date and time assembly was starts
Rules Assembled Count of rules successfully assembled.
Rules Skipped Count of rules not eligible or not requiring rules assembly.
Total Rules Count of rules in the application.
Status Status
Download Logs Click to download a ZIP file containing more detail.

Notes

This facility is available to those users who hold the Pega-Landing.pxStaticAssemblyControl privilege.

The results of this processing depends on whether your own requestor session uses the Application-Based Assembly (ABA) mode or the older rules assembly mode to find assembled rules. In turn, your mode is determined by the prconfig setting fua/assemblyCacheMode that controls ABA operations for your node and the value of the Revert to previous generation caching checkbox on the Settings tab of your access group. If your mode changes, you should re-run the static assembler. See Understanding Application-Based Assembly mode.

Rule Types Included in Static Assembly BUG-73207

The following types of rules are evaluated by the Static Assembler for pre-assembly:

  • Access When
  • Activity
  • Case Match
  • Case Type
  • Control
  • Data Transform
  • Decision Table
  • Decision Tree
  • Declare Expression
  • Declare OnChange
  • Declare Trigger
  • Edit Input
  • Edit Validate
  • Flow
  • Flow Action
  • Harness
  • HTML
  • HTML Fragment
  • JSP
  • List View
  • Map Value
  • Navigation
  • Paragraph
  • Report Definition
  • Section
  • Skin
  • Summary View
  • Validate
  • When
  • XML Stream

Other rule types, such as Application, Class, RuleSet, RuleSet Version, List, Property, Application Specification, Binary File, Work Parties, Product, etc., are not considered for the assembly process.

UpTools — System
UpDesigner Studio — About Landing Pages

Help System home pageHelp Home