Release v0.7.0 · oracle-samples/node-red-nodes

v0.7.0 - Release Notes

New nodes:

Streaming (oci-streaming-config, oci-streaming-out, oci-streaming-in, oci-streaming-commit): Configure connections, publish messages, consume individual messages or batches, and commit delivery progress automatically or manually.
Managed Kafka (oci-kafka-config, oci-kafka-producer, oci-kafka-consumer, oci-kafka-commit): Connect using TLS/SASL authentication, produce and consume messages, and commit offsets. Batch consumption groups records by partition.
Queue (oci-queue-config, oci-queue-out, oci-queue-in, oci-queue-ack): Publish and receive messages individually or in batches, with long polling and per-message acknowledgement results.
Functions Invoke (oci-functions-invoke): Invoke synchronously to receive the result, or use detached mode to confirm acceptance without waiting for completion.
API Request (oci-api-request): Send signed HTTPS requests to OCI APIs.
Monitoring (oci-monitoring-publish, oci-monitoring-query): Publish custom metrics and query metric data using Monitoring Query Language (MQL).

Transactions now remain available when messages pass through Catch nodes or are cloned.
Database operations within a transaction run sequentially, with coordinated cleanup during timeout or redeploy.
Expired transactions and references belonging to another DB Connection are rejected instead of silently starting separate database work.
A commit requested after a reported database processing error now rolls back and reports DB_TRANSACTION_ROLLBACK_REQUIRED.
Enqueue (enqueue) now uses the configured recipients list.
Continuous Dequeue (dequeue) briefly shows the received message count without pausing consumption.

New examples cover:

Improvements:

Mapped action nodes now accept JSON objects created by Node-RED Function nodes in Message payload mode.
Smart Operations Transformer (smo-transformer) handles incomplete data, timers, and errors more reliably.
The meter-reading example verifies that the asset is missing before creating it; unrelated errors no longer trigger asset creation.
Examples use consistent titles and separate error reporting from successful output.

Database, OCI, and Fusion input-node failures now reach Catch once, rather than producing duplicate error messages.
OCI API-key authentication correctly reads and validates the private-key file.
ORDS timeouts cover the complete response, and polling stops emitting results after redeploy.
Fixed MQTT topic handling, telemetry validation, logging editor settings, and stale node statuses.
Clarified installation, example setup, and IoT Subscribe command delivery.

Flows that match specific node-status text, shapes, or timing may need adjustment.
Smart Operations Transformer now consistently reports failures through msg.error and Catch.