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 (https://ideas.ibm.com).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Hi John, we look forward to our discussion on November 27. Prior to our meeting, could you please review this comment which comes from our development team and we will discuss this further together when we meet to see if this could address your request. Here is the comment:
"We think what the customer should be doing here is using a combination of environment properties and application Process properties. Then they should only need to have one application process.
Basically, the application process would have an non-required property(or set of properties) that is the thing they need to fill in(like RFC id), and then they would have an environment property defined on all environments that dictates whether its required. At the start of the process they would then have a step that checks that if env property (requiredRFCID or something) is Y or 1 or true or whatever they like, it would validate the rfc id for that environment, if the env property is not set, just skip that step."
Thank you for your reply. We will review your response with the development team today and provide feedback soon. We have a call on November 27 to discuss this. I will move this back to the "Under Review" state.
Im well aware of the switch statements and how it could be used here. Our usecase is that we have two applications process, one for test and one for PR, which calls the same component processes hence the actual deployments steps will be run mostly the same way across the environments.
The issue lies in that we want to utilize the application properties to make the user enter some input parameters (like RFC id) to the PR deployment. From what I understand this is only doable through application properties and not environment properties. We of course dont want users to have to enter this information when deploying to the test environments, and thats why we ended up with two different application processes.
Perhaps there is an other solution to making applications processes bound to an environment but I failing to find it.
We will work to schedule a meeting to discuss this Idea. Thank you for submitting it. Our development team will join us for the meeting so more context is available. I think there is a way to handle this programmatically using tools like switch statements and the ${p:environment.name} property. We can discuss this further.
Here is what our development team shared (and we will discuss as a group soon):
"By design, we expect applications process to be run the same way in all environments. This way they can get a accurate test case before trying them out in production. Is there some specific reason they need it to run in production(PR), but not test?"
Thanks for creating this Idea for us. We have opened a jira discussion topic for this idea to review it with our development team. We will be in touch to provide updates.