I spent this week fine-tuning smart-workflow, our AI integration for Business Processes.
Chore π§Ή
LTS 14 release is coming soon, so as a warm-up I aimed to remove a long standing
technical debt, from the first alpha releases. Namely the dynamic class generation,
which was back then used to provide structured output for agent calls.
This worked out easier than expected.
So, I had enough time to prep burgers π for team dinner in cooperation with grill master @Lukas Lieb π₯οΈ.
Enterprise AI π€π’
My colleague @Nam Mai brought my attention to enterprise-ready AI platforms.
Companies use products like LiteLLM, as a single point to run all their AI efforts.
So I was curious how such an ecosystem fits to smart-workflow.
Routing π§
Routing is something an AI platform can do well. Instead of just firing all calls
to a static LLM, a platform can route small prompts to a simple open weights model,
while giving heavy large context tasks to strong frontier models.
Inspired by this I found that the community π€ has already built this
routing ready to be used in smart-workflow.
I left the routing prototype however, in exploration state as I couldn't easily
identify the preferred routing strategy that I personally would like to run.
Tools π οΈ
Business Processes are first-class tools that can be used by an AI Agent run by smart-workflow.
This means our agents can easily interact with your existing process landscape
and their users. For a company that is already bound to an AI Platform,
this could become a challenge. Since such platforms aim to call only tools known and assigned
by a managed MCP registry.
So I started to add a simple MCP interface π to smart-workflow. It opens the door for any
harness or AI platform to interact with Business Processes in Axon Ivy.
As a proof of concept I started my workflows using Copilot π

TL;DR π¬οΈ
Axon Ivy Smart-Workflow is easy to adapt to enterprise platform needs. It was LLM vendor agnostic ever since. And now gives you more freedom on how to run it; either leading your AI initiatives or partaking by supplying Business Processes as tools.
I can't wait leaving the smart-workflow beta phase and seeing the user base growing, as LTS 14 is soon approaching. ποΈ