Job execution requests contain two java maps (string and object) serialized with jobContext and workflowContext variables.
In the recent version of Flex JEF Script action, those variable are only accessible with the getters getJobContextVariables and getWorkflowContextVariables on the context variable.
Example
def execute() {
def jobContext = context.getJobContextVariables()
def workflowContext = context.getWorkflowContextVariables()
}
Enterprise
Enterprise carries out the following functions during execution:
- Fills in using the job and context variables upon launching a job.
- Updates the job and workflow context variables when JEF returns the job response.
Services
Plugin developers running executors can carry out the following:
- Receive job and workflow contexts:
String strAssetId1 = (String) jobContextVariables.get("asset");
String strAssetId2 = (String) workflowContextVariables.get("asset"); - Update the job and workflow context variables to send back the response:
jobResponse.setJobContextVariable("asset", “new value”);
Job and workflow context variables are only updated if changes have been made.
The following expressions are supported in workflow string variables for Demux and Segemented Proxy actions in order to pass lists of assets: <samp class="ph codeph">[x,y,z]</samp> and <samp class="ph codeph">x,y,z</samp>.
The following expressions are supported in workflow string variables for Demux and Segemented Proxy actions in order to pass lists of assets: <samp class="ph codeph">[x,y,z]</samp> and <samp class="ph codeph">x,y,z</samp>.
Comments
0 comments
Please sign in to leave a comment.