No Check-in with Pega Warnings

Prevention is better than cure.

One of the main pain points of any Pega project is the gradual accumulation of technical debt. This buildup can be clearly seen by the declining compliance score. One of the ways to mitigate technical debt is to have a keen eye on code smells and refactor regularly. To identify code smells Pega has a static code analysis mechanism called Pega Warnings.

Even though the best practice is to fix (or occasionally justify) the warnings as soon as they appear, the best practice is not always followed and rules are checked-in with unattended warnings consequently increasing the overall technical debt of the system.

What if there is a way to stop the check-in process if a rule has unattended warnings. Following simple change will halt the check-in process if a developer tries to check-in with unjustified warnings.

From my practical experience I can say that this small change will have a huge impact on the overall quality of the code.



Comments

Post a Comment

Popular posts from this blog

Creating custom rules in PRPC

Image
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
Read more

Creating custom rules in PRPC – Introduction

Image
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 &quo
Read more

CSSA PDN Links Compilation

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
Read more