The all concept of PRPC is to break the wall between IT and BUSINESS department. We don’t want to see the business guys writing requirements for two years and developers writing Java for the 2 following years.
A PRPC architect should be able to discuss the business needs and configure dynamic and easy to change rules. Also a PRPC architect doesn’t have to be a Java expert, we don’t want to have a new member of the team looking into hundreds of Java lines to finally understand what should be changed to create a quick evolution for a new business requirements.
I believe this is mainly why writing custom java is mentioned on our guardrails.
This could be happening. For a developer the tentation is high to do everything in Java but the main goal at this point should be, how can I make it simple, how can I make it easy to change, to modify and to eventually re-use. What do I really need to do in Java lines and what can be achieved with RULES. This is how I would do it, try to use RULES as much as I can and maybe create Rule-Utility-Function or a Java step to do the remaining work.