What happens if a developer modifies a case type while a rule is checked out?

When a developer checks out a rule in Pega, they create a separate version of that rule that they can modify without affecting the live environment. Any modifications made to a case type during this checkout process do not impact the application or the current version of the rule until it has been checked back in. This allows developers to test and refine their changes independently, ensuring stability in the existing application while work is being done on the new version. Once the developer checks the rule back in, the modifications become effective and are applied in the application.

This mechanism ensures that the development and production environments can operate smoothly without interference during active development, allowing teams to work efficiently on enhancements or bug fixes without introducing potential issues to end-users.