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.
Application should allow log tracing at app server level
In Production, there are cases where Support engineers need to debug an issue enabling verbose trace for an application server. However , the logging on a specific application server is not supported by IBM Sterling product.
Provide for consideration of in-store take-sales (non-order) / cash-and-carry when calculating node sell-thru - without impacting transaction quota
Today, Sterling provides for calculation of store node sell-through velocity based on the order fulfillment that OMS has visibility to by virtue of orchestrating orders. However, in practice, a given store node derives a large portion of its sell-...
Ability to convert JSON payload to XML sent to asynchronous defined in OMS
OMS currently supports conversion of JSON payloads to XML if passed to REST endpoints defined from OMS. However, if there are asynchronous services defined in OMS using JMS/ MQ, it mandates that the inputs passed is always XML for consumption by O...
Alerts for Agent Exception to be raised per order
When any alert is raised for Agent Exception for an order , all the alerts are consolidated under AGENTEXCEPTION exception type and not per order number. if alerts are available for each order number , it will be easier for IT support team to look...
To enhance the WebStore application to support the pagination strategy -"GENERIC"
PaginationStrategies are set to perform ServerSidePagination or MixedPagination. It helps to fetch the records in batches. Store supports NEXTPAGE Strategy. But not all the OOTB List APIs support NEXTPAGE Strategy. By default, only 'Generic' strat...
Returns processing on over shipped catch weight quantities
When a refund is initiated on an overage product (Meat/Deli), IBM matches Refund quantity with ORDERED qty, NOT with SHIPPED quantity. This causes discrepancy during settlement, and needs to be manually adjusted.
Prevent reversing existing authorization upon error on subsequent authorization requests on the card
A valid authorization can be used to charge the member upon ship confirmation and hence the product should not be reversing all the authorizations on the tender.
Provide capability for a BUC user to get from Node exception alert or a Node Details page to Node’s order list
OMNI Fulfillment managers oversee several hundred nodes and need the ability to see a Node's open order, or orders flagged as an exception, while reviewing the node's alerts or from the Node Detail page. Use Case. How to get from Node exception to...
Add support for alerts with data security groups/teams, filter alerts based on enterprise assignment in the team.
Currently alerts aren't managed by team assignment, the request is to fix that so that if a user belongs to a team that is restricted to enterprise 1 they are only able to see alerts associated to enterprise 1 and not enterprise 2 or 3.
Attributes in Device definition should be available in getDeviceList API input and output
Through API manageDevice, we can define the attribute values against any printer that we are configuring. But there is no capability to fetch the details of these attributes using getDeviceList. Thus, those attributes can not be used in implementa...
Do not place IBM confidential, company confidential, or personal information into any field.