One-click Deployment

One-click deployment allows you to deploy Workflow to users without running a client installation on their computers. It also provides the ability for a client to update itself when the server is upgraded.

Important: Support for one-click installation of Workflow will be discontinued in a future release of the software. The client installation should be used when one-click installation is discontinued.

Before you can use one-click deployment, you must complete the following prerequisites:

  • Microsoft® .NET Framework 4.5 (Full Framework)
    Note: Custom display or form assemblies that target earlier versions of .NET will continue to function as before. However, saving changes made to such custom assemblies requires that they be upgraded, which is accomplished in different ways, based on the version of .NET:
    • For an assembly that pre-dates .NET 4.0, you must upgrade the assembly when you open it. Failure to do so results in an error and the inability to save the edited assembly.
    • For an assembly that targets .NET 4.0, the assembly is upgraded automatically when opened, and changes to such assemblies can be saved as before.
    Service providers that target versions of the .NET framework before version 4.5 must be recompiled targeting .NET 4.5.
  • The NetTCPPortSharing service must be enabled and started.
  • Security certificates cannot be deployed remotely. Install your certificates by manually installing a copy of the certificates from the server. Certificates can be copied from the server to a disk or other portable device, and then installed, or by using your IT department's method of delivering and installing files.
  • MIME types must be added to each computer in order for the .manifest and .deploy files to work correctly. For more information, see the following:

When an administrator installs Workflow on a server computer, the files required for the one-click deployment are installed when you perform a server installation.

On 32-bit computers, these files are located in a folder called Deployment in the following location:

<install dir>\Program Files\Proficy\Proficy Workflow\Program\Deployment

On 64-bit computers, these files are located in a folder called Deployment in the following location:

<install dir>\Program Files (x86)\Proficy\Proficy Workflow\Program\Deployment

An Administrator user must share this folder on the server computer, and then users can access it through a web page. The file used for one-click deployment is:


You can create a web page, a button, or any means of access you want to use to make one-click deployment available to your users.

Each time a user invokes one-click deployment, it checks for any code updates, such as patches and service packs, that have been applied to the server (and subsequently to the one-click deployment files) and applies those changes to the one-click client. This allows your users to always be working with the same version of code as the server.

After installing Workflow on the server computer, you can copy the Deployment folder to another location for users to access. If you copy the folder to another location, you must re-copy the folder whenever code updates are applied in order for users to get the updates.

Important: Do not move the Deployment folder from its install location. If this folder is moved, code updates cannot be applied to it.