Organization Wide Search

• Introduction

• How does Organization Wide Search Work?

• Requirements for Organization Wide Search

• Limitations of Organization Wide Search

Introduction

Organization Wide Search on Whatfix DAP on OS enables users to search for content across multiple Enterprises (ENTs) under one organization.

Note:

• DAP on OS needs to be linked to an Organization ID (org_id). To create a new org_id or link the DAP on OS account to an existing org_id, contact support@whatfix.com.

• Organization Wide Search operates based on the org_id. Once connected, all content and users under the same org_id are managed together. This enables users to search for content from various applications, such as Salesforce and ServiceNow, as long as they are mapped to the same org_id.

How does Organization Wide Search Work?

With Organization Wide Search, users can access and search for content across different applications or ENTs mapped to the same org_id. For example, users on DAP on OS can search and access content created on ENT 1 (DAP on Web) and ENT 2 (DAP on Desktop). Content from ENT 1 and ENT 2 shows up in the search results of ENT 3 (DAP on OS).

Requirements for Organization Wide Search:

• The ENTs should be linked to the same org_id.

• Role tag names and conditions (for example, window variable names and values) should be the same across ENTs. Organization Wide Search relies on these tags to identify and display content accurately. The Search Scope for Organization Wide Search can be configured using role tags. Organization Wide Search does not recognize role differences and may fail to show the right content if role tags are not consistent.

Limitations of Organization Wide Search:

• QuickRead does not support Organization Wide Search. It can only provide responses based on content created or repositories integrated on the DAP on OS dashboard.

• Organization Wide Search is not supported in Export Mode of Deployment.