Change PRConfig.xml file settings

Each node of a Process Commander cluster has a file named prconfig.xml that holds the configuration settings for an installation. The file is loaded on start-up.

Many of the default installation settings can be modified by accessing the prconfig.xml file as described below:

Stop the Process Commander application.
Un-deploy the Process Commander application.
Extract the prconfig.xml file from one of the following locations:
If Process Commander is deployed as a Web application, locate and unzip the prweb.war file to a location that you have access to. Then extract the prconfig.xml file from the WEB_INFclasses directory.
If Process Commander is deployed as an enterprise application, locate and unzip the prresources.jar located in the APP-INFlib directory. Then extract the prconfig.xml file from the .jar file.
Open the prconfig.xml file in a text editor.
Add the entries you need.
Save the file and repackage the modified prconfig.xml file into the prweb.war or prresources.jar file, as appropriate.
Redeploy Process Commander.

Pega Interview Questions

Question about the agents.
How to trace an Agent?
What is IAC, when did you use in the project.
What is cover and covered objects.
Have you used spin-off shapes in your application, if so what is the case.
What are the type of log files we have
Ans: AlertSecurity, Services-PAL, Log Files and Alert Files
Do you know the concept of validation rules?
How do you a log a message in PRPC?
Tell me about the locking concept in PRPC.
 What is DWA (Direct Web Access) 
What are PEGA Guardrails 
What is the diff b/n Decision Table and decision tree 
What is Declare expression 
How do u connect to the Web service
What is xml file name created during connection of web-service 
What is order of execution in Decision Table and decision tree
About the availability of rules
Rule resolution algorithm 
Explain about DCO 
Regarding a scenario (If an organization has 60 branches and a rule has to be used in all the based on the branch name… the question was not asked clearly) Ans: Multivariate Circumstance property.
What are the issues faced in Upgrading from 5.3 to 5.5 or similar version upgrade questions
How do you purge the work objects? 
Will you try to remove the assignments shape of a flow in the production system
What is the role of the master agent 
Do you have any idea about the AES? 
Suppose I need to access the Google service, how can I achieve this in pega
What are the rules which are not rule resolved? 
What is the actual usage of the blocked, with drawn, NO. When you use it?
What is the usage of Property-Alias rule 
What are the various ways to restrict user to edit the rules. 
How do you display an image dynamically in a list view rules based different types of urgency.
Process cycle of IAC 
What is the major difference between the Cover and Folder
How do you build a new Rule-Form
 In how many ways you can create a new PRPC application.
What is a screenflow.Difference between screen flow and processflow?
How do you povide SLA for the workobject? A : Model
In Connect Sql rule stored procedures are written in which tab?
Save,Browse,Delete etc tabs present in Sql rule.Which tab will be called when?
What is the difference between workobject and worktype?
What is the difference between Decision tree and Decision Table?
If you have work experience on Soap Service.What are the rules required for Soap Service?
In which tab WSDL file will be generated in the Service Package?
About the debuggine tools like Clpboard,Tracer etc.
Some times performance tool.
About dynamic select.
declarative rules like declare constraint,onchane,trigger etc.
How do you expose a property?
What is the need of exposing a property? 
how to IAC to connect to web application in Pega
How to use existing css in Pega
what is difference between decision table & descision tree
what are guardrails in Pega
SOAP integration using PEGA ——— Techincal/Functional

Harness,HTML,Section rules———– Technical



Pega Guadrials

SMART BUILD methodology

Debugging tools(tracer, PAL etc)———————– In depth

Exception Handling——————–Various ways

Declarative rules———–Expressions, triggers, onchange etc

Reports creation————–List Views/Summary Views/Charts/Graphs

Rule Resolution————-Advantages/Disadvantages

CACHE mechanism

Performance Evaluation———-Using PAL, SMA(System Mgmt App)

prconfig,prlogging xmls ———–Idea on configuration

Pega application deployment on various servers like DEV/QA/PROD

Differences between V5.x and V4.2

Migration of Rules

Test cases generation using V5.4

Unit testing from developer perspective

Various type of flows, flow shapes, flow actions


Accessgroups,portal,operators profile,workbaskets,worklists,workmanager,classgroup

Work-, Embed- and Data- classes

Roles, Privileges——-Creation and Manage

Decision Trees/Decision Maps/Decision Tables———-Creation and differences among them

Column exposing and the advantage of it

Pega DB schema——–pc_work,pr_other,pc_link etc

Application Accelrator, Rules Inspector

1)asked about file and email listener


3)aggregate property and it’s related to which class type

4)about reporting

Thanks for starting this forum. Thanks again…
I have some Questions Known….
1. About Sub Flow
2. Decision Table, Decision Tree
3. Declarative Expression
4… Would add the list later

Reports(list and summary view)

PEGA Configuration.



how to connect external DB.

About the product and Product Patch?

Diff. b/w Major, Minor and patch.

About obj-open,obj-save, obj-list, rdb-open,rdb-save?

Diff b/w flowaction and harness.

Whats are stepmethods you used while developing Activity 

Pega PRPC topic to learn

Introduction to PRPC                                                                        
Ø  Using Process Commander and PRPC Developer Portal Basics
Ø  Architecture
Ø  Common Rule Types
Ø  Examining Rules Using PRPC (Class, Class Group, Rule Sets etc)
Ø  Understanding work and data class structures
Ø  Understanding Properties
Ø  Process Flows (Flow types, Shapes )
Ø  User Interface overview (Harness, Section etc )
Ø  Rule Set and Security Overview
Ø  Using the Clipboard and tracer
Ø  Implementing PRPC
Ø  Building Class Structure
Ø  Creating Property and Model Rules
Ø  Creating Flow Rules
Ø  Building the User Interface
Ø  Enhancing the User Interface
Ø  An overview of Declarative rules
Ø  Validation
Ø  Using decision rules
Ø  Using Activities
Ø  Assigning work
Ø  Integrating PRPC Applications
Ø  Connecting to an External Relational Database
Ø  Documenting and Saving your Work
 PEGA Hands On
Ø  Class Structure And Rule set Design
Ø  Environmental Setup
Ø  Application Profile, Application Accelerators
Ø  Building Primary Business Flows
Ø  Designing the Data Classes and Data Class Models
Ø  Building Secondary Business Flows and Exception Flows
Ø  Implementing Decisions, Validations etc…
Ø  Execution of flows and Unit testing and PAL Reports
Ø  Documenting and Packaging the rules.

What is PDCA ( The Deming Cycle)?

W. Edwards Deming in the 1950’s proposed that business processes should be analyzed and measured to identify sources of variations that cause products to deviate from customer requirements. He recommended that business processes be placed in a continuous feedback loop so that managers can identify and change the parts of the process that need improvements. As a teacher, Deming created a (rather oversimplified) diagram to illustrate this continuous process, commonly known as the PDCA cycle for Plan, Do, Check, Act*:
  • PLAN: Design or revise business process components to improve results
  • DO: Implement the plan and measure its performance
  • CHECK: Assess the measurements and report the results to decision makers
  • ACT: Decide on changes needed to improve the process

Pega BPM – An Intro

With Pega BPM, business can define, manage and change their processes exactly when they need to improve operations and add value to customer interactions.

Pega helps businesses build flexible and scalable  solutions that achieve predictable outcomes remarkably fast – often in sixty to ninety days.

Applications build with Pega BPM are easily defined and changed, because Pega directly capture business objectives.

The business results achieved with Pega BPM are compelling:

  – 30% increase in business
  – 40% improvement in productivity
  – Five times faster development

What is BPM?

BPM = Business Process Management

BPM is the organizational activity that incorporates: Planning, Designing, Building, Operating, Maintaining, and improving business processes and their enabling capabilities forever and for everyone.

Businesses would have a number of processes which need to be repeated over and over again. Some examples would include adding a new customer, modifying details of a customer, paying salary to employees, granting leave to employees, introducing products, etc. These processes also use variety of methods to input data such as web-pages, installed applications, call centers and back offices.

Many organizations, especially the large ones, use various software in each of the sub-divisions to automate and computerize these processes. BPM tools help in maintaining all business rules in one place. BPM tools also help in reducing the coding effort as they are business friendly.

Scrum – An introduction

One of the most successful agile methods because of its hyper productivity
It is management oriented
Somewhat CMM Level 3 equivalence
Widely Used. Examples:

  • Google Adwords
  • 3M
Scrum Roles
  • Scrum Master (Conducts daily scrum meeting, assure scrum rules are followed, removes obstacles, shields teams, facilitator not a manager)
  • Product Owner(Accountable for product success, defines product features, maintains product backlog)
  • Development team
  • Other parties involved
  • Time Box – 2 to 4 weeks
  • An iteration for a building a piece of increment
  • It’s the working time, not planning or asking what to do
  • the team manages itself during a sprint
  • the team commits to product backlog during sprint planning meeting
  • The Sprint backlog is updated a sprint

Scrum – Agile Methodology – An introduction

  • Agile says “No Documentation”. So, no documents will be created henceforth
  • Each department will transition to Agile methodology in its own pace. Example Testing teams would take a different time to move to agile compared to the development or the project management teams.
  • Start the transition from bottom up. 
  • Ignore story priorities
  • All stories must complete on last 1-2 days of sprint
  • Team should pick up more stories than it can test
  • Make sure Definition of Done (DoD) is never looked into during sprint review and is invisible on team pages too
  • Make sure tasks published on scrum task board do not have test plan review, test execution and bug fixing
  • Code changes should continue till last date of sprint
  • Make sure minimum time exists for bug fixing at the end of sprint
  • Make sure some bugs are carried over to next sprint and to bug backlog
  • Make sure bugs are not tagged to stories/feature
  • Make sure no regression testing is possible in the sprint
  • Focus only on the tasks assigned to you
  • Estimates should include only development complexity/size

BPM Major competitors

IBM: Wepshere Business Process IntegrationSuite
IBM: FileNET P8 Business Process Manager
Documentum: Business Process Manager
TIBCO: iProcess Suite (From Staffware)
BEA: BEA Aqualogic and Fuego BPM
Intalio: Business Process Management System
Pegasystems: Smart BPMSuite
Phaon: Beacon
Ultimus: Ultimus BPM Suite
Captaris: Captaris Workflow
Metastorm: e-Work
Lombardi Software: Teamworks
Savvion: Business Manager, Process Modeler
Appian: Appian Enterprise