My Oracle Support Banner

Isolating Non Repository Items In Parallel Development (Doc ID 2516248.1)

Last updated on JUNE 30, 2022

Applies to:

Siebel CRM - Version 17.0 [IP2017] and later
Information in this document applies to any platform.

Goal

How the non-repository changes like views, responsibilities, runtime events, etc would work in case of siebel 17.X parallel development? There are 2 parallel releases R1 & R2 and both have their own non-repository items. So if created2 integration workspaces pointing to these 2 releases then the non-repository items then how to keep the non-repository items for both the integration workspaces different?
 

Solution

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
Goal
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.