eQuipAPI

GetMobileWorkflowTransactions

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

**GetMobileWorkflowTransactions** Parameters:
Name	Parameter	Data Type	Required
UserID	query	string	No
Workflow_configuration_id	query	string	No
transactionID	query	int?	No
ReturnSize	query	int?	No

**TransactionsResult** Parameters:
Name	Parameter	Data Type	Required	Description
Transactions	body	List<Transaction>	No

**Transaction** Parameters:
Name	Parameter	Data Type	Required
TransactionID	body	int	No
TransactionGuid	body	string	No
TransactionFields	body	List<TransactionID>	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/reply/GetMobileWorkflowTransactions HTTP/1.1 
Host: equipstage2.e-isg.com 
Content-Type: application/xml
Content-Length: length

<GetMobileWorkflowTransactions xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/eQuipModel">
  <ReturnSize>0</ReturnSize>
  <UserID>String</UserID>
  <Workflow_configuration_id>String</Workflow_configuration_id>
  <transactionID>0</transactionID>
</GetMobileWorkflowTransactions>

HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length

<TransactionsResult xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/eQuipModel">
  <Transactions>
    <Transaction>
      <TransactionFields>
        <TransactionID>
          <FieldName>String</FieldName>
          <FieldValue />
        </TransactionID>
      </TransactionFields>
      <TransactionGuid>String</TransactionGuid>
      <TransactionID>0</TransactionID>
    </Transaction>
  </Transactions>
</TransactionsResult>