Version 2.1.0 extends radixAPI with new licensing, workflow, PDF generation, logging, notification, and integration capabilities. The release also improves operational control for running work, strengthens credential handling, and adds clearer feedback channels for connected web applications.
Where available, the notes below also mention whether the feature can be managed or observed in the Radix Backend UI.
Licensing and guarding are now based on the Durst License Manager.
This aligns Service Worker feature access with Durst-managed license data, so available functions can be controlled through licensed permissions and limits.
The API checks licensed routes, workflow access, node permissions, and concurrency values before accepting protected operations.
Backend UI: license details, packages, concurrency values, licensed permissions, expired permissions, and license upload/generation are available in the License views.
Passwords and credentials are stored encrypted in the database.
Stored secrets are protected at rest, reducing the risk of exposing sensitive access data through database access or backups.
S3 credential secret keys and sensitive environment-variable values such as passwords or secrets are encrypted by the API.
Backend UI: credentials and environment variables can be added, edited, listed, searched, and deleted; encryption is handled by the backend.
Created output results are exposed as pURLs for download without authentication.
Workflow outputs can be shared through generated public URLs, which simplifies download flows for external systems and users that should not authenticate against the backend.
Backend UI: workflow results can be inspected through workflow details and the testing UI result view when returned by the backend.
Workflows and processes can be listed, and running processes can be cancelled.
Operators can inspect current and historical execution state and stop work that is no longer needed or should not continue.
The API exposes process abort handling through /api/v1/processes/abort and protects it with workflow licensing.
Backend UI: Workflows and Processes views provide filtering, searching, automatic refresh, workflow-to-process navigation, and process abort actions.
Workflows support a generic pdfToolbox node.
Workflow definitions can now call pdfToolbox as a reusable node type, allowing for all possible pdfToolbox actions.
The node is part of the licensed node set, so it can be enabled or blocked through license permissions.
Server-Sent Events provide direct feedback to web applications.
Web clients can receive live workflow progress events instead of relying only on polling, improving responsiveness for longer-running operations.
The API exposes the stream at /sse/workflow-progress.
Backend UI: the main layout listens to this stream and shows progress notifications with links back to the related workflow or process.
Workflow responses include the new result.severity object.
Consumers can evaluate the severity of a workflow result without parsing tool-specific output, which makes downstream handling and UI feedback more consistent.
URIs in payloads with placeholder are resolved consistently, with an error returned when a referenced URI cannot be found.
This makes missing inputs fail explicitly and helps users detect broken references earlier in a workflow run.
Webhook queueing and DLQ handling have been added.
Failed webhook deliveries can be retained for follow-up handling instead of being lost after delivery errors.
Backend UI: the Webhook DLQ view supports listing, searching, viewing payloads, editing destination URLs, resending, and deleting failed webhook entries.
/marketing/createpdf can use pdfToolbox as the PDF creation engine.
PDF creation can now be routed through pdfToolbox, enabling more consistent processing with existing pdfToolbox-based production flows.
The API supports engine selection for create PDF workflows and can use the configured marketing-createpdf settings.
Incoming files can be named through query parameters on marketing endpoints.
Clients can pass meaningful file names with uploads, making downstream processing, logs, and output packages easier to understand.
The API handles the filename query parameter on several marketing endpoints, including create PDF, quickcheck, fixCheckPreview, saveasimg, jobticket, imageconvert, compare, and ConvertAPI flows.
New marketing endpoint: /marketing/compare.
The compare endpoint adds a backend entry point for comparing PDF files.
The route is backed by the compare workflow spec and the marketing-compare environment-variable service.
For OEM customers only: new marketing endpoint calculateNesting using imposeService 0.0.84.
OEM integrations can calculate nesting data through imposeService, supporting automated imposition-related planning.
ConvertAPI is supported.
This adds an external conversion option for workflows that need ConvertAPI-backed transformations and requires a separate ConvertAPI token from https://www.convertapi.com/.
The API exposes this through /marketing/convertApi and includes convertapi in the licensed node and route set.
Notifications can be sent via email and Slack.
Workflow and system events can be pushed to configured email and Slack channels, improving operational visibility outside the application.
Backend UI: environment-variable service/key options include mailer, slack, email notification, Slack notification, SMTP settings, Slack token, and Slack channel.
OpenSearch can be used as a logging service.
Logs can be written to OpenSearch for centralized search, retention, and operational analysis.
The API can index audit logs to OpenSearch, read workflow logs from OpenSearch, and include OpenSearch in health checks when RADIX_LOG_DRIVER is set accordingly.
Backend UI: workflow logs are available from the Workflows view; OpenSearch service configuration itself is backend-side.
Resulting files can be placed into folders when uploading to S3.
Generated output can be organized in structured S3 paths, making result storage cleaner for customers and integrations.
Backend UI: S3 credentials can be managed in the Credentials view; resource and repository selections are available elsewhere in the UI.
Database and logging entries can be cleaned automatically after a configured retention time.
Retention-based cleanup helps keep database tables and log storage from growing without bound in long-running installations.
The API uses two cron jobs: cleanWorkflows first soft-deletes old workflows, processes, containers, and resources, then cleanDatabase permanently removes expired records, files, archives, custom results, and matching OpenSearch audit-log entries.
The retention behavior is configured with RADIX_CRON_CLEANWORKFLOWS_* and RADIX_CRON_CLEANDATABASE_* environment variables.
@nestjs/throttler with separate global, workflow, and marketing tiers. By default this is 10 requests per 100 seconds globally and 20 requests per 100 seconds for workflow write endpoints and marketing endpoints.RADIX_THROTTLE_LIMIT_* and RADIX_THROTTLE_TTL_* environment variables.pdfToolbox 17.0.683 is supported.
The service worker runs the latest supported pdfToolbox version for PDF processing and workflow node execution.
pdfChip 2.7.101 is supported.
The service worker runs the latest supported pdfChip version for HTML-to-PDF and related rendering workflows.