ドラッグドロップ
左側の適切なルールセット バージョン タイプを右側の対応するシナリオにドラッグします。

Reveal Solution
Discussion
Correct Answer:

Explanation:

* Major version: In Pega, a major version update is typically used when there are significant changes to the application, such as the introduction of new functionalities, case types, or major changes to existing functionalities. Adding a new "Order return" case type to the Shopping application constitutes a significant enhancement, thus it would usually require incrementing the major version of the ruleset.
* Minor version: Minor version updates are used for less significant changes that don't alter the application's primary functionality but still add enhancements or optional components to the existing structures. Adding a stage-specific optional action to an "Order placement" case lifecycle would be a good candidate for a minor version update because it extends the functionality without fundamental changes.
* Patch version: Patch versions are often used for bug fixes or minor improvements that do not add new functionalities but rather correct issues with existing ones. Fixing a bug that lists product options by product ID instead of by name is a classic example of a patch fix, as it corrects a specific issue without materially expanding or altering the functionality of the application.
References:
* Pega official documentation would typically include a section on ruleset versioning that describes the
* scenarios for using major, minor, and patch versions.
* Best practices as described in Pega Community articles and the Pega Academy training materials also discuss how to manage ruleset versions effectively in various development scenarios.