EasyMorph Explorer

Boards are constructed by stacking sections of different types. Any board can have any combination of the following section types:

• Metrics and KPIs
• Shared files and folders
• Tables and charts
• Open issues (tickets)
• Automation tasks
• Data Catalog assets
• Links to external resources
• Multi-line text
• (Embedded) Tableau and Power BI dashboards

Unlike traditional dashboards, Explorer boards are intended for action and collaboration, not just for looking at charts and metrics.

• Upload and download files
• Trigger automation flows
• Create, assign, and resolve issues (tickets)
• Update records
• Find and retrieve documents (e.g. invoices)

From boards, you can navigate and explore your business data further by retrieving in one click detailed datasets, transactions, logs, related documents, analytical reports, or going to specific pages in other applications and websites (e.g., CRM systems, government portals, or BI applications).

Data tables (datasets) in the Catalog don't have to physically exist somewhere. They can be computed on demand with visual EasyMorph workflows. It helps avoid copying data, building dedicated analytical databases and data pipelines.

Computed datasets are always up to date and contain exactly the requested information. All you need to open them is to click a button.

Features:

• Computation parameters (e.g, period start and end dates)
• Download as Excel of CSV files
• View, filter, and analyze right in Explorer

In the Catalog, not only tables can be computed on they fly. Paths to files can also be dynamically computed on demand. As a result, one "computed" file asset (e.g., "Invoice") can provide access to many documents of the same type.

In a similar fashion, a weblink can be computed on demand as well. Such "smart" links can point to customer profiles in CRM systems, locations on Google Maps, or BI dashboards with pre-selected values in filters.

By using computed assets, the Catalog can "hyperlink" together data that resides in many disparate business systems. As a result, you can navigate and explore all your business data from one place, Explorer, no matter where it's physically located.

For instance, you can start by looking at recent orders, then go in one click from specific order to the customer who made it, then open the payment details and download the invoice. Even if all this data is stored in different business systems, you can still browse and open it in Explorer without leaving the application.

Create custom issue types for different types of tasks and notifications. Configure processing states for each type.

Examples:

• Data quality problem
• Alert about a KPI falling out of range
• Notification about incomplete orders
• Request to provide data
• Form submission from website
• Upcoming equipment maintenance

Besides regular file attachments, attach "smart" computed Catalog assets that provide more context and allow exploring data, retrieving documents related to this particular issue, or triggering pre-configured actions related to the issue (e.g., cancel the order).

All that makes issue resolution faster and more convenient as all the necessary information and automation is just a click away.

Issues are the center point of collaboration in Explorer which offers multiple ways to create (raise) issues throughout the application for user convenience. For instance, issues can be created right in Tasks, in File Manager, or in Analysis View.

Besides that, issues can be raised automatically in any EasyMorph workflow with the help of the "Raise issue" action.

Open the query result in Analysis View for fast in-browser filtering, analysis, and exploration.

Alternatively, download the full query result as a file in one of the following formats:

• CSV file
• Excel spreadsheet
• Apache parquet
• Qlik QVD
• Tableau Hyper

Organize queries into a querybook, a collection of queries to the same database. Share querybooks with your teammates to foster collaboration.

Share querybooks safely with less technical colleagues for easier collaboration. Leverage the role-based permissions configurable in the space settings to prohibit them from changing queries or saving changes.