IBM Sterling Ideas

formerly Watson Supply Chain

Submit new product ideas for IBM Sterling solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed. Order Management, Store Engagement, Watson Order Optimizer, Inventory Visibility, CPQ and Call Center are now part of Watson Supply Chain

Connect with IBM experts and your peers on the Supply Chain Collaboration Community and the Order Management Interest Group

Increase the maximum number of statuses displayed in InFlight

The number of statuses displayed in "New" InFlight needs to be increased to what it is in "Legacy" InFlight.  The attached Word doc. shows the difference between what is displayed for the same document in "New" and "Legacy" InFlight.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Oct 8 2018
  • Delivered
How will this idea be used?

When there are AS2 connection issues, we are not able to see the full history for a document.  This is very important in trouble shooting.  When there are more than 25 statuses, it stops displaying them, so the last one displayed does not even match the current status.

What is your industry? Other
What is the idea priority? High
DeveloperWorks ID
Link to original RFE
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    October 14, 2018 19:15

    Is anyone else having this problem?  If so how are you working around it?  Why is it not an issue for you?

    Suggestions welcomed.

  • Admin
    John DELPIZZO commented
    October 17, 2018 17:26

    Agree it should work the same. Routing to engineering for evaluation.

  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    January 09, 2019 18:30

    It is possible to view a maximum of 50 statuses, however, this is still not enough when there are multiple retries doing FTP, for instance.  The last status in the File portion of the screen might show "Success" and the Event is "Scheduled for Retry" or "Retry Started".  The TRUE status in the Document detail portion of the screen is "Failed" if it runs out of retries and the process stops.  This needs to be changed so that all the statuses show up in the File portion of the screen until it is either truly successful or it fails.  Perhaps some maximum needs to be in place in case of unending loops, etc., but this maximum has to be much higher than 50.  Perhaps 500 would be reasonable.  The current limitation does not allow the user enough visibility to trouble shoot.

  • Admin
    JEANNINE Calandra commented
    January 17, 2019 20:17

    An update to address this is planned for January 24th