Provide documentation about the server workflow API
Terminée
Please provide documentation about the server workflow REST API, similar to the reporting and printing modules, which are documented here and here.
Bonus points for adding reference to all three to the developer site.
-
Commentaire officiel
The REST API for Workflow Server can be found via this URL when installed on-premises:
https://<host>/vertigisstudio/workflow/service/specification(Assuming the default Virtual Directory was chosen in the Post Installer.)
-
Berend Veldkamp
Is this not (partially?) documented here in a workflow deployment ...\Workflow\Web\service\Specification\swagger.json
1 -
Ken Lyon
Can you please update the swagger api and docs to include all of the REST api's around managing workflows. Watching the web traffic, specifically around server side workflows, it is missing documentations for the folllowing end points:
workflow/service/auth/token/designer (POST Request)
workflow/service/designer/workflows (POST Request)0 -
@...
There are no plans to support third-part designers at this time.0 -
Ken Lyon What do you mean with ‘third-part designers'?
0 -
Nico Burgerhart Sorry, I was maybe jumping a few steps ahead in my mind. I think the endpoints referred to are only relevant for communication between the designer and the server. These are used when editing a workflow, not running one. You would likely only use them if you intended to write your own custom code for submitting edits to the server.
0 -
Ken Lyon
We are using those end points to move server side workflows between environments that are hosted on different machines. Not for building out a tool to replicate the workflow tooling or creating our own from code.
0 -
@... I'm interested to learn more about your goal with this. You have two different machines, and you wish to move workflows from one machine to the other.
Are you deleting them from the source or they just being copied?
What is being done with them on the destination? Do you have a separate installation of Workflow Server there that's using them?
If so, what is the motivation behind having more than one installation?0 -
Ken Lyon
We have different environments for dev, test, and prod. For each layer we have a stack of servers with the products on them. We do all of our development in dev then promote the workflow up through the environments. Then we do a UAT in test followed by a final push into prod.
To keep all of the portal Id's the same we have a python script that moves the portal items between the portals. For the server side workflows we then run a second script that then pushes the script from the lower workflow server to the next environment.
0
Vous devez vous connecter pour laisser un commentaire.
Commentaires
9 commentaires