Feature Requests

Part-Level Hotpoint Link Management
Overview: Currently, hotpoint links can only be configured at the page-part level when interacting with a BOM on a part page. While this works functionally, it requires repetitive manual setup when the same part appears across multiple pages, assemblies, or manuals. Current Limitation: When a part number appears in multiple locations, hotpoint links must be created individually for each page instance. If the linked page changes due to a revision, each hotpoint link must be manually updated. This results in significant administrative effort and increases the risk of inconsistent or outdated links. Proposed Enhancement: Add the ability to define hotpoint links at the part level rather than only at the page-part level. With this enhancement: •A hotpoint link would be associated directly with the part number •That link would automatically appear anywhere the part number is used •The link would function as a master link for that part Example Use Case: A part number is used across multiple assemblies and manuals. A single hotpoint link is configured at the part level pointing to a specific instruction or detail page. Wherever that part number appears, the hotpoint link is automatically available. If the linked page is revised or changes, the link only needs to be updated once at the part level and will apply everywhere the part is referenced. Benefits: •Significant reduction in manual setup and maintenance •Consistent hotpoint behavior across all documents •Simplified revision management •Reduced risk of broken or outdated links •Improved scalability as documentation grows Summary: Part-level hotpoint links would allow teams to manage links once and apply them everywhere a part is used. This would greatly improve efficiency, consistency, and long-term maintainability of documentation.
2
·
Feedback Forum
Proposed Enhancement: Grouped Content Associations on Product Pages
Overview Currently, product pages allow content to be associated in two ways: Related and Attached. This works well from a functional and reference standpoint, but the experience could be significantly improved by introducing grouping within these association types. Current Limitation All related or attached content appears as a flat list. As the volume of associated content grows, this can become difficult for both administrators to organize and for end users to quickly interpret. Proposed Enhancement Introduce the ability to create association groups within both the Related and Attached content areas—similar to how users can create favorite groups when starring media in the content viewer. For example: •Within Related Content, allow groups such as: •Manufacturer Documents •Installation Guides •Compliance & Certification •Marketing Materials Each group would: •Be configurable by administrators •Contain one or more associated content items •Display to end users as a distinct card or section on the product page End User Experience Instead of seeing a long, unstructured list of documents, the user would see clearly labeled cards (e.g., Manufacturer Documents) that help them immediately understand what type of content is available and where to look. Benefits •Improves content discoverability and usability for end users •Scales better as product documentation grows •Aligns with existing Documoto patterns (favorite groups) •Reduces cognitive load and page clutter •Provides administrators with better organizational control Summary This enhancement builds on existing association functionality without changing how content is technically referenced. It simply adds a layer of organization and presentation that improves clarity, usability, and scalability of product pages.
1
·
Product Pages - Early…
Feature Request: Global Page-to-Part Relationships with Per-Page BOM Population Control
Description / Use Case: We would like the ability to relate pages directly to parts in Documoto, similar to the existing functionality that allows pages to be related to parts through a BOM on a Parts Page. This request extends that capability to allow global page-to-part relationships that are not limited to a single BOM or drawing, while providing fine-grained control over how each relationship is used. Proposed Functionality: Global Page-to-Part Linking • Allow users to create relationships between a part and one or more pages at the global part level. • These relationships should function like existing page-to-part links created through a BOM. Permission-Aware Navigation • When a user selects a linked page, the system should navigate to that page only if it exists in a book the user has access rights to. • If the system is not able to dynamically remove or hide links based on user access rights, display a custom access-restricted error page instead of a generic 404. • The error page should clearly indicate that the content exists but access is restricted. Visibility of Links • Page-to-part links should be viewable from: The Part Page The Parts List within a drawing (when applicable) Per-Page Toggle for BOM Population • For each page related to a part, provide an independent toggle that controls how that specific link is applied: Part Page Only: The link is visible only on the Part Page and does not appear in any BOMs. Populate in BOMs: The link automatically appears anywhere the part is used within BOMs across different drawings. • This toggle should be configurable per page-to-part relationship, not as a single global setting. • This allows some pages to remain contextual references while others are fully propagated into BOMs. Benefits: • Enables fine-grained control over documentation visibility • Supports complex parts with multiple supporting documents • Reduces duplication and manual maintenance of BOM links • Improves user experience and avoids misleading 404 errors • Maintains Documoto’s existing security and permission model Summary: This enhancement would expand Documoto’s page-to-part relationship model by introducing global linking with per-page BOM propagation control, improving flexibility, usability, and documentation consistency across books and drawings.
0
·
Developer Forum
Load More