> 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/list-customizations/manage-naming-convention.md).

# Manage Naming Convention option in Patch My PC Publisher

*Applies to: Patch My PC Publisher V3.x*\
*Available at level: All Custom Products, All Vendors, Vendor*\
*Available on tab: Intune Apps, Intune Updates*

The **Manage Naming Convention** right-click option in Patch My PC (PMPC) Publisher allows you to define a custom naming standard for the Win32 applications and updates created by Publisher at the levels detailed above.

This helps ensure application names in Intune are consistent, descriptive, and aligned with your organizational standards.

If no custom naming convention is configured, or if the pattern is left empty, Publisher uses its default naming format.

{% hint style="info" %}
**Note**

This right-click option is only available at the Product Tree levels specified in the *Applies to:* section for Intune Apps and Updates. For options available at the Product level, see [Custom Intune App Properties](/patch-my-pc-publisher/customizations/list-customizations/custom-intune-app-properties.md).
{% endhint %}

When you select the **Manage Naming Convention** right-click option, the **Custom Intune Application Properties** dialog appears.

<figure><img src="/files/piZ3ENb1Fqogy6S3ytS8" alt="&#x27;Custom Intune Application Properties&#x27; dialog" width="373"><figcaption></figcaption></figure>

From here, you can configure a custom name format for Win32 applications created by Publisher by using at least one or more of the provided token values (which 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 or update name, which can be reused or extended in your custom pattern.

### **Example**

Custom Intune App name configured as:

```
[App] - %OriginalName%
```

Resulting Intune application name:

```
[App] - Google Chrome 142.0.7444.176 (x64)
```

{% hint style="info" %}
**Note**

When creating naming conventions for **Intune Updates**, remember that **%OriginalName%** already includes the **Update** **for** prefix.

Avoid adding additional wording like **Update** to prevent duplicated names.
{% endhint %}

This approach allows you to clearly identify Publisher-created applications whilst retaining the original product and version details.

## Configure a Naming Convention

To configure a naming convention:

1. Right-click the relevant object in the Product Tree and select **Manage Naming Convention**.
2. On the **Custom Intune Application Properties** dialog, click one or more token values to build your required naming pattern.
3. Click **OK** to save the configuration.

The naming convention is applied during the next Publisher [Synchronization](/patch-my-pc-publisher/manage/sync-schedule-tab.md) and affects newly created applications and updates only.

{% hint style="danger" %}
**Important**

If a naming convention is configured at the All Products or Vendor level, that configuration is inherited automatically by any products lower in the Product Tree, unless they are overridden at a product level by using the [Custom Intune App Properties](/patch-my-pc-publisher/customizations/list-customizations/custom-intune-app-properties.md) right-click option.
{% endhint %}


---

# 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/list-customizations/manage-naming-convention.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.
