Posts

Showing posts from August, 2012

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...

http://www.bigcinemas.com -- BIG FRAUD

Image
I tried booking tickets at Big Cinemas, Ameerpet, Hyderabad through online booking on https://www.bigcinemas.com  on 12 of July'12. The booking process & show/seat selection went on smooth and i provided my credit card details on the website to confirm the booking. After some minutes of processing, its mentioned as " Some technical difficulties occurred during your booking process, Please check your email for confirmation.If you have not received any booking confirmation and your payment is deducted, Kindly contact us at support@bigcinemas.com for your refund. " -- Mind you, i didn't click on Back or Refresh on the browser for this to happen. I immediately mailed to above email id to receive this response on 14th July. Dear Guest, Warm Greetings from BIG Cinemas ! We appreciate you taking the time to contact us and share your query. We are not able to trace the failed transaction with the details received from you. We request you to please forward us your c...