Skip to main contentSkip to footer

Workflow

July 2026 | IFS Strategic Advisory Architecture

Orchestrating Business Process Automation (BPA) & Workflows in IFS Cloud

A technical blueprint for configuring, debugging, and scaling transactional and non-transactional process orchestrations inside the IFS Cloud Aurena Architecture.

The Four Operational Subsystems of IFS Cloud Workflows

 
BPA Engine (Camunda Core)

A platform-native BPMN 2.0 execution engine. Handles state transitions, complex gateways, parallel execution forks, and programmatic user interactions via low-code or JavaScript/Groovy injection.

 
Entity Event Actions

PL/SQL-based database triggers operating at the logical unit (LU) data layer. Ideal for high-performance, synchronous data validation, auditing, and immediate state mutation before transaction commit.

 
Aurena User Tasks

State-aware human interaction blocks configured directly inside Aurena Client pages. Forces contextual user input or multi-level sign-offs using dynamically-rendered assistant panels.

 
OData Integration Points

Native HTTP/REST service tasks operating on the OpenAPI 3.0 standard. Safely transmits JSON payloads to exterior message queues, ESB clusters, or IoT endpoints with built-in retry policies.

Maximizing Throughput and Eliminating Transaction Bottlenecks

Developing workflows within IFS Cloud requires a strict separation of concerns between client-side rendering, projection routing, and database execution. Poorly configured workflows—especially those running complex PL/SQL packages inside synchronous BPMN Service Tasks—can easily lead to database lock contention, increased API latency, and critical thread pool starvation on the middle-tier container pods.

To optimize execution, technical architects should enforce asynchronous boundaries within the Camunda process model. By designating service tasks as asynchronous, long-running processes (such as external SOAP/REST API round-trips) are decoupled from the user's synchronous Aurena transaction. This prevents browser timeouts and ensures that database transactions are committed immediately, freeing up session resources.

Architect's Note: Guarding Transaction Integrity

Always verify your transaction boundaries when writing Pre-BPA and Post-BPA events. A failure in a synchronous Pre-BPA execution path will trigger a roll-back of the initiating OData projection request. Conversely, asynchronous Post-BPA workflows fail gracefully in the background, requiring proper BPMN error boundary handling to log failures in the Camunda cockpit without disrupting the user interface experience.

Architectural Deep Dive & Workflow FAQ

Custom Event Actions (PL/SQL) are low-latency, run directly on the Oracle database container, and are best suited for single-entity validation, row-level data manipulation, and immediate table auditing.

Business Process Automation (BPA) should be used when the process requires state preservation, complex conditional routing, user input collection (User Tasks), integration with external API endpoints (Service Tasks), or asynchronous background processing. BPA is modeled in BPMN 2.0 and executes in the Java-based Middle-Tier runtime environment.

Workflows authored using the native IFS Cloud BPA tool are saved as system-owned XML configurations within the metadata schema, decoupling them from core application source code. Because of this architectural separation, they survive biannual release upgrades (e.g., R1 to R2) without manual code merges. However, because workflows interact directly with Projection APIs, any breaking changes to the underlying OData Entity/Projection contracts will require workflow validation. Solution architects should integrate BPA functional tests into their IFS Automated Test Suite (TS) as part of the regression testing cycle.

External orchestrators can trigger BPAs by making authenticated HTTP POST requests to the /int/ifsapplications/projection/v1/ system projections. By invoking a Custom Action bound to a Projection, the event broker fires the linked Custom Event, which sequentially instantiates the BPA workflow. Authentication must be managed securely through OAuth 2.0 client credentials via IAM (Identity and Access Management) clients registered within the IFS Middleware Server.

Ready to Optimize Your Automation Architecture?

Assess your workflow footprint. Migrate legacy PL/SQL customizations and disconnected event triggers into upgrade-safe, highly visible BPMN orchestrations.

Schedule Architecture Review
IFS-ERP Consulting

ROI Calculator

Calculate your return on investment

Input Values

€
€
€

Results

Annual Savings
€ 0
Payback Period
0 months
ROI
0%
Monthly Savings
€ 0

Get Detailed Report

Enter your details to receive a detailed ROI report.