When It Comes to IFS Automation, Are You Building for the Future or Just Plugging Holes?

In the race toward smarter, leaner ERP systems, automation stands at the center of transformation. The less manual thinking and clicking required, the faster your business runs. But if you’re working in IFS Cloud, you’re likely faced with an important question: should you automate using PL/SQL Custom Events or the newer Business Process Automation (BPA) Workflows?

Let’s break down the pros and cons—and which path leads to a future-proof solution.

Why Automate?

The goal of automation in ERP is simple: eliminate unnecessary effort when outcomes are predictable. Whether you’re triggering a shipping notice or updating a customer record, automation reduces risk, saves time, and streamlines your business processes.

But not all automation is created equal. IFS offers two core methods to automate: the legacy PL/SQL Custom Events, and the newer Workflows via Business Process Automation (BPA).

PL/SQL Custom Events: Old School, Still Useful

PL/SQL Custom Events are based on Oracle database triggers, a technology that’s been around since 1986. They’re simple, direct, and still surprisingly powerful.

Pros:

  • Triggered on create, update, or delete database actions.
  • Written directly in PL/SQL—meaning they can run quickly and are familiar to DBAs.

Cons:

  • Bypass lifecycle controls, meaning they may introduce risk or instability in managed environments.
  • Declared deprecated by IFS—with the exact sunset date still unclear.
  • Cannot interact well with the user or other parts of the system during execution.
  • Suffer from the mutating trigger problem—you can’t query or modify the same table being triggered.
  • Character limit on code (around 3980 characters).

In short, they work, but they don’t scale—and they’re not aligned with IFS’s future vision.

BPA Workflows: The Modern Automation Standard

IFS introduced Business Process Automation Workflows in 2021—and they’ve been rapidly evolving with each Cloud release.

These Workflows offer a low-code/no-code approach, empowering business users and developers alike to build smart automations with visual tools and user interaction.

Pros:

  • Fully supported and actively enhanced by IFS.
  • Visual, intuitive interface—low-code development reduces complexity.
  • Can trigger even without database changes—thanks to integration with Projection Actions.
  • Supports user interaction, such as form inputs and decision trees.
  • Can be launched via Workflow commands (buttons), improving UX for clients.

Cons:

  • More complex than PL/SQL triggers—steeper learning curve.
  • Still evolving—some functions feel unfinished depending on your IFS Cloud version.
  • Not always as quick to implement as simple triggers.

Despite some growing pains, BPA is clearly the future—and every new version of IFS Cloud brings significant improvements.

So Which Should You Use?

Here’s the short answer:

Use BPA Workflows wherever possible.

They’re future-proof, align with IFS’s roadmap, and offer better UX and flexibility. But if you hit a wall—whether it’s due to functionality, time constraints, or version limitations—PL/SQL Custom Events can still be a powerful backup.

In fact, many organizations use a hybrid approach, gradually replacing legacy triggers with Workflows as functionality matures and business needs evolve.

Final Thoughts

Automation in IFS Cloud isn’t just about reducing clicks—it’s about building systems that scale with your business. BPA Workflows are where IFS is investing, and they offer the kind of agile, user-friendly automation that modern businesses demand.

But don’t be afraid to reach for PL/SQL Custom Events when you need a quick fix or workaround—just know that their days are numbered.

IFS Cloud is changing. The question is: are your automations ready for what’s next?