Search results

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

QPR ProcessAnalyzer API can be used to build integrations with other applications and automate operations in the process mining system. QPR ProcessAnalyzer

automatically to QPR ProcessAnalyzer, and also the QPR UI dashboard export files are not compatible with the new QPR ProcessAnalyzer UI. Features for QPR ProcessAnalyzer:

Use this option when the data is fully managed in QPR ProcessAnalyzer UI (not in the Snowflake UI). The table name has the following format: qprpa_dt

the security of QPR ProcessAnalyzer Server installation. In addition to the server hardening, there are also hardening instructions for QPR ScriptLauncher

data in QPR ProcessAnalyzer persistently. Datatables can contain one-to-many named columns and zero-to-many rows. Datatables are stored to QPR ProcessAnalyzer

QPR ProcessAnalyzer database has a configuration table PA_Configuration containing settings listed in the tables below. You need SQL Server Management

in the UI, the script must not contain commands where ExecuteInClientSide is enabled, because that is only supported when running scripts using QPR ScriptLauncher

opening QPR ProcessAnalyzer. For each variable add "&<variable name>=<variable value>" in the end of the URL. For example: https://SERVERNAME/ui/#/dashboard

QPR ProcessAnalyzer writes a permanently stored log of all operations it's performing. The logs can be used for monitoring, auditing, troubleshooting and

onqpr.com/QPRPA/ui/, the QPR ProcessAnalyzer web application is loaded before going to the identity provider. When a user logs in to QPR ProcessAnalyzer

empty array, if there are no business calendars stored to the model. Note: UI allows to set only one business calendar for a Model. CaseAttributes (AttributeType*)

properties to be set that define which kind of UI control is used. The following parameters can be used: control: UI control type which is one of the following:

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

QPR ScriptLauncher is a tool to run QPR ProcessAnalyzer scripts, and enable connections to datasources from the local network where ScriptLauncher is running

the link is interpreted as a relative link which is added to the end of the QPR ProcessAnalyzer address to form the complete link. Examples: https://google

loaded 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

HTTP status code 302 (Found) with a location (in HTTP response header) to QPR ProcessAnalyzer containing the samlhash parameter in the the location (that

settings in stringified JSON format. Contains the following settings: uiLanguage: UI language of the user. dateFormat: The date time format used to present

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

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

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

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

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

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