Name: Using Kyma for Custom Logic in SAP Sales and Service Cloud Version 2
Uploaded: 2024-5-2
Duration: 210 s
Description: In this video, see how Events can be configured to trigger powerful serverless functions that can be programmed externally with a programming language of your choice.

Share feedback

<p>Planned maintenance of Practice Systems</p>

Planned maintenance of Practice Systems

Why create an SAP account?

Enhance your learning experience

SAP Learning

Subscribe now

Learn more

Live Sessions

Hands-on Practice

Certification

My Learning

Ready to start learning?

<div><div><div><div>In this video, see how Events can be configured to trigger powerful serverless functions that can be programmed externally with a programming language of your choice.</div></div></div></div>

Using Kyma for Custom Logic in SAP Sales and Service Cloud Version 2

In this video, we want to show you how it is possible to consume events of the Sales and Service Cloud V2 with the help of Kyma. So let's jump to the architecture of this use case. We are starting in the Sales and Service Cloud V2 with a service case, and we are changing the priority of this case. This triggers an event, which is consumed by Kyma. Kyma checks the priority of the case, and if the priority was increased, Kyma creates an additional task in the Sales and Service Cloud. So let's start with the implementation of the use case. First, we have to configure the endpoint where we can send the event to. This is done in Kyma. You can see the Kyma dashboard and the function overview here. You can create the function in JavaScript or Python. An inline editor is provided. In this case, our function checks if the priority was raised and if it was raised another post request is sent to the Sales and Service Cloud. Now we have to configure the Kyma endpoint where we can send the event to. This is done in the API root section. At the top you can see the hostname which we can use in the communication setup scenario in the Sales and Service Cloud in the next step. Let's jump to the Sales and Service Cloud version 2. First we have to create the communication system. Therefore, we create a new system, click on outbound, and use the hostname we just generated in the API rules in the Kyma environment. The last configuration step is the configuration of the trigger. This can be done in the out-of-flow rules. In this case, we use the service case as an entity and only try to trigger an event when a case is updated. No conditions are set for this case, but it's possible to set some. And if the condition was met or the case was updated, in this case only, we send  notification to the communication system we just created. In our case, this means when a notification is sent to this communication system, the function we just created is triggered. Last but not least, I want to show you what we just created. You can see the service case now. To trigger the function, we have to change the priority. Then I jump to the Kyma Logs. And what you can see here is that the function successfully noticed that the priority was raised. So an additional task will be created. The next logging message is the confirmation that the task was created successfully. Now we memorize the ID of the created task, 78, and jump back to the Sales Cloud. And here we go. We are logged in with the sales rep now, which was originally assigned to the service case. And below, you can see there are several follow-up cases we just created. Now you have seen how easy it is to create and use an event which triggers an external function written in Pro Code, JavaScript in this case, to execute logic and write back data to the Sales and Service Cloud. This gives you lots of flexibility when it comes to extensibility.