Search results

mouse clicks, key presses, UI elements focuses, button clicks, element selections and text input. QPR TaskRecorder collects the UI events to a CSV file, which

components to the QPR ProcessAnalyzer Server computer. Here are the required IIS configurations for QPR ProcessAnalyzer Server. QPR ProcessAnalyzer requires

to another expression and copied to the correct expression. QPR ProcessAnalyzer Server and QPR ScriptLauncher are now using .Net 8 (previous was .Net 6)

Workspace Elements API (a.k.a. UI elements API) is used by the Workspace to move multiple items of different types to other project delete items (multiple

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

the UI. Defined as true or false. More information about the 12-hour clock: https://en.wikipedia.org/wiki/12-hour_clock. serverVersion (string): QPR ProcessAnalyzer

scheduled using a script (alternatively users can initiate the sending in the UI). When notifications are processed and sent, the following logic is applied

Filtering_in_QPR_ProcessAnalyzer|Using Filters QPR TaskRecorder|QPR TaskRecorder Installation QPR_ProcessAnalyzer_System_Architecture|System Architecture QPR_Pr

Process Mining. Most common ways of creating models in QPR ProcessAnalyzer are using the webUI to import data and more advanced techniques such as SQL

} html, body, .mw-body h1, .mw-body h2, input { font-family: Segoe UI,SegoeUI,Segoe WP,Helvetica Neue,Helvetica,Tahoma,Arial,sans-serif; } .mw-body-content