OIG 3.20.2 Resolution Inconsistent
(Doc ID 2707007.1)
Last updated on SEPTEMBER 02, 2020
Applies to:Oracle Health Insurance Claims Adjudication - Version 22.214.171.124.0 and later
Information in this document applies to any platform.
Able to create classes but the scope of the class is limited.
With the upgrade/path provided creating a class in dylo now works. Instantiating a class in the same dylo works as well. Instantiating that class in another dylo does not work consistently. If the dylo is another class it seems to work. When trying to instantiate that class in a dylo that is just a script it cannot resolve the class. The same issue is experienced with the inbound code. The code does not compile.
For Outbound Vendor integration all code has been written in groovy using classes. It runs successfully from the command line on the VDI. When porting it over to dynamic logic functions an error is received that it cannot resolve classes imported.
When attempting to test after applying the patch, the following error occurs.
org.codehaus.groovy.control.MultipleCompilationErrorsException: startup failed:
ohi.dynamiclogic.vendorroutertransformnrt.vendorRouterTransformNRT.groovy: unable to resolve class ohi.dynamiclogic.OutboundVendorFileLineWriter
@ line 22, column 28.
def outboundFileWriter = new ohi.dynamiclogic.OutboundVendorFileLineWriter()
ohi.dynamiclogic.vendorroutertransformnrt.vendorRouterTransformNRT.groovy: unable to resolve class OutboundVendorFieldMapping
@ line 23, column 8.
List<OutboundVendorFieldMapping> fieldMappings = outboundFileWriter.buildFieldMappings()
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