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.
Need to support criteria-based, more granular archive/purge policies for metadata and files
Requirement stated by customer is that B2Bi needs to support more granular archive/purge policies based on specific criteria such as trading partner and transaction type (identifiable through EDI Correlation).
Customer requires complete encryption of all objects stored at rest in B2Bi/SFG database including trading partner information
Requirement has been stated by customer that all columns in the B2Bi/SFG database be encrypted, beyond what is hashed (passwords) and at-rest encryption (documents). This would include more recent sensitive information such as user names, IPs and...
SSH User Identity Key > 2,048 bit
Partner ask to generate a auth key of 4,096-bit or larger, however Sterling menu doesn't allow for any key size except 1,024, 1,536 or 2,048. Also, there does not appear to be a documented and supported method to generate a key pair using a comma...
HSTS enhancement on GIS system
u As per the incident TS007584566 we have requested for HSTS enhancement in GIS system.Previously we have requested the same via TS007322240 and we have been suggested to raise a enhancement request as it is standard functionality.Kindly consid...
Update Certificate File via REST API
The B2B REST API allows the user to delete, create, or update attributes (such as the name) of an HTTPS certificate on the system. However, it does not allow a user to update a certificate in place (the "Update from existing PKCS12 Certificate fil...
Make the selected font color configurable in the skins.properties_style_ext file for B2Bi properties.
The selected font color now is yellow and can't be changed. If you color code your environments the standard green, yellow and red. The yellow font color is now hard to see your environments. Let us decide what the selected font color should be.
Enhance SWIFTNet7ClientResend business process to update previously failed filegateway deliveries
Currently SWIFTNet7ClientResend will be triggered via the SWIFT Adapter Scheduler to look at the SWNET_MSG table for failed PUT transfers to SWIFT. Upon detection of these types of failure the scheduler will trigger an execution of the SWIFTNet7Cl...
EBICS order type - automatically splitting and processing of SEPA containers
We have a requirement to split the SEPA XML containers for customers from Ebics order payload file and process them individually
Include special characters (e.g. @) in Parameter Name of Obscure Data - Process Data Values service
We are using SI 184.108.40.206 and the Parameter Name does not allow special characters such as "@" being used in the Obscure Data - Process Data Values service. This prevents email addresses being used as Names.
Remove the validation of the X520SerialNumber in the PKI-J toolkit
An error occurred when updating a certificate for a client with a Serial number too long issue. Certicom found that certificate is not valid and cannot be used since the X520SerialNumber contains more than 64 characters which violates the RFC.
Do not place IBM confidential, company confidential, or personal information into any field.