> For the complete documentation index, see [llms.txt](https://docs.digibee.com/documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digibee.com/documentation/release-notes/november-2026/november-4.md).

# November 4

## <i class="fa-rocket">:rocket:</i> **Platform Improvements**

### **Assertions on any step and a new Test Case Panel**

Test Cases now let you validate any step of the pipeline and review the results of every Test Case in one place.

* **Assertions on any step:** In the Expected Results section, you can now add assertions to the output of any step, including steps inside For Each, Choice, and Block Execution.
* **No more Partial status:** A Test Case now passes only when all its assertions pass. Test Cases that were Partial now show as Fail.
* **Test Cases in the toolbar:** Test Cases now have their own option in the Design toolbar, on the left side of the Canvas.
* **Test Case Panel:** After a run, a new panel shows every Test Case and which assertions passed or failed.
* **Execution selector:** When you run several Test Cases, choose which execution to inspect in the Execution Panel.
* **Mock step names:** When you mock a response, steps are listed by name, with the connector type below.

<a href="https://docs.digibee.com/documentation/development-cycle/build-overview/canvas/test-cases.md" class="button primary">Explore the Test Cases documentation</a>

![](https://4091659634-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE9x0KHkAmxzJGlYPs9aE%2Fuploads%2F1etgQnwTpsLz7sGqx5kf%2Funknown.png?alt=media\&token=090e5c81-965f-44fc-b519-3b274a151f2b)

### **More run details in the Execution Panel and easier pipeline navigation**

Inspecting runs and navigating your pipeline on the Canvas is now easier.

* **Run status and duration:** The Execution Panel header shows the status of the run and how long it took.
* **Messages tab:** Messages now has its own tab in the Execution Panel, next to Logs.
* **Log severity:** Each log entry shows its severity (Info, Warning, or Error), so you can spot problems faster.
* **Flow Tree and Problems tabs:** Flow Tree and Problems are now separate tabs in the Flow section of the Design toolbar, on the left side of the Canvas. Problems shows how many problems were found in the pipeline. In Flow Tree, clicking a step takes you to it on the Canvas.

<a href="https://docs.digibee.com/documentation/development-cycle/build-overview/canvas/execution-panel.md" class="button primary">See the Execution Panel documentation</a>

### **Size and Pipeline Engine version filters in Run**

You can now filter deployments in Run by Size (Small, Medium, and Large) and by Pipeline Engine version. Both filters accept multiple selections and work in the card and list views. Status also gains the option “Deleting”.

Everything updates instantly, with no need to click Apply, and your selection is saved in the URL: just share the link so someone else opens the list with the same filters.

<a href="https://docs.digibee.com/documentation/development-cycle/overview" class="button primary">Read the Run documentation</a>

![](https://4091659634-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FE9x0KHkAmxzJGlYPs9aE%2Fuploads%2F6DtNejRD75kEwPHThwUH%2Funknown.png?alt=media\&token=723745ec-51f2-4326-9d70-f0ce64f211aa)

### **Alphabetical folder order in Build**

Folders inside a project are now listed in alphabetical order instead of in the order they were created, following the same logic already used for projects and pipelines. This makes folders easier to find, especially in projects with many of them.

New or renamed folders move to their alphabetical position when the list refreshes.

<a href="https://docs.digibee.com/documentation/development-cycle/build-overview/projects.md" class="button primary">Check out the Projects documentation</a>

## <i class="fa-plug">:plug:</i> **Connectors & Triggers**

### **Jack Henry connectors: jXchange and SymXchange**

Two new connectors let your pipelines call Jack Henry's core platforms through their SOAP APIs. The [Jack Henry jXchange](https://docs.digibee.com/documentation/connectors-and-triggers/connectors/financial-services/jack-henry-jxchange.md) connector calls jXchange operations on SilverLake, CIF 20/20, and Core Director, including paginated search operations. The [Jack Henry SymXchange](https://docs.digibee.com/documentation/connectors-and-triggers/connectors/financial-services/jack-henry-symxchange.md) connector calls SymXchange methods on the Symitar core platform and can automatically detect which SymXchange release your host uses.

<a href="https://docs.digibee.com/documentation/connectors-and-triggers/connectors/financial-services" class="button primary">Browse the Jack Henry connectors documentation</a>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.digibee.com/documentation/release-notes/november-2026/november-4.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
