Search results

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

variation might contain events that are not in the design model, or the sequence of events doesn't correspond to the defined sequence in the design model. The

architecture for QPR ProcessAnalyzer with its main components. QPR ProcessAnalyzer consists of the following components: QPR ProcessAnalyzer Web UI: Web UI

steps assume that the QPR ProcessAnalyzer is set up to the IIS Default Web Site. Download QPR ProcessAnalyzer Server package available in the downloads page

rows in the eventlog data. In practice, if the model uses a datatable for events, the order of rows in the datatable determines the order of events. Thus

belongs to a specific variation. Event describes that something happened in a specific time. In QPR ProcessAnalyzer, event represent a specific timestamp and

found in QPR ProcessAnalyzer Expression Analysis. Expression Designer is used to run expressions in a generic context. Write the expressions in the upper

D-13491: QPR ProcessAnalyzer server crashed now and then when sorting was in progress and the query was cancelled. D-13380: Dimensioning integers in in-memory

There are following types of objects managed in the QPR ProcessAnalyzer server memory: If the QPR ProcessAnalyzer server doesn't have enough memory to store

computer where QPR ProcessAnalyzer server is running. UsedProcessMemory (Integer) Current memory consumption by the QPR ProcessAnalyzer Server in bytes.

Download QPR ProcessAnalyzer Welcome to QPR ProcessAnalyzer Wiki! QPR ProcessAnalyzer is a software for turning event and transactional data into visual

Models[0].EventLog; Let("el", Models[0].EventLog); el.Cases el.Cases.Events el.Cases:Events el.Cases:Events.Type.Name el.Cases.StringJoin("->", Events.Type

position in a way that the entire diagram fits to the visible screen. Also shows the current zoom percentage of the diagram. Zoom in: Zooms in the diagram

page describes how user sessions are managed in QPR ProcessAnalyzer. All requests to QPR ProcessAnalyzer are performed by a user account. Users needs to

are written in SQL and consist of standard SQL commands, QPR ProcessAnalyzer commands and special parameters related to QPR ProcessAnalyzer. Scripts are

JSON by converting JSON strings into objects and objects into JSON strings. In the expression language, the object created from JSON strings, are dictionaries

contains script examples written in the QPR ProcessAnalyzer expression language. See how expression scripts can be created in the Workspace. For documentation

TimeStamp > at)) ) .Unit ); Let(\"CurrentTime\", GetAt( 0, _ ), Flatten( EventLog .ActiveEventUnitsAt( CurrentTime ) ) ) " } ] }

texts in the UI are translated, but there are the following exceptions: Process mining data imported to QPR ProcessAnalyzer (e.g. case and event attribute

the ${...} syntax: Process is blocked for total of ${Count(EventLog.Cases)} orders Notifications can be processed and sent either in the Email notifications