Scribd
Upload
326 views2 pages

Understanding Business Process Flows

Flows are a diagrammatic representation of business objectives that define the lifecycle of a business process. A flow consists of a sequence of graphical shapes and connectors that model the different paths a case can take through completion. Shapes represent tasks that users complete, and connectors define the order and flow. There are two main types of flows - process flows, which can contain work objects and multiple assignment tasks, and screen flows, which present a single transaction across multiple pages and do not contain work objects. Work object data and rule definitions are stored in different database tables mapped to their class structures.

Uploaded by

YEMINENI HARISH BABU
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
326 views2 pages

Understanding Business Process Flows

Flows are a diagrammatic representation of business objectives that define the lifecycle of a business process. A flow consists of a sequence of graphical shapes and connectors that model the different paths a case can take through completion. Shapes represent tasks that users complete, and connectors define the order and flow. There are two main types of flows - process flows, which can contain work objects and multiple assignment tasks, and screen flows, which present a single transaction across multiple pages and do not contain work objects. Work object data and rule definitions are stored in different database tables mapped to their class structures.

Uploaded by

YEMINENI HARISH BABU
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as TXT, PDF, TXT or read online on Scribd
  • Flow Overview: Introduces the concept of Flows, a diagrammatic representation of business objectives, including properties and types.
  • Types of Flows: Details the different types of flows including properties and screen flow types, explaining various applications within business systems.

Flows

..................................................................

Properties ....> Sections....> FA....> Flow

What is Flow ? Flow is a Digramatic reprasentation of business objective.

Process category...

New , Open , Inprogress , Resolved - completed

GenerateID .... OOTB

pyID , pzInsKey , pzpvStream (Blob Column)

About Flow Rule/Process Flow/Work Flow/Case/Transaction

Flow is a Process Rule


Flow is an instance of Rule-Obj-Flow
Purpose: To Define Life Cycle of the Business
A flow is a sequence of events that models a business process in your application.
You create flows to support the different paths that users
can take as they move a case through its life cycle.
You can define paths in a flow by using graphical shapes and connectors. The shapes
and settings that you choose depend on who performs
each task, the types of decisions that users make, and order in which the events
occur.
Flow shapes
A shape in a flow represents a task that a user or application completes as part of
a business process. By connecting different types of
shapes in a flow, you can define the path that a case follows from creation to
resolution.

Where WO Data Gets Stored in the rulebase?

It is Stored under Work Table(pc_acko_ackoauto_work), Inside Work Table under a


Column pzpvstreamin Binary/BLOB Format
Whatever the WO Data we submitted it will convert into diff format in a column
( pzpvstream) and saved in BLOB/Binary Format
UI --> XML--> BLOB-> Data Table
=========================================
pzpvstream: U work Object Data will be stored to this Property
pyID: it is a unique identifier. Ur WO ID Value will be assigned to a Predefined
property called pyID
=======
Where can we Create Work Object/Flows.
Work Object is an instance of Class group. Concrete class can have instances, but
not abstract classes.
We can add Work Objects only under Concrete Class ( Is a Class group & Belongs to
class group)- Keys( pyid) is defined only for Is a Class
group & Belongs to Class group.
We Cannot add WO under abstract class & Data Classes & Int Classes.
We cannot add WO's under Doesn't belongs to Class group (Data Classes & Int
Classes)

3 Types of Tables we have in Rule Base:

pc Table/Work Table: Work Object data will be mapped


pr Tables: Data Tables / Data Types will be mapped
pr4 Tables: Business rules /PEGA Rules will be mapped
Any Business rule we add in the application will be saved under the pr4 table.
Note: Any rule we create in the application including WO are instances of some
concrete class i.e. all the rules & WO gets stored in to
specific tables which are mapped to their instance classes.

Types of Flows:
Flow Types:
Process Flows
Screen Flows
Sub Flows ( Called Flows- Process Flow/Screen Flow)
Diff B/w Process & Screen Flows:
Process Flow:
• We can Add Work Object
• We Can add Multiple Flowaction's for Assignment
• Flowaction Name is Given under Assignment Connector Properties
• Routing is Possible at the Assignment Level
• In Process Flow 1 Transactions can have multiple steps/Tasks. In Process flow
every step is a separate task.
• We can Call Screen Flows & Process Flow in Process Flows, Calling One
Process/Screen Flow in another Process flow is called Sub
Flow. The Called flow will be subflow
• In Process flow there are no Types( Templates - Perform , New, Confirm)
• Process flow is the starting flow of the application/ Starter Flows
• In Process Flow we have only Front Navigation
• In Process Flow we have basic shapes, Advanced Shapes & Smart Shapes

Screen Flow :

We cannot Add Work Object


• We can Add One Flowaction for the Assignment
• Flowaction name is given under assignment shape Properties
• Routing is Not Possible at Assignment Level, but it is possible at Flow Level.
The routing option is available under start shape properties.
• In Screen flow entire transaction is Considered as 1 Task
• We can Call Screen Flow in Screen flow, We cannot call Process flow in Screen
flow.
• We have to call Screen flow in Process flow using Sub Process Shape
• Screen flow Contains Types/Templates ( Perform, Tabbed, TreeNavigation)
• In screen flows we have front & Back Navigation b.w Pages
• In screen flow we don't have advanced shapes.

Flows .................................................................. Properties ....> Sections
pr Tables: Data Tables / Data Types will be mapped pr4 Tables: Business rules /PEGA Rules will be mapped Any Business rule we

You might also like