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

Subject Areas

Subject Areas

The Subject Areas tab in the lower portion of the screen provides a tree that shows how the IDD application is configured.
As items are selected in the tree, the Add, Edit, and Delete buttons update to reflect the options available. The levels in the tree are:
Tree Level
Description
IDD Application
Subject area groups can be added.
Subject Area Group
The subject area group can be edited or deleted. Subject areas can be added.
The subject area group identifies the logical ORS to which the child subject areas belong, and which base object is the primary table for these subject areas. A subject area group can have one or more child subject areas - all sharing the same primary table. These subject areas are grouped together in the IDD application.
Subject Area
The subject area can be edited or deleted. Subject area children can be added.
If the subject area group contains more than one subject area, each subject area defines the HM entity type or sub-type qualifier that identifies the subject area. You also specify:
  • the package used to display search results
  • the match rule set and match type to use for duplicate checks
  • the columns from the Primary table that are part of this subject area
Subject Area Child
The subject area child can be edited or deleted. For each subject area child, you must specify:
  • the type of relationships (one:many, many:many, and so on)
  • which match path leads to the child table (the match path list is populated based on the relationship type selection)
  • the columns from the child table that are to be displayed.
Subject Area Grandchild
The subject area grandchild can be edited or deleted. For each subject area grandchild, you must specify:
  • the type of relationship (one:many, many:many, and so on)
  • which match path leads to the child table (the match path list is populated based on the relationship type selection)
  • the columns from the child table that are to be displayed.

0 COMMENTS

We’d like to hear from you!