> 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/copy-parameter-template-from-other-application-version.md). # Copy parameter template from other application version Copy parameter templates between application versions in Device Management to reuse existing configurations across multiple applications or versions. ## What is copying a parameter template? This feature copies a parameter template (PT) from an existing template, or from another version of an application. You can view all parameter templates, the application version each was copied from, its last-modified date and time, and who made the modification. You must provide a name for the new parameter template.
## Copy options * **From Existing Templates**: Lists all existing PTs with a radio button, letting you copy one PT from the same version. Save the selected template under a new name. * **From Another Version**: Lists PTs with checkboxes, letting you copy PTs from another version. You can select multiple and click **Save**. --- # 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/copy-parameter-template-from-other-application-version.md?ask=&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.