November 4
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.

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.
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.

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.
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 connector calls jXchange operations on SilverLake, CIF 20/20, and Core Director, including paginated search operations. The Jack Henry SymXchange connector calls SymXchange methods on the Symitar core platform and can automatically detect which SymXchange release your host uses.
Last updated
Was this helpful?