Missing SKYVVA__MessageId while processing with InterfaceExecute scheduler #
An issue occurred during outbound processing with the InterfaceExecution scheduler where the SKYVVA__MessageId was not being generated into the request payload. This issue has since been resolved.
Missing the Category values on Message Type Field Entry #
To create the message type field entry, there are two ways: manually or by creating an auto-select from IStructure in the repository. This issue occurred while using “Select Field From the Repository” to create the message field entry. It was not taking the category value from the IStructure into the category field of message type field entry. However, this issue has now been fixed.
Loading all messages on the message detail screen inside the Root Message #
There was a problem when attempting to view a specific message, as the whole message tree was displayed on the message details screen. This could be difficult to view and took a long time to load, particularly when there were many messages in a root. However, this issue has been resolved by displaying only fifteen business messages including the select message. The selected message will highlight the green color.
Job id did not update the Basket Queue while running a schedule #
This issue occurred when the package size was added to the interface group and processed by the scheduler. For example, we have 30 baskets in the working basket, and each EO Queue has 6 baskets. Each basket contains 20 records, and the added package size is 100. As a result, it will take five baskets to complete a job because five baskets equal 100 records. It will take one basket for each EO Queue, so five EO Queues will work on the job. However, although the job is completed, it only updates one Queue for this job ID. This issue has been resolved.
