Variable

Use to define a variable for an event handler or process. A variable cannot be shared with other event handlers or processes.

Once a Variable is added, the properties for the activity must be set appropriately in the Property window.

Parameter

Use to define a parameter for a process or external process.

Once a Parameter is added, the properties for the activity must be set appropriately in the Property window.

ClientMessage

Use to declare a client message to be used in the client request event handler. The declaration is invalid after an event handler ends.

A client message is automatically added to the Client Messages node when an activity that references the client message is added to the orchestration.

Once a ClientMessage activity is added to an event handler, the client message to be referenced must be identified in the Property window.

ServerMessage

Use to declare a server message to be used in the client request event handler. The declaration is invalid after an event handler ends.

A server message is automatically added to the Server Messages node when an activity that references the server message is added to the orchestration.

Once a ServerMessage activity is added to an event handler, the server message to be referenced must be identified in the Property window.

Assign

Use to copy data between fields and variables.

For simple fields and variables, data is copied from the source <From> to the destination <To>.

For arrays, the source (simple data or an array) can be appended to the end of the destination array (Append) or a source array can replace the destination array (Copy).

Once an assign activity is added to an event handler, the following properties must be set in the Property window: AssignmentType, From, and To. Also, refer to Assign Data for Message Dialog Box.

The Assign activity may throw one of the following exceptions: InvalidCastException, InvalidFormException, OutOfRangeException, InputDataOverflowException, ArithmeticException, or NullReferenceException.

AssignMessage

Use to create a new message of the specified type from information in Orch.Message.

Throws an AssignMessageException if the Orch.Message cannot be cast to the message type.

Once an AssignMessage activity is added to an event handler, the To property must be set in the Property window. Also, refer to Assign Data for Message Dialog Box.

The AssignMessage activity may throw one of the following exceptions: AssignMessageException or NullReferenceException.

Throw

Use to throw the identified exception.

Once thrown, the exception can be caught by a matching Catch activity.

Certain activities throw exceptions to indicate abnormal processing conditions.

Use to explicitly throw an exception or throw a caught exception.

Once a throw activity is added to an event handler, the following properties must be set in the Property window: ExceptionCode, ExceptionSubCode, ExceptionName, and Message.

Catch

Use to catch the identified exception and specify the exception handling activities in the event that the specified exception occurs.

Once a catch activity is added to an event handler, the ExceptionName property must be set to an exception name that a Throw activity throws.

Process

Use to define a process that can package a sequence of instructions to perform a specific task as a unit.

Once a Process activity is added, the ProcessName property must be set in the Property window. ProcessName must be a valid C# identifier and unique in the orchestration.

CallProcess

Use to invoke the specified process in the orchestration.This activity may be used anywhere within a Start activity or Catch activity.

Once a CallProcess activity is added, the ProcessName and the Parameters collection properties must be set in the Property window. ProcessName identifies the process to call, and is selected from a list of available processes. The Parameters Collection shows the parameter assignments.

ExternalProcess

Use to define the signature of a process that integrates external code with orchestration.

Once an ExternalProcess activity is added, the ProcessName property must be set in the Property window. ProcessName must be a valid C# identifier and unique in the orchestration.

WriteLog

Use to write an entry to the trace log from orchestration. This activity may be placed anywhere within a Start activity or Catch activity.

Once a WriteLog activity is added, the LogLevel and LogMessage properties must be set in the Property window.

Switch

Use to start the candidate section selection process. The activity specifies the variable used to select the section. This activity may be used anywhere within a Start activity or Catch activity.

Once a Switch activity is added to an event handler, the SwitchSource property must be set in the Property window.

Case

Use to define one candidate section for the Switch activity. It specifies the value used in selecting this section.

Once a Case activity is added to an event handler, the CaseValue property must be set in the Property window.

Default

Use to define a candidate section to be executed if no other section is selected in the Switch activity.

If

Use to describe a condition that must be met. A Then activity is automatically nested under the If activity.

Once an If activity is added to an event handler, the Condition property must be defined in the Edit Condition Dialog Box.

This activity may throw the following exceptions: InvalidCastException, ArithmeticException, or NullReferenceException.

Else

Use to enclosed the actions that must occur if the If activity condition is False.

Then

Use to enclose the actions that must occur if the If activity condition is True.

WhileDo

Use to enclose activities that are repeated until the Boolean-valued condition evaluates to False.

Once a WhileDo activity is added to an event handler, the Condition property must be defined in the Edit Condition Dialog Box.

The WhileDo activity may throw one of the following exceptions: InvalidCastException, ArithmeticException, or NullReferenceException.

DoWhile

Use to enclose activities that are repeated once and repeated until the Boolean-valued condition evaluates to False.

Once a DoWhile activity is added to an event handler, the Condition property must be defined in the Edit Condition Dialog Box.

The DoWhile activity may throw one of the following exceptions: InvalidCastException, ArithmeticException, or NullReferenceException.

PickMessage

Use to a cause a branch to an IsMessage activity or an IsOther activity based on the message type of Orch.Message, which contains the last message received from the server application.

IsMessage

Use to enclose activities that are executed when the Orch.Message is a particular server message.

Once an IsMessage activity is added to an event handler, the Message property must be defined in the Property window.

IsOther

Use to enclose activities that are executed when the Orch.Message is not a server message that is defined in an IsMessage activity.

Connect

Use to attempt to establish a connection to the server application.

Once a Connect activity is added to an event handler, the properties for the activity must be set appropriately in the Property window. Also, refer to Assign Data for Message Dialog Box.

The Connect activity may throw the ConnectFailedException.

Disconnect

Use to disconnect from the server.

InvokeServer

Use to invoke the server application by sending a server message and receiving a server message response.

The ReceiveTimeoutException is thrown if a message is not received from the server within the specified time.

Once an InvokeServer activity is added to an event handler, the properties for the activity must be set appropriately in the Property window. Also, refer to Assign Data for Message Dialog Box.

The InvokeServer activity may throw one of the following exceptions: ConnectorException, ReceiveTimeoutException, or AssignMessageException.

ReceiveServer

Use to receive a server message response from the server application.

The ReceiveTimeoutException is thrown if a message is not received from the server within the specified time.

Once a ReceiveServer activity is added to an event handler, the properties for the activity must be set appropriately in the Property window.

The ReceiveServer activity may throw one of the following exceptions: ConnectorException, ReceiveTimeoutException, or AssignMessageException.

SendServer

Use to send a server message to the server application.

Once a SendServer activity is added to an event handler, the properties for the activity must be set appropriately in the Property window. Also, refer to Assign Data for Message Dialog Box.

The SendServer activity may throw the ConnectorException.

OnClientRequest

Use to insert an event handler that is used when a client message is received from the client.

Once an OnClientRequest activity is added to an event handler, the Message property must be set in the Property window.

ReplyToClient

Use to send a reply to the client.

Once a ReplyToClient activity is added to an event handler, the properties for the activity must be set appropriately in the Property window. Also, refer to Assign Data for Message Dialog Box.

The ReplyToClient activity may throw the ConnectorException.

MessageFilter

Use to specify the message filter for each message sent or received from the server.

Once an MessageFilter activity is added, the MessageFilterName property must be set in the Property window. MessageFilterName must be a valid C# identifier and unique in the orchestration.