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

DaaS Providers

DaaS Providers

Communication with a DaaS provider is through SOAP requests and responses. Send a request to the DaaS provider with the minimum required information about a business entity. The DaaS provider responds with information that you can use to expand the business entity view and enrich the business entity data.
You must configure a DaaS provider as an extension in the Provisioning tool. A DaaS provider configuration combines a web service call with business entity to XML format and XML format to business entity transformations. You must specify the metadata, such as required fields and the type of service, such as READ or SEARCH.
For example, if you specify the name of an organization, the DaaS service searches for the name and returns a list of records with matching names. If you specify a unique value, such as the D-U-N-S number, the DaaS service performs a direct match, and returns the details of the organization. You can configure multiple DaaS providers.
Every DaaS provider must have at least one required field. Specify the required fields when you configure a DaaS provider.
Communication with a DaaS service is through the DaaS component that you add to a record view layout.

0 COMMENTS

We’d like to hear from you!