week 3: introduction to the enterprise edition unit 1

Week 3: Introduction to the Enterprise Edition

Unit 1: Differences Between Community and

Enterprise Editions

2PUBLIC© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ

Differences between community and enterprise editions

What is the community edition of SAP Conversational AI?

▪ The community edition of SAP Conversational AI is

the free trial landscape of our chatbot building

platform, accessible to all our community of users

around the world at https://cai.tools.sap/.

▪ Anybody can create their own account for free in a

few minutes and start building chatbots on the

community edition.

▪ For productive and commercial usage of your

chatbots, the enterprise edition of the platform is

mandatory.

https://cai.tools.sap/



What is the enterprise edition of SAP Conversational AI?

▪ The enterprise edition can be used by SAP Conversational AI

customers to have all their chatbots and data securely isolated in

their own tenant.

It provides a secure, role-based, and user-friendly experience for

using the chatbot UI that is integrated in the different product

applications.

▪ The main benefits of having your data secured in your tenant are:

– It allows management and consumption of data independently of

other tenants.

– It ensures that data belonging to a specific tenant is visible to only

those users who have access to the tenant.

– It enables lower floor price per customer when using shared

resources.

– It allows an easy integration of your chatbot with other SAP

products because tenant separation is a key concept across SAP

solutions.



Comparison table (current as of July 2021)

Features Community Edition Enterprise Edition

Free Paid

URL Community edition URL Tenant-specific

SSO (with Web client) No Yes

Data isolation No Yes

Destinations No Yes

Premium features

(Test Tab…)

No Yes

Support No Yes

Productive usage No Yes



Transport bots across community and enterprise (1)

▪ You can transport your existing bots across your

SAP Conversational AI enterprise tenants or

community tenant.

▪ This provides the flexibility to move your bots across

tenants without the need to re-build the bots from

scratch in the target tenant.

▪ This feature is available for both action and

FAQ bots.



Transport bots across community and enterprise (2)

You can import and export bots either from the user interface or

using APIs.

▪ Transport bots from user interface

Both community and enterprise users can import and export bots from

the user interface.

Ensure that the necessary requirements are fulfilled before either of the

actions are triggered.

For more details, please refer to Transporting Bots From User Interface.

▪ Transport bots using APIs

Only enterprise edition users can export and import bots using the APIs.

This separates the scope between bot development and bot delivery, as

the tenant administrators can transfer the required bots or bot versions

from the source tenant into the target tenant and deliver the bots after

performing minimum configurations or customizations without the

involvement of the bot developer.

For more information, see Transporting Bots Using APIs.

https://help.sap.com/viewer/e61957c3eb584a7ba8e49bf687f65ad5/latest/en-US/c52d6caacd08453f82de27216ed15320.html

https://help.sap.com/viewer/e61957c3eb584a7ba8e49bf687f65ad5/latest/en-US/0afed4b5a75f4ce8846336e698a18dbd.html

https://help.sap.com/viewer/e61957c3eb584a7ba8e49bf687f65ad5/latest/en-US/e3ff9c0f5d0e446db0d146068e93f57b.html



Transport bots process involves two steps

1. ExportDownload the selected bot version(s) into the local repository in

the form of a content package (zip file).

2. ImportUpload or import the content package (zip file) into the target

tenant(s), using which you can create new bots or add new

versions of existing bots. If you import the bot for the first time,

a new bot (with the same ID as the source bot) is created in the

target tenant. With the subsequent import/s (of the same bot

with new version), a new version is added for the existing bot.

RestrictionThe files generated during one type of export (user interface or

API) should be consumed within the same process only. For

example, you cannot import files using an API that have been

exported from the user interface and vice-versa.



Appendix

▪ Configuring the Enterprise Edition

▪ Transporting Bots Across Tenants

– Demo

– Documentation

▪ Pricing

▪ Join us on SAP Community

▪ Ask questions on SAP Answers

https://help.sap.com/viewer/b2541bd8032b403c9c083ca20682dd3b/latest/en-US/19a65fd6e8f44fbaa872b907b35039bb.html

https://www.youtube.com/watch?v=tvVcvX1Ztzo

https://help.sap.com/viewer/e61957c3eb584a7ba8e49bf687f65ad5/latest/en-US/82dd6271cfa440f7959a6bf2c2910117.html

https://discovery-center.cloud.sap//serviceCatalog/conversational-ai?service_plan=sap-conversational-ai&region=europe(frankfurt)&tab=service_plan

https://community.sap.com/topics/conversational-ai

https://answers.sap.com/tags/73555000100800001301

Thank you.

Contact information:

[email protected]

© 2021 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of

SAP SE or an SAP affiliate company.

The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its

distributors contain proprietary software components of other software vendors. National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or

warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.

The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty

statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional

warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or

any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,

and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and

functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason

without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or

functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ

materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they

should not be relied upon in making purchasing decisions.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered

trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names

mentioned are the trademarks of their respective companies.

See www.sap.com/trademark for additional trademark information and notices.

www.sap.com/contactsap

Follow all of SAP

http://www.sap.com/trademark

https://www.sap.com/registration/contact.html

https://plus.google.com/+SAP

https://www.linkedin.com/company/sap

https://www.youtube.com/user/SAP

https://twitter.com/sap

https://www.facebook.com/SAP


Unit 2: End-to-End Demo


End-to-end demo

Discover the features only available in the enterprise edition

Bot TestingRun unit tests for your chatbots

SAP Business Technology Platform DestinationsDefine connections for outbound communication from your application to

remote systems. These remote systems can be on-premise or in the cloud.

SAP Single Sign-On (SSO)Provide to users a controlled

access to SAP and non-SAP

applications with a single

password

SAP Fiori Launchpad

Integration with Web ClientEmbed chatbots in different

SAP solutions


End-to-end demo

Demo

DEMO


End-to-end demo

Appendix


▪ Create a destination in an SAP BTP subaccount

▪ Pricing



https://help.sap.com/viewer/b2541bd8032b403c9c083ca20682dd3b/latest/en-US

https://help.sap.com/viewer/dmc-int-guide/e08040a9cf664555957a419dc2df0e19.html




Thank you.


[email protected]










warranty.














Follow all of SAP









Unit 3: Using the Test Tab


Using the Test tab

What is the Test tab?

▪ The Test tab is available for enterprise edition users

only.

It is available for both intent-based and FAQ bots.

▪ Before you deploy your bot to your application, you

need to check your bot’s quality to ensure

consistency in the end user experience.

▪ Using the Test tab, you can automate the testing for

the most used test sentences or expressions to verify

the expected response from the bots whenever any

changes are made to the training data of the bot.

▪ This is especially useful if your existing bot model

has closely related intents with similar expressions,

as you can continuously improve your bot without

disrupting the existing model.

Same applies for expressions with closely related

entities.


Using the Test tab

How to run a test using the Test tab (1)

It is recommended that you run the regression test after

every modification done to the bot's conversation flow.

It is used to determine if the modification impacted the

existing bot flow or created new errors.

1. Click the Test tab.

2. On the test Overview page, click +New Spec to create a

new test spec.

3. Provide a suitable name for your test spec. Click Create.

4. Before you run the test, you need to first add test cases to

the spec. Click edit (pencil icon) under Total Test Cases or

choose Manage Test Cases under the overflow menu

(three dots) on the right.

5. Click +New Expression and enter an expression that you

want to test. You can add as many expressions as you like.

The entities in the expression are highlighted (underlined).


Using the Test tab


6. For each expression, you can add input memory as

the JSON with key value pairs.

The response from the bot is dependent on the

expression and the input memory. For example, a

skill to place an order has product id and quantity as

requirements, with corresponding replies defined for

each requirement. There can be multiple scenarios

for which you can create test cases.

You can add expressions with memory values or

without memory values. The expression can:

− include both required values

− include only one required value

− exclude both required values

Based on the input memory and the expression

combination, you can define the expected response.


Using the Test tab


7. For each test case, the detected skill, intent, language,

entities, and the expected values are displayed. You can

remove the detected skill or intent and select another

one, switch the language, and add or remove entities.

8. Go back to the Overview page and click Run Test.

The Run Test button is not highlighted if there are no test

cases added.

9. Select the bot version you would like to run your test

against and click Run. A green bar indicates success, a

combination of green and red bar indicates that some

tests have failed. If the test run was unsuccessful, a red

exclamation icon is displayed.

10. To view the test runs, click the overflow menu (three dots)

and select View Test Runs. All the test runs are listed on

the Test Runs page showing date and time, version, and

the test results (successful or failed) for each test.


Using the Test tab


11. For detailed results, click the blue arrow on the right.

12. The failed test cases are listed on the Specs page.

The errors may be due to an unmatched skill or an

entity.

Click the arrow on the right side of an expression for

more details.

Note that the first test case is expanded by default.

You can choose the expand all option to expand all

the test cases simultaneously.


Using the Test tab

Example

In the following example, the skill and the entity that were recognized didn’t match the existing list

of skills and entities. You need to either reword the expression or add a new skill and entity so that

the bot can respond to this expression.


Using the Test tab

How to manage your test cases

Action Why is this needed?

Remove the detected skill and select

a different skill

If you've added a new skill in your bot and want to check if it is going to be detected, you can use the

same test case by selecting another skill.

Remove the detected intent and

select a different intent

If you've added a new intent in your bot and want to check if it is going to be detected, you can use the

same test case by selecting another intent. You can select an intent only from the existing intents.

Change the selected language This helps you test the expression for a different language. But you need to ensure that you have

added the training data in the selected language.

Remove the detected entities and

tag additional entities

You can remove the entities (including gold entities) that should not be evaluated at runtime. Besides

this, you can select a word and assign an entity from the list of all the available entities.

Select any element or multiple

elements from the JSON response

to validate for future test runs

You can add multiple conditions using the elements from the JSON response –

nlp, messages, conversations, logs, qna, fallback, hasDelay, hasNextMessage.

Select the appropriate operator and enter a value, depending on what you picked as the operator. This

is to ensure that correct parameters are sent to the API from the expression that is provided.

If you have updated the training data of your bot (for example, added entities, skills, language, and

so on), you can directly edit the existing test case under Manage Test Cases and check if the skill,

intents, and entities are detected or not.


Using the Test tab

Test your FAQ bots (1)

▪ After you have updated the FAQ documents of your bot (added,

removed, or modified Q&A pairs), you can verify if the modification

impacted the bot responses or created new errors. The process to test

the expressions for an FAQ bot is the same as described in the

preceding section.

▪ For FAQ bots, values are displayed based on the detected skill:

− If Customer Satisfaction Prompt, Customer Satisfaction

Reply and Small Talk skills are detected, the skill, language, and the

expected values are displayed.

− If the FAQ skill is detected, the skill, best matched Q&A pairs (up to

three pairs), language, and the expected values are displayed. For

each Q&A pair, the FAQ document that includes the Q&A pair and the

expected matching confidence score for each Q&A pair is displayed.

▪ On the Manage Test Cases tab, you can directly edit the existing test

case and check if the skill, Q&A pairs (only for FAQ skill), language, and

expected values are detected or not.

https://help.sap.com/viewer/b2541bd8032b403c9c083ca20682dd3b/latest/en-US/d6f4b0366e634c93bed4715d690a4de8.html


Using the Test tab

Test your FAQ bots (2)

Action Why is this needed?

If an FAQ skill is detected, you can

remove the matched Q&A pair or

select another one from the same

FAQ document

If you've added a new Q&A pair in your FAQ document and want to check if it’s going

to be detected, you can select the new Q&A pair instead of the one that was matched.

If the selected Q&A pair doesn’t match, it is displayed in red. You can also remove the

matched Q&A pairs, however the detected FAQ skill and the FAQ document can’t be

removed or changed.

If any one of the three skills (other

than FAQ) is detected, you can

remove the detected skill and

select a different skill

You can select another skill from the list of four skills that are available. It is to check if

the selected skill is going to be detected if the user enters the provided test

expression.

Change the selected language You can test the expression in a different language. For this, you need to ensure that

you have added the Q&A pairs in the FAQ document in the selected language.

Select any element or multiple

elements from the JSON response

to validate for future test run

You can add multiple conditions using the elements from the JSON response. This is

to ensure that correct parameters are sent to the API from the expression that is

provided.


Using the Test tab

Good to know

▪ All the permissions that apply for the Train tab are applicable

for the Test tab as well.

For more information, see Permissions at Bot Level.

▪ You can also use the Test APIs to create test cases.

For more information, see API Reference.

▪ You can rename an existing Test Spec on the overview page.

Click the spec, edit the name, and press Enter. To delete a test

spec, click the overflow menu (three dots) and

select Delete from the list. The test spec with all the test cases

is deleted.

▪ To delete a test case, select the test case and click the bin

icon. You can select all the test cases simultaneously using the

icon to the left of the Skill (in the table header) and click delete.

▪ When you fork a bot, all the test specs are exported to the new

bot. However, the test results aren’t forked. You need to run

the tests again in the destination bot.

https://help.sap.com/viewer/b2541bd8032b403c9c083ca20682dd3b/latest/en-US/06b052f684ce47e4a2b787e4856ff9af.html

http://help.sap.com/disclaimer?site=https://reverseproxy.cai.tools.sap/docs/api-reference/#bot-testing-api


Using the Test tab

Demo

DEMO


Using the Test tab

Appendix

▪ Documentation

▪ API Reference



https://help.sap.com/viewer/b2541bd8032b403c9c083ca20682dd3b/latest/en-US/06b389ad3e0d42c7818fb8d0bb5356c5.html

http://help.sap.com/disclaimer?site=https://reverseproxy.cai.tools.sap/docs/api-reference/#bot-testing-api



Thank you.


[email protected]










warranty.














Follow all of SAP









Unit 4: Setting Up the Enterprise Edition


Setting up the enterprise edition

Requirements

▪ SAP Business Technology Platform (SAP BTP)

Global Account needs to have the required

entitlements for subscribing to the SAP

Conversational AI (SaaS) application.

▪ SAP Business Technology Platform (SAP BTP)

Subaccount should have the Cloud Foundry

environment enabled before subscription to SAP

Conversational AI.

▪ The user needs to have the Subaccount Admin role

to subscribe to the SAP Conversational AI

application.



Steps

1. Get required entitlements added to you Global

Account

2. Go to Subaccount Service Marketplace SAP

Conversational AI and create the instance of the

SAP Conversational AI application / subscription.

3. After the subscription is created successfully, go to

Role Collections Create new role collection or

add cai_developer role to an existing role collection

4. Assign the role collection to the IDP user directly or

do role collection mapping for an IDP group

5. Go to Service and Instances Search for SAP

Conversational AI Select “Go to Application” to

launch you SAP Conversational AI enterprise

tenant.



Demo

DEMO



Assign roles

Role Description

cai_developer To allow the bot developer to log into the SAP

Conversational AI enterprise tenant and create or

modify bots

cai_release_admin To transport and configure bots across tenants

cai_tenant_admin To manage tenant configurations and features

cai_user Automatically assigned by XSUAA for every logged

in users. Not to be assigned by tenant administrators

As a tenant administrator in SAP Business Technology Platform, you can assign the following roles:



Enable developer token

▪ If you have the developer token for a bot, you have

the authorization to modify that bot.

▪ Taking security into consideration, developer tokens

are disabled for API access by default.

This is applicable for all enterprise tenants that have

subscribed to the SAP Conversational AI service.

▪ As an enterprise tenant administrator, you can raise

a ticket for enabling developer tokens at tenant level.

You need to provide the subaccount details and

the API endpoint in the ticket.

http://help.sap.com/disclaimer?site=https://launchpad.support.sap.com/#incident/solution



Appendix


▪ Get started with SAP BTP Enterprise Account

▪ Pricing



https://help.sap.com/viewer/b2541bd8032b403c9c083ca20682dd3b/latest/en-US

https://discovery-center.cloud.sap/missiondetail/3019/3297/




Thank you.


[email protected]










warranty.














Follow all of SAP








week 3: introduction to the enterprise edition unit 1

Documents