Design and Develop Extensions on SAP Service and Sales Cloud Version 2 Using SAP AppGyver

[VinayPrasad_PM]

Starting March 2023, SAP AppGyver is renamed to SAP Build Apps, and you can find the related document here.

 

What is SAP AppGyver application development?

SAP AppGyver is a no-code development environment that allows users to build business applications without the need for pro-code development knowledge. SAP AppGyver helps professional and citizen developers build and deliver applications quickly. SAP AppGyver provides a no-code application composition tool empowering non-developers to create complete applications without writing a single line of code.

 

Why the industry is moving towards no-code tools like SAP AppGyver?

Changing market dynamics force today’s organizations to evolve continuously. While digital transformation was a line item on many business agendas long before COVID-19, the pandemic has shown very clearly how vulnerable companies are. At the same time, resources are becoming scarcer. The need for developers is growing faster than they can be educated. These circumstances and complex IT landscapes make it challenging for companies to be agile and innovative and remain competitive.

No-Code tooling and the democratization of development have become key dimensions to address the need to deliver processes and applications faster while lowering the total cost of development.

 

Extending SAP Service and Sales Cloud Version 2 using SAP AppGyver

Side-by-side extensions are enhancements to the core functionality without impairing the existing system functionality. In our case, we have an SAP Service and Sales Cloud Version 2 system that you intend to enhance and adjust to a specific business case. To do so, you can build an extension of SAP AppGyver, built on the Business Technology Platform. With side-by-side extensions, you can extend scope with custom solutions, complement data from different backend systems, combine it in a single application, stay flexible, and adjust quickly while keeping the digital core focused.

 

Why SAP AppGyver-based extensibility in SAP Service and Sales Cloud Version 2?

With SAP AppGyver, we empower users to deliver sophisticated enterprise-grade applications without code by building applications visually. SAP AppGyver empowers business users and citizen developers to deliver pixel-perfect standalone apps and extensions in a full no-code composition environment. You can increase development efficiency while eliminating coding effort and also build full-stack apps intuitively for Web, iOS, and Android.

 

This blog highlights the pre-packaged AppGyver with SAP Service and Sales Cloud Version 2.

• Provides a no-code platform to build apps that extend and connect processes with a streamlined experience.


• Eliminates complexity related to process orchestration with a visual design approach, predefined data sources, and connectors


• Embeds easily apps into the customer service process directly within the SAP Service and Sales Cloud Version 2 solution.

 

How to Setup SAP AppGyver

AppGyver needs to be configured before first-time use. If AppGyver is not configured on SAP Service and Sales Cloud Version 2, raise an incident on the component CA-LCA-ACP with the following details:

Note: Refer to Setup SAP Build Apps help with SAP Sales Cloud V2 and SAP Service Cloud V2 and provide your BTP Account details.

• SAP Service Cloud Tenant URL


• SAML 2.0 Trust Configuration for the identity provider used by SAP Service Cloud
  
  
  
  • XML metadata, name, origin key
  
  
  • Existing IdP User Groups to BTP Role Collection mappings if available
  
  
  
  


• SAP Service Cloud Discovery API Destination configuration
  
  
  
  • base path (if not same as SAP Service Cloud tenant URL)
  
  
  • authentication type
    
    
    
    • OAuth2SAMLBearerAssertion
      
      
      
      • OAuth Client App Name
      
      
      • OAuth Client Id
      
      
      
      
    
    
    • Additional parameters as needed by other authentication types
    
    
    
    
  
  
  
  


• SAP Service Cloud Mashup API Destination configuration
  
  
  
  • base path (if not same as SAP Service Cloud tenant URL)
  
  
  • authentication type
    
    
    
    • OAuth2SAMLBearerAssertion
      
      
      
      • OAuth Client App Name
      
      
      • OAuth Client Id
      
      
      
      
    
    
    • Additional parameters as needed by other authentication types
    
    
    
    
  
  
  
  

Once the ticket is assigned, please grant access to the ticket handler:

• Access to customer Global Account (Control Center) to create Subaccount


• SAP Service Cloud basic auth admin credentials for establishing Trust between BTP Destinations and SAP Service Cloud

How to Access SAP AppGyver in SAP Service and Sales Cloud Version 2

1. log in to SAP Service Cloud Version 2 or SAP Sales Cloud Version 2.


2. Navigate to the app switcher, and choose AppGyver.Note: If AppGyver is not configured (tenant not found) on SAP Service and Sales Cloud Version 2, follow the steps in the previous section and raise an incident on the component CA-LCA-ACP.
   


3. A new browser tab opens, displaying the AppGyver lobby.

 

Designing and Developing AppGyver Extensions

1. Click Create to start a new project. Enter a Project Name* and a Short Description for your project, and click Create.


2. A pop-up is displayed as shown below.


3. Once the app is created, you can see the UI Canvas.


4. Design and develop extensions using drag-and-drop visual programming tools of AppGyver. For more information on creating an AppGyver application, seehttps://docs.appgyver.com/ui/overviewAn example Extension UI is shown below:


5. Go to the Auth tab to enable Authentication. Click Enable Authentication.


6. All the available authentication methods are displayed. Choose SAP BTP authentication from the authentication methods.


7. A pop-up similar to the one below is displayed.


8. Click OK.


9. Click Only Web in BPT configuration, and click the Save BTP Configuration button.


10. Navigate to the Data tab, to Integrate with SAP Service and Sales Cloud Version 2 using BTP destinations and use REST API’s content in your SAP AppGyver App. Select the ADD INTEGRATION.


11. On the Add Integration page, click BTP DESTINATIONS.


12. You will see a list of BTP Destinations.Note: BTP Destinations listed here are the destinations to your own SAP Service and Sales Cloud Version 2 API destination as it is set up on the BTP sub-account by the SAP AppGyver support team when the SAP Service and Sales Cloud Version 2 system is provisioned.


13. Click, for example, C4C_Discovery which is added as SAP Service and Sales Cloud Version 2 API destination. You will see a list of data entities or REST APIs from the SAP Service and Sales Cloud Version 2.


14. On the left navigation pane, you can see a list of all REST APIs that can be consumed in the AppGyver app. You can use the search functionality to filter down a particular data entity.


15. You can choose, for example, installed base, and click ENABLE DATA ENTITY.


16. Also, you can consume the REST APIs or OData from external systems under AppGyver classic data entities.

 

 

Deploying AppGyver Extensions as Mashups in SAP Service and Sales Cloud Version 2

1. On the LAUNCH tab, click on DISTRIBUTE from the left navigation and click OPEN BUILD SERVICE.


2. You will now be redirected to the BUILD Choose a form factor, where you want to deploy. Let’s say, we want to deploy as Web App. Now, click CONFIGURE.


3. Enter the AppGyver Hosted Domain information in the Hostname.


4. Click SAVE & NEXT. In the next screen, choose MTAR and SAVE & NEXT.


5. Choose SAVE & NEXT on the Image Assets.


6. Click SAVE & NEXT on the Permissions tab.


7. Once the configuration is complete, it’s now time to build.


8. Click BUILD, and enter the following information as shown below:


9. Once you click on BUILD, it takes about 15 to 30 minutes (time may vary) for the build to complete.


10. Now click DEPLOY MTA. In the Deploying Multi-Target Application(MTA) pop-up, click AUTHORIZE BTP DEPLOYMENTS.


11. Choose the SAP Service Cloud mashup destination as it is set up on the BTP sub-account by the SAP AppGyver Support team when the SAP Service and Sales Cloud Version 2 system is provisioned.


12. Click Deploy MTA where you can see the progress of the deployment.


13. Once the deployment is complete, the Mashup Id is displayed.

 

Embedding the AppGyver Extensions in SAP Service and Sales Cloud Version 2 Application

 

1. On the SAP Service and Sales Cloud Version 2, navigate to User Profile ->  All Settings -> Mashup Authoring and look for the Mashup ID.


2. You can now embed this mashup in an SAP Service and Sales Cloud Version 2 application, for example, in the Agent Desktop app.


3. Go to your user profile, and click Start Adaption.


4. All the sections where adaptations can be enabled are shown below.


5. To insert your mashup, select a section and click Edit Tabs, and choose to Create


6. Embed the newly created mashup in your SAP Service and Sales Cloud Version 2 application (in this case, Agent Desktop).


7. Embedded the newly created mashup in your SAP Service and Sales Cloud Version 2 Application (In this case, Agent desktop)

You’ve now successfully designed and developed an AppGyver extension and embedded the extension as a mashup in an SAP Service and Sales Cloud Version 2 application.

 

Wrap UP

• Included with SAP Service and Sales Cloud Version 2, AppGyver provides a no-code platform to build apps that extend and connect processes with a streamlined experience


• Eliminates complexity related to process orchestration with a visual design approach, predefined data sources, and connectors


• Easily embeds apps into the customer service process directly within the SAP Service and Sales Cloud Version 2

Please explore the SAP Cloud for Customer Community page and feel free to ask questions!

[yun_07]

Very nice and informative blog! Thank you, Vinay.

[VinayPrasad_PM]

Welcome, Wang

[RNL]

Hi Vinay,

Thank you for your blog. What are the requirements to use Appgyver? We retrieve a "Tenant not found" message, after step2.

Thank you, René

[VinayPrasad_PM]

Hi Rene

If you are already an SAP Service Cloud V2 Customer, please create an incident in the component CA-LCA-ACP

Thanks

Vinay

[former_member40527]

Thanks Vinay for providing clarity and information!

[VinayPrasad_PM]

Welcome, Shridhar

[PacoRuiz]

Hi Vinay,

first of all: great blog!

I have a question: How can we create custom logic using AppGyver in order to adapt the standard functionality?

for example, capturing a BeforeSave event for Sales Quotes and changing the values of some fields based on custom logic.

With SDK we can introduce custom logic into events or BADIs. How it works with AppGyver?

[VinayPrasad_PM]

Hi Francisco

There shall be hooks in the standard functionality for adaptions, which is on the roadmap.

Thanks

Vinay

[former_member831914]

Hi Vinay,

Thanks for your blog!!! It is just the information I was looking for.

I have some questions related to the appgyver extensions that I would really appreciate you help me to solve:

- is it possible to activate the adaptation functionality within a appgyver extension (ie. hide/display fields based on business roles in an appgyver extension)? If so, do we need to follow any design pattern or add/use specific components in the appgyver extension?

- Changes in the layout/theme of the standard solution also apply to appgyver extensions?

Thanks in advance,

Carlos

[VinayPrasad_PM]

Hi Carlos

These ideas are on our roadmap.

Thanks

Vinay

[SCHNEIDERT]

Hi vinay.prasads, thanks for your informative blog post! 🙂

I have some questions related to the setup:

1. SAML 2.0 Trust Configuration: By default, Sales Cloud V2 is not pre-integrated with one of our IAS tenants. Which information do we have to provide here in that case?


2. SAP Service Cloud Discovery API Destination configuration: where do I find or create that information?


3. Access to customer Global Account: Here I only have to add a user for SAP Support colleague in the Global Account that has been provisioned by SAP together with the V2 tenant, is that correct? Do you know if it is only possible to connect the customers' Global Account or ANY other subaccount (e.g. an existing subaccount of a partner?)

Last question: Does this whole integration process has to be done by SAP Support or is it also possible to do it by ourselves?

Kind regards

Tobias

[DhruvinM]

Hi vinay.prasads  Thanks for the blog!

So seems SAP is moving in with Cloud native 😛 Do we foresee complete migration from C4C to this topic? and if yes how do we deal with Custom BO developments and apart from AppGyver do we have anyother possibilities like BTP Extension suite etc , for custom development?

Looking forward to recieve your feedback.

Regards

Dhruvin

[SCHNEIDERT]

Does "pre-packaged AppGyver with SAP Service and Sales Cloud Version 2" mean that it is free of charge?

Because in our BTP Global Account that has been provisioned together with the V2 solution, the services are not active by default.

Is there an additional subscription necessary?

BR Tobias

[VinayPrasad_PM]

Hi Tobias

AppGyver is part of SAP Service and Sales Cloud Version 2 pricing. No additional subscription is necessary.

Thanks

Vinay

 

[VinayPrasad_PM]

Hi Tobias

This integration has to be done by SAP Support.

Thanks

Vinay

[VinayPrasad_PM]

Hi Dhruvin

There shall be tools to migrate data from C4C to CNS V2 but CNS V2 will be a reimplementation. There shall be options other than AppGyver like Business Application Studio etc for Custom logic.

Thanks

Vinay

 

 

[dpksghl_30]

Hi Vinay,

Very nice blog!

I have questions on provisioning SAP Sales or Service Cloud V2 tenant:

1. How should we ask for new V2 system from SAP?


2. What details are shared by SAP initially with the requestor?


3. Can anyone enroll for a SAP training program to understand and implement solution with SAP Sales or Service Cloud V2?

Please help with these details.

Thanks

Deepak

[Kinsbrunner]

Hi Vinay,

Thanks for sharing this interesting blog with the Community.

I'd like to understand how to enhance an existing standard scenario such as, for example, the Move In process. Let's say it has 3 steps and I'd like to add an additional step. Would the right approach be to use AppGyver? Is this feasible? How? As per my understanding, AppGyver (now aka SAP Builds) is for developing, as you said, a side-by-side extension but, how to deal with this scenario where we are not just adding an extra field but an extra screen?

Thanks!

Alejandro.

[s0007226202]

Dear,  does this mean that SAP will push forward AppGyver / SAP Build as the recommended architecture, and decommission the Sales/Service Cloud SDK (Cloud Application Studio) as an extension model?

 

What is SAP's recommendation for current Sales/Service Cloud customers that seek to create applicatiopn extensions ?   Side-by-side, or SDK/CAS ?

 

Thanks!

[VinayPrasad_PM]

SAP Build Apps is one of side by side extension options for SAP Sales Cloud Version 2 and SAP Service Cloud Version 2.

SDK will remain an extension model option for the Cloud for Customer Sales and Service Cloud.

[VinayPrasad_PM]

Hi Alejandro

In SAP Sales Cloud Version 2 and SAP Service Cloud Version 2, extra fields are added by In-App extensions. Extra screens can be added via SAP Build Apps.

Best Regards

Vinay

[Kinsbrunner]

Thanks Vinay for taking the time to answer me, once again!

Which would be the right path to transition from C4C development into Sales/Service Cloud v2 development?

For sure, reading standard documentation but, until now, there is almost no technical documentation nor guidelines.

Let me know your comments.

Regards.

Alejandro.

[dhruv_mehta]

Hi Vinay,

isnt Appgyver or SAP Build is very limited in terms of developing custom BOs? In those cases what needs to be done?

BR

Dhruvin

[VinayPrasad_PM]

Hi Alejandro

There shall be tools to migrate data from C4C to CNS V2 but CNS V2 will be a reimplementation.

Best Regards

Vinay

[VinayPrasad_PM]

Hi Dhruvin

There shall be options other than SAP Build Apps(low-code) like Business Application Studio(pro-code) etc for Custom logic.

Best Regards

Vinay

[DhruvinM]

Cool! Really looking forward for the same.

[PacoRuiz]

Hi Vinay,

I suppose additional subscription and users licences for BAS will be required, don´t?

do you know the estimated release date for BAS integration with V2?

 

Thanks in advance!

[DamoH]

What is the offline capability of the App developed in App Gyver?

[DamoH]

Does it mean the sunset of Kyma?

[rogermirandae]

Thank you very much for the information.

I have a question. If a customerhas SAP Sales & Services Cloud version 2 and does not purchase SAP Build Apps due to budget issues, what is the path they should follow to develop on their system?

Thanks 😄

[susheelkc]

Hi Rogelio,

You can see the documentation for more details.

Regards,

Susheel

[VinayPrasad_PM]

Build Apps is an SAP-recommended option. Since SAP Sales and Service Cloud Version 2 is built on Open Architecture standards like REST APIs and Business Events, Customers and Partners can choose their own Platform for extensions.