workflows:workflow_building
Differences
This shows you the differences between two versions of the page.
Next revision | Previous revision | ||
workflows:workflow_building [2019/12/12 16:24] – created benjamin | workflows:workflow_building [2021/02/11 20:49] (current) – [Error handling] benjamin | ||
---|---|---|---|
Line 1: | Line 1: | ||
- | =====Workflow operating principle===== | + | ====== Workflow operating principle |
To create a first simple encoding workflow, right click on the job canvas, choose ' | To create a first simple encoding workflow, right click on the job canvas, choose ' | ||
Line 6: | Line 6: | ||
Link them together, left mouse click on output' | Link them together, left mouse click on output' | ||
- | {{ :processor_example_1.jpg?600 |}} | + | {{ workflows:processor_example.png?nolink600 |
Set your watch path in Monitor Node, configure your H264 encoder Processor and choose a destination folder in Delivery Node. The workflow is ready. | Set your watch path in Monitor Node, configure your H264 encoder Processor and choose a destination folder in Delivery Node. The workflow is ready. | ||
Start the workflow with a right click on workflow' | Start the workflow with a right click on workflow' | ||
+ | You can submit manually a file (even if your workflow is disabled) by right-click on monitor node and choose ' | ||
+ | |||
+ | |||
+ | --------------------------------------------------------------- | ||
=====Advanced Workflow===== | =====Advanced Workflow===== | ||
Line 20: | Line 24: | ||
====Working with variables==== | ====Working with variables==== | ||
- | __Download Link__ : {{working_with_user_variables.json}}\\ | + | __Download Link__ : {{ :working_with_user_variables.json}}\\ |
After importing the workflow, select it in your workflow list and right click-> submit file at the first node. | After importing the workflow, select it in your workflow list and right click-> submit file at the first node. | ||
It will copy the file you submitted to c:\temp (if the folder exists).\\ | It will copy the file you submitted to c:\temp (if the folder exists).\\ | ||
Line 44: | Line 48: | ||
* Once you created a variable, you can select it from the list in every processor of every workflow. But remember, it's value is empty by default when a job starts | * Once you created a variable, you can select it from the list in every processor of every workflow. But remember, it's value is empty by default when a job starts | ||
+ | -------------------------------------- | ||
====Working with Statics vs Variables==== | ====Working with Statics vs Variables==== | ||
- | __Download Link__ : {{working_with_statics_vs_variables.json}}\\ | + | __Download Link__ : {{:working_with_statics_vs_variables.json}}\\ |
This workflow shows whats the difference between a variable and a STATIC.\\ | This workflow shows whats the difference between a variable and a STATIC.\\ | ||
Line 61: | Line 66: | ||
7) Enter a value for the static. Note again that this value cannot be changed by a job\\ | 7) Enter a value for the static. Note again that this value cannot be changed by a job\\ | ||
- | ->Screen to promote with 1.0.0 version-> | + | {{: |
+ | ----------------------------------------------- | ||
====Error handling==== | ====Error handling==== | ||
- | __Download Link__ : {{working_with_errors.json}}\\ | + | __Download Link__ : {{:working_with_errors.json}}\\ |
This workflow is demonstrating how to catch and resolve errors.\\ | This workflow is demonstrating how to catch and resolve errors.\\ | ||
It first tries to deliver the input file to a share that actually does not exist. (wait a while, it will retry 100 times). When it fails, it will deliver to a fallback location. After that, we use a hold node with " | It first tries to deliver the input file to a share that actually does not exist. (wait a while, it will retry 100 times). When it fails, it will deliver to a fallback location. After that, we use a hold node with " | ||
I guess this is a little known but very powerful feature of FFAStrans workflows. Right click the input connector of a processor to select if the processor is executed on success, error or in any case.\\ | I guess this is a little known but very powerful feature of FFAStrans workflows. Right click the input connector of a processor to select if the processor is executed on success, error or in any case.\\ | ||
- | {{::execute_error.jpg?direct&400|}} | + | {{:workflows:error_handling.png?nolink&700|}} |
+ | |||
+ | ----------------------------------------- | ||
+ | |||
+ | |||
+ | < |
workflows/workflow_building.1576167883.txt.gz · Last modified: 2020/11/16 19:08 (external edit)