30 Apr Omniscope Rock 2026 Release Candidate Preview

Posted at 12:54h in Announcement, Rock build, Uncategorized by

 

What is changing in the upcoming Rock 2026 edition, what you can try now, and what we recommend checking before adopting the stable Rock build.

Omniscope Rock 2026 is currently in Release Candidate phase, with the Rock release currently targeted for the end of Q2.

This article summarises the main improvements in the upcoming Rock 2026 edition. It is intended for existing customers who want to understand what has changed, explore the new capabilities, and check their own important workflows, reports and deployment setup before adopting the stable Rock build.

Rock 2026 brings together a substantial year of work across:

  1. AI assistants and natural-language data analysis
  2. LLM provider support and model configuration
  3. Data prep and schema drift handling
  4. Conditional flows and data validation
  5. Reporting and visualisation
  6. Workflow automation and scheduling
  7. APIs and integrations
  8. Platform, deployment, administration and security

The strongest concentration of work has been around AI, LLMs and automation, but the release also includes many improvements for report authors, workflow builders, administrators and teams running Omniscope in production.

Candidate builds go through extended testing before becoming Rock stable. During the Release Candidate phase, customers can test the current Candidate build locally with their own projects and data, or use the cloud sandbox for a quicker smoke test.

Is Rock 2026 a migration project?

Rock 2026 is not intended to require a disruptive migration project.

For most customers, it should be treated as a normal major upgrade. Omniscope is designed to maintain compatibility with existing projects, but as with any significant platform release we recommend checking the parts of your own setup that matter most before moving production use across.

The Release Candidate period gives you a safe opportunity to:

  • open key reports
  • run important workflows
  • check scheduled or automated processes
  • verify data connections
  • confirm exports and report output
  • check permissions and viewer behaviour
  • test integrations and API touchpoints
  • explore the newer AI and automation capabilities

The aim is not to test every new feature. The aim is to confirm that your own important usage behaves as expected, while also seeing where the product has moved forward.

Related articles to link from this section

What is new in Omniscope Rock 2026?

1. AI assistants, Insight Explorer and natural-language analysis

Rock 2026 significantly expands the AI layer in Omniscope.

The work covers both user-facing AI assistants and the underlying AI infrastructure needed to support different providers, models, reasoning modes, data-sharing policies and deployment choices.

This includes improvements to:

  • Insight Explorer / Data Q&A
  • Report Ninja
  • AI Insights block
  • AI Request block
  • models and providers configuration
  • OpenAI, Anthropic, Gemini, xAI, OpenRouter and local LLM support

Insight Explorer / Data Q&A

Insight Explorer builds on the earlier Data Q&A work and moves it beyond simple text answers.

Users can ask natural-language questions across report data and receive structured, explainable responses. Instead of only returning a written answer, the assistant can now produce a more interactive result with sections such as:

  • question
  • activity
  • explanation
  • answer

As results stream in, users can see charts, formatted text, intermediate steps and explanations. This makes the process more transparent: the user can inspect how Omniscope queried and analysed the data, rather than receiving a black-box answer.

This is especially useful when viewers or editors want to explore a dataset without building new charts manually, while still being able to verify the answer.

New publisher controls also allow report authors to customise how the experience appears. For example, they can hide or customise sections, adjust styles, tailor the prompt, and define the initial question.

Report Ninja

Report Ninja has been improved so it can configure more of a report and behave better across different model types.

Recent work includes support for:

  • active filters, allowing broader visual exploration
  • report styling and fonts
  • view layout and size awareness
  • additional measure functions
  • top-N bars
  • AI-driven styles by default in new configurations
  • improved handling of mid-conversation changes to report data
  • better behaviour with lower-cost and local models
  • improved support for unconstrained local LLMs

The result is a more capable report assistant. It can help create and refine dashboards while taking more account of the report’s structure, layout, visual styling and current data.

Workflow Ninja

Workflow Ninja is an early AI assistant – which will be improved after this release – for understanding and explaining complex workflows.

It can answer questions about how fields move through a workflow, how blocks transform data, and which blocks are relevant to a particular output. Responses can include diagrams and block links, making it easier to inspect the relevant part of the workflow.

This is useful for onboarding new users, documenting complex projects, troubleshooting data pipelines, or understanding workflows created by someone else.

As mentioned, stay tuned, the Visokio team will focus on this area soon…

AI Insights block

The AI Insights block brings natural-language analysis into the workflow.

Instead of only using AI interactively in a report, workflow builders can generate insight text as part of a repeatable data process. This makes it possible to create pre-calculated commentary, summaries or explanations that can then be used in reports, exports, emails or downstream workflow steps.

The block can answer a single question or process multiple questions from a Requests input. This makes it suitable for repeatable report commentary, automated insight generation and scheduled analysis.

AI Request block

The AI Completion block has been renamed AI Request and redesigned for better usability and consistency with AI Insights.

The block supports several patterns:

  • one request without an input dataset
  • one request per record
  • record-level prompts using fields from the input data
  • optional context datasets
  • whole-dataset analysis using context only
  • structured output and diagnostic options

The optional context dataset is important. It allows the AI request to use supporting data, not just the current record. This expands the block from simple row-by-row text generation into richer analysis, classification, enrichment and dataset-level reasoning.

Thinking and reasoning output

Rock 2026 adds more support for reasoning-style models.

Depending on the provider and model, Omniscope can expose reasoning summaries or thinking output. For OpenAI models using the Responses API, this includes reasoning summaries. For some local models using Chat Completions-compatible APIs, this can include fuller thought-process style output where supported by the model.

There are also controls for thinking level and verbosity, allowing users to adjust model behaviour for different use cases.

AI data-sharing controls

AI integrations now include more detailed controls for what data can be shared with a provider.

Administrators can configure levels of data sharing, ranging from full datasets through to schema-only or no dataset information. This makes it possible to use different policies for different providers. For example, a cloud provider may be limited to schema-only access, while a privately hosted local model may be allowed to process full datasets.

This gives organisations more control over privacy, governance and AI deployment strategy.

AI provider and model support

Rock 2026 substantially expands model-provider support.

Supported or improved providers include:

  • OpenAI
  • Azure OpenAI / AI Foundry-style deployments
  • Anthropic Claude
  • Google Gemini
  • xAI Grok
  • OpenRouter
  • local LLMs
  • llama.cpp
  • vLLM

Recent model support includes OpenAI GPT-5 series models, GPT-OSS open-weight models, Anthropic Claude models, Gemini models and Grok models.

OpenRouter support is especially useful for customers who want access to many different providers and models through a single integration, while still being able to choose the most suitable model for each Omniscope AI feature.

Local model support has also improved, including better support for GPT-OSS models on llama.cpp and vLLM, plus provider options to work around known compatibility issues.

Related articles to link from this section

 

2. Data prep and schema drift handling

Rock 2026 includes important improvements for data precision, schema stability, incremental loading, exports and workflow reliability.

These changes are especially relevant for production workflows where source data may change over time, outputs must remain stable, or small data-format differences matter.

Define Schema and schema drift handling

New schema-related blocks help standardise and stabilise field names and data structure.

The Define Schema block locks a stable output schema by mapping input fields to consistent names and types. It supports aliases and matching rules, helping workflows cope with source systems where field names or structures may change.

This is useful for production workflows where downstream blocks, reports or exports expect a consistent structure.

The Format Field Names block helps rename selected or all fields into a consistent naming style, creating cleaner and more uniform datasets.

Together, these features help reduce the impact of schema drift and make workflow outputs more predictable.

Data Table append modes

The Data Table block has new and improved append behaviours for incremental loading.

These include:

  • append only new rows using record-key checks
  • refill mode based on increasing field values
  • append modes that preserve existing edited data

These are useful for workflows where data is loaded repeatedly from systems that emit new records over time, such as records with increasing timestamps or numeric IDs.

Embedded data sources

The File Source block now supports an Embedded Data File location option.

This allows data sources to be embedded within the project, similar to project attachments. Embedded sources are included in the IOZ file when present.

This is useful for templates, demos, portable projects, controlled file uploads, keeping project folders tidy, hiding uploaded files from directory listings.

When dropping a data file into a project, it is now stored embedded rather than adjacent, helping keep folders cleaner.

Instant Dashboard also uses the embedded data file feature for handling uploaded data files.

Project Path Scanner improvements

The Project Path Scanner block now supports remapping Batch Append folders and Append Files blocks.

This helps when moving projects between environments or updating file/folder paths across projects.

Excel .xls numeric precision

Numeric precision when importing Excel .xls files has been improved.

Values now retain full decimal precision while preserving cell display formats, such as currency or unit prefixes and suffixes. This brings .xls behaviour closer to existing .xlsx behaviour.

Number precision in exports

Number precision has been extended in delimited export and Snowflake bulk export.

This helps preserve data accuracy in exported outputs, especially for workflows involving detailed decimal values or database loading.

Negative number formats

Rock 2026 adds support for custom negative number formats in workflows and reports.

Supported formats include:

  • minus sign, e.g. -123
  • parentheses / accounting format, e.g. (123)
  • debit / credit ledger notation, e.g. DR 123 / CR 123

This is useful for finance, accounting and management reporting.

Parquet and date/time improvements

Support has been improved for:

  • binary fields in Parquet files
  • legacy timestamp formats such as INT96
  • additional date-time patterns for automatic date recognition
  • R and Python Custom Blocks handling milli- and microseconds more predictably

Nondeterministic data diagnostics

Several optimisations reduce repeated data retrieval from upstream sources during workflow execution.

This reduces the likelihood of database query restarts and improves workflow efficiency.

A new opt-in diagnostic check helps identify nondeterminism in workflows, especially where database engines may return records in unstable order unless ordering is explicitly defined.

Related articles to link from this section

3. Conditional Workflow execution, validation and authoring

Rock 2026 introduces a new Control Flow block category and several improvements for building more structured, adaptive workflows.

These changes make it easier to build workflows that branch, validate data, route inputs and outputs, and repeat logic across items.

Control Flow block category

The new Control Flow category includes:

  • If Then Split
  • Input Router
  • Output Router
  • Validate Data
  • For Each

Together, these blocks allow workflow authors to build more adaptive data pipelines.

Instead of every workflow following a single fixed path, workflows can now express logic such as:

  • run this branch only if a condition is met
  • route data to different outputs
  • validate data before continuing
  • halt or divert outputs when checks fail
  • repeat an operation for each item or parameter value

If Then Split

The If Then Split block enables conditional execution.

It is useful when a workflow should take a different path depending on data conditions, parameters or validation outcomes.

For example, a workflow might continue only if input data passes a quality threshold, or run different outputs depending on the selected scenario.

Input Router and Output Router

The Input Router and Output Router blocks provide more control over how data moves through a workflow.

They are useful in projects with multiple inputs, optional inputs, reusable workflow sections or branching outputs.

Validate Data

The Validate Data block supports more formal data validation inside workflows.

It can be used to check whether incoming data meets expected conditions and, depending on configuration, can allow execution to continue, send results to a halted output, or support alerting and notification patterns.

This is important for operational workflows where invalid data should be caught early before it reaches reports, exports or downstream systems.

For Each

The For Each block supports repeated execution patterns.

It can be used where the same workflow logic needs to be applied across multiple values, files, groups, parameters or scenarios.

This helps reduce duplication and makes parameterised processing easier to maintain.

Workflow canvas and block UI improvements

Workflow authoring has also received several usability improvements, including:

  • better canvas positioning when pinning blocks
  • centred pinned blocks without changing zoom scale
  • optional dotted workflow grid visibility
  • a new Input tab on blocks to inspect incoming data
  • UI improvements across workflow and block dialogs
  • preserved layout when copying and pasting multiple blocks, including groups, between projects

These changes are not individually large, but together they make complex workflow building easier to navigate, document and maintain.

Related articles to link from this section

4. Microsoft 365 and email integration

Rock 2026 adds Microsoft 365 support for both workflow email delivery and Scheduler emails.

This is important because many organisations are moving away from basic SMTP authentication and towards Microsoft Graph-based application authentication.

Microsoft 365 email delivery for workflows

Workflow email delivery can now use Microsoft 365.

Email delivery settings are configured centrally in:

Admin > Email Delivery

A new Mail server type option allows administrators to choose between:

  • SMTP
  • Microsoft 365

SMTP configuration remains unchanged. Microsoft 365 uses Microsoft Graph with app-only authentication using the client credentials flow.

Once configured, these settings are used by workflow blocks that send email, including Email Output and Validate Data blocks.

Microsoft 365 support for Scheduler emails

The Scheduler Send email action now includes an option to use the mail server configured in Admin > Email Delivery.

This allows Scheduler emails to be sent using either SMTP or Microsoft 365, depending on the configured mail server type.

This is useful for scheduled notifications, alerts, report distribution and automated operational emails.

Microsoft 365 connector block

Rock 2026 also adds a Microsoft 365 connector block focused initially on Mail.

The connector supports reading email messages from Microsoft 365 using Microsoft Graph and app-only authentication.

It supports:

  • Tenant ID, Client ID and Client Secret configuration
  • target mailbox configuration using Mailbox UPN
  • mailbox folder selection
  • filtering by date, subject and sender
  • attachment metadata fields
  • attachment counts
  • downloading file attachments to a chosen folder
  • filename filtering
  • overwrite control

This initial release focuses on Mail. Additional Microsoft 365 services, such as Contacts, Calendar, OneDrive and SharePoint, will be added in future based on demand.

Related articles to link from this section

5. Reporting, visualisation and report authoring

Rock 2026 includes a large number of reporting and visualisation improvements.

These changes give report authors more control over report presentation, image export, view behaviour, styling, saved states, network visualisation and data visibility.

Saved Explorations

Saved Explorations allow report viewers to save and return to a particular exploration state.

This can include filters, selections and variable states. Viewers can return to the same state later without keeping the browser tab open, and can share saved states by link.

This is useful when users want to preserve a particular finding, collaborate on a view of the data, or return to an analysis state after further investigation.

Live query formula functions

New live query formula functions have been added, including: DATE, DATEUNIT, DATETRUNC, ABS, MOD, POWER, INTCEIL, INTFLOOR, LEN, UPPER, LOWER

SUBSET functions are also now fully supported, including expressions such as:

SUBSET_SUM([Price], SUBSET([Category]))

This expands what can be calculated in live query contexts, subject to the performance of the underlying database engine.

Image export for all report views

Image export in reports has been improved substantially.

All view types are now supported, including:

  • Map
  • Table
  • Pivot
  • Pictorial
  • Tree
  • other standard report views

Image export also works when a view is paned or tiled. Entire report tabs can now be exported as images.

This makes it easier to reuse Omniscope report output in presentations, documents, emails, PowerPoint decks and operational packs.

Network view suite

Rock 2026 introduces and improves a suite of network-based views.

This includes:

  • Network View
  • Tree View
  • Sunburst View
  • related network-based visualisations such as Sankey and Dependency Wheel

The new Network View is designed for visualising relationships, structures and connectivity. It supports both grouped and linked network types, allowing users to model entities and connections in different ways.

Layout options include Spring, Balloon, Tree, Circle, Grid, Spiral, Manual

This makes the view suitable for use cases such as social networks, process flows, organisational structures, product relationships, handoffs, journeys and dependency maps.

The Tree and Sunburst views now share more of the same network framework. Users can switch between compatible network-based views while retaining the underlying structure.

Recent improvements include:

  • rectangle selection in Network and Tree views
  • colour ramp by level options
  • node label measure configuration
  • automatic population of linked network from/to fields where possible
  • warnings when Tree or Sunburst views detect non-hierarchical network structures
  • Sunburst migration to the network framework and removal of the experimental tag

Pictorial view

The Pictorial view visualises data using repeated or stacked images.

This is useful for story-driven reporting, public-facing dashboards or situations where visual metaphors communicate values more clearly than a conventional bar or table.

Recent improvements include:

  • label options above or inside images
  • image export support
  • better report integration

Measure Colouring Framework

Custom measure colouring gives report authors more precise control over how colours are applied inside a view.

Instead of relying only on field settings and report style, authors can configure colour behaviour for measures directly.

Supported approaches include:

  • Fit to Data
  • Fixed colour points
  • Category-based colours

In the Pivot view, when paning by measures, colours can be applied relative to measure values so that each cell’s colour reflects its associated measure.

View configuration and branding defaults

Branding can now store View Configurations.

This means branding presets can define not only colours, fonts and themes, but also how new views behave by default.

For example, an organisation can define defaults such as:

  • rounded bars
  • hidden gridlines
  • line chart styles
  • table styling
  • filter behaviour
  • preferred chart options

This helps teams maintain consistent report styling without manually reconfiguring each new view.

Advanced layout and styling controls

Rock 2026 adds more styling control at view level.

Recent additions include:

  • view margins on all sides
  • negative view margins
  • per-side border width
  • corner radius options
  • content padding
  • view shadow styling
  • report page background bleed
  • collapsed page spacing in view mode
  • improved Explore mode styling
  • view toolbar improvements
  • option to hide device title and toolbar in Filters view

These options allow report authors to create more polished layouts and visually join multiple views so they appear as a shared panel.

Charting engine update

The charting engine powering many Omniscope views has been updated.

This brings a range of enhancements, bug fixes and performance improvements. Existing chart appearances are intended to be preserved where possible, although subtle visual differences may be visible.

Other chart and view improvements include:

  • Bar view maximum-bars-before-load-more option when multiple splits are configured
  • Bar view corner radius
  • improved axis label behaviour, including max width, auto-rotation and staggered labels
  • label contrast options in Comparison Bar
  • Waterfall colour-by-split option
  • Scatter and Line marker hover reveal modes
  • Table image alignment option
  • Table view disable viewer sorting option
  • Blank view

Content view link target

The Content view now has a This frame link target option.

This allows links to open in the current frame, alongside the existing options to open in the current tab or a new tab.

This is useful when embedding content or building report navigation experiences where links should remain inside the same report frame.

Related articles to link from this section

6. Automation, Scheduler and project execution

Rock 2026 includes important improvements for automating Omniscope projects and workflows.

The main direction is to make automation easier to configure from inside projects, more flexible to trigger, and more suitable for operational use.

Project Automations

Project Automations allow an Omniscope project to run by itself on a schedule.

Instead of configuring everything separately in the Scheduler app, users can configure automation directly from the project menu. Depending on licence and configuration, this can be used to refresh reports or execute selected workflow blocks.

This is useful for:

  • refreshing dashboards before users arrive
  • updating reports after nightly data loads
  • running preparation blocks at off-peak times
  • sending scheduled outputs
  • automating routine data workflows without opening the project manually

Scheduler Basic supports report auto-refresh. Scheduler Pro supports both report refresh and selected workflow block execution.

Scheduled execution of workflow blocks

Scheduler Pro now supports scheduled execution of workflow blocks directly from inside the Workflow app.

This is available from the workflow block menu under Automation. It allows automation to go beyond report refresh and into workflow processing, such as running import, preparation, validation, export or email-output blocks.

This makes scheduled automation more accessible to workflow authors and reduces the need to build everything manually in the Scheduler app.

Ad hoc execution powered by the Scheduler API

The Scheduler app’s Execute / Play action is now a full ad hoc execution.

This means a task can be started on demand and run in the background without blocking other users. This is useful when a user needs to trigger an execution immediately, but the task may take time and should not monopolise the UI.

Scheduler API and third-party automation

The Scheduler API, Workflow API and Project API continue to form the automation API family in Omniscope.

Together, these APIs allow external systems to:

  • trigger workflows
  • execute scheduler tasks
  • update project parameters
  • create projects from templates
  • upload files into project-creation flows
  • monitor execution state
  • integrate Omniscope with external platforms

This is relevant for customers who want to integrate Omniscope with orchestration tools, portals, internal systems or third-party automation services.

Project API embedandcreate endpoint

A new embedandcreate endpoint has been added to the Project API.

This allows an external process to upload a file, embed it inside the project, and create the project from a template at the same time.

This is useful for self-service or template-driven workflows, where a user or external system submits a file and Omniscope creates a ready-to-use project around it.

Related articles to link from this section

7. APIs, integrations and external access

Rock 2026 improves the way Omniscope can be connected into a wider technology stack.

This includes improvements to API documentation, Project API capabilities, Scheduler execution, JDBC configuration and Query API use cases.

New API documentation interface

The Omniscope API page now has a new interface available from:

Admin App > API Documentation

This makes it easier for administrators and developers to explore the available APIs and understand how they fit together.

Automation API family

The main automation APIs include:

  • Workflow REST API
  • Project REST API
  • Scheduler REST API

These allow external systems to trigger workflows, create projects from templates, execute scheduler tasks, pass parameters and monitor execution.

Query API

The Query API allows external systems and custom views to query data behind reports and receive structured JSON.

This can be used to:

  • replace CSV exports with API endpoints
  • build client-side applications
  • feed external systems with filtered or aggregated Omniscope data
  • expose report data in a more controlled, programmable form
  • combine report data querying with workflow or scheduler execution

JDBC and database connectivity

JDBC additional parameter options are now parameterisable in blocks.

This makes it easier to build reusable database configurations where connection details, parameters or environment-specific values need to change without duplicating projects.

Database driver administration has been improved, including support for bundling or uploading multiple drivers for a single database vendor and improved handling of uploaded driver deletion where JARs are in use.

Windows network path support

Support for Windows network UNC paths, such as \\server\share, has been improved.

Browsing into subfolders and selecting files from network locations now works more reliably.

Related articles to link from this section

8. Platform, deployment and administration

Rock 2026 includes improvements for customers running Omniscope in server, multi-user, containerised or production environments.

In-memory workflow execution mode

A new optional in-memory workflow execution mode allows transformations and report publishing to run entirely in RAM.

This can provide very fast processing when projects fit in memory and can also support deployments without local disk storage.

It is useful for:

  • lightweight execution nodes
  • containerised deployments
  • burst processing
  • dedicated execution machines
  • environments focused on execution performance

Multi-node and viewer-node reliability

Reliability has been improved for multi-node setups, including shared-drive and Docker deployments.

This makes report-serving “viewer” nodes work more consistently alongside execution nodes.

This is particularly relevant for deployments that separate report viewing from workflow execution, or where Omniscope is being run across multiple server processes or container nodes.

Docker deployment

Docker deployment support has continued to improve.

This is relevant for organisations that want repeatable deployments, containerised infrastructure, orchestration through Kubernetes, or separation between execution and report-serving environments.

Web Access admin dashboard

The Web Access admin dashboard has been updated.

This improves the administrative experience for managing access and web-facing behaviour.

Usage tracking and interaction tracking

Usage tracking and analytics options continue to improve, including options to link Google Analytics tracking to OpenID custom claims and enable debug mode.

This can help administrators understand adoption, usage patterns and report access behaviour.

Log file rotation

Log file rotation now uses Linux-style numbering, where .1 is the newest rotated file.

This makes log handling more consistent for administrators familiar with Linux server conventions.

Related articles to link from this section

9. Permissions, editing and governance

Rock 2026 adds more granular controls for editing, data visibility and governed report usage.

Field editing restrictions

Fields can now be restricted to allowed values.

Restrictions can be based on:

  • Custom Values: a predefined list of allowed values
  • Field Values: a dynamic lookup of values from another data source field

Field Values also support hierarchies. For example:

Category > Sub-category > Product

When a higher-level value is selected, lower-level options are filtered automatically.

Editing restrictions apply in both the Table and Editable Table views. This makes editable reports safer and more controlled, especially where users should choose from approved values rather than entering free text.

Hierarchy-aware editing restrictions

Hierarchy-aware restrictions make editing more context-sensitive.

For example, users selecting a country could then see only valid regions, resorts or products associated with that country.

This is useful for data-entry workflows, operational updates, reference-data maintenance and governed self-service editing.

Per-view data export control

The new per-view Disable export and show data option gives report publishers more control over where users can inspect or download data.

This complements existing report-level and permission-level controls.

File upload permissions

It is now possible to disable file uploads on a per-folder basis.

This gives administrators more control over where users can upload files and supports more governed folder structures.

Password handling in IOZ files

Passwords can now be included in IOZ files, preserved and encrypted on import/export.

This can simplify some project transfer or backup scenarios while keeping credentials encrypted.

Related articles to link from this section

Recommended checks during the Release Candidate phase

Rock 2026 is not expected to require a disruptive migration, but we recommend customers use the Release Candidate period to validate the areas that matter most to their own setup.

For customers with limited time, focus on the workflows, reports and integrations that would cause the most disruption if they behaved unexpectedly.

Suggested validation checklist

 

Reports

Check that:

  • key reports open successfully
  • filters, selections and variables behave as expected
  • important charts still look correct
  • saved report states behave as expected
  • viewer users can access reports as intended
  • image export works where used
  • data export and show-data behaviour matches your sharing policy

 

Workflows

Check that:

  • important workflows execute successfully
  • source blocks connect to the expected data
  • key transformation outputs match expectations
  • validation steps behave correctly
  • data tables and append modes behave as expected
  • workflows using file paths, network paths or embedded files still work

 

Automation

Check that:

  • project automations run on schedule
  • Scheduler tasks can be executed
  • ad hoc execution behaves as expected
  • scheduled emails are delivered
  • API-triggered workflows or scheduler jobs still work

 

Integrations

Check that:

  • database connections work
  • JDBC parameters and drivers behave as expected
  • Connector settings work, where used
  • external API integrations still authenticate and execute
  • Project API, Workflow API, Scheduler API or Query API calls work where relevant

 

Administration and deployment

Check that:

  • user permissions behave as expected
  • viewer users remain view-only
  • folder upload permissions are correct
  • server logs and diagnostics are available
  • Docker or multi-node deployments behave as expected
  • report-serving nodes work correctly if used

Features worth exploring during the RC phase

In addition to checking existing projects, Rock 2026 is a good opportunity to explore newer capabilities that may simplify how your team works.

Areas worth trying include:

  • Insight Explorer / Data Q&A
  • Report Ninja
  • AI Insights block
  • AI Request block
  • Workflow Ninja
  • Local LLMs support
  • Project Automations
  • Control Flow blocks
  • Define Schema and Format Field Names
  • Saved Explorations
  • Network, Tree, Pictorial and Sunburst views
  • Field Editing restrictions

Release Candidate availability

The current Release Candidate build is available for early review and local testing.

Customers can use the Candidate build to test Omniscope with their own projects, data and workflows before the stable Rock build is released.

A cloud sandbox is also available for customers who want a quicker smoke test or an initial look at the new capabilities without setting up a local installation.

During the Release Candidate phase, builds may be updated as issues are resolved and final improvements are made. Customers testing the RC should use the latest available Candidate build.

Summary

Omniscope Rock 2026 is a major product edition with substantial improvements across AI, automation, workflows, reporting, data infrastructure, integrations, APIs and platform administration.

The biggest changes are around AI-assisted analysis, LLM provider support, automation and workflow execution, but the release also includes many practical improvements for report authors, workflow builders and administrators.

Rock 2026 is not intended to be a disruptive migration project. However, as with any major upgrade, customers are encouraged to validate their own important reports, workflows, scheduled jobs, integrations and deployment setup during the Release Candidate phase.

This gives teams a safe way to confirm existing usage, explore the newer capabilities, and prepare for the stable Rock 2026 release.

Print page
No Comments

Leave a Reply

Discover more from Visokio

Subscribe now to keep reading and get access to the full archive.

Continue reading