A cover is a work object that is also a parent to one or more related work objects. Typically one work party — such as the customer party — is present in the cover work object and also present in all of the covered work objects associated with the cover. The covered work objects are the children in a parent-child relationship. • By default, the system prevents the resolution of a cover work object unless all of its "member" covered work objects are resolved. Ex: Building construction (Cover) -> a) Wood work (WO) b) Plumbing (WO) c) Painting (WO). If all 3 works done (Resolved) then we can say Building (Cover) is ready to join.

• •

Cover is a work object that is an instance of a concrete class derived from the Work-Cover- abstract class. Your


includes harness rules, flow action rules, and activities that support working with covers. The covered work objects can be of differing work types. However, the work type of the cover and the work type of the covered objects must all belong to the same work pool. •

The covered work objects can be of differing work types. However, the work type of the cover and the work type of the covered objects must all belong to the same work pool.
By default, locking a covered work object also locks the cover work object. This is desirable because the cover work object may contain totals, balances, counts, or other derived values that require single-threaded access.

The standard ticket rule Work-Cover-.AllCoveredResolved alerts a cover flow that all the member work objects are resolved. If your application is to incorporate this constraint, include this ticket in the flow rule or rules for the cover work object.

• • • • •

The standard list view rule Work-.WorkInACover.ALL displays the urgency (pyUrgencyWork property), work object ID (pyID), subject (pyLabel), and status (pyStatusWork) fields as columns, without sorting. The standard local flow actions Work-.AddToCover, Work-.AddCovered, and Work-.RemoveFromCover allow user management of cover contents. The Work-.NewCovered harness rule supports entry of a new cover and cover members. Activities Work-.AddCoveredWork, Work-.AddCovered, and others support operations with covers.

One cover work object may cover multiple other work objects. When any one of the covered work objects is opened, Process Commander by default uses a conservative approach and acquires locks on the covered work object and the covering work object. This ensures that data can be updated in both objects with transaction integrity.

• •

Customize the activity DetermineLockString property-set and update it with no locking
A flow rule — an instance of the Rule-Obj-Flow rule type — is a network of shapes representing tasks and connectors (directed arrows), each with associated parameters and values. Flows govern: How work objects are created ,How they progress through one or more flow executions ,How they become resolved (completed)

Flows are the fundamental rule instances that represent business processes, identifying who works on a work object in what sequence, what decisions and processing occur automatically, and many other aspects of the business process.

Sunday, August 21, 2011


• Some applications don't require users to interact with work object forms. Flows that implement straightthrough-processing operate without user input. External portals and systems can execute flows through Active Server Pages, JavaServer Pages, Service Portlet or Service JSR94 rules, or other means. Informally, these are known as "headless" BPM applications. A collection of standard activities known as the Process Engine API simplifies building such applications. •
Application developers use Microsoft Visio to create, edit, and evolve a flow. Process Commander uploads the resulting VSD file, including the Shape Parameters details from the workstation. Both the diagram image (a JPG file) and the rule details are saved with the flow rule.

• •

You can't test a flow rule that has Availability set to No/Draft. You can test the flow rule if the Availability is set to Yes, even if the Visio DRAFT mode ( ) is in force, indicating that not all the activities, properties, or other rules are yet defined.

At runtime, a user can start the execution of a flow by entering a new work object. The system examines the property pyFlowName, in the model instance for the class, to determine which flow to start. We can think of the flow operating on the data (properties) in the work object until the flow finishes or the work object becomes resolved The system generates a unique work object ID for a new work object. (This occurs for starter flows, those for which the Creates a new work object? box on the Flow form is selected.) Flow creates assignments for human users reflecting the need for more facts, judgments, and places the assignment into an appropriate user worklist or workbasket. After a user (or in some cases an agent or external participant) perform an assignment, the work object progresses farther through the flow.

• •

• • •

The Process Explorer tool presents — for the currently selected application — starter flow rules and the subflows they call in a graphical form. A flow rule that contains no assignments, and so can execute from start to end without human input, is known as a straight-through process. A flow rule that consists only of assignments or decisions and meets other criteria is known as a screen flow. A flow that creates a new work object is called a starter flow. Processing of a subflow is synchronous, meaning that the calling flow execution pauses for the duration of the subflow. When the subflow execution reaches a Flow End shape, the calling flow can continue.

• •

The Split/Join facility (

) supports such asynchronous operation, by allowing processing of two or more subflows to proceed in

parallel. For ex: Loan processing: 1) Loan Credit Process 2) Fraud checking .Both are different subflows. Eg: Standard flow Work-.ParallelWork

Use a Split-ForEach (

) shape to iterate over the pages of a Page List or Page Group property. For each page, you can

conditionally start a flow execution for the work object. Processing can resume after any one, or all, of the subflows end. Eg: standard flow Work-.StandardApprovalsAll

We can't use the Split-ForEach shape to create work objects. At runtime, this shape process the work object's embedded Page List or Page Group properties; the embedded pages must exist before the SplitForEach shape is reached.

Sunday, August 21, 2011


As a best practice. On Another Work Item to start processing on a different work object.AddCovered.AddtoCover to start a new flow execution. August 21. Use the Flow shape rather than a Spin-off shape to start a synchronous flow execution. ensure that everyone in your development team is using a common version of Visio. Users can select the standard flow action Work-. pyLastFlowStep — Internal name of the most recent shape or connector processed pyNextFlowStep — Internal name of the next shape or connector to be processed pyFlowParameters — A classless page containing parameters used to start this flow As a best practice. errors. Sunday. Process Commander operates identically whether you use Visio 2002 or Visio 2003 (also called Visio XP). Identify the objects the flow rule is to update.BPM and BRE • • • A Spin-Off task ( ) starts asynchronous execution of a different flow. As a best practice. but the tasks corresponding to the unreachable shapes will never be performed. special cases. and similar exceptions. The integer property @baseclass. review carefully any shapes that turn gray. revise the flow to call or branch to subflows to handle continuations. Processing of the current flow does not pause or wait for results from the other flow.pxFlow contains a page of facts about each execution: pyFlowType — Second key part of the flow rule pxAssignmentKey — Key of the current assignment instance for this flow execution. Select: 1) 2) 3) • • • 1) 2) 3) 4) 5) • On Current Work Item to continue processing on the current (unresolved) work object in the next flow. in which the current flow execution pauses while the subflow executes. On Embedded Page to apply this flow to an embedded page. The Page Group property @baseclass. Work-. 2011 3 . delete the gray shapes or add a comment as to why they are present. typically an instances of the Assign-Workbasket or Assign-Worklist class. Flow rules containing too many shapes can introduce complex. on the same work object or a different work object. SmartBuild guardrails recommend limiting a flow rule to contain 15 or fewer shapes. • After saving a flow rule. difficult-to-debug processing into your application. You can save and execute a flow rule that contains unreachable shapes.AddFlow. not counting Notify and Router shapes. rollbacks (sometimes called compensating transactions). • • You can save and run a flow rule in draft mode in systems where the production level is set to a value less than 5. If your flow grows to contain more than 15 shapes. or Work-.pxFlowCount indicates how many flow executions are in process for the work object. • Include tickets and utility tasks to accommodate cancellations. or non-mainstream processing.

use a when rule. iteration within an activity is limited to a single step. decision tree rule. Agents are not true authenticated users and by default cannot run activities that are restricted to authenticated users. • Accordingly. or activity methods are available.BPM and BRE • • Choose likelihood values that are initial guesses. you must make a separate activity and include the Call statement in the original activity. or parse rule whenever these rule types capture the business requirements well. Limit hand-coded Java. If your processing need requires two or more steps. Flow Analysis button on the Activity rules provide you with one way to automate the processing of work using a procedural. clear this check box if the activity is for an agent. Similarly. Limit activities you create to fewer than 25 steps. Reserve your valuable time and Java skills for implementing things that do not already exist. rather than procedurally. Security tab is checked. However. more appropriate rule types. • • Don't create an activity in your application when you can call a standard activity to perform the needed processing. August 21. After the flow is in use. use activities only when there are no other. 2011 4 . click the Design tab to obtain statistics for comparison. An activity is presented as a series of steps. In most cases. library functions. without requiring Java skills or manually entering Java code. For example. use a Declare Expression rule to calculate declaratively. instead of using a series of activity steps. they can run activities regardless of the • • Authenticate? Sunday. When writing activities. map value rule. Avoid Java steps in activities when standard rule types. keep the following best practices in mind: Keep activities short. with some of the same features as an object-oriented programming language—such as iterations or conditions.4 and earlier releases. this check box is ignored by agents for which the Bypass activity authentication check box (on the value. Select this check box for all but those specific activities that guests • Authenticate? need to run. program-like approach. decision table. • In V5.

See Comment tasks. 2011 5 . Fork — Supports automatic selection of one connector from two or more. Assignment-Service — Waits for an external callback from an external system using Service BPEL rules. Associate a Router task with an assignment task. Decision — Identifies an activity that can make an automated decision about the progress of the work object through this flow. See Decision tasks. Ticket — Marks a business exception that might arise at any point in the flow. FlowStart — Identifies the start task of this flow. See Fork tasks. See Spin-off tasks. See Ticket tasks. or agent other than the current user. See FlowEnd tasks. Comments do not affect execution of the flow. See Integrator tasks. Comment — Adds explanatory text comments anywhere on the flow diagram. you can associate a service level rule with it. as shown here. See Split-Join tasks. Spin-off — Starts a new flow execution and does not wait for its completion. See Split-ForEach tasks. Connectors leaving assignment tasks may be flow actions. after the assignment task is defined. Connectors leaving other tasks may be when conditions. After you enter an assignment task. Pools and swim Lanes — Identifies and groups tasks performed by separate organizational units within one division. See Assignment-Service task. Connector — Associates a task in the flow with another that may follow the first task. Split-ForEach — Performs an operation or test on each element in a repeating group. Router — Sends an assignment be sent to a user. Sunday. FlowEnd — Marks the end of the flow. See FlowStart tasks. such as a cancellation. This activity determines which worklist or workbasket is to contain the assignment. August 21. See Pool tasks. See Notification tasks.BPM and BRE Shap Description e Assignment — Creates an assignment at runtime associated with work object in a workbasket or worklist. Notification — Notifies a work party by e-mail or correspondence about the status or progress of this work object as the assignment is created. both of which must complete before the current flow resumes. you can create an associated Router task. Integrator — Identifies an activity that can connect to an external system to send or receive data. Split-Join — Sends the work object to two other flows. workbasket. See Connectors and Flow Actions. See Associating a Service Level with an Assignment. Optionally. A clock appears on the diagram. See Assignment tasks. See Router tasks.

Do not use this for assignments directly. Failure of an Integrator task causes the designated flow rule to start. 2011 6 . Another standard assignment activity Assign-. For example. To facilitate detection and analysis or repair of such events. For example. Creates an instance of the Assign-Worklist class.BPM and BRE Utility — Specifies an activity to run at that point in the flow to perform automated processing without any user assignment.rule types). Sunday. add at least one flow action.WorkList — Causes the assignment to be placed on the worklist of the current operator (or of another operator identified by a Router shape). a tested connector interface may fail or time out. the system presents available flow actions in a selection list. The assignment normally appears on the worklist of the user who executes the flow. exceed normal limits. sending a temporary assignment by e-mail to a party identified in the work object who is not an interactive Process Commander user.WorkBasket — Causes the assignment to be placed in a workbasket. For every assignment.AddHistory. Process Commander automatically adds an instance to the work object history. A Declare Expression rule records this in property Work-. • Flow processing of a work object normally pauses when it reaches an assignment shape until a user completes the assignments. causing work object processing in the flow rule to halt. Work-. and so on. you may want to define and include local flow actions that let users bypass approvals. The flow rule can send out e-mail correspondence. an integrator task can connect to a customer master database to retrieve account balances or verify account numbers and status. with connector flow actions (sorted by decreasing likelihood) appearing above local flow actions. Work-.External — Starts the directed Web access feature. • • Execution of the standard Utility activity Work-. or send an assignment to someone. when a flow execution completes processing for most shapes. and other activities that call the History-Add method for a work object can add instances to work object history. Work-. Integrator tasks use activities (with Connect as the Activity Type) that call connector rules (Rule-Connect. See Utility tasks. attempt retries. • At runtime. Work-. you can designate in your application a flow rule for connector exceptions. • • • • • • • • • • Add an assignment task for each place in the business process that requires human judgment and input.Connect activity is used internally when creating an instance of the Assign-Connect class and to support BPEL processing. By default. Creates an instance of the Assign-Workbasket class. Select one or more local flow actions that are to be available at runtime from the assignment.pyTotalFlowActionCost. cancel assignments.For various reasons.Agent — Sends the assignment to a background process rather than to a person (rarely used. For each work object. similar to WorkBasket ). the system computes the sum of these cost values for the specific path it takes through the flow rule. determined by an associated Router shape. August 21. skip over the integrated step.

class but are not part of the Process Engine API. The flow rule references a data instance that does not exist. 2011 7 . access group. or subflows.@baseclass. Use Work-. If you prefer. privilege ReconcileProblemWork is listed in the Access of Role to Object rule for the role PegaRULES:SysAdm4. ProblemFlowsForCurrentOrganization.5 or later. • For flows created or edited with V5. and so on. in a different attachment category. The flow execution is stuck.FlowProblems (using the same work object ID). none of the outgoing connectors evaluate to true. Sunday. versions. releases the lock and sends back HTML code that closes the work IFRAME. A problem flow can be caused by many different conditions. work group. Work-.Action NotifyQuick Work-. We can override the standard routing activity Work-. network. service level. privileges.DoClose Executed when the operator clicks the close button on a work object form. When it detects a problem flow. operator. capabilities of users. Calls Work-. access roles. To NewCategory Work-. organization. An activity has failed. the Router shape is optional. • • • • • By default. These list view reports include ProblemAssignments.A problem flow execution (or problem flow for short) is a list report of a paused flow rule execution for a work object. Examples: workbasket. The conditions cause a problem flow execution to start: The flow rule references a rule that does not exist. you can record the Router activity directly in the Assignment shape or Router Pool shape ( panels. harness. Creates a new cover work object and performs a Commit method.CloseWorkItem. ProblemAsssignmentsForCurrent Organization. Work-. relating to the flow rule. The database. ProblemFlows. or other prerequisites to execute. Work-. or a connector rule has failed or timed out.CorrUpdate Updates correspondence. map value.AddCovered Purpose Creates simple correspondence. the properties in the work object.AddCoveredWork rather than Work-.ConnectionProblem provides a default approach to exception handling.CloseWorkItem Closes the work object. Examples: an activity. in that following a decision shape. August 21. which saves the work object and releases all locks.toProblemFlowOperator in each application to send these to a different worklist or to a workbasket. ) properties These activities apply to the Work. Process Commander by default starts the standard flow Work-. which enables these operators to view reports that contain all flow and assignment errors. and other data. decision tree. hardware. or system software has failed. The work object contains invalid data that causes one of the above conditions.CopyAttachment Makes a copy of (the most recent edition of) an existing attachment.BPM and BRE • The standard flow rule Work-. Full Name Work-. or a rule that a user (or agent) executing the flow lacks RuleSets.AddCovered in situations where the Commit method is not wanted until later.

another to verify the information and calculate payments.class or a class derived from Work-. simplifies the flow diagram by eliminating a fork or decision shape.) See How to customize the activity success and exception windows. Full Name Purpose @baseclass.BPM and BRE Work-. Such activities must not use any methods that directly change the properties or the database. During flow processing. Each lane has a router activity associated with the assignments within it. this activity forces completion of an assignment and advances the flow execution along a specified (connector) flow action.RandomSelectio Supports statistical sampling. If you prefer. Connect.) See How to customize the activity success and exception windows.ActivityStatus Presents a form when a top-level activity completes with presenting an HTML display.getFlow ProblemOperator Work-. Typically referenced in an Operator ID instance.ShowDesktop Causes the portal to be displayed after log in. and a third to issue payments and update financial records. For flows created or edited with V5. Declare Expression. CodeSupports the Single Sign-on feature. For example. If the activity uses the TaskStatus-Set method to one of a few possible activity outcomes. ("Please contact your System ExceptionHandler Administrator . You want each to have its own work group and workbasket. Referenced in standard harness forms.com) who receives assignments for flow problems. the Notify shape is optional. An activity executing anywhere in entire Process Commander application can set or raise this ticket by executing the Obj-Set-Tickets method with this ticket name as a parameter. Work-. • • For an activity in the Work. Back Office. August 21. 2011 8 . one for each status value. A value of Utility. Supports the Get Next Work button on the Confirmation harness form.LogOff Ends a requestor session. the router assigns the work object to the appropriate workbasket inside the lane. Router Pool and Swim Lane shapes to organize and graphically identify a related group of task shapes that are performed within a specific work context (typically a work group) or business purpose.5 or later. You create a pool named Insurance Claim Process containing three swim lanes named CSR. Assign. Select for an activity supporting locatable pages.EmailSend Sends e-mail correspondence. • • • • • • • • Declare Expression rules do not evaluate during the execution of an OnChange. an insurance claim application has one assignment instructing operators to collect customer information. Select for an activity to be executed automatically by a Declare OnChange rule. Work-. @baseclass. Notify.activity. See Portal basics — Using the Process Work workspace for advanced notes on this activity. "REJECT". Using three connectors from the utility. Can be called by an agent. Work-. A capability called locatable pages reduces the need for pages to be explicitly named in the rule. but returned no content. the Activity Type field (on the Security tab) of an activity determines whether it can be used in a flow shape. You cannot attach a Router shape to an assignment in a swim lane. See flow problems.ResumeFlow Typically called when a service level deadline or goal is not met. the outgoing connectors can depend on this Status value. Security. ("The operation completed NoContentHandler successfully." with green checkmark.WorkPartyRetrie Refreshes the party identity in a work object. Data-Corr-. n Work-. Retrieves an assignment from a user's worklist or from a workbasket. These pages can be used to find pages referenced in a when condition.AppAuthenticate Code-Security.ActivityStatus Presents a form when an activity fails or an uncaught Java exception occurs. Data-Portal. a utility activity might return the values "HIRE". and "WAIT"^ through a TaskStatus-Set method.StartNewFlow Starts an additional flow execution on the current work object. or constraints rule. or Route indicates that the activity can be referenced directly in a flow task of the corresponding type. and Fulfillment. OnChange activities must not perform any forward chaining themselves.GetNextWork Identifies the operator (by default Administrator@org." with red X. you can record the Notification activity directly in the Assignment shape properties panel. ve These standard activities apply to a class other than Work-. Locatable pages can be used with these rule types: Constraints (Rule-Declare-Constraints rule type) Sunday. For example.

including embedded properties. Instead of rewriting the called activity's steps in the calling activity.S. • You can use as selection criteria only those properties that are exposed as database columns. For example. or share the parameter page of the calling activity. • A declarative page is a clipboard page created by execution of a declare pages rule (Rule-Declare-Pages rule type). you can reference the activity. The first time each evening (after the 4:30 P. Sunday. The main advantage of being able to call an existing activity is reuse. they are created only when first accessed. New York market close) that a requestor attempts to access the page. • The Obj-Browse method searches instances of one class and copies specified properties onto the clipboard. • Declarative pages are not created at system startup. declarative pages do not persist. the system automatically loads the page with the latest end-of-day prices. creating a list of instances. the method can retrieve values of properties that are not exposed as columns. a declarative page may hold last night's closing U. This method differs from the Obj-Browse method by not allowing you to define search criteria. This eliminates the need for the developer creating the when condition rule to specify the page. • A completed Obj-Browse method is similar to a SQL statement of this form: Select <FIELDS> from the <OBJCLASS> where <CONDITIONS = A VALUE> and place them on the <PAGENAME> page. 2011 9 . each on an embedded page. stock prices in a Value Group property indexed by ticker symbol. The page can remain unmodified in memory until the next day's closing. or in an external database table that is linked to an external class.BPM and BRE Declare Expressions (Rule-Declare-Expressions rule type) When conditions (Rule-Obj-When rule type) References to properties on a locatable page use the locate keyword in lowercase as a prefix to or initial portion of the page name. The returned instance is then converted to a clipboard page. • The Obj-Open method returns a single instance stored in the PegaRULES database. as in: locateCustomer. you must identify the key of the instance. • The Page-Copy method replicates the entire contents (all properties and embedded properties) of an existing clipboard page to a new or existing clipboard page. • The Call method instructs the current activity to find and run another activity using Rule Resolution.OrderAmount At runtime. August 21. the system uses backward chaining and an activity with type Locate to find and (if necessary) add the proper page to the clipboard. The called activity can use its own parameter page. Configure this by selecting the Pass the current parameter page? option in the method parameters. • Declarative pages can improve performance and reduce memory requirements when all or many requestors in an application need to access static information or slowly changing information. so that the property reference Declare_Stock. • Ordinarily. However. the calling activity resumes processing. After the called activity completes.Price("IBM") is the closing price for IBM shared. they are not saved to the PegaRULES database but are reconstructed when next accessed and the previous version is expired.M.

an approach known as call-by-reference. and system response • Use the Branch instruction to cause the current activity to find another specified activity and branch to it without a return. The lists are: • • Current list — highest priority Activity list — intermediate priority Sunday. detailed debugging for activities.BPM and BRE • The Page-Remove method deletes one or more named pages from the clipboard. control returns to the calling activity. For more complex activities. the tools variable • • identifies the PublicAPI class. Do not enter a constant as the value of an output parameter. For a complete list of available PublicAPI Java methods. complicate debugging. the Utility type activity can use the TaskStatus-Set method to return a text value in the pxTaskStatus property to the flow as a basis for decisions. • Use of explicit class names can introduce inflexibility. or it can share its own parameter page with the called activity. use this syntax: pega_rules_string. When that activity completes. • • • @CurrentDateTime() is a standard function rule that returns the current system date and time . • Flow processing automatically controls locking and transaction boundaries for work objects. Each function rule belongs to a RuleSet. a standard library named String is defined in the Pega-RULES RuleSet. This method is primarily used for debugging. refer to each library by its RuleSet and library name. stored in Java constructs. The Tracer tool provides powerful. Using this method can simplify flow diagrams by eliminating fork or decision shapes that follow a utility shape. pyWorkPage. • The Show-Page method sends an XML representation of the current page (as specified in the Step Page field) to your browser window. By convention. consult the Public API JavaDocs. Eg: Call Data-Admin-Operator-ID.Account). even when run by others or in background. The Performance tool provides comprehensive statistics about resources consumed by a requestor.pyUserIdentifier property is set to the parameter defined on the Parameters tab of an activity. Do not use the Commit method (or the Obj-Save method with the WriteNow parameter selected) in any custom activity called by a flow. • The calling activity can provide input parameters to the called activity. Three tools support developers as they work with activities: • • • The Clipboard tool lets developers examine and alter the contents of their clipboard. 2011 10 . the Clipboard tool and Tracer tool are valuable debugging aids. August 21. For example.Analyze • Do not use a local variable to hold an output parameter. To reference this library in your Java. • Use the Call instruction to cause the current activity find another specified activity and execute it. and reduce opportunities for rule reuse. • Optionally.equalsIgnoreCase ("ABC123DEF". avoid this format whenever possible. Connectors leading from the activity can be based on this status value. Process Commander maintains three activity lists for each requestor. To call a function rule from a Java step.

You can set break points for specific steps in activities. 2011 11 . Use the Tracer to test and debug activities. To see pz properties and other clipboard entries that aren't truly properties. declarative rule. It resides in memory on the server.clipboardViewerUpdate privilege. Each Tracer session on the node uses a separate file in the temporary file directory on the server. decision rules. Edit the prconfig. 2. delete. and modify pages using the Action menu Quickly start activities and flows using the Action menu The clipboard has a hierarchical structure based on XML. You can see in summary or detail the processing that occurs as you or another requestor executes an activity. parse rules. or to track the growth and contraction of your clipboard over time. Action menu items that update the clipboard contents are available only to users who hold the @baseclass. Select Run > Performance. To use an in-memory buffer rather than the file buffer.000 events. service rules.clipboardViewer privilege. or flow rule. but not its size in bytes. This can improve performance of the requestor session being traced so that elapsed time statistics during tracing are closer to the normal value (when not being traced). These standard properties support internal operations. If you omit the second line. The Clipboard display doesn't include properties with names that start with pz. The Clipboard display shows the contents of the clipboard. use the Tracer. Stop and restart (or redeploy if necessary) the server node to have the changes take effect. To see the contents of unnamed pages. August 21.xml file to contain two lines: <env name="tracer/queue/type" value="file" /> <env name="tracer/queue/file/limit" value="nnnnn" /> where nnnnn is a non-negative integer. As you interact with the Clipboard tool at your workstation. change the value for the type from "file" to "memory": <env name="tracer/queue/type" value="memory" /> Business Process Management is the organizational activity "that incorporates: • • • • • Planning Designing Building Operating Maintaining Sunday. update. To adjust the size of the Tracer file buffer: 1. The Clipboard tool is available only to users who have access to the @baseclass. Select the Abbreviate Events box to reduce the quantity of detailed clipboard detail sent to the Tracer.BPM and BRE • Workflow list — lowest priority Use the Clipboard tool when developing and debugging to: • • • • Examine property values and messages associated with them Find the information necessary to reference a property — the page names and the property name Quickly create. you see a static snapshot copy. then click the Add Reading with Clipboard Size link. • You can use the Performance tool to see the size of your clipboard in bytes. Large clipboards can affect performance because memory in the Java Virtual Machine supporting Process Commander holds the clipboards of all requestors. and flows. right-click in the left panel and select Show XML. The standard access role PegaRULES:SysAdm4 provides these privileges. the default limit is 50.

decisions. known as goals. by ensuring compliance with business policies. and other applications through services. Each service level rule defines one to three time intervals. August 21. as important as facilities. supporting access to external systems. a developer can set a goal of 30 minutes to call a customer back and a deadline of four hours. the service level rule is identified in the standard property . " Business processes are capabilities. nonprogramming form. and late intervals. assignments. and uses advanced software techniques to compute the consequences and results of rules. PegaRULES supports declarative rules. and giving visibility to work in process.) For the overall work object. highly scalable and reliable. multithreaded execution and a large number of industry interfacing and standards. (The time interval starts when the assignment is created. and automated processing. Sunday. not when a user begins processing the assignment. A business rules engine is a software component that allows business rules to be recorded in a non-procedural. and technology. routing. The PegaRULES component of PegaRULES Process Commander provides a powerful rules engine supporting business process management. they must be managed from inception to retirement. The business rules engine can be embedded or called from another system using Service JSR94 rules. Developed in Java. people. that indicate the expected or targeted turnaround time for the assignment. 2011 12 . deadlines. Process Commander supports Simply Smart Business Process Management through rules covering flows.BPM and BRE and improving the business processes and their enabling capabilities forever and for everyone. typically set up through a model for the class. or time-to-resolve for the work object. Process Commander supports exceptions management applications and the staff that processes exceptions. A service level rule is an instance of the Rule-Obj-ServiceLevel type.pySLAName. Like other assets.

Service Level Advanceflow Default NotifyAssignee NotifyManager TransferToManager NotifyandTransfer Purpose Push the assignment along a flow action automatically. The activity Data-Corr-. 2011 13 . The agents in this rule provide the following types of processing: • • • • • • • Processing service level events and escalation Applying a flow action to assignments in bulk Sending out e-mail correspondence Archiving and purging work objects. TransferToWorkbasket Transfer assignment to a workbasket when it is open at deadline time. Sends e-mail to the assignee's manager upon reaching the deadline time. and the late interval defines post-deadline times.ProcessEvents supports service level processing for both assignments and work objects. If an assignment is not completed before the time limit. Each time interval is in days. Service level rules define three time intervals. Sends an e-mail reminder to assignee upon reaching goal time or deadline time. and so on. minutes. when requested through the bulk processing feature of the Process Work workspace of the WorkUser portal. escalate the assignment. Notifies manager when the assignment remains open after one full day (goal time). Imposes a goal of two days and a deadline of five days. service level rules. archive work objects. work object history. and seconds. send an alert or e-mail message. and late intervals. Transfers the ToManager assignment to a manager after three days (deadline time). The activity Assign-. known as goal. Five agents in the Pega-IntSvcs RuleSet process queued service and connector requests and perform maintenance for PegaDISTRIBUTION MANAGER (formerly called Correspondence Output Server. Enable this row of the Agent Schedule form unless your applications use only non-BPM rules-engine facilities. send it to someone else. and assignments. The goal time is the smallest time interval. attachments. Escalation can change the urgency value of the assignment or work object. or COS). and so on.AgentBulkProcessing supports background processing of flow actions in bulk against assignments. cancel the entire flow. based on schedules The activity @baseclass.BPM and BRE The Pega-ProCom agent detects service levels not achieved — unmet goals or deadlines — promptly. deadline. escalation occurs. and work object attachment. and history Retrieving PDF files from the PegaDISTRIBUTION Manager Running tests defined through the optional Automatic Testing facility Checking incoming e-mail (deprecated in V5. • • checkPrintErrors checkFaxErrors Sunday. cancel the work. August 21. the system can automatically notify one or more parties. Service level rules can be associated with a work object or an assignment.ProcessAssignments performs periodic processing to delete selected work objects. When the time interval defined by the service level is reached without the assignment being performed (or the work object becoming resolved).getConvertedPDFsfromPDM requests that the PegaDISTRIBUTION Manager send a converted Portable Document Format (PDF) file to the Process Commander server.Send supports outgoing e-mail if your system contains one or more Email Account data instances with a second key part of Notify. Transfer assignment to manager upon reaching the deadline. the deadline time is a longer interval. The activity Assign-Archive. The Pega-ProCom agent — a background requestor — detects goals and deadlines not met and performs escalation processing.3) The activity System-Queue-ServiceLevel. hours. or initiate other processing. The agents in the Pega-ProCom RuleSet process e-mail.

PegaDISTRIBUTION Manager can also convert Word documents to Acrobat PDF format. Rows of this table have one of five record types in this table: • • CACHE — Notify all nodes of rules created. this runs every 60 seconds. • RFDEL — Indicates that a static-content rule (from one of the Rule-File-* rule types) was deleted. 2011 14 . • RUF-X — Indicates that a library was regenerated on one node. optional Windows server application used to support a Process Commander system for printing and faxing of Microsoft Word documents. If the system has run for at least an hour since startup.BPM and BRE • • • purgeRequestsTable ProcessServiceQueue ProcessConnectQueue PegaDISTRIBUTION Manager is a small. so all nodes are instructed to delete the extracted static file. The standard activity Code-. Rows of the pr_sys_updatescache database table (corresponding to the System-Updates-Cache) class form the input queue.StaticContentCleaner deletes (or "prunes") files from the server file system containing static content. August 21. which trims older rows of the pr_perf_stats table System pulse processing. Typically. all properties are searched. so that other nodes are instructed to regenerate this library. Using the System Management application. Deleting this cache is a manual option in the System Management application. The standard activity Code-. or status) has advantages and costs. where NNN is the value of the following setting in the prconfig. Allowing application users to find work objects using full-text search (in addition to structured searches based on owner. The agents in this rule provide the following processing: • • • System Cleaner System Pulse System Indexer • • • Rule Usage Snapshot Static Content Cleaner System Work Indexer Log-Usage. The standard activity Code-. typically occurs every 60 seconds. PNG.SystemIndexer updates the search index cache that supports Find and Find Content operations of the Advanced Search facility. Lucene indexes for work objects are created only when the dynamic system setting PegaRULES:indexwork/enabled is set to true. The agents in the Pega-RULES RuleSet perform general system housecleaning and periodic processing.xml file: <env name="http/staticcontentminpruningage" value="NNN" /> The SystemWorkIndexer agent periodically updates Lucene indexes to support text-based searches for work objects. Normally running once an hour. deleted. party.UsageCleaner. Consider these factors: • • • • Full text searches may reduce the chances that an application user enters a duplicate work object Full text searches do not depend on exposed columns. so other nodes are to delete their own LLC.SystemPulse. style sheets (CSS file type) and JavaScript files (JS file types) in the StaticContent folder. writing out instances of the Log-RuleUsage class and Log-RuleUsage-Details class. or updated since the most recent pulse.RuleUsageSnapshot normally runs once every 24 hours. or consolidate and compact indexes for improved search performance. INDEX — Records the need to incrementally update Lucene indexes (typically indexes are created and saved only on one node of a cluster) • DELLC — Indicates that the Lookup List Cache (LLC) — was deleted on this node. you can rebuild indexes completely. defined by the activity Code-. or GIF file type). such as images (JPG. Full text searches can increase operator productivity by providing faster access than structured searches Full text searches may produce many "hits" that require further review and qualification Sunday. this activity deletes extracted static content that is older than NNN days. this activity takes a snapshot of the rule assembly cache.

In some cases. Work object history instances are stored as objects in classes derived from the History-Work.indexing/workenabled — Set to true or false to control whether searching is supported for Workinstances. A history instance may also contain attachments. The Dynamic System Settings are: • Pega-RULES. Indexing is controlled by settings in standard Dynamic System Settings data instances (Data-Admin-System-Settings class) and by a check box option on the Advanced tab of the Class form. Default is true. URI of the node on which searching occurs. Others are added automatically at runtime. search requests from other nodes are forwarded to this node. and user who updated a work object. which covers system and requestor performance of all types. Before building indexes on a new installation. the historical copy can be used to undo changes or roll back an object to its previous values and state. time.indexing/dataenabled — Set to true or false to control whether searching is supported for Datainstances. or other object in the system. which (in the initial PegaRULES database schema) are stored in the pr_perf_stats table. Instances of the Log-Usage class. The indexing facility places the index files it creates (with file type . The DataIndex and WorkIndex subdirectories contain CFS files for data instances and work objects respectively In some cases. or added as a result of values you select for the Audit Note field of flow shapes. Through standard SOAP connector rules. which cover only rules assembly rules — rules of those rule types that the system converts to Java code. History instances identify date. notes made by this user.indexing/ruleenabled — Set to true or false to control whether searching is supported for Ruleinstances.cfs) in subdirectories of this directory. Don't confuse Log-Usage data. this can reduce processing workloads and disk space requirements. Default is false. The name of the class is History-ZZZZZ. make sure no value is set for the errorMB setting. in the format: http://10. • Pega-RULES. hash node ID of the node on which the indexes reside. when editing the flow rule in Visio. or an internal copy of the entire instance as it was before the update. only rule indexing is enabled. support system-performance and usage reporting. • Pega-RULES. where ZZZZZ is the name of the work object class.60. indexing occurs on only one node. Sunday. with Log-RuleUsage data.AddHistory to a flow to add a history instance at any point in the flow. the PegaRULES database indexes are defined for the pr_perf_stats table.indexing/explicitindexdir — If not blank. Default is false. 2011 15 . identifies a directory on the server that can hold indexes.class.SearchSOAPURI — Needed in a multinode cluster. • Pega-RULES. If no explicit directory name is specified. The first character of the requestor ID identifies a requestor type: • • • • A — Services (APP requestor types) B — Background requestors (BATCH requestor type) H — Interactive browser users (BROWSER requestor type) P — Portlet users (PORTLET requestor type) To improve access.BPM and BRE • • Full text searches may disclose sensitive work object details to uses who otherwise would not be permitted to open or review such work Indexing (performed in the background by the Pega-ProCom agent) and searching (performed on request) can impact system performance. August 21.51. • Pega-RULES. • Pega-RULES.indexing/hostid — Needed in a multinode cluster.indexing/enabled — Set to false to disable all searching. The system creates rule indexes in a subdirectory named PegaRULEIndex. rule.) • Pega-RULES. (In a multinode cluster. a PEGA0004 alert threshold (alerts/database/interactionByteThreshold/errorMB) can cause the indexing process to fail before completing.214/prweb/PRSOAPServlet By default in new installations. You can add the utility activity Work-. Default is true. indexes are created in a subdirectories of the PegaRULES Web root directory (typically /prweb).

people such as customers or applicants or policy holders. Correspondence Rules (Rule-Obj-Corr)  Has more than one Fragment Rules (Rule-Corr-Fragment) Sunday.Default. completing an assignment L — A user completed and submitted a local flow action (other than a transfer). This property has one of the following values: • • • • • A — A user begins performing an assignment F — A user completed and submitted a (connector) flow action.class are created when a form (such as the Operator ID form) is saved or when a Data Table row is saved. These rules provide the content and logic that flow processing uses to generate customized correspondence for the recipient. Data-. Correspondence flow actions. 2) Work-Cover-. so the assignment remains open. Data-Party-Com represents for-profit companies and corporations such as vendors Data-Party-Gov represents government agencies Data-Party-Org represents not-for-profit organizations By default. Data-. August 21.classes that contain properties for holding contact information. Correspondence activities.class if it is also empty. and when you check in a rule ( ) into a RuleSet that requires check-out. Correspondence can be sent only to people who are identified as work parties. Correspondence rules. or Assign. The History-Work-. use correspondence flow actions. Background correspondence processing. o o o o o Data-Party-Operator represents Process Commander users who have operator IDs. M — A user added a memo to history. If the same piece of correspondence is to be sent to the same work party for every work object created by a flow. Correspondence rules are usually thought of as the top-level rule (or the container template) with fragments as the component parts of the template.BPM and BRE When you add a new concrete class under the Work-. R — A user completed the transfer of an assignment to a different worklist or workbasket Process Commander’s correspondence feature is supported by the following: • • • • • Work parties. When you delete an empty concrete Work-. contained in each history instance.class. A work party is a person or organization associated with a work object. In this case. When the (human) operator working on an assignment needs to specify information about what to send and who to send to.Default. The history instance for a checkedin rule contains the entire previous contents of the rule before update: Instances of concrete classes derived from the History-Data. the system automatically creates a similar class to contain history details of that class. Data-Party-Person represents individual people who are not Process Commander operators. identifies the event that corresponds to the instance. Process Commander’s flow processing and agent activities take care of correspondence generation and processing in the background. Five Data-Party. using the new class name as the trailing portion of the Historyclass name. 2011 16 . there are two standard work parties rules in Process Commander. These are visible from the History Details button display (on the History tab).pyHistoryType property. or Assign. Instances of the concrete History-Rule class are created when you create a rule (with Save or Save As after New) when you save a rule into a RuleSet not requiring check-out. there’s no reason to make operators do any work. 1) Work-. the system deletes the associated History.base class. use flow shapes and standard activities to configure correspondence to be added programmatically.

PegaRULES supports declarative rules. The flow actions SendCorrespondence and Notify prompt the user to select a work party and a correspondence rule. The PegaRULES component of PegaRULES Process Commander provides a powerful rules engine supporting business process management. you can configure the correspondence rule to prompt operators for input. The business rules engine can be embedded or called from another system using Service JSR94 rules. August 21.BPM and BRE Eg: Rule-Obj-Corr instance has <pega:include name=”Logo. selecting a correspondence rule. entering values for any fields the correspondence rule needs input for. Correspondence processing can use work object attachments as email attachments.Email” type=”Rule-Corr-Fragment”> <pega:include name=”Footer.CorrNew activity. Configure an email account object (Data-EmailAccount) that holds information about the email server and user account flow processing should use to send outbound email. 4. Type of the correspondence rule: • • • • Data-Corr-Email Data-Corr-Letter (type = Mail) Data-Corr-Fax Data-Corr-PhoneText To send automatic notification messages about assignments. Create the work parties rules that associate work party roles with your work classes.Email” type=”Rule-Corr-Fragment”> <pega:include name=”BodyofEmail. Java Specification Request 94 (JSR 94) describes an Application Programming Interface (API) for rules engines defined by the Java Community Process (JCP). use the notify shape with one of the standard notify activities (Work-. Developed in Java. To send any other kind of correspondence programmatically. The JSR 94 integration interface makes Process Commander processing available to external Java applications through JSR 94 invocations to JSR94 service rules. BuildCorr is a screen flow that walks the operator step-by-step through the process of specifying the work party role. highly scalable and reliable. and uses advanced software techniques to compute the consequences and results of rules. 3. SendCorrespondence starts a screen flow named BuildCorr. 2. and so on. and other applications through services.Email” type=”Rule-Corr-Fragment”> There are four standard correspondence types: • • • • Email Fax Mail PhoneText If a piece of correspondence will be selected by a human user (rather than generated in the background). Configure your flows to call the standard correspondence activities and flow actions at the appropriate places. use the utility shape with the Work-. for example). nonprogramming form. Create correspondence. If the work object has attachments. The following list summarizes the general steps for configuring correspondence generation in your flows. the operator can select which attachments to use as email attachments. correspondence fragment. 2011 .Notify. multithreaded execution and a large number of industry interfacing and standards. 1. and HTML stream rules. A business rules engine is a software component that allows business rules to be recorded in a non-procedural. the AddAttachments flow action enables users to upload a single file and select a category for it while AddMultipleAttachments enables user to select multiple files and choose a category for each. This service type enables the Process Commander 17 Sunday.

any Java program. Unlike the signature-based style. the system automatically checks an internal dependency network for other values that are affected and performs other processing as determined by the network. or through an instance of the PegaRULES engine. Service JSR94 rules support the engine API invocation style only. A client application sends the input to the service rule by calling a method in the proxy — a method with parameters that match the service rule. Decision rules perform a calculation or test that often is used to determine the next step in a flow execution or other calculations. When the value of a property is involved in any of these declarative rules. Process Commander provides three Java-based service interfaces (EJB. August 21. because you are not using a proxy compiled by Process Commander. no compile-time validation of method names and parameters does not occur. including property definitions. Declare OnChange or Declare Trigger rule. You can establish required relationships among properties in a Declare Expression. Changes in some property values — from any source — are automatically propagated forward or backward to change other property values. Java. The client application calls one Java method no matter which service rule is targeted in Process Commander. and JSR94) that you can use to request services using a signature-based or an engine API invocation-based • Signature-based means the external application invokes the Process Commander service rules through the proxy EJB or Java archive generated by the service package.BPM and BRE product to be embedded into. Service EJB rules and Service Java rules support both invocation styles. • Engine API invocation means the external application invokes the Process Commander service rules through a (generic) business delegate.class. and so on. The parameters provided in the invocation identify the service rule and provide the input for the service rule. This is known as forward chaining. Declarative processing simplifies your application and reduces the number of activities you need to create.5 contains six types of declarative rules: Constraints Declare OnChange Declare Expression Declare Page Declare Index Declare Trigger Validation is the processing needed to ensure that inputs (from a user. edit validate rules. constructs the URI for the service rule. the Property-Seek-Value method can access the computational relationships among properties in a Declare Expression rule to identify source values needed to compute a missing property value. 2011 18 . client-side JavaScript functions. A Service JSR94 rule is an instance of the Rule-Service-JSR94 class. from an external system. Constraints. in accord with the JSR 94 specification. The proxy manages type validation. This technique is known as backward chaining. directly through the PRService EJBs. and called directly from. and validate rules. In an activity. You can validate input by various means. or from a file) meet criteria defined by your application requirements. V5. A declarative rule is an instance in a class derived from the Rule-Declare. The proxy publishes the method signatures of the service rules. V5.4 contains six types of decision rules: case match hierarchy decision table map value decision tree when Declarative rules offer an attractive alternative to procedural calculations. The declarative processing facilities support operation of six rule types: Sunday.

BPM and BRE • • • • • • Constraints rules (Rule-Declare-Constraints rule type) Declare Expression rules (Rule-Declare-Expressions rule type) Declare Index rules (Rule-Declare-Index rule type) Declare OnChange rules (Rule-Declare-OnChange rule type) Declare Trigger rules (Rule-Declare-Trigger rule types) Declare Pages rules (Rule-Declare-Pages rules type) Declare Index rules support reporting and belong to the SysAdmin category. Sunday. updated. and other facts. numbers. A Declare OnChange rule causes computation to occur when the value of certain "watched" properties change. where the decision criteria fit a table or matrix structure. in this case). When conditions are the simplest decision rules. Pages that are not valid cannot be saved to the database. A when condition rule evaluates a relationship among one or more property values. A Declare OnChange rule starts an activity that can perform more complex or comprehensive computations than can be defined by expressions. Decision tree rules contain a list of one or more input properties. Create Declare Trigger rules to cause an activity to run when instances of a specific class are created. This implements a form of forward chaining. August 21. The Declarative Network display conveys relationships among properties that are computed by Declare Expression rules in the selected application. time. a decision tree rule to capture complex IF-THEN situations that involve multiple tests and criteria. the system monitors whether the constraint is met each time either value changes. has inputs and results. in the database. Declare Pages rules belong to the Technical category. 2011 19 . This may cause more frequent updating than a Declare Expression rule. such as: ActualExpense("December") is never greater than BudgetExpense("December"). and can return a property value as a result. the system adds a message on the page containing the left-hand property (ActualExpense(). recording the date. or dates) into a single resulting value. A Declare Trigger rule identifies processing to occur automatically when an instance of a specific class is saved or deleted. You can reference decision tree rules in flows through a decision task. marking the page as not valid. like a decision tree rule. If the constraint becomes false. and in any activity that executes the Property-Map-DecisionTree method. This is a straightforward way to present decisions and computations that depend on ranges of the input values. Use a map value rule to convert one or two input values (text. Forward chaining Forward chaining provides the automatic propagation of changes in one property value to cause recomputations of another property's value. As with expressions. or deleted Declare Trigger rule can implement a form of logging or audit history for a class. and returns true or false. A map value rule. A Constraints rule records an expected relationship between property values.

so other rules (such as activities) cannot be used to update or remove them Once the page has been populated. 2011 20 . and no new properties can be added to the page. At runtime. The created pages are treated as reserved. The page can easily be shared by multiple requestors. rather than when inputs change. Declarative pages enable developers to define a set of named clipboard pages for an application. A capability called locatable pages reduces the need for pages to be explicitly named in the rule. if property is missing Whenever used The Property-Seek-Value method is the foundation of backward-chained processing. Locatable pages can be used with Constraints rules and Declare Expression rules. Examples of the data types to be shared are: • • • • Cached global system settings Lookup lists Product information Any other application wide information that should ideally be shared A declarative page can be stored at the thread or node level. Sunday.BPM and BRE Backward chaining Backward chaining executes Declare Expression rules when a value is needed for a property. it is marked as read-only to maintain data integrity. They are created and refreshed on demand as they are needed by other rules. Backward chaining applies to Declare Expression rules with the Calculate Value field set to one of the following: • • • When used if no value present When used. August 21. It is for this reason that all of the properties on the page are not modifiable. the system uses backward chaining and an activity with type Locate to find and (if necessary) add the proper page to the clipboard. This eliminates the need for the developer creating the when condition rule to specify the page.

The alias rule provides an optional natural-language description and prompting that supports certain selection lists on decision rule forms. Delegation creates an instance of the System-User-MyRules class. when condition rules. These pages can be used by developers to store common data in one place that is shared by multiple users of an application. retrieval. Use an alias function rule to define prompting for a function rule for users who maintain decision rules. • • int). the page is accessible to a given requestor’s process. A delegated rule is a link to a rule or data instance that provides a quick shortcut.lang. Click the link to open the form. on the other hand. and constraints rules. Thread page examples might include: o o o o o Cache information about the current user Credentials Personal information (such as address information) Customized user preferences Information about the process or activity executed Node pages. You cannot define an alias for a Java. August 21.Alias function rules are useful for functions that managers or less technical developers may use frequently in decision tree rule. type Alias function rules are instances of the Rule-Alias-Function Obj-Browse — Executes an SQL SELECT statement. and sorting capabilities of a list view rule. without report display Sunday. Declare Expression rules. with the WHERE condition limited to exposed properties Obj-List-View — Executes the selection.String function rule that returns a complex Java type (that is. hence. 2011 21 . a type other than a or a primitive type such as class. are available to all requestors on a given node or application server. improving performance. In other words. Examples might include: o o o o o o o Lookup lists Code tables Organizational information Translation tables System settings External data that changes infrequently Any commonly used enterprise information All declare pages are cached and remain on the clipboard until further notice.BPM and BRE Thread level pages allow developers to define pages similar to those generated by the existing Locate Page facility.

RDB-List. Leave unselected if you plan to update the embedded pages. alter your application or database to eliminate those alerts that occur frequently. select this check box. 2011 22 . or PEGA0028. As a best practice.BPM and BRE Obj-Browse: ReadOnl Select to mark the embedded pages for the selected instances as read-only. Use the Obj-Filter method to refine search results by deleting pages based on when condition tests that involve non-exposed property values. The result of the method is a Code-Pega-List structure that contains all rows and all columns of the object. Sunday. and for best performance. Execution of this method may cause an alert to be added to the Alert log. the ReadOnly setting is ignored. It does not affect your ability to remove an embedded page completely (with the Obj-Filter or Page-Remove method). Obj-List-View: Use the Obj-List-View method to execute the retrieval and sorting operations. Obj-Filter: Use the Obj-Filter method to filter the embedded pages of a results page (such as a Code-Pega-List page produced by the Obj-List. of type PEGA004-PEGA007. meaning that later processing by the y requestor cannot update or delete data in the page. For example. Obj-List-View or Obj-Browse methods) based on one or more when condition rules. a PEGA0025 alert occurs. Marking the embedded pages as read-only with this check box prevents changes to the values of properties on the embedded pages. PEGA0027. including the Storage Stream (BLOB) column. but not the formatting and display processing. specify sorting only when needed. August 21. PEGA0025. The alert indicates that exposing one or more columns in the PegaRULES database table that holds instances of the class is likely to improve performance. If the Select array is empty. Obj-List-View processing can return a smaller set of columns and a more precisely selected set of rows than the similar Obj-List method. if execution of an Obj-Browse method accesses properties within the Storage Stream column. including aggregate properties. For best performance. and so can require less memory and less network traffic than an Obj-List method. Similarly. This records your intent that the embedded pages are not to be altered and can reduce memory requirements by retaining only specific property values extracted from the Storage Stream (Blob) column. The embedded pages are not read-only. use an Obj-Browse method to search and retrieve instances of a class where the selection criteria involve only Single Value properties exposed as columns in the PegaRULES database. Use care to retrieve only the rows (instances) and columns (properties) you truly need. Review the Alert log to understand the frequency and sources of such alerts. of a list view rule. This method can return thousands of database rows and create large clipboard pages.

PRPC Failed Start PegaRULES engine failed to initialize. See Understanding caching. See How to detect longLong Requestor running requestors.xml file. This causes the system to invalidate older entries in the cache. Database query operation has exceeded an elapsed time threshold setting. a personal cache. or a property Cache Force conclusion cache has reached or exceeded a limit specified in the prconfig. See How to monitor interactive response times. See How to DB Time detect lengthy PegaRULES database operations. See Understanding caching.xml file. The number of records in the rule assembly cache. August 21. Sunday. The number of records in the rule assembly cache. The master agent has detected a long-running requestor session. See How to monitor DB Bytes Read Storage Stream operations. PRThreads Limit Number of PRThreads has exceeded the threshold for a requestor. a personal cache.BPM and BRE ID PEGA0001 PEGA0002 PEGA0003 PEGA0004 PEGA0005 PEGA0008 PEGA0009 PEGA0010 PEGA0011 Category Browser Interaction Message text and description PEGA0016 PEGA0017 PEGA0018 PEGA0019 Browser interaction time has exceeded a threshold setting. or a property conclusion cache has reached or exceeded about 75% of the limit specified in the Cache Reduced prconfig. This Reduced causes the system to immediately invalidate older entries in the cache. Agent Disabled Agent processing disabled because of execution errors Services — One of five time thresholds was exceeded during a service execution See Service Total Time Testing Services and Connectors on the Integration page of the Pega Developer Network. See How to detect lengthy DB Commit Time PegaRULES database operations. See How to detect lengthy DB Rollback Time PegaRULES database operations. making room for additions. PRPC Started PegaRULES engine successfully started. Number of bytes received from the database has exceeded threshold. Database commit operation has exceeded a threshold setting. 2011 23 . Database rollback operation has exceeded a threshold setting. making room for newer ones.

Loading Declarative Loading declarative network has exceeded an elapsed time threshold. PEGA0021 PEGA0022 PEGA0023 PEGA0024 PEGA0025 PEGA0026 PEGA0027 PEGA0028 PEGA0029 PEGA0030 PEGA0031 PEGA0032 PEGA0033 PEGA0034 PEGA0035 Security alerts are recorded in the Security log.000 kilobytes (or another threshold setting). Rule change invalidated the specified threshold of entries in the Rule Assembly cache. An HTML stream sent to the browser exceeds 2. See Invalidated Rules How to detect when a rule change invalidates many entries in the Rules Assembly cache. Rule Cache The rules cache became disabled. within a Pega Composite Application. an HTTP request referenced an unexpected property. The attempt was ignored. The number of requestors on a system node exceeds 200 (or another threshold setting). an Obj-Browse method) accessed properties within the Columns Storage Stream (blob) column. that is. August 21. See How to detect database list operations that return DB Rows Returned many rows. The number of declare indexes in a single interaction exceeded threshold. See More about Declare Page rules. A generated HTML stream was overwritten without being sent to the browser client. typically by an administrator using the System Disabled Management Application. contained the pyStream parameter. within a Pega Composite Application. These can arise from an improperly coded URL JavaServer Page tag. See Stream Overwritten How to detect when a generated stream was overwritten but never sent. Security alert. Database query length has exceeded the specified threshold See How to detect when the DB Query Length database query length has exceeds a specified threshold. See How to PEGA0020 Connect Total Time detect lengthy connector executions and Testing Services and Connectors. Declarative Page The total of shared memory to store Node-scope declarative pages has exceeded a Memory threshold. See How to Declare Index detect when the number of declare indexes exceed a threshold. Sunday. Security alert. properties not exposed as individual columns. Reading Blob Need A list operation (for example. See How to detect Network large declarative networks. ID SECU0001 SECU0002 SEC0003 SEC0004 Category Security Security Security Security Message text and description Security alert. located on the Integration page of the Pega Developer Network. See How Clipboard List Size to detect when a Page List property has many elements. but did not free sufficient virtual memory.BPM and BRE A connector call to an external system has exceeded an elapsed time threshold. A garbage Collection collection operation completed. A Page List property contains more than a specified threshold number of elements. See How to Connection Time detect long database connection waits. Requestor Limit See How to detect when the number of requestors exceeds the threshold. an HTTP POST operation sent an XML document containing clipboard page details from a web node within a Pega Composite Application. A requestor on a web node. A URL received from a web node. Database The elapsed time taken to acquire a database connection exceeded a threshold. Security alert. attempted to execute an activity or list view rule that is not marked for web node execution. The rules cache became enabled. The URL was ignored. typically accomplished by an administrator using the Rule Cache Enabled System Management application. A list operation returned many rows. HTML Stream Size See How to detect large HTML streams. JVM Garbage Collection usage threshold exceeded for long-lived object memory pool. 2011 24 .

August 21. 2011 25 .BPM and BRE Sunday.

Sign up to vote on this title
UsefulNot useful