Flows that think along
pronubes Version 1.5
More logic, less effort, higher security
In production, things rarely go exactly to plan. Systems drop out briefly, data changes only occasionally, and the same process is maintained slightly differently in ten places. That costs time, creates unnecessary data volumes and makes your IT/OT landscape harder to manage.
Version 1.4 brought more transparency with AuditLog and REST Tunneling. pronubes 1.5 takes the next step: your data flows now make their own decisions, handle errors in a controlled way and transmit only what is really relevant.
The logic update
Intelligence directly in the data flow
At the heart of 1.5 are four new building blocks. They move logic to where it belongs: into the data flow itself rather than into additional scripts or workarounds.
Variables
Order, security and key figures at the push of a button
As projects grow, so does the number of variables. Version 1.5 keeps this manageable.
Central certificate management
Consistent security standards across all sites
Secure OPC UA connections need certificates, and until now they had to be maintained separately at every installation. From 1.5, your IT can issue, renew and revoke them for all installations via a central server (OPC UA GDS).
More highlights
Less preparation, more targeted use of resources
Besides the major topics, 1.5 includes several features that noticeably ease day-to-day work.
More transparency and stability in operation
A clear focus on day-to-day operations
Besides the new features, there was a clear focus on day-to-day operations.
Security: proactively up to date
Security is part of the design
With 1.5 we updated several third-party components for which security advisories (CVEs) have been published. Our review shows that pronubes Edge in its default configuration is not practically affected by any of these vulnerabilities. We close them consistently anyway, because for us security is not an afterthought but part of the design.
Update with a safety net
What changes with the update – and what does not
In short: your existing installations keep running as before after the update. New behavior applies where you switch it on. Two exceptions are worth a look: the service works faster under load, and deleted Edge instances lose remote access immediately.
Logic belongs in the data flow, not in additional scripts.
Talk to us about how pronubes 1.5 can be used in your production.
FAQs
What is new in pronubes 1.5?
At its core are four building blocks for logic in the data flow: conditions (IF), functions (FX), error handling (Try/Catch) and the Change Gate. In addition there are a folder structure for variables, protected credentials, key figures instead of raw data and scalable flows.
What are conditions (IF) used for in a flow?
A single flow can branch differently depending on the situation instead of needing a separate flow for every case. This keeps flows clearer and easier for colleagues to follow.
Do flows change automatically when a function (FX) is modified?
No. A flow only uses the new version of a function once you deliberately republish it. This keeps it clear which version is running in production.
What happens if a target system is briefly unavailable?
With error handling, the flow detects the error, can retry the operation automatically and reports the problem in a targeted way instead of simply aborting.
What does the Change Gate do?
Data is only passed on when a relevant change occurs. You define what counts as relevant. This relieves databases, networks and cloud storage and lowers costs.
