You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: docs/sap-ai-core/consume-models-with-the-harmonized-api-2392d9a.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -26,7 +26,7 @@ curl --request POST $ORCH_DEPLOYMENT_URL/completion \
26
26
}
27
27
},
28
28
"llm_module_config": {
29
-
"model_name": "gpt-35-turbo-16k ",
29
+
"model_name": "gpt-4o-mini",
30
30
"model_params": {
31
31
"max_tokens": 50,
32
32
"temperature": 0.1,
@@ -44,7 +44,7 @@ curl --request POST $ORCH_DEPLOYMENT_URL/completion \
44
44
}'
45
45
```
46
46
47
-
This request configures the templating module with a single user message with two parameters: `text` and `language`. The `language` parameter is also configured with English as the default. The LLM module is configured to use gpt-35-turbo-16k in the latest available version and a set of model parameters. The `input_params` field contains the values for the parameters `text` and `language`. These values are used during this request in the prompt sent to the model.
47
+
This request configures the templating module with a single user message with two parameters: `text` and `language`. The `language` parameter is also configured with English as the default. The LLM module is configured to use gpt-4o-mini in the latest available version and a set of model parameters. The `input_params` field contains the values for the parameters `text` and `language`. These values are used during this request in the prompt sent to the model.
48
48
49
49
The response contains a `request_id`, the module results from each module that was executed, and the `orchestration_result`, which includes the response of the call to the model.
50
50
@@ -63,7 +63,7 @@ The response contains a `request_id`, the module results from each module that w
Copy file name to clipboardexpand all lines: docs/sap-ai-core/create-a-collection-9cbfe27.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@
10
10
11
11
You have created a resource group for grounding purposes. For more information, see [Create a Resource Group for Grounding](create-a-resource-group-for-grounding-6712bfe.md)
12
12
13
-
You have created a generic secret for grounding purposes. For more information, see [Create a Generic Secret for Grounding](create-a-generic-secret-for-grounding-bdea357.md)
13
+
You have created a generic secret for grounding purposes. For more information, see [Grounding Generic Secrets for Microsoft SharePoint](grounding-generic-secrets-for-microsoft-sharepoint-bdea357.md)
Copy file name to clipboardexpand all lines: docs/sap-ai-core/create-a-generic-secret-1831845.md
+14-4
Original file line number
Diff line number
Diff line change
@@ -37,10 +37,15 @@ SAP AI Core lets you optionally use generic secrets at the following levels:
37
37
38
38
Generic secrets are different to system secrets \(such as object store, Docker registry, and so on\) and can be used to store sensitive information, either for the main tenant, for all of its resource groups, or for each resource group via an API. The latter can be attached to containers in executions or deployments as environment variables or volume mounts.
39
39
40
-
Tenant-wide secrets are only automatically propagated to the appropriate resource group when a new execution or deployment is created. They are not propagated to running deployments.
40
+
> ### Note:
41
+
> In order to allow rotation of tenant-wide secrets for long-running deployments without restarting the deployment, the following guidelines must be followed:
42
+
>
43
+
> -> The deployment must mount the tenant-wide secret. For more information see [Consume Generic Secrets in Executions or Deployments](https://help.sap.com/docs/AI_CORE/52b4adb30e6744709d6226d2b0659dea/185a3245692542a78bfeff87220410c6.html).
44
+
> -> The deployment must monitor the mounted secret for changes instead of relying on an in-memory copy of the secret read from the mount.
45
+
> -> When a tenant-wide secret is updated, the tenant is responsible for observing the `resourceGroupSecretReplicationStatus` field of the `Get Secret` endpoint, to ensure that the replicator has successfully updated the secret in the required resource groups. For more information, see [Create a Generic Secret](https://help.sap.com/docs/AI_CORE/52b4adb30e6744709d6226d2b0659dea/1831845910364e97b3a7c6644a9e1f4b.html).
41
46
42
47
> ### Note:
43
-
> Each tenant can have a maximum of five tenant-wide secrets. If you reach this limit, you'll receive an error message. To free up space, you can delete some tenant-wide secrets as described at [Delete a Generic Secret](delete-a-generic-secret-d5d5187.md). Alternatively, you can submit a ticket to request an increase your quota.
48
+
> Each tenant can have a maximum of five tenant-wide secrets. If you reach this limit, you'll receive an error message. To free up space, you can delete some tenant-wide secrets as described at [Delete a Generic Secret](delete-a-generic-secret-d5d5187.md). Alternatively, you can submit a ticket to request an increase in your quota.
44
49
45
50
46
51
@@ -103,10 +108,15 @@ SAP AI Core lets you optionally use generic secrets at the following levels:
103
108
104
109
Generic secrets are different to system secrets \(such as object store, Docker registry, and so on\) and can be used to store sensitive information, either for the main tenant, for all of its resource groups, or for each resource group via an API. The latter can be attached to containers in executions or deployments as environment variables or volume mounts.
105
110
106
-
Tenant-wide secrets are only automatically propagated to the appropriate resource group when a new execution or deployment is created. They are not propagated to running deployments.
111
+
> ### Note:
112
+
> In order to allow rotation of tenant-wide secrets for long-running deployments without restarting the deployment, the following guidelines must be followed:
113
+
>
114
+
> -> The deployment must mount the tenant-wide secret. For more information see [Consume Generic Secrets in Executions or Deployments](https://help.sap.com/docs/AI_CORE/52b4adb30e6744709d6226d2b0659dea/185a3245692542a78bfeff87220410c6.html).
115
+
> -> The deployment must monitor the mounted secret for changes instead of relying on an in-memory copy of the secret read from the mount.
116
+
> -> When a tenant-wide secret is updated, the tenant is responsible for observing the `resourceGroupSecretReplicationStatus` field of the `Get Secret` endpoint, to ensure that the replicator has successfully updated the secret in the required resource groups. For more information, see [Create a Generic Secret](https://help.sap.com/docs/AI_CORE/52b4adb30e6744709d6226d2b0659dea/1831845910364e97b3a7c6644a9e1f4b.html).
107
117
108
118
> ### Note:
109
-
> Each tenant can have a maximum of five tenant-wide secrets. If you reach this limit, you'll receive an error message. To free up space, you can delete some tenant-wide secrets as described at [Delete a Generic Secret](delete-a-generic-secret-d5d5187.md). Alternatively, you can submit a ticket to request an increase your quota.
119
+
> Each tenant can have a maximum of five tenant-wide secrets. If you reach this limit, you'll receive an error message. To free up space, you can delete some tenant-wide secrets as described at [Delete a Generic Secret](delete-a-generic-secret-d5d5187.md). Alternatively, you can submit a ticket to request an increase in your quota.
Copy file name to clipboardexpand all lines: docs/sap-ai-core/data-masking-8b87002.md
+14-14
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ The data masking module is optional and serves to anonymize or pseudonymize pers
6
6
7
7
There are two ways in which you can mask data:
8
8
9
-
-Anonmyization replaces personally identifiable information in chosen categories with a `MASKED_ENTITY` placeholder. Anonymized data can't be unmasked because the original data isn't retained.
9
+
-Anonymization replaces personally identifiable information in chosen categories with a `MASKED_ENTITY` placeholder. Anonymized data can't be unmasked because the original data isn't retained.
10
10
- Pseudonymization substitutes personally identifiable information in selected categories with a `MASKED_ENTITY_ID` placeholder. Pseudonymized data can be unmasked in the response.
11
11
12
12
The module currently supports the following anonymization services:
@@ -118,7 +118,7 @@ Phone Number
118
118
</td>
119
119
<tdvalign="top">
120
120
121
-
International phone numbers in the following format: +country code, any prefix and phone number
121
+
International phone numbers in the following format: +country/region code, any prefix and phone number
122
122
123
123
</td>
124
124
</tr>
@@ -147,12 +147,12 @@ profile-email
147
147
</td>
148
148
<tdvalign="top">
149
149
150
-
Email addresses
150
+
E-mail addresses
151
151
152
152
</td>
153
153
<tdvalign="top">
154
154
155
-
Email addresses
155
+
E-mail addresses
156
156
157
157
</td>
158
158
</tr>
@@ -169,7 +169,7 @@ SAP Staff User ID Numbers
169
169
</td>
170
170
<tdvalign="top">
171
171
172
-
UserID: Sequence of characters that starts with either C, I, or D followed by 6-8 digits.
172
+
User ID: Sequence of characters that starts with either C, I, or D followed by 6-8 digits.
173
173
174
174
</td>
175
175
</tr>
@@ -186,9 +186,9 @@ Public SAP Accounts
186
186
</td>
187
187
<tdvalign="top">
188
188
189
-
S-userid: Sequence of characters that starts with S and followed by 6-11 digits.
189
+
S-user ID: Sequence of characters that starts with S and followed by 6-11 digits.
190
190
191
-
P-userid: Sequence of characters that starts with P followed by 10 digits.
191
+
P-user ID: Sequence of characters that starts with P followed by 10 digits.
192
192
193
193
</td>
194
194
</tr>
@@ -222,7 +222,7 @@ Username and Passwords
222
222
</td>
223
223
<tdvalign="top">
224
224
225
-
Detected if words similar to user, username, pass, passwords, etc.
225
+
Detected if words similar to user, user name, pass, passwords, and so on.
226
226
227
227
</td>
228
228
</tr>
@@ -239,7 +239,7 @@ National ID Number
239
239
</td>
240
240
<tdvalign="top">
241
241
242
-
20+ countries/regions \(e.g., E.U., South America\)
242
+
20+ countries/regions \(for example, E.U., South America\)
243
243
244
244
</td>
245
245
</tr>
@@ -307,7 +307,7 @@ Passport Number
307
307
</td>
308
308
<tdvalign="top">
309
309
310
-
30+ countries/regions \(e.g., E.U., Asia Pacific, North America\)
310
+
30+ countries/regions \(for example, E.U., Asia Pacific, North America\)
311
311
312
312
</td>
313
313
</tr>
@@ -324,7 +324,7 @@ Driver's License
324
324
</td>
325
325
<tdvalign="top">
326
326
327
-
30+ countries/regions \(e.g., E.U., Asia Pacific\)
327
+
30+ countries/regions \(for example, E.U., Asia Pacific\)
328
328
329
329
</td>
330
330
</tr>
@@ -341,7 +341,7 @@ Nationality
341
341
</td>
342
342
<tdvalign="top">
343
343
344
-
190+ country names, official country names, and country codes
344
+
190+ country/region names, official country/region names, and country/region codes
345
345
346
346
</td>
347
347
</tr>
@@ -467,9 +467,9 @@ Mixed
467
467
</table>
468
468
469
469
> ### Caution:
470
-
> The masking service can obscure personally identifiable information in prompts. However, since it relies on automated detection mechanisms, it can't guarantee that all such information will be identified and masked.
470
+
> The masking service can obscure personally identifiable information in prompts. However, since it relies on automated detection mechanisms, it can't guarantee that all such information is identified and masked.
471
471
>
472
-
> Anonymization replaces personally identifiable information in an irreversible way. This leads to a loss of context, which may limit the model's ability to process the input. For instance, if tasked with writing a story about Michael and Donna, anonymization of profile-person would result in a story about `MASKED_PERSON` and `MASKED_PERSON`, making it impossible to distinguish between the two.
472
+
> Anonymization replaces personally identifiable information in an irreversible way. As a result, context can be lost, which can limit the model's ability to process the input. For instance, if tasked with writing a story about Michael and Donna, anonymization of profile-person results in a story about `MASKED_PERSON` and `MASKED_PERSON`, making it impossible to distinguish between the two.
473
473
474
474
-**[Enhancing Model Consumption with Data Masking](enhancing-model-consumption-with-data-masking-592c570.md"")**
The following data repositories are supported in the grounding module:
8
+
9
+
- Microsoft SharePoint
10
+
11
+
The following authentication types for each document repository type:
12
+
13
+
- Microsoft SharePoint
14
+
- OAuth2Password
15
+
16
+
- OAuth2ClientCredentials
17
+
18
+
19
+
20
+
To onboard a Microsoft SharePoint repository, see [Grounding Generic Secrets for Microsoft SharePoint](grounding-generic-secrets-for-microsoft-sharepoint-bdea357.md)
21
+
22
+
-**[Grounding Generic Secrets for Microsoft SharePoint](grounding-generic-secrets-for-microsoft-sharepoint-bdea357.md"")**
Copy file name to clipboardexpand all lines: docs/sap-ai-core/get-a-repository-a64179d.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -10,7 +10,7 @@
10
10
11
11
You have created a resource group for grounding purposes. For more information, see [Create a Resource Group for Grounding](create-a-resource-group-for-grounding-6712bfe.md)
12
12
13
-
You have created a generic secret for grounding purposes. For more information, see [Create a Generic Secret for Grounding](create-a-generic-secret-for-grounding-bdea357.md)
13
+
You have created a generic secret for grounding purposes. For more information, see [Grounding Generic Secrets for Microsoft SharePoint](grounding-generic-secrets-for-microsoft-sharepoint-bdea357.md)
0 commit comments