Skip to Main Content
IBM Sterling

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 (

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:

Search existing ideas

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 your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Oct 22, 2018

ITXA support Bulk Update Codelist API without Version Number

Build-Date: 20181003.0829

Case Number: TS001467199


  1. We are referring here Bulk Update Codelist API . Not the Update Codelist API
  2. We want to use the API from Sterling Business process
  3. The below is the API URL used in the SBI BP http Post Service and this works fine.

<assign to="URI" from="&apos;/spe/svc/codelists/DEFAULT|DON_TEST|||8/actions/bulkupdatecodes&apos;"/>

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


"codes": [


"columns": null,

"description": "don156",

"endDate": null,

"id": "DEFAULT|DON_TEST|||8|don15|don15",

"receiverItem": "don156",

"senderItem": "don156",

"startDate": null




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.

  • Guest
    Jan 14, 2021

    Luke, what is the alternate for this problem ?

  • Guest
    Jan 9, 2020

    No plans to implement as it would require extensive work in the API.

  • Guest
    Jan 31, 2019

    Hi Team,

    We have not received any update on the subject idea yet. Kindly let us know the progress.



    Prosenjit Das