eQuipAPI

<back to all web services

CheckTrackingWorkFowAssetIsEditablebyScopeAndReadOnly

Check asset is editable by scope and readonly

Check asset is editable by scope and readonly
CheckTrackingWorkFowAssetIsEditablebyScopeAndReadOnly Parameters:
NameParameterData TypeRequiredDescription
UserIDBodystringYesUser Internal ID
AssetListBodystringYesSelected AssetId For Edit
IsForDisabledAssetBodyboolNoGive for not use disabled asset
strWorkflowIDBodystringYesTracking WorkFlow Id
IsForButtonWfBodyboolNoGive for Button Workflow click
CreatedByUserIDBodystringNoThe user's ID created the transaction.

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

HTTP + SOAP11

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

POST /soap11 HTTP/1.1 
Host: equipstage2.e-isg.com 
Content-Type: text/xml; charset=utf-8
Content-Length: length
SOAPAction: CheckTrackingWorkFowAssetIsEditablebyScopeAndReadOnly

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
    <soap:Body>

<CheckTrackingWorkFowAssetIsEditablebyScopeAndReadOnly xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/eQuipModel">
  <AssetList>String</AssetList>
  <CreatedByUserID>String</CreatedByUserID>
  <IsForButtonWf>false</IsForButtonWf>
  <IsForDisabledAsset>false</IsForDisabledAsset>
  <UserID>String</UserID>
  <strWorkflowID>String</strWorkflowID>
</CheckTrackingWorkFowAssetIsEditablebyScopeAndReadOnly>

    </soap:Body>
</soap:Envelope>