Skip to content

Commit 513bba8

Browse files
authored
fix formatting
1 parent 7f5b4f7 commit 513bba8

1 file changed

Lines changed: 12 additions & 12 deletions

File tree

tutorials/ai-core-orchestration-grounding/ai-core-orchestration-Grounding.md

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -355,7 +355,7 @@ Generic secrets securely store SharePoint credentials required for document acce
355355
356356
• Enter the secret in JSON format. For example:
357357
358-
```CODE
358+
```json
359359
{
360360

361361
"type": "SFRUUA==",
@@ -533,9 +533,9 @@ secret.json()
533533
534534
[OPTION BEGIN [Bruno]]
535535
536-
### 7.a Using Pipeline API
536+
#### 7.a Using Pipeline API
537537
538-
#### Create Pipeline
538+
##### Create Pipeline
539539
540540
- Pipelines define the process for grounding and retrieving content from SharePoint repositories.
541541
@@ -551,29 +551,29 @@ In this use case, we have added facility management emails as grounding document
551551
552552
![img](img/image014.png)
553553
554-
#### Get All Pipelines
554+
##### Get All Pipelines
555555
556556
This request retrieves a list of all existing pipelines within the resource group. It helps in managing and monitoring available pipelines for orchestration.
557557
558558
![img](img/image031.png)
559559
560-
#### Get Pipeline by Pipeline ID
560+
##### Get Pipeline by Pipeline ID
561561
562562
This request fetches details of a specific pipeline using its unique ID. It is useful for verifying the configuration and settings of a particular pipeline.
563563
564564
![img](img/image032.png)
565565
566-
#### Get Pipeline Status by Pipeline ID
566+
##### Get Pipeline Status by Pipeline ID
567567
568568
This request checks the current status of a specific pipeline, such as whether it is running, completed, or failed. It helps in tracking the execution progress.
569569
570570
![img](img/image033.png)
571571
572572
Once the pipeline is successfully created, documents uploaded in SharePoint are converted into vectors via APIs. The conversion process can be validated upon successful pipeline execution.
573573
574-
### 7.b Using Vector API
574+
#### 7.b Using Vector API
575575
576-
#### Create collection
576+
##### Create collection
577577
578578
• Expand 06_vector and select create_collections request.
579579
@@ -585,7 +585,7 @@ Once the pipeline is successfully created, documents uploaded in SharePoint are
585585
586586
![img](img/image066.png)
587587
588-
#### Create documents
588+
##### Create documents
589589
590590
• Click on the create_document request and replace the path parameter with the valid collection ID.
591591
@@ -595,7 +595,7 @@ Once the pipeline is successfully created, documents uploaded in SharePoint are
595595
596596
![img](img/image067.png)
597597
598-
#### Verifying Vector Processing (Optional)
598+
##### Verifying Vector Processing (Optional)
599599
600600
These steps help inspect vector collections and documents to confirm successful processing.
601601
@@ -635,7 +635,7 @@ These steps help inspect vector collections and documents to confirm successful
635635
636636
[OPTION BEGIN [JavaScript SDK]]
637637
638-
### 7.a Using Pipeline API
638+
#### 7.a Using Pipeline API
639639
640640
In this step, we will create a document-grounding pipeline in SAP AI Core using the `@sap-ai-sdk/document-grounding` package of the [SAP Cloud SDK for AI (JavaScript)](https://github.com/SAP/ai-sdk-js/tree/main/packages/document-grounding).
641641
@@ -680,7 +680,7 @@ console.log('Created Pipeline with ID:', pipeline?.pipelineId);
680680
681681
```
682682
683-
### 7.b Using Vector API
683+
#### 7.b Using Vector API
684684
685685
we are creating a document-grounding pipeline using SAP AI Core. The pipeline is configured to integrate with Microsoft SharePoint as a data source, enabling AI-driven document processing. This setup allows seamless ingestion of documents from a specified SharePoint site, ensuring efficient data retrieval and processing.
686686

0 commit comments

Comments
 (0)