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.
RTAM - Inventory Alerts - Save Suppy, Demand & Safety Stock inventory positions
As part of inventory publish, few systems are interested in ATP (supply - demand - safety stock), few other systems are in only (supply - demand) and few others are interested in only onhand supply. However, RTAM publishes only ATP and to calculat...
Database extensions should have a provision to create indexes only on ACTIVE tables.
Database extensions should have a provision to create indexes only on ACTIVE tables. As most of the queries/monitoring and reporting are performed on the ACTIVE tables.These indices may not be always needed on the HISTORY tables.
Java 64 bit implementation for Application Manager
In my team, everybody having Java 32 bit even I also downgraded to 32 bit which can support 9.5 Console-> Configuration -> Launch Application Manager. We seen that if we use 64 bit, then Application Manager we not able to Launch.Once we move...
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' st...
Order Management on Cloud dataload to use DB Index and runstats for table YFS_ITEM
During an OMoC initial dataload there can be a need to upload 1M+ item records to the YFS_ITEM DB table. This table is initially empty and non indexed. This can make the dataload INSERT take a very long time when using the ManageItem API. There is...
Let us decide if YFS_INVENTORY_ITEM "select for update" will be used during API calls
For many models, a "select for update" is essential. In our case, our items are tightly controlled, so we do not expect to need to create inventory item records that can then be promised or ordered. We would like to have the choice in findInventor...
Enable purging data from transaction tables directly, instead of first purging to history
We currently have userexit purgeOrderToExternalDataStoreUE for purgeOrder. This was provided by IBM on our request. We are using this currently in production. This only covers orders and its related entities, but not shipments, receipts, work orde...