--- title: "Comprehensive Guide to Multimodal AI Assessment Configuration" slug: "configuring-ai-assessment" description: "Discover how to configure and utilise the Multimodal AI Assessment rule to enhance your system's analysis capabilities. Learn step-by-step setup today." status: "update" updated: 2026-10-30T08:25:04Z published: 2026-10-30T08:25:04Z canonical: "documentation.encodify.com/configuring-ai-assessment" --- > ## Documentation Index > Fetch the complete documentation index at: https://documentation.encodify.com/llms.txt > Use this file to discover all available pages before exploring further. # Configuring Multimodal AI Assessment This guide provides an end-to-end operational overview of how to configure, deploy, and manage the Multimodal AI Assessment rule within the platform. This advanced functionality enables your system to transmit structured text data and media files from specified modules directly to an artificial intelligence service, subsequently capturing and recording the analytical results back into your system workflow. ## Rule Configuration The configuration is divided into five primary configuration steps. ### Step 1: Basic Info and Triggering Conditions Defines the rule's identity and the specific trigger criteria. | Field | Description | | --- | --- | | **Name** | Enter a unique name for the rule (e.g., "Product Compliance Review"). | | **Description** | (Optional) Briefly explain the purpose of this AI assessment. | | **Active Toggle** | Ensure this is switched On for the rule to run. | | **Type** | Select Multimodal AI Assessment from the dropdown. | | **Sort Order** | Determines the priority if multiple rules are triggered simultaneously. | | **Module** | Select the primary module (e.g., Products) that will trigger the assessment. | | **IF Condition** | Set the criteria that must be met for the rule to be executed. | ### Step 2: Fields from Main Item Identifies which specific field data from the main item should be sent to the AI. | Field | Description | | --- | --- | | **Analyzed Module** | This defaults to the module selected in the **Conditions** section. | | **Analyze Data in Fields** | Click **Add Field** to specify the field data you want the AI to evaluate. It is also possible to select File fields and define whether the original file or its rendition should be sent for evaluation. After selecting direct module link field from main module to linked module - fields from referenced module become available for selection in **"Analyse Data in Fields from ..."** section.Note: only one hope is supported | ### Step 3: Fields from Linked Modules Select additional data from linked modules to be sent to the AI. | Field | Description | | --- | --- | | **Linked Module** | Select the linked module. Note that only modules with module links to the main module can be selected. Direct links from the main module to linked modules are not supported. | | **Link Field** | Identify the field that connects the two modules. | | **Filter by Field/Values** | (Optional) Narrow down which linked items are sent (e.g., only items where Status is "Available" or "Ready"). | | **Analyse Data in Fields** | Select the field(s) to send. | | **Media Holder** | For file fields, specify if the original file or rendition is sent for assessment. | ### Step 4: AI Instructions Defines the exact directive and analytical framework communicated to the AI. | Field | Description | | --- | --- | | **Prompt for AI** | Utilise the rich text editor to compose clear, concise, and unambiguous instructions. The prompt input field natively supports Markdown formatting for enhanced structural clarity. | | **Example High-Level Directives** | "Analyze the provided product description and the attached media files. Check for brand consistency and safety compliance. Return a risk score and a brief summary." | | **Enable Grounding** | When enabled, the AI may use external search results to supplement the assessment. | > It is recommended to use Google [Gemini](https://gemini.google.com/) or [AI Studio](https://aistudio.google.com/) to develop solid prompts before adding to the Encodify platform. Other Generative AI platforms might yield similar results. ### Step 5: Storing the Results Define how the AI's response should be stored. | Field | Description | | --- | --- | | **Storage Method** | Choose between **Save in Current Item** or **Create Inline Item**. | | **Status Field Mapping** | Map the statuses to your main module's field options so you can track progress (e.g., Map "*In Progress*," "*Completed Successfully,*" and "*Failed*"). | The AI’s output field mapping is the same regardless of which save method is selected. Saving to a separate module will require the target module and linked field to be specified. | Field | Description | | --- | --- | | **Confidence Score** | Usually a numeric (decimal) or text field. | | **Assessment** | Text or Text box field to store assessment result. | | **Status Code & Error Message** | Vital for troubleshooting failed calls. | ## Rule Execution Logic This rule does not, contrary to other rules, have a subtype or event that triggers it. Instead, it is governed by the following logic: | Logic Component | Description | | --- | --- | | **Action Trigger** | Execution is triggered by a Create or Update action on the main item within the selected main module. | | **Status Gatekeeper** | The rule will only run if the mapped **Status** field value does not equal the options mapped as "In Progress," "Failed," or "Completed Successfully." This prevents infinite loops. | | **Filter Match** | The item must meet the specific criteria defined in the Conditions section (if any). | Once triggered, the item status will shift to **"In Progress"** until the AI service returns the data to the mapped result fields. Successful assessments will set the main item’s status to the option mapped as **“Completed Successfully“.** ## Technical Limitations and Troubleshooting To ensure seamless execution, prevent infinite loops, and avoid file evaluation failures, all AI automation rules must operate within specific technical boundaries. All guidelines regarding **payload constraints**, **status gatekeeping**, **race conditions**, **file naming, etc.** are centralised in our [foundational documentation](/v1/docs/generative-ai-based-rules).