Dear Team,
(ASIS:) As per the current settings one would be able to create such connections that have the same type and the same title.
(TOBE:) Please, make sure that a particular type could contain maximum 1 server-connection with the same title.
Thanks and regards,
Peter
by: Peter S. | 3 months ago | *All other
Comments
Thank you for the idea. Are you thinking about this within a single folder scope or across folders?
Restricting names might cause backward-compatibility issues, so we’d need to be careful with such a change. If we add a warning, we also need to decide at which level we validate - a single folder for the same type-name combination, the full folder path, or across all folders.
And at what point does this actually become a problem for users? When choosing a connection for a task, when managing connections in a folder, or some other use case?
If the issue shows up during management or selection, we could surface extra metadata to help choose the right one. How do these connections typically differ today - by URL, username/token, or something else?
Dear Team, thank you for checking the idea.
It should be solved with onward-compatibility. It may be rather a suggestion for easier management of configuration items.
Scope: meant globally.
Potential issue: the user does not select the intended server within the user interface, but a different one with the same naming.
It may be considered when one would add/create a new server, so the actual settings may be intact.
Would additional metadata help your teams choose the right connection? For example, showing where the connection is defined (folder) or the connection URL. We understand this information may overlap, as the system does not currently prevent it.
We could also improve the experience by showing a warning when creating a connection with a name that already exists elsewhere in the system, including where the existing connection(s) are located. This would remain a warning (not a hard restriction) to maintain backward compatibility.
Please let me know if this approach could work for your team.
Dear Team,
Thank you for checking it, for the current case
-connection URL should be OK.
For the future case showing a warning when creating a connection, with possible duplicated content, should be a great help.
Thank you in advance.
Regards.