已授权Blue Prism开发的自动化能否部署至未安装该软件的设备？

Hey there! Let's walk through your questions clearly, since I've navigated Blue Prism deployment constraints like this before.

Can you deploy Blue Prism automations to computers without Blue Prism installed? #

Short answer: No, you can't run Blue Prism workflows natively on a machine without any Blue Prism components—here's why and what you can do instead:

• Blue Prism processes are tied to its runtime environment and repository. To execute them, the target machine needs at least the Blue Prism Runtime Client (a lighter, cheaper alternative to the full development client) with a valid runtime license.
• Runtime licenses are significantly more cost-effective than full development licenses, designed specifically for running automations without editing capabilities. You'd just need to install the Runtime Client on target devices, configure it to connect to your Blue Prism repository, and then trigger your workflows via command line or scheduled tasks.

Is there a way to compile Blue Prism processes to EXE? #

Blue Prism doesn't have a built-in feature to export processes as standalone EXEs, but there are workarounds that let you create an EXE-like experience for end users:

• Package with command-line wrapping:
  1. Use Blue Prism's Publish tool to export your process as a .bprelease package.
  2. Create a batch script (.bat) that uses Blue Prism's AutomateC.exe command-line utility to run the process. For example:

     "C:\Program Files\Blue Prism Limited\Blue Prism Automate\AutomateC.exe" /run "Your Process Name" /resource "Your Resource Name"
     

  3. Use a third-party tool (like a batch-to-EXE converter) to turn this .bat file into an EXE. When users launch this EXE, it will trigger the Blue Prism process via the runtime environment.
• Build a custom wrapper application:
  You can develop a simple .NET application (using C# or VB.NET) that calls Blue Prism's REST API or .NET SDK to initiate process runs. Compile this application to an EXE—this acts as a user-friendly entry point, but still requires the Blue Prism Runtime and valid license on the target machine.

Important note: None of these workarounds bypass Blue Prism's licensing requirements. You still need valid runtime licenses for every device executing the automation, as Blue Prism's licensing is tied to the runtime environment, not the wrapper EXE. Always ensure your deployment aligns with Blue Prism's license terms.

内容的提问来源于stack exchange，提问作者XYZKLM