Skip to content

Commit 872cd82

Browse files
committed
updates on tutorials
1 parent 327a744 commit 872cd82

File tree

5 files changed

+30
-52
lines changed

5 files changed

+30
-52
lines changed

tutorials/add-authorization/add-authorization.md

Lines changed: 4 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -98,10 +98,6 @@ CAP offers a possibility to add local users for testing as part of the `cds` con
9898
"auth": {
9999
"kind": "mocked",
100100
"users": {
101-
102-
"password": "initial",
103-
"roles": ["support"]
104-
},
105101
"alice": {
106102
"roles": ["support"]
107103
},
@@ -117,9 +113,8 @@ CAP offers a possibility to add local users for testing as part of the `cds` con
117113
118114
Each user entry is part of the `users` object. The key is the `id` of the user and they can have different properties. For this scenario, you define a `password` and an array of roles.
119115
120-
You have added three users:
116+
You have added two users:
121117
122-
- `[email protected]` with the `support` role and the `initial` password
123118
- `alice` with the `support` role and no password
124119
- `bob` with the `support` role and no password
125120
@@ -178,11 +173,11 @@ When accessing the **Incidents** service of the **Incident Management** applicat
178173
>2. Choose **Fiori: Open Application Info**.
179174
180175
181-
3. In the **Username** field of the auth popup, enter `[email protected]`.
176+
3. In the **Username** field of the auth popup, enter `alice`.
182177
183-
4. In the **Password** field, enter `initial`.
178+
4. Leave the **Password** field empty.
184179
185-
<!-- border; size:540px --> ![Sign In Incident Management Application](./local-login.png)
180+
<!-- border; size:540px --> ![Sign In Incident Management Application](./local-login-java.png)
186181
187182
You can now access the **Incident Management** application.
188183

tutorials/build-cap-app/build-cap-app.md

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -511,22 +511,22 @@ Replace the respective generated CSV templates with the following content:
511511
- `db/data/sap.capire.incidents-Status.csv`:
512512
513513
```csv
514-
code;descr;criticality
515-
N;New;3
516-
A;Assigned;2
517-
I;In Process;2
518-
H;On Hold;3
519-
R;Resolved;2
520-
C;Closed;4
514+
code,descr,criticality
515+
N,New,3
516+
A,Assigned,2
517+
I,In Process,2
518+
H,On Hold,3
519+
R,Resolved,2
520+
C,Closed,4
521521
```
522522
523523
- `db/data/sap.capire.incidents-Urgency.csv`:
524524
525525
```csv
526-
code;descr
527-
H;High
528-
M;Medium
529-
L;Low
526+
code,descr
527+
H,High
528+
M,Medium
529+
L,Low
530530
```
531531
532532
> Notice that `cds add data` created eight files, while we're adding data to just six of them. We're leaving the files `sap.capire.incidents-Status.texts.csv` and `sap.capire.incidents-Urgency.texts.csv` empty because they hold translated text that will be filled once the application is localized and translations are created.

tutorials/prep-for-prod/prep-for-prod.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -653,4 +653,10 @@ You should get an output like:
653653
[INFO] ------------------------------------------------------------------------
654654
```
655655
656-
[OPTION END]
656+
[OPTION END]
657+
658+
### Deployment Options
659+
660+
Now that you have prepared your CAP application for deployment, you can choose from the following deployment options:
661+
- Follow the tutorials in the [Deploy a Full-Stack CAP Application in SAP BTP, Cloud Foundry Runtime Following SAP BTP Developer’s Guide](https://developers.sap.com/group.deploy-full-stack-cap-application.html) group to deploy the application in the SAP BTP, Cloud Foundry runtime.
662+
- Follow the tutorials in the [Deploy a Full-Stack CAP Application in SAP BTP, Kyma Runtime Following SAP BTP Developer’s Guide](https://developers.sap.com/group.deploy-full-stack-cap-kyma-runtime.html) group to deploy the application in the SAP BTP, Kyma runtime.
4.94 KB
Loading
Lines changed: 8 additions & 31 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Assign the User Roles
3-
description: This tutorial shows you how to assign roles to users.
3+
description: This tutorial shows you how to assign role collections to users.
44
parser: v2
55
auto_validation: true
66
time: 15
@@ -12,12 +12,12 @@ author_profile: https://github.com/slavipande
1212

1313
## You will learn
1414

15-
- How to create and assign a role collection in the SAP BTP subaccount.
15+
- How to assign a role collection in the SAP BTP subaccount.
1616

1717

1818
## Prerequisites
1919

20-
- You have deployed your application in either the SAP BTP, Cloud Foundry runtime or the SAP BTP, Kyma runtime. For deploying in the SAP BTP, Cloud Foundry runtime, follow the steps in the [Deploy in SAP BTP, Cloud Foundry Runtime](deploy-to-cf) tutorial that is part of the [Deploy a Full-Stack CAP Application in SAP BTP, Cloud Foundry Runtime Following SAP BTP Developer’s Guide](https://developers.sap.com/group.deploy-full-stack-cap-application.html) tutorial group. For deploying in the SAP BTP, Kyma runtime, follow the steps in the [Deploy in SAP BTP, Kyma Runtime](deploy-to-kyma) tutorial that is part of the [Deploy a Full-Stack CAP Application in SAP BTP, Kyma Runtime Following SAP BTP Developer’s Guide](https://developers.sap.com/group.deploy-full-stack-cap-kyma-runtime.html) tutorial group.
20+
- You have deployed your application in either the SAP BTP, Cloud Foundry runtime or the SAP BTP, Kyma runtime. For deploying in the SAP BTP, Cloud Foundry runtime, follow the steps in the [Deploy in SAP BTP, Cloud Foundry Runtime](deploy-to-cf) tutorial that is part of the [Deploy a Full-Stack CAP Application in SAP BTP, Cloud Foundry Runtime Following SAP BTP Developer’s Guide](https://developers.sap.com/group.deploy-full-stack-cap-application.html) tutorial group. For deploying in the SAP BTP, Kyma runtime, follow the steps in the [Deploy in SAP BTP, Kyma Runtime](deploy-to-kyma) tutorial that is part of the [Deploy a Full-Stack CAP Application in SAP BTP, Kyma Runtime Following SAP BTP Developer’s Guide](https://developers.sap.com/group.deploy-full-stack-cap-kyma-runtime.html) tutorial group.
2121
- You have an [enterprise global account](https://help.sap.com/docs/btp/sap-business-technology-platform/getting-global-account#loiod61c2819034b48e68145c45c36acba6e) in SAP BTP. To use services for free, you can sign up for an SAP BTPEA (SAP BTP Enterprise Agreement) or a Pay-As-You-Go for SAP BTP global account and make use of the free tier services only. See [Using Free Service Plans](https://help.sap.com/docs/btp/sap-business-technology-platform/using-free-service-plans?version=Cloud).
2222
- You have a platform user. See [User and Member Management](https://help.sap.com/docs/btp/sap-business-technology-platform/user-and-member-management).
2323
- You are an administrator of the global account in SAP BTP.
@@ -31,45 +31,22 @@ author_profile: https://github.com/slavipande
3131

3232
> This tutorial follows the guidance provided in the [SAP BTP Developer's Guide](https://help.sap.com/docs/btp/btp-developers-guide/what-is-btp-developers-guide).
3333
34-
### Create a role collection and add role
35-
36-
1. Open the SAP BTP cockpit and navigate to your subaccount.
37-
38-
1. Choose **Security** &rarr; **Role Collections**, and then choose **Create**.
39-
40-
<!-- border; size:540px --> ![Role Collections](./create-role-collection.png)
41-
42-
2. In the **Create Role Collection** popup, enter **Incident Management Support** in the **Name** field and choose **Create**.
43-
44-
<!-- border; size:540px --> ![Create Role Collection](./create-role-collection-popup.png)
45-
46-
3. Choose the role collection **Incident Management Support** from the list of role collections and choose **Edit** on the right.
47-
48-
<!-- border; size:540px --> ![Edit Role Collection](./edit-role-collection.png)
49-
50-
4. Open the value help in the **Role Name** field.
51-
52-
<!-- border; size:540px --> ![Value Help](./role-value-help.png)
53-
54-
5. Search for the role **support**, select it, and choose **Add**.
55-
56-
<!-- border; size:540px --> ![Add Role](./add-role.png)
57-
58-
6. Choose **Save**.
5934

6035
### Assign a role collection to a user
6136

6237

63-
1. Choose **Security** &rarr; **Users**, and then choose a user from the list.
38+
1. Choose **Security** &rarr; **Users**, and then choose a user from the list.
6439

6540
2. Under **Role Collections** on the right, choose **Assign Role Collection**.
6641

6742
<!-- border; size:540px --> ![role collection](./rolecollection1.png)
6843

69-
2. In the **Assign Role Collection** dialog, select the **Incident Management Support** role collection and choose **Assign Role Collection**.
44+
The role collections **admin** and **support** are automatically generated during deployment.
45+
46+
2. In the **Assign Role Collection** dialog, select the **support** role collection and choose **Assign Role Collection**.
7047

7148
<!-- border; size:540px --> ![role collection](./rolecollection11.png)
7249

73-
You have assigned the **Incident Management Support** role collection to your user.
50+
You have assigned the role collection to your user.
7451

7552
> You might need to log out and log back in to make sure your new role collection is taken into account.

0 commit comments

Comments
 (0)