> 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/minor-release/release8.2/release-notes/general-advanced-jobs.md).

# General Advanced Jobs

This release introduces a set of new jobs that enable users to update module- or feature-specific data using advanced algorithms.

<table><thead><tr><th width="204">Name</th><th>Description</th></tr></thead><tbody><tr><td>Migrate Lineage Status and Error Buckets</td><td><p>This one-time advanced job updates existing lineage records after an upgrade. It replaces outdated lineage status values with the latest ones. It assigns meaningful error categories to failed lineage records, making status and error information easier to understand in the user interface.</p><p><strong>Note:</strong> Run this job only once after upgrading to apply the lineage status and error category updates.</p></td></tr><tr><td>Update Blank Governance Role</td><td><p>This advanced job updates blank governance role values across catalog objects by assigning the configured administrator to the selected governance role fields. It can update specific governance roles or process all supported catalog objects and supports batch processing for large volumes of data.</p><p><strong>Parameters:</strong></p><ol><li>Attribute 1 – Governance Role Fields: Specify the governance role fields to update as a comma-separated list. If left blank, the job updates governancerole4, governancerole5, and governancerole6.</li><li>Attribute 2 – Object Table Names: Specify the catalog object table names to process as a comma-separated list. If left blank, the job processes all supported catalog objects.</li><li>Attribute 3 – Batch Size: Specify the number of records to process in each batch. If left blank, the default batch size is 50,000. Supported values range from 1,000 to 500,000.</li></ol></td></tr><tr><td>Sensitive Data Encryption Migration</td><td><p>This advanced job migrates sensitive source data between plain text and encrypted formats. It updates supported data values, such as top values, minimum and maximum values, profile results, and failed Data Quality values, while skipping values that are already in the selected format.</p><p><strong>Parameters:</strong></p><ol><li>Attribute 1 – Batch Size: Specify the number of records to process in each batch. If left blank, the default batch size is 10,000.</li><li>Attribute 2 – Migration Mode: Specify the migration mode. Enter 'encrypt' to encrypt sensitive data, or 'decrypt' to convert encrypted data back to plain text.</li></ol></td></tr><tr><td>Create Datastory for askEdgi</td><td>This advanced job creates the default askEdgi Data Story structure required for askEdgi to organize and manage generated content. It creates the askEdgi Data Story domain and the required story hierarchy if they do not already exist. The job runs only when askEdgi is enabled and skips any existing Data Story entities</td></tr></tbody></table>

## Existing Advanced Jobs - Updated

This release includes updates to existing advanced jobs, improving processing logic, performance, and reliability across supported workflows.

<table><thead><tr><th width="220.111083984375">Name</th><th width="137.4444580078125">Updated Field</th><th>Updated Field Value</th></tr></thead><tbody><tr><td>Loading QVDS</td><td>Attribute1</td><td>Connection Id</td></tr><tr><td>Loading QVDS</td><td>Attribute2</td><td>Build Lineage (true / false)</td></tr><tr><td>Loading QVDS</td><td>Attribute3</td><td>Report name to build lineage</td></tr><tr><td>Loading QVDS</td><td>Help</td><td><p>This advanced job copies QVD files from a remote location, such as Azure Blob Storage or a remote path, to a local path for Qlik Sense processing. It can also build lineage for Qlik Sense dashboards after the QVD files are loaded.</p><p><strong>Parameters</strong></p><ol><li>Connection ID: Specify the Qlik Sense connection ID.</li><li>Build Lineage (true/false): Set to true to build lineage after loading QVD files, or false to only load the files.</li><li>Report Name to Build Lineage: Specify the Qlik Sense report or dashboard name for which lineage should be built.</li></ol></td></tr><tr><td>Copy Metadata Between Connectors/Schemas</td><td>Help</td><td><p>This advanced job copies metadata for tables and table columns from a source connector to a target connector. It supports copying selected metadata, such as tags, terms, descriptions, governance roles, certifications, custom fields, access settings, and security settings. Metadata can be filtered by connector and schema, with optional case-sensitive or case-insensitive table name matching.</p><p><strong>Parameters</strong></p><ol><li>Attr1 – Source Connector Name: Specify the source connector. Only one connector can be selected per job. (Required)</li><li>Attr2 – Source Schema Name: Specify the source schema to copy metadata from. (Optional)</li><li>Attr3 – Object Type and Metadata Attributes: Specify the object type and the metadata attributes to copy. Supports optional case-sensitive or case-insensitive table name matching. (Required)</li><li>Attr4 – Target Connector Name: Specify the target connector to receive the metadata. Only one connector can be selected per job. (Required)</li><li>Attr5 – Target Schema Name: Specify the target schema associated with the selected target connector. (Optional)</li></ol></td></tr><tr><td>Copy Metadata Between Connectors/Schemas</td><td>Attribute3</td><td><em>{"objectType": "oetable","tag":true,"term":true,"title":true,"businessDescription":true,"technicalDescription":true,"certification":true,"governanceRoles":true,"customFields":true,"objectAccess":true,"objectSecurity":true,"caseSensitive":false}</em></td></tr></tbody></table>

***

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/minor-release/release8.2/release-notes/general-advanced-jobs.md?ask=<question>&goal=<endgoal>
```

`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.