Skip to Main Content
Cloud Platform

This is an IBM Automation portal for Cloud Platform products. 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 Future consideration
Workspace UrbanCode
Categories Deploy
Created by Guest
Created on Dec 13, 2022

The status/result of a deployment should correctly reflect the result of the external approval process

We are making use of the external approval process to check at deployment time if the deployment is allowed to happen.

Our process consists of two steps:

- Step 1: Make an external call with the 'Send HTTP Call' step

- Step 2: A groovy script to print the output & set the Status to "Success" or "Failure" through a Post-Processing script

When a deployment is triggered, we always set the "post-deploy-put-url" in our 'requestApplicationProcess' request that points to a web hook in Jenkins & 'post-deploy-message' is set to '${p:finalStatus}'. Based on the response of the webhook call, we either proceed with the Jenkins pipeline. If we get a status that is failed, the pipeline gets aborted.

The problem that we are facing is two-fold:

1) UCD doesn't trigger our callback when the External Approval Process fails

2) When the deployment failed, and it clearly says 'External approval failed. This

process request has been aborted.' in the Execution Log, when we ask the status of the request with the api 'https://xxxx/cli/applicationProcessRequest/requestStatus?request=181e7dbf-2a9d-991d-ccff-40b29e1a3550'

Then the response is:


"status": "PENDING",



The above statuses are clearly incorrect. When an external approval process fails, the deployment will never continue. Not now, not in the future, so the fact that UCD still sees & reports them as 'PENDING' - 'SCHEDULED FOR FUTURE' is clearly wrong.

Idea priority High
  • Admin
    Osman Burucu
    Mar 8, 2023

    A preliminary evaluation of this request indicates that it is consistent with our business strategy. Further evaluation of this RFE is underway.

  • Admin
    Osman Burucu
    Feb 15, 2023

    Thank You for providing a new idea. Together with the development lead we are analyzing it.