Idea
Best Practices for Naming Conventions.
In many ways, the Pega Platform is ensuring the best practices that developers need to maintain with the help of guardrails.
But there is no way we can ensure to follow best practices when it comes to naming conventions as of now. But theoretically, we can say how a stage, process, step, or rule should be named.
The solution I thought of is analyzing the names with NLP and indicate an error or a warning immediately after they enter. So that developers can change or modify.
And we can suggest similar context names following the best practices, according to the text entered by the developers. So this even reduces the work of a developer.
I totally agree with that but on the higher note, we could at least add it as a feature so the developer could know like whatever entered is falling under the best practices for naming conventions or not. And definitely, this isn't mandatory as you mentioned every organization has its own naming conventions.
Thank You,
Sadhvikkalakonda
Hi @SAISADHVIKK,
Thank you for sharing your idea here in the Pega Collaboration Center (PCC)!
I have submitted this idea on your behalf in our internal system for feature enhancements and updated your post with the associated FDBK-ID. You can take this ID to your Account Executive for next steps.
Thanks and keep the ideas coming!
@SAISADHVIKK ,
I could suggest to use the naming conventions used in Java OR any other Object Oriented programming languages in General.
Every organization has their own variable/fn/class naming conventions. I don't think enforcing everyone to follow same naming convention could add value from my experience.
-Nanjundan Chinnasamy | PEGA Lead Decisioning Architect