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
feat: add sample file processing as post-deployment step 4
- Add bundle_info.json manifests for claim_date_of_loss and claim_hail
- Add Step 4 to post_deployment.ps1 and post_deployment.sh
- Creates claim batch with schemaset ID
- Uploads files with mapped schema IDs
- Submits batch for workflow processing
- Update DeploymentGuide.md with new step and sample output
- Update AVMPostDeploymentGuide.md with manual sample processing instructions
- Normalize output prefixes: ASCII dashes for ps1, emojis for sh
Copy file name to clipboardExpand all lines: docs/AVMPostDeploymentGuide.md
+18-4Lines changed: 18 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,9 +11,10 @@ This document provides guidance on post-deployment steps after deploying the Con
11
11
After successfully deploying the Content Processing Solution Accelerator using the AVM template, you need to:
12
12
13
13
1.**Register schemas** — upload schema files, create a schema set, and link them together
14
-
2.**Configure authentication** — set up app registration for secure access
14
+
2.**Process sample files** — upload and process sample claim bundles for verification
15
+
3.**Configure authentication** — set up app registration for secure access
15
16
16
-
> **Note:** When deploying via `azd up`, schema registration happens automatically through a post-provisioning hook. AVM deployments require the manual steps below.
17
+
> **Note:** When deploying via `azd up`, schema registration and sample processing happen automatically through a post-provisioning hook. AVM deployments require the manual steps below.
17
18
18
19
## Prerequisites
19
20
@@ -73,14 +74,27 @@ The script is idempotent — it skips schemas and schema sets that already exist
73
74
74
75
> **Want custom schemas?** See [Customize Schema Data](./CustomizeSchemaData.md) to create your own document schemas.
75
76
76
-
### Step 4: Configure Authentication (Required)
77
+
### Step 4: Process Sample File Bundles (Optional)
78
+
79
+
After schema registration, you can upload and process the included sample claim bundles to verify the deployment is working end to end. Each sample folder (`claim_date_of_loss/`, `claim_hail/`) contains a `bundle_info.json` manifest that maps files to their schema classes.
80
+
81
+
The workflow for each bundle:
82
+
1.**Create a claim batch** with the schema set ID via `PUT /claimprocessor/claims`
83
+
2.**Upload each file** with its mapped schema ID via `POST /claimprocessor/claims/{claim_id}/files`
84
+
3.**Submit the batch** for processing via `POST /claimprocessor/claims`
85
+
86
+
You can perform these steps via the web UI or the API directly. See the [API documentation](./API.md) and [Golden Path Workflows](./GoldenPathWorkflows.md) for details.
87
+
88
+
> **Note:** When deploying via `azd up`, sample file processing happens automatically as Step 4 of the post-provisioning hook.
89
+
90
+
### Step 5: Configure Authentication (Required)
77
91
78
92
**This step is mandatory for application access:**
Copy file name to clipboardExpand all lines: docs/DeploymentGuide.md
+29-4Lines changed: 29 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -311,6 +311,7 @@ Schema registration happens **automatically** as part of the `azd up` post-provi
311
311
2. Registers the sample schema files (auto claim, damaged car image, police report, repair estimate)
312
312
3. Creates an **"Auto Claim"** schema set
313
313
4. Adds all registered schemas into the schema set
314
+
5. Processes sample file bundles (`claim_date_of_loss/` and `claim_hail/`) — creates claim batches, uploads files with their mapped schemas, and submits them for processing
314
315
315
316
After successful deployment, the terminal displays container app details and schema registration output:
316
317
@@ -358,7 +359,29 @@ Schema registration process completed.
@@ -420,10 +443,12 @@ The automation is fully compatible with the WAF / production profile (`main.waf.
420
443
421
444
### 5.4 Test the Application
422
445
446
+
>**Note:** The post-deployment hook automatically uploads and processes two sample claim bundles (`claim_date_of_loss` and `claim_hail`). You can verify the results in the web app immediately after deployment.
447
+
423
448
**Quick Test Steps:**
424
-
1. **Download Samples**: Get sample files from the [samples directory](../src/ContentProcessorAPI/samples) — use the `claim_date_of_loss/` or `claim_hail/` folders for auto claim documents.
425
-
2. **Upload**: In the app, selectthe**"Auto Claim"** schema set, choose a schema (e.g., Auto Insurance Claim Form), click Import Content, and upload a sample file.
426
-
3. **Review**: Wait for completion (~1 min), then click the row to verify the extracted data against the source document.
449
+
1. **Check Processed Results**: Open the web app — you should see the two sample claim batches already processed with extracted data.
450
+
2. **Review**: Click a processed claim row to verify the extracted data against the source document.
451
+
3. **Upload More (Optional)**: To test additional uploads, get sample files from the [samples directory](../src/ContentProcessorAPI/samples), selectthe**"Auto Claim"** schema set, and upload via Import Content.
427
452
428
453
📖 **Detailed Instructions:** See the complete [Golden Path Workflows](./GoldenPathWorkflows.md) guide for step-by-step testing procedures.
0 commit comments