In the previous blog Recommendations for Addressing the n+1 landscape - Approach 1 we talked about the approach using direct production bug fixes. In this Blog, we talk about the approach when the next wave of development is for New Objects only
Approach 2: New BOs created in the existing solution
Scenario: Your next wave of development is essentially only for new objects
Objective: Achieve differentiation by segregating the NEW BO using Business Options
In the existing PDI solution, if a new BO is to be created, it can be linked to a separate Business Option (provided a Business Topic was created for the existing PDI solution), thereby allowing the user to scope this in the Production tenant only when Phase 2 goes live. Until then, continue to test in the Test Environment. Here again, one can continue with the existing 3-tenant landscape since the new BO development needs only additional scoping when ready in the Production tenant. On the existing Dev and Test environment the new BO and UIs would be scoped of course but doesn’t affect or interfere with the existing code (assuming there is no cross referencing of new BO in existing code of course)
ABSL Code: Since this is linked to the new Business Option, the code wouldn’t be visible unless scoped in the Production tenant
New WoC/UI: Since this is linked to the new Business Option, the Uis and new WoC wouldn’t be visible unless scoped and assigned in the Production tenant
New Custom UI associated with the standard screen: Since this is linked to the new Business Option, the additional enhancement related to the new BO wouldn’t be visible unless scoped and assigned in the Production tenant
This is a 4 part blog series with the following links:
Approach 3: Switch Option (Next Blog)
Recommendations for addressing the n+1 landscape - Approach 3
This is a 4 part blog series with the following links:
Recommendations for addressing the n+1 landscape - Approach 1
Recommendations for addressing the n+1 landscape - Approach 2(When new BOs are created in the existi... - This blog
Recommendations for addressing the n+1 landscape - Approach 3 (Switch Option)
Recommendations for addressing the n+1 landscape - Approach 4 (Commenting out Code)
With contributions from pramodh.patil stefankrauth sridhar.natarajan
Thanks !
Vinita
