Overview
When a Preventive Maintenance (PM) is assigned to multiple assets, the generated tasks are difficult to differentiate because the task name does not automatically include asset-specific identifiers. Users want the task name to dynamically reflect key asset details, and they want this behavior to be user-configurable so each organization can choose which fields appear.
Current Limitations
• Multi-asset PMs generate multiple tasks with the same or generic task name.
• Task names do not dynamically include asset identifiers (e.g., asset #, name, location).
• Even when assets share the same location, users must open each task to confirm which specific asset it applies to.
