Things you need to know before proceeding with your first CURD actions in PEGA

Here is sample Work Flow

• Configure Case: Cases can be configure while creating application or can be done from Cases Explorer. Which consists Stages and Steps. Here steps are nothing but a flow.
• Data Table: Need to create properties in Data class, which acts as a column in the Database.
• Data Model: Need to create properties in Work class to bind with UI components.
• Section: Where you will assemble all the UI components
• Flow Action: Configure Section here to add any page level validations
• Activity: Your business logic will happen here
• Flow: you can configure your flow here
• Test the Case: Use tools like Clipboard, UI tree, UI inspect, Tracer.

Note: Any help related any rule / property / flow… you will find under Actions dropdown > Get Help.

Stages & Processes:

              You can go to Process by clicking cases types and click on any case; you can change the name of the Stage. Inside Stage, you can define any number of processes (steps). Each step should have one flow.

There are two types of Flows

• Process Flows/ Starter Flows/ Straight through Flows/ Main Flows
• Screen Flows

All 4 possible ways are allowed, like in Process FLOW you can call Process/Screen Flows

In Screen Flows you can call Process/Screen Flows.

Flows/ Starter Flows/ Straight through Flows/ Main Flows

           Right click on any steps click on open then you can see Process Flows. It is called Modular Tool, which has pre-defined shapes.

We use around 7 to 8 shapes in PEGA.

• Start: Begin the flow
• End: end the flow
• Assignment:
• Developer : Adding a Flow Action
• Business Analyst: will assign the task to developer using router and SLA.
• Subprocess:  used to call one flow in another flow
• Decision: used to call a condition in flow 
• Decision Table
• Decision Tree
• Map Value
• When
• Utility:  used to call method inside flow
• Integrator: connectors (inside connectors we need to use  methods with Activity Rule)

In both Flows, all shapes are same but behaviour is different for few shapes

• Assignment shape: In Process Flow, we can define Flow Action in assignment shape connector, but in Screen shape, we can see only empty inside connector. We need to give in the Assignment shape only.
• Routing, Service Level and Notifications are available in Screen Shapes but not there in Process Flows.
• Start shape: In Process Flow, it is empty. In screen, flow you can configure predefined screenplay types, means you can change the appearance of the page by using predefined screen flow type.
• Integration Shape: available only in process screen, not in screen flow.
• In process flow, you cannot navigate back flow. Only forward flow you can navigate. Where as in Screen flow both front and back navigation is possible.
• Work object will be created once after saving a flow, the work can added to the work group. It will automatically defined in the work group. So from the process flow it will generate case id, using that they will monitor the flow. Screen flows does not support work object. However, we can add screen flow to existing work object (process flow). Using subprocess shape, we can call the screen flows in the application.

Section:

           For every section, we need to add FLOW ACTION In Flow Action you need to configure section Under Flow Action > you can set page level validations. Page level business logic can set in Action tab

Activity:

          Activity rule comes Under Technical Rule Category, Using this we can build business logic. 

We can use Activity Rule in 10 different ways. 

• Utility Shape
• Section
• Property
• Flow Action rule
• Harness
• Onchange
• Connectors
• Services.

Explanation of Activity Rule Tabs

• Steps:  

            We can define methods. Only Method is mandatory in this page, rest of them are optional.

• Label: You can either use // to comment that method or you use this to pass parameter.
• Loop: to use loop condition then you can use this
• When: if you want to call this method on any pre condition then we can use
• Parameters: What type of parameters are mapping to which properties need to give it here.
• Method: use the existing method
• Step: to debug the application 
• Description: used to provide info of that method
• Jump: if you want to jump control 

• Pameters: You can provide temporary variable here in this tab
• Pages & Classes: Pages are used for debugging purpose and also reference purpose on what class we can performing the debuggers like Work or Data classes. Pega by default has some page names. 
• pyWorkPage: Generally for the work class we will give. It is case sensitive.          PEGA contain internal server (Clipboard tool/ Testing and debugging tool). Whenever we enter any data in form, first the data will be save in clipboard tool before saving to Database.You need to use pyWorkPage as a reference for insert operation to the Work class.You can give any page name to Data class while inserting.We will use pyWorkPage while inserting records.Using this you can perform server level debug.These will acts as reference to the Work and Data classes in Steps tab.
• Primary: we will give this to Data class reference while fetching single record.

• Security: Controlling the usage of the activity

 You can configure any number of methods in this Activity. Execution will start from order top to bottom. If you want you can jump from one method to another method. Methods are predefined in PEGA; we need to provide inputs/parameters to it.

Different types of methods are there:

• Connector methods
• Obj methods
• Obj-save: insert/update
• Obj-open: Fetch single record
• Obj-browse: Fetch multiple records
• Obj-delete: Delete record
• Property methods
• Property-set method
• Property-map-decision-table
• Property-map-decision-tree
• Property-map-value/value-pair
• Page methods
• RDB methods
• Show methods

Flow: 

        You can create Flow from Cases Explorer or from Process rule category.

Test:

       Use the clipboard debugger tool to debug the values and the flow.