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. Appendix A: Sizing and Platform Requirements
  9. Appendix B: Application Components
  10. Appendix C: IDD Security Configuration
  11. Appendix D: Data Security
  12. Appendix E: Example Role-Based Security Configuration
  13. Appendix F: Data Masking
  14. Appendix G: Siperian BPM Workflow Engine
  15. Appendix H: Locale Codes
  16. Appendix I: Troubleshooting
  17. Appendix J: Glossary

Data Director Implementation Guide

Data Director Implementation Guide

Open Merge/Unmerge Tasks

Open Merge/Unmerge Tasks

IDD applies the following rules to determine whether the merge or unmerge task can be opened by the user.
  • Merge task can be opened, only if all the Primary Object that are to be merged meet the data security settings.
  • Unmerge task can be opened if Primary Object can be opened according to Data Security settings.
For example, consider a data security model in which the user has the role, SalesManager-CA and has the security filter billing address state code – CA.
Using the data security model mentioned above, consider a scenario where there are two persons in database with same name Kevin Durant. One of the individuals has one billing address in LA (CA State), and the other one has a Bill Address in New York (NY State). User with no data security restrictions creates
Merge
task for two person records. Users with SalesManager- CA role will not be able to open the task as they do not have the required permission to open a person record with billing Address in NY State and thus cannot perform a whole
Merge
task.

0 COMMENTS

We’d like to hear from you!