overview
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
| overview [2020/11/26 16:52] – [Actions] dmitry | overview [2020/11/26 17:03] – [Workflow automation] dmitry | ||
|---|---|---|---|
| Line 76: | Line 76: | ||
| * EasyMorph datasets (.dset) | * EasyMorph datasets (.dset) | ||
| - | ==== Automation | + | ==== Workflow automation |
| - | EasyMorph workflows can have following automation: | + | EasyMorph workflows can perform external actions, for instance: |
| * File and folder operations (copy/ | * File and folder operations (copy/ | ||
| * Running external applications, | * Running external applications, | ||
| Line 83: | Line 83: | ||
| * Embedded PowerShell scripting | * Embedded PowerShell scripting | ||
| + | A workflow can be composed using advanced patterns: | ||
| + | * FOR..EACH type of loops (iterations) | ||
| + | * DO..WHILE/ | ||
| + | * IF..THEN..ELSE type of conditional branching | ||
| + | * Subroutines | ||
| + | * Error recovery | ||
| + | |||
| + | Workflows can have complex hierarchical structure when a project can consist of multiple modules, and each module can consist of multiple table groups. Such a structure allows designing and navigating workflows with hundreds of transformation steps (actions). | ||
| ==== Integration with external systems ==== | ==== Integration with external systems ==== | ||
| EasyMorph workflows can also integrate and interact with external systems and applications. | EasyMorph workflows can also integrate and interact with external systems and applications. | ||
overview.txt · Last modified: 2022/07/22 04:36 by dmitry