Question & Answer
Question
Why does the REALTIME_AVAILABILITY_CHANGE event get triggered even when RaiseEventOnAllAvailabilityChanges is passed as 'N'?
Cause
This is Working as Designed
Answer
It working as per product design because API will call the same transaction (real time availability change ) which agent will call.
For example if you call the scheduleOrder API from API tester, it will call the scheduleOrder transaction and if we configured any service on this then API also will call that service.
In simulation if we are passing RaiseEventOnAllAvailabilityChanges = N, message is getting published by API without crossing the thresholds level.
The behaviour of the API is Working as it was designed. The use case it is catering to is following:
With WebSphere Commerce integration, WebSphere Commerce will call this API when they don't find availability info for a item in the cache. So this API will not only fetch the real time availability information from Sterling system but also update the WebSphere Commerce cache by publishing message to WebSphere Commerce.
The Java Docs were updated to reflect this in version 9.3 onwards: "Whether set to Y or N, REALTIME_AVAILABILITY_CHANGE or REALTIME_AVAILABILITY_CHANGE_LIST event is raised on all availability changes regardless of whether availability exceeds or falls below specified thresholds. Valid values: Y or N. Default value: N"
For example if you call the scheduleOrder API from API tester, it will call the scheduleOrder transaction and if we configured any service on this then API also will call that service.
In simulation if we are passing RaiseEventOnAllAvailabilityChanges = N, message is getting published by API without crossing the thresholds level.
The behaviour of the API is Working as it was designed. The use case it is catering to is following:
With WebSphere Commerce integration, WebSphere Commerce will call this API when they don't find availability info for a item in the cache. So this API will not only fetch the real time availability information from Sterling system but also update the WebSphere Commerce cache by publishing message to WebSphere Commerce.
The Java Docs were updated to reflect this in version 9.3 onwards: "Whether set to Y or N, REALTIME_AVAILABILITY_CHANGE or REALTIME_AVAILABILITY_CHANGE_LIST event is raised on all availability changes regardless of whether availability exceeds or falls below specified thresholds. Valid values: Y or N. Default value: N"
[{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SS6PEW","label":"IBM Sterling Order Management"},"ARM Category":[{"code":"","label":""}],"Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF034","label":"Windows Mobile"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"All;9.2.1;9.2","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
Was this topic helpful?
Document Information
Modified date:
07 April 2020
UID
swg21902613