Table of Contents

Search

  1. Preface
  2. Introduction
  3. IDD Concepts
  4. Implementation Process
  5. IDD Configuration Manager
  6. Manual IDD Configuration
  7. IDD Global Properties
  8. Sizing and Platform Requirements
  9. Application Components
  10. IDD Security Configuration
  11. Data Security
  12. Example Role-Based Security Configuration
  13. Data Masking
  14. Siperian BPM Workflow Engine
  15. Locale Codes
  16. Troubleshooting
  17. Glossary

Data Director Implementation Guide

Data Director Implementation Guide

Open Review Tasks with Multiple Roles

Open Review Tasks with Multiple Roles

User with multiple roles can open the task only if the following conditions are satisfied.
  • All the pending records associated with task should satisfy data security filters for at least one user role.
  • A user with multiple roles can have combinations of filters applied. The result is that the user has access to all the data available in each assigned role - a union of the filter assignments.
  • If security filters are configured over children or grandchildren, then one of the following conditions must be true.
    • Primary object has at least one record passing security restrictions in each child tab with enabled data security.
    • The pending record associated with the task has a child tab with data security enabled and meets the data security setting as mentioned in the preceding condition.
For example, consider a data security model in which the user has the role, Sales Manager- NY and has the data security filters as mentioned in the section Open Review Tasks with a Single Role and also role, CarSalesManager-NJ, which has the following security filters configured.
  • Filter 1: State code is NJ.
  • Filter 2: Car Year is 2009.
Also, user has another role CarSalesManager-CA, which has the following security filter configured.
  • Filter 1: Address State code is CA.
  • Filter 2: Car year is 2008.
Using the data security model mentioned above, consider a scenario where the database has a primary object record, Mr. Derrick Rose, who has the Billing address in CA State and home as phone type. User with no data security restrictions adds a new billing address in NY State and creates
Send for Approval
task. User with Sales Manager- NY role will be able to open the Mr. Derrick Rose record on the data view as it satisfies security filters of SalesManager-NY role.
Using the same data security model mentioned above, consider a scenario where the database has a primary object record, Mr. Tyros Thomas, who has the Billing Address in CA State and a car produced in 2008. User with no data security restrictions changed the billing address to NJ and creates
Send for Approval
task. User with both the roles both the roles CarSalesManager-CA and CarSalesManager-NJ is not allowed to open the task as Mr. Tyros Thomas does not satisfy filters for CarSalesManager-CA and CarSalesManager-NJ with pending record for new address.

0 COMMENTS

We’d like to hear from you!