Unify Connection Creation Interface in Document Builder with the Rest of ELM Tools

Hello,

The current experience for creating and selecting connections in Document Builder is not aligned with the user interface and workflow used across the rest of the ELM applications (RM, ETM, etc.).

Specifically:

• Creating a connection requires selecting the Global Configuration separately from the target artifact (module, test plan, etc.).
• The interface used is different from the standard artifact/configuration selector available in other tools.
• The user experience is inconsistent with the rest of the ELM ecosystem.
• The Connections section quickly becomes cluttered.
• Many connections are created but never reused.
• The connection dropdown available when generating a report only allows text search, with no filtering, grouping, or classification.

As a result:

• The Connections area becomes difficult to manage.
• It is hard to understand why certain connections were created.
• Report creation becomes less efficient.
• The overall experience feels disconnected from the rest of ELM.

Proposed Enhancement

1. Unified Selection Interface

Document Builder should use the same configuration and artifact selection interface that is used throughout the rest of ELM.

This includes:

• Integrated selection of the Global Configuration.
• Standard hierarchical navigation to select the artifact (module, test plan, etc.).
• The same visual and interaction model users are already familiar with.

This would significantly improve usability and consistency across the platform.

2. Improved “Ad Hoc Connection” Experience

The current Ad Hoc Connection option opens a separate window with a different interaction model.

Instead, it should:

• Use the same unified selector for configuration and artifact.
• Provide a consistent experience aligned with other ELM tools.
• Allow users to dynamically select what they want to export at the time of report generation.

In practice, users often need to export a specific artifact within a specific configuration at a given moment. Creating a permanent connection is not always necessary.

A more dynamic approach would:

• Reduce unnecessary permanent connections.
• Better reflect real-world workflows.
• Increase efficiency and flexibility.

Expected Benefits

• Consistent user experience across the ELM ecosystem.
• Reduced clutter in the Connections section.
• Lower administrative overhead.
• Faster and more intuitive report generation.
• Improved usability in environments with multiple configurations.
• Better alignment with user-centered design principles.

Functional Justification

In real usage scenarios, users frequently need to generate documents from a specific artifact within a specific configuration on demand. The current connection model encourages the creation of persistent connections that are often not reused, leading to accumulation and management complexity.

A unified and more dynamic selection model would significantly improve efficiency, clarity, and overall usability of Document Builder.

Thanks!!