Dynamic External Activity


The Dynamic External Activity makes it possible to create an external activity with configurable input and output arguments without having a specific .NET class for the activity on the server.

Inheritance Hierarchy:



An external activity is an activity whose execution logic runs in a client application rather than on the server. A typical external activity consists of a server component that defines the input and output arguments of the activity and a client component that performs the actual execution logic. The server component is a compiled .NET class. The Dynamic External Activity provides a generic way to configure the input and output arguments of an external activity without having to compile a specific .NET class on the server.

Custom code is required to perform the execution logic of the activity in the client application. This code is referred to as an "activity handler." An activity handler can be registered with a dynamic external activity using the External ID property.

In a Workflow:

Using custom code you can create an activity handler in your client application. The coding language depends on the Client API you are using. You can then register your activity handler using a specific External ID. Then configure a Dynamic External activity in your workflow that specifies the same External ID and provides the appropriate input and output arguments that the activity handler expects.


Name Description

Display Name


You can change the name of an activity to one that describes what it does. A descriptive name can make a workflow easier to interpret and maintain.

External Id

An activity handler within a client can reference this particular activity using this external identifier.


Create Input Argument


Create Output Argument

Version Information:

Supported from: Geocortex Essentials 3.4.2, Geocortex Viewer for Silverlight 1.1, Geocortex Viewer for HTML5 1.0.