Pega Training

Draft Flow :-

When we create a new flow, every flow by default, will be in Draft mode

Draft flows are dummy flows.

Draft On means , it’s in Draft mode and it is a dummy flow just for demo purpose. Draft flows are non-executable in Production.

When we create a flow, after all the configurations are done, make sure you turn off draft mode.

To turn off the draft mode, go to diagram tab and click on the icon “Draft ON”. When we click on it, it will be displayed like “Draft Off”

Understanding Creates a New Work Object Check box, available under process tab of Flow.

When we select this check box “Flow will be executable” that means, we see run option available under action dropdown.

Else Flow will be non-executable, means that, run option in action drop down will not be available.

Before you test it make sure you turn off draft mode.

Technical Explanation

Selecting the Option “Creates a new work object” makes the flow to generate a Work Object when a transaction is initiated.

This Work Object is a virtual entity that gets created in the background and travels through the flow from start shape to till end shape on it’s way to get resolve.

Work Object is Unique Identification for each transaction.

Work Object also called as “Case”.

Each Work Object can be uniquely identified by an ID called Work Object ID or Case ID.

EX :  C-123

Here C-  is called Prefix.

123 is sequential numeric number.

Here Work Object C-80 is created.  Enter the data and submit.

The Complete Transaction Data Will be held by Work Object.

After We submit the UI form, Work Object data gets stored into Backend Rulebase table.

Work Objects gets stored in Work Table.

“Work Table à PC_Work”.

Work Object or Case Continuation

               

Submit

Once, case is submitted, WO along with data gets stored into one of the tables called as

Work Table.

To see the Work Table and Work Object Created, go to Rule base.

Open PgAdmin4 Environment

Each Wotk object that we have create is a record in this table.

Work Object ID gets stored in a column pyID.

Look at the last column of the table

pzPVStream :- In this column WO data gets stored.

All the Entries First Name, Last Name Age, Gender etc..  gets stored into this column.

Here the format of data is BLOB.

BLOB – Binary Large Object.

Just Create a Test flow in Impl Class Group.

Open FW Class Group Flow and Save as to Implementation Class Group.

Save As

Create and Open.

Now, Run this flow.

C-82 is the Work Object Created.

Go to DB and see work table.

In the Previous Work Table, the New Work Object C-82 is not availalble.

Now, check in a different table.

Now, C-82 has been stored in a different table.

When flow is created in Implementation class group , the created cases stored in Table

 pc_arbe_arbellav_work

When flow is created in Framework class group , the created case stored in Table pc_arbe_fw_arbellai_work

·         When Work Object has been created by Implementation Class Group Flow, that work object is called as Instance of Impl class Group.

·         When Work Object has been created by Frame Work Class Group Flow, that work object is called as Instance of Frame Work class Group.

Work Object :-

       It is an instance of Class Group.

Class Group :-  

       It is instance class of Work Object(S).

To see the instance of a class Group.

Single Click on Class Group name it displays list of instances

Similarly click on FW class Group

Done.

How does process commander identifies the exact work Table to store work objects of a class group.

C-82 is an instance of Implementation class group Arbe-ArbellaV-Work

Where as

C-81 is an instance of Frame Work Class Group Arbe-FW-ArbellaI-Work

Each instance have it’s own instance class.

·         Each instance class has been mapped to one physical table in the Rulebase.

To see the mapping

Right click on each of class as shown below.

Click on the above row

The Above rule is called “Data base table mapping Rule”. Which Maps a class to a physical table in the Rule base.

This rule has been automatically created when we create new application.

Also It has created a physical table in the backend with the name pc_Arbe_FW_ArbellaI_Work.

The Table pc_Arbe_FW_ArbellaI_Work is amped to Frame Work Class Group “Arbe-FW-ArbellaI-Work”.

When an instance is created for Frame work class group, it gets stored into it’s Mapping Table.

Every Concrete class gets mapped to a Physical Table in the Backend.

The instance of concrete class gets stored into it’s mapped table.

Similarly Open the mapping rule of Implementation Class Group.

pc_Arbe_ArbellaV_Work

Our Implementation class group is mapped to a different table “pc_Arbe_ArbellaV_Work”.

The instance or Work Object of Implementation class Group gets stored into the table “pc_Arbe_ArbellaV_Work”.

When A Work Object Created it get’s stored into the Mapped table of It’s class Group.

Done.