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

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.