HTML Properties - Revision history

Ollvihe: /* User and session information in QPR ProcessAnalyzer UI */

2019-12-23T09:58:14Z

User and session information in QPR ProcessAnalyzer UI

Ollvihe: /* Cancelling QPR ProcessAnalyzer Queries */

2019-12-23T09:58:07Z

Cancelling QPR ProcessAnalyzer Queries

Ollvihe: /* Direct Queries to Datasource */

2019-12-23T09:56:12Z

Direct Queries to Datasource

Ollvihe: /* Examples */

2019-12-23T09:55:12Z

Examples

Ollvihe: /* Examples */

2019-12-23T09:54:54Z

Examples

Ollvihe: /* Import QPR ProcessAnalyzer Data */

2019-12-23T09:54:22Z

Import QPR ProcessAnalyzer Data

Ollvihe: /* User and session information in QPR ProcessAnalyzer UI */

2019-10-30T13:58:29Z

User and session information in QPR ProcessAnalyzer UI

Ollvihe: /* User and session information in QPR ProcessAnalyzer UI */

2019-10-30T13:55:16Z

User and session information in QPR ProcessAnalyzer UI

Ollvihe: /* User and session information in QPR ProcessAnalyzer UI */

2019-10-30T13:53:51Z

User and session information in QPR ProcessAnalyzer UI

Ollvihe: /* User and session information in QPR ProcessAnalyzer UI */

2019-10-30T13:46:59Z

User and session information in QPR ProcessAnalyzer UI

← Older revision		Revision as of 09:58, 23 December 2019
Line 237:		Line 237:

	When defining CSS styles in HTML presentation objects, note that CSS definitions are global in the HTML page, and thus it's possible to add CSS that affects structures outside the HTML presentation object. To make sure that the CSS doesn't have unintentional effects outside the HTML presentation object, use id's or classes that are unique. It can be done by using the <uniqueId> tag in the name of the id or class.		When defining CSS styles in HTML presentation objects, note that CSS definitions are global in the HTML page, and thus it's possible to add CSS that affects structures outside the HTML presentation object. To make sure that the CSS doesn't have unintentional effects outside the HTML presentation object, use id's or classes that are unique. It can be done by using the <uniqueId> tag in the name of the id or class.
−
−	~~== User and session information in QPR ProcessAnalyzer UI ==~~
−	~~Note: this feature is only available in the QPR ProcessAnalyzer UI (not in QPR UI).~~
−
−	User and session related information is available in the below listed JavaScript variables. User information is from the QPR ProcessAnalyzer user management. The information is removed from the JavaScript variables when user logs out.
−
−	~~{\| class="wikitable"~~
−	~~!Property name~~
−	~~!Description~~
−	\|-
−	~~\|qpr.version~~
−	~~\|[[QPR_ProcessAnalyzer_Release_Notes\|QPR ProcessAnalyzer version]].~~
−	\|-
−	~~\|qpr.sessionInfo.accessToken~~
−	\|Access token for the user session. An access token is created when a user logs in, and it's invalidated when user logs out. The access token is used to authenticate each request to the QPR ProcessAnalyzer server.
−	\|-
−	~~\|qpr.sessionInfo.user.description~~
−	~~\|User additional description.~~
−	\|-
−	~~\|qpr.sessionInfo.user.email~~
−	~~\|User email address.~~
−	\|-
−	~~\|qpr.sessionInfo.user.fullName~~
−	~~\|User full name.~~
−	\|-
−	~~\|qpr.sessionInfo.user.globalRoles~~
−	~~\|All [[User_Roles_and_Permissions_in_QPR_ProcessAnalyzer#Global_and_Project_Roles\|global roles]] of the user (as a string array). Note that the project specific roles are not listed.~~
−	\|-
−	~~\|qpr.sessionInfo.user.groups~~
−	~~\|All [[Manage_Users_in_QPR_ProcessAnalyzer_Excel_Client#Assigning_User_to_User_Group\|groups]] of the user.~~
−	\|-
−	~~\|qpr.sessionInfo.user.id~~
−	~~\|User id.~~
−	\|-
−	~~\|qpr.sessionInfo.user.loginName~~
−	~~\|User login name.~~
−	\|}

	== Example: Reading Datasets ==		== Example: Reading Datasets ==

← Older revision		Revision as of 09:58, 23 December 2019
Line 194:		Line 194:

	See the [[#Examples\|Examples]] section for more example(s).		See the [[#Examples\|Examples]] section for more example(s).
−
−	~~== Cancelling QPR ProcessAnalyzer Queries ==~~
−	~~Cancelling a QPR ProcessAnalyzer query initiated by a qpr.runQuery function is done using the JavaScript function '''qpr.cancelQuery(identifier)'''. The qpr.cancelQuery function has one parameter:~~
−
−	~~{\| class="wikitable"~~
−	~~!'''Parameter name'''~~
−	~~! '''Description'''~~
−	\|-
−	~~\|\|identifier~~
−	~~\|\|The query identifier of the runQuery function.~~
−	\|}

	== QPR UI Protocol Versions ==		== QPR UI Protocol Versions ==

@@ Line 122: / Line 122: @@
 == Direct Queries to Datasource ==
-The ''direct query'' is a way to fetch data from the QPR UI datasources ([[QPR Suite Web Service Datasource|QPR Suite Web Service]], [[QPR ProcessAnalyzer Datasource|QPR ProcessAnalyzer]], and [[QPR Reporting Expression]]) without creating a dataset. This is done using the JavaScript function '''qpr.runQuery(datasourceType, queryParameters, successCallback, errorCallback, identifier)'''. Parameters for the qpr.runQuery function:
+The ''direct query'' is a way to fetch data from the QPR UI datasources ([[QPR Suite Web Service Datasource|QPR Suite Web Service]] and [[QPR Reporting Expression]]) without creating a dataset. This is done using the JavaScript function '''qpr.runQuery(datasourceType, queryParameters, successCallback, errorCallback, identifier)'''. Parameters for the qpr.runQuery function:
 {| class="wikitable"

@@ Line 327: / Line 327: @@
 * [[HTML Presentation Object: Get cell value from dataset|Get cell value from dataset]]
 * [[HTML Presentation Object: Hierarchy Browser|Hierarchy Browser]]
 * [[HTML Presentation Object: BPMN Diagram|BPMN Diagram]]
 [[Category: QPR UI]]

@@ Line 329: / Line 329: @@
 * [[HTML Presentation Object: QPR ProcessAnalyzer Query|QPR ProcessAnalyzer Query]]
 * [[HTML Presentation Object: BPMN Diagram|BPMN Diagram]]
 [[Category: QPR UI]]

@@ Line 214: / Line 214: @@
 * '''protocolVersion''': Communication protocol version that the QPR UI server uses.
 * '''ssoConfigured''': boolean value stating if single sign-on is in use or not.
 == Tag uniqueId ==

@@ Line 308: / Line 308: @@
 Note: this feature is only available in the QPR ProcessAnalyzer UI (not in QPR UI).
-User and session related information is available in the below listed JavaScript variables. User information is from the QPR ProcessAnalyzer user management.
+User and session related information is available in the below listed JavaScript variables. User information is from the QPR ProcessAnalyzer user management. The information is removed from the JavaScript variables when user logs out.
 {| class="wikitable"

@@ Line 330: / Line 330: @@
 |-
 |qpr.sessionInfo.user.globalRoles
-|All [[User_Roles_and_Permissions_in_QPR_ProcessAnalyzer#Global_and_Project_Roles|global roles]] that the user currently has (as a string array). Note that the project specific roles are not listed.
+|All [[User_Roles_and_Permissions_in_QPR_ProcessAnalyzer#Global_and_Project_Roles|global roles]] of the user (as a string array). Note that the project specific roles are not listed.
 |-
 |qpr.sessionInfo.user.groups
-|All groups of the user.
+|All [[Manage_Users_in_QPR_ProcessAnalyzer_Excel_Client#Assigning_User_to_User_Group|groups]] of the user.
 |-
 |qpr.sessionInfo.user.id

@@ Line 320: / Line 320: @@
 |Access token for the user session. An access token is created when a user logs in, and it's invalidated when user logs out. The access token is used to authenticate each request to the QPR ProcessAnalyzer server.
 |-
-|qpr.sessionInfo.user.id
+|qpr.sessionInfo.user.description
-|User id.
+|User additional description.
 |-
-|qpr.sessionInfo.user.loginName
+|qpr.sessionInfo.user.email
-|User login name.
+|User email address.
 |-
 |qpr.sessionInfo.user.fullName
 |User full name.
 |-
-|qpr.sessionInfo.user.email
+|qpr.sessionInfo.user.globalRoles
-|User email address.
+|All [[User_Roles_and_Permissions_in_QPR_ProcessAnalyzer#Global_and_Project_Roles|global roles]] that the user currently has (as a string array). Note that the project specific roles are not listed.
 |-
 |qpr.sessionInfo.user.groups
 |All groups of the user.
 |-
-|qpr.sessionInfo.user.globalRoles (string array)
+|qpr.sessionInfo.user.id
-|All [[User_Roles_and_Permissions_in_QPR_ProcessAnalyzer#Global_and_Project_Roles|global roles]] that the user currently has (as a string array). Note that the project specific roles are not listed.
+|User id.
 |}

@@ Line 306: / Line 306: @@
 == User and session information in QPR ProcessAnalyzer UI ==
-Note: this feature is only available in the QPR ProcessAnalyzer UI, and not in QPR UI.
+Note: this feature is only available in the QPR ProcessAnalyzer UI (not in QPR UI).
-User and session related information is available in the following JavaScript variables. User information is from the QPR ProcessAnalyzer user management.
+User and session related information is available in the below listed JavaScript variables. User information is from the QPR ProcessAnalyzer user management.
 {| class="wikitable"
-!Function Name
+!Property name
 !Description
 |-
 |qpr.version
-|QPR ProcessAnalyzer version.
+|[[QPR_ProcessAnalyzer_Release_Notes|QPR ProcessAnalyzer version]].
 |-
 |qpr.sessionInfo.accessToken
-|Access token for the user session. The access token is created when user logs in and it's invalidated when user logs out. The access token is used to authenticate each request to the QPR ProcessAnalyzer server.
+|Access token for the user session. An access token is created when a user logs in, and it's invalidated when user logs out. The access token is used to authenticate each request to the QPR ProcessAnalyzer server.
 |-
 |qpr.sessionInfo.user.id
@@ Line 334: / Line 333: @@
 |-
 |qpr.sessionInfo.user.description
-|User description.
+|User additional description.
 |-
-|qpr.sessionInfo.user.groups (string array)
+|qpr.sessionInfo.user.groups
 |All groups of the user.
 |-
 |qpr.sessionInfo.user.globalRoles (string array)
-|All [[User_Roles_and_Permissions_in_QPR_ProcessAnalyzer#Global_and_Project_Roles|global roles]] that the user currently has. Note that the project specific roles are not listed.
+|All [[User_Roles_and_Permissions_in_QPR_ProcessAnalyzer#Global_and_Project_Roles|global roles]] that the user currently has (as a string array). Note that the project specific roles are not listed.
 |}