Lesson 01: Introduction to Pega
Pega Systems Inc. is a Cambridge, Massachusetts based Software Company and PEGA is one of the Leading IT Software Technologies with a Focus of delivering quality IT training to individuals.It is used in developing software for Customer Relationship Management (CRM) and Business Process Management (BPM).
Lesson 02: What is Pega PRPC?
Pega is the software for customer centrality. Most of the world’s leading corporations use Pega to drive profits growth, enhance customer expertise and improve operational performance. PRPC (Pega Rules Process Commander) is a software product designed, licensed and marketed by Pegasystems Inc (PEGA). PRPC is a core segment of Pegasystems's "SmartBPM" suit of BPM (Business Process Management) explanations. Pega Rules Process Commander comes essentially as two strategic entities, • Pega Rules: Core Java-based/Object-Oriented Rules Engine. • Process Commander: Layers of pre-configured rules that implement a stable foundation on which to perform community and customization.
Lesson 03: BPM Data Tables?
A data table is a simple structure consisting of the rows of a Pega 7 Platform concrete class that includes only scalar (Single Value) properties. Informally, a data table is the Pega 7 Platform's internal representation of a "flat file" that contains no repeating groups.
Lesson 04: How we can create a pega sample application?
So you have the Pega 7 platform up and working. Now what? It´s time for one of the fundamental tasks often achieved by a Lead System Architect (LSA) which is setting up a new application structure. This structure includes more than just an application name. It also describes certain business and technical perspectives. To catch these aspects Pega comes with a wizard called App Express. This wizard will effectively create rules to define the Organizational and Class Hierarchies. The Document Application tool captures information and images from any application in your stack and generates the customizable application, application outline and specification documents that you can share with stakeholders. This tool was previously called the Application Document wizard.
Lesson 05: How can we create an Agent?
An agent schedule instance (Data-Agent-Queue class) determines whether an agent runs and for a multinode system on which server nodes it runs. Agent schedules cannot be created manually. The Agent Manager master agent generates agent schedule instances from agents rules (Rule-Agent-Queue rule type). The Agent Manager on your Pega 7 Platform system generates at least one agent schedule instance for each agent rule. In a multinode system, for each agents rule, the Agent Manager generates one agent schedule instance for each node. For example, if a clustered Pega 7 Platform system has five nodes, then there are five Pega-ProCom agent schedule instances generated from the Pega-ProCom agents rule.
Lesson 06: How we can create a Pega Report?
Both managers and developers can create and manage reports by using the portal that is best suited for their roles. For more information about how to create reports, see the following Help topics: Creating reports in Designer Studio, Creating reports in Pega Express, Creating reports in Case Manager.
Lesson 07: How can we create a pega Integrator?
An Integrator shape identifies an activity that connects your Pega 7 Platform system to an outer system to send or receive data. An integrator shape can connect to a customer master database to retrieve account balances or verify account numbers and status. Integrator shapes use activities (with Connect as the Activity Type) that call connector rules (Rule-Connect- rule types).