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.
Ability to generate CDT differences between two CDT Full export and apply the differences to a target environment
Configuration differences to largely automate migration of differential configuration from a lower work stream to a higher work stream without re-typing.Configuration differences to automate removal of configuration from a higher work stream if it...
DB Extract agent should be extracting data more frequently
Currently the field 'FrequencyInHours' in the DB Extraction agent configuration defines how frequently the data can be extracted. The min value for FrequencyInHours is 1 hour. This would mean that we can only pick up data that is older than 1 hour...
Being able to monitor and get alerted for external services failures
External Services MonitoringExample: Alert if OMS not able to connect with VertexAgent Trigger FailuresAlert if Agent Job trigger failed/Failure
Being able to get alerted based on log file monitoring
It would help to view data similar to Kibana Based Dashboards and get alerts based on Error Codes & Rate of Error Codes.
Ability to view contents of a QueueNumber of messages/Queue DepthOldest MessageAbility to clear Bad data/Add for any Smoke testReceive Queue Depth Alerts (via pagerduty). Aging Messages AlertsIdle Time - No transactions in the queue in last one hour
Being able to get alerted through intelligent data-driven alerting mechanism
Provide us an ability to get alerted as part of data driven alerting.ExamplesNo Orders not created in last one 20 MinsLow Volume of Shipments from DCHigher Fraud Hold Pending OrdersSchedule Agent backlog High Configurable by Channel, Thresholds, B...
Real Time - Order Processing Dashboard required
We would like to measure the below KPIs (and get alerted)Orders Flow by Selling Channel ( Web, Call Center, Store)By Hour, By Day, Trend Graph for Previous day vs CurrentOrder Allocation Summary By Fulfillment Channel ( DC, Store, DropShip)By Hour...
Support for latest Cybersource SDK
The latest Cybersource SDK jar file (6.2.7) requires the use of apache commons lang 3 version 3.4 jar file (version 3.3 also works).
Since the base product already includes apache commons lang 3 version 3.2 however, the updated jar file does not ...
Ability to issue a common build that includes all extensions
In the on-prem world, we would build custom extensions and issue smcfs build. In the cloud world, we are required to create UI extension jars (for call center, and other apps) and drop the respective jar files under respective application WEB-INF ...
Provide method to script the OMoC/Cloud build and deploy process
The following are the 7 basic steps for building and deploying a package to the OMoC/Cloud OMS environment. In an on-prem instance of OMS, all of these steps are easily scripted so that the admin can run one command and execute everything, that ma...