MENU
How can a single report be configured to display the account attributes of all the accounts to Application Owners?
To configure a single report that displays the account attributes of all the accounts to their respective Application Owners in Saviynt, the best approach is D. V2 Analytics using SQL Query with User Context. Here's a breakdown:
Saviynt's Analytics V2: This is Saviynt's newer analytics platform, offering more advanced features and flexibility compared to the older version.
SQL Query with User Context: This is the key to achieving the desired outcome. 'User Context' means that the query will be executed in the context of the currently logged-in user (in this case, the Application Owner).
How it Works:
Dynamic Filtering: When an Application Owner runs the report, the 'User Context' will automatically filter the data to show only the accounts that they own.
Security and Data Privacy: This ensures that each Application Owner only sees the data that they are authorized to access.
SQL Query Structure: The SQL query would likely involve a JOIN between the accounts table and a table that defines application ownership (e.g., applications), using a WHERE clause that filters based on the current user's ID or username. Something like this (syntax might need adjustment for Saviynt's specific SQL dialect):
SELECT a.*
FROM accounts a
JOIN applications app ON a.application_id = app.application_id
WHERE app.owner_id = ${CURRENT_USER_ID} -- This is the user context part
Why Other Options Are Less Suitable:
A . Use Elasticsearch Query: While Elasticsearch can be used for analytics, it might not be the best tool for this specific requirement, as it doesn't inherently support the concept of 'User Context' in the same way as SQL queries in Analytics V2.
B . V2 Analytics using SQL Query with External Connection: External connections are used to query data from external databases, which is not necessary in this scenario.
C . V2 Analytics using SQL Query with Allowed Action: Allowed Actions are used to define actions that can be performed on analytics results, not for filtering data based on user context.