Skip to main content

New Features

View the target state of dynamic search rules

You can now see the state of dynamic search rules as if all pending update tasks had been processed. This helps you understand what changes are coming before they’re fully applied.

New route: GET /dynamic-search-rules/{ruleUid}/target

Returns the target state of a specific rule with:
  • current: the current dynamic search rule object, or null if it doesn’t exist yet
  • target: the fields that will be modified by pending tasks, or null if the rule will be deleted
  • needsProcessing: boolean indicating if pending tasks exist for this rule
  • taskUids: array of pending task IDs for this rule

New parameter: showTarget on POST /dynamic-search-rules

When you set showTarget: true when listing rules, the response includes:
  • Global fields: needsProcessing, taskUids, totalRuleCount, and targetTotalRuleCount
  • Each rule gets a needsProcessing boolean showing if pending tasks apply to it

Example: Creating and checking a new rule

Create a new rule:
Check its target state before processing:
List all rules with target information:
Response includes pending task information for the entire rule set and each individual rule.

Improvements

Resolved a regression where interleaving relevancy and sort rules in federated search would skip alternating rules. Sort ranking rules placed after relevancy rules are now applied correctly. Find more information on GitHub