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.

Add a new idea Subscribe
Status Needs more information
Workspace Sterling B2B Integration SaaS
Categories Inflight
Created by Guest
Created on Sep 26, 2025

RELATED IDEAS

Receiver mailslot information should be available from Inflight Events and in the Inflight filters

Below are the existing situations:

  • Currently the customer see only MQ Message ID and MQ Correlation ID from the Inflight. However, no mailslot information is available there.

Current Challenges:

  • From the Inflight, the customer doesn’t have the visibility of the mailslot where their files have been reached.

  • Especially for the BEDI setup, the only way to check if a particular file has been delivered or not is checking each batch during that time manually. This efforts will be reduced. Without support help it is difficult for the customer to find out the final status of the messages.

Use Case

  • There are many EDI and non-EDI flows where we are sending files from GISHI malslot to Receiver mailslot. The customer knows about the Receiver Mailslot. Hence, this enhancement will be very helpful to track a file for the support team as well as the customer.
    Example: As an example, PREMIER FARNELL UK LTD sends messages from GISHI to the mailslot SRXEVPFP, then it reaches to the Receiver mailslot SRXEVPPI, from where the customer picks the file. Right now from the Inflight only the following details are available:
    Event Details:
    System: PRO02
    Process ID: 627055427
    System: TX01
    Process ID: a13922fd-23d3-49d3-a49a-3290cd4a69ba
    MQ Message ID: E2D9E7C5E5D7C6D7F0F0F0F1F0F8F1F9F0F3F3F8F0F7F0F0
    MQ Correlation ID: F7F8F0F6F1F28183F0F0F0F4F1F1F9F883F0F6F784F8F6F7
    Protocol: CNET
    Audit Key: {1}

New functionalities to be added: Below new functionalities to be added

  • When a file process from GISHI mailslot to CNET mailslot(Target System ID: CNet), in inflight the receiver mailslot information should be visible.

Functionalities to be Added:

  • Inflight - Filters- Add 'ReciveMQslot' as a filter field and display it as a new column in the Inflight Outer View

  • When a file process from the GISHI to CNET mailslot, the final mailsot details and the final status of the message should be visible from the Inflight.

  • Right now, only MQ ID is available, along with this, the Batch number and Tracking ID from VAN should be visible from the Inflight.

  • Admin
    Manoj Panda
    Dec 12, 2025

    Dear Souradip,

    Thank you for submitting this idea and highlighting the challenges around not having Receiver Mailslot visibility in the Inflight events. I understand how this creates gaps for both customers and Support—especially in BEDI and other multi-hop flows where tracking the final delivery endpoint becomes manual and time-consuming.

    Providing Receiver Mailslot information directly within Inflight (and possibly as a filter) aligns well with our goal to improve end-to-end traceability and reduce dependency on Support. This enhancement would certainly simplify monitoring, speed up investigations, and give customers more direct control over their document visibility.


    To evaluate this further, I would like to clarify a few key points:

    1. Should Receiver Mailslot be shown only in the Inflight details, or also be available as a searchable/filterable field?

    2. For multi-hop flows (GISHI → Transform → Receiver), do you want to see only the final Receiver Mailslot or all intermediate hops?

    3. Do customers need this visibility for all protocols and flows, or mainly for EDI/BEDI-specific traffic?

    4. How should the system behave if the message has not yet reached the Receiver Mailslot or if delivery fails—should it display “Pending/Not Reached”?

    5. Should access to Receiver Mailslot information be available to all customer users, or restricted to certain roles (e.g., admin or operational users)?

    Once I have your inputs, I will review this with Engineering and Support to assess feasibility, metadata availability, and UI/UX implications for adding this visibility to Inflight.


    Thank you again for bringing this valuable enhancement forward.


    Regards,

    Manoj Panda

    Product Manager, IBM Sterling B2B & VAN

    Reply

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.