Overview
The current PM structure requires users to create separate PMs for each asset. While assigning one PM to multiple assets exists as a workaround, it introduces new issues—specifically identical naming and bulk generation. The goal is to make multi-asset PM assignment a fully supported workflow by improving naming and controlling how PMs are generated.
Current Limitations
• The system expects one PM per asset, requiring duplication when managing similar assets.
• Updating multiple PMs becomes time-consuming and error-prone when changes are needed.
• Assigning one PM to multiple assets acts as a workaround but is not fully supported as a scalable workflow.
