> 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/service-desk/about-service-desk/advanced-jobs.md).

# Advanced Jobs

1. **Service Desk V1**\
   This advanced job helps to migrate existing service desk templates to a new version. It enables selecting existing templates and completing mandatory fields before submitting service requests for multiple objects on behalf of various users.

{% hint style="info" %}
Note: No attribute is needed to run this job. Execute it once during the initial use of OvalEdge and every time the tool version gets updated. Only the System Admin can perform this job.
{% endhint %}

2. **External Tickets Syncing**\
   This advanced job synchronizes ticket status in an external ticketing tool, such as Jira, ServiceNow, or DevOps. It facilitates changing tickets' status to either "Approved" or "Rejected" based on their current status. \
   Unapproved tickets in the external ticketing tool will be directly changed to the "Rejected" status, while approved tickets will be moved to the "Approved" status.
3. **Update Group Info for Service Requests**\
   This job updates the Group Info for existing Service Requests, excluding API Access Requests.
4. **Migrate Service Desk Notification Templates**\
   This job involves updating service desk inbox notification templates with the old service desk inbox message.

***

Copyright © 2025, 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.ovaledge.com/service-desk/about-service-desk/advanced-jobs.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.