PRPC Developer

If you are familiar with JavaScript you must have come across the usage of Higher Order Functions. Simply put higher order functions can accept functions as parameters or can return function as a result. When you understand the basics, it's joy to work with them. Due to the elegant design of PRPC runtime, we can easily simulate higher order functions using activities. Following activity is a good example of such a scenario. Code-Pega-List.ProcessSelection So next time when you find a problem see if you can solve it using higher order functions. If properly used your code will be more modular and look very professional.

Have you seen a colored clipboard like this before, probably not right, please read to find out how and more importantly why it looks as it is.

One of the major problems that Pega projects face with time is build up of test rules within the official business rulesets. If not properly managed these rules could end up in the production environment which is not an ideal situation to have. But can we really stop creating test rules, for me the answer is no, because creating test rules is also an integral part of the iterative development process. So how can we maintain a clean development environment while also allowing the creation of test rules. The answer is the Sandbox ruleset . By creating a separate ruleset only for test rules it is possible to have a clean development environment while allowing the creation of test rules in development process. Following are the steps that have to be followed Create a sandbox ruleset and version Update ruleset restrictions in classes to include the sandbox ruleset Create a separate sandbox application rule and include the sandbox ruleset and put your main application as t...

You can find the first part of this post from here What do you think one of the frequently asked question in PDN forum, any guesses?, it's about Excel integration with PRPC, but ironically by the time of this writing PRPC still does not support a rule based approach to the problem of Excel integration. So are we in a dead-end, frankly not. Due to the elegant design of PRPC, we can create our own custom rule to accomplish the task.   Welcome to the second post of the series "Creating custom rules in PRPC", as I pointed out in the first post, in this post I am planning to systematically lay down the steps that need to be taken in order to create a custom rule. Word of caution: Most of the things I am writing here are, what I called observable knowledge, meaning - understanding how something works literally by observing the system and in case of PRPC reading the rules in the system without going through a formal How-To docume...

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