> For the complete documentation index, see [llms.txt](https://docs.ovaledge.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ovaledge.com/release8.2/askedgi/administration-and-governance/service-desk-integration.md). # Service Desk Integration This article explains how to configure the Legacy Data Quality Status property in Service Desk templates. It describes how this property enables organizations to capture approved legacy data quality issues and preserve remediation context for future analysis. When a Data Quality service request is marked as a Legacy Data Quality Issue, the system automatically captures the approved corrective action and stores it as data cleanup context for the associated object. This context is then available for downstream processes, including askEdgi and Retrieval-Augmented Generation (RAG), to support governed data cleanup and business-aware analysis. ### Service Desk Templates A new template-level property, Legacy Data Quality Status, is introduced to support capturing and storing historical data quality issue context. This capability is designed to ensure that data quality remediation insights are preserved and made available for downstream systems, including RAG-based context retrieval. The feature is applicable only to Data Quality Issue request types and is controlled through template configuration. ### Template Property Configuration A new configuration property is introduced at the template level: * Property Name: Legacy Data Quality Status * Configuration Key: legacydataqualitystatus * Type: Checkbox (True / False) **Default Behavior** * Default value: False * For Data Quality templates: Enabled (True) by default * Hidden for all other template types **Functional Behavior** When the Legacy Data Quality Status property is enabled: 1. A new status becomes available: 2. Status: Legacy Data Quality Issue 3. Action: Mark as Legacy Issue 4. When a service request is moved to this status: 5. A backend fulfillment job is triggered automatically 6. The job captures and stores data quality context 7. This process is system-driven and does not require user intervention beyond status change **Job Behavior** An internal fulfillment job is triggered when the request status changes to Legacy Data Quality Issue. **Key Characteristics:** * This is a system-level job * It is not visible in the UI * It is automatically linked to the template property ### Context Capture Logic When the status is moved to Legacy Data Quality Issue: 1. The system reads the Corrective Action field provided by the approver 2. If the field contains data: 3. The content is stored as data cleanup context 4. The context is attached to the corresponding object 5. If the field is empty: 6. No context is captured This context is then used for downstream processing, including RAG-based retrieval. **askEdgi Integration** * When a request is marked as Legacy Data Quality Issue, the associated context is captured for that object * Context is stored at the object level (Table/File) * Multiple contexts can exist for the same object This enables improved contextual understanding for future analysis and recommendations. ### Status and Action A new system-defined action and status are introduced: * Action: Mark as Legacy Issue * Status: Legacy Data Quality Issue This status is controlled by the template property and is available only for Data Quality Issue requests. **Scope:** * System-controlled * Enabled/disabled through template configuration *** Copyright © 2026, OvalEdge LLC, Peachtree Corners, GA USA --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.ovaledge.com/release8.2/askedgi/administration-and-governance/service-desk-integration.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.