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.
-
Tracing User Activity Across Multiple Sterling Applications
We are frequently receiving some requirements from the business regarding user activity for different applications(for ex: Call Center for Commerce, Sterling Business Center, IBM Store) which they are currently using.
For some users we are pr...
-
IBM Fix for createException
In createException(YFSEnvironment env, org.w3c.dom.Document inXML) API, in logs we able to find CreateuserID vaiable, once we directly call this API with this ID its overwrite session object userid. So want you to not display this ID in logs. In t...
-
Avoid opening capacity on shipment cancellation using changeShipment API
Enhance the product to provide a configurable option in Sterling to avoid opening capacity on cancellation of shipment using changeShipment API. Scenario: Consider a node with available capacity of 50. When an order is sourced to that node, availa...
-
Different safety factor % of onhand buffer to be set for each Node Type
Bussiness needs to mask an article with item node combination as there might be different scenario's where the store decides not to sell an item even if there is an inventory in the store. So we are looking if there is any other configuration whic...
-
Report availability at the Segment level.
Currently the monitorItemAvailability API and all RTAM capabilities report inventory at the node and item level, to some degree including tag information. The RTAM information doesn't have any references to segment. An example usage of segmentatio...
-
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.
-
Support Alternate UOM for the item pricing and promotion
Typically alternate uoms have a different pricing than the primary uom. The application currently allows to define pricing and promotions based on primary uom only. I believe the application uses primary uom to identify the item but that should no...
-
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...
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.
1
Future consideration