Configuring Dynamic Job Configuration using JSON Metadata Instances

Enterprise allows you to configure an ActionConfig dynamically, e.g. in a workflow execution, an existing groovy script can update and set the configuration to be used by the following ActionConfig using a json-metadata-instance.

JEF supports <action-node-name>-json-metadata-instance dynamic updates if the context variable is set in the workflow before job execution, e.g. setting the following workflow context variable will change the configuration of the “Smoke 1” Action Config:

{
 "Smoke 1-json-metadata-instance" : "{\"expected-success\": false,\"milliseconds-to-wait\": 
100,\"count\": \"1\", \"resume-supported\":false,\"update-interval\":1}"
}
If the configured json-metadata-instance is incorrect and no ActionConfiguration can be instanced, the following occurs:
  • If the first node of the workflow is incorrectly configured, then the workflow is not created.
  • If the second or subsequent node of the workflow is incorrectly configured, then the workflow stays in running node.
Note: This behaviour is the same for other, non-JEF actions.
https://help.ooyala.com/sites/all/libraries/dita/en/media-logistics/flex/dev/70/jef_config_using_json.html

Was this article helpful?