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.
-
Improve case sensitivity in OMS search functions
Searching for a name in the OMS requires a perfect match with capitalization. I would like this to be improved so that the OMS also brings up names that are not perfect matches. For instance, if I search Jake Brewer, but the customer input jake br...
-
Create refresh button for Returns
When a return order is created it should have a refresh button OOTB in the OMS UI that allows the user to refresh the return without having to go back to the original order.
-
Built in Multi Line Reshipments
Currently, If a customer needs an entire order reshipped the user would need to reship each line individually and the lines would release separately. We would like a OOTB way to reship multiple lines at one time and have them release together.
-
Allow line and header level discounts as percent
Currently, in OMS users have to calculate the percentage at a line level and it creates a possibility for human error. I would like to allow the user to input a discount percent at both the line and header level in OMS. This would reduce the numbe...
-
Add a status field on Inflight under Business Field1 to find out only the status of "Finish" documents
Many Support Users from GSK are asking if there is a way find Finish documents from Inflight from search criteria instead of looking into events. This feature will also be useful if there was a planned outage at partner of customer side to hold do...
-
User group filter with & (and)/ |(or) and return attribute customisation
To implement PEM SSO current PEM can only use custom attribute / attribute with which can only return one string. Expected output as mentioned below.Sample output user role: </property><property><name>role</name><value&g...
-
Display of Translation error in the Inflight search Dashboard
Every time we see any translation failure in Inflight, we will have to open the error-ed entry to see why the transaction got failed, and Inflight eventually do not show up the error immediately if there is any failure. It would take time to load ...
-
Suppress password policy error messages from SEAS logs if using Ping for Active Directory.
ERROR LdapPasswordPolicyRetriever - ************** Uknown or unsupported LDAP server detected
We use Ping for our Active Directory solution and it was determined that Ping does not return the password policy to SEAS as expected. Therefore, this...
-
Group system in userfile.cfg (UNIX)
In an environment with hundreds of users defined in the same userfile.cfg, it would be nice to be able to govern them through a system of groups or profiles to reduce administration time and avoid unnecessary failures.
-
Standardize SYSOPTS syntax for multi-environments
SYSOPTS syntax is written differently depending on the environment: Windows, i5/OS, z/OS, and UNIX. Example on z/OS: SYSOPTS = "DATATYPE(BINARY) XLATE(YES) STRIP.BLANKS(NO)" Same example on UNIX: sysopts=":datatype=binary:xlate=yes:pipe=yes:" This...
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.
0
Submitted