HTTP-request: automatically implement or approve change
Disclaimer : Over the years, the use of HTTP-actions is gradually being discouraged and replaced by API's. These API's can be used in action sequences.
Disclaimer : Over the years, the use of HTTP-actions is gradually being discouraged and replaced by API's. These API's can be used in action sequences. While HTTP-actions will still work within the change module, they too will some day be end of life. If you are affected by this change, read our landing page regarding this change: KI 14437 - Changes to HTTP Save Actions - FAQ. An alternative with an action sequence for this HTTP request can be found in KI 11149 - Action Sequence: Automatically approve Change request. Disclaimer: Because of changes in the authentication mechanism of TOPdesk in Q4 of 2018, passwords in http-requests might no longer work. For more information, please refer to KI 10571. Answer: It is possible to control the processing status of a change using an HTTP-request. These HTTP-requests are not the same in all versions of TOPdesk. The following HTTP-request can close an extensive change in TOPdesk versions 4.4. through 5.3.SP1: http://[SERVER:PORT]/tas/secure/newchange?action=edit&unid=[-UNID-]&field0=currentphase&value0=7&j_username=USERNAME&j_password=PASSWORD&save=true&save=true&validate=false The following HTTP-request can close or approve an extensive change from TOPdesk 5.4 onwards: http://[SERVER:PORT]/tas/secure/newchange?action=edit&unid=[-UNID-]&field0=authorized&value0=true&j_username=USERNAME&j_password=PASSWORD&save=true&validate=false The following HTTP-request can authorize a Preliminary Request for Change and fill a Manager in (with the manager of choice instead of "_FILL_THE_MANAGER_HERE_"): http://[SERVER:PORT]/tas/secure/newchange?action=edit&unid=[-UNID-]&field0=authorized&value0=true&replacefield0=req_authpersonid&searchfield0=ref_dynanaam&searchvalue0=\U_FILL_THE_MANAGER_HERE_\u&j_username=USERNAME&j_password=PASSWORD&save=true&validate=false These HTTP-requests can for instance be triggered when all underlying change activities have been completed, and the change may be authorized. The HTTP-request will need to be linked to an event with the following format: - Occurs with Edit card - When Change in Progress can be authorized will be changed to True