Class group work pool diff

A class group is an instance of the Data-Admin-DB-ClassGroup class.

A class group instance causes the system to store the instances corresponding to
two or more concrete classes that share a common key format in a single databas
e table. The name of the class group is a prefix of the names of the member clas
ses.
Class groups are commonly used to cause the system to store instances of similar
or related work item concrete classes together in one relational database table
. This is known as a work pool. Work pools are referenced in access group instan
ces
Tickets on Assignments:Ticket can be set to Assignment but cannot be called from assignment. Tickets ca
n be called only from activity Obj-Set-Ticket
Declare expressions
Field Description
Target Property Data
Select to determine how often Process Commander recomput
es the value of the Target Property (identified in the second key part).
Calculate Value Select an option to determine which events cause this rule to ru
n:
Value Description
Whenever inputs change (Default). Forward-chaining recomputation. The target pr
operty is not recomputed when the property is used as a source, only when one of
the expression inputs change. If the target property is not present on the page
when needed or is present but has no value, the Declare Expression rule does no
t run.
When used if no value present Compute when the value is null, blank, zero, or
does not yet appear on the page. Assuming the computation results are not null,
later requests for the target property do not cause the Declare Expression rule
to run.
When used if property is missing
Recomputation when the target property i
s not present on the clipboard.
Whenever used Just-in-time recomputation even when the property already has a
value, using backward chaining.
This choice ensures that the target property value matches the computed value a
t the start of every activity step, by evaluating the rule upon every read acces
s of the target property. Because this choice can be costly in terms of performa
nce, a warning icon appears when you save the rule form.
During backward chaining computations, if the Otherwise section of a decision t
ree or decision table, or the Default row in a map value rule referenced in a De
clare Expression rule can be computed, but properties needed for other parts of
the form are not defined, the Otherwise value is returned as the value of the ru
le. (In Process Commander releases before 5.3, this condition produced an except
ion that ended processing.)
When applied by a Rule Collection
Causes this Declare Expression rule to e
xecute only when referenced during a collection rule execution (Rule-Declare-Col
lection rule type). Expressions of this type can be self-referential; for exampl
e:
MyProperty=.MyProperty+1.
As a best practice, select Whenever used when the expression involves values fr
om properties on multiple pages.
Declare trigger in Tracer
Using the Tracer, you can watch the evaluation of a Declare Trigger rule if the
Execute field value is Immediate:
1.
Start the Tracer and select a requestor session.
2.
Click the Options button ( ) and check the Declare Trigger box in the Ev
ent Types to Trace section.
3.
Select the RuleSet that contains the rule to be traced.
4.
Use this method to initiate backward chaining computations for the value
of a property, based on Declare Expression rules.

5.
For example, the standard activity Work-.VerifyProperty
referenced in th
e standard flow action Work-.VerifyProperty calls this method.
6.
Parameters
7.
This method has four parameters:
Parameter
Description
GoalProperty
Identify the property to compute. This must be the Target Proper
ty key part of a Declare Expression rule.
AlwaysRecompute Select to force the system to compute the value of the property
identified in the GoalProperty parameter even when the property already is prese
nt on the clipboard and has a non-null value.
In most cases, leave this box cleared, so that the Compute Value field in the De
clare Expression rule applies.
AlwaysForwardChain
Select to cause the system to forward chain after backwa
rd chaining, even when the goal-seek attempt failed. If not selected, when goal
seeking fails, any property changes made by the goal seek process are not consid
ered for forward chaining.
In most cases, leave this box cleared.
MissingReference Property
Optional. Enter a target property, a local varia
ble, or an activity parameter. When backward chaining fails to compute the prope
rty identified in the GoalProperty parameter, the method stores name of the prop
erty that prevented the computation from completing there.
8.
Results
9.
This method uses backward chaining on the dependency network defined thr
ough Declare Expression rules to compute or recompute the value of the goal prop
erty.
10.
The system uses the GoalProperty parameter and class of the step page (o
r primary page) as the Applies To key part to search for the Declare Expression
rule. It then uses the Declare Expression rule to starts backward-chaining compu
tations to obtain a value for the property.
11.
If backward chaining is successful, the result is a new value for the pr
operty identified in the GoalProperty parameter. (Other properties may also have
new values, all consistent with Declare Expression rules and other declarative
rules).
12.
If the backward chaining computation is unable to compute a value for th
e GoalProperty property, it may return instead the name of another property (ide
could contribute to the c
ntified in the third parameter) that if it had a value
omputation. Your application may then prompt a user for a value for this propert
y, or use other means to obtain this value.
13.
For more information, see More about Declare Expression rules.
Validate rules : Obj-validate(to call validate rule) and property-validate from activity
Validate rule in flow action
Validate rule can be called from correspondence prompts tab
Purging
You can purge all work objects from a system and reset the work object ID number
ing to 1 in pc_data_uniqueid table in Pega.
Stop the server. Using an SQL tool, open the PegaRULES database. Truncate all ro
ws of six tables:
pc_work
pc_assign_workbasket
pc_assign_worklist
pc_history_work
pc_index_workparty
pc_link_attachment
Purge/Archive wizard
Define criteria and a schedule for purging resolved work items from the system.
Property-Alias
Create property alias rules to provide an alternative name, more meaningful to u

sers who may be developing or updating function alias rules.

In V5.4 and earlier releases, property alias rules can be referenced in list vi
ew rules. This use of property alias rules is deprecated beginning with V5.5.
How do you display an image dynamically in a list view rules based different typ
es of urgency?
Same we should write a html rule and place it in format of a proerpty in list vi
ew as we discussed.
Trace Agents
1.)
Delay the agent.
2.)
Identify the agent in requestor Management with ruleset/ delay time.
3.)
Start the Tracer from Start tracer option in Requestor Management on the t
op
Diff. b/w Major, Minor and patch.
The major version number of a RuleSet version consists of the first two digits o
f the complete version number. For the RuleSet version Alberta:04-01-07, the maj
or version number is 04 and the minor version number is 01.
The Skim operation creates a new major version.
Rules in versions below the major version are not visible to rule resolution. If
your RuleSet list includes version ALPHA:04-07-15, no rules in ALPHA:03-XX-XX a
re available to you.
The minor version number of a RuleSet version consists of the middle two digits
of the complete version number. For the RuleSet version Alberta:04-01-07, the ma
jor version number is 04 and the minor version number is 01. The final two digit
s are known as the patch version.
The patch version number of a RuleSet version consists of the final two digits o
f the complete version number. For the RuleSet version Alberta:04-01-07, the pat
ch version number is 07.
d/f btw html htmlfragment
Html code when required for reuseable create a HTML Fragment.
Comparing HTML fragments with HTML rules
You can create a "universal" part in an HTML rule by using the ultimate base cla
ss (@baseclass) as the Applies To part of the key.
However, if you use an HTML fragment instead, then at runtime the system avoids
the overhead of the class inheritance algorithm. Therefore, using HTML fragments
for universal parts improves runtime performance.
not rule resolved rules.
Binary rules
Rule Resolution-------------Advantages/Disadvantages
Process Commander includes infrastructure to make rule resolution select the the
right rule at the right time quickly.
Disadvantages not found
How do you povide SLA for the workobject? A : specify pySLAName in model which
calls overallsla flow automatically.
In Connect Sql rule stored procedures are written in which tab?
In open tab of connect sql rule.
What are the type of log files we have
Ans: Alert Security, Services-PAL, Log Files and Alert Files
How do you a log a message in PRPC?
There is a method called log-message to write message to log files when error occu
rs
What is the PegaRULES Log Analyzer tool and how does it work?
Answer
The PegaRULES Log Analyzer (PLA) tool is a Web application that consolidates and
summarizes three types of logs from individual JVM server nodes in your applica
tion system. The log data provide key information about operational and system h
ealth. Developers and system administrators can use this information to quickly
identify, diagnose, and remediate issues that may be degrading or compromising:

Performance
The Alert log contains diagnostic messages that identify individual
system events that exceed performance thresholds or failures. Alert messages con
tain a set of field values that identify the alert, the conditions that caused i
t, and the state of system when it occurred.
Stability
The Pega (system) log gathers system errors, exceptions (with their st
ack trace statements), debug statements, and any other messages not specified as
alerts. The Pega log can contain messages created by your activities as well as
messages created by standard rules.
Scalability
The JVM garbage collection (GC) log provides insight into how a java
application makes use of memory.
During application processing, Process Commander writes to the performance alert
log a sequence of text entries called alert messages that identify mainly perfo
rmance-related issues or errors. The performance alert log is usually named Pega
RULES-ALERT-YYYY-MMM-DD log.
Each performance alert message is named "PEGAnnnn" where nnnn is the message ID,
which represents the system event that generated the alert. The message describ
es the event and contains other information such as the value that exceeded the
threshold, the type of requestor (for instance, browser), the activity or stream
that triggered the alert, and so on.
Security alerts are generated in the security alert log when security to a Proce
ss Commander web node server is at risk. The security alert log is usually named
PegaRULES-ALERTSECURITY-YYYY-MMM-DD log. These alerts are named "SECUnnnn." For
more information about web nodes see How Internet Application Composer works.
The alert logs contain the following alerts. The category descriptions appear on
the Process Commander My Alerts display and in the PegaRULES Log Analyzer tool.
Performance alerts
Alert Category
PEGA0001 - HTTP interaction time exceeds limit
Browser Time
PEGA0002 - Commit operation time exceeds limit
DB Commit Time
PEGA0003 - Rollback operation time exceeds limit
DB Rollback Time
PEGA0004 - Quantity of data received by database query exceeds limit
DB Bytes Read
PEGA0005 - Query time exceeds limit
DB Time
PEGA0006 - Update operation time exceeds limit
DB Time
PEGA0007 - Database operation time exceeds limit
DB Time
PEGA0008 - PegaRULES engine started
PRPC Started
PEGA0009 - PegaRULES engine failed to start
PRPC Failed Start
PEGA0010 - Agent processing disabled
Agent Disabled
PEGA0011 - Total request time exceeds limit
Service Total Time
PEGA0012 - Outbound mapping time exceeds limit
Service Mapping Time
PEGA0013 - Activity interaction time exceeds limit
Service Activity Time
PEGA0014 - Inbound mapping time exceeds limit
Service Interaction Time
PEGA0015 - Data parsing time exceeds limit
Service Parse Time
PEGA0016 - Cache reduced to target size
Cache Reduced
PEGA0017 - Cache exceeds limit

Cache Force Reduced

PEGA0018 - Number of PRThreads exceeds limit
PRThreads Limit
PEGA0019 - Long-running requestor detected
Long Requestor Time
PEGA0020 - Total connect interaction time exceeds limit
Connect Total Time
PEGA0021 - Clipboard memory for declarative pages exceeds limit
Declarative Page Memory
PEGA0022 - Rule cache has been disabled
Rule Cache Disabled
PEGA0023 - Rule cache has been enabled
Rule Cache Enabled
PEGA0024 - Time to load declarative network time exceeds limit
Loading Declarative Network
PEGA0025 - Performing list with blob due to non-exposed columns
Reading Blob Need Columns
PEGA0026 - Time to connect to database exceeds limit
Acquire DB Connection
PEGA0027 - Number of rows exceeds database list limit
DB List Rows
PEGA0028 - GC cannot reclaim memory from memory pools
Memory Pool Collection
PEGA0029 - HTML stream size exceeds limit
HTML Stream Size
PEGA0030 - The number of requestors for the system exceeds limit
Requestor Limit
PEGA0031 - Generated stream overwritten and not sent to client
Stream Overwritten
PEGA0032 - Rule change invalidated the specified threshold of entries in the Rul
e Assembly cache
Invalidated Rules
PEGA0033 - Database query length has exceeded a specified threshold
DB Query Length
PEGA0034 - The number of declare indexes from a single interaction exceeds a thr
eshold
Declare Index
PEGA0035 - A Page List property has a number of elements that exceed a threshold
Clipboard List Size
PEGA0036 - PegaRULES engine intentionally shut down
PRPC Shutdown
PEGA0037 - Rule assembly time exceeded threshold
Rule Assembly Time
PEGA0038 - The wait time for rule assembly cache access exceeds a threshold
Cache Find Synch Time
PEGA0039 - The size of a BLOB column read exceeds a threshold
Blob Size Read
PEGA0040 - BLOB size written to the database exceeds a threshold
Blob Size Written
PEGA0041 - Work object written to the pr_other table
Work Object PR_OTHER
Security alerts
Alert Category
SECU0001 - Unexpected properties received in HTTP request
Security
SECU0002 - XML received in post data for web node requestor
Security
SECU0003 - Attempt to execute a rule failed in web node environment
Security
SECU0004 - Attempt to run a stream from URL failed in web node environment

Security
SECU0005 - A Thread name in a URL contains invalid characters
Security
Tell me about the locking concept in PRPC.
A Process Commander requestor can lock an open instance if all of the following
are true:
?
The instance belongs to a concrete class that has Allow Locking? checked
in the class rule and
?
The instance has ever been saved and committed to the PegaRULES database
.
?
The requestor has an access role that conveys the privilege needed.
Locking
By default, locking a covered work object also locks the cover work obje
ct. This is desirable because the cover work object may contain totals, balances
, counts, or other derived values that require single-threaded access.
Whenever you open a work object in a modifiable mode, such as the Perform form,
your requestor acquires a system lock so that no one else can alter the work obj
ect until you are done with it. If you lose your session while such a form is pr
esented, for instance by closing the browser window, or if your session times ou
t from inactivity, the lock is later released, normally one hour after the time
the lock was established.
Locking can arise from three sources:
The most common reason a work object is locked is that someone else is working o
n it. The Lock form indicates who has the object locked.
The next most common reason is that you were working on this work object earlier
, but then your session timed out or you lost the browser -- and the time since
this occurred is still within the one hour that the lock is held. In this case,
you can click the Release Lock button at the bottom of the form.
Rarely and briefly, a work object is locked by the operator System. This occurs
when an assignment on that work object has reached its goal, deadline, or late t
ime, and the Pega-ProCom agent locks the work object for a short time to process
the service level event. If you receive such an indication that a work object i
s locked by the system, just close the Lock form and try again.

Will you try to remove the assignments shape of a flow in the production system
What is the role of the master agent
When Process Commander starts, the Agent Manager (master agent) gathers and cach
es all the agent configuration information for your system.
2. The Agent Manager launches the initial startup of all the agents by checking
each of the Agents rules and reading all the agent settings for those rules.
3. For each Agents rule, the Agent Manager determines whether there is a corres
ponding Agent Schedule data instance for each node to use to start the agents.
4. If no Agent Schedule data instance exists for this node, the Agent Manager c
reates one by copying the relevant information from the Agents rule.
What are the various ways to restrict user to edit the rules.
Using Delegated rules access roles we can make restrict the user not to edit the
rules.
Delegated rules
By design, the leftmost tab of the forms for ten rule types provides access to f
ields most likely to change over time. Although rules of any type can be delegat
ed, managers are most likely to learn and understand the following types:
?
Case match
?
Constraints
?
Decision table

?
?
?
?
?
?
?

Decision tree
Declare Expression
Flow
Flow action
Service level
Map value
When condition

Creation order of application

Org div unit
Rulesets
Application
Access group
Operator ID
Class structure