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 Submitted
Categories Usability
Created by Guest
Created on Apr 24, 2024

PCM File Reprocessing

User would like the ability to see the status updating with the appropriate status once a file has been reprocessed. Example when a file has been reprocessed user would like to see the different stages the file is flowing though (Processed, Timed Out, Waiting, Complete, etc). 

Current behavior, only shows the status' of "Reprocessed", "Failed", and "Success".

User frequently has the need to reprocess mass number of files at once, currently when reprocessing a mass number of files the PCM environment times out without giving notice. This is causing a major issue to the user and the customer as files will be reprocessed multiple times causing the same file to be sent a multiple number of times because user is not aware the file is in the "Process" of reprocessing or if the system has times out. When the files are duplicated this is causing profit loss. For internal user this is also causing many hours of rework which is not acceptable. This is not a very good experience for the user or customer and negatively impacts the users brand.

The desired behavior user would like to see is, In the event of mass restarts over a threshold, they should be handled via an offline job of some sort that goes back and updates the status of the document in PCM. E.g. the document can start with 'processing' then when its successful be set to 'complete' or if PCM times out waiting on B2B, the status would be set to 'Timed Out' or "Waiting". And if the reprocessing is successful it would shift to 'Complete' so that the status in PCM matches the status of the underlying system