Insurance Claim Processing with Document Upload using OmniScript

Overview

This use case enables customers to submit insurance claims through an OmniScript interface. During the submission process, customers can upload documents such as damage images, reports, or any other supporting files. These documents are stored as ContentVersion records and are linked to the corresponding custom object Insurance_Claim__c record. A summary screen at the end shows both the claim details and the uploaded file names.

Step-by-Step Implementation

Tools & Technologies Used

Object Model

Step 1: Custom Object: Insurance_Claim__c

This object stores all claim-related data entered by the user.

Fields Used:

Step 2: Create OmniScript

Navigate to OmniStudio > OmniScripts, and create a new OmniScript:

Step 3: Add Elements to OmniScript

1. Claim Information Step

This is the first step where the user provides the details about their insurance claim.

Input Fields to Add:

Submit Claim

• Add a DataRaptor Post Action
• Use a DataRaptor Turbo to save the claim into Insurance_Claim__c
• Store the returned Id in a variable (e.g., %ClaimId%)

Upload Files

• Add a File Upload element
• Configure:
  
  
  • Document Object: ContentVersion
  • Parent Id: %ClaimId%
  • Allow Multiple Files: Yes
  • Max File Size: Optional (e.g., 5MB)

Summary Screen with Input Text

• Add a DataRaptor Extract to get files:
  
  
  • Object: ContentVersion
  • Filter: FirstPublishLocationId = %ClaimId%
  • Output fields: Id, Title
• Add Input Text elements (Read-only):
  
  • Label: Uploaded File 1

File Upload Configuration Summary

DataRaptor Configuration

DataRaptor Turbo (Post) – Insurance Claim Creation

Object: Insurance_Claim__c

Operation: Create / Upsert

Interface Type: Load

Input Type: JSON

Output Type: SObject

Field Mappings

Attachment Linking

To associate uploaded files:

• Use ContentDocumentLink
• Set LinkedEntityId = ID of the created Insurance_Claim__c record

Example of Input Text on Summary Screen

Claim Submitted Successfully!

   Uploaded Documents:
   [ Input Text: PoliceReport.pdf - /sfc/servlet.shepherd/document/download/069XXXXXX ]
   [ Input Text: DamagePhoto.jpg - /sfc/servlet.shepherd/document/download/069YYYYYY ]
   

These Input Text fields are marked as Read Only and show both file name and download link.

Final Output

At the end of this flow:

• Insurance_Claim__c is created
• Files uploaded via File Upload are stored as ContentVersion
• Files are linked to the Claim using FirstPublishLocationId
• User sees a summary screen with file names and links inside Input Text fields

Final Thought

By leveraging Salesforce OmniStudio’s low-code capabilities, this solution offers a clean and efficient way for customers to submit insurance claims and upload supporting documents, without relying on Apex or Integration Procedures.

This process enhances the customer experience through guided OmniScript flows, stores documents securely as ContentVersion records, and provides a clear summary of uploaded files all while ensuring scalability and maintainability.

This approach reflects how Astrea IT Services utilizes declarative tools to deliver real-world business solutions with agility and professionalism.

Have questions or need assistance? Feel free to contact us at support@astreait.com