Posts

Showing posts with the label Pega

Missing feature in PEGA 7: Process Instance Manager

Image
There may be many more features which PRPC doesn't have. May be the work on it is in progress with product team or may be Pega never felt to have one such thing. As a developer or the production system admin or a manager role in an prpc application, you may want to have a visibility of the business process. The over all business processes created in the system till date, the business processes running now, business processes that are suspended, business processes in waiting state. Something like this,                                                     Images: Cordys BOP4 We can also get all these info by running OTB list views from Work-, Assign- etc. but still a view like this would certainly be useful. Couple of days back, when i had been to Pega Developer Conference 2013 , i talked the team at the Designer Studio booth and they too...

Pega Vs Cordys

Important differences between Pega & Cordys: Non availability of Process Instance Manager in PEGA Clipboard in PEGA Vs  Data passage from one component to another component in CORDYS Everything is web service in CORDYS Non availability of integration to the any source version control in PEGA  Collaborative Work Space(CWS) can be attached to any any source version control in CORDYS Declarative Rules & Forward Chaining & Backward Chaining in PEGA JavaScript customization on b rowser events(OnClick, OnChange etc.) and integration with UI (XForms) in CORDYS Spinoff & Split Join flow shapes in PEGA

Usage of WorkGroup & WorkBasket in Pega

Image
It's been some time since i'm trying to understand the case management in PRPC. The concepts of WorkList, WorkGroup, WorkBasket are most confusing if not understood with some examples. Not to criticize any, i questioned many of my friends who has decent hands on experience in PRPC. But all that i get are vague answers or should i say theoritical answers. Spending lot of time on developer help, pdn etc, here is what i understood. Before i blabber more, let me put down the definitions from PRPC here, A workbasket is a named queue of open assignments that are not associated with an operator. A workbasket is defined by an instance of the Data-Admin-WorkBasket class. A work group is an instance of the Data-Admin-WorkGroup class. A work group can identify a user who is a supervisor, and a set of workers and workbaskets that report to that supervisor. Just have a look at how work group(referred as WG further) and work basket(referred as WB further...

Input validation & formatting at client side in Pega

Image
Client side validation is a very useful and beautiful feature of any web applications. The basic validations and formatting which doesn't require server side action can be done at the client side i.e. browser side mostly, and then the user submission can be passed on to the server. Two useful things of client side validation are, Reducing the serverside action, thus, reducing the burden/load on the server for the simple validations. Increasing the response time of the application. I.e. user need not have to wait for the request to be sent to the user and wait for the server to respond back to just say, " One text field is empty in the user form ". Pega provides rules Rule-Edit-Input and Rule-Edit-Validate for such formatting/conversions and validations. Rule-Edit-Input : This is provided in the advance tab of the property rule form. This performs conversions and not validations. No response will be sent to the user reg. the input validity. This rule performs con...

Exception handling in Pega Activities

Image
Exception handling in java methods can be done in many ways. We can log the reason for the exception, the respective stack trace and we can even manage to print the stack trace to your application specific logs(java does that by default though) explicitly using Reflection API or many other mechanisms. Pega also have such mechanism to exception handling in Activity rules. This can be done using standard when conditions named StepStatusGood and StepStatusFail(in @baseclass) in transitions of activities. These when conditions internally uses pxMethodStatus property to validate whether the execution of the particular step is successfull or failure. pxMethodStatus  property will be updated regulary with the status after end of each step execution and before the start of the next step execution. We also have a boolean named hasMessages which informs you whether a page contains one or more page messages. Any page which has one or more messages are treated invalid page  ...

Useful Activities of Work- class

Some very useful activities from Work- class we use very often in our day-to-day development process are listed below.  Work-.Add activity creates a new work object and performs a Commit method (without a cover object) Work-.AddWork activity creates a new work object but doesn’t perform a Commit method Work-.AddCovered activity creates a new covered work object and performs a Commit method Work-.AddCoveredWork activity creates a new covered work object and doesn’t performs a Commit method Work-.AddToFolder activity adds the work item to the folder Work-. ActionNotifyQuick activity creates simple correspondence Work-.CorrUpdate activity updates the correspondence Work-.CorrNew activity creates a new correspondence Work-.StartNewFlow activity starts an additional flow execution on the current work object. Work-.ResumeFlow activity is typically called when a service level deadline or goal is not met, this activity forces completion of an...

Pega Screen Flow

Image
Pega screen flow is a flow category option provided by PRPC to gather/collect information from the user in a particular sequence. Screen flow enables the user to go back and forth and edit the information at any point of time till the form is submitted finally. Screen flow can be created from New instance of FLOW rule dialog. The Template field has to be selected as screen flow.  Screen flows cannot create new work object and hence cannot be used to start an application. Because, "Creates a new work object?"  option in the process tab of Flow rule will be disabled for screen flows. This also means, a screen flow is useless unless used in a starter(i mean standard) flow. Screen flows can have embedded subflows. But normal standard flow cannot be added as subflow and only another screen flow can be added as subflow. The available flow shapes for a screen flow are, In screen flow, Flowactions are referenced by assignment shape rather than connect...