Documentation

Trace:

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
workflow:rest_api [2019/03/19 15:59]
admin
workflow:rest_api [2020/06/12 15:01] (current)
cduncan Edited for English grammar (capitalization, punctuation, correct verb conjugation)
Line 1: Line 1:
 ~~NOTRANS~~ ~~NOTRANS~~
-~~Title: ​Custom function~~+~~Title: ​REST API~~
  
-The REST API is part of the product and API documentation is available with Swagger UI in [[visionx:​home|VisionX]],​ e.g.: \\ +The [[jvx:​common:​util:​rest|REST API]] is part of the product and API documentation is available with [[https://​swagger.io/​tools/​swagger-ui/​|Swagger UI]] in [[visionx:​home|VisionX]],​ e.g.: \\ 
 ''<​nowiki>​http://​localhost/​swagger/?​url=http://​localhost/​app/​webcontent/</​nowiki>​**<​fc #​BF0000>​Appname</​fc>​**/​workflow.json''​ ''<​nowiki>​http://​localhost/​swagger/?​url=http://​localhost/​app/​webcontent/</​nowiki>​**<​fc #​BF0000>​Appname</​fc>​**/​workflow.json''​
  
-The port may be different in your environmentif port 80 is not available, e.g. localhost:​8080.+The port may be different in your environment if port 80 is not available, e.g. localhost:​8080.
  
 If you want to start a workflow with Java directly, it's no problem: If you want to start a workflow with Java directly, it's no problem:
Line 43: Line 43:
 }</​file> ​ }</​file> ​
  
-Note that the URL is different in the Java callbecause the Swagger UI was used from VisionX and the manual call assumes that the application runs deployed with an application server like Tomcat.+Note that the URL is different in the Java call because the Swagger UI was used from VisionXand the manual call assumes that the application runs deployed with an application server like Tomcat.
This website uses cookies for visitor traffic analysis. By using the website, you agree with storing the cookies on your computer.More information