IBM Sterling Ideas
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.
As part of the Watson Customer Engagement team we onboard new partner for our clients into SCBN solution . Onboarded solutions like envelopes often need modifications based on ticket PER/Support cases requests . Currently when we edit an en envelope in SPE02 we do not have the options to add comments or description of what change is made to the existing envelope based on the ticket number . Only when we create/clone a new envelope the basic tab in the envelope gives us this option and not the others . For example when we go to the "Key Identification Parameters " tab to modify/edit any existing settings , say the version or the EDI ID , once we have made the changes we have to save and the change shows up under the previous comments / ticket number of the envelope . Even the new change for the new version shows up under an old description for example the ticket number when the envelope was created . Along with the basic tab we should have a column to add comments or description and it should be made mandatory . In this way we should have a clear idea what change was made , under which case and description of the change , then only we should be allowed to save the changes as a good practice.
This allows us to have a current view and the latest change made to the envelope that helps greatly in troubleshooting issues.If the new changes are made and the description shows an old ticket number it is misleading .
How will this idea be used?
This idea helps in keeping track of all the latest changes in the solution and helps in troubleshooting issues during the on-boarding process . Faster rectification of issues and smooth on-boarding can be achieved over this good practice .
|What is your industry?||Other|
|What is the idea priority?||Medium|