Sorry if this idea is duplication of existing idea but we are now going to upgrade to 7.3.2 and noticed again the nice feature of being able to show details of a resource in Control.It would be great to have at least local FQDN and server FQDN select...
Hello,I am posting here because the issue came up when working with MSAL that needs external DLL.When we copy the Microsoft.Identity.Client.dll file to the folder where automate.exe is located it works.When we copy the dll to another folder Blue Pris...
Hello,Note: Sorry for duplicate idea. I maybe already posted this idea when we were using 6.4 and read similar ideas posted by other users. Unfortunately I could not find a list of my own ideas to post an update, so I had to create a new idea. Now pa...
It is possible to start schedule, delete schedule, report on schedule... but there does not seem to be a command to create or retire schedules, which would complete the functionality for CLI commands for AutomateC.exe
I understand it may improve user experience when they can chose their own language and see Blue Prism UI and log entries in their native language.However, in an international environment with more than one language, this seems to be contra productive...
Hello @robert.nicklin Thanks for your reply. As far as I can see about all information in the details window in Control is also available in the Environment Report you were pointing me to. So following your way of thought the details windows wouldn't...
Hello @GeoffHirst Sorry for the late reply but we 'solved' the issue by copying the DLL into the program folder, which is OK for the time of install but replacing the DLL at a later time will be a pain. Also not knowing why it doesn't work with other...
Hello @BUL_LA The DLL should be in the same folder as Automate.exe. I think you already did so.Since DLL and Automate.exe are in the same folder the references in the VBO must not contain any path information. So downloading the MSAL package from DX ...
Hello @GeoffHirst Thanks for the reply.The version number shown in the error message is always the version number of the DLL. If we switch to another version then the version number of this file is shown. This indicates the issue is not with the DLL ...
