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

Step 3.1. Configure Subject Areas in the Hub Console

Step 3.1. Configure Subject Areas in the Hub Console

Configure subject areas in the Hub Console.
  1. In the Schema Manager, review the match path components that are configured for the root object of the subject area and verify that there are match paths for each of the child objects that need to be included in the subject area and for related objects that need to be used in searches.
  2. In the Packages tool, create the search display package that will be used to display the search results for the subject area. This is a package with the subject area root object as its primary table.
  3. In the Schema Manager, check subject area lookup dependencies.
    Lookup Mechanism
    Description
    Code Lookup tables
    Code lookup tables must have the Lookup Indicator set to TRUE (checked) in the base object properties in the Schema Manager.
    Entity Lookups
    Entity lookups can be specified only to entities that are configured as subject areas. This can introduce complex dependencies between the subject areas. As part of the iterative development of an IDD application, you can exclude entity lookups from the initial IDD configuration if there are dependencies on the other subject areas that have not been configured. The lookup fields can be added after all subject area dependencies are satisfied.

0 COMMENTS

We’d like to hear from you!