BatchValidate Method Does Not Work As Expected After Upgrading To 220.127.116.11
(Doc ID 1642563.1)
Last updated on MARCH 02, 2017
Applies to:Siebel eConfigurator - Version 18.104.22.168  and later
Information in this document applies to any platform.
BatchValidate has been called in order to create the default instance of a customizable product.
However, BatchValidate doesn't save the instance when status is Invalid
Happens after upgrade to 22.214.171.124 (Incremental Repository Merge applied)
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
|This document is being delivered to you via Oracle Support's Rapid Visibility (RaV) process and therefore has not been subject to an independent technical review.|