Table to XLog Converter

This node converts a Data Table from KNIME platform into an event log PortObject. CaseID, Event class, time stamp and format are mandatory to set up in the first table; In table "Choose Attribute Set", other attributes for traces and events are set optional due to the need. In Expert Choice, it lists the strategy to handle error, empty cells and the XFactory to create event log.

Options

Standard Options

Case ID

Choose one column as caseID for the event log

Eventclass

Choose one column as eventID for the event log

Life Cycle

Choose one column as life cycle for the event log. If there is no such column, choose the option NO AVAILABLE.

Time Stamp

Choose one column as time stamp for events in the event log. It should be in format of ZonedDateTime or DateTime format. Else, the configuration error is given.

Choose Attributes Set

Trace Attributes

Choose table columns as trace attributes. For all events with in one trace, they are supposed to have the same values for each trace attributes. Else, it will omit this trace in the event log. Values from included columns will be shown as the attributes for each trace. Please make sure the columns chosen in "Standard Options" are included; else, it will give the InvalidConfiguration Error.

Event Attributes

Choose table columns as event attributes. Values from included columns will be shonw as the attributes for event. Please make sure the columns chosen in "Standard Options" are included; else, it will give the InvalidConfiguration Error.

Expert Choice

XFactory

XFactory implementation that is used to create the log. Some implementations might be more memory efficient, consider changing this in case you import a huge log. Additional Conversion Options (Defaults are a good guess)

Error Handling

The strategy to stop conversion upon malformed input or try to import as much as possible.

Sparse / Dense Log

This affects how empty cells in the CSV are handled. Exclude (sparse) or include (dense) empty cells in the conversion. Some plug-ins require the log to be dense, i.e., all attributes are defined for each event. In other cases it might be more efficient or even required to only add attributes to events if the attributes actually contain data.

Views

This node has no views

Workflows

• Event Log Filtering & DiscoveryKNIME Hub

Links

• No links available

Developers