
"“People wanted to see more pro-code flexibility,” he said in an interview at Sapphire 2026. “We had gone with a low-code approach. You could give it extension points and tools, but you couldn't touch the core of it. Now you can build a custom agent, connect it to your own GitHub.”"
"“What people want is agentic flows with clear gates and workflows and subagents,” von Rüden said. “Old Joule didn't provide that. Now it's all baked together.”"
"Joule and AI Agent Hub are generally available, though the latter is now getting a “massive revamp” with version 2.0. The Knowledge Graph is live and has expanded beyond its original scope. Initially used for building Joule skills, it now feeds context directly to AI agents so they can “figure out how to call something dynamically,” von Rüden said."
"Joule Studio, however, is still in early customer adoption; general availability is expected in the third quarter - a year behind the original target. Joule Work, the new engagement layer announced this week, isn't expected until the second half of this year."
SAP’s original architecture prioritized ease of use over power, limiting pro-code flexibility and preventing direct access to the core. Customers needed agentic flows with clear gates, workflows, and subagents, which the earlier Joule Studio did not support natively. Joule and AI Agent Hub are generally available, while AI Agent Hub is undergoing a major revamp for version 2.0. The Knowledge Graph is live and expanded beyond building Joule skills, now providing context directly to AI agents to dynamically determine how to call capabilities. Joule Studio remains in early adoption, with general availability expected in the third quarter, and Joule Work is planned for the second half of the year.
Read at InfoWorld
Unable to calculate read time
Collection
[
|
...
]