The rule engine and its steps
You define conditions and a sequence of actions (set a field, create a record, send a notification, block a transition). Rules are tested before rollout, so automation stays predictable.
System features
Low-code and automation - logic that works for you
Where configuration is not enough, rules, scripts and SQL queries take over. You automate decisions and data processing without building a separate system.
In short
The low-code layer in Opero runs logic on events: the rule engine reacts on a “when a condition is met, run these steps” basis, the script engine handles unusual processing, and SQL queries reach for data exactly the way you need it.
What you get
Three layers of logic on your data.
The script engine
Expression and script fragments called from rules, calculated fields and templates, for scenarios beyond visual configuration.
SQL queries
Named, parameterised, reusable queries that feed rules, reports and choice fields.
More about this
Automation that takes over repetitive work.
The low-code layer in Opero automates the work that eats into your team's time today. The rule engine runs on a simple "when a condition is met, run these steps" basis: set a field, create a record, send a notification, block a transition in a process. You define and test rules before rollout, so automation stays predictable rather than risky.
For scenarios that go beyond visual configuration, the script engine takes over. You run expression and script fragments from rules, calculated fields and templates whenever non-standard data processing is needed. That is the low-code part: you reach for code only where it actually pays off, without building a separate system.
SQL queries give you full control over the data. Named, parameterised, reusable queries feed rules, reports and choice fields whenever standard filters are not enough. Together, rules, scripts and SQL turn Opero into a platform that does the repetitive work for you.
Questions
Frequently asked questions.
How does the rule engine work?
A rule is written as "condition, then action". When the condition is met (for example priority changes to critical), the system runs the defined steps, such as setting a field or sending a notification.
Do automations require a developer?
Rules are built visually. Scripts and SQL queries are optional and only become useful for more complex logic.
Related features
See also
Processes and workflowDesign every flow of work as a process. Approvals, document routing and procedures move through defined stages, so nothing gets lost between departments.Reports and analyticsBuild tables, charts and dashboards on live system data. From an aggregate number you can go down to a single record without exporting to a spreadsheet.No-code platformConfigure objects, forms, menus and dashboards visually in Opero.
Next step
Automate the repetitive work.
See how rules and scripts take over the manual steps your team does today.