Hello good night, I'm new in the world of VRealize Orchestrator, I will need import files type .workflow that I can download of this page, I have Version 8.1 it is possible? and how could i do it? and sorry for my bad English
Hello Ilian, thank you very much for your answer... then if I have a .workflow, I cant in any way to import a my Orchestrator? or can I to do a packet with this .workflow and import to Orchetrator?
This can be done only by using the REST api.
First you need to get the id of the category you want to import the workflow in by using the GET method of /vco/api/categories .
Then to import the .workflow file you will have to use the POST method of /vco/api/workflows .
You will need to provide the categoryId as a query parameter. ex: https://<orchestrator-fqdn>/vco/api/workflows?categoryId=8af885e971c499d70171c68d13ce0082
and provide the .workflow file as a form-data parameter with a key "file"
I am looking for additional info on the import function, I have tried to automate this through vro and have the export working using base64encode/decoding but I have yet to get the import API to function properly. I am returning a 405 and 406 error, The target resource does not have a current representation that would be acceptable to the user agent, according to the proactive negotiation header fields received in the request, and the server is unwilling to supply a default representation.
Hmm that doesn't seem accurate there is an API call for importing workflows requiring category ID, this is what I am exploring and attempting to get to work.
Please look at
If you have a ".workflow" file you can use a ZIP tool (e.g., 7-zip) to expand the contents like this
The file "workflow-content" is XML but you can read the workflow script / items within it. Also, the header elements will show the parameters, attributes etc
Worst case, by doing this you should be able to manually re-construct the workflow in your 8.1 instance (create new workflow, build out the items and copy in the script elements)
Not the most elegant but will work if you only have one workflow. If you have many then this could get pretty tedious
I have been able to get the import to work using postman successfully please see the postman code extract.