With this release we enabled lowering the recipe visibility using an API call.
To lower the visibility use the /v2/recipes/{RECIPE_ID}/visibility
API endpoint.
Check our API documentation for exact API call format.
To remind, the visibility can be workspace
, contract
and tenant
. The workapace
is the lowest visibility. Please note the following before trying to lower the visibility:
We extended the recipe creation API to include the author
attribute as well.
Here is an example section of the recipe draft:
{
"data": {
"type": "recipe",
"attributes": {
"info": {
"title": "My simple recipe",
"author":"THE AUTHOR OF RECIPE NAME IS LOCATED HERE",
"short_description": "The short description text is here",
"description": "Long description text goes here."
},
With this release we improved the conditions when the polling flows start after you update and publish the draft which replaces the active flow.
When you publish a new draft over the active flow it would not trigger a new execution, but will wait and run it on next due execution time.
Please note: If you need to execute your flow right away you can always press Run now to do so.
We started an audit of code in our components against the possibility of them exposing sensitive data in the logs. The following components were checked and potential parts refactored:
Introducing new component Oracle JDE Edwards EnterpriseOne Orchestrator.
Execute an Orchestration
actionQuery
action metadata with additional options