IFS Cloud architecture · Custom Events and Workflows
Execute Online SQL event actions are deprecated in IFS Cloud, so each one you keep is debt you carry into every update
An event action of type Execute Online SQL runs a SQL statement in the database whenever the event fires, and IFS marks that action type as deprecated in IFS Cloud. The in-platform alternative is the Workflow action type, which starts a pre-defined workflow in the embedded Camunda engine. This article shows how to sort your existing event actions, which target each one should move to, and where workflows themselves create new debt.
Key takeaways
- The IFS Cloud documentation for Manage Event Actions states that the Execute Online SQL action type is deprecated, and lists Workflow as the action type that calls the embedded Camunda workflow engine.
- The SQL in an event action is text stored in configuration. Nothing compiles it against the next release, so a changed method or column surfaces only when a user triggers the event.
- IFS Cloud ships Release Updates twice a year and Service Updates monthly, and IFS guidance is to minimize tailorings and in particular customizations. Every event action with SQL is part of what you retest at each update.
- Each event action gets its own decision: configuration, a Workflow whose timing fits how the record is changed (a change made by direct SQL or a background job starts a workflow only through an event action with Asynchronous timing), an integration outside IFS through the APIs, or a documented customization with a named owner.
An IFS Cloud solution can look clean in the extension list and still carry SQL statements in event actions, because event actions are configuration and nobody counts them as code. That is where the architectural debt hides. It costs nothing on the day the event action is created and it costs retesting, or an incident, at every Release Update after that.
1.Why an Execute Online SQL event action becomes architectural debt
An Execute Online SQL event action is a SQL statement that IFS Cloud runs in the current database when a custom event fires. The Manage Event Actions documentation describes it as intended to execute a method, an UPDATE or an INSERT, not to return any values, and states that the action type is deprecated in IFS Cloud.
Three properties turn an Execute Online SQL event action into debt:
- It is invisible to the build. The statement lives in the event action, not in the delivered solution, so a code review of your customizations does not see it.
- It depends on internals you do not own. The statement calls IFS methods or writes to tables whose structure IFS can change in a Release Update. The failure appears at runtime, on the user's save.
- It runs inside the business transaction. A slow or failing statement blocks or rolls back the user's own change, and the database error the user sees does not say which business rule failed.
The IFS Cloud Fundamentals page sets the frame: Service Updates are monthly cumulative sets of high severity fixes, Release Updates are twice-yearly updates with new functionality, and the guidance is to minimize tailorings and in particular customizations. An event action with SQL is a customization in effect, even though it is entered as configuration. The broader cost of carrying such objects is described in The True Cost of Customization in IFS Cloud.
2.What changes when the logic moves to a Workflow
A Workflow in IFS Cloud is a BPMN process that runs in the Camunda workflow engine in the middle tier and works through projections, the endpoints the OData provider exposes. According to the What are Workflows documentation, a workflow is invoked from a projection action, from an event action or from a workflow command.
The timing you choose decides the transaction behaviour, so it is the first design decision for each converted event action.
| Timing | When it runs | Transaction | Typical use |
|---|---|---|---|
| Before | Before the projection action | Same transaction as the user's change | Validation that must pass for the save to succeed, enrichment of values before they are stored |
| After | Immediately after the projection action | Same transaction as the user's change | Follow-up changes that must commit together with the original record, when the change comes through a projection action; an event action with After timing does not start the workflow for changes made by direct SQL or a background job |
| Asynchronous | Picked up by a listener in the background | Separate transaction in a separate thread | Notifications, calls to external systems, anything the user should not wait for |
A Before or After workflow that fails rolls back the user's change, while an Asynchronous workflow cannot stop the save. If an exception occurs during a Before or After workflow, the entire transaction rolls back and the user sees an error, so the workflow has to return a message the user can act on. An Asynchronous workflow cannot stop the save, so it suits work that may fail and be retried. The User Interaction workflow type is supported only when the workflow is invoked from a projection action. The 25R1 Workflow FAQ adds a limit that matters when converting event actions: when a record is changed by direct SQL or a background job, a workflow is triggered only by a Workflow type event action with Asynchronous timing, and with After timing it is not triggered.
The difference from the SQL statement is that the workflow calls projections, the same API layer IFS maintains for its own clients, instead of database internals. That does not make a workflow free of maintenance, but it moves the dependency from database internals to the API layer that IFS publishes for its own clients and integrations. The extension model behind this is set out in Update-Safe IFS Cloud Extensions.
3.How to decide the target for each event action
Converting event actions starts with an inventory, not with the Workflow Designer, because a part of the SQL statements should not become workflows at all. The Fundamentals page names three ways to tailor IFS Cloud: Configure, Extend on the inside (Customize) and Extend on the outside. Each event action is sorted into one of them, or retired.
- List every event action of type Execute Online SQL with its event, the business object and the person who asked for it. Event actions without an owner are the first candidates for removal.
- Write down what each statement does in business terms: sets a default, blocks an invalid value, changes a status, informs someone or sends data out. The technical SQL matters less than this sentence.
- Check standard and configuration first. A statement that duplicates standard behaviour is deleted rather than converted, and page behaviour such as hiding or arranging fields belongs in configuration with Page Designer, not in SQL.
- Move process logic to a Workflow: validation and enrichment with Before timing, follow-up updates with After timing, notifications and outbound calls with Asynchronous timing. Check first how the record is changed: if the event also fires on changes made by direct SQL or a background job, only an event action with Asynchronous timing starts the workflow, as stated in the Workflow FAQ, so Before or After logic would be skipped for those changes.
- Move integration logic outside IFS when the statement exists only to feed another system. An external platform reading through the IFS Cloud APIs keeps that logic out of the business transaction.
- Keep the rest as a documented customization. Some PL/SQL logic has no workflow equivalent. It then belongs in the customer solution built with IFS Developer Studio, under version control and with a named owner, not in a text field of an event action.
The order matters. Opening the Workflow Designer first leads to converting every statement one to one, which moves the same debt to a new place.
4.Where workflows create new debt
A workflow built like a PL/SQL procedure carries the same risk as the event action it replaced, only drawn as a BPMN diagram. Four patterns are worth checking in every design review:
- Loops over large volumes inside the workflow. Processing thousands of lines in the engine belongs in a projection action or a batch process; the workflow should govern the process, not carry the data.
- Synchronous calls to external systems. A Before or After workflow that waits for another system makes the user's save depend on that system. Outbound calls go Asynchronous.
- Bypassing standard validation. A workflow that pushes data past a check IFS performs on purpose recreates the problem of direct database writes through the API layer.
- Diagrams that nobody can read. When a workflow needs a long explanation, split it into smaller workflows with one purpose each, so that the next consultant can trace a stalled approval to one step.
Every workflow also needs the same register entry as any other extension: what it does, who owns it and how it is tested after a Release Update.
5.How event action debt shows up in a project review
In my project reviews, event actions with SQL show up first through their symptoms: a save that fails only for certain records, a status that changes without a visible reason, or a defect that returns after each update under a new ticket number. The review traces each symptom back to an object and adds the object to the extension register with a decision from section 3.
When the project is already in trouble, this inventory is one part of the modifications and extensions area of a wider diagnostic, described in IFS Cloud Implementation Rescue. Failures that appear only after an update are covered in Silent Custom Code Failure After an IFS Cloud Upgrade, and the choice between quick reports, custom fields and custom events in IFS Quick Reports vs Custom Fields vs Custom Events.
6.Frequently asked questions
Is Execute Online SQL still supported in IFS Cloud?
The Execute Online SQL event action type is marked as deprecated in the IFS Cloud documentation for Manage Event Actions. New logic should not be built on a deprecated action type, and existing statements should be moved to configuration, a Workflow, an external integration or a documented customization.
Can every Execute Online SQL event action be replaced by an IFS Cloud Workflow?
Not every Execute Online SQL event action in IFS Cloud has a Workflow equivalent. Logic that duplicates standard behaviour is deleted, process logic moves to a Workflow, and logic that only feeds another system moves to an integration through the IFS Cloud APIs. PL/SQL logic with no other home becomes a documented customization with a named owner.
Which workflow timing should replace a validation in an IFS Cloud event action?
A validation that must pass for the save to succeed uses Before timing in an IFS Cloud Workflow. A Before workflow runs in the same transaction as the user's change, and an exception rolls back the entire transaction, so the workflow should return a clear message that tells the user what to correct. This applies to changes made through a projection action; a change made by direct SQL or a background job starts a workflow only through an event action with Asynchronous timing, which cannot block the save.
Do IFS Cloud Workflows slow down the user's save?
IFS Cloud Workflows with Before or After timing run inside the user's transaction, so their work adds to the time of the save, and an event action with After timing does not start a workflow for changes made by direct SQL or a background job. Workflows with Asynchronous timing run in a separate transaction in a background thread, so notifications and calls to external systems placed there do not make the user wait.
Why do event actions with SQL matter for IFS Cloud updates?
An Execute Online SQL event action calls IFS Cloud database methods or tables directly, and IFS ships Release Updates twice a year and Service Updates monthly. A statement that depended on a changed method or column fails at runtime after the update, so each such event action has to be retested or retired.
7.About the author
Dariusz Myśliwiec: 18 years hands-on with IFS (Apps 7.5 to 10 and IFS Cloud). IFS Certified Associate Consultant. PRINCE2® 7. Independent practice based in Kraków, delivered remotely across Europe and globally. You talk to the consultant who does the work, not a sales layer.
In project reviews I go through event actions, workflows and customizations object by object, and each recommendation names the object and the reason, so your team can check it without me.
Selected clients from my IFS work: Fugro · LGC · BVI Medical · Betafence (PRÆSIDIAD) · Barlinek · NGK Ceramics · Newag · Oleofarm.
IFS is a registered trademark of IFS AB; this practice is not affiliated with IFS AB.
Not sure how much logic sits in your event actions?
Bring the list of custom events and their actions, or an export of them. On a technical call we go through a sample and I tell you which ones should become configuration, workflows or documented customizations, and what a full review would cover.
Book a technical call about your event actions Read: Update-Safe IFS Cloud Extensions

Deutsch (Deutschland)
Polski (PL)