Table groups

When your workflow grows the workspace may become cluttered with tables. Typically, it's a sign that tables in the workflow should be split into two or more table groups where each group is located in a separate tab. Tabs in EasyMorph are similar to sheets in Excel, in a way.

To create a new group, simply create a new tab in the workspace (just like you create a new sheet in Excel). When a new group is created you can either create new tables in it by adding new data, or move tables from other groups (tabs). To move a table into another group, right-click the table's title bar and select "Move to tab...". It is also possible to derive a new table in a new tab.

create new group

Actions in table in one group may reference tables from other groups. The order of tabs doesn't affect the order of workflow execution (again, similarly to Excel). Tabs can be moved left or right just by dragging them.

Naming groups (tabs)

The best practice is splitting a workflow into logical phases or stages where each group corresponds to a phase (stage), and naming groups accordingly. A group name should provide a rough idea on what's going on inside the group. A few examples of good names for groups (notice the imperative naming style):

  • Fetch raw data
  • Check data quality
  • Clean up
  • Calculate attributes
  • Aggregate
  • Calculate metrics
  • Export

Hint:to quickly switch between groups press Ctrl+Tab, or Ctrl+Shift+Tab.

Naming tables

Tables in EasyMorph have a dual nature because they can represent a data entity or an operation, or both. Most frequently, tables are named semantically after the data entity that the table produces (i.e. the table result). In other words, do not name tables after the data that a table receives as input. Name tables after their outputs. A few examples of good names for tables:

  • Orders
  • Orders with extra attributes
  • Region lookup table
  • Customer metrics weekly
  • Export

It is especially helpful to name tables semantically if they are referenced in other tables in such actions as "Merge" or "Append".

If the purpose of a table is to perform an operation (especially an external one) then it may not have a semantic data entity as its output. In this case, name the table after the high-level operation performed by the actions in this table. A few examples of good names for such tables:

  • Export to database
  • Upload modified files
  • Send email notification
  • Validate parameters

Hint: to quickly rename a table press F2. Press Ctrl+F2 to select next table.


Read next: Export data into files