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.
<assign to="URI" from="'/spe/svc/codelists/DEFAULT|DON_TEST|||8/actions/bulkupdatecodes'"/>
Here "DON_TEST" is the Codelist Name , 8 is the Codelist Version Number.
Our Objective is to not use version number in the URL whereas API should intelligent enough to find out the selected default version from the Codebase and work on that version. It's difficult for us to keep track the latest version and provide the same in the URL and it will be more error prone incase version mismatch.
API also should create a new version while updating the latest version and mark the new version as latest version in the system.
4. We have to provide the Old items value as well as the new item value when we want to do any update of the existing item using Bulk Update .
We have to provide ID field details in the API Body when we want to update any existing item(Sender Code, Receiver Code, Start Date, End Date, Description) with new item.
Ex. Here we want to update Don15(Old Sender Code/Receiver Code) with Don156( New Sender Code/ Receiver Code). Input Json file will be look like below
Expectation: There must be some way to avoid giving Old data items while updating with new data items. As we are trying to build some automation to update Codelist from SBI Business Process hence it will be difficult for us to maintain both Old Items and New items.
|What is your industry?||Wholesale Distribution & Services|
How will this idea be used?
Customer wants this feature should be available ASAP in Production as there is a situation where we want to Update Multiple Code list at a time and we want to build some automation to update all code List at a time.
Do not place IBM confidential, company confidential, or personal information into any field.