Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
en:start [2016/07/08 13:58] admin [Workflow Designer] |
en:start [2019/06/10 10:59] admin |
||
|---|---|---|---|
| Line 2: | Line 2: | ||
| Documentation of my Workflow Designer Documentation. | Documentation of my Workflow Designer Documentation. | ||
| - | It could be used for the 5.40 and 6.x version. | + | It could be used for both 6.x and 7.x version. |
| {{ :en:import_searchcontact_create.png?nolink |}} | {{ :en:import_searchcontact_create.png?nolink |}} | ||
| Line 11: | Line 11: | ||
| - [[en:start:entitydata|EntityData]] | - [[en:start:entitydata|EntityData]] | ||
| - [[en:start:custom_functions|Custom Functions]] | - [[en:start:custom_functions|Custom Functions]] | ||
| - | - [[ru:start:developers|Developers]] | + | - [[en:start:developers|Developers]] |
| Line 20: | Line 20: | ||
| ==== Main differences to internal Module ==== | ==== Main differences to internal Module ==== | ||
| - | My Workflow Designer is build on single tasks, which could be combined in a individual way. For example you had the condition in the internal module, which would filter the execution of a workflow. In my module, every record execute every workflow. It is you task to filter these records, you want to interact with, with a Condition block. But here you could interact with the false path, too. | + | Workflow Designer is build on single tasks, which could be combined in a individual way. For example you had the condition in the internal module, which would filter the execution of a workflow. In my module, every record execute every workflow. It is you task to filter these records, you want to interact with, with a Condition block. But here you could interact with the false path, too. |
| Every task has one input and one or multiple outputs. The executer follows the path from one task to another and execute all tasks until the path end. You could connect two tasks in one output and split the execution into two paths. This is no problem. | Every task has one input and one or multiple outputs. The executer follows the path from one task to another and execute all tasks until the path end. You could connect two tasks in one output and split the execution into two paths. This is no problem. | ||