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:58] – [Automation] dmitry | overview [2021/05/05 15:07] – [Integration with external systems] dmitry | ||
---|---|---|---|
Line 9: | Line 9: | ||
* Text files with fixed width columns | * Text files with fixed width columns | ||
* Excel spreadsheets (.xlsx, .xlsm, .xls) | * Excel spreadsheets (.xlsx, .xlsm, .xls) | ||
- | * XML files | + | * XML and JSON files |
* Google Sheets | * Google Sheets | ||
* SharePoint lists | * SharePoint lists | ||
Line 17: | Line 17: | ||
* EasyMorph datasets (.dset) | * EasyMorph datasets (.dset) | ||
- | Once tables are loaded into EasyMorph they can further | + | Once tables are loaded into EasyMorph, they can be modified using actions (transformations) that are applied sequentially one after another. |
- | Databases can be queried using the visual Query Editor | + | Databases can be queried using the visual Query Editor intended for users who don't know SQL. |
Files can be loaded by simply dragging them into EasyMorph. It's possible to load and automatically append multiple files at once. | Files can be loaded by simply dragging them into EasyMorph. It's possible to load and automatically append multiple files at once. | ||
+ | |||
+ | [[https:// | ||
+ | [[https:// | ||
+ | |||
==== Actions ==== | ==== Actions ==== | ||
- | All manipulations with tables are done with the help of various [[[[transformations: | + | All manipulations with tables are done with the help of various [[[[transformations: |
* [[transformations: | * [[transformations: | ||
Line 38: | Line 42: | ||
The final state (result) of a table is the result of all actions of this table applied consequently, | The final state (result) of a table is the result of all actions of this table applied consequently, | ||
- | Some actions (e.g. [[transformations: | + | Some actions (e.g. [[transformations: |
==== Expressions ==== | ==== Expressions ==== | ||
Line 52: | Line 56: | ||
* [[syntax: | * [[syntax: | ||
* [[syntax: | * [[syntax: | ||
+ | |||
+ | [[https:// | ||
==== Derived tables ==== | ==== Derived tables ==== | ||
- | Derived tables | + | Derived tables |
+ | |||
+ | Since you can derive any number of tables from a table and then keep transforming every derived table in its own way, you can create non-linear action chains. For instance, you can produce two derived tables from a table, transform each of them in its own way and then append or merge them back into one table. | ||
- | Since you can derive any number of tables from a table, and then keep transforming every derived table in its own way, you can create non-linear action chains. For instance, | + | Derived tables |
- | Derived tables can be calculated | + | [[https://easymorph.com/learn/derived-tables.html|Tutorial: |
==== Data export ==== | ==== Data export ==== | ||
- | Exporting data is performed using export actions. They can be inserted at any point of workflow. Export actions do not modify tables, they just export them into specified file format or external system. Therefore the output of an export action is always | + | Exporting data is performed using export actions. They can be inserted at any point of workflow. Export actions do not modify tables. They export them into a specified file format or external system. Therefore the output of an export action is always the same as the input. |
As of version 4.5 EasyMorh can export into the following data formats and systems: | As of version 4.5 EasyMorh can export into the following data formats and systems: | ||
Line 75: | Line 83: | ||
* Qlik data files (.qvd) | * Qlik data files (.qvd) | ||
* EasyMorph datasets (.dset) | * EasyMorph datasets (.dset) | ||
+ | |||
+ | [[https:// | ||
+ | [[https:// | ||
==== Workflow automation ==== | ==== Workflow automation ==== | ||
Line 90: | Line 101: | ||
* Error recovery | * Error recovery | ||
+ | Workflows can have a 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 enterprise / cloud applications |
EasyMorph workflows can also integrate and interact with external systems and applications. | EasyMorph workflows can also integrate and interact with external systems and applications. | ||
Line 108: | Line 120: | ||
==== Auto-documentation ==== | ==== Auto-documentation ==== | ||
- | EasyMorph can automatically generate human-readable documentation in plain English for current project. Read more about [[documentation|Auto-documentation]]. | + | EasyMorph can automatically generate human-readable documentation in plain English for the current project. Read more about [[documentation|Auto-documentation]]. |
==== Scheduling ==== | ==== Scheduling ==== | ||
- | [[https:// | + | [[https:// |
+ | |||
+ | [[https:// | ||
==== Command-line execution ==== | ==== Command-line execution ==== | ||
- | EasyMorph projects can be executed from the command line thus allowing integration with third-party applications. Read more about [[command_line|command line parameters]]. | + | EasyMorph projects can be executed from the command line, thus allowing integration with third-party applications. Read more about [[command_line|command line parameters]]. |
- | A more robust integration option is the " | + | A more robust integration option is the " |
+ | |||
+ | [[https:// | ||
==== EasyMorph Server ==== | ==== EasyMorph Server ==== | ||
- | [[https:// | + | [[https:// |
==== EasyMorph Community ==== | ==== EasyMorph Community ==== | ||
The [[https:// | The [[https:// | ||
- | |||
**See also:** | **See also:** | ||
Line 130: | Line 145: | ||
* [[https:// | * [[https:// | ||
* [[https:// | * [[https:// | ||
+ | * [[https:// |
overview.txt · Last modified: 2022/07/22 04:36 by dmitry