This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
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:
The apache lucene index builds the index with hard-coded string ‘AdditionalAttribute’ as the index field name
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:
Ability to build the search index with “Indexfield Name” as the AdditionalAttribute Name instead of hard-coding to ‘AdditionalAttribute’
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.
What is your industry?
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:
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.
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.
Do not place IBM confidential, company confidential, or personal information into any field.