Sanae BEKKAR – My Blog –

What’s coming next ?

File Server System Events

Eventing is being extended to the file system. For example, an integration can be triggered the moment a new file lands in a specified directory. This opens up powerful use cases for legacy systems and hybrid cloud environments.

Project Support for Decisions

Project-based decision services are another enhancement. You can :

• Invoke them directly from the OIC canvas using native actions
• Define business rules inside a project
• Reuse them across multiple integrations

Decision services provide the ability to model, evaluate, and reuse business rules are becoming central to OIC’s automation vision.

With 25.4, you can :

• Define decision tables inside projects
• Drag and drop decision actions directly into integration flows
• Make business logic reusable and centrally governed

Creating a decision in OIC is simple , just :

1. Define the inputs (ex. product name)
2. Set the logic in a table, for example:

You might define a “Discount Decision” table where each product (e.g., Bike, Car) has a different discount percentage. This logic can be invoked in sales, order management, and pricing flows without rewriting or hardcoding rules.

Product	Discount
iBike	15%
iCar	10%
Other	0%

3. Use a native action in your integration , just drag and drop the decision call into the flow.
4. At runtime, the integration sends the input to the decision table, which returns the correct business outcome.

No scripting, no external rules engines, and no disjointed maintenance.

Invoke process

Back by popular demand: the ability to invoke processes directly from the integration canvas , a Gen 2 capability making its return in OIC 3. Paired with decision services, this enables more intelligent and dynamic process flows.

Also share lookups between projects library is possible.

Auto-Retry Logic

One of the most requested features by integration developers is finally : Auto-Generated Retry Logic.

When building integrations that depend on external systems, network hiccups, service unavailability, or transient errors are inevitable.

Until now, developers had to manually wire up retry mechanisms , etc.

With the new « Add Retry Logic«  feature , all you need to do is:

1. Click “Add Retry Logic” in your integration flow.
2. OIC automatically wraps your activity (e.g., invoke or assign) with the necessary retry pattern.
3. Variables such as:
   • MaxRetryAttempts
   • RetryDelay
   • BackoffStrategy
     are assigned and exposed for easy configuration.

No need to hand-code loops, delays, or counters , it’s all handled.

Under the hood , what is happened is that :

• OIC wraps the selected step(s) with a retry framework
• Conditional logic is injected to monitor retry attempts and determine when to stop
• Delays are handled based on your configuration ( fixed delay or exponential backoff)
• A retry counter tracks the number of attempts made

Let’s say you’re calling a third-party shipping API that occasionally times out during high traffic. With the new feature:

• Set retries to 3
• Apply an exponential backoff starting at 5 seconds
• Add an error handler to gracefully exit or alert on final failure

Now your integration can recover from transient issues .

That will :

• Reduces development time
• Ensures consistency across integration teams
• Improves resilience of mission-critical processes
• Adheres to integration best practices effortlessly

With this enhancement, Oracle is continuing to letting developers focus on what matters: business logic and innovation.

This makes it easier than ever to follow best practices for resilient, fault-tolerant integration design, while maintaining clean and readable integration flows.

Data Masking for PII

New tools will allow sensitive information like credit card numbers to be masked in logs or output, ensuring compliance and privacy by design, especially valuable for finance, healthcare, and retail integrations.

For AI side :

Native OCI AI Services in OIC

With Oracle’s push into AI, OIC now features native drag-and-drop actions to integrate with OCI AI services. The first to launch is Document Understanding, which enables:

• Document classification (e.g., invoice, PO)
• Extraction of key fields (like total amount, vendor name)

This opens the door for intelligent automation in invoice processing, contract management, and more. Additional OCI AI services are expected to be natively integrated soon.

AI-Powered iCal Expression Generator

Creating complex schedules in OIC will be as simple as writing a sentence.

Whether you’re triggering batch processes, sending scheduled reports, or syncing data between systems, you need precise and reliable time-based execution.

While simple schedules are easy to define in OIC, many real-world use cases require complex recurrence rules  like:

• “Run every last Friday of the quarter”
• “Execute every Monday and Wednesday at 4:00 PM, except public holidays”
• “Trigger on the 15th day of every third month”

These advanced schedules typically require manually writing iCal (iCalendar) expressions, which are both powerful and difficult to write from scratch.

With « AI-assisted iCal generation « , you can now:

1. Write your schedule in plain English (natural language)
2. Click “Validate”
3. Automatically generate a correct iCal expression

For example, typing:

“Run every second Tuesday at 3 PM”

will output the proper iCal rule behind the scenes , ready to be applied to your scheduled job.

So helpful , in way that:

• No need to learn iCal syntax
•  Faster setup of scheduled jobs
• Supports real-world scheduling, even the most complex rules are supported

More Native OCI AI Services

Oracle is not stopping at Document Understanding. The roadmap includes native OIC actions for several other OCI AI services, enabling broader use cases such as:

• Language: Sentiment analysis, entity extraction, translation
• Vision: Image classification, object detection
• Speech: Transcription and audio analysis
• Gen AI: Summarization, classification, chatbot enrichment

Each of these will follow the same low-code principle: easily accessible, declarative, and embeddable within OIC flows.

One-Click Retry Logic

Error handling is a critical part of resilient integration design. In response to customer feedback, OIC 25.4 introduces auto generated retry logic , a major time saver for developers.

With a single click, you can inject fully-configurable retry logic into your integrations. Key features include:

• Retry attempts (e.g., 3 retries)
• Exponential backoff intervals (e.g., 5s, 10s, 20s)
• Variable assignment for retry timing and counter tracking

All logic is pre-wired for you, allowing developers to focus on business flows instead of writing boilerplate fault-handling code.

As Oracle moves closer to releasing AI agents, desktop RPA, and deeper process automation capabilities, OIC is clearly evolving into more than just an iPaaS. It’s becoming a complete platform for business automation.

Thanks for reading !