For the complete documentation index, see llms.txt. This page is also available as Markdown.

Parameter management

Prepare validated application parameters and templates before scheduling deployment.

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:

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

Contact the VCS team to upload a user-defined VPFX file for basic and advanced parameters.

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

Document the application version, changed values, and intended targets before scheduling. Do not reuse a parameter set until its application version matches.

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

  • the VPFX fields and VPDX values apply to the same application version

* the saved values match the documented change

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

Result

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

Next steps

Last updated

Was this helpful?