Improving response time by caching rules with the Static Assembler
The Static Assembler allows you to pre-assemble and cache the rules of an application. 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 access the Static Assembler landing page, click
.To assemble an application, select the application from the list available in the Application Name drop-down control.
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 started. |
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. |
This facility is available to those users who hold the Pega-Landing.pxStaticAssemblyControl privilege.
Rule types included in static assembly
The following types of rules are evaluated by the Static Assembler for pre-assembly:
|
|
|
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.