The Hotspot Editor frontend enables authors to place, move, select, and configure clickable hotspots directly on an image or diagram within the authoring workspace, giving them an intuitive visual way to build context-rich navigation. The experience should fit the existing panel-based authoring patterns, with the canvas as the primary interaction area and hotspot details or linking controls presented through the appropriate side panel or contextual UI. Frontend state should keep hotspot edits responsive with clear save, loading, and error handling while integrating with the platform API for persistence and retrieval of hotspot definitions and their linked parts, components, or informational elements. The UI should also handle invalid links, unsaved changes, and permission-based access consistently with the wider authoring experience.
Deliver the authoring experience so users can open interactive 3D CAD views directly from topics, individual steps, and spare part pages, with the model presented in the relevant preview area or panel without breaking their current workflow. The frontend should support deep-linking to specific annotations and design details, keep that selection in URL and local view state where applicable, and coordinate with platform APIs to load the correct model context for the current object and workspace. The UI must handle loading, access, and failure states consistently through existing error-handling patterns, so users always understand whether a model is available and what detail is being referenced. This gives authors and consumers clearer visual context and more precise technical guidance at the point of use.
The Electronic Parts Catalogue editor frontend will give authors a focused authoring experience in the Authoring workspace for building rich part pages with multiple configurable views, combining graphics, parts lists, quantities, profiling metadata, and notes in a clear and responsive UI. The epic should cover the editor surfaces, panels, and form interactions needed to create and update this content, with frontend state kept in sync with the platform API and reflected consistently across preview, metadata, and list-based editing flows. It should handle loading, validation, save states, and API failures using established hooks, stores, and error-handling patterns so authors can work confidently in both web and desktop clients. The result is a maintainable, user-friendly catalogue editing experience that supports accurate, visually rich parts content tailored to different audiences and product configurations.
Deliver a frontend experience in the Authoring workspace that lets users load EBOM data from PLM, review the imported engineering structure, and work with the resulting service-oriented assemblies and spare parts assortment as clear, navigable UI states rather than backend-only processing. The feature should fit the existing panel and perspective patterns, using list/tree views, contextual right-panel detail, and workspace-aware state management to show import progress, transformation results, and any validation or failure states from the platform API. The UI should support responsive feedback for long-running operations with loading, empty, and error boundaries, and keep users informed through consistent dialogs, toasts, and refresh behavior as SBOM and assortment data become available.
This epic delivers the Guided Fault Trace editor as an authoring experience in the frontend, letting users build and maintain diagnostic flows through a clear visual workflow for decision points, outcomes, and troubleshooting actions. In the Authoring workspace, the feature should fit established panel and form patterns, manage editor state predictably with shared hooks and stores, and keep the UI responsive during create, edit, reorder, and save interactions through appropriate loading, optimistic, and validation states. The frontend must integrate cleanly with the platform API for persistence and retrieval while handling permission-based access, unsaved changes, and failure scenarios through the platform’s unified error handling and feedback patterns. The result is a structured, user-friendly editing experience that helps authors produce fault-tracing content technicians can follow quickly and reliably.