Licensing changed substantially in opscotch 3.1.1.
The licensing model is now hierarchical runtime licensing. Licenses are issued through https://licensing.opscotch.co, can be delegated down a chain of authority, and can be managed without rebuilding packages.
Update for 3.1.6: the previous embedded licensing model has been removed. Use the hierarchical licensing model and the opscotch licensing app for current deployments.
Version 3 of opscotch introduces a small but powerful "preprocessor" called doc for JavaScript processors. The doc functions allow you to add documentation and add programatic declarations of what inputs and outputs your step expects and returns. It's a way to validate and perform type checking, and also declares your expectations to callers.
See the doc documentation here
Prior to version 3.1.0 of opscotch, you could only receive text content from the HTTP trigger i.e. json or text like. Version 3.1.0 now lets workflows receive raw binary uploads. The new context.getStream() call gives you direct access to the byte stream.
Prior to version 3.1.0 of opscotch, payload manipulation was limited to text - you could manipulate that at the byte level in JavaScript but it was very cumbersome and inefficient.
Version 3.1.0 of opscotch adds a ByteContext plus a ByteReader for low-level byte manipulation inside workflows. This is for engineers who already think in buffers, encodings, and compression.
Version 3.1.0 of opscotch adds error-handling helpers to the JavaScript context. You can now flag user-facing errors, capture system errors, and check whether a context (including one returned from sendToStep) is in an error state.
The goal: make signing, encryption, hashing, and random bytes straightforward without leaving JavaScript processors. Version 3.1.0 of opscotch introduces a CryptoContext that brings libsodium-grade primitives into workflows. It works with ByteContext, so everything is buffers (not strings).
Version 3.1.0 of opscotch adds support for HTTP multipart uploads, letting you receive text/JSON and binary content in the same request. This unlocks use cases like “send me the metadata and the file in one hit,” without forcing you to pick one or chain requests. With saftey in mind - this is disabled by default.
Version 3.1.0 adds OpenTelemetry support so opscotch can join your existing traces. Enable it with an environment variable and annotate traces from JavaScript processors.
Version 3.1.0 of opscotch adds two big improvements for handing work to other steps: a new JavascriptStateContext for reading results and errors, and sendToStepAndForget(...) for fire-and-forget concurrency.
In opscotch version 3, file access was introduced, along with the fileWatcher step trigger. File watching is a capability that allows you to request the agent to call a step when a file is changed—for example, when a log file is updated, you can receive the new lines as a step payload. As security is always a top priority, file access is strictly controlled in several ways.