Cloud and AIOps
This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps 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).
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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
This request will not be implemented, for architectural and security reasons.
Workflows are executed by workers, and workers are not necessarily located on the same host or environment as the Concert instance itself. Many enterprise deployments rely heavily on remote workers for execution, so there is no guarantee — and often no expectation — that a "local" file path would even be reachable from the worker running the workflow.
Beyond that, allowing the execution engine to read arbitrary files from a local file system without any authentication is a security risk we're not willing to introduce. File access of this kind would bypass standard authentication and access controls, which would not pass reasonable security review.
Recommended approach:
Files should be sourced through an authenticated, addressable location — for example, a shared storage system, object store, or internal API/service that the workflow execution can access with proper credentials, regardless of which worker executes the workflow.