为什么我的虚拟机在我最小化或关闭时停止执行 blueprism 自动化进程？
Why does my virtual machine stop conducting blueprism automated processes when I minimize or close it?
我在远程计算机上自动化流程。当我从控制室开始一个过程时，它工作得很好。但是，一旦我最小化或关闭远程计算机（我没有关闭它，我只是关闭 window），远程计算机就崩溃了。日志包含无法找到元素之类的条目。原因是，远程计算机甚至没有打开应用程序。
那么，这是什么原因呢？计算机状态为桌面，因此没有屏幕保护程序或登录屏幕。
预期结果：即使远程桌面会话不在屏幕上，机器人也应该正常工作，就像在生产环境中一样。
您没有指定，但以下答案推断了您关于如何“[最小化] 或 [关闭]”您的 "remote computer" 的陈述，以假设您正在利用 Microsoft 的远程桌面连接 utility/protocol.
Blue Prism 特别不鼓励在基于 Blue Prism 的环境中使用远程桌面来操纵远程运行时资源，因为协议本身的使用会导致 Blue Prism 用于在 Windows 中定位元素的方法桌面环境完全停止工作。这在 Blue Prism's official documentation on Remote Access Tools:
中明确说明
The following tools have been deemed to be specifically unsuitable for
providing remote access to Blue Prism environments:
Remote Desktop Connection (RDP)
The way that this Windows tool (and other tools that
use the RDP protocol) handle session management is not compatible with
Blue Prism:
- The underlying operating system is aware as a connection is established which can, subject to the automation techniques being
applied, result in the executing automation being interupted.
- It requires the remote access credentials to be aligned with the credentials used to authenticate the target system against the network
which presents a potential security risk.
- As a user authenticates any previously connected users are locked out.
- Each connection creates a separate desktop session.
- The connection is not maintained throughout a system reboot.
我在远程计算机上自动化流程。当我从控制室开始一个过程时，它工作得很好。但是，一旦我最小化或关闭远程计算机（我没有关闭它，我只是关闭 window），远程计算机就崩溃了。日志包含无法找到元素之类的条目。原因是，远程计算机甚至没有打开应用程序。
那么，这是什么原因呢？计算机状态为桌面，因此没有屏幕保护程序或登录屏幕。
预期结果：即使远程桌面会话不在屏幕上，机器人也应该正常工作，就像在生产环境中一样。
您没有指定，但以下答案推断了您关于如何“[最小化] 或 [关闭]”您的 "remote computer" 的陈述，以假设您正在利用 Microsoft 的远程桌面连接 utility/protocol.
Blue Prism 特别不鼓励在基于 Blue Prism 的环境中使用远程桌面来操纵远程运行时资源，因为协议本身的使用会导致 Blue Prism 用于在 Windows 中定位元素的方法桌面环境完全停止工作。这在 Blue Prism's official documentation on Remote Access Tools:
中明确说明The following tools have been deemed to be specifically unsuitable for providing remote access to Blue Prism environments:
Remote Desktop Connection (RDP)
The way that this Windows tool (and other tools that use the RDP protocol) handle session management is not compatible with Blue Prism:
- The underlying operating system is aware as a connection is established which can, subject to the automation techniques being applied, result in the executing automation being interupted.
- It requires the remote access credentials to be aligned with the credentials used to authenticate the target system against the network which presents a potential security risk.
- As a user authenticates any previously connected users are locked out.
- Each connection creates a separate desktop session.
- The connection is not maintained throughout a system reboot.