Saved search requests are predefined named queries which can be executed at any moment. Users specify such queries by themselves and users with admin authorities can share it for other users within tenant.

Saved search requests are characterized by following fields:

• name
• description
• query- valid Reltio search query string. Examples:

  • equals(relevanceScores.matchRule, 'configuration/entityTypes/HCP1/matchGroups/PotentialMatchByEmail')

  • equals(relevanceScores.matchRule, 'configuration/entityTypes/HCP1/matchGroups/PotentialMatchByEmail')

  • inSameAttributeValue(equals(relevanceScores.matchRule, 'configuration/entityTypes/HCP1/matchGroups/PotentialMatchByEmail') and gt(relevanceScores.relevance, 0.8))

  • gt(relevanceScores.relevance, 0.8)

  • lte(relevanceScores.relevance, 1.0)

  • equals(relevanceScores.relevance, 0.75)

  • range(relevanceScores.relevance, 0.8, 1.0)

  • equals(relevanceScores.actionLabel, 'candidate for merge')

  • inSameAttributeValue(equals(relevanceScores.actionLabel, 'candidate for merge') and equals(relevanceScores.matchRule, 'configuration/entityTypes/HCP1/matchGroups/PotentialMatchByEmail'))

• count- quantity of profiles found by the Query
• isFavorite- flag designed for filtering (true/false)
• isPublic- flag that specifies whether other users in this tenant can use this request (in read only mode). This field makes sense for administrators only (ROLE_ADMIN & ROLE_ADMIN_<tenant>). For other users this field will be always set to false regardless of what value has been sent.
• uiState- valid JSON, which intended to keep state of visual controls for query editing.
• owner
• createDate
• updateDate