Closed
Ruleset naming convention with "-"
Hi, in our latest 8.4 product, i see a lot of rulesets with a dash inside "-".
Is that the latest recommended naming convention?
e.g.
| PegaCS-SuggestedReplies:08-04 |
| PegaCS-ApplicationGuides:08-04 |
| PegaCS-FBM:08-04 |
| PegaCS-IVA:08-04 |
| PegaCS-IVR:08-04 |
| PegaCS-IVRCDH:08-04 |
| PegaCS-WFI:08-04 |
| PegaCS-Advisor:08-04 |
| PegaCS-AdvisorReporting:08-04 |
| Pega-Reporting:08-04 |
| Pega-UIDesign:08-04 |
| Pega-Gadgets:08-04 |
| Pega-UIComponents:08-04 |
| Pega-UIEngine:08-04 |
| Pega-ProcessEngine:08-04 |
| Pega-SearchEngine:08-04 |
| Pega-IntegrationEngine:08-04 |
| Pega-RulesEngine:08-04 |
| Pega-Engine:08-04 |
Posted: 5 years ago
Pegasystems Inc.
US
Pega develops foundation apps.
A dash makes it easy for someone to see to which Pega foundation app the ruleset belongs.
That doesn’t mean that everyone else needs begin their ruleset name within their company name.
A layer abbreviation prefix, e.g. “CS-” for customer service, though makes sense for those building on top of Pega's Customer Service app.
Ruleset names should never be purely an abbreviation where no word spelled out.
Someone maintaining code should NOT have guess what each abbreviation means.
A ruleset name can be 64 characters long.