Beruflich Dokumente
Kultur Dokumente
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
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
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