# December 2025 Release Notes

## GRAX Product Updates

### December 2025

December brought a meaningful behavioral change to Search, with AND logic now the default for multi-condition queries, as well as a set of improvements to the restore experience, activity management, and general interface usability. Several smaller refinements across navigation, progress visibility, and layout round out a productive end to the year.

***

### Backup & Restore

#### Point-in-Time Now Applies to Automatic Activities

**What Changed:** Point-in-time context is now threaded through to automatic backup activities, ensuring they operate within the intended time scope when a point-in-time is set.

**Why This Matters:** Automatic activities can now be scoped to a specific point in time, giving you more precise control over what data those activities act on. This is particularly relevant when running targeted restores alongside automated workflows.

***

#### Restore Compare View Sorts Fields by Restorability

**What Changed:** In the field comparison view during a restore, fields are now sorted with restorable fields listed first, followed by the remaining fields in alphabetical order.

**Why This Matters:** The most actionable information is now at the top. When reviewing a restore, you see the fields you can actually update first, rather than having to scan through the full list to find them.

***

### Search

#### Search Now Defaults to AND Logic

**What Changed:** New searches now use AND logic by default, meaning all conditions in the search must be satisfied for a record to appear in the results. Previously, the default was OR logic.

**Why This Matters:** AND logic is more precise and aligns with how most searches are actually intended to work. If you are searching for records that meet multiple criteria simultaneously, you no longer need to manually switch the logic mode. Existing saved searches and templates are not affected by this change.

***

#### Created At Filter Hidden When Field Is Not Present

**What Changed:** The "Created At" filter option in Search is now hidden for object types that do not include a CreatedDate field.

**Why This Matters:** Showing this filter for objects where it has no effect caused confusion and could lead to searches that produced unexpected results. The filter now appears only where it is relevant.

***

#### Search Progress Indicator Refreshed

**What Changed:** The search progress indicator has been updated with a clearer visual design that better communicates how a search is advancing toward completion.

**Why This Matters:** The previous indicator gave limited feedback during longer searches. The updated design makes it easier to read at a glance and reduces uncertainty about whether a search is still running.

***

### User Interface

#### Child Emails Now Support Deep Linking

**What Changed:** You can now open a specific child email directly by including its identifier as a URL parameter. Sharing or bookmarking a link takes the recipient straight to that email thread within the record.

**Why This Matters:** When collaborating on a record review or escalating an issue, you can now point someone to the exact email you are referencing rather than asking them to navigate to it manually.

***

#### Object Options Load Progressively for Large Activities

**What Changed:** For activities with more than 1,000 phases, the Object Options section now loads progressively rather than waiting to load everything at once before displaying.

**Why This Matters:** Large activities would previously cause a noticeable delay before the Object Options section became usable. Progressive loading keeps the interface responsive and lets you start reviewing options while the rest continues to load.

***

#### Improved SSO Error Messaging for Insufficient Permissions

**What Changed:** When a user attempts to log in via SSO without the required permissions, the error message now clearly identifies what permission is missing and what needs to happen for access to be granted.

**Why This Matters:** Vague SSO errors slow down onboarding and IT support. A specific, actionable message gets users to the right person faster and reduces back-and-forth between users and administrators.

***

### How to Get the Most from These Updates

**Review your saved search configurations.** The new default of AND logic applies to searches created going forward. If you have team members building new searches, let them know that multi-condition searches now work as AND by default, which may be a welcome change or one worth explaining depending on their use case.

**Use the new deep link capability for email threads.** If your team does record reviews in GRAX and references specific emails, you can now share a direct link to the thread. This works especially well in combination with Search to surface the record and then navigate directly to the relevant communication.

**Check your large activities.** If you manage activities with many phases, Object Options now loads progressively. The experience for large activity configurations should feel noticeably more responsive.

***

### Questions or Feedback?

Reach out to your GRAX Customer Success contact or visit our support portal for help with any of these updates.

***

*December 2025*


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://documentation.grax.com/notices/release-notes/december-2025-release-notes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
