> 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.1/release-notes/administration.md). # Administration ## Job Workflow ### New & Improved #### Bulk Execution Support for Multiple Job Workflows In the Job Workflow, users could execute only one Job Workflow at a time. When multiple Job Flow Names were selected, the Execute option in the action menu was disabled, requiring users to run each workflow individually. With this improvement, users can now select multiple Job Flows and execute them together in a single action. The Execute option remains enabled for multiple selections, allowing bulk execution directly from the action menu. ## ETL ### New & Improved #### Enhanced ETL Management Experience The ETL module has been enhanced to provide a more streamlined experience for creating, managing, and monitoring ETL workflows. The ETL List page has been simplified by removing non-operational fields, renaming columns for clarity, and making the ETL Name the primary navigation link to the Summary page. The Create ETL panel now includes clearer field names, mandatory validations, and improved configuration controls. The ETL Summary page provides centralized visibility into ETL metadata, connection details, scheduling information, execution settings, and SQL scripts. Inline editing, audit history, and lifecycle-based edit restrictions are also included for better governance and control. Additional enhancements include dedicated tabs for Staging Tables and ETL Executions, enabling users to review staging readiness, execution history, logs, job status, and run details more efficiently. ## Service Desk Administration ### New & Improved #### Improved Error Handling for Unmapped CTA Templates In Data Product Subscription, when no Service Desk template was mapped to the CTA button, the system displayed a generic error message with limited information, which made it difficult for users to understand why the action failed and what configuration was missing. With this improvement, the system now displays a detailed error message when no template is mapped to the CTA button: “There is no Template mapped to this Call to Action (CTA) button. Connect with the System administrator to map at least a global template to this CTA button.” This enhancement provides clearer guidance to users and helps administrators quickly identify and resolve the missing template configuration. ## Schedule ### Fixed #### Consistent Time Zone Display on Schedule Pages In the Schedules module, all execution timestamps are now displayed in the user’s local time zone, with the applicable time zone clearly shown. UTC values remain available through tooltips for additional reference. The Execution Time Zone column has also been removed to simplify the schedule view. *** 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.1/release-notes/administration.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.