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.
-
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...
-
Capability to copy or share BUC Workspace across multiple users
Need the ability to set-up large / complex workspaces that can be shared across multiple users. One user may have edit capabilities while others may have view capability only Or, in lieu is workspace sharing, offer an option to copy a workspace be...
-
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.
-
Authenticate OMS users without having to preload the user base
Many clients of OMS do not maintain a user repository system that can send user load to OMS. Users will be present on the client's active directory and will can be authenticated and created in OMS during the authentication.
-
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...
-
Unable to add charge per line once order is invoiced.
Requirement is to create informational charge for line after order is invoiced. Following below steps followed. Once order is invoiced. call change order to add informational change i.e. ChangePerLine and ChargePerUnit. ChargePerUnit is getting up...
-
Better integration between manageOrganizationHierarchy and Calendars
The API for managing organizations allows the caller to specify the receiving, shipping and business calendars, but only by specifying the calendar key. The key is typically a system generated value which is unique to the environment and therefore...
-
Account for store time zone in RTAM node level availability calculation
RTAM would honor the property yfs.useNodeLocaleTimeForCapacityCheck, which is currently required in CoC implementations to have inventory APIs correctly calculate availability in the store's local time.
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
Planned for future release