New Ranks & Badges For The Community!
Notice something different? The ranks and associated badges have gone "Star Fleet". See what they all mean HERE

Synchronous REST API for flows execution

Idea ID 1664656

Synchronous REST API for flows execution

Users would ike synchronous REST API for flows exection so that busy-waiting on client side to be avoided.

This can be implemented by exposing a sync/async parameter to the OO REST API.

 

9 Comments
Micro Focus Expert
Micro Focus Expert
Status changed to: Waiting for Votes
 
Cadet 3rd Class Cadet 3rd Class
Cadet 3rd Class

This would be useful when calling OO flows from HCM Dynamic JS options too.

Ensign Ensign
Ensign

This could be very handy

Micro Focus Contributor
Micro Focus Contributor

This feature was available in the old SOAP API so I think the fact it is missing in the REST API makes this a bug not an "idea".

Micro Focus Frequent Contributor
Micro Focus Frequent Contributor
Status changed to: Declined

The implications of implementing this idea, the way it was requested, poses security concerns and we are declining this idea. 

In the future releases we would like to introduce publish/subscribe notifications that will address also this request.

Micro Focus Contributor
Micro Focus Contributor

Hi FlorinM

We have waiting over a year for someone to evaluate this "idea" so could you be so kind as to elaborate why you have declined this?

What security concern do you have when HTTPS and credentials are used?

You say that a future release may include a feature "publish/subscribe notifications", what is  this and how will it work?  

Regards Mark 

Micro Focus Frequent Contributor
Micro Focus Frequent Contributor

@Mark4 , in order to implement a synchronous connection we would need to use web sockets. Now consider multiple long running flows (more than 12 hours for example). Implementing synchronous REST APIs this way and having such flows will easily lead to resource exhaustion, thus having the system vulnerable for DOS attacks.
The future direction is to move to an event based implementation. At the moment there are no publicly available information for this capability, but we will announce it when it will be ready to be released.

Micro Focus Expert
Micro Focus Expert

In a cloud native world like, both invocation types are usually supported async (event based) and sync. It will be great for Micro Focus OO to align with AWS Lambda or other orchestration tools where both invocation types (sync and async) are supported. 

Possible workaround is to use this Community/Open Source Tool:  

https://marketplace.microfocus.com/itom/content/flowinvoke

Micro Focus Expert
Micro Focus Expert

@FlorinM  I'm wondering why not provide this option and let the users choose . There could be users with flows running less time and not willing to implement their own REST client to wait for flows executiom

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.