> 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.3/governance-catalog/governance-app/integration.md).

# Integration

The Governance App can be integrated with the Service Desk to support compliance-related requests. When an end user submits a response, it may represent a request that requires further action. Integrating with the Service Desk enables users to map a Governance App to a predefined service desk template, along with an associated approval workflow.

**Once this integration is configured:**

* A ticket is automatically created in the Service Desk whenever a new response is submitted or a campaign is completed.
* The ticket follows the approval workflow defined in the service desk template.
* Designated stakeholders in the workflow are responsible for fulfilling the request.

## **Configuration Details**

* **Object Type:** Governance App
* **Request Type:** Compliance

To enable this integration:

1. Create the Governance App.
2. Define the required workflow in the Service Desk.
3. Create a Service Desk template. 

   <figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdy58CX0-6Tm4usr4RKH9L6n-kXmRhyjGR3U5Dumd5l_b0WiAI3ZQraq7cM0quJM_R4eQOElDpzoNM_7QtDvgYNEeZ7g_3rSjHIaOj7k_od2MLN1rewOr94EsFWpCD3j2OTdnr7?key=VyJIEWhJt8GJcPkcCGszQg" alt=""><figcaption></figcaption></figure>
4. Assign the app to the template with the defined workflow.

   <figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXcwJ-MQA8CwVfwQ8sQc47XiaJSRWr-TaesN60mnsdMsWUNn76zU_56PmijombAMWlpEUGVGIGukQiJorT1MrXz3mqHc10jm4NJ7w8vt1AGkwwS0vcbli-2dcwRc87xo5k2kRw_-YQ?key=VyJIEWhJt8GJcPkcCGszQg" alt=""><figcaption></figcaption></figure>

## Ticket Information in the App

Within the respective Governance App, users can view the following ticket details:

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXccihgE1ZcsfMZ4nfvBDo_XPOByXj3tDvCUikCHLFREn14hBEKH7GqPf1dhlNcr41vLfOyVD_RQGp8XfNr68M1gobvdUkYVeTKlwlLHi0PFBQbS7P6i8lUmverZsjpU29p4Z2Ua4g?key=VyJIEWhJt8GJcPkcCGszQg" alt=""><figcaption></figcaption></figure>

* **Request ID:** The unique ID of the ticket created in the Service Desk.
* **Ticket Age:** The duration since the ticket was created.
* **Status:** The current status of the ticket.


---

# 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/release8.3/governance-catalog/governance-app/integration.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.