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 (https://ideas.ibm.com).


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 (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.

Status Under review
Created by Guest
Created on Apr 10, 2026

Sequence number capability with configurable RESET options

Currently we have a hard Government requirement to reset a sequence number every year but would like to have a more generic configurable option which can be triggered via map.

 

Provide a standard mapper function or something which can be called from mapper

  • Generate incremental sequence numbers within a mapping execution
  • Support configurable reset options such as:
    • Per message / transaction
    • Daily / monthly / yearly reset
    • Custom reset triggers (e.g., based on field value or batch)
  • Allow formatting options (prefix, suffix, padding, length)
  • Ensure thread-safe handling in parallel processing scenarios
  • Admin
    Manoj Panda
    Apr 10, 2026

    @Guest Thanks for submitting this idea and for clearly outlining the need for a configurable sequence number reset capability. We recognize that reset requirements—often driven by regulatory or partner mandates can be a challenge in active implementations. The scenarios you’ve described, including mapper‑driven triggers, formatting flexibility, and safe handling in parallel processing, provide helpful context.

    We’re currently reviewing this request to better understand the broader customer impact and the most appropriate way to address it within the product. We may follow up with a few clarifying questions as part of this review. Please feel free to add any additional use‑case details that might be helpful. please check below questions.


    1. Reset scope

    • Should the sequence reset be scoped per trading partner, document type, or business process?

    2. Trigger mechanism

    How should the reset be triggered in your use case (time‑based like yearly, event‑based, or driven by a field/value in the message)?

    3. Usage frequency

    Is this reset expected to occur as a regular operational behavior (e.g., annually) or only during exceptional events?

    4. Current workaround

    Are you using any workaround today (custom mapping logic, external counters, database sequencing), and what limitations are you hitting?

    Manoj Panda

    Senior Product Manager

    IBM Sterling