Cloud Platform

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:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive a notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

If you encounter any issues accessing the Ideas portals, please send email describing the issue to ideasibm@us.ibm.com for resolution.

For more information about IBM's Ideas program visit ibm.com/ideas.

Status Under review
Workspace UrbanCode
Categories Deploy
Created by Guest
Created on Sep 7, 2021

Access to ApplicationProcessRequest properties without a full deployment trace

In order to generate custom deployment reports to our release management team, we are required to list up all the deployments, including a wide range of additional data (may or may not come from UCD).


As part of the deployments, there are certain properties that are set when launching a deployment through the API. These properties are ApplicationProcessRequest properties that act as metadata in this case.


As part of generating this file, we request all the deployments that happened through https://www.ibm.com/docs/en/urbancode-deploy/7.1.1?topic=ar-get-information-about-all-application-process-requests-server. However, this endpoint does not return these properties.


Therefore, we need to make an additional call to https://www.ibm.com/docs/en/urbancode-deploy/7.1.1?topic=resource-applicationprocessrequestinforequestidproperties-get to retrieve this information. The problem here is that this payload is very large (it contains the full deployment as a rootTrace). In case we need to generate a report for 2 months with 1000's of deployments, this process become very slow, consumes a lot of time for information that we don't need.

Why is it useful?

Our batch to generate the file of the deployments of the last 30 days takes 3,5 hours. We're currently requested to generate this report for the past 6 months for audit (potentially up to year). This is going to take longer & will have to run during business hours or we have to cut it up into multiple chunks.

Idea Priority High