Incorrect Base Schema And Script Code When Creating Issues Detected For An Activity
Last updated on APRIL 29, 2016
Applies to:Oracle Utilities Mobile Workforce Management - Version 188.8.131.52.0 to 184.108.40.206.9 [Release 2.2]
Oracle Real-Time Scheduler - Version 220.127.116.11.0 to 18.104.22.168.9 [Release 2.2]
Information in this document applies to any platform.
Incorrect base Schema and base Script Code when creating Issues Detected for an Activity
Create plug-in algorithms that will create Issues Detected for an Activity for business specific scenarios (similar to the base Algorithm M1-VAL-ACT). However there are 2 issues found which are due to an incorrect base schema and base script code.
1. The schema related to Issues Detected cannot handle multiple message parameters because the list has a primary key of "Parameter Type". The result is that we can’t have a message with multiple message parameters.
2. Base script M1-ActDspShr has incorrect code when calling the F1-ReturnMessage Business Service. The script is not able to properly pass the message parameters of the issues detected list. The result is that the expanded message of F1-ReturnMessage does not properly populate the message parameters.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms