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

Item Catalog Search Index Enhancements


OM provides feature to store all extended item catalog data in the form of additional attributes. This feature also allows us to setup any type of complex structure between itemid and extended catalog data. Internally the product uses “Additional attributes” entity to create this type of setup. OM also provides the ability to search these attributes to fetch relevant items by building apache lucene search. OM also provides feature to restrict the item search space using the item category and the same item attributes. All these are via the searchCatalogIndex api.

However there are some deficiencies with this setup and it doesn’t really help using the index for fine grained item search:

  1. The apache lucene index builds the index with hard-coded string ‘AdditionalAttribute’ as the index field name
  2. When a subset of item attributes are added to the item category and the category path is passed in the input to the searchCatalogIndex api to search for the data, we are not sure whether the index search is efficient enough to only search the attributes configured under that category.

So we would like to log the following enhancement requests:

  1. Ability to build the search index with “Indexfield Name” as the AdditionalAttribute Name instead of hard-coding to ‘AdditionalAttribute’
  2. Ability to have ‘Condition’ like attribute in the ‘For Filter’ : Presently the apache ‘Term’ feature supports ‘condition’ based search. We need a similar attribute on the ‘For’ filter. Reasons being the enhanced ability to query the index fields by constructing the query at runtime.
  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • May 9 2018
  • Needs review
How will this idea be used?

The customer that we are working for, has a concept of item controls. Using this controls setup, the business team sets up various business rules to restrict the type of item that can be ordered. Some of the use cases are:

  1. restriction based off whether the ordering user is part of a particular user group, type of user and the type of order that he is placing.
  2. Restriction based off whether the ordering user is using a particular ordering platform, based off whether the item belongs to a particular group etc.,

With all these enhancements, we expect to deliver a superior search functionality to the customer.

What is your industry? Consumer Products
What is the idea priority? Urgent
DeveloperWorks ID
Link to original RFE
  • Attach files