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.
WorkOrder Purge effeciency
Observation in workOrder purge agent. 1) Multiple getsJobs are getting triggered with EnterpriseCode. 2) yfs_task_queue table doesn't have EnterpriseCode column, which leads to pick unnecessary records for executeJob (multiple enterprise scenario)...
Scheduling agent triggers in different time zones (Other than UTC)
Currently the advances scheduling option for agents only takes time in UTC and triggers the same in UTC time zone. For different countries like US people want agents to be trig-erred in their time zone for example EST. EST has to be converted to U...
Enhance data export process to support cloud storage
As per the current design, the export file is directly written onto the SFTP server also it's possible that incomplete files can be read by the consumer process. because this is implemented on SFTP there is no inherent event that can trigger a co...
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...
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.
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.
JSON Support for Agents/Integration Servers
Be able to consume a JSON message via Agents and Integration Server. Currently only XML Messages are consumed. Similar to APIs we should be able to consume JSON messages.
Implement 'Hold' for a bulk product order for up to 30mins (or XX mins) as per OMoC SF ticket TS002131182
Add following functionality for 'On Hold' bulk items up to XX mins. As per following scenario ... We have created a remorse hold, to hold order's for 30 mins. To resolve the hold, we have created hold processing agent which is abstract transactio...
Ref Case #:TS001675506, ETS and EAD not getting updated for pickup Orders (Chained Orders) when there is change in PO ETA
Whenever there is change in PO ETA, For Pickup Orders Orders (Chained Orders) ETS, EAD are not updated correctly.
More details can be found at case#: TS001675506
Do not place IBM confidential, company confidential, or personal information into any field.