Isolating Non Repository Items In Parallel Development
(Doc ID 2516248.1)
Last updated on NOVEMBER 18, 2020
Applies to:Siebel CRM - Version 16.7 [IP2016] and later
Information in this document applies to any platform.
How the non-repository changes like views, responsibilities, runtime events, etc would work in case of IP18 parallel development? There are 2 parallel releases R1 & R2 and both have their own non-repository items. So if we create 2 integration workspaces pointing to these 2 releases then the non-repository items then how can we have keep the non-repository items for both the integration workspaces different?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document