This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. 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.
We have an exploration not planned yet to confirm what columns we can provide as an option to the user to select (customize) the results view.
The recommendation of usage of Tags demonstrates lack of understanding of Process Engineering, error resilience, and most of all, having read the initial description as I've explained precisely why this is particularly problematic.
Even if we add a new other layer it would depend on user's manul input, which would could be forgethen as well.
False: The DSCx (Data Source Connection) MUST be Named (as it's infrastructure to Doc Builder usage so process control would dictate these will follow stronger protocols in definition (these aren't defined per execution either, frequency of process step not only increases cost, it increases error opportunities - that DSCx are defined once / Stream means if they are defined correctly, they will always be correctly defined; if incorrect, it will be detected fairly quickly if this column is added).
Thank you for submitting idea.
We discussed it internally and Data Source Connection can also be a duplicated information in different templates, becasue you can use the same data source in different templates.
The recommendation as best practices is use different Names and Tags.
Even if we add a new other layer it would depend on user's manul input, which would could be forgethen as well.
Could you please provide a screenshot or any other way to show what you are thinking for this improvement?