Unable to use schema elements as Business Object attributes when schema is defined inside the wsdl
(Doc ID 2506747.1)
Last updated on FEBRUARY 08, 2020
Applies to:Oracle Business Process Management Suite - Version 188.8.131.52.0 and later
Information in this document applies to any platform.
When importing a WSDL into a project you cannot use the schema elements defined in that WSDL as datatypes in custom BPM objects
If you try to use one of these elements in a BPM object you'll get an error:
"Unable to save XXXXX is in line in a wsdl and cannot be used as an attribute. Cause: The type is in line in a wsdl. Action: Remove the argument with that type)."
In BPM Composer it may have a different behavior where the schemas aren't available for selection.
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