Is there any best practice for maintaining BRF+ applications in a multi-release environment? For example, take the following scenario:
1. BRF+ Application ZAP_EXAMPLE with Global access level is deployed to production as version 1.0
2. Application ZAP_EXAMPLE has new business rule functionality that is being developed for a version 2.0 in development system
3. Application version ZAP_EXAMPLE has an emergency fix to version 1.0 business rules that needs to move into production
Can application versions somehow be used to control this? Are there options other than removing version 2.0 rules so that fixes to version 1.0 can be moved into production without moving up the 2.0 rules?
Thanks,
Nick Simon