> 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://verifone.cloud/sites/default/files/inline-images/1_20.jpg" alt="Edit parameters action"><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://verifone.cloud/sites/default/files/inline-images/2_7.jpg" alt="Activation confirmation"><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 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.verifone.com/support-us/verifone-hq/vhq-parameter-management/configuring-parameter-templates/configuring-parameters-for-single-device/editing-parameters.md?ask=<question>&goal=<endgoal>
```

`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.