Skip to main content

OLIVE Platform Version 1.2.0

Release Date: 29 April 2026

Status: Public Development Release

This is a past release

This page is a record of what changed in OLIVE 1.2.0. It is not documentation for operating 1.2.0.

The rest of this manual documents OLIVE 1.3, and the procedures, values and version tables in it do not apply to 1.2.0. Anything on this page that reads like an instruction — configuration, supported components, environment notes — was true for 1.2.0 at the time and may since have changed.

For the current release see the 1.3.1 release notes, and for the components and versions in it, Platform Technology Overview.

Overview​

OLIVE Platform Version 1.2.0 extends the connector workflow engine with execution control features, improves data orchestration capabilities, and updates documentation systems. This release includes file handling improvements for connectors, and migration of handbook documentation to Markdown-based systems. Infrastructure improvements support horizontal scaling and multi-tenant deployments with custom certificate authority options. The ingress controller has been migrated to Traefik, and operators are advised to switch from NGINX as it is no longer supported. LLM integrations are expanded to include additional providers, and OpenAPI import functionality is introduced for datapoint generation.

Features​

Workflow Engine Enhancements​

Covered most core requirements for workflow-based automation.

Execution Improvements​

Expanded execution capabilities to support advanced workflow control patterns.

Added:

  • Fork with compete property: Control fork now fully supported with the compete property. When set to true, concurrent tasks race against each other with a single winner that sets the composite task's output. When set to false (default), the task returns an array of outputs from each branch, preserving declaration order.
  • Wait states: Workflows can pause or delay execution for a specified duration, enabling time-based logic and coordination between tasks.
  • Timeouts: Configure timeout policies at the workflow or task level to define maximum execution duration after which the execution fails.
  • Try-catch error handling: Workflows can gracefully handle errors with try-catch mechanisms, including error filtering and retry policies for failed tasks.
  • Pause and resume: Workflows can be suspended and later resumed, enabling long-running operations and manual intervention workflows.

Usability Enhancements​

  • Workflow task for setting values now returns outputs, enabling easier chaining.
  • Improved default timeout behavior for more predictable and long-running executions.
  • Ongoing testing and documentation of system limitations for transparency.

Improvements for debugging complex workflows:

  • Adding labels in Temporal UI to identify individual datapoints
  • Adding workflow diagnostic information when executing a workflow with diagnostics option turned on
  • Added possibility to cancel ongoing workflows

Data Orchestrator Improvements​

Integration & Chaining​

Introduced option to return raw results, simplifying:

  • Connector chaining
  • External system integration

Reduces the need for intermediate transformations.

File Handling Enhancements​

Files can now be both provided as inputs to, and generated as outputs from, connectivity elements. Currently, this feature supports files up to a maximum size of 2 MB.

Datapoints:

  • Can return files as outputs
  • Can consume files mid-connector (previous limitation resolved)

Improved handling of large files, increasing stability and performance for high-volume use cases.

Execution Control​

Added pause and resume functionality for connectors:

  • Enables long-running or stateful processes
  • Improves resilience in unstable environments

Support asynchronous connectivity use cases.

Documentation Modernization​

API Documentation​

Upgraded the API documentation to a more modern solution.

  • Provides a significantly improved look and feel.
  • Improves functionality for executing APIs directly from the documentation.
  • Makes API exploration, testing, and onboarding easier for developers.

Handbook Documentation​

Migrated handbook documentation from Confluence to Markdown. Two handbooks are now available:

  • Connectivity Developer Handbook: Provides guidance for developing connectivity applications.
  • Platform Administrator and Operator Handbook: Provides operational guidance for OLIVE Platform administrators and operators.

Both handbooks:

  • Are available as searchable and downloadable HTML packages
  • Are hosted with each OLIVE deployment

Efficiency & Maintainability​

The new handbook documentation setup makes us more efficient by enabling:

  • Easier creation and maintenance of documentation
  • Easier referencing of examples instead of copying them repeatedly
  • Fewer copy-paste errors
  • Better handling of versions
  • Faster and more reliable search
  • Independence from Confluence

Editor & Developer Experience​

Added encryption support for exports:

  • ZIP exports can now be password-protected
  • Protects sensitive data (e.g., authentication credentials)

Introduced OpenAPI import functionality:

  • Automatically generates datapoints and schemas from OpenAPI specifications
  • Example: Full datapoint generation for ADOxx-based APIs

Benefits:

  • Faster setup for integrations
  • Reduced manual effort
  • Lower risk of configuration errors

Usability Improvements​

  • Open edit dialogs in a new window for better workflow
  • Ability to copy element IDs directly

Expanded AI / LLM Integrations​

Added support for a broad range of LLM providers in the prompt datapoint extension:

  • Anthropic
  • AWS Bedrock
  • DeepSeek
  • Google Gemini
  • Groq
  • Mistral
  • Ollama (for self-hosted models)
  • Perplexity
  • AWS SageMaker

Impact:

  • Greater flexibility in AI integration
  • Support for both cloud-based and on-premise AI strategies

Bug Fixes & Incremental Improvements​

  • Upgraded JSONata to the latest version for new features and better performance.
  • Fixed default behavior for:
    • Scheduler
    • Time-to-live (TTL) settings
  • Extended OAuth2 capabilities:
    • Now supports communication with ADOxx-based products
  • And other minor bug fixes

Operation​

Infrastructure Improvements​

Ingress Controller Migration​

Migrated from NGINX Ingress to Traefik Ingress.

  • NGINX Ingress is no longer supported in our setup.
  • Traefik is now the default ingress controller for RKE2, aligning with current platform standards.

Migration Support​

Provided dedicated migration documentation to support a smooth transition from NGINX to Traefik.

  • Covers configuration changes and recommended migration steps.

Scalability & Runtime Improvements​

Horizontal Scaling​

Documented horizontal scaling of key platform components, including:

  • Temporal workers (workflow engine)
  • Data Orchestrator

Enables improved performance and resilience under increased workload.

Multi-Tenant Deployments​

Custom Certificate Authority Support​

Added configuration options in the OLIVE Platform Helm charts to support custom Certificate Authorities (CA).

Easier use of multi-tenant deployment in laboratory setting.

Development Package​

The developer package can be found in: https://gitlab.com/olive6224315/dev-package.git

The package contains the foundational configuration bundle necessary to install or upgrade to OLIVE 1.2.0 as well as the handbooks.

The package is encrypted with the password that was used the last time for the developer package.

A new example has been added to the development package, demonstrating how to use OLIVE within Excel spreadsheets.

Known Issues​

  • When setting up OLIVE, you must import three packages: the foundational OLIVE Connectivity Bundle (OCB), the Connectivity Developer Handbook, and the Platform Administrator and Operator Handbook. This is necessary due to file upload size limitations on the start page, which prevents importing all packages at once.
  • In the connectivity editor, some dialog fields (such as when assigning a tag during OpenAPI import) may lose focus when typing certain characters. Workarounds include pasting the text directly into the field or type without pauses.

Current Status​

AreaStatusNotes
Core ServicesOperationalCore connectivity, orchestration, and template services are available and stable for development use.
MicrofrontendsPartial SupportThe existing microfrontends used in OLIVE use cases are functional. The creation of new microfrontends is supported on a prototypical basis. Future changes are expected, and migrating to them will require manual effort.
SecurityNot yet reviewedA formal security audit has not been completed. Use only in isolated, non-production environments.
Documentation & Training MaterialAvailableComprehensive documentation is provided, including the OLIVE Platform Handbook, and a developer package that includes simple examples and more complex business use case scenarios to support onboarding and practical learning.

Security & Cost Considerations​

Security​

No formal security review has been completed. Assume no privacy or confidentiality when using OLIVE over public networks. Avoid deploying in production or connecting to sensitive environments.

Use only in controlled lab or development setups.

Costs​

Running OLIVE in pay-as-you-go cloud environments (e.g., AWS, Azure, GCP) may incur compute, storage, and networking charges.

We recommend:

  • Setting budget alerts and thresholds
  • Regularly monitoring cloud resource consumption
  • Reviewing connected third-party service usage

Testing & Environment Notes​

Test CategoryStatusRemarks
Unit & API TestsPassedAutomated unit and selected API tests succeeded.
Manual Release TestsPassedBasic manual validation of functionality completed.
Security TestsNot performedSecurity and penetration testing pending.
Performance / Load TestsPartially performedTo be extendend in future releases.

Intended Use​

This release is suitable for development and evaluation purposes.

It allows teams to:

  • Explore and understand core OLIVE connectivity concepts
  • Experiment with connectivity instance management
  • Build and test proof-of-concept integrations

⚠️ Not recommended for production use at this stage.

Service Versions​

Core Services​

Service NameVersion
cloud-function-registry2.1.0
instantiator1.1.0
data-orchestrator3.3.0
file-storage-service1.2.0
import-export1.1.0
landing-service0.2.0
ui-component-registry2.2.0
microfrontend-interpreter2.2.0
editor3.3.0
repository1.4.0
session-memory1.1.0
scheduler1.1.0
template-data-retriever0.1.0

Extension Services​

Service NameVersion
adoxx-embedder1.2.0
agent-caller2.1.0
aws-query-caller1.1.0
cloud-function-executor1.1.0
embed-indexer1.1.0
mcp-server-caller0.1.0
prompt-caller2.1.0
temporal-caller0.1.0
transcript-to-txt0.1.0
vector-service1.1.0
develop-support0.1.0
parse-openapi0.1.0

QA Services​

Service NameVersion
ping1.1.0
simple-adder1.1.0
auth-tester0.0.1

Infrastructure Charts​

Service NameVersion
auth-proxy0.3.3
certificate1.2.3
couchdb1.2.2
keycloak-setup1.1.22
seaweedfs0.1.2
opensearch1.2.2
tenant-setup1.1.0
vault-secrets-setup1.2.0
workflow-engine-postgres0.2.6

Third Party Dependency Versions​

We tested the platform with these third party infrastructure versions:

ComponentVersion
RKE2 Versionv1.33.8+rke2r1
Hashicorp Versionhashicorp/vault:1.18.1
Keycloak Versionkeycloak:26.2.4
ArgoCDquay.io/argoproj/argocd:v2.14.2
CloudNativePG (CNPG) operator1.27.1