@sap-ai-sdk/orchestration 1.7.1-20250205013109.0 → 1.7.1-20250206013111.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +28 -1
- package/package.json +3 -3
package/README.md
CHANGED
|
@@ -220,6 +220,10 @@ const responseContent = response.getContent();
|
|
|
220
220
|
|
|
221
221
|
Many models in the orchestration service have image recognition capabilities, meaning the models can take images and answer questions about them.
|
|
222
222
|
|
|
223
|
+
> [!Warning]
|
|
224
|
+
> The `image_url` content type can only be used in messages with `role: 'user'`.
|
|
225
|
+
> Attempting to use `image_url` in non-user messages will result in an error.
|
|
226
|
+
|
|
223
227
|
```ts
|
|
224
228
|
import { OrchestrationClient } from '@sap-ai-sdk/orchestration';
|
|
225
229
|
|
|
@@ -230,7 +234,7 @@ const orchestrationClient = new OrchestrationClient({
|
|
|
230
234
|
templating: {
|
|
231
235
|
template: [
|
|
232
236
|
{
|
|
233
|
-
role: 'user',
|
|
237
|
+
role: 'user', // image_url content type is only supported in user messages
|
|
234
238
|
content: [
|
|
235
239
|
{
|
|
236
240
|
type: 'text',
|
|
@@ -406,6 +410,29 @@ Set it to `help.sap.com` to retrieve context from the SAP Help Portal.
|
|
|
406
410
|
Set `data_respotiories` property with an array of `REPOSITORY_ID` values to search in specific data repositories.
|
|
407
411
|
Skip this property to search in all available data repositories.
|
|
408
412
|
|
|
413
|
+
#### Data Masking in Grounding
|
|
414
|
+
|
|
415
|
+
You can also configure masking of the grounding input to anonymize sensitive information while preserving necessary context for the Orchestration service.
|
|
416
|
+
A masking configuration can be added in the grounding example above to mask the grounding input.
|
|
417
|
+
|
|
418
|
+
```ts
|
|
419
|
+
masking: {
|
|
420
|
+
masking_providers: [
|
|
421
|
+
{
|
|
422
|
+
type: 'sap_data_privacy_integration',
|
|
423
|
+
method: 'pseudonymization',
|
|
424
|
+
entities: [{ type: 'profile-email' }, { type: 'profile-person' }],
|
|
425
|
+
mask_grounding_input: {
|
|
426
|
+
enabled: true
|
|
427
|
+
},
|
|
428
|
+
allowlist: ['AI Core']
|
|
429
|
+
}
|
|
430
|
+
];
|
|
431
|
+
}
|
|
432
|
+
```
|
|
433
|
+
|
|
434
|
+
The `allowlist` property allows you to specify terms that should remain unmasked, ensuring important context-specific terminology is preserved in the grounding input.
|
|
435
|
+
|
|
409
436
|
### Using a JSON Configuration from AI Launchpad
|
|
410
437
|
|
|
411
438
|
If you already have an orchestration workflow created in AI Launchpad, you can either download the configuration as a JSON file or copy the JSON string directly to use it with the orchestration client.
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@sap-ai-sdk/orchestration",
|
|
3
|
-
"version": "1.7.1-
|
|
3
|
+
"version": "1.7.1-20250206013111.0",
|
|
4
4
|
"description": "",
|
|
5
5
|
"license": "Apache-2.0",
|
|
6
6
|
"keywords": [
|
|
@@ -21,8 +21,8 @@
|
|
|
21
21
|
],
|
|
22
22
|
"dependencies": {
|
|
23
23
|
"@sap-cloud-sdk/util": "^3.26.0",
|
|
24
|
-
"@sap-ai-sdk/core": "^1.7.1-
|
|
25
|
-
"@sap-ai-sdk/ai-api": "^1.7.1-
|
|
24
|
+
"@sap-ai-sdk/core": "^1.7.1-20250206013111.0",
|
|
25
|
+
"@sap-ai-sdk/ai-api": "^1.7.1-20250206013111.0"
|
|
26
26
|
},
|
|
27
27
|
"devDependencies": {
|
|
28
28
|
"@sap-cloud-sdk/http-client": "^3.26.0",
|