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.

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.
  • Guest
  • May 9 2018
  • Not under consideration
Order Management (OnPrem & OMoC)
What is your industry? Consumer Products
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.

×

Attachments Open full size

Related ideas

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.