QPR ProcessAnalyzer Wiki - User contributions [en]

PA Configuration database table

2022-08-10T11:41:55Z

QPRAdmin: added Application=QPR_ProcessAnalyzer; to snowflake connection string example

QPR ProcessAnalyzer database has a configuration table '''PA_Configuration''' containing settings listed in the tables below. You need '''SQL Server Management Studio''' to edit the settings in the configuration table. QPR ProcessAnalyzer Server needs to be restarted (e.g. IIS application pool recycled) for the changes to take effect.

== General Settings ==
{| class="wikitable" style="text-align: left"
!Name !!Default value !!Description
|-
||SessionIdleTimeout
||3600
||Idle user session expiration timeout in seconds. User session expires if the session hasn't been used after this amount of time.
|-
||SessionMaximumDuration
||86400
||Maximum duration for a user session in seconds. Even if a session is used so that the SessionIdleTimeout is not reached, the session is expired after this amount of time.
|-
||SandboxDatabaseConnectionString
||
||Connection string to scripting sandbox database (ETL). If not defined, ETL scripts cannot be run. Connection string for the scripting sandbox database is similar to the [[Web.config_file#Connection_Strings_Section|QPR ProcessAnalyzer database connection string]].
|-
||DefaultUiLanguage
||en_US
||Language code for the UI language that new user accounts get by default. Thus, a created user account has this language until the user changes her/his language. Also the login page is translated using this language when QPR ProcessAnalyzer is used for the first time in that web browser (when user has changed the language, it's remembered by the browser). This setting must be one of the supported language codes (xx_XX):
* Finnish: '''fi_FI'''
* French: '''fr_FR'''
* English: '''en_US'''
* German: '''de_DE'''
* Spanish: '''es_ES'''
* Swedish: '''sv_SE'''
* Polish: '''pl_PL'''
|-
||DefaultDateFormat
||MM/dd/yyyy
||Default date format that new user accounts get by default. The date format does not contain the time part (e.g. hours, minutes and seconds). Defined using the .Net date format (https://docs.microsoft.com/en-us/dotnet/standard/base-types/custom-date-and-time-format-strings).
|-
||DefaultFirstDayOfWeek
||0
||Default first day of the week that new user accounts get by default. '''0''' is Sunday and '''1''' is Monday. This information is used by the UI when showing e.g. calendars.
|-
||DefaultUse12HourClock
||false
||Defines whether the 12-hour clock is used by default (instead of the 24-hour clock) for the new user accounts when showing time information in the UI. Defined as '''true''' or '''false'''. More information about the 12-hour clock: https://en.wikipedia.org/wiki/12-hour_clock.
|-
||SqlServerConnectionString
||
||ADO.Net connection string for the SQL Server database containing the datatables data. It's recommended to use separate database, but it's also possible to connect to the same database as the [[Web.config_file#Database_Connection_String|metadata database]]. When this setting has been configured, new datatables are created to this database instead of the metadata database. The old datatables are still located in the metadata database, and new datatables cannot be created to the metadata database anymore. Note that the connection uses ADO.Net (not ODBC), so the connection string is similar to the metadata database connection string in the [[Web.config_file#Database_Connection_String|web.config]] file.
|-
||SnowflakeConnectionString
||
||ODBC connection string for the Snowflake connection, that needs to be configured to process models in the Snowflake. The connection string has following format:
<pre>
Driver={SnowflakeDSIIDriver};Application=QPR_ProcessAnalyzer;Server=<account_identifier>.snowflakecomputing.com;Database=QPRPA;Schema=QPRPA;Warehouse=QPRPA;Role=QPRPA;uid=QPRPA;pwd=<password>
</pre>
where <password> is the Snowflake user password and <account_identifier> is the Snowflake account identifier. In the example, the database, schema, warehouse, role and user are named to QPRPA. In addition to this setting, the Snowflake ODBC driver needs to be installed in the machine running the QPR ProcessAnalyzer Server. When this setting has been configured, users can create Snowflake stored datatables and models using Snowflake calculation. More information about [[Snowflake_Connection_Configuration|Snowflake connection configuration]].
|-
||NumberOfParallelModelReaders
||4
||Models and datatable contents can be loaded with multiple simultaneous connections to the database to speed up the loading. This setting determines how many parallel loaders/readers at maximum (loaders are loading at the same time). For smaller models there are less parallel loaders than the defined limit: If there are less than 100000 rows in the table, there is only one loader. If there are less than 200000 rows in the table, there are only two loaders, and so on.

The more there are parallel loaders, the more processor load and network bandwidth is consumed, and other operations in QPR ProcessAnalyzer might slow down. Note also that the performance optimum is achieved with a certain number of parallel loaders which differs between environment. Thus to achieve the best performance, data loading should be tested with different number of parallel loaders. Increasing number of parallel loaders beyond the optimum decreases the performance.

|-
||StartupModelLoadingMaxParallelism
||2
||Maximum number of QPR ProcessAnalyzer models that are loaded into memory simultaneously by the [[Automatic_Model_Loading_on_Server_Startup|Automatic Loading on Server Startup]]. If there are more models to be loaded on the server startup than this setting, loading for the rest of the models is started one by one when previous model loadings are completed. If this setting is not defined, '''2''' is used as a default value.

Loading more models at the same time will speed up the whole model loading process, but on the other hand, it causes more load on the system, which affects the system responsiveness for users. Model loading consists of (1) transferring data from the datasource to QPR ProcessAnalyzer and (2) loaded data preprocessing into a model. The former uses mainly network bandwidth (if datasource is in a different server) and the latter uses mainly processor capacity in the QPR ProcessAnalyzer server.

This setting affects only the model loading during the server startup and it doesn't restrict models loadings initiated by users.
|-
||AllowExternalDatasources
||True
||Determines whether the [[Generic_Functions_in_QPR_ProcessAnalyzer#Other_functions|ImportOdbc]] and ReadWebService functions in the expression language and the [[QPR_ProcessAnalyzer_Model_Datasources#Loading_Data_from_ODBC_Datasource|ODBC model datasource]] can be used. This setting is for disabling external interfaces for security reasons. By default, external interfaces are allowed.
|-
||AllowNonTemporaryETLTargetTable
||False
||Defined whether ETL scripts are allowed to create global temporary database tables (tables starting with ##). More information about temporary tables: https://docs.microsoft.com/en-us/sql/t-sql/statements/create-table-transact-sql?view=sql-server-ver15#temporary-tables.
|-
||DatabaseBulkCopyTimeout
||600
||BulkCopyTimeout given for QPR ProcessAnalyzer database SqlBulkCopy operations.
|-
||DatabaseBulkCopyBatchSize
||5000
||BulkCopyBatchSize given for QPR ProcessAnalyzer database SqlBulkCopy operations.
|-
|SandboxDatabaseBulkCopyTimeout
||600
||BulkCopyTimeout given for sandbox SqlBulkCopy operations.
|-
||SandboxDatabaseBulkCopyBatchSize
||5000
||BulkCopyBatchSize given for sandbox SqlBulkCopy operations.
|}

== SAML 2.0 Federated Authentication Settings ==
Note that the SAMLMetadataUrl and ServiceProviderLocation are mandatory for the federated authentication to work.

{| class="wikitable" style="text-align: left"
!Name !!Description
|-
||SAMLMetadataUrl
||
Metadata URL of the identity provider (IdP). Check that the metadata url can actually be opened using a web browser and is publicly available. The metadata is an XML document starting with '''<?xml version="1.0" encoding="UTF-8"?>''' followed by an '''EntityDescriptor''' tag. The metadata URL might look '''<nowiki>https://your.federated.identity.provider.com/saml/metadata</nowiki>'''. This setting is mandatory for the SAML authentication to work.
|-
||ServiceProviderLocation
||
Specifies the QPR ProcessAnalyzer server location (the root path which contains e.g. the ''ui'' folder). It's used by the url to redirect back to QPR ProcessAnalyzer after a successful authentication from the identity provider. The setting is defined in the following form: '''https://<hostname>/qprpa''', for example '''<nowiki>https://customer.onqpr.com/qprpa</nowiki>'''. Note that the actual redirect back url is '''https://<hostname>/qprpa/api/saml2/acs''' (/api/saml2/acs is automatically included to the url). This setting is mandatory for the SAML authentication to work. Note that if this reply url is configured the identity provider, it must match with the ServiceProviderLocation setting.
|-
||SAMLUserIdAttribute
||
Name of the SAML attribute in the assertion that will be used as the user's login name. If this field is not defined, the '''saml:Assertion''' > '''saml:Subject''' > '''saml:NameID''' attribute in the assertion is used. If this setting is given, one of the '''saml:Assertion''' > '''saml:AttributeStatement''' > '''saml:Attribute''' elements in the assertion is used (the '''Name''' attribute in the '''saml:Attribute''' element is used for matching). Please note that the saml:NameID element is different than the usual SAML attributes that are defined by the saml:Attribute elements. For example, if an email address is used as a user id, the value of the setting could be for example ''<nowiki>http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress</nowiki>''.
|-
||SAMLEncryptionCertificate
||This setting defines a PEM formatted X.509 certificate (defined in RCF 1422) used to encrypt SAML assertions. The public key of the certificate is published in the service provider metadata, where the identity provider can read it and encrypt SAML assertions. QPR ProcessAnalyzer as the service provider uses the corresponding private key of the certificate to decrypt SAML assertions. The setting needs to be a PEM formatted certificate file that is base64 encoded and it doesn't contain the BEGIN CERTIFICATE etc. header or footer lines. This setting is needed only when using the SAML assertions encryption. Even though this setting is defined, the SAML assertions are not required to be encrypted. More information how to create the certificate file (https://stackoverflow.com/questions/16480846/x-509-private-public-key) and convert it to base64 (https://stackoverflow.com/questions/46959822/base-64-encoded-form-of-the-pfx-file).
|-
||SAMLSigningCertificate
||This setting defines a PEM formatted X.509 certificate (defined in RCF 1422) used to sign SAML authentication requests sent from QPR ProcessAnalyzer to the identity provider. The public key of the certificate is published in the service provider metadata, where the identity provider can read it, to verify the authenticity of the SAML requests. The setting needs to be a PEM formatted certificate file that is base64 encoded and it doesn't contain the BEGIN CERTIFICATE etc. header or footer lines. If this setting is not defined, the internal hard-coded signing certificate is used. More information how to create the certificate file (https://stackoverflow.com/questions/16480846/x-509-private-public-key) and convert it to base64 (https://stackoverflow.com/questions/46959822/base-64-encoded-form-of-the-pfx-file).
|}

== SMTP Server Settings ==
SMTP server settings are neede for QPR ProcessAnalyzer to be able to send email messages. Email sending is used by the notifications functionality and the SendEmail function in the expression language.

{| class="wikitable" style="text-align: left"
!Name !!Description
|-
||SmtpServer
||DNS name, host name or IP address of the SMTP server. Mandatory setting for the email sending to work.
|-
||SmtpPort
||TCP port number of the SMTP server. If not defined, port '''25''' is used by default.
|-
||SmtpAuthenticationUsername
||User name for authenticating to the SMTP server. If not defined, no authentication is used to connect to the SMTP server.
|-
||SmtpFromAddress
||Email address where email messages sent by QPR ProcessAnalyzer appear to be coming from. This doesn't need to be a real email address, although the address used may affect email spam filters. The setting configured here is the default email address to use in following cases:
* ''From address'' is not set for the email notifications
* ''From'' parameter is not defined for the expression language ''SendEmail'' function
* ''EmailFrom'' parameter is not defined for the SQL Scripting SendEmail operation
|-
||SmtpAuthenticationPassword
||Password for authenticating to the SMTP server.
|-
||SmtpEnableSSL
||'''True''' or '''False''' depending whether SSL connection to the SMTP server is used or not. If not defined, ''False'' is the default value.
|}

== Readonly Information ==

{| class="wikitable" style="text-align: left"
!Name !!Description
|-
|DatabaseId
||Unique identifier for the QPR ProcessAnalyzer database, which is generated when the database is initialized during the server installation. If this setting is empty, a new unique database id is generated for this setting, and that value is used after that.
|-
|DatabaseVersion
||Database schema version. It will be updated automatically when the newer version of QPR ProcessAnalyzer Server connects to the database and performs migration for the database schema.
|-
||InitializationScriptDatabaseVersion
||Database version that was when the database was initialized when the software was installed. Do not change this setting.
|-
||MinimumDatabaseVersion
||Minimum allowed database version for QPR ProcessAnalyzer Server connecting to the database. This is a legacy setting and it should not be used.
|}

MediaWiki:Common.css

2022-01-28T09:13:00Z

QPRAdmin:

/* CSS placed here will be applied to all skins */

#footer-places, #pt-mytalk, #footer-icons, #p-namespaces, #footer-info-lastmod, #footer-info {
display: none;
}

.mw-body {
margin-left: 13.4em;
}

.mw-wiki-logo {
background-image: url(/pawiki/images/a/af/QPR_ProcessAnalyzer.png);
background-size: 160px;
margin-top: -150px; margin-left: 15px;
}

#p-logo a {
background-position: 0px 75px;
}

div#mw-panel {
width: 12.5em;
padding-top: 0px;
padding-left: 0.5em !important;
top: 105px;
}

#p-logo {
left: 1.5em !important;
}

div#mw-panel div.portal div.body ul li {
font-size: 0.9em;
padding: 0.2em 0;
}

div#mw-panel div.portal h3 {
font-size: 0.9em;
font-weight: 600;
padding: 0.25em 0 0.1em 0.25em;
}

a, a:visited, div#mw-panel div.portal div.body ul li a, div#mw-panel div.portal div.body ul li a:visited {
color: #0f2975;
}

h1, h2, h3, h4, h5, h6 {
color: #3d3d3d;
font-weight: 600;
}

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 {
font-size: 14.5px;
}

.mw-body h1 {
font-size: 35px;
}

.mw-body h2 {
font-size: 25px;
}

.mw-body h3 {
font-size: 19px;
}

pre {
font-family: Consolas,Menlo,Monaco,Lucida Console,Liberation Mono,DejaVu Sans Mono,Bitstream Vera Sans Mono,Courier New,monospace,sans-serif!important;
font-size: 14px;
line-height: 20px;
background-color: rgb(250, 250, 250);
tab-size: 3;
}

div#mw-panel div.portal h3 {
font-size: 1em;
}

div.vectorMenu h3 span {
padding-top: 1.25em;
}

.searchresult {
font-size: inherit;
max-width: inherit;
}

div#simpleSearch #searchInput {
padding: 0em 0 0em 0.3em;
font-size: 15px;
}

#wpTextbox1 {
font-size: 14px;
}

#toc {
font-size: 15px;
background-color: inherit;
}

.catlinks {
background-color: inherit;
}

table.wikitable {
background-color: white;
}

table.wikitable > tr > th, table.wikitable > * > tr > th {
background-color: #f8f8f8;
}

.image > img {
max-width: 100%;
height: auto;
}

/*These are for the product download page buttons.*/
.downloadButton {
width: 260px;
height: 91px;
display: inline-flex;
margin: 15px 10px 0px 15px;
border-radius: 5px;
background-color: #069cf0;
font-size: 19px;
vertical-align: top;
line-height: 1.5;
padding-bottom: 3px;
}
.downloadButton > .text, .downloadButton > a {
color: white !important;
background-image: none;
margin: auto;
text-align: center;
padding-right: 0px !important;
}

QPR ProcessAnalyzer Chart

2021-03-29T08:06:53Z

QPRAdmin:

Chart allows creation of versatile and visually appealing charts with flexible KPI definitions to answer specific business needs. Chart allows to calculate KPI's from all process mining objects, such as cases, events, event types or flows. The data can be to be sliced into configurable dimensions and KPIs calculated for each dimension. It's also possible to disable slicing to show a simple list of all analyzed items.

== Introduction ==
Chart is available as the first item in the tool palette which can be seen when editing is started.
In a basic form, the result of this analysis is a table with the following columns: (1) One column for each specified dimension, and (2) at least one column for each specified value. The result of this analysis is a table with one row for each unique dimension value combination.

The basic flow of using the chart is the following:
# Choose objects to visualize, e.g. cases, events, event types or variations.
# Choose how to slice (or dimension) the data into parts, e.g. by attributes (regions, products), by durations or by dates (months, quarters).
# Choose measures/KPI's to be calculated for each dimension. Measure could be e.g. number of items, average duration, or cost.
# Choose the best visualization for the data, such as column charts, donut charts or tables.

Chart also has a fullscreen mode which expands one chart to the whole screen. The fullscreen is available in the icon on top right corner of each chart. The fullscreen can be disabled, by clicking the cross icon in the top right. When in the fullscreen, filtering can be done and on-screen settings are disabled.

Chart is available in the navigation menu where there are ready-made views containing chart, such as ''Advanced Process Discovery'' and ''Chart''. The ready-made views are for ad-hoc analysis, and the settings cannot be saved, but they are preserved during the user session. Chart is also available as a component when creating dashboards, where chart settings are saved as part of the dashboard, and thus all users see the dashboard as it was designed.

== Analyzed Data Selection ==
When creating a chart, the first thing to decide, are which items to be analyze.

Settings that determine which data is
* '''Analyze''': Choose the process mining objects to analyze, e.g. cases, events, variations, event types or flows. Analyzed items can also be limited by a certain criteria. For cases, it's recommended to use chart filter if a subset of cases is needed.
* '''Slice into Dimensions''': When checked, data is sliced in to the defined dimensions, and the row count depends on how many unique dimension values there appear in the data. When dimensioning is in use, a single row represents one or several analyzed items. When unchecked, data is not sliced into different dimensions, but each analyzed item is as a separate row in the data. There are thus as many rows as there are analyzed items.
* '''Sorting''': Data can be ordered based on data chosen to the measures/dimensions/columns. Both ascending and descending ordering is available. Sorting can also be disabled if it doesn't have any use, as sorting affects performance when there is large number of rows. Note that for charts having numerical or date X-axis, sorting doesn't have any visible effect, because position of data points in the chart (columns etc.) depend on measure/dimension data values instead of order of rows. When ''custom'' is selected, a custom sorting can be defined when clicking the ''Advanced sorting'' button as an object array with the follow properties for each object:
** '''type''': either '''measure''' or '''dimension'''
** '''index''': measure or dimension order number (starts from 0)
** '''direction''': Either '''ascending''' or '''descending'''

Example:
[[File:Advancedsortingexample.png|center|700px]]

<pre>
[
{
"type": "measure",
"index": 1,
"direction": "descending"
},
{
"type": "dimension",
"index": 0,
"direction": "ascending"
}
]
</pre>
* '''Maximum Rows''': Number of rows returned are limited to this maximum count. This setting is useful with sorting to show only the most relevant items. In addition, in certain selections there may be a large number of rows, so the maximum should always be limited.

== Visualization Settings ==
[[File:Chartsettingsgeneral.png|right]]
* '''Visualization''': Choose how data is visualized. There are variety of charts available, and also a table, a pivot chart, and a KPI card (see more in [[#Available_Visualizations|next chapter]]. It depends on the visualization, which mappings can be selected for measures/dimensions/columns.
* '''Stacking''': In charts, stacking is used to show series on top of each other, which better visualizes the sum of the measures across different series.
* '''% Stacking''': In charts, percentage stacking shows the measures as percentages of the sum of the measures. The total is thus always 100%.
* '''Polar Chart''': In charts, shows the X-axis as a circular instead of a horizontal line. The polar chart works with many chart types, such as column, line and area charts.
* '''Show Data Labels''': When checked, numerical measure values are shown next to the data point in charts.
* '''Group Rows Exceeding Maximum''': When checked and when number of rows is limited by the ''Maximum Rows'' setting, the extra rows are aggregated into the last row.
* '''Title''': Custom title for a chart or table can be defined that replaces the automatically created title. When this field is empty, an automatically created title is used in charts. Note that the table does not have an automatically created title. To hide the title, a space character can be defined.
* '''Subtitle''': Custom subtitle for a chart that replaces the automatically created subtitle. When this field is empty, an automatically created subtitle is used showing the chart filter (if defined). To hide the subtitle, a space character can be defined.
* '''[[#On-screen Settings|On-screen Settings]]'''
* '''Custom Layout''': Using the Custom Layout, advanced settings for the chart and table can be accessed using the JSON format. Settings defined here override the default chart and table settings. Overriding is done for individual properties, so only the customized settings need to be mentioned. See examples for [[QPR ProcessAnalyzer Graphs#Customization%20Examples|customizing charts]].

== Available Visualizations ==
Chart provides variety of visualization. Here are mentioned some of those:
* '''[[QPR ProcessAnalyzer Table|Table]]''': The table shows the data in a similar form that it is returned from the server, and thus the table is useful when defining dimensions and measures. In the table, dimensions are first starting from the left and then there are measures. Filters can be created from the table by clicking dimensions/columns (it's not possible to create filter by clicking measures). Also when creating a column filter to the table (which only filters the data in the table), a process mining filter is automatically suggested which can be accepted or ignored. Columns widths can also be changed, and tables are able to remember the adjusted widths.
* '''[[QPR ProcessAnalyzer Pivot Table|Pivot Table]]''': In the pivot table, the first dimension is visualized as rows and the second dimensions is visualized as columns. Measures are as cell values of the pivot table. In addition to the usual table, the pivot table provides changing number of columns depending how many unique values there are in the second dimension.
* '''[[QPR ProcessAnalyzer KPI Card|KPI Card]]''': The KPI card shows a single KPI value calculated from the whole data, and optionally a color rectangle next to the value to visualize the KPI performance.
* '''[[QPR ProcessAnalyzer Graphs|Graph]]''': These chart types use ''low'' and ''high'' mappings.
* '''Root Causes''': Special visualization for the Root Causes analysis. When using this visualization, also the analyzed objects need to be ''Root causes''.

== Measures, Dimensions and Columns ==
[[File:Chartsettingsmeasures.png|right]]When dimensioning is used (''Slice into Dimensions'' setting checked), '''measures''' and '''dimensions''' can be chosen (in the respective tabs), and when dimensioning is not used, '''columns''' can be chosen (in the respective tab).

When dimensioning is used, there can be zero to many dimensions defined. Available dimensions depend on which objects are selected for the analysis (in the ''Analyze''' dropdown list). The calculation returns as many rows as there are unique combinations for each dimensions values. For example, if you dimension by two dimensions, the other containing 3 unique values, and the other 5 unique values, there can be maximum of 3x5=15 rows in the resulting data. Note that all combinations might not appear in the data and thus the number of rows might be less.

When the data is sliced into different dimensions, measures are calculated for each dimension. There can be zero to many measures defined. Measures are typically numerical information as most charts visualize only number, but tables can be used to present any kind of data.

When dimensioning is not used, one to many columns can be chosen. Columns are simple properties or attributes of the listed objects. If showing data in a table, there is one row for each of the analyzed objects.

Each measure, dimension and column contain the following buttons when hovering:
* '''Measure/dimension/column settings''': Opens a dialog for the detailed settings that affect only to this measure/dimension/column (see the next chapter).
* '''Convert to custom expression''': Converts the measure/dimension/column to a custom expression for advanced editing. Note that it's not possible to go back, so if need to do that, remove the custom measure/dimension/column and create a new. Tip: When writing custom expressions, it's useful to start with a ready-made measure/dimension/column to get an expression to further edit.
* '''Move down''': Moves this measure/dimension/column one step down and moves the one previously below, one step up (they are switching places).
* '''Move up''': Moves the measure/dimension/column one step up and moves the one previously above, one step down (they are switching places).
* '''Add measure/dimension/column''': Moves this measures/dimensions/columns and all below it one step down to make space for a new one.
* '''Delete measure/dimension/column''': Deletes this measure/dimension/column and moves all others below one step up.

== Measure, Dimension and Column Settings ==
[[File:Chartsettingsmeasuresettings.png|right]]When hovering a measure/dimension/column settings, the first of the appearing icons opens a dialog for the measure/dimension/column detailed settings. The following settings are common for measures/dimensions/columns:
* '''Custom label''': By default, measures/dimensions/columns have automatically created descriptive labels that are shown, e.g. as chart axis titles or table column names (depending on the visualization). Use this custom label to define your own label which replaces the automatic label.
* '''Visualization''': In charts, series specific visualization for this measures/dimensions/columns. Overrides the default visualization defined in the ''General'' tab.
* '''Visualization color''': In charts, color for visualizing this measure/dimension/column, appearing for example as a column or line color.
* '''Round to decimals''': Numeric values are rounded to this defined number of decimals. Note that despite the rounding, values are sorted based on the accurate values.
* '''Unit''': Unit that is visible after each measure/dimension/column value. In most cases, the units are determined automatically, e.g. for duration type of data.
* '''Data type''': Expected data type for the measure/dimension/column. The defined data type must match with the actual datatype of the calculated data to work correctly. As an exception, the ''text'' type can be used with any type of data, because all types of data can be converted into strings. Data types are very important for the visualization to work, e.g. charts require numerical data to be numbers. Data type list also contains ''Auto detect'' which analyzes the calculated data and chooses the datatype based on the most common datatype in the data. Note that the auto detect doesn't give the correct data type when there is no data available.
* '''Mapping in chart''': When using the chart, defines how this measure/dimension/column is mapped in the chart, for example to Y-axis, X-axis, series etc.
* '''Date format''': Date type of data is presented with this date format.
* '''Web link''': When defined (works in tables only), the measure/dimension/column will be a clickable web link opening the target web site to a new tab. Only the text in the table cell is clickable, so filtering is possible when clicking next to the text. To refer to the data in the same row, web links can contain tags (e.g. '''${dimension:1}'''), which are replaced with the data. You can also refer to the clicked value with '''${this}'''. If the web link only consists of a single tag, the tag value is not encoded (because the tag is assumed to contain a full url). If the web link contains static text in addition to the tags, the tag values are encoded using encodeUriComponent (because tags are assumed to be used as url parameters). If the link does not start with http:// or https://, the link is interpreted as a relative link, and it's added to the end of the QPR ProcessAnalyzer url. Examples: ''<nowiki>https://google.com/search/q=${measure:2}</nowiki>'', ''<nowiki>https://devnet.onqpr.com/pawiki/index.php?search=${this}</nowiki>''
* '''Adjustment expression''': Expression that is added to the end of the measure/dimension/column expression. The adjustment expression can be used for example to convert or map values.
* '''Statistical calculations''': Different kind of calculations done to measure/dimension/column data. Several items from the list can be used at the same time. Some calculations require an additional parameter, that is specified in the ''Reference value for statistical calculations'' field. Available calculations are:
** '''Remove nulls''': Removes rows where the measure/dimension/column has a null value.
** '''Remove empty strings''': Removes rows where the measure/dimension/column has an empty string value.
** '''Remove outliers using normal distribution''': Removes rows where the measure/dimension/column has a value that is outside the [average] +/- X * [standard deviation]. The X is defined as an additional parameter.
** '''Remove insignificant values from start and end''': Removes rows from the beginning and end of the dataset the measure/dimension/column value is below the defined percentage of the maximum value in the dataset. This setting can be used to remove e.g. indiscernible items in a column chart.
** '''Remove values lower than''': Removes rows where the measure/dimension/column value is lower than the defined limit. Requires numerical column.
** '''Remove values greater than''': Removes rows where the measure/dimension/column value is greater than the defined limit. Requires numerical column.
** '''Remove dates older than (days)''': Removes rows where the measure/dimension/column value is earlier than the defined number of days. Requires a date type of column.
** '''Remove dates older than (months)''': Removes rows where the measure/dimension/column value is earlier than the defined number of months. Requires a date type of column.
** '''Remove dates that are in future''': Removes rows where the measure/dimension/column value is in future when comparing to the current time.
** '''Remove repeating values''': Removes rows where the measure/dimension/column value occurs the second or more time. i.e. only the first occurrence is preserved. Note that the order of data is relevant.
** '''Remove values repeating more than''': Removes rows where the measure/dimension/column value occurs more than the defined times. Note that the order of data is relevant.
** '''Fill gaps in dimensioning''': Rows rows to the data to fill "missing" values. When the data is numerical, all the missing integer values between the minimum and maximum values are created. When the data is dates, all months start timestamps are created between the minimum and maximum.
** '''Show cumulative values''': Calculates sum of values for the measure/dimension/column from the beginning until that data point.
** '''Show change from previous''': Calculates difference to the previous value. The first value shows zero.
** '''Show percentual change from previous''': Calculates a percentual change to the previous value. The shown unit changes to percentage. The first value shows zero.
** '''Smooth using moving average''': Calculates all measure/dimension/column values as an average of the nearest values. The additional parameter is the number of steps to go back and forth to take into account.
** '''Calculate moving sum''': Calculates sum for each measure/dimension/column values. Goes back number of steps defined by the additional parameter.
** '''Add by''': Adds the specified number to all the measure/dimension/column values.
** '''Multiply by''': Multiplies all measure/dimension/column values by the specified number.
** '''Divide by''': Divides all measure/dimension/column values by the specified number.
** '''Sort by this column''': Sorts the data ascending by this measure/dimension/column.
** (not available in UI) '''replaceNullValues''', '''replaceEmptyStrings''', '''replaceTrueValues''', '''replaceFalseValues''': Replaces the respective data value (null, empty string (string), true value (boolean), false value(boolean) ) with any other value defined using the ''referenceValue'' parameter.
* '''Reference value for statistical calculations''': The reference numerical value that is used in some of the statistical calculations.
* '''[[QPR_ProcessAnalyzer_Table#Conditional_Formatting|Table conditional formatting]]''': Background color or text color based on data.
* '''Custom aggregation expression''': Define a custom aggregation expression to be used instead of the default aggregation expression. The aggregation expression calculates an aggregate value for the excluded rows that exceed the maximum value when ''Group Rows Exceeding Maximum'' is in use.
* '''Color mappings''': Maps measure/dimension/column values to colors, so that selected values are always visualized with selected colors. Other values will get colors based on the chart's color palette. Color mappings defined to a measure/dimension/column that is mapped to X-axis or to series, takes effects in charts. There is no UI for this setting, so it needs to be defined directly to the dimension definition in the chart settings. Example:
<pre>
"colorMappings": {
"Robert Miller": "#36d475",
"Patricia White": "#ef5254",
"Mary Wilson": "#b9bdc1"
}
</pre>
* '''Show in datalabels (showInDatalabels)''': Defines whether the measure/dimension/column is shown in a chart data label (true/false). If any measure/dimension/column has showInDatalabels set to true, the default data labels are overridden by this setting to show only the defined ones. There is no UI for this setting, so it needs to be defined directly to the measure/dimension/column definition in the chart settings.
* '''Top items (topItems)''': Shows only the defined number of dimension values which have the largest volumes (e.g. number of cases or events depending on what's analyzed). Data with the remaining values are now shown. If using only one dimension, the ''Maximum rows'' settings provides the same result, but the Maximum rows usually doesn't work in a desired way when there are multiple dimensions - the top items setting is for that purpose. The top items settings is not available for measures. There is no UI for this setting, so it needs to be defined directly to the dimension/column definition in the chart settings.

In addition, measures have the following settings:
* '''Calculate measure for''': Measure can be calculated for ''each dimension separately'' (the default option) which is the normal dimensioning behavior. It's also possible to ignore the dimensioning for this measure and calculate the measure for the ''currently filtered data'' (i.e. the measure is calculated for the entire dataset that the chart is based on). Furthermore, it's also possible to ignore filters and calculate the measure value for the ''entire model data''.
* '''Variable name''': Name of the variable containing this measure value. The variable can be used in expressions for other measures. The variable is created when a name for it has been defined.

== Filtering Settings ==
[[File:Chartsettingsfilter.png|right]]In QPR ProcessAnalyzer, filters can be applied on two levels:
* Entire dashboard: Dashboard filters are applied to all charts in the dashboard and they are visible in the main header. When clicking items in the charts, dashboard filters are created.
* Individual chart: Chart filters are applied only to the chart where the filters are defined for. Filters for a chart can be viewed and edited in the chart settings. Chart filters can be created from the chart settings. Tip: If the desired type of filter cannot be created from the Add filter dialog, create the filter first as a dashboard filter and then drag and drop the filter rule over the chart. The filter rule is moved as a chart filter.

Chart filters and behavior for the chart filtering is defined in the Filter tab having the following settings:
* '''Chart Follows Dashboard Filters''': When checked, the chart is filtered by the filters in the dashboard. When unchecked, the chart is not affected by filters in the dashboard, and thus the chart is based on data in the entire model.
* '''Create Filters from Chart''': When checked, filters can be created based on selected items in the chart. When unchecked, no filters are created when clicking the chart.
* '''Update Filter During Selection''': When checked, other charts are filtered during selecting items in this chart, enabling to preview filtering results in other charts before confirming the selection. When unchecked, a filter is created only when the selection is confirmed, improving smoothness of usage in large models.
* '''On-screen Settings Follow Flow Selection''': When checked, selecting flows (e.g. in the flowchart) changes accordingly the start and end event types that are as on-screen settings. Note that the start and end event types need to be as on-screen settings, for the automatic fill in to work. When unchecked, the automatic fill in is disabled.
* '''Chart Filter''': Button to add filters that affect only this chart. There can be many filter rules defined. Filter rules can be edited by clicking them and removed from the recycle bin icon. The filters work in a way that only data that is matching to all the filter rules are shown.
* '''Chart Comparison''': Rules that are used by the root causes analyses, which are finding root causes for the phenomena pointed by those rules.

Note that in addition to the process mining filters, objects can be filtered in the chart using the expression language. For that there are many ready-made selections. The process mining filters should be used when when the process mining model should be kept in a consistent state, e.g. filtering event types recalculates variations. Certain kind of filtering is not possible through the process mining filters, and then expression based filtering should be used, e.g. filter events based on event attributes or filtering flow objects.

== Visualize KPI Targets with Colors==
When visualizing KPI's, it's essential show how the measure is performing comparing to targets. Targets can be visualized e.g. in charts (see more below) and in the KPI Card ([[QPR_ProcessAnalyzer_KPI_Card#Visualize_KPI_Targets_with_Colors|see how to]]).

Target values can be shown in the charts as follows:
# Select e.g. the ''Column Chart'' as a visualization. (Colors can be visualized also with other chart types.)
# Select your KPI as the first measure.
# For the measure, select ''Variable for other measures'' in the measure settings.
# Select ''Data point colors'' as the second measure, and define the limit values between green-yellow and red-yellow.
# For the Data point colors measure, select ''Mapping in Chart'' is ''Data point color'' in the measure settings.
# When using charts, usually a dimension is selected as well.

Now the KPI targets are visualized as colored columns.

== Advanced Settings ==
[[File:Chartsettingsadvancedsettings.png|right]]
* '''Chart settings (editable)''': All settings in a chart are stored in a single entity that are shown here. The settings can also be edited directly. There are validations in place, so invalid settings are not accepted.
* '''[[#Linked settings|Linked settings]]'''
* '''[[#Variable mappings|Variable mappings]]'''
* '''[[#Benchmark performance|Benchmark performance]]'''
* '''Show in Query Designer''': For testing and development purposes, clicking this button starts editing the current expression in the Expression Designer.
* '''Model''': Allows to select a ProcessAnalyzer model that is used for this chart. When selecting ''<used by dashboard>'', the model that is currently selected for the dashboard in the header, is used for this chart. This setting allows to create dashboards, where the same dashboard fetches data from different models.
* '''Visible Case Attributes''': Only the defined case attributes are shown in settings where case attributes need to be selected from a list. This setting can be used to hide unnecessary case attributes to make lists shorter and easier to use. When no case attributes are defined, all case attributes are shown.
* '''Visible Event Attributes''': Only the defined event attributes are shown in settings where event attributes need to be selected from a list. This setting can be used to hide unnecessary event attributes to make lists shorter and easier to use. When no event attributes are defined, all event attributes are shown.
* '''Visible Event Types''': Only the defined event types are shown in settings where event types need to be selected from a list. This setting can be used to hide unnecessary event types to make lists shorter and easier to use. When no event types are defined, all event types are shown.
* '''Background color''': Chart area background color affecting the Highcharts-based charts, KPI cards, tables (excluding the grey header), and root causes visualization.
* '''Analyzed objects sample size''': Sampling randomly removes some of the items leaving only the sample size of items left to the analyzed objects. If sample size is not defined, sampling is not used. The purpose of sampling is to improve performance, as there will be less items in the dimension and measure calculation. The intention is that the calculation from the sampled dataset would provide close enough results in statistically high enough probability. Sampling cannot be used in some calculations, because it affects the calculation results.
* '''Update Chart When Changing Settings''': When checked, the chart is not updated automatically when changing chart settings, but when clicking the Apply button in the General tab. Disabling automatic updating improves performance in large models when changing several settings at the same time.
* '''Enable Caching''': Enable or disable chart data caching both in the client and server side. Caching improved performance as in the second time, data can be quickly retrieved from the cache. Some reports benefit of disabled caching so that the up-to-date data is always retrieved.
* '''Show Tabs''': Enables or disables tabs above the chart to quickly change charts. Tabs are showing the most common presets. When tabs are shown chart title are not shown (titles are still shown for tables).
* '''Query''': This option shows the entire query that is sent to the server for calculation. The query contains the ''expression'' (the previous option), and in addition other information, such as the model id, filter and comparison.
* '''Root expression''': Shows the root expression in a multi-line format. The root expression is also visible in the ''expression'' but there it's encoded to a single line.
* '''Component settings''': Chart uses Highcharts component to draw charts and Syncfusion component to draw tables. With this options you can see the actual configuration that is used by the visualization component. In this option, the actual data is removed, because in some cases there may be lot of data.
* '''Component settings (with data)''': This is similar option as the previous, except the data is also included.
* '''Chart filter''': Shows the chart filter in a JSON format. This only contains the chart filter (not the stored or dashboard [[Filtering_in_QPR_ProcessAnalyzer|filter]]). Syntax for the filter JSON is described in [[Filtering_in_QPR_ProcessAnalyzer_Queries|Filtering Queries]].
* '''Chart comparison''': Similar to the Chart filter, except showing the defined comparison.

=== On-screen Settings ===
Measure, dimension, column and analyzed objects parameters can be defined as on-screen settings, i.e. the settings are always visible above the chart in the dashboard for quick access. The on-screen settings are defined as a JSON array, where each item is an object with following properties:
* '''type''': Either ''measure'', ''dimension'' or ''root''. If slicing into dimensions is disabled, columns correspond to dimensions.
* '''index''': Index of the measure, dimension or column starting from zero.
* '''parameter''': Name of the parameter.
* '''label''': Custom label for the setting.
* '''maxWidth''': Maximum width of the shown setting in pixels.
* '''newLine''': Defines whether the setting is positioned to a new line for more spacing between settings.
* '''control''': UI control type which is one of the following: singleselectlist, dynamicsingleselectlist, multiselectlist, singlelinetext, multilinetext, numericfield, datefield, datetimefield, checkbox, bpmneditor or colorpicker.
* '''mandatory''': Defined that the UI control is mandatory, i.e. the chart is not drawn until a value has been specified.
* '''defaultValue''': Default value used when the chart is opened. Note that when a UI control is mandatory and there is not default value, the chart is not drawn until a value has been specified.
* '''minValue''': For ''numericfield'', specified the minimum allowed numerical value.
* '''maxValue''': For ''numericfield'', specified the maximum allowed numerical value.
* '''allowDecimals''': For ''numericfield'', specified whether decimal numbers can be specified (or only integer numbers).
* '''escape''': Defines whether the value is escaped for string literals (" -> \" and \ -> \\). Escaping is needed when the value is used in an expression in a string literal.
* '''trueValue''' For ''checkbox'', defines the value to be used when the checkbox is checked.
* '''falseValue''': For ''checkbox'', defines the value to be used when the checkbox is unchecked.
* '''updateImmediately''': For ''numericfield'' and ''singlelinetext'', specified whether the chart is updated with each change of the input box value. When disabled, the value updated only when cursor leaves the input box.

Example:

[[File:Onscreensettingsexample.png|center|850px]]
<pre>
[
{
"type": "dimension",
"index": 0,
"parameter": "Attribute",
"maxWidth": 500
},
{
"type": "dimension",
"index": 1,
"parameter": "Period",
"label": "Time"
}
]
</pre>
=== Variable mappings ===
Setting are for binding [[Dashboard_Variables|dashboard variables]] to chart settings, meaning that chart settings are changed when variables are changed. It's possible for example to add a drop-down list component, bind the list to a dashboard variable, and then bind the variable to settings in several charts. When using dashboard variables, the used variables need to be defined in the ''Dashboard Properties'' dialog in the ''Variables'' tab, so that the initial values of the variables are stored to the dashboard. Note that dashboard variables can be used in custom expressions using tags without specifying them in the variable mappings. Variable mappings are configured as an array of mappings where each item is an object with the following properties:
* '''variable''': Name of the bound dashboard variable.
* '''type''': One of the following type of chart setting: '''measure''', '''dimension''', '''root''' (for the ''Analyze'' list parameters), '''generic''' (all other settings in chart), '''filter''' (to map to chart filter).
* '''index''': When ''type'' is a ''measure'' or ''dimension'', the order number of the measure/dimension (starts from 0).
* '''parameter''': Name of the chart setting or parameter to bind to.
* '''filterType''': When ''type'' is ''filter'', define the filter type as '''IncludeCases''', '''ExcludeCases''', '''IncludeEventTypes''' or '''ExcludeEventTypes'''.
* '''ruleType''': When ''type'' is ''filter'', define the rule type as one of the following: '''CaseAttributeValue''', '''EventAttributeValue''', '''EventType''' or '''Case'''.
* '''attribute''': When ''type'' is ''filter'' and ''ruleType'' is ''CaseAttributeValue'' or ''EventAttributeValue'', define the case/event attribute name.
<pre>
[
{
"variable": "CaseAttributeVariable",
"type": "measure",
"index": 0,
"parameter": "Attribute"
},
{
"variable": "EventTypes",
"type": "filter",
"filterType": "IncludeEventTypes",
"ruleType": "EventType"
}
]
</pre>

=== Linked settings ===
Settings are for linking settings or parameters within a single chart. When configured, the linked settings are kept in synchronization, i.e. when any of the settings is changed, other linked settings are also changed. Linked settings are configured as an array of ''setting groups'' which are array of objects. Each object points to an individual setting using the following properties:
* '''type''': One of the following type of chart setting: '''measure''', '''dimension''', '''root''', '''generic''', '''tag'''.
* '''index''': When type is a measure or dimension, the order number of the measure/dimension (starts from 0).
* '''parameter''': Name of the chart setting or parameter.
* '''tagName''': When ''type'' is ''tag'', defined the linked tag name. The tag can be used in custom expression similar to variables.

Example:

[[File:Linkedsettings.png|center|500px]]
<pre>
[
[
{
"type": "measure",
"index": 0,
"parameter": "Start event"
},
{
"type": "measure",
"index": 1,
"parameter": "Start event"
}
],
[
{
"type": "measure",
"index": 0,
"parameter": "End event"
},
{
"type": "measure",
"index": 1,
"parameter": "End event"
}
],
[
{
"type": "measure",
"index": 0,
"parameter": "Time unit"
},
{
"type": "measure",
"index": 1,
"parameter": "Time unit"
}
]
]
</pre>

=== Benchmark performance ===
Clicking the '''Benchmark performance''' buttons starts a performance benchmark run for the chart, which measures the time taken for the server to calculate and return the required data for the chart. Benchmarking is useful when for example creating custom expressions and finding the most optimal way of writing them. The benchmark runs the calculation multiple times to reduce effect of random variation in the measurement. When the benchmark run is completed, the following information is shown:
* Benchmark result (shown as bolded) (calculated as a median time of the individual measurements)
* Variation in the benchmark measurement (calculated as a standard deviation of the individual measurements divided by the benchmark result)
* Difference to the previous benchmark result
* List of all individual measurements (abandoned are greyed out)

The highest individual measurements (approximately 40%) are abandoned from the calculation and shown as greyed out, because the highest measurements are usually result of the random variation.

The history of benchmark runs done for the chart are preserved until the dashboard is closed.

== Copy Chart Settings from Another Chart ==
You can copy chart settings and use them in another chart as follows: Go to the '''Advanced''' tab and choose from the bottom dropdown list '''Edit chart settings'''. Select all JSON and copy it to a clipboard. Go to another chart, paste the settings to the same chart settings textbox and click Save.

[[Category: QPR ProcessAnalyzer]]

QPR Software as a Service Agreement

2019-11-20T07:05:52Z

QPRAdmin:

SOFTWARE AS A SERVICE AGREEMENT

This Software as a Service Agreement is a legal agreement between QPR Software Plc. (hereinafter "QPR") and a customer organization (hereinafter the "Customer" and, together with QPR, the "Parties") for software hosting services (“Services”) that you purchase.

YOU AGREE TO BE BOUND BY THE TERMS OF THIS SOFTWARE AS A SERVICE AGREEMENT WHEN YOU PURCHASE AND USE SOFTWARE HOSTING SERVICES FROM QPR SOFTWARE PLC.

By way of this Software as a Service Agreement, the Customer agrees to allow QPR to host software, which the Customer has licensed and paid for, at QPR’s or its hosting vendor's data center(s). Services shall be provided in accordance with the terms of the agreement in force at the time of delivery. By using the Services, you accept and agree to the terms and conditions of this Agreement.

'''1 Contents of the Services'''

1.1 The Services shall contain the hardware- and software platform required for the Service for the Customer including the Server hardware, network connectivity from the server hardware to the internet, and backups of the data in the environment.

1.2 Operational Support: Support for the environment is available from QPR Customer Care during normal business opening hours. QPR reserves the right to alter the business opening hours of QPR Customer Care. QPR may at its own discretion subcontract any part or all of the support services to its authorized resellers, subcontractors, or representatives which are bound by the same responsibilities as QPR.

'''2 Service and Network Availability'''

2.1 Guarantee of Availability: QPR will make commercially reasonable efforts to ensure that the Services are available to use during any given time, except during maintenance windows. Operation of the Service may require short breaks in the service outside maintenance windows.

2.2 Maintenance Windows: QPR will perform maintenance in hosting servers and environments in pre-scheduled maintenance windows. The standard maintenance windows will be communicated separately. In case of emergency maintenance requirements, QPR will make effort to inform Customers of such maintenance needs at least 24 hours in advance.

2.3 Third Party Network Availability: QPR cannot guarantee network availability between the Customer and the hosted environment, as network availability can involve numerous third parties and is beyond the control of QPR. QPR will not be liable for any down time that you experience as a result of your own network connectivity issues.

2.4 Unavailability of Services: QPR is obligated to start resolving any service outage or other problem with the Services within one (1) hour after receiving notification from the Customer during opening hours of QPR Customer Care. QPR will make efforts to determine whether the outage or other problem is within QPR's reasonable control. If QPR determines the issue is attributable to QPR, the Customer will be credited 1 day of Service fee for every 4 hours of down-time the Customer experienced after the notification of the downtime to QPR. QPR will have no other liability to the Customer for failure to provide the guaranteed network availability.

'''3 Information Security, Storage and Backup'''

3.1 Information Security: QPR will make commercially reasonable efforts to provide and maintain a secure environment for Customer Data. In the unlikely event of a security breach of Customer Data caused by QPR, the exclusive remedy will be limited to a refund of the total amount paid by customer for the SaaS service over the twelve (12) months preceding the event. You understand and agree to assume the risk of any such security breach and agree to hold QPR harmless therefrom.

3.2 Data Storage: Customer data is stored in a database file on hosted servers and it is backed up on a nightly basis. QPR shall maintain your data/information for a period of ten (10) business days after the Service is cancelled and will deliver the data to Customer upon request.

3.3 Data Backup: Customer Data is backed up on a nightly basis. In the unlikely event of a data loss in which all sets of backup data are also unrecoverable, QPRs sole liability will be to provide you with a refund of a maximum twelve (12) months of SaaS Service fees. No Customer Data is retroactively removed from the backups.

3.4 Rights to Customer Data: QPR asserts no ownership or other rights to Customer Data. The Customer is solely responsible for having all required rights to use the Customer Data in the manner required by the Service or applicable laws, including but not limited to transferring the data to an information system maintained by a third party. Customer agrees to not transfer any illegal or infringing material to the Service.

3.5 Storing Customer Data: QPR may store the Customer Data at any geographical location within the European Union using any third-party storage providers it deems suitable. Should there be limitations as to where customer data can be stored geographically, Customer is obliged to inform QPR before transferring any of such data to the service.

3.6 Access to Customer Data: QPR personnel shall not access the Customer Data, except as needed for resolving any technical problems of the Service, performing maintenance tasks to the Service, or performing agreed services.

3.7 Return of Data: Should Customer wish to obtain a raw copy of Customer Data from QPR, it is made possible by QPR guiding the Customer to download the data or by agreeing on a separately invoiceable service by QPR. Customer is liable to communicate this request to QPR prior to or in conjunction with termination of Services.

'''4 Service Fees'''

4.1 Service Fees: You agree to pay for such Services on a timely basis and in accordance with payment terms and contract duration. Your failure to make timely payment for Service fees may result in QPR suspending your account and subsequently deleting Customer Data from the Service after 30 days when the Service fee due date has passed.

'''5 Warranties and Disclaimer of Warranties'''

5.1 Except as provided below, QPR warrants that it owns all rights, title and interest in and to the Software and Software Products and that the Software substantially conforms to the functional specifications and that the Software and Software Products shall be free from material defects in workmanship and materials that prevent them from substantially meeting the aforementioned criteria.

5.2 EXCEPT AS EXPRESSLY PROVIDED IN THIS SAAS SERVICE AGREEMENT, AND TO THE MAXIMUM EXTENT PERMITTED BY LAW, NEITHER PARTY MAKES ANY WARRANTIES TO THE OTHER PARTY, AND EACH PARTY DISCLAIMS ALL WARRANTIES, ORAL OR WRITTEN, EXPRESS, IMPLIED OR STATUTORY, WITH RESPECT TO ITS PERFORMANCE UNDER THIS AGREEMENT, FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT AND IMPLIED WARRANTIES ARISING FROM ANY COURSE OF DEALING OR COURS OF PERFORMANCE. QPR DOES NOT GIVE ANY WARRANTY THAT THE SERVICE IS VIRUS OR FAULT FREE, OR IT FUNCTIONS UNINTERRUPTED. QPR PROVIDES THE SERVICE “AS-IS.

'''6 Limitation of Liability'''

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, IN NO EVENT WILL QPR BE LIABLE FOR ANY LOST PROFITS OR BUSINESS OPPORTUNITIES, LOSS OF USE, BUSINESS INTERRUPTION, LOSS OF DATA (WHETHER DIRECT OR INDIRECT), OR ANY INDIRECT, SPECIAL, INCIDENTAL, PUNITIVE OR CONSE¬QUEN¬TIAL DAMAGES UNDER ANY THEORY OF LIABILITY, WHETHER BASED IN CONTRACT, TORT, NEGLIGENCE, PRODUCT LIABILITY, OR OTHERWISE. BECAUSE SOME JURISDICTIONS DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES, BUT MAY ALLOW LIABILITY TO BE LIMITED, IN SUCH CASES QPR’S ENTIRE LIABILITY SHALL BE LIMITED TO THE TOTAL AMOUNT PAID BY CUSTOMER OVER THE SIX MONTHS PRECEDING THE CLAIM GIVING RISE TO LIABILITY.

'''7 General Terms'''

7.1 Consent to Use of Data: The Customer agrees that QPR and its affiliates may collect and use technical information gathered as part of any support provided to you in relation to the Services. QPR may also collect information on how and by whom the Service is being used. Collected information may be used to improve QPR support and Services or to provide customized services or technologies to the Customer. QPR will not disclose information concerning the use of the Service outside of the Customer organization in a form that personally identifies the user.

7.2 Consent to Communications: Customer agrees that QPR may send electronic and other communications to users of the Service.

7.3 Additional Services: This Agreement applies to Service updates, supplements, or Internet-based Services components that QPR may provide to you or make available to you after the date you purchase Services from QPR, unless QPR provides other terms along with the updates, supplements, or Internet-based Services components. QPR reserves the right to discontinue any Internet-based Services provided to you or made available to you.

7.4 Applicable Law: This Agreement shall be governed by and construed in accordance with the laws of Finland excluding its choice of law provisions. Any dispute arising hereunder shall be resolved by The Arbitration Institute of the Finland Chamber of Commerce. The arbitration shall be held in Helsinki and the language of proceedings shall be in English, unless the Parties otherwise agree.

7.5 Assignment: This Agreement and any rights thereto or obligations or interests may not be assigned without a prior written consent of QPR.

7.6 Waiver: Waivers must be in writing signed by an authorized representative. The waiver of one breach or default under this Agreement will not constitute the waiver of any subsequent breach or default.

7.7 Severability: Any provision of this Agreement held to be illegal or unenforceable will be deemed amended to conform to applicable laws or regulations, or if it cannot be so amended without materially altering the intention of the parties, it will be stricken and the remainder of this Agreement will continue in full force and effect.

QPR ProcessAnalyzer Wiki

2012-02-29T11:11:29Z

QPRAdmin:

QPR ProcessAnalyzer Wiki

2012-02-29T11:11:16Z

QPRAdmin:

PA Wiki:About

2012-02-29T11:04:30Z

2012-02-14T10:02:18Z

QPRAdmin:

QPR ProcessAnalyzer Wiki

2012-02-14T09:50:45Z

QPRAdmin: /* Analysis */

This wiki contains the documentation for QPR ProcessAnalyzer, which is a Microsoft Office Excel Add-in for Automated Business Process Discovery.

== Installing ==
See the [[Installing QPR ProcessAnalyzer]] page for instructions on how to install QPR ProcessAnalyzer.

== Using QPR ProcessAnalyzer ==

QPR ProcessAnalyzer commands are located on the QPR ProcessAnalyzer tab on the ribbon:

[[File:Ribbon.png]]

=== Tools ===
[[Data Source]]: configuring ProcesAnalyzer web service address and credentials.<br\>
[[User Manager]]: create, edit, and delete users and manage user roles.<br\>
[[Model Manager]]: manage models available on the current ProcessAnalyzer web service connection.<br\>

=== Analysis ===
Run [[Process Analysis|Process]], [[Duration Analysis|Duration]], [[Profiling Analysis|Profiling]], or [[Path Analysis|Path]] analysis.<br\>
The Analysis Settings pane can be opened by clicking the [[File:SettingsLink.png]] button in the Analysis group of the ribbon.<br\>

=== Show ===
Show events filtered according to the [[Cases]], [[Variations]], [[Events]], [[Event Types]], or [[Flows]] of the selected element(s).

=== View ===
The [[Filtering|Include Only]] and [[Filtering|Exclude]] buttons will create a filtered view according to what's selected in the analysis view.<br\>
The [[Views#Change View|Change]] button can be used to change the view.<br\>
The [[Views#View Manager|View Manager]] can be opened by clicking the [[File:SettingsLink.png]] button in the View group of the ribbon.<br\>

=== Help ===
Access QPR Processanalyzer Tutorial, Sample Files, About, and QPR ProcessAnalyzer Web User Interface.

== Use Cases ==
See the [[Use Cases]] page for different QPR ProcessAnalyzer tools.

QPR ProcessAnalyzer Wiki

2012-02-14T09:49:16Z

QPRAdmin:

This wiki contains the documentation for QPR ProcessAnalyzer, which is a Microsoft Office Excel Add-in for Automated Business Process Discovery.

== Installing ==
See the [[Installing QPR ProcessAnalyzer]] page for instructions on how to install QPR ProcessAnalyzer.

== Using QPR ProcessAnalyzer ==

QPR ProcessAnalyzer commands are located on the QPR ProcessAnalyzer tab on the ribbon:

[[File:Ribbon.png]]

=== Tools ===
[[Data Source]]: configuring ProcesAnalyzer web service address and credentials.<br\>
[[User Manager]]: create, edit, and delete users and manage user roles.<br\>
[[Model Manager]]: manage models available on the current ProcessAnalyzer web service connection.<br\>

=== Analysis ===
Run [[Process Analysis|Process]], [[Duration Analysis|Duration]], [[Profiling Analysis|Profiling]], or [[Path Analysis|Path]] analysis.

=== Show ===
Show events filtered according to the [[Cases]], [[Variations]], [[Events]], [[Event Types]], or [[Flows]] of the selected element(s).

=== View ===
The [[Filtering|Include Only]] and [[Filtering|Exclude]] buttons will create a filtered view according to what's selected in the analysis view.<br\>
The [[Views#Change View|Change]] button can be used to change the view.<br\>
The [[Views#View Manager|View Manager]] can be opened by clicking the [[File:SettingsLink.png]] button in the View group of the ribbon.<br\>

=== Help ===
Access QPR Processanalyzer Tutorial, Sample Files, About, and QPR ProcessAnalyzer Web User Interface.

== Use Cases ==
See the [[Use Cases]] page for different QPR ProcessAnalyzer tools.

QPR ProcessAnalyzer Wiki

2012-02-14T09:47:41Z

Filtering in QPR ProcessAnalyzer

2012-02-14T09:22:40Z

QPRAdmin:

Using the '''Include Only''' and '''Exclude''' buttons and their drop-down menus it is possible to filter the data. Depending on the active view, the buttons do the following:

'''Process Analysis View with 1..n Activities Selected, 1..m Transitions selected''':
*Include Only
: Creates a new view containing only the cases that go through all the selected activities and transitions.
*Exclude
: Creates a new view excluding the cases that go through the selected activities and transitions.

'''Duration Analysis with 1..n Rows Selected''':
*Include Only
: Creates a new view containing only the cases with the selected duration(s).
*Exclude
: Creates a new view excluding the cases with the selected duration(s).

'''Profiling Analysis with 1..n Rows Selected''':
*Include Only
: Creates a new view containing only the cases with the selected duration(s).
*Exclude
: Creates a new view excluding the cases with the selected duration(s).

'''List of Cases with 1..n Rows Selected''':
*Include Only
: Creates a new view containing only the selected case(s).
*Exclude
: Creates a new view excluding the selected case(s).

'''List of Variations with 1..n Rows Selected''':
*Include Only
: Creates a new view containing only the cases that belong to selected variation(s).
* Exclude
: Creates a new view excluding the cases that belong to selected variation(s).

'''List of Event Types with 1..n Rows Selected''':
*Include Only
: Creates a new view containing only the activities that are selected.
*Exclude
: Creates a new view excluding the activities that are selected.

'''List of Events with 1..n Rows Selected''':
*Include Only
: Creates a new view containing only the events that are selected.
*Exclude
: Creates a new view excluding the events that are selected.

The filtered view that is created will be available in the [[View Manager]].

The filtered view can also be accessed by selecting it by using the [[Change View|Change]] drop-down menu.

Clicking the '''Change''' button will open a drop-down list containing the following items:
*Restore Default: restores the view to the default state
*Each view for the current model, sorted by time
*Clear All Filters: clears all filters applied by the Include Only and Exclude buttons

Filtering in QPR ProcessAnalyzer

QPR ProcessAnalyzer Wiki

2012-02-13T13:28:30Z

QPRAdmin:

QPR ProcessAnalyzer Wiki

2012-02-13T13:27:09Z

QPRAdmin:

Manage Users and Groups

2012-02-13T13:12:54Z

QPRAdmin: Created page with 'As a non-administrator user, you can view and edit your user properties via the User Manager dialog: #Select your user name from the list and click the '''Properties''' button. #…'

As a non-administrator user, you can view and edit your user properties via the User Manager dialog:
#Select your user name from the list and click the '''Properties''' button.
#In the User Properties dialog that opens, you can change your User Name, E-Mail address, and Password.
#To apply the changes, click '''OK'''.

QPR ProcessAnalyzer Wiki

2012-02-13T12:59:59Z

QPRAdmin:

QPR ProcessAnalyzer Wiki

2012-02-13T12:59:19Z

QPRAdmin:

QPR ProcessAnalyzer Wiki

2012-02-13T12:40:35Z

QPRAdmin:

MediaWiki:Mainpage

2012-02-13T12:26:49Z

QPRAdmin: Created page with 'QPR_ProcessAnalyzer_Wiki'

QPR_ProcessAnalyzer_Wiki

QPR ProcessAnalyzer Wiki

2012-02-13T12:25:17Z

QPRAdmin: Created page with 'This wiki contains the documentation for QPR ProcessAnalyzer, which is a Microsoft Office Excel Add-in for Automated Business Process Discovery. == Installing == See the [[Insta…'