eQuipAPI

CallButtonWorkflowFromTrackingWorkflowFormSubTransaction

The following routes are available for this service:
All Verbs	/CallButtonWorkflowFromTrackingWorkflowFormSubTransaction

**CallButtonWorkflowFromTrackingWorkflowFormSubTransaction** Parameters:
Name	Parameter	Data Type	Required
UserID	query	string	No
WorkflowID	query	string	No
TransactionID	query	int	No
TransactionTableID	query	int	No
TransactionTableName	query	string	No
TrackingFormDataCollection	query	List<FormData>	No

**FormData** Parameters:
Name	Parameter	Data Type	Required
FieldID	body	int	No
FieldName	body	string	No
FieldValue	body	Object	No
FieldType	body	short	No

To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml

HTTP + XML

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /xml/oneway/CallButtonWorkflowFromTrackingWorkflowFormSubTransaction HTTP/1.1 
Host: equipstage3.e-isg.com 
Content-Type: application/xml
Content-Length: length

<CallButtonWorkflowFromTrackingWorkflowFormSubTransaction xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/eQuipModel">
  <TrackingFormDataCollection xmlns:d2p1="http://schemas.datacontract.org/2004/07/eQuipLib.Workflow">
    <d2p1:FormData>
      <d2p1:FieldID>0</d2p1:FieldID>
      <d2p1:FieldName>String</d2p1:FieldName>
      <d2p1:FieldType>0</d2p1:FieldType>
      <d2p1:FieldValue />
    </d2p1:FormData>
  </TrackingFormDataCollection>
  <TransactionID>0</TransactionID>
  <TransactionTableID>0</TransactionTableID>
  <TransactionTableName>String</TransactionTableName>
  <UserID>String</UserID>
  <WorkflowID>String</WorkflowID>
</CallButtonWorkflowFromTrackingWorkflowFormSubTransaction>