This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
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:
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Thank you for taking the time to provide your ideas to IBM. Your request may not be delivered within the release currently under development, but the theme aligns with our current long-term roadmap and, as such, is being tagged for future consideration.
Resolving the discrepancy between B2Bi/SFG and PEM username length is an important enhancement. However, usernames are the primary key in around 35-40 tables in the database, requiring a significant schema change, and UI + API testing.
Initial investigation in this area shows that while some databases like MS SQL can change primary keys on the fly during upgrades, others like Oracle cannot -- forcing customers to take an outage in order to upgrade. Oracle is our most commonly used database and would impact a large portion of our install base.
This breaks our rolling upgrade strategy for 6.2.x and adds complexity to any customer updating to the version with this feature. Due to the schema change and downtime required, we can only make this change in a major product version, i.e. a future 6.3.x release, to set the correct upgrade scope expectations with customers.
As such, we're considering this as a "future consideration" for our next major release of the product, tentatively scheduled for 2H 2025.
However, there is a workaround that could help in the meantime - using a SSP/SEAS custom user exit to map a long email/userID to a unique ID that fits into the current character limitations. IBM Expert Labs could assist with exploring solutions in this area.
We truly value our relationship with you and appreciate your willingness to share details about your experience, your recommendations, and ideas.
Please note: IBM's statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM's sole discretion.