IBM Sterling Ideas

Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Post your ideas

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
1. Post an idea
2. Upvote ideas that matter most to you
3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

getOrderList API should provide one unioned, sorted result set across active and history records

Today's implementation of getOrderList API makes two calls under the hood - one to archive tables and one to active tables (assuming archive switch was invoked in the call.)


Almost *no* consumer of order history wants two separate lists, each sorted with its own history. Rather, the consuming application typically wants one cohesive time-ordered list of orders, especially from an Order Management system of record. How the data is stored and retrieved in the underlying should be of no concern to the consuming application(s), and the ramifications of the underlying design should be masked for the consumer. The serving application should take the onus to union THEN sort the result set, rather than requiring comparable functions in each and every consuming system.


Presumably, this behavior was designed with an assumption that archive records are inherently older that active records. This is not always true. As a multi-brand retailer, with staggered onboarding of brands to OMS, it is entirely possible to have a single customer with migrated (archived) records which are newer than one or more of the active records received for another brand. The net result to the customer is a brand-diminishing, improperly sorted order history (Several customers have already called this out.)


There is also a behavior in Call Center which moves order records from archived to active upon search and view, even when no modifications are made, which further exacerbates the issue.


  • Guest
  • Sep 8 2021
  • Future consideration
What is your industry? Retail
How will this idea be used?

Order history (getOrderList) is used to drive the My Account section of each of our website properties, and our telephone-based self-serve order status system at the Call Center.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.