Understanding UI HTML, Variable,
DB store
Understand Basic Rules in Pega
FYI : Ignore, Reading RED COLOR statements, for now.
The below are some basic rules in Pega
Property, Section, Flow Action, Flow.
1. Property :- Property is just like a variable in other programming languages, it holds
values, it’s associated with name, Property Type (text, decimal, date etc), Control…
Property is an instance of a concrete Class ‘Rule-Obj-Property’.
Property
Property can be created under “Data Model” Category.
To Create a Property follow below navigation
A Property will have below attributes.
1. Name : Name of the Property
2. Property Type : The Type of Data that a property can hold be identified by this attribute.
3. UI Control :- This identifies, how this property should be visible when it is added into
design Phase of UI (Section)
4. Table Type : Optional, to define the label values of Radio buttons, Dropdown etc…
2. Section
Section is a UI Rule, used to design Screens.
Section is an instance of class Rule-HTML-Section
Section can be created under User Interface Category..
A Section is going to hold different controls into it’s layout.
Layout is like a Table element in HTML which can be used to Align the Controls.
A Section can hold Controls into it’s layout and associate them with Properties.
-------------------
3. Flow Action : It’s a container of Section which adds an action to the UI such as Submit, save,
cancel etc..
Flow Action is an instance of Class Rule-Obj-FlowAction
Flow action can be created under Process Category.
Flow action is like a container of Section.
The section we have created should be added into flow action.
A Flow Action allows a user to perform an action like Submit, save, cancel etc…
A Flow Action Can be integrated into flow by using assignment shape’s outward connector.
4. Flow or Work Flow : Flow defines transaction Life Cycle.
This is an instance of class Rule-Obj-Flow
A Work Flow is heart of PRPC transaction processing.
Any Transaction processing has to be designed using a work flow.
The below are basic flow shapes.
1. Start : A Transaction gets initiated at this flow shape.
2. Assignment : The primary purpose of this flow shape is, used to call flow action into
flow.
3. End Shape : A Transactions gets resolved at this flow shape.
A Flow must have one and only one start shape and it can have at least one end shape.
To create UI and make it part of Work Flow, follow below steps.
1. Identify and create all the required properties.
2. Create UI, by section rule, drag and drop properties into Layout of section.
3. Create Flow action, Include section into Flow action
4. Create Flow, use assignment shape, and call the flow action into flow using assignment
shape’s outward connector.
5. To make the flow executable, choose the option, “Creates a new work object” and then run
the flow.
Thank you
