Skip to main content

<reply>

Send a response from a business process before its execution is complete.

Syntax

<reply/>

Attributes and Elements

name, disabled, xpos, ypos, xend, yend attributes

Description

The “primary response” from a business process is the response it returns to the request that originally invoked the specific business process instance. Normally, the business process will return its primary response automatically, as soon as it is done executing. However, the <reply> element can be used to return the primary response sooner. This can be useful if the response needed by the original caller is ready to be returned, but there is additional work for the business process to perform as a result of the original call.

The <reply> element returns the response object from the business process execution context, so a business process must use the <assign> element to assign values to properties on the response object, prior to making a <reply>.

Note:

There is more information about the business process execution context in the documentation for <assign>.

Example

The following example shows the reply action, used to return a response before continuing to execute the rest of the business process:

<call name="FindSalary" target="MyApp.PayrollApp" async="1">
    <request type="MyApp.SalaryRequest">
        <assign property="callrequest.Name" value="request.Name" />
        <assign property="callrequest.SSN" value="request.SSN" />
    </request>
    <response type="MyApp.SalaryResponse">
        <assign property="context.Salary" value="callresponse.Salary" />
    </response>
</call>
<assign property="response.Salary" value="context.Salary" />
</reply>
<call name="UpdateSalaryCache" target="MyApp.PayrollApp" async="0">
    <request type="MyApp.SalaryCacheRequest">
        <assign property="callrequest.SSN" value="request.SSN" />
        <assign property="callrequest.Salary" value="context.Salary" />
    </request>
</call>

FeedbackOpens in a new tab