| GET | /TrackingWorkflow/CheckAssetIsEditablebyScopeAndReadOnly | Check asset is editable by scope and readonly | |
|---|---|---|---|
| POST | /TrackingWorkflow/CheckAssetIsEditablebyScopeAndReadOnly | Check asset is editable by scope and readonly |
| Name | Parameter | Data Type | Required | Description |
|---|---|---|---|---|
| UserID | Body | string | Yes | User Internal ID |
| AssetList | Body | string | Yes | Selected AssetId For Edit |
| IsForDisabledAsset | Body | bool | No | Give for not use disabled asset |
| strWorkflowID | Body | string | Yes | Tracking WorkFlow Id |
| IsForButtonWf | Body | bool | No | Give for Button Workflow click |
| CreatedByUserID | Body | string | No | The user's ID created the transaction. |
To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml
The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.
POST /xml/oneway/CheckTrackingWorkFowAssetIsEditablebyScopeAndReadOnly HTTP/1.1
Host: equipstage2.e-isg.com
Content-Type: application/xml
Content-Length: length
<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>