Pega is a Java-based BPM tool which is used to build enterprise applications. Among all the BPM tools in the market Pega is the leading and No-1 BPM tool according to market standards far beyond its competitors. Pega enables in creating and managing web-based applications with less effort and faster deadlines using Agile or Scrum methodology.

Pega Training Syllabus

BPM Overview, Project Implementation Methodology, Class Structures & Hierarchy

  • Introduction to BPM
  • Introduction to PRPC
  • Smart BPM
  • Build for change
  • Application Documents
  • DCO
  • Application express
  • PRPC frameworks
  • Class structure in PRPC
  • ECS
  • Inheritance
  • Class groups

Data Modeling

  • Define PRPC classes
  • Data branch
  • Property Types and Modes – Single and page properties

Process Flow – Flow & Flow Actions, SLA

  • Different flow shapes and their purpose
  • Usage
  • Creation
  • Flow Actions
  • SLA – Creation, Usage

User Interface

  • Properties display and validation
  • Layouts
  • Harness
  • Sections
  • Style Branding

Decision Rules

  • Creation of different decision rules, usage in flows and activities.

Declarative rules

  • Forward chaining
  • Backward chaining
  • RDE
  • Declare constraints
  • Declare triggers
  • OnChange

Case Management

  • Work flow
  • Units of work
  • Work status
  • Locking
  • Design correspondence
  • Send correspondence

PRPC Database Concepts

  • Role of PegaRules DB
  • Link between rules and DB
  • Basic tables
  • Exposing column properties

Activities

  • Definition
  • Configuration
  • Steps
  • Parameters
  • Security
  • Common methods

Integration with external systems

  • SOA
  • HTTP
  • SOAP
  • WSDL
  • Connectors & Services
  • Listeners
  • Connect SQL

Rule Management & Security

  • Rule
  • Ruleset
  • Ruleset version
  • Rule resolution algorithm
  • Operator ID
  • Access group
  • Access role
  • Privilege

Performance, PRPC Guardrails & Topics revision.

  • Clipboard
  • Alerts
  • Pre-flight
  • PAL
  • DB trace
  • Tracer
  • SMA
  • 10 guardrails
  • Iterative approach
  • Class structure
  • Build for change
  • Design intent driven process
  • Security and object