In OSM 7.2 The First Part Of The EjbName Of An External Automation Component Has To Match Taskname
(Doc ID 1572906.1)
Last updated on FEBRUARY 28, 2019
Applies to:
Oracle Communications Design Studio - Version 7.2.2 and laterInformation in this document applies to any platform.
Symptoms
On : 7.2.2 version, Order And Service Management
ACTUAL BEHAVIOR
---------------
In OSM 7.2 the first part of the ejbName of an external automation component has to match the task name otherwise the consumption of messages will not work properly.
The expectation is that there should be a validation in Design Studio while modelling the automation task.
For example if a task with:
Design Studio should indicate an error for this automation task.
BUSINESS IMPACT
-----------------------
Message consumption is not proper and the order gets stuck or fails.
Changes
Cause
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
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |