AutoGeneratePages

For T27 and UTS projects only:

For all project types:

DefaultReceiveHandling

Select ThrowException to throw an UnorchestratedMessageException when a client message is received and is not handled in the orchestration.

Select MapAndForward if AutoGeneratePages is set to True. When set to MapAndForward, the client message is mapped to a server message, the field data is mapped to the server message, and the server message is sent to the ClearPath application.

DefaultReplyHandling

Select ThrowException to throw an UnorchestratedMessageException when no reply is made to the client in the orchestration.

Select MapAndForward if AutoGeneratePages is set to True. When set to MapAndForward the last server message received is mapped to the client message of the same name, the field data is mapped to the client message, and the client message is sent to the client.

RequireLastReplyAsNextRequest

If True, the default behavior requires that the last message sent to the client is the next message received from the client. This mimics Web page form submission and provides a means of enforcing this behavior in orchestration.

If orchestration receives a client message out of sequence, the Orchestration will throw an OutOfOrderException.Uncaught orchestration exceptions are typically presented to the client as a code exception and may be caught and handled using normal exception handling techniques.

Generated ASP.Web pages will typically redirect the user to the page intended for next submission. This behavior can be overridden on a message-by-message basis by setting the value of RequireAsNextRequest property of the client Reply orchestration activity.

If you are using a Web service presentation, set this property to False.

The default setting is False.

UnrecognizedReceive

When ePortal does a receive operation (InvokeServer or ReceiveServer) with a receive message of Orch.Message, this is called a default receive operation.

Whenever orchestration performs a default receive operation, ePortal attempts to match the data received against each of the server records, with one or more identification fields, in your data source project. If the data received from the ClearPath system does not match any server records in your data source project, this is called an unrecognized receive.

The UnrecognizedReceive property is set to an output server message that is used to format the data when orchestration gets an unrecognized receive.

If you set this property to blank, an unrecognized receive results in an exception.

Refer to Using Orchestration to Identify an Output Server Message for more information.