Search results

text input. QPR TaskRecorder collects the UI events to a CSV file, which can be uploaded to QPR ProcessAnalyzer for further analysis. QPR TaskRecorder

CaseAttributes, EventAttributes and Eventlog work only for the in-memory models and they require the model to be loaded into the memory. If the model is not in the

query, the individual expressions are run in following contexts: Root expression is run either in the EventLog or generic context, depending on the ContextType

is kept only in memory and not stored permanently in QPR ProcessAnalyzer. Suitable ODBC driver needs to be installed in QPR ProcessAnalyzer server, and

into QPR ProcessAnalyzer memory and the model doesn't have any of the other statuses that are for in-memory models. Note that in QPR ProcessAnalyzer, all

two types of charts available: in-memory chart (described by this article) used for calculating in QPR ProcessAnalyzer in-memory engine and the Big data

model can have an own business calendar and in addition, business calendars can be defined in custom expressions. In dimensions and measures calculating durations

model EventLog, containing all the events in the Model. In addition, there are filtered EventLogs which are subsets of a certain Model EventLog. The filter

which cases/events are included and which are excluded from the resulting dataset. Filters are very powerful feature in QPR ProcessAnalyzer, because any

Undesired event: the event occurred in the eventlog, but it's not in the design model and thus it should not occur at all. This deviation is not shown in Snowflake

by the QPR ProcessAnalyzer system. In-memory model API is the interface in the backend for the process mining calculations performed in the QPR ProcessAnalyzer

QPR ProcessAnalyzer queries for models data can be filtered to include only selected cases or events to the calculation. The expression query have the

datatables don't appear to QPR ProcessAnalyzer until they have been created in the QPR ProcessAnalyzer UI. When the underlying table in the Snowflake is deleted

Timespans. Min: Lowest/first value in the data. Can be used for data that can be sorted. Max: Highest/last value in the data. Can be used for data that

that user. In QPR ProcessAnalyzer, scripts can be run in the server side mode which will make SAP connection in the server machine, or using QPR ScriptLaucher

manage all kinds data in QPR ProcessAnalyzer expression engine that run in-memory. As DataFrame is an in-memory object, processing large dataset using DataFrames

contains both the events and case attributes data. See how to import CSV, PACM and XES files to QPR ProcessAnalyzer. SAP Order-to-cash: Event Data and Case

prerequisites need to be fulfilled to run the eventlog prediction: QPR ProcessAnalyzer 2024.2 or later in use Snowflake connection is configured Source

cached eventLog with the same key already exists in the system, that eventlog is used instead of creating a new. Visibility of cases is limited in a way

file log contains information about all operations performed by the QPR ProcessAnalyzer server in a detailed level. The server file log is stored in the