Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Adrie Ruiz (AdrieR44)
Hoverstate

Hoverstate
US
AdrieR44 Member since 2019 1 post
Hoverstate
Posted: Nov 12, 2019
Last activity: Nov 13, 2019
Posted: 12 Nov 2019 19:24 EST
Last activity: 13 Nov 2019 19:03 EST
Closed

Business Architect Essentials (v.8) - Rules and rulesets

Hi Pega Community!

I'm working through the BA Essentials Course version 8. While going through rules and rulesets I encountered this explanation for patch versions:

  • The patch version consists of fixes to address bugs in an application. For example, you notice that a field in the current version of an application has an incorrect label. You create a new minor version to correct the field label.

Is the example incorrect for explaining that a bug fix would require a new minor version? If the issue is to correct the existing field label would it not be a patch version?

To see attachments, please log in.
Pega Academy

Posted: 5 years ago
Updated: 5 years ago
Posted: 13 Nov 2019 16:38 EST
Updated: 13 Nov 2019 16:39 EST
Wolfgang Radl (mrwolf)
PEGA
Senior Solutions Consultant
Pegasystems Inc.
US

You're correct, changing an existing label usually warrants a patch and not a minor version. I think the description in the module is misleading (or plainly wrong, depending on your definition). Your application will always use the latest patch available for a rule (e.g. 01-01-05) without requiring you to make any changes to the referenced rulesets:

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice