Table of Contents

Search

  1. Preface
  2. Overview, Downloading, and Installing
  3. Administration API
  4. Identity Service API
  5. Screenflow Programming and SDK
  6. ActiveVOS WSHT API
  7. Embedding Request Forms in Standalone Web Pages
  8. XML-JSON for Process Central

7. APIs, SDKs, and Services

7. APIs, SDKs, and Services

Reply Message

Reply Message

In earlier releases, a service call step was called a Service Call step.
The following sample data shows an example of the reply message:
<xsd1:automatedStepResponse xmlns:xsd1="http://schemas.active-endpoints.com/appmodules/ screenflow/2010/10/avosScreenflow.xsd"> <!--Optional:--> <xsd1:fields> <!--Optional:--> <xsd1:field name="string"/> </xsd1:fields> <!--Optional:--> <xsd1:guideData> <!--Optional:--> <xsd1:parameter name="string"/> </xsd1:guideData> </xsd1:automatedStepResponse>
The elements of the message are described in the following table:
automatedStepResponse output element
Description
fields
Contains the data described as output fields for the service call step. They are name/value pairs where the
name
is in the attribute name and the
value
is the data under the element. For both input and output, the field can be defined as complex (attribute
complex="true"
) in the
services.xml
file on the parameter or field). In that case, the value can be arbitrary XML that can be used in a renderer. See the Starter project example for a simple example used in Hello World.
guideData
Contains the new data to be set for the guide context data if the service has
passAllData="true"
in the
services.xml
file