The get/check-out and submit/check-in operations are implemented using two REST Web service commands: do.ashx?cmd=clientget and do.ashx?cmd=clientput.

clientget

The clientget Web service command gets the data of an object that should be stored in the file on the client computer.

http://myserver/GNPortal/do.ashx?cmd=clientget&id=1664&name=MimoPC

The command above returns the data of the object with id 1664 to be stored in the client computer with the clientSpec ‘MimoPC’.  (Call ‘do.ashx?cmd=help&name=clientget’ to see all the options of the clientget command – including those related to checking-out the object).

clientput

The clientput Web service command must be called with an HTTP POST – where the POSTed data is the content of the file on the client computer. For example, POSTing the file to:

http://myserver/GNPortal/do.ashx?cmd=clientput&id=1664&name=MimoPC

causes the system to update the content of the object with id 1664 using the POSTed data, that is passed to the update workflow specified in the clientSpec MimoPC. (call do.ashx?cmd=help&name=clientput to see all of the options of the clientput command – including those related to checking-in the object).

Note

cmd4 clientget and clientput commands internally use calls to the above Web service commands, plus some SOAP calls, to retrieve information about the objects to check-out or check-in.