Disclaimer: The insights shared in this blog are based on my personal observations and learning. They may not apply universally, and I encourage readers to conduct their own research and make an informed decision before using this content for productive use.
Introduction
This is the first part of a multi-part series designed to walk you through the end-to-end setup and usage of Joule Studio. In this part, we’ll focus on provisioning—laying the foundation for a successful Joule Skill development journey.
Whether you’re an architect, developer, or business process expert, this guide will help you correctly configure your SAP BTP environment, set up entitlements, and prepare your subaccount for secure and scalable development with Joule.
What is Joule Studio?
Joule Studio enhances the productivity and business impact of Joule, SAP’s AI copilot. It is equipped with powerful capabilities designed to extend Joule’s intelligence to align with your organization’s specific processes, terminology, and needs.
Key Features:
Develop new Joule Skills for executing tailored, deterministic tasks aligned with business operations.Manage and deploy updated skill versions to ensure continuous adaptability and improvement.Define user access and permissions, ensuring the right teams can execute or administer the skills securely.Seamlessly integrated with SAP Build, Joule Studio benefits from SAP’s low-code/pro-code environment powered by generative AI.
SAP Joule Studio Architecture
Business Challenges and SAP’s Solution
Business Challenges
Fragmented user experiences across enterprise applications.Time-consuming manual processes, such as fetching business data.Limited customization in out-of-the-box AI tools.Technical complexity in onboarding automation tools.
SAP’s Solution: Joule Studio with SAP Build
SAP addresses these challenges through:
Low-code development with SAP Build for quick customization.Joule Booster to simplify provisioning and trust setup.Joule Skills to extend the AI assistant with custom logic and backend integration.BTP & IAS integration for secure, scalable access control.
Quotas
When using Joule Studio the following quotas apply.
A quota represents the numeric quantity that defines the maximum allowed consumption of a resource. In other words, how much of a service plan you’re entitled to use.
You can find the quotas listed for Joule Studio below.
Action tasks
Connection timeout
1 minute
Time to establish the connection with the remote host.
Socket timeout
3 minutes
Maximum period between two data packets.
Total execution time
4 minutes
Total time an action task can execute.
Request body size
512 KB
Response content size
100 KB
Known Limitations
When using Joule Studio, note the following limitations:
The authorizations defined at environment level support users or user groups. Projects can be shared with a maximum of 10 user groups with execution or admin rights, or 5 users, and cannot be shared with a combination of user groups and users.Deploying Joule skills to a shared environment in a production tenant can take up to 30 minutes.It is possible to release and deploy a project in which no triggerable skills have been defined. However, this can lead to errors during the deployment.When you use processes and automations from SAP Build Process Automation it is only possible for Joule Skills to start the processes or automations. Results from process and automations can not be integrated into the Joule skill flow.If you type in values for Inputs or Outputs for your Joule skill and delete these manually, the value is missing but you can still release your project. The missing parameter can lead to errors when you run your Joule skill.If you enter just a space, for example ” “, in an input or output parameter, you can release your project but this can lead to errors during deployment.When using a data type as input, if you use object binding to map to different fields, such as input and output parameters from other steps, this could lead to errors when you launch your Joule skill in Joule.If you change permissions in a shared environment, you need to undeploy and redeploy the projects that have been deployed to the environment
Prerequisites
Before you begin, ensure the following:
The SAP Build – build-default plan is available in your Global Account.
The Joule entitlement is assigned in your Global Account.
Your IAS tenant is automatically discovered in the System Landscape of your BTP Global Account.
Joule Studio supports the following data centers*:
Region Name
Region
Infrastructure Provider
Application Identifier
Subprocessor Region
Australia (Sydney)
AP10
Amazon Web Services (AWS)
das-application!b36397
Australia
Europe (Frankfurt)
EU10
Amazon Web Services (AWS)
das-application!b188376
Europe
Europe (Frankfurt)
EU30
Google Cloud Platform (GCP)
sb-das-application!b7641
Europe
Europe (Netherlands)
EU20
Microsoft Azure
sb-das-application!b61066
Europe
US East (VA)
US10
Amazon Web Services (AWS)
das-application!b170816
US
US East (VA)
US21
Microsoft Azure
sb-das-application!b18572
US
US Central (IA)
US30
Google Cloud Platform (GCP)
sb-das-application!b19666
US
* Subject to the availability of Joule Base and SAP Build.
Provisioning Setup
Create a Subaccount in a supported region and subscribe to SAP Build.
In the subaccount’s Trust Configuration, connect your IAS tenant via OpenID Connect (Joule does not support SAML).
Disable the Default Identity Provider for login.
Launch the Joule Booster from the Global Account:
Select your subaccount.
Choose SAP Build Process Automation under capabilities.
Add the SAP Build system using the build-default plan.
Complete the wizard by clicking Finish.
Once complete, navigate to System Landscape → Formation.
In your subaccount:Create the Joule Admin Role Collection, add all Joule roles, and assign your IAS user.
Create the ProcessAutomationAdmin Role Collection similarly.
In Part 2 of this series, we will dive into developing a custom Joule Skill—adding actions, inputs, and defining the skill logic using SAP Build.
Conclusion
With Joule Studio, businesses can extend SAP Joule’s AI capabilities to address their unique operational needs—quickly and efficiently. From provisioning and configuration to skill development and testing, SAP provides a comprehensive framework that’s both powerful and secure.
By building custom Joule Skills within SAP Build, enterprises unlock new opportunities for automation, accelerate digital transformation, and empower users to achieve more with less complexity. Joule is not just an AI assistant—it’s your intelligent productivity partner.
Disclaimer: The insights shared in this blog are based on my personal observations and learning. They may not apply universally, and I encourage readers to conduct their own research and make an informed decision before using this content for productive use.IntroductionThis is the first part of a multi-part series designed to walk you through the end-to-end setup and usage of Joule Studio. In this part, we’ll focus on provisioning—laying the foundation for a successful Joule Skill development journey.Whether you’re an architect, developer, or business process expert, this guide will help you correctly configure your SAP BTP environment, set up entitlements, and prepare your subaccount for secure and scalable development with Joule.What is Joule Studio?Joule Studio enhances the productivity and business impact of Joule, SAP’s AI copilot. It is equipped with powerful capabilities designed to extend Joule’s intelligence to align with your organization’s specific processes, terminology, and needs.Key Features:Develop new Joule Skills for executing tailored, deterministic tasks aligned with business operations.Manage and deploy updated skill versions to ensure continuous adaptability and improvement.Define user access and permissions, ensuring the right teams can execute or administer the skills securely.Seamlessly integrated with SAP Build, Joule Studio benefits from SAP’s low-code/pro-code environment powered by generative AI.SAP Joule Studio Architecture Business Challenges and SAP’s SolutionBusiness ChallengesFragmented user experiences across enterprise applications.Time-consuming manual processes, such as fetching business data.Limited customization in out-of-the-box AI tools.Technical complexity in onboarding automation tools.SAP’s Solution: Joule Studio with SAP BuildSAP addresses these challenges through:Low-code development with SAP Build for quick customization.Joule Booster to simplify provisioning and trust setup.Joule Skills to extend the AI assistant with custom logic and backend integration.BTP & IAS integration for secure, scalable access control. QuotasWhen using Joule Studio the following quotas apply.A quota represents the numeric quantity that defines the maximum allowed consumption of a resource. In other words, how much of a service plan you’re entitled to use.You can find the quotas listed for Joule Studio below. Action tasksConnection timeout1 minuteTime to establish the connection with the remote host. Socket timeout3 minutesMaximum period between two data packets. Total execution time4 minutesTotal time an action task can execute. Request body size512 KB Response content size100 KB Known LimitationsWhen using Joule Studio, note the following limitations:The authorizations defined at environment level support users or user groups. Projects can be shared with a maximum of 10 user groups with execution or admin rights, or 5 users, and cannot be shared with a combination of user groups and users.Deploying Joule skills to a shared environment in a production tenant can take up to 30 minutes.It is possible to release and deploy a project in which no triggerable skills have been defined. However, this can lead to errors during the deployment.When you use processes and automations from SAP Build Process Automation it is only possible for Joule Skills to start the processes or automations. Results from process and automations can not be integrated into the Joule skill flow.If you type in values for Inputs or Outputs for your Joule skill and delete these manually, the value is missing but you can still release your project. The missing parameter can lead to errors when you run your Joule skill.If you enter just a space, for example ” “, in an input or output parameter, you can release your project but this can lead to errors during deployment.When using a data type as input, if you use object binding to map to different fields, such as input and output parameters from other steps, this could lead to errors when you launch your Joule skill in Joule.If you change permissions in a shared environment, you need to undeploy and redeploy the projects that have been deployed to the environmentPrerequisitesBefore you begin, ensure the following:The SAP Build – build-default plan is available in your Global Account. The Joule entitlement is assigned in your Global Account. Your IAS tenant is automatically discovered in the System Landscape of your BTP Global Account.Joule Studio supports the following data centers*:Region NameRegionInfrastructure ProviderApplication IdentifierSubprocessor RegionAustralia (Sydney)AP10Amazon Web Services (AWS)das-application!b36397AustraliaEurope (Frankfurt)EU10Amazon Web Services (AWS)das-application!b188376EuropeEurope (Frankfurt)EU30Google Cloud Platform (GCP)sb-das-application!b7641EuropeEurope (Netherlands)EU20Microsoft Azuresb-das-application!b61066EuropeUS East (VA)US10Amazon Web Services (AWS)das-application!b170816USUS East (VA)US21Microsoft Azuresb-das-application!b18572USUS Central (IA)US30Google Cloud Platform (GCP)sb-das-application!b19666US* Subject to the availability of Joule Base and SAP Build. Provisioning SetupCreate a Subaccount in a supported region and subscribe to SAP Build. In the subaccount’s Trust Configuration, connect your IAS tenant via OpenID Connect (Joule does not support SAML). Disable the Default Identity Provider for login. Launch the Joule Booster from the Global Account: Select your subaccount. Choose SAP Build Process Automation under capabilities. Add the SAP Build system using the build-default plan. Complete the wizard by clicking Finish. Once complete, navigate to System Landscape → Formation. In your subaccount:Create the Joule Admin Role Collection, add all Joule roles, and assign your IAS user. Create the ProcessAutomationAdmin Role Collection similarly. In Part 2 of this series, we will dive into developing a custom Joule Skill—adding actions, inputs, and defining the skill logic using SAP Build.ConclusionWith Joule Studio, businesses can extend SAP Joule’s AI capabilities to address their unique operational needs—quickly and efficiently. From provisioning and configuration to skill development and testing, SAP provides a comprehensive framework that’s both powerful and secure.By building custom Joule Skills within SAP Build, enterprises unlock new opportunities for automation, accelerate digital transformation, and empower users to achieve more with less complexity. Joule is not just an AI assistant—it’s your intelligent productivity partner. Read More Technology Blog Posts by SAP articles
#SAP
#SAPTechnologyblog
