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).
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.
See this idea on ideas.ibm.com
Implement a configurable mechanism within Apptio BI report settings to dynamically force specific filter criteria based on the user's selected TBM Studio view, thereby enabling granular report access control and eliminating the sole reliance on line-item permissions.
Currently, controlling data access within Apptio BI reports with True Cost as the data source, often relies heavily on TBM Studio's line-item permissions, which can be rigid and limited to a single dimension. This proposal introduces a more flexible and user-centric approach by allowing report administrators to define filter rules that are automatically applied to an Apptio BI report based on the Cloudability view selected by the user.
Why it is useful: This feature offers several significant benefits:
Enhanced Data Security and Compliance: Ensures users only see data relevant and permissible to their specific role or area of responsibility, even when sharing common reports.
Reduced Administrative Overhead: Eliminates the need for complex and often cumbersome line-item permission configurations in TBM Studio, simplifying user management and report distribution.
Increased Flexibility and Versatility: Enables filter enforcement based on multiple dimensions or complex logic defined within the view, which is not possible with current line-item permissions. This empowers administrators to create more nuanced data access rules.
User Empowerment: Shifts control of report access and filtering logic closer to the business users and report administrators who understand the data and organizational structure best.
Streamlined Reporting Experience: Users will automatically see filtered reports appropriate for their view, reducing the need for manual filter application and potential data exposure.
Who would benefit from it:
Cloudability Administrators: Would experience a significant reduction in the complexity and time required to manage user permissions and data access.
Report Developers/Administrators: Would gain greater control and flexibility in designing and distributing reports with tailored data views.
Business Users: Would benefit from a more intuitive and secure reporting experience, automatically seeing only the data relevant to their context without needing to apply manual filters or navigate irrelevant information.
Organizations utilizing TBM Studio and Apptio BI: Would improve data governance, reduce compliance risks, and optimize their reporting processes.
How it should work:
Report Configuration Interface: Within the Apptio BI report configuration settings, a new section would be introduced, similar to how business mappings are currently defined.
View-Based Filter Logic: This new section would allow report administrators to define "View-Based Filter Rules." The logic would operate as follows:
Condition: "IF User's Selected View EQUALS [Cloudy View Name(s)]"
Action: "THEN APPLY THE FOLLOWING FILTERS TO THIS REPORT: [List of Dimension/Attribute filters and their values]"
Filter Definition: The administrator would be able to select various dimensions and attributes available in the report's dataset and define the specific values or ranges that should be applied as filters when that particular view is active.
Idea priority | Medium |
By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.