Joule Studio's capabilities allow it to connect to a data source, in our case SAP Business One, thanks to Actions, and this is a central and fundamental concept.
Actions in SAP Build are components that allow you to Create, Read, Update or Delete (CRUD) data through Destinations, which in turn connect to the Service Layer.
If you want to delve deeper into Actions, I recommend the following link: ODATA - Actions
Currently, Actions can be created using the OpenAPI Specification 3.0, but this doesn't yet exist for the SAP Business One Service Layer. It has been documented in a requirement that you can find at this link: https://influence.sap.com/sap/ino/#/idea/311258
However, we can create Actions from scratch. This requires a solid understanding of how to use the SAP Service Layer, as well as access to it.
I'll explain how they are created, tested, and consumed using Joule Studio's skills; if you master this, you'll be ready to move forward.
Step 1
Direct link: https://youtu.be/3vmdXuFYenM?si=wfnTwnZMpxm5R1g3
Step 2
Now that we have the Action published, we go to the Joule Studio skill, add it, and configure the input we added, this will make Joule ask the user for the Service call number.
If the response is successful, Joule will be able to answer the user's queries, I'll explain this in another post.
Best regards.
Erick Gómez
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
| User | Count |
|---|---|
| 9 | |
| 6 | |
| 5 | |
| 5 | |
| 5 | |
| 5 | |
| 4 | |
| 4 | |
| 3 | |
| 3 |