element startPageFlow

diagram |
namespace | http://pageflow.api.pfe.n2.tibco.com
properties |
content | complex
children | pageFlowDefinition formalParams responsePayloadMode cacheTimeout
annotation |
documentation
Request element for startPageFlow operation.
source | <xs:element name="startPageFlow"> <xs:annotation> <xs:documentation>Request element for startPageFlow operation.</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="pageFlowDefinition" type="pfecom:PFETemplate"> <xs:annotation> <xs:documentation>Unique identifier of the pageflow to be started.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="formalParams" type="df:dataPayload" minOccurs="0"> <xs:annotation> <xs:documentation>Data for the formal parameters associated with the pageflow start event. Note: You cannot determine the names of these formal parameters programmatically. Instead, you must obtain them by examining the process in TIBCO Business Studio.</xs:documentation> </xs:annotation> </xs:element> <xs:element name="responsePayloadMode" type="df:payloadModeType"> <xs:annotation> <xs:documentation>Enumerated value defining the format of the data payload to be used in the response message (XML or JSON). If not specified, the default value is JSON. (RSS is currently not supported.) </xs:documentation> </xs:annotation> </xs:element> <xs:element name="cacheTimeout" type="xs:long" minOccurs="0"> <xs:annotation> <xs:documentation>**PRIVATE API - Reserved for internal use** Timeout value (in minutes) for the pageflow activity.</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType> </xs:element>

WSDL documentation generated by XMLSpy WSDL Editor http://www.altova.com/xmlspy