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.
Support for TLS V1.3 for B2BAC trading partner connections
The governance body across the Superannuation Transaction Network (STN) is maturing its security posture. As such they are looking to mandate TLS V1.3 connection in the future.
Password stretching use appropriate ASD approved algorithm for B2Bi
A recent audit under the Gateway Network Governance Body - Information Security Requirements has identified that B2BI is not compliance is ASD ISM control 1402 - Security Control: 1402; Revision: 5; Updated: Aug-20; Applicability: O, P, S, TS Stor...
Support for TLS encryption to four MEIG databases
Precision Administration is an approved Gateway Operator. Consequently we are bound by the security requirements of our governance body - the GNGB - https://www.gngb.com.au/ The GNGB published their Information Security Requirements which includes...
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.
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...
BYO (Bring Your Own) Certificate with CRL checking
For "New Install" tasks - instead of using self-signed certificates, Control Center Director should allow to use user's certificate for the communication between Connect Direct server and Control Center Director.
Add Failed Login Attempts information to Audit Log
Failed Login Attempt is considered to be important audit trail information and should be present in the Audit Log.
Increase the maximun runnable C:D session from 99 to *NOMAX or a higher limit
Currently, the maximum active C:D session is 99, when the session limit is reached, and new C:D job is initiated , it will abend with CDE0200 and the C:D job have to be retried again.
Logging and Monitoring - extend the storage of Application logs to 12 months
Telstra Security Operations - Risk Assessment Rating High Audit logs are not stored for 12 months or sent to Telstra's splunk solution. Infrastructure audit logs are stored for 12 months but application audit logs only stored for 90 days. Mitigati...
Order Status changes to be audited
when order line status is changed by schedule order/release order or any other API's, status change is not getting audited in the order audit tables. Request to get this feature added
Do not place IBM confidential, company confidential, or personal information into any field.