1. Home Screen

The Home screen lists every process definition that has been created or initiated.
Selecting a process in the list shows its details on the right: creation date, creator, and upload status.

1.1 Viewing a Process

Select a process from the Process Definitions list to see its details.

If the upload finished successfully, Upload Status shows “Saved” and a “View Map” button appears, opening the process map for that process.

1.2 Abandoned Processes

A process whose upload did not complete shows Upload Status: False.
Users can select it and use “Delete abandoned Process” to remove it from the list.

1.3 Creating a New Process

Select “+ Create New” to open the Process Creation Wizard. Enter a process name and select Next to begin the five-step upload process described in Section 2.

Existing process names cannot be used to create a new process.

2. Wizard Steps

ProcessZoo Lite is structured as a five-step wizard. Each step builds on the data and configuration from the previous one. The current step is indicated by the step counter in the sidebar.

The wizard guides the upload of an event log file through five steps, shown in the left-hand panel: Upload Source File, Map Headers, Verify Schema, Verify Mapping, and Visualize Process Map.

2.1. Upload Source File

Select the upload area to choose a .csv or .txt file from your device.

2.1.1. File delimiter

Configures the character used to separate values in your file.

The following options are available:

• Comma ( , ) — Use if your file is a comma separated file.
• Semi-colon ( ; ) — Use if your file is a semi-colon separated file.

2.1.2. Date format

Configures how the timestamp column in your file should be interpreted.

ProcessZoo Lite supports the following options:

• MM/DD/YYYY (US) — Month-first date format.
• DD/MM/YYYY (UK/European) — Day-first date format.
• YYYY-MM-DD (ISO) — ISO 8601 date format.

Note: Selecting the wrong date format may cause timestamps to be parsed incorrectly in later steps.

Note: the upload is limited to 5000 rows per file, and only one file can be uploaded per process. Uploading a file exceeding this limit may only save the first 5000 rows or corrupt the process creation process entirely.

Select “Next” to continue once file configuration is done.

2.2. Map Headers

Maps the columns detected in your uploaded file to the three fields required by ProcessZoo Lite. The left column lists the required components; the right column provides a dropdown of all column headers found in your file.

2.2.1. Case Identifier

The column that groups individual events into a single case (process instance).

This field allows for a single column mapping. Any datatype is supported, saved as a text entity in the Dataverse table.

2.2.2. Event Identifier

The column that contains the activity or action name for each row.

This field allows for a single column mapping. Any datatype is supported, saved as a text entity in the Dataverse table.

2.2.3. Timestamp

The column that determines the chronological order of events within a case.

This field allows for a single column mapping. The mapped column must contain values parsable as a date, according to the date format configured in 2.1.2. The corresponding Datetime entity is saved in the Dataverse table.

Select “Back” to return to the previous step to readjust file configuration or replace uploaded file or continue once all three components are mapped.

2.3. Verify Schema

A visual confirmation step that displays the mapping defined in 2.2 before it is applied to your dataset.

It is a side-by-side comparison of the File Schema (the source column names) and the SCvation Schema (the internal component names) so the mapping from Section 2.2 can be reviewed.

2.3.1. File Schema

Displays the column names exactly as they appear in your uploaded file.

2.3.2. SCvation Schema

Displays the three standard field names (Case, Event, Timestamp) that ProcessZoo Lite uses internally, with an arrow indicating which file column maps to each.

If a mapping is incorrect, use Reconfigure mapping to return to 2.2. Otherwise, use Confirm schema to proceed.

2.4. Verify Mapping

A live preview of the event log, parsed using the delimiter, date format, and mapping configured in the previous steps.

2.4.1. Event log preview

Displays the first 10 rows of the parsed dataset in a table, with columns for row number, Case ID, Event, and Timestamp.

The active delimiter and date format are shown above the table for reference.

2.4.2. Row count

Displays the total number of rows detected across the full dataset, independent of how many rows are shown in the preview.

Select “Save Process” to upload the data to Dataverse. A “Saving to Dataverse” indicator appears while the upload is in progress.

2.5. Visualize Process Map

Generates an interactive process flow visualization from the event log saved to Dataverse.

2.5.1. Process graph

A directed graph in which each node represents an event and each connecting line represents a transition between two events. Each event node displays a count of its total occurrences. Each transition line displays a count and average duration for that specific event-to-event sequence.

2.5.2. Metrics panel

Displays summary metrics for the currently loaded process:

• Cases — Total number of distinct cases in the dataset.
• Variants — Total number of unique event sequences detected.
• Events — Total number of distinct event types.
• Rows Read — Total rows parsed from the source file.
• Avg Events / Case — Average number of events per case.
• Case/Variant Ratio — Ratio of cases to variants; lower values indicate greater process variability.

2.5.3. Golden path

The most frequently occurring event sequence in the dataset, automatically highlighted in the process graph to help identify the primary flow of the process.

Select “Next Steps” to continue or select the home icon to return to the home screen.

Note: If the data has a sizeable volume (1000 rows plus for a process) there may be delay between landing on the process map page and the generated process map being displayed to the user. An error message indicating the process not being found may be shown to the user. This is a timing issue between Dataverse and the update cycle of the custom component of the process map.