August Developer Challenge Week 2 – New Joule Studio

[Rekha_DR]

                               

This is part of the August Developer Challenge on Joule Studio.

Now that you have a background in SAP Joule, we come to the part everyone is waiting for:  New Joule Studio. SAP Joule Studio is SAP’s AI-first development environment for building custom AI agents, apps, and workflows. Powered by the SAP Business AI Platform.

During this challenge, you will be taking up a course to build your foundational knowledge about the New Joule Studio, which was announced during Sapphire 2026 in May. 

Your Task 

Step 1:  Click on this link: Introducing Joule Studio.   

Step 2: On the top right corner, click on the User Icon to log on to SAP Learning with your SAP Universal ID and password. 

Click on “Start Learning” to begin the course. 

You will be offered 3 units to complete.  

Unit 1: Big-Picture SAP Business AI Platform – Pillars of SAP Business AI Platform.  

Unit 2: Joule Studio – Intent-Based development, Demo, Creating AI Agent 

Unit 3: n8n Workflows in Joule Studio – creating n8n workflows in Joule Studio.

You Nailed it! We are happy that you have earned yourself an Achievement Badge. Click on this badge.  

You will be navigated to the “Completed” activity page. Find the record with the course “Introducing Joule Studio” and click on View Badge. 

You will be offered a pop-up. Click on “Make badge public”. 

Make a screenshot of this pop-up and post it in the comments of this blog post along with your answer for the question below:

Question for this Week's Challenge: Comment for this blog post at least ONE key difference between the Classic Joule Studio and the New Joule Studio.  

Here we see who has earned the Badge and when. You can see the options to publicly share your Badge on LinkedIn, save as PDF etc. Do not forget to share this badge on LinkedIn if you like!  

Well done! We believe you are having in this learning process so far. From next week, you will get hands-on. We look forward to seeing you there. Stay connected and stay happy!

[anviksha_shukla]

The Classic Joule Studio is tightly integrated with SAP Build and primarily uses a visual low-code experience to create custom Joule skills and agents. In contrast, the New Joule Studio is an open, AI-first development environment that supports both no-code and pro-code development, allowing developers to use frameworks such as LangChain, LlamaIndex, Pydantic AI, and IDEs like VS Code or Cursor.

[AI4S_Solutions]

One key difference between Classic Joule Studio and the New Joule Studio is that the New Joule Studio provides an AI-first environment focused on creating AI agents, applications, and workflows with intent-based development, while Classic Joule Studio was primarily focused on earlier Joule extensibility and customization approaches.

Thank you, SAP Community and SAP Learning for this challenge.

[PREMRAJA]

Key difference bwt Classic Joule Studio and New Joule Studio:

Classic: The edition is optimized for low-code/no-code developers building custom Joule skills and agents within the SAP Build.

New: It targets the professional developers who need production-grade, code-first agentic AI with deep SAP business context and full DevOps integration.

[SomanathReddy]

In classic Joule studio, you specify the artifacts you want to build, and in the new Joule Studio you only specify your the intent and the business need.

[Mohammed_Nabeel]

For me, the main difference between the Classic Joule Studio and the New Joule Studio comes down to how we build:

Classic Joule Studio- we manually build custom skills and agents to fit specific business needs. we need to design the steps.

New Joule Studio - we simply describe what outcome we want in natural language. Joule then generates the entire setup and system tools automatically. 

[AnimeshDutta]

Classic Joule Studio

Joule Studio (in SAP Build)

Think of it as the place to **extend Joule**.

*Build custom **Skills** and **Agents**

 * Low-code development experience: Ideal for functional consultants and citizen developers enhancing existing capabilities

It introduces a new way to build enterprise AI with:

 ✅ Intent-based development using natural language

✅ Support for everything from **no-code to pro-code**

✅ Model-agnostic architecture

✅ Integrated AI application, agent, and workflow development

✅ A managed runtime for enterprise-scale deployment

[NivedhaMathavan]

One key difference:

Classic Joule Studio, focuses on manually building Joule skills and agents within SAP Build — developers define the business logic, workflows, integrations, and configurations themselves. New Joule Studio, built on the SAP Business AI Platform, introduces an intent-to-outcome (intent-based) development approach: you describe a business requirement in natural language, and the platform generates the business intent analysis, PRD, specification, code, testing, and deployment automatically.

[Tehseen_Chakoli]

Answer for the question is 
Classic Joule Studio – you build everything yourself. You manually set up the logic, workflows, and integrations inside SAP Build.
New Joule Studio – you just describe what you want in plain language, and it does the heavy lifting for you (understanding your requirement, drafting a spec, writing code, testing, and deploying it).

[lucca_castro]

The fundamental shift between Classic Joule Studio and the New Joule Studio lies in the development paradigm itself.

Classic Joule Studio required working with isolated technical artifacts, where business intent had to be manually interpreted and translated into technical implementation through slow, disconnected handovers between business and technical teams.

The New Joule Studio collapses that gap entirely through Intent-Based Development: you describe the desired outcome in natural language, and the platform automatically drives the full lifecycle from Intent Analysis through PRD, Specification, Code, Testing, and Deployment, all within a single SAP-managed environment.

Beyond automation, solutions are now grounded in SAP Knowledge Graph, SAP Domain Models, SAP Signavio, and SAP LeanIX, ensuring every agentic solution is aligned with real business context, upgrade-safe, and Clean Core compliant by design, not by effort.

[Rush_SAP]

Classic Joule Studio is primarily designed for creating custom Joule skills and agents within SAP Build, whereas the New Joule Studio is a comprehensive AI-first platform that supports the end-to-end development and management of AI agents, applications, and workflows at enterprise scale.

[Mohammad_Adil_Ali]

Classic Joule studio mainly relied on Configurations, it had maunal mapping of intent and backend actions . New Joule studio is mainly based on intent based development. Promp->Executable Spec->Code Generation

[VishnAndr]

Joule Studio 2.0 has shifted the paradigm: no manual setup anymore; it is intent-based development now all over the place.

[Tulika_Raj]

Classic is manual/hand-coded, New is intent-based/AI-generated from a natural-language description

[Vivek689]

Classic joule studio requires manual configuration to build single purpose agents specific to one application and bound to SAP Build constructs. New joule studio provides intent based development of complex multi agent workflows, apps, agents with cross application scope and it is model agnostic and tool agnostic

[i_Dani]

Classic Joule Studio: You manually build agents/skills inside SAP Build — defining the business logic, workflows, and configurations yourself.

New Joule Studio: Uses intent-based development — you describe a business requirement in natural language, and the platform generates the business intent analysis, spec, code, testing, and deployment for you — and it's more open, integrating external AI models and third-party tools rather than being limited to SAP Build alone.

[Shipra_Duggal-27]

Answer to the question - Key difference between the Classic Joule Studio and the New Joule Studio:

Classic Joule Studio: A tool inside SAP Build to customize and extend the Joule Copilot with skills and agents.

New Joule Solution: A standalone, SAP Business AI platform to build agents, apps, and entire end-to-end workflows with intent-based generation, managed runtime, and enterprise scale governance.  It's a no code to pro code approach.
 

[tauhid1984]

Answer 

Key difference: Development approach — manual configuration vs. intent-based generation.

Classic Joule Studio (built on SAP Build) requires developers to manually define the business logic, workflows, integrations, and configurations when creating skills and agents.
New Joule Studio, by contrast, uses an intent-to-outcome approach: you describe a business requirement in natural language, and the platform itself generates business intent analysis, PRD, Specification, Code, testing and deployment — essentially automating the steps a developer used to do by hand.
A second difference worth mentioning if you want to add more: openness/extensibility. Classic Joule Studio is mainly focused on building skills and agents within SAP Build, while New Joule Studio supports a more model-agnostic and extensible approach, integrating external AI models and third-party tools.
SAP Community

[Fahri_Donmez_tr]

The new Joule Studio changes the way you use it, offering goal-oriented, low-code development across all environments instead of manual setup for workflows.

[sumit_saini98]

nice

[pavankumar_reddy90]

Classic Joule Studio requires manually configuring skills and agents, whereas New Joule Studio uses intent-based development. You describe the business outcome in natural language, and it generates the requirements and solution artifacts.

[rishwanth_s981]

One key difference between Classic Joule Studio and the New Joule Studio is that the new version follows an intent-based development approach. Instead of manually building agents and workflows, users can describe a business outcome in natural language, and Joule Studio generates the intent, requirements, specifications, code, tests, and deployment artifacts automatically. This significantly reduces the gap between business ideas and implementation.

[janos_resz]

Classic Joule Studio and the New Joule Studio. 

In New Joule Studio, AI generates the PRD for you to share with your team; in Classic Joule Studio, you have to create the PRD manually.

SAP

[metalhead]

The key difference for me is who does the driving. In Classic Joule Studio you configure every phase yourself. Analysis, functional spec, agent setup, code, test, deployment. All separate steps you drive manually. New Joule Studio flips that. One environment for agents, applications and workflows, all starting from business intent. You describe the outcome in plain language and it analyses that intent, generates a PRD that becomes the single reference point for goals, users and success measures, then builds technical specifications and the actual solution from it. Either code you pick up in your own IDE, or an n8n workflow orchestrating SAP and third-party systems in the same flow. The whole thing runs through the Idea Board, so nothing drifts from what the business originally asked for. It validates before it ships. Automated tests, a Testing Overview showing pass, fail and an overall quality score, then packaging and deployment to a managed runtime. No infrastructure to stand up. And it's not throwaway code. The generated project stays fully editable, so developers can extend and maintain it in whatever tools they already use. Classic is "configure each phase." New is "state the goal, then review and refine what it produces." Feels less like using a tool and more like directing one.

[amandeswal25]

Joule Studio, Classic Edition vs. New Joule Studio (in SAP Build)

SAP now offers two flavors of Joule Studio. The Classic Edition is about extending what Joule already does, while the New Joule Studio in SAP Build is a next-generation, outcome-driven studio for building net-new agents and skills. Here’s how they compare:

Aspect Joule Studio, Classic Edition New Joule Studio (in SAP Build)Primary PurposeTarget AudienceSkill BuildingAgent DesignDevelopment ApproachBusiness Context GroundingIntegrationFramework SupportSecurity & GovernanceAvailabilityPositioning

Enhance and extend Joule’s existing capabilities to meet organization-specific needs	Build net-new, tailored AI agents and Joule Skills from scratch for unique business scenarios
Developers extending Joule’s out-of-the-box behavior	Both business users and professional developers, via low-code/no-code tooling
Develop new, deterministic Joule Skills for tailored, repeatable tasks	Skill Builder for rule-based Joule Skills integrated into workflows
Design interactive Joule agents that collaborate with Joule for complex, multi-step tasks	AI Agent Builder for goal-oriented, multi-step reasoning agents that can plan, reflect, and choose their own tools
Visual interface; also supports AI-assisted “vibe coding” for agent configuration using natural language	Drag-and-drop low-code designer; also generates production-ready code (agent definitions, agentic workflows) with IDE/VS Code handoff
Operates within the SAP Build environment on SAP BTP	Taps directly into SAP Knowledge Graph, SAP Business Data Cloud, SAP Signavio (process insights), and SAP LeanIX (architecture context)
Integrated within SAP Build; depends on SAP Build Process Automation	Exposes SAP Integration Suite connectors and third-party actions; supports MCP and A2A (Agent-to-Agent) protocol for cross-system workflows
Standard SAP Build tooling	Supports LangGraph, AutoGen, and LlamaIndex; integrates with Git and CI/CD pipelines
Role-based access, audit logging, and permission management for skills and agents	Full SAP governance layer: role-based access, data masking, content filtering, and full trace logs active by default
Globally available across US, Europe, and Australia; no SAP S/4HANA license dependency	Part of the latest SAP Build capability; available on SAP BTP
Evolving into a distinct product within the SAP Build family, focused on conversational experiences via an agentic approach	The “latest capability” in SAP Build — positioned as the next generation, outcome-driven AI studio

In short: Classic Edition extends and refines Joule for your organization; the New Joule Studio builds and orchestrates entirely new agentic experiences with deeper data grounding, open frameworks, and governance on by default.

[NicoGo]

One key difference: Classic Joule Studio requires developers to manually define business logic and workflows within SAP Build, while New Joule Studio uses an intent-to-outcome approach — you describe the business requirement in natural language, and it auto-generates the PRD, spec, code, and tests.

[liyaqath]

The Classic Joule Studio was primarily chatbot/conversational AI focused, while the New Joule Studio is a unified platform for building AI agents, applications, and workflows end-to-end.

[rishabh_shaily]

Classic Joule Studio relies on a manual, configuration-driven approach where users must explicitly build and configure individual skills and agents within SAP Build, mapping inputs and outputs step-by-step.In contrast, the New Joule Studio utilizes intent-based development, allowing users to describe business requirements in natural language and automatically generating the product requirements document, code, workflows, and deployment artifacts

[Deepak_003]

Classic Joule Studio has you build things manually — you configure Joule Skills and AI Agents yourself step by step in SAP Build. New Joule Studio flips that: you just describe your intent in plain language, and it handles the rest (Business Intent Analysis, PRD generation, etc.) to build the agent automatically.

Joule Studio, classic edition Joule  SAP Build Apps 

[waseem1713]

Question: difference between the Classic Joule Studio and the New Joule Studio?

Answer: Classic Joule Studio relied on low-code, step-by-step manual configuration of skills, triggers, and parameters within SAP Build. In contrast, the New Joule Studio introduces Intent-Based Development, allowing you to describe a business problem in natural language to automatically generate PRDs, specifications, implementation code, tests, and deployment configurations across a structured AI lifecycle.

[Yuva1]

Classic Joule Studio focuses on manually configuring and building isolated, low-code AI skills  inside SAP Build . New Joule studio focuses on intent based natural language approach to build ,orchestrate ,end to end autonomous agent workflows and cross application solutions

[stefano1977]

Hello,

here my earned badge.

I don't have experience in the old Joule  studio version but I see a very promising tool to manage software with AI from conception to delivery.

[muthukumaran84]

Key difference between Classical Joule Studio and Joule studio 2.0 from my view:
Using Classical Studio - we can build Joule skills and Agents
Joule Studio 2.0 - AI First development platform where we can build Agents, apps, workflow orchestrations using NLP and Intent based development.

[Pamela]

Classic Edition — Configuration-first, start with a blank canvas and build step by step: define a skill, configure its inputs/outputs, wire up tools, and deploy

New Joule Studio 2.0 — Intent-first, start by describing the business outcome in plain language. Joule Studio then generates the requirements, agent specification, and build artifacts from that intent — using SAP's own business context, process models, and Knowledge Graph as grounding.

[Nirupama46]

ONE key difference between the Classic Joule Studio and the New Joule Studio: With Classic Joule Studio, we can build joule skills and custom agents whereas with New Joule Studio, we can build agents, apps, workflows with intent based development. 

[nitesh0506]

The biggest difference is that New Joule Studio is intent-driven, enabling AI-assisted creation of agents, apps, and workflows, while Classic Joule Studio was more manually configured and developer-driven.

[shankar_narayan_k]

Classic Joule Studio is configuration-driven, while New Joule Studio is intent-driven. New Joule Studio lets users describe a business requirement in natural language and helps turn it into a deployable solution.

• Classic Joule Studio: Manually configure skills, agents, logic, workflows, and integrations.
• Intent-driven: Start with the business intent and perform intent analysis.
• End-to-end: Generate PRD, Specification, Code/Workflow, Testing, and Deployment.
• More open: Supports external AI models and third-party tools.
• In short: Classic Joule focuses on configuration, while the New Joule focuses on intent-to-outcome.

[anissara_s]

Classic Joule Studio - you set it up yourself on BTP: entitlements, SAP Build Process Automation, Joule plan, Cloud Identity Services.

New Joule Studio - fully SAP-managed runtime, zero operational overhead,  nothing to provision before you build.

[ujala2017]

The classic Joule studio was not an intent based development approach where as the new Joule studio is an intent based developement approach aslong with N8N workflow where as in the classic joule stusio the N8N Workflow based approach was missing

[Sharathmg]

The key difference in my view is the seamless integration of workflow and ability to use AI prompts in building agents. 

[BodaChandana]

Classic Joule Studio is mainly focused on building skills and agents within SAP Build, whereas the New Joule Studio supports a more model-agnostic and extensible approach, integrating external AI models and third-party tools to create more robust end-to-end solutions.

[Raja7799]

For me:
Classic Joule Studio is primarily focused on building custom joule agent using SAP Build Low code no code, while the New Joule Studio is afully managed, enterprise-scale platform for building AI agents, applications, and workflows with intent-based development and pro-code frameworks.

[ChiragPRO99]

Classic Joule Studio is primarily capability-based, where predefined capabilities drive the interaction. The New Joule Studio is intent-based and agentic, allowing agents to understand user intent, reason, and dynamically determine the actions needed to fulfill the request.

[ahmedrfaayis]

Classic: you specify the artifacts — skills, agents, integrations — and wire them yourself.
New: you specify the intent. The platform analyses it, drafts a PRD, then generates the spec, code, tests and deployment — with an SAP-managed runtime and native n8n workflows.
From "build me these components" to "here's the business outcome I need."

[kenzi]

One key difference is that Classic Joule Studio focuses on manually creating and configuring Joule skills and agents, while the New Joule Studio uses an intent-based development approach.

With the New Joule Studio, we can describe the business requirement in natural language, and it can help generate the solution artifacts and even create n8n workflows for process automation. This makes the new approach more flexible for building end-to-end agents, applications, and workflows with much less manual configuration.

- Kenzi Sibuma

[hrs-grg12]

Classic Joule Studio was really about building skills and agents inside SAP Build, and you basically had to define the business logic, workflows, and integrations yourself by hand. The new one runs on the SAP Business AI Platform and flips that around—you just describe what you need in plain language and it works out the intent analysis, PRD, spec, code, testing, and deployment for you. It's also less locked-in, so you can plug in outside AI models and third-party tools.

[Pais]

Agentic AI based approach using intent from business requirements 

[MAHERG]

                                                        

Classic Joule Studio: primarily focuses on building custom Joule skills and agents using low-code/pro-code capabilities within SAP Build.

New Joule Studio: provides an AI-first, intent-based development environment where you describe what you want in natural language, and it can generate agents, applications, and workflows.

[vivek_kumar811]

Classic Joule Studio mainly focuses on building skills and agents using a low-code approach in SAP Build, where developers need to manually define the workflows, integrations, and business logic.

New Joule Studio follows a more AI-first and intent-driven approach. Instead of starting with configuration, users can describe their business requirement in natural language, and the platform helps generate and refine artifacts such as PRDs, specifications, code, tests, and deployment assets before the actual solution is created.

In short, Classic Joule Studio is more about manually configuring agents, while New Joule Studio starts with the business intent and supports the full development lifecycle.

[jlgalvezf]

My answer:

The new Joule Studio enables intent-based agent generation: the user describes the business outcome in plain language (a prompt), and the studio derives the requirement automatically instead of requiring manual technical setup. The flow has four stages:

1. Intent description – the user states the business need in natural language, with no technical specification required.
2. Automated artifact generation – based on that intent, Joule Studio generates a full package: a Product Requirements Document (PRD) that acts as the functional specification, a Technical Specification (implementation design), Code Scaffolding (the actual agent code or workflow — which can target an IDE-based implementation or an external orchestration engine such as n8n, depending on the scenario), an Evaluation Suite (test cases and edge cases), and, when needed, a Multi-Agent Orchestration Definition.
3. Review and refinement – every generated artifact is editable; teams can adjust the PRD, the technical spec, the code, or the test cases before deployment.
4. Managed deployment – once tests pass, the agent is deployed through Joule Studio's managed runtime, which handles execution, scaling, monitoring, and security without manual infrastructure decisions.

In contrast, classic Joule Studio requires the developer to manually configure each phase individually: choosing the model, designing the prompt, wiring up tools, creating the agent definition, writing evaluation logic, and configuring the deployment runtime — each step demanding specialized technical expertise. This makes the classic approach developer-dependent, while the new intent-based flow is designed to be usable by business analysts and functional consultants without deep technical skills.

[Jinang]