> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/support-us/verifone-hq/vhq-parameter-management/configuring-parameter-definitions-for-applications.md).

# Configuring parameter definitions for applications

This section discusses configuring Parameters for applications in VHQ.

{% hint style="info" %}
**Use this when** you need to upload the parameter definition (.vpdx) file for an application so its parameters can be managed in VHQ.
{% endhint %}

As part of the VHQ parameter management process flow, application developers build a *Parameter Definition* file that defines all parameters of the application and their attributes.

The *Parameter Definition* file is an XML file with the .vpdx extension. It defines:

* Names of application parameters, their organization into groups, and default values.
* Name of the parameter file on the device.
* Format and structure of the parameter files on the device.

## Configure parameter definitions for an application

{% stepper %}
{% step %}

### Open the Applications Library

Go to **Device Management** > **Manage Downloads** > **Applications Library**.
{% endstep %}

{% step %}

### Click Configure

Click **Configure** in the *Parameter Definitions* column for the selected application. Choose one of three options:

* **New**: Browse to select and import a new parameter definition file.
* **Reuse from other versions**: Select the parameter definition file from another version of the application.
* **None**: No parameter definition file is selected.

<figure><img src="https://1987038285-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAwQr3EajB7K9ETISDCLz%2Fuploads%2FswUvppsNDLgbShPTSecL%2Fimage%20(5).avif?alt=media&amp;token=1bf13347-8f98-4b14-be6d-4ad8f90cea4c" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Browse and select the file

You can view the parameters of the file, but they can't be edited from this screen.

<figure><img src="https://1987038285-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAwQr3EajB7K9ETISDCLz%2Fuploads%2Fxry56knRjmyBYq6Wpxbp%2Fimage%20(6).avif?alt=media&amp;token=a927ff8b-4d9b-48f3-9e6d-e7a1ac99f319" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1987038285-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAwQr3EajB7K9ETISDCLz%2Fuploads%2FtvGGY1HogKhipuXpcYAp%2Fimage%20(7).avif?alt=media&amp;token=28534b1b-023b-4ee1-8290-cd8db4f4e989" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

{% hint style="info" %}
The *Parameter Definition* file can only be uploaded once.
{% endhint %}

{% hint style="info" %}
**Example**: You imported the parameter definition file for App1 version 1.0. A new version, App1 1.1, becomes available with issue fixes but no parameter changes — you can reuse the parameter definitions already set up for App1 1.0.
{% endhint %}

<details>

<summary>Keywords</summary>

Also called: parameter definition file, .vpdx. Search terms: reuse from other versions, applications library.

</details>


---

# 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.verifone.com/support-us/verifone-hq/vhq-parameter-management/configuring-parameter-definitions-for-applications.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.
