QPR ProcessAnalyzer Table - Revision history

Ollvihe: /* Table actions */

2025-02-06T16:28:40Z

Table actions

← Older revision		Revision as of 16:28, 6 February 2025
Line 23:		Line 23:
	* '''Set dashboard variables''': Set [[Dashboard_Variables\|variables]] when clicking the text in the table cell. Similar tags as for the web link, can be used both for the variable name and variable value fields. If there is either the sys:dashboard or sys:dashboardIdentifier variable among the changed variables (i.e. clicking will go to other dashboard), the variables are set to the session level - otherwise they are set to the dashboard level. If defining the ''Filter'' or ''Comparison'' variable with an empty value, the corresponding filter or comparison rule is created automatically (works only for dimensions). Variable values are always strings because the value is defined as a string "template". For Snowflake models, variable values are formatted using the [[Stringified_Value_Format\|stringified format]] (they are compatible with the [[Chart_Linked_Settings\|linked settings]]), and for in-memory models variable values are set as such without any formatting.		* '''Set dashboard variables''': Set [[Dashboard_Variables\|variables]] when clicking the text in the table cell. Similar tags as for the web link, can be used both for the variable name and variable value fields. If there is either the sys:dashboard or sys:dashboardIdentifier variable among the changed variables (i.e. clicking will go to other dashboard), the variables are set to the session level - otherwise they are set to the dashboard level. If defining the ''Filter'' or ''Comparison'' variable with an empty value, the corresponding filter or comparison rule is created automatically (works only for dimensions). Variable values are always strings because the value is defined as a string "template". For Snowflake models, variable values are formatted using the [[Stringified_Value_Format\|stringified format]] (they are compatible with the [[Chart_Linked_Settings\|linked settings]]), and for in-memory models variable values are set as such without any formatting.

	The checkbox '''Open in new window''' determines whether to ~~use~~ same browser window or ~~open~~ to a new window or tab. When checked, the link will be opened or variables will be set in a new browser window or tab. When unchecked, the link will be opened or variables will be set in the same window.		The checkbox '''Open in new window''' determines whether the target opens to the same browser window or to a new window or tab. When checked, the link will be opened or variables will be set in a new browser window or tab. When unchecked, the link will be opened or variables will be set in the same window.

	It's also possible to run scripts that are available in the [[Actions_to_Run_Script_in_Table\|table context menu]].		It's also possible to run scripts that are available in the [[Actions_to_Run_Script_in_Table\|table context menu]].

Ollvihe: /* Table actions */

2025-02-06T16:22:55Z

Table actions

← Older revision		Revision as of 16:22, 6 February 2025
Line 19:		Line 19:

	== Table actions ==		== Table actions ==
	Clicking ~~text items~~ in the table can ~~change dashboard variables or~~ open web links. These are configured using the table actions as follows:		Clicking texts in the table can open web links and set dashboard variables. These are configured using the table actions as follows:
	* '''Open web link''': Measure/dimension/column will be a clickable web link opening the defined web site. 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 which is added to the end of the QPR ProcessAnalyzer address to form the complete link. Examples: ''<nowiki>https://google.com/search/q=${measure:2}</nowiki>'', ''<nowiki>https://wiki.onqpr.com/pa/index.php?search=${this}</nowiki>'', ''<nowiki>qprpa/ui/#/dashboard?sys:dashboard=123&myVariable=${dimension:1}</nowiki>''		* '''Open web link''': Measure/dimension/column will be a clickable web link opening the defined web site. 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 which is added to the end of the QPR ProcessAnalyzer address to form the complete link. Examples: ''<nowiki>https://google.com/search/q=${measure:2}</nowiki>'', ''<nowiki>https://wiki.onqpr.com/pa/index.php?search=${this}</nowiki>'', ''<nowiki>qprpa/ui/#/dashboard?sys:dashboard=123&myVariable=${dimension:1}</nowiki>''
	* '''Set dashboard variables''': Set [[Dashboard_Variables\|variables]] when clicking the text in the table cell. Similar tags as for the web link, can be used both for the variable name and variable value fields. If there is either the sys:dashboard or sys:dashboardIdentifier variable among the changed variables (i.e. clicking will go to other dashboard), the variables are set to the session level - otherwise they are set to the dashboard level. If defining the ''Filter'' or ''Comparison'' variable with an empty value, the corresponding filter or comparison rule is created automatically (works only for dimensions). Variable values are always strings because the value is defined as a string "template". For Snowflake models, variable values are formatted using the [[Stringified_Value_Format\|stringified format]] (they are compatible with the [[Chart_Linked_Settings\|linked settings]]), and for in-memory models variable values are set as such without any formatting.		* '''Set dashboard variables''': Set [[Dashboard_Variables\|variables]] when clicking the text in the table cell. Similar tags as for the web link, can be used both for the variable name and variable value fields. If there is either the sys:dashboard or sys:dashboardIdentifier variable among the changed variables (i.e. clicking will go to other dashboard), the variables are set to the session level - otherwise they are set to the dashboard level. If defining the ''Filter'' or ''Comparison'' variable with an empty value, the corresponding filter or comparison rule is created automatically (works only for dimensions). Variable values are always strings because the value is defined as a string "template". For Snowflake models, variable values are formatted using the [[Stringified_Value_Format\|stringified format]] (they are compatible with the [[Chart_Linked_Settings\|linked settings]]), and for in-memory models variable values are set as such without any formatting.

Ollvihe: /* Table actions */

2025-02-06T16:21:47Z

Table actions

← Older revision		Revision as of 16:21, 6 February 2025
Line 21:		Line 21:
	Clicking text items in the table can change dashboard variables or open web links. These are configured using the table actions as follows:		Clicking text items in the table can change dashboard variables or open web links. These are configured using the table actions as follows:
	* '''Open web link''': Measure/dimension/column will be a clickable web link opening the defined web site. 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 which is added to the end of the QPR ProcessAnalyzer address to form the complete link. Examples: ''<nowiki>https://google.com/search/q=${measure:2}</nowiki>'', ''<nowiki>https://wiki.onqpr.com/pa/index.php?search=${this}</nowiki>'', ''<nowiki>qprpa/ui/#/dashboard?sys:dashboard=123&myVariable=${dimension:1}</nowiki>''		* '''Open web link''': Measure/dimension/column will be a clickable web link opening the defined web site. 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 which is added to the end of the QPR ProcessAnalyzer address to form the complete link. Examples: ''<nowiki>https://google.com/search/q=${measure:2}</nowiki>'', ''<nowiki>https://wiki.onqpr.com/pa/index.php?search=${this}</nowiki>'', ''<nowiki>qprpa/ui/#/dashboard?sys:dashboard=123&myVariable=${dimension:1}</nowiki>''
	* '''Set dashboard variables''': Set [[Dashboard_Variables\|variables]] when clicking the text in the table cell. Similar tags as for the web link, can be used both for the variable name and variable value fields. If there is either the sys:dashboard or sys:dashboardIdentifier variable among the changed variables (i.e. clicking will go to other dashboard), the variables are set to the session level - otherwise they are set to the dashboard level. If defining the ''Filter'' or ''Comparison'' variable with an empty value, the corresponding filter or comparison rule is created automatically (works only for dimensions). ~~Variables set~~ are always strings because the value is defined as a string "template". For Snowflake models, variable values are formatted using the [[Stringified_Value_Format\|stringified format]] (~~so that the~~ are compatible with [[Chart_Linked_Settings\|linked settings]]), and for in-memory models variable values are set as such without any formatting.		* '''Set dashboard variables''': Set [[Dashboard_Variables\|variables]] when clicking the text in the table cell. Similar tags as for the web link, can be used both for the variable name and variable value fields. If there is either the sys:dashboard or sys:dashboardIdentifier variable among the changed variables (i.e. clicking will go to other dashboard), the variables are set to the session level - otherwise they are set to the dashboard level. If defining the ''Filter'' or ''Comparison'' variable with an empty value, the corresponding filter or comparison rule is created automatically (works only for dimensions). Variable values are always strings because the value is defined as a string "template". For Snowflake models, variable values are formatted using the [[Stringified_Value_Format\|stringified format]] (they are compatible with the [[Chart_Linked_Settings\|linked settings]]), and for in-memory models variable values are set as such without any formatting.

	The checkbox '''Open in new window''' determines whether to use same browser window or open to a new window or tab. When checked, the link will be opened or variables will be set in a new browser window or tab. When unchecked, the link will be opened or variables will be set in the same window.		The checkbox '''Open in new window''' determines whether to use same browser window or open to a new window or tab. When checked, the link will be opened or variables will be set in a new browser window or tab. When unchecked, the link will be opened or variables will be set in the same window.

Ollvihe: /* Table actions */

2025-02-06T16:20:04Z

Table actions

← Older revision		Revision as of 16:20, 6 February 2025
Line 21:		Line 21:
	Clicking text items in the table can change dashboard variables or open web links. These are configured using the table actions as follows:		Clicking text items in the table can change dashboard variables or open web links. These are configured using the table actions as follows:
	* '''Open web link''': Measure/dimension/column will be a clickable web link opening the defined web site. 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 which is added to the end of the QPR ProcessAnalyzer address to form the complete link. Examples: ''<nowiki>https://google.com/search/q=${measure:2}</nowiki>'', ''<nowiki>https://wiki.onqpr.com/pa/index.php?search=${this}</nowiki>'', ''<nowiki>qprpa/ui/#/dashboard?sys:dashboard=123&myVariable=${dimension:1}</nowiki>''		* '''Open web link''': Measure/dimension/column will be a clickable web link opening the defined web site. 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 which is added to the end of the QPR ProcessAnalyzer address to form the complete link. Examples: ''<nowiki>https://google.com/search/q=${measure:2}</nowiki>'', ''<nowiki>https://wiki.onqpr.com/pa/index.php?search=${this}</nowiki>'', ''<nowiki>qprpa/ui/#/dashboard?sys:dashboard=123&myVariable=${dimension:1}</nowiki>''
	* '''Set dashboard variables''': ~~Defines~~ [[Dashboard_Variables\|variables]] ~~that are set,~~ when clicking the text in the table cell. Similar tags as for the web link, can be used both for the variable name and variable value fields. If there is either the sys:dashboard or sys:dashboardIdentifier variable among the changed variables (i.e. clicking will go to other dashboard), the variables are set to the session level - otherwise they are set to the dashboard level. If defining the ''Filter'' or ''Comparison'' variable with an empty value, the corresponding filter or comparison rule is created automatically (works only for dimensions). Variables set are always strings. For Snowflake models, variable values are formatted using the [[Stringified_Value_Format\|stringified format]], and for in-memory models ~~variables~~ values are set as such without any formatting.		* '''Set dashboard variables''': Set [[Dashboard_Variables\|variables]] when clicking the text in the table cell. Similar tags as for the web link, can be used both for the variable name and variable value fields. If there is either the sys:dashboard or sys:dashboardIdentifier variable among the changed variables (i.e. clicking will go to other dashboard), the variables are set to the session level - otherwise they are set to the dashboard level. If defining the ''Filter'' or ''Comparison'' variable with an empty value, the corresponding filter or comparison rule is created automatically (works only for dimensions). Variables set are always strings because the value is defined as a string "template". For Snowflake models, variable values are formatted using the [[Stringified_Value_Format\|stringified format]] (so that the are compatible with [[Chart_Linked_Settings\|linked settings]]), and for in-memory models variable values are set as such without any formatting.

	The checkbox '''Open in new window''' determines whether to use same browser window or open to a new window or tab. When checked, the link will be opened or variables will be set in a new browser window or tab. When unchecked, the link will be opened or variables will be set in the same window.		The checkbox '''Open in new window''' determines whether to use same browser window or open to a new window or tab. When checked, the link will be opened or variables will be set in a new browser window or tab. When unchecked, the link will be opened or variables will be set in the same window.

Ollvihe: /* Table actions */

2025-02-06T16:18:03Z

Table actions

← Older revision		Revision as of 16:18, 6 February 2025
Line 19:		Line 19:

	== Table actions ==		== Table actions ==
	Clicking text items in the table can change dashboard ~~variable values~~ or open web links. These are configured using the table actions as follows:		Clicking text items in the table can change dashboard variables or open web links. These are configured using the table actions as follows:
	* '''Set dashboard variables''': Defines [[Dashboard_Variables\|variables]] that are set, when clicking the text in the table cell. Similar tags as for the web link (more below), can be used both for the variable name and variable value fields. If there is either the sys:dashboard or sys:dashboardIdentifier variable among the changed variables (i.e. clicking will go to other dashboard), the variables are set to the session level - otherwise they are set to the dashboard level. If defining the ''Filter'' or ''Comparison'' variable with an empty value, the corresponding filter or comparison rule is created automatically (works only for dimensions).		* '''Open web link''': Measure/dimension/column will be a clickable web link opening the defined web site. 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 which is added to the end of the QPR ProcessAnalyzer address to form the complete link. Examples: ''<nowiki>https://google.com/search/q=${measure:2}</nowiki>'', ''<nowiki>https://wiki.onqpr.com/pa/index.php?search=${this}</nowiki>'', ''<nowiki>qprpa/ui/#/dashboard?sys:dashboard=123&myVariable=${dimension:1}</nowiki>''
	* '''Open web link''': ~~When defined (works in tables only), the measure~~/dimension/column will be a clickable web link opening the ~~target~~ web site. 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 which is added to the end of the QPR ProcessAnalyzer address to form the complete link. Examples: ''<nowiki>https://google.com/search/q=${measure:2}</nowiki>'', ''<nowiki>https://wiki.onqpr.com/pa/index.php?search=${this}</nowiki>'', ''<nowiki>qprpa/ui/#/dashboard?sys:dashboard=123&myVariable=${dimension:1}</nowiki>''		* '''Set dashboard variables''': Defines [[Dashboard_Variables\|variables]] that are set, when clicking the text in the table cell. Similar tags as for the web link, can be used both for the variable name and variable value fields. If there is either the sys:dashboard or sys:dashboardIdentifier variable among the changed variables (i.e. clicking will go to other dashboard), the variables are set to the session level - otherwise they are set to the dashboard level. If defining the ''Filter'' or ''Comparison'' variable with an empty value, the corresponding filter or comparison rule is created automatically (works only for dimensions). Variables set are always strings. For Snowflake models, variable values are formatted using the [[Stringified_Value_Format\|stringified format]], and for in-memory models variables values are set as such without any formatting.

	~~There is also a~~ checkbox '''Open in new window''' ~~to determine~~ whether to use same browser window or open to a new window or tab. When checked, the link will be opened or variables will be set in a new browser window or tab. When unchecked, the link will be opened or variables will be set in the same window.		The checkbox '''Open in new window''' determines whether to use same browser window or open to a new window or tab. When checked, the link will be opened or variables will be set in a new browser window or tab. When unchecked, the link will be opened or variables will be set in the same window.

	It's also possible to run scripts that are available in the [[Actions_to_Run_Script_in_Table\|table context menu]].		It's also possible to run scripts that are available in the [[Actions_to_Run_Script_in_Table\|table context menu]].

Ollvihe: /* Table actions */

2024-08-04T17:17:23Z

Table actions

← Older revision		Revision as of 17:17, 4 August 2024
Line 24:		Line 24:

	There is also a checkbox '''Open in new window''' to determine whether to use same browser window or open to a new window or tab. When checked, the link will be opened or variables will be set in a new browser window or tab. When unchecked, the link will be opened or variables will be set in the same window.		There is also a checkbox '''Open in new window''' to determine whether to use same browser window or open to a new window or tab. When checked, the link will be opened or variables will be set in a new browser window or tab. When unchecked, the link will be opened or variables will be set in the same window.

			It's also possible to run scripts that are available in the [[Actions_to_Run_Script_in_Table\|table context menu]].

	==Conditional formatting==		==Conditional formatting==

Ollvihe: /* Icons in table cells */

2024-01-11T13:34:20Z

Icons in table cells

← Older revision		Revision as of 13:34, 11 January 2024
Line 278:		Line 278:
	"value": 100,		"value": 100,
	"comparison": ">"		"comparison": ">"
			},
			{
			"icon": "sentiment_very_dissatisfied"
	}		}
	],		],
	~~"icon": "sentiment_very_dissatisfied",~~
	"color": {		"color": {
	"rules": [		"rules": [

Ollvihe at 12:11, 9 January 2024

2024-01-09T12:11:49Z

Ollvihe: /* Textual equal rules for background color */

2024-01-09T12:10:25Z

Textual equal rules for background color

← Older revision		Revision as of 12:10, 9 January 2024
Line 298:		Line 298:

	=== Textual equal rules for background color ===		=== Textual equal rules for background color ===
	If cell content is "Dallas", background color is #00FF00~~, if~~ cell content is "New York" background color is #FF0000~~, and other~~ cells have background color #FFFF00.		If cell content is "Dallas", background color is #00FF00. If cell content is "New York" background color is #FF0000. Other cells have background color #FFFF00.
	<syntaxhighlight lang="json" line>		<syntaxhighlight lang="json" line>
	{		{

Ollvihe: /* Textual equal rules for background color */

2024-01-09T12:09:55Z

Textual equal rules for background color

← Older revision		Revision as of 12:09, 9 January 2024
Line 298:		Line 298:

	=== Textual equal rules for background color ===		=== Textual equal rules for background color ===
	If cell content is "Dallas" background color is #00FF00, if cell content is "New York" background color is #FF0000, and other cells have background color #FFFF00.		If cell content is "Dallas", background color is #00FF00, if cell content is "New York" background color is #FF0000, and other cells have background color #FFFF00.
	<syntaxhighlight lang="json" line>		<syntaxhighlight lang="json" line>
	{		{

← Older revision		Revision as of 12:11, 9 January 2024
Line 298:		Line 298:

	=== Textual equal rules for background color ===		=== Textual equal rules for background color ===
	If cell content is "Dallas", background color is #00FF00. If cell content is "New York" background color is #FF0000. Other cells have background color #FFFF00.		If cell content is "Dallas", background color is #00FF00. If cell content is "New York", background color is #FF0000. Other cells have background color #FFFF00.
	<syntaxhighlight lang="json" line>		<syntaxhighlight lang="json" line>
	{		{
Line 322:		Line 322:

	=== Numerical not equal rules for background color ===		=== Numerical not equal rules for background color ===
	If cell content is not 5, background color is #00FF00~~, and other~~ cells have background color #FFFF00.		If cell content is not 5, background color is #00FF00. Other cells have background color #FFFF00.
	<syntaxhighlight lang="json" line>		<syntaxhighlight lang="json" line>
	{		{
Line 341:		Line 341:

	=== Boolean equal rules for background color ===		=== Boolean equal rules for background color ===
	If cell content is "true", background color is #00FF00~~, if~~ cell content is "false", background color is #FF0000~~, and other~~ cells have background color #FFFF00.		If cell content is "true", background color is #00FF00. If cell content is "false", background color is #FF0000. Other cells have background color #FFFF00.
	<syntaxhighlight lang="json" line>		<syntaxhighlight lang="json" line>
	{		{
Line 395:		Line 395:

	=== Textual equal rules based on value in other column ===		=== Textual equal rules based on value in other column ===
	If cell content in dimension index 1 is "Delivery", background color is #00FF00~~, and other~~ cells have background color #FFFF00. Note that this conditional formatting results in same colors in all columns because the conditional formatting is not referring to the column itself.		If cell content in dimension index 1 is "Delivery", background color is #00FF00. Other cells have background color #FFFF00. Note that this conditional formatting results in same colors in all columns because the conditional formatting is not referring to the column itself.
	<syntaxhighlight lang="json" line>		<syntaxhighlight lang="json" line>
	{		{
Line 418:		Line 418:

	=== Textual equal rules for icons with colors ===		=== Textual equal rules for icons with colors ===
	If cell content is "Delivery", icon is "arrow_upward" with ~~icon~~ color is #FF0000~~, and other~~ cells icon is "arrow_downward" with ~~icon~~ color is #00FF00.		If cell content is "Delivery", icon is "arrow_upward" with color is #FF0000. Other cells icon is "arrow_downward" with color is #00FF00.
	<syntaxhighlight lang="json" line>		<syntaxhighlight lang="json" line>
	{		{