jlanka Contributor.
Contributor.
267 views

REST call path on 2018.05

Jump to solution
Spoiler
We are upgrading to 2018.05 from 10.22.  On 10.22 we used this path to make a REST call:  https://centralname:8443/oo/rest/latest/executions  But on 2018.05 that doesn't seem to work.  If we substitute v1 for latest it works but we have a lot of code that references the URL with latest.  Any thoughts on getting that to work?

Thanks in advance
0 Likes
1 Solution

Accepted Solutions
Micro Focus Expert
Micro Focus Expert

Re: REST call path on 2018.05

Jump to solution

Hello Jlanka,

 

Thank you for contacting Micro Focus Forum. My name is Carlos, I am from the OO/CSA team

 

Could you please share what is the error you get and what is the body used for the call?

 

Thanks! 

 

 

Carlos Rojas
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation.
0 Likes
4 Replies
Micro Focus Expert
Micro Focus Expert

Re: REST call path on 2018.05

Jump to solution

Hello Jlanka,

 

Thank you for contacting Micro Focus Forum. My name is Carlos, I am from the OO/CSA team

 

Could you please share what is the error you get and what is the body used for the call?

 

Thanks! 

 

 

Carlos Rojas
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation.
0 Likes
jlanka Contributor.
Contributor.

Re: REST call path on 2018.05

Jump to solution

This is the call with the v1 in the path. It gets back a response with the run ID:
curl -k -u "username:password" -X POST -H "Content-Type:application/json" -d '{"uuid":"01d4476c-b9fb-435f-990b-897f3f85e3fb","inputs":{"groupName":"a","groupMembers":"a,b,c","domain":"CORP"}}' "https://servername:8443/oo/rest/v1/executions"
{"feedUrl":"https://servername:8443/oo/rest/v1/executions/231300194/steps","executionId":"231300194","errorCode":"NO_ERROR"}

This is the call with latest in the path. It gets back no response:
curl -k -u "username:password" -X POST -H "Content-Type:application/json" -d '{"uuid":"01d4476c-b9fb-435f-990b-897f3f85e3fb","inputs":{"groupName":"a","groupMembers":"a,b,c","domain":"CORP"}}' "https://servername:8443/oo/rest/latest/executions"

This is the call with v2 in the path, it also gets back no respons:
curl -k -u "username:password" -X POST -H "Content-Type:application/json" -d '{"uuid":"01d4476c-b9fb-435f-990b-897f3f85e3fb","inputs":{"groupName":"a","groupMembers":"a,b,c","domain":"CORP"}}' "https://servername:8443/oo/rest/v2/executions"

0 Likes
Micro Focus Expert
Micro Focus Expert

Re: REST call path on 2018.05

Jump to solution

Hi Jlanka,

 

This might be because the body has some changes in this version. If you look at the API documentation (here) you will notice that you need to use flowUuid instead of uuid.

 

Please give it a try and let us know.

 

Thanks! 

Carlos Rojas
Customer Support Engineer

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation.
0 Likes
jlanka Contributor.
Contributor.

Re: REST call path on 2018.05

Jump to solution

yes, changing uuid to flowUuid fixed the problem.  Thank you very much

 

0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.