User guide for diagnostic tool is not specifying the binary name

[pere]

In

Studio - About The Diagnostic Tool

you’re instructing us to use that tool, that is supposed to help us finding solutions to our problems with your tools.

You say there that either you can download it from the resource center or use the one provided with your product in a certain directory.

Well, in that case… could you please state in those docs WHAT THE NAME OF THE EXECUTABLE IS? Yeah, I’m “smart enough” to find it myself. It’s UiPath.DiagnosticTool.exe. Or so I suppose. Because it could be whatever random other one and have made a wrong assumption. In any case: there’s 654 items in that folder, that’s a documentation page, people are supposed to read it to seek help and follow the proper steps. They are already upset because of the problems they are facing. And then they find out they didn’t even bother writing the name of the binary they have to run. Gosh.

Your documentation is, generally speaking, of very bad quality.

[ptrobot]

While I do agree that UiPath documentation can be lacking sometimes, the article does say that you can just press Start button and search for it.

[pere]

Disagree; that’s not what I’m looking for. I said the binary file. We already know that “Diagnostic Tool” is the name of the diagnostic tool. Using the Windows built-in search feature completely defeats the sense of what I’m complaining about. The place it should be is in the docs, in the same line they mention the folder. That’s the way a properly written, helpful documentation, should be written. Not overcomplicating things.

That said, I just found out that the name of the binary actually IS stated in that docs page. I’m not gonna erase the thread or whatever; I acknowledge my own mistakes:

That said, even that I think my point is still valid in my complaint. They mention the binary by the end of the page, when you have already done your own research to find it and in the “command Line Arguments” section, when you probably only wanted to run the GUI one. It’s merely a simple matter of usability.

[ptrobot]

The shortcut does point to the binary file.

[pere]

I’m talking about the documentation. UiPath’s docs.

Not Windows search feature.

I said in advance that I could find it myself. I didn’t even have to use any search tool.

What I’m complaining of it’s been already argued in my previous comments and I still hold the same opinion.

Thank you.

[ptrobot]

Yeah, I guess we have to agree to disagree. The documentation you refer to does state that you can find it in Start.

Now if you feel that using search is “cheating”, you can just press Start and go to Alls Apps and scroll down to UiPath. From there it’s just a matter of using “Open file location” to hunt down the exe-file.

You can find the exe-file and I can find the exe-file so maybe the documentation isn’t that bad?

[pere]

No; I don’t feel that’s “cheating”. I think it’s overcomplicating things and a very poorly written documentation, very clumsy and unusable and even a stupid way of giving instructions. As another reason for my point: why the heck are you providing the path, the two possible ones, if you don’t provide at the same time (probably in the same path itself) the name of the binary? If you are gonna tell the user to use the search tool, the previous information about the path is futile.