DMW Behavior On Renaming Models And Tables
(Doc ID 2583747.1)
Last updated on SEPTEMBER 25, 2019
Applies to:Oracle Health Sciences Data Management Workbench - Version 18.104.22.168 and later
Information in this document applies to any platform.
When renaming a model or table in Development lifecycle, it gets renamed in all lifecycles immediately, without promoting said model version. For example, MyModel1 must be renamed to MyModel2. As soon as it is changed in DEV lifecycle; PROD shows already the change, even before it is promoted to QC. Is this the expected behavior?
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