Table of Contents

Search

  1. Preface
  2. Introduction
  3. Configuring the Data Director Application
  4. Establishing a Root Node
  5. Defining the Business Entity Model
  6. Configuring Business Entity Properties
  7. Configuring Reference Entity Properties
  8. Transforming Business Entities and Views
  9. Configuring Hierarchy and Network Relationships
  10. Creating Match Rule Sets
  11. Configuring Search
  12. Configuring Tasks
  13. Configuring Security and Data Filters for Business Entities
  14. Configuring the Content Security Policy
  15. Integrating Data as a Service
  16. Configuring External Calls
  17. Designing the Data Director User Interface
  18. Localizing Data Director
  19. Appendix A: Provisioning Tool Frequently Asked Questions

Record View Layouts

Record View Layouts

Record views appear in an entity tab when users create or manage records or when users manage tasks in the Task Manager. You can design multiple record view layouts. You can add primary components to layouts to manage records. Add secondary or custom components to display the information related to records, such as matched records and social media feeds.
You can configure actions that users can perform using the record view, such as creating a record or reviewing tasks.
You can design Record View and Review Task, Merge Task, and Unmerge Task layouts. The layout type determines the primary components that you can add to the layout and the actions that users can perform. For example, if you design an Unmerge Task layout, only the primary components that help users to unmerge records are available.
When you design a record view, enable the default record views. Users can manage records using the default record views while you design the custom record views. If enabled, the names of the default record views appear as tabs. After you design custom record views, you can hide the default record views.
When you design a record view, select a template that can display the components that you want. For example, to display data in a record, the template must have a panel that is big enough to display the record details. When users log in to Data Director, layouts that are applicable to their user roles appear in the application.
The following image shows a record view with the Record Details component in the main panel and secondary components that display related information in the sidebar:
The sample record view contains the Record Details component, the Source Systems component, the Similar Records component, and Twitter feed.
If you do not want to design record view layouts, enable the default record views. The default record views contain a primary component, but do not contain any secondary or custom components.

0 COMMENTS

We’d like to hear from you!