PRPC Developer

Pega Rules Process Commander is such a wonderful product. It is built so elegantly with layer upon layer of abstraction so that a normal business user can easily change the runtime behavior in order to adjust to the changing business conditions without going through a typical development cycle. At the same time it is a mixture of J2EE technologies, bunch of browser based thin client technologies and more importantly a wonderful design that has the unique feature of "ability to be extended in multiple layers", where a person could not distinguish whether a feature is out of the box or custom made. All these are possible due to the initial wonderful design of PRPC. One of the best things that the designers of PRPC have done is, even though there are multiple layers of abstraction, they have given us, the end developers a chance to extend the core product through custom rule creation. Before creating custom rules first let's get a clear understanding to the question ...

Following PDN links compilation document will help you to prepare for the Pega Certified Senior System Architect CSSA 5.5 exam. It is created according to the CSSA blueprint . Please use this as a starting point to prepare for the exam. Happy reading. CSSA PDN Links Compilation

Business needs are always changing, so changing a logic of a process even after it went to the production is quite common. PRPC with the Build for Change motto does very good job of keeping it promises. But you need to be careful when changing flows. Because you might be in trouble if you do not know the below points. Happy reading. PDN article link

According to my view Content search is one of the main features within PRPC and most probably the best. Content search enables us to learn the beautiful PRPC architecture and it acts like a personal trainer. So how does the content search does all its magic. The secret is, Pega’s Content search is implemented using Apache Lucene open source text search engine. You might be thinking it is a well known fact. Yes, you are absolutely correct, most of the Pega developers know that the content search is based on Apache Lucene. So then what’s all this fuss about. The truth is we only use a fraction of what is available to us as content search, since the content search is based on Apache Lucene, we literally get the power of Query Parser Syntax in Lucene directly into content search. That means you can do Fuzzy searches , Wildcard searches , Fields searches , Proximity searches , use Boolean operators , Group several searches and list goes on. For actual syntaxes please read this w...

As Software engineers , the pinnacle of PRPC development is creating your own custom rules which goes through the Rules assembly or First Use Assembly ( FUA ) process. You might wonder why someone should put custom rules creation at the top, frankly the reason is when you design a custom rule and finally implement it, you are exposed to the wonderful design of Pega itself and you slowly understand the inner workings of PRPC. The moral of the story: Don’t be stuck in a higher level abstraction layer, go down and explore how the creature is build, then only you will understand its behavior.

Have you seen the following error messages, as developers we might have seen below error messages while developing with PRPC. But what will happen if these error messages happen to pop up on production environments. Look closely, these messages might be disclosing internal details or sometimes these messages are not meaningful to end users even though these are good debugging aid for developers. So as a solution PRPC has given us various options to customize error messages and configure some of them. To find out please read the following three PDN articles. Happy Reading. 1. Suppress details of show exception details (Java Exception Traceback) 2 . How to suppress the Show Details link after a database exception ...