Documente Academic
Documente Profesional
Documente Cultură
A) Split join is sub flow of ur flow is completed before continuing the current flow completed.
Split for each is to send a work object through another flow based on the information in the pages of page list and page
group.
Rule-Declare-Trigger?
A) It identifies an activity to run when an instance of specific class is saved, updated or deleted in the database.
this implements a form of forward chaining.
EX: A Declare Trigger rule can execute an activity each time an instance of class is saved with modified ZIP code.The activity
might send a email to
Sales representative whose area includes new address.DT can implement a form of class history like date, time and other
facts.
Can we start a flow using activity and what is that method which is to be used?
A) Yes, Flow-New method is used to start a new flow.
Can we use Rdb-Save along with commit, if yes then why? if not yes then why?
A) Yes, commit is used to save the data permanent in the DB.
What is Access Group and Access roles and difference between them?
A) Access groups make a set of RuleSet versions available to requestors.
Use an access role name to convey permissions (capabilities) to a user or a group of users. Access roles can be referenced
in requestor instances, Operator ID instances, in access group instances, in activities, and in queries.
How many requestor types are there and what are they?
A) Application, Batch, Browser, Portal.
Backward Chaining: It provides the automatic calculations of a property value by executing the declarative rule, when a
value is needed for property rather than whenever inputs change.
EX: If the Area property depends on the Length and Width property, then backward chaining causes the Area property
recomputed each time the Area property is required.
Virtusa
Declarative rules?
A) Rule-Declare-Expressions, Rule-Declare-Index, Rule-Declare-Trigger, Rule-Declare-OnChange
Rule-Declare-Constraints
Declare on change?
A) it is the instance of Rule-Declare-OnChange rule types. it is used to run an activity automatically at activity step limits
whenever the specify property value is changed. this capability provides automatic forward chaining.
EX: we can create a declare onchange rule to send an email to emp whenever HRA,TA,PF is changed. we can define RDO
rules property inside the embedded page. we need to specify page name and class name in the pages and classes tab.
Declare pages?
A) it is the instance of Rule-Declare-Pages rule type. it is used to define the content of clipboard page that is available in read
only mode for multiple requestors in ur application. the name of the declare page starts with Declare_.
What is circumstance?
A) Circumstance is the optional condition and enhancement of rule resolution alg. diff variations of the rules within the
same version created for diff flavors suit for different situation. circumstance works during the rule resolution, at run time
system first find the rules based on class hierarchy then searches for a rules the requestors session needs, it compares the
values of rule set, version, availability to determine which rule executed.
call, branch?
A) call Activity: the call activity instructs the current activity to find and run another activity using rule resolution.After the
called activity completes the calling activity processing.the called activity can use its parameter page. the main advantage of
call activity is reuse.
Branch Activity: it is similar to call method. Branch activity refers to the another activity. the execution of the original
activity ends the execution of the branched activity completed without return..
Mphasis
What is Access Group?
A) Access Group controls the security basing on the job functions. It is instance of Data-Admin-Operator-AccessGroup.
Various aspects that can be controlled through access group are default and available types of works( also called as work
pools ) , Primary rulesets ( Access Control to rulesets), Assigned roles, Portal layout
what is Agent?
A) Agents are internal background process operating on the server to run an activities. Agents are asynchronous and
independent. They also perform system tasks such as sending email notifications and synchronizing caches across nodes.
Activities they call run individually on their own scheduled and one activity doesn't have to finish another activity
How to integrate with SOAP (or) how to create a connect SOAP?
A) service pkg, service soap, activity.
what is exact difference between step page and page new(both will create the pages)?
A) Step page defines the page context on which a method is going to be executed. step page does not creates a page..while
page-new is used to create page
What is flow-action?
A) it is the instance of Rule-Obj-Flow Action rule type. it is the one category in UI specifies the choices to user performing
assigned work object.
Local FA: if action is finished, work object returns to same level.
Connector FA: if action is finished, work object moves to next level.
Have you used spin-off shapes in your application, if so what is the case?
A) The work object processing in the current flow in parallel without waiting in the other flow to continue.
If you have work experience on Soap Service. What are the rules required for Soap Service?
A) Service Package, Service SOAP, Activity
SmartBPM methodology takes an iterative development approach that is structured around four phases and two
supplemental activities. It is not a concrete prescriptive process. It is designed to be flexible so your
implementation team can adapt it to any size project.
Project Initiation Activity Kicks off project development. The goal of this activity is to prepare, organize,
and set the proper expectations for the project initiative to follow. Performed at the beginning of the project, its
goal is knowledge transfer and education. This is to provide business participants with terminology that assists
them with requirements gathering, objective determination and scope definition.
Inception Phase Defines the scope, captures business requirements and organizes them into projects that
result in an approved proposal. The current process is evaluated to identify possible improvements. Projects are
broken down into manageable development units called slivers. Requirements, use cases, and work types are
captured and entered into the Application Profiler. The development effort is estimated.
Elaboration Phase Builds out the foundation of the proposed implementation using the Application Profile in
the Application Accelerator. Requirements, use cases, and work types are expanded to include further details.
Process discovery is performed to identify the initial flow of work and user interface design. Application standards
are established. Testing and migration plans are drafted.
Construction Phase Builds the implementation on the foundation created in the Elaboration phase.
Configuration tasks are assigned using an iterative implementation model. Components are unit tested as they
are completed and test scripts are developed.
Transition Phase Moves the implementation to the end user and testing teams. The focus is on end to end
testing and user acceptance to ensure the quality of the application and its readiness for migration and
deployment to production.
Go-Live Activity Occurs when a completed sliver is launched into a production environment and business
users begin to use the live application.
The lifecycle of a Pega Scrum project is designed around the five stages shown below.
Vision Definition Develops an understanding of the big picture for team members, a project roadmap and
high level product backlog.
Project Initiation Determines the scope of the initial project, kicks it off and sets expectations.
Enterprise Planning Designs the infrastructure needed to support today's capabilities and future needs as
well as the enterprise level class structure that supports maximum re-use as implementations are deployed.
Release Implementation Builds the application in sprints using the Scrum approach to software
development.
Release Retrospective Evaluates, adjusts, and improves the process to promote continuous process
improvement.
Important Terminology
Application Accelerator An automated Process Commander tool that uses input from an application profile
to create the foundation rules for a new implementation.
Application Profiler An automated Process Commander tools that creates a high-level scoping document
produced that can be used as a project proposal and an application profile that can be consumed by the
Appliation Accelerator to create rules. It details work types, requirements, use cases, actors, interfaces and
reports/correspondence for an implementation.
Atomic Use Case A subset of a business use case that describes a portion of the process that is performed
by a single actor in the process. Corresponds to actions performed by that actor.
Business Objectives Project goals that, when reached, signify a return on business benefit.
Business Use Case Describes the full lifecycle of a process for a single work type. It is broken down into
atomic use cases.
Requirement Details a business need; used to verify that the resulting implementation is what the business
needed.
Work Type A business problem that requires an automated solution that is associated with one business use
case and one or more atomic use cases. For example: A claim, loan, or service request.
Understanding the Class structure and RuleSets generated by the Application Accelerator
The Application Accelerator generates an initial layered enterprise class structure and multiple RuleSets, based
upon the input values you provide (and default values)
Layer Purpose
Enterprise Reuse For assets that need to be reused on an enterprise-widebasis. Such assets are rules
for enterprise-wide business logic (such as standard properties, decision tables, Service
Level rules) and enterprise-wide data assets (such as classes and rules for data stored
in the system, and classes and rules for access to data in external systems, via
connectors).
For example, the MyCo enterprise wants to reuse the property that holds an employee's
serial number on an enterprise-wide basis, so that the various applications used by that
employee across the enterprise can consistently rely on the same serial number
Divisional Reuse For assets that need to be reused on a division-widebasis. Such assets are rules for
division-wide business logic (such as standard properties, decision tables, Service Level
rules) and division-wide data assets (such as classes and rules for data stored in the
system, and classes and rules for access to data in external systems, via connectors).
For example, a division wants to reuse a service level rule that defines the expected
For example, the MyCo enterprise makes auto loans, and has an auto loan framework
that is comprised of all of the assets needed for MyCo's standard auto loan process.
Each division of MyCo extends that basic auto loan application to meet their specific
divisional needs: the commercial business line division's auto loan application needs to
handle loan requests distinct from that of MyCo's personal line division.
For example, the commercial business line's auto loan application reuses assets from
the commercial business line division layer and from the auto loan framework layer,
while the personal line's auto loan application reuses assets from the personal line
PRPC Base Consists of the PRPC system's built-in classes and rules necessary for processing
Product cases and other work in PRPC applications, as well as for areas of PRPC itself.
A system architect starts the Application Accelerator, and in the Application Overview window, chooses the
application profile the team created. To generate the application structure that supports both the framework and
the equipment setup sliver, the system architect specifies a framework named OnboardingFW and an
implementation named Equipment in the Application Overview window.
On the Base and RuleSets step of the Application Accelerator, the system architect replaces the displayed
default organization and division values with the official ones: GLBX.com and HR, and keeps the default class
structure of Standard. The displayed values refresh to reflect the input values:
Clicking Preview displays the enterprise class structure that will be generated by the Application Accelerator given
those input values:
Why do non-work classes, like Org-, inherit from Work- (in 6.1+) or Work-Cover- (in 6.2+)
Because of rule resolution, inheriting from Work- or Work-Cover- on those levels allows for increased
sharing of case-management-related or work-related assets across multiple applications. For example, if a
company creates two top-level classes for some reason (such as when two organizations do not currently
work with each other and they want to develop applications independently), the applications can still share
work-related assets.
Why does the Org RuleSet have the OrgInt RuleSet as a prerequisite (required) RuleSet?
So that business logic rules in the Org RuleSet have the ability to reference integration-related rules and
classes stored in the OrgInt RuleSet.
Direct Capture of Objectives (DCO) is the set of tools designed to capture and tie business objectives, project
goals, requirements, and use cases to actual implementations.
A. Application Profiler
An Application Profile is an auto-generated Microsoft Word document designed to help you in the information-
gathering phase of a project's life cycle.
The document is created by the Application Profiler -- an automated tool that guides you through a series of input
steps to collect organization, use case, requirements, and other application information to produce a
comprehensive and professional looking work-based proposal and sizing estimate for your projects.
The profiler supports an iterative approach to information gathering that allows you to create, update, and
save profiles, and to generate in-process documents as you collect project data during the inception process.
From the File menu on the developer portal, select one of these options:
o New > Application Profile to create a new application profile
B. Application Accelerator
The Application Accelerator is a Direct Capture tool that speeds the creation of new applications, frameworks, or
the extension of an existing application or framework.
It guides you though a series of steps to gather and review the information that is used to create the class
structure and rules for your application. It supports an iterative development approach that allows you to enter,
update, and save data until you are ready to create the application.
The accelerator can be launched from a completed application profile or a menu on the developer portal.
The wizard is structured to guide you through a series of input steps that prompt you for information about the
following elements of your application:
Requirements
Actors
Work Types
Use Cases
From the Application menu, select Direct Capture of Objectives > Enable this Application
From the File menu, select Open > All Wizards to open an existing enablement instance from a list of open and
resolved records.
For example:
System needs to have 2-3 seconds screen to screen interaction is a non-functional requirement tied to
the overall application
First Name should not be longer than 20 characters is an a business rule requirement tied a specific use
case
Structured parsing
Control methods and instructions
Apply-Parse-Delimited
Activity-Clear-Status Apply-Parse-Structured
Activity-Set-Status Apply-Parse-XML
Activity-End Map-Structured
Activity-List-Add Parse-Byte-Pos
Branching to another activity Parse-Char-Pos
Calling another activity Parse-Fixed-Binary
Collect Parse-Packed-Decimal
Exit-Activity Text-Infer
Requestor-Stop Text-Normalize
Thread-Clear
Wait
Process
Similar Java, XML, or
Commander Rule type
database concepts
term
activities Rule-Obj-Activity public Java instance methods with a void return type
The shape in a Visio flow diagram, references an activity that updates a work object, but does not
require user interaction and input. Your system includes standard activities for utility tasks, and you
can create additional ones.
Each utility task references an activity with an Activity Type of Utility ss from utility shape we can
call activity but vise versa not possible.
Obj-Open : we will get multiple records from table based on the criteria from the specified class.
Or Opens an instance of a given class
OBJ-open-handle: here we have have to pass the pzInskey as a instance handle, this mehod will
open only one record at time. Or Open object by handle to the pzInsKey value
The handle of an instance is a unique key, in an internal format, assembled by the system that
identifies an instance in the PegaRULES database. It may differ from the visible key generally used
to identify instances. (Every instance has a unique handle, but more than one instance may share the
same visible key.) For rule instances, the handle includes system-generated identifying values
(including the create date and time) that make it unique.
Use the Obj-Open-By-Handle method only if you can determine the unique handle that permanently
identifies which instance to open. Otherwise, use the Obj-Open method.
Rules: inheritance that can maximize reuse of your rules while allowing localized overriding as
appropriate. Also called polymorphism, inheritance allows a rule created for one class (possibly an
abstract class) to be applied to other classes that inherit from it.
Class inheritance searches for rules from a concrete, lower class, up the class hierarchy to find
available rules.
1. DBTrace: DBTrace is a feature in the Performance Analysis Tool (PAL) that creates a detailed log of
calls to the PegaRULES database. DBTrace displays SQL statements sent to the database and the
time spent for each operation.
PAL: This data is stored in PAL counters or PAL readings. PAL stands for Performance AnaLyzer,
and is a collection of counters and timer readings, stored in the requestor, that an application
developer could use to analyze performance issues in a system.
PAL Features
Add Reading
Add Reading with Clipboard Size
Reset Data
Save Data
Start DBTrace
DBTrace Options
Start Profiler
Show Graph
My Alerts
Alerts:
During application processing, Process Commander writes to the performance alert log a sequence
of text entries called alert messages that identify mainly performance-related issues or errors. The
performance alert log is usually named PegaRULES-ALERT-YYYY-MMM-DD log.
AES:
Exceptions are processed in a similar way as alerts. When a Process Commander server generates
exceptions they are sent by SOAP to the AES system. The system parses the exceptions and stores
the records in the pegaam_exception table in the AES database. Based upon how often an exception
occurs and the system events that triggered those exceptions, AES aggregates these records into
work objects called AES exception items. These items are written to the AES database in the
pegaam_exception_work table.
Creating the separate DB table for that work class with in the DB, or map to external db and further
saves will go to that DB
Obj-list : Retrieve to a page, read-only, a selected set of properties Import ant fields Obj-List:
RequestType: The Type of the browse; allows different processing or sets of properties to be
defined. Defaults to Standard. Key-part to the Rule-RDB-SQL instance.
Access: An indication of the database package used to access this table, from the INI file (currently
ODBC). Key-part to the Rule-RDB-SQL instance.
ObjClass: The object Class to List. When used with RuleObjList parameter, this is the class of the
list to use.
Using log-message.
Preflight:
Starts the Application Preflight tool, which reports warning conditions on the rules in your
Application RuleSets. These may indicate guardrail compliance issues, potential performance issues,
accessibility status, or other notable conditions.
- Application Preflight tool to list each rule in an application that contains a warning message.
Warning messages suggest that the rule is at variance with guardrails and other best practices. You
can also check for browser compatibility of visual elements.
you can extend the set of warnings with a custom activity named Rule-
ZZZZ.CheckForCustomWarnings, where Rule-ZZZZ is a rule type.
Warnings are maintained as instances of the Index-Warning class and saved in the pr_index_warnings
database table.