Search results

been loaded into the memory. If Case permissions are used for the model, and user doesn't have GenericWrite permission for the model, null is returned for

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

any other purpose than running QPR ScriptLauncher. Permissions need to be configured for the folder containing the QPR ScriptLauncher application files

imported using QPR ProcessAnalyzer but using Snowflake's own tools, the CREATE STAGE and CREATE FILE FORMAT permissions are not required. When QPR ProcessAnalyzer

easiest to run QPR ProcessAnalyzer with a database user assigned the db_owner permissions, it's more safe to restrict the database permissions only to needed

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

token (session id). globalPermissions: Global permissions of the user as comma separated list. serverVersion: Version of the QPR ProcessAnalyzer server.

incorrectly require the write permissions. Workaround is to give users the Designer role which will give the needed permissions. Note that the Designer role

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

data in QPR ProcessAnalyzer persistently. Datatables can contain one-to-many named columns and zero-to-many rows. Datatables are stored to 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:

requires at least project Designer or project Administrator permissions (GenericWrite permission). Notification rules can be double-clicked or select a row