Security and Process Control in Financial Data Management
Explore the importance of process-level security in financial data management, including business use cases, data access rules, conditional input enforcement, security filtering, and process control workflows. Learn how to implement no input rules and business rules to enhance security measures.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
You are allowed to download the files provided on this website for personal or commercial use, subject to the condition that they are used lawfully. All files are the property of their respective owners.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author.
E N D
Presentation Transcript
PROCESS LEVEL SECURITY Jon G & Eric Davidson
Business Use Case Alice is a controller at the plant level Executes base input workflow each month, certifies, and locks Bob is the Group Finance Controller and needs to unlock Alice s workflow to enter an adjustment in a form Once Bob unlocks Alice s workflow, Alice would have the ability to edit data This poses an audit and control risk
No Input Rules Certain data intersections in Cube can be marked as invalid for a variety of reasons Can be done through Member Properties or Constraints
Data Access Conditional Input Can enforce Conditional Input Rules today through the Data Access tab in the Cube Settings
Conditional NoInput Business Rule New feature in 3.6 Now can write a Business Rule to implement Conditional Input Rules Flexible enough to have input conditional based on values in other cells or Member Filters Place logic in a Finance Business Rule Assign Business Rule to related Cube(s)
Security Filtering with NoInput Rules We can use the NoInput Business Rule based on a security group Use a separate cube to set the security level by entity Finance Business rule is attached to the Cube
Process Control Cube Process Control Cube is used to store status flags for the Process Control Level
Process Control Workflow & Form Workflow is built for an Admin to enter a Security level by Entity
NoInput Business Rules + Process Control NoInput Rules could be created to process in this way: Perform a lookup for the intersections to be edited via a GetDataCell function to see which security level is in play (e.g. level 3) Check the security level assigned to the user, either via a number on that user s Text1 property or via their inclusion in a User Group Based on the User s security level vs. what is in place via Process Management, the user will either be permitted to input data or denied based on NoInput logic
Enhancements & Product Integration Use a workflow event handler to automate the process control security level setting Property in workflow for promotion/demotion level It s gonna be HUUUUUUGGGGEEEE
