> For the complete documentation index, see [llms.txt](https://docs.patchmypc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patchmypc.com/patch-my-pc-publisher/customizations-right-click-options/set-custom-application-icon-and-properties.md).
# Set Custom Application Icon and Properties
*Applies to: Patch My PC Publisher V2.x*\
*Available at level: Product*
\
*Available on tab: ConfigMgr Apps, Intune Apps*
## Overview
**Set Custom Application Icon and Properties** allows you to override the default name, description, and icon used for applications created by the Publisher.
This option is used when you want application metadata to remain consistent across ConfigMgr and Intune apps, rather than changing automatically with each new version. The Publisher applies the configured properties when the application is first created and reapplies them whenever the application is updated.
You can configure a custom application name, description, and icon. For ConfigMgr applications, you can also define a localized application name. These settings ensure a consistent end user experience in the Intune Company Portal or ConfigMgr Software Center.
If no custom values are specified, the Publisher uses the default Patch My PC generated values.
{% hint style="info" %}
**Note**
This option is especially useful for task sequence scenarios or long running deployments where a static application name or icon is required and changes between versions could cause confusion or unexpected behavior.
{% endhint %}
### Token Values
Naming conventions are built using token values. At least one token must be included.
\
The available tokens are shown at the top of the dialog and can be clicked to insert them at the cursor position.
* **%VendorName%**
\
Resolves to the software vendor name.
* **%ProductName%**
\
Resolves to the product name and architecture.
* **%Version%**
\
Resolves to the application version.
* **%OriginalName%**
\
Resolves to the default Patch My PC application name.
**Example**
\
Custom ConfigMgr App name configured as:
```
DEV - %OriginalName%
```
Resulting ConfigMgr application name:
```
DEV - Brave 144.1.86.148 (EXE-x64)
```
{% hint style="info" %}
**Note**
Token values are populated from the Publisher catalog definition. These values are stored in English and are not automatically translated to another language.
{% endhint %}
{% hint style="warning" %}
**Important**
If the ConfigMgr apps global option to [Do not include the version in the application name](/patch-my-pc-publisher/administration/configmgr-apps/options/application-creation-options.md#do-not-include-the-version-in-the-application-name) is enabled, the **%OriginalName%** token will also omit the version number. In this scenario, the original name resolves to the product name and variant/architecture only, without the version suffix.
{% endhint %}
## **Configure** Custom Application Properties
To configure Custom Application Properties:
1. Right-click the Product you want to customize.
2. Select **Set custom application icon and properties**.
3. Enter a custom Application name if required. For ConfigMgr, optionally configure a Localized application name.
4. Enter a Custom Description\*.
5. Select **Browse** to upload a custom icon if required.
6. Click **OK** to save the configuration.
\*Click **Show default description** to display the original catalog description. Copy the text to the clipboard, paste it into the **Custom Description** field, and edit it to create your custom description.
The custom properties are applied during the next Publisher [synchronization](/patch-my-pc-publisher/administration/sync-schedule.md) and affect newly created and updated applications for that product.
---
# 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.patchmypc.com/patch-my-pc-publisher/customizations-right-click-options/set-custom-application-icon-and-properties.md?ask=&goal=
```
`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.