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 Submitted
Created by Guest
Created on Sep 29, 2026

Support mandatory `modifiedBy` parameter on Segmentation Allocation Rules APIs in Order Hub to track the user who last created or modified a rule.

Currently, when Segmentation Allocation Rules are created or updated in Order Hub or via the SIP Inventory Configuration APIs (POST and PUT /inventory/{tenantId}/v1/configuration/segmentRules), the response only stores and returns ruleId and lastModifiedTime. There is no field to capture or retrieve the user (modifiedBy) who created or modified the rule.

We request the following enhancement for the Segmentation Allocation Rules Configuration APIs:

  1. Enforce modifiedBy as a mandatory parameter in the request payload of POST /inventory/{tenantId}/v1/configuration/segmentRules and PUT /inventory/{tenantId}/v1/configuration/segmentRules/{ruleId} (and automatically pass the logged-in user ID when modified via Order Hub UI).

  2. Store and return modifiedBy alongside lastModifiedTime in GET /inventory/{tenantId}/v1/configuration/segmentRules and GET /inventory/{tenantId}/v1/configuration/segmentRules/{ruleId} (RuleDetailsResponse).

What is your industry? Electronics
How will this idea be used?

This will be used to identify which user created or last modified a segmentation allocation rule across Order Hub UI and API integrations. Enforcing modifiedBy as a mandatory field ensures user accountability alongside lastModifiedTime whenever inventory allocation rules are updated.