> 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/verifone-central-device-management/verifone-central/rollouts/parameter-management.md).

# Parameter management

Use **Parameter management** to configure and deploy application parameters across one device or many devices.

Parameter management helps you control application settings without updating each device manually.

### When to use this page

Use this page when you need to:

* prepare parameter values before rollout
* understand which files control available fields and saved values
* decide whether the next task belongs on one device, a batch, or a template-driven rollout

### Before you start

Confirm that:

* your role allows you to manage parameters or run parameter rollouts
* you know which application and version the parameters apply to
* you have the correct parameter files or template data for the target devices

If you plan to deploy the configuration next, review:

* [Rollouts](/verifone-central-device-management/verifone-central/rollouts.md)
* [Manage rollouts](/verifone-central-device-management/verifone-central/rollouts/manage-rollouts.md)
* [Schedule rollouts](/verifone-central-device-management/verifone-central/rollouts/schedule-rollouts.md)

### What parameter management supports

Use parameter management to:

* define and update application parameter values
* manage parameter configuration for one device or many devices
* prepare parameter data for rollout
* separate frequently used values into basic or advanced parameter sets

### Understand application parameters

Applications include executables and configuration files.

The configuration files store application parameters. These values control how the application behaves on the device.

Parameter attributes can be added when an application is introduced. They can also be updated later and downloaded to devices as part of a rollout.

### Understand parameter files

Parameter management uses two XML file types:

* **VPFX** — the Verifone Parameter Form file. This file lists the available parameters.
* **VPDX** — the Verifone Parameter Definition file. This file lists the parameters and their configured values.

You configure the parameter values in the `.vpdx` file. Then upload the definition file to Device Management before scheduling a parameter rollout.

Use this rule when working with the files:

* use **VPFX** to understand which parameters exist
* use **VPDX** to define the values you want devices to receive

### Understand parameter templates

A **parameter template** is a reusable set of parameter values for an application.

Use templates to:

* manage a common configuration for a group of devices
* update some or all parameters for an application
* reduce repeated manual edits across the estate

One or more parameter templates can be configured for each application.

### Basic and advanced parameters

Parameter management supports both **basic** and **advanced** parameter files.

Use this split to organize parameters by how often they are configured or reviewed.

You can:

* view and edit parameters in the basic list
* view and edit parameters in the advanced list
* schedule rollouts for either parameter type to one device or a batch of devices

{% hint style="info" %}
Contact the VCS team to upload a user-defined VPFX file for basic and advanced parameters.
{% endhint %}

Application-specific VPFX files can be uploaded to Device Management. After upload, only the basic parameters configured for the selected application version are shown in the basic parameter view.

### Choose the right parameter path

Use these rules:

* use the single-device flow when one device needs review or correction
* use the batch flow when one change must reach many devices
* use add or delete actions when the parameter set itself must change

### How parameter management fits into rollouts

Parameter management is the preparation stage for parameter deployment.

Most parameter rollout work follows this order:

1. define or update the parameter values
2. organize the values in a template or parameter file
3. schedule the rollout
4. monitor rollout progress and results

### Verify before rollout

Before you move to scheduling, confirm that:

* the application version is correct
* the parameter values are saved in the intended file or template
* the next rollout target is clear

### Related deployment areas

Use these pages when you need to manage other rollout content:

* [Software management](/verifone-central-device-management/verifone-central/rollouts/software-management.md) — manage software packages and reference sets
* [Content management](/verifone-central-device-management/verifone-central/rollouts/content-management.md) — manage static files and media for rollout

### Result

Parameter management prepares the configuration values needed for a controlled parameter rollout.

### Next steps

* [To view/edit basic/advanced parameters for a single device](/verifone-central-device-management/verifone-central/rollouts/parameter-management/to-view-edit-basic-advanced-parameters-for-a-single-device.md)
* [Edit parameters for batch devices](/verifone-central-device-management/verifone-central/rollouts/parameter-management/edit-parameters-for-batch-devices.md)
* [Add/delete parameters](/verifone-central-device-management/verifone-central/rollouts/parameter-management/add-delete-parameters.md)
* [Schedule rollouts](/verifone-central-device-management/verifone-central/rollouts/schedule-rollouts.md)


---

# 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/verifone-central-device-management/verifone-central/rollouts/parameter-management.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.