> 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-templates/configuring-parameters-for-single-device/editing-parameters.md).

# Editing parameters

Edit device parameters in VHQ using configured parameter templates with automatic or manual activation based on direct parameter activation settings.

{% hint style="info" %}
**Use this when** you need to edit an application's parameter values for a single device.
{% endhint %}

Before editing, ensure the application's parameter form view file (PFX) is configured, and that parameter templates are set up if you plan to use them.

## Edit parameters for a device

{% stepper %}
{% step %}

### Open the device profile

Go to the **Device Profile** screen of the selected device.
{% endstep %}

{% step %}

### Select the application

Under *Device Details*, select **Parameter**, then select the application to edit.
{% endstep %}

{% step %}

### Click edit

Under *Actions*, click the edit icon.

<figure><img src="https://1987038285-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAwQr3EajB7K9ETISDCLz%2Fuploads%2FPY1r0eZ43WRtr7XgJ1Ss%2Fimage%20(25).avif?alt=media&amp;token=15a7cebb-95f0-4111-a257-740a08b18f35" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Edit the values

Click the edit button. Containers are listed as tabs, with parameters and their values. On the *Edit Parameter for Application* form, enter values — you can view each parameter's description, default value, and source type as you edit.
{% endstep %}

{% step %}

### Save

Click **Save**.
{% endstep %}

{% step %}

### Activation

Once saved, the change activates automatically (unless configured otherwise — see below).

<figure><img src="https://1987038285-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAwQr3EajB7K9ETISDCLz%2Fuploads%2FGpecYiQVIqbHnoi5t3jM%2Fimage%20(26).avif?alt=media&amp;token=c658585e-5caa-42cd-bd31-0f4cb6c4e6eb" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

{% hint style="info" %}
**Direct Parameter Activation** (under **Estate Administration** > **System Configuration** > **System**) can be set to **True** or **False** to control whether parameters send automatically on modification.
{% endhint %}

If **Direct Parameter Activation** is **True**, the *Activate* button in *Device Profile* > *Parameter* is hidden. If **False**, the *Activate* button is visible so you can activate parameters manually.

## Guidelines

* All parameters defined in the PFX appear in this list by default, shown with their PDX default values. To exclude specific parameters from editing, remove them from the PFX — they'll keep their default values.
* If you don't configure a value for a parameter, it uses its PDX default value.

{% hint style="info" %}
**How VHQ evaluates parameters for download**, in order of precedence:

1. Parameter values configured at the device level.
2. Parameter values configured for parameter templates.
3. Default parameter values as defined in PDX.

A device-level value takes highest precedence; if not configured, the parameter template value is used; if neither is configured, the PDX default is used.
{% endhint %}

<details>

<summary>Keywords</summary>

Also called: edit device parameters, direct parameter activation. Search terms: single device parameters.

</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-templates/configuring-parameters-for-single-device/editing-parameters.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.