eQuipAPI

CheckTransactionNameExistsOrNotInTransactionTable

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

**CheckTransactionNameExistsOrNotInTransactionTable** Parameters:
Name	Parameter	Data Type	Required
UserID	query	string	No
AssetList	query	string	No
tranTableID	query	string	No
TransactionId	query	int	No
tranTableName	query	string	No
TransactionCollection	query	List<SearchParamForTransaction>	No
AssetSearchConfigID	query	string	No
TargetWorkflowID	query	string	No
SourceWorkflowID	query	string	No
RequestedQuantityList	query	string	No
IncompleteTransaction	query	bool	No
IsAddToList	query	bool	No

**SearchParamForTransaction** Parameters:
Name	Parameter	Data Type	Required
FieldID	body	string	No
MappedFieldName	body	string	No
AssetField	body	string	No
FieldName	body	string	No
FieldValue	body	Object	No
Operator	body	string	No
FieldType	body	short	No
RecurrenceRuleEditorValueParamCollection	body	List<RecurrenceRuleEditorValueParam>	No

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

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

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

POST /json/oneway/CheckTransactionNameExistsOrNotInTransactionTable HTTP/1.1 
Host: equipstage2.e-isg.com 
Content-Type: application/json
Content-Length: length

{"UserID":"String","AssetList":"String","tranTableID":"String","TransactionId":0,"tranTableName":"String","TransactionCollection":[{"FieldID":"String","MappedFieldName":"String","AssetField":"String","FieldName":"String","FieldValue":{},"Operator":"String","FieldType":0,"RecurrenceRuleEditorValueParamCollection":[{"ActualValueType":"String","ActualValue":{}}]}],"AssetSearchConfigID":"String","TargetWorkflowID":"String","SourceWorkflowID":"String","RequestedQuantityList":"String","IncompleteTransaction":false,"IsAddToList":false}