computerNameTemplate enhancement request

[helder14]

Hi there,

I’d like to request an enhancement to computerNameTemplate so that:
1. It can reference the computerName token; and
2. It supports inline reformatting of any token (including those populated after the User Entry step), without needing an extra script.

Current behavior

Currently, when using computerNameTemplate, we are limited to the other tokens (e.g. assetTag, email). This creates an extra step in workflows where both computerName and assetTag need to follow specific formats.

Example

Desired outputs:
• computerName: mac-023-company
• assetTag: mac-023
• User input: 023

With the current setup:
• I configure computerNameTemplate to use the assetTag token.
• The user entry (023) becomes the assetTag.
• I substitute the computerName to become mac-023-company.
• However, the assetTag remains just 023, so I need to run an additional script to reformat it to mac-023.

With the proposed enhancement:
• The template could reference the computerName token directly.
• Formatting rules could be applied inline to any token, including those from User Entry.
• In this case, the user would only enter 023 once. The template could then natively produce:
• computerName: mac-023-company
• assetTag: mac-023

Benefits
• Keeps computerName and assetTag aligned using a single template.
• Removes the need for post-setup scripts just to format token values.
• Makes workflows simpler, cleaner, and more consistent.

Thanks for considering this enhancement!