QPR Impact Analysis - Revision history

Kju: /* Configuration of Reports */

2023-01-12T08:08:52Z

Configuration of Reports

Kju: /* Reporting platform installation */

2023-01-12T08:05:15Z

Reporting platform installation

Kju: 2019 -> 2022

2022-03-08T14:36:16Z

2019 -> 2022

TeeSiip: /* Reporting platform installation */

2019-07-22T10:59:12Z

Reporting platform installation

TeeSiip at 10:58, 22 July 2019

2019-07-22T10:58:47Z

MikkKorp: /* Configuration of Reports */

2019-07-10T11:52:43Z

Configuration of Reports

MikkKorp: /* Reporting platform installation */

2019-07-09T12:27:40Z

Reporting platform installation

MikkKorp: /* Purpose of the Reporting Feature */

2019-07-09T11:36:02Z

Purpose of the Reporting Feature

MikkKorp: /* Purpose of the Reporting Feature */

2019-07-09T11:34:02Z

Purpose of the Reporting Feature

MikkKorp at 11:28, 9 July 2019

2019-07-09T11:28:37Z

@@ Line 98: / Line 98: @@
 |}
-When using gap analysis, both left and right side models must be included in the report. In addition, note that the gap analysis only compares connections between the first and last node, and it doesn’t take into account any differences in the middle of the path. Also, the gap analysis doesn’t show any differences when properties of elements have been changes (e.g. element name), only connections between elements matter. For comparing changes in element attributes, use the '''''Model comparison''''' function ([http://kb.qpr.com/qpr2019-1/model_comparison.htm http://kb.qpr.com/qpr2022-1/model_comparison.htm]).
+When using gap analysis, both left and right side models must be included in the report. In addition, note that the gap analysis only compares connections between the first and last node, and it doesn’t take into account any differences in the middle of the path. Also, the gap analysis doesn’t show any differences when properties of elements have been changes (e.g. element name), only connections between elements matter. For comparing changes in element attributes, use the '''''Model comparison''''' function ([http://kb.qpr.com/qpr2023-1/model_comparison.htm http://kb.qpr.com/qpr2023-1/model_comparison.htm]).
@@ Line 108: / Line 108: @@
 |'''elementTypes''' (string array) ||List of element types which belong to the node. Asterix (*) refers to all element types.
 |-
-|'''filter''' (string) ||Condition to filter out elements. Filtered elements are not used in the report as part of the paths. Filtering condition syntax is same as the criteria parameter in QPR Web Service QueryObjects operation: [http://kb.qpr.com/qpr2019-1/index.html?queryobjects.htm http://kb.qpr.com/qpr2022-1/index.html?queryobjects.htm]
+|'''filter''' (string) ||Condition to filter out elements. Filtered elements are not used in the report as part of the paths. Filtering condition syntax is same as the criteria parameter in QPR Web Service QueryObjects operation: [http://kb.qpr.com/qpr2023-1/index.html?queryobjects.htm http://kb.qpr.com/qpr2023-1/index.html?queryobjects.htm]
 |-
 |'''instance''' (boolean)||Determines whether elements or element instances are used in the node.
@@ Line 128: / Line 128: @@
 !Report attributes (only defined for the first path)
 |-
-|'''attributes''' (string array)||Element attributes visible in the report. The attributes are defined as QPR Web Service attributes. A list of all attributes: [http://kb.qpr.com/qpr2019-1/index.html?supported_parameters.htm http://kb.qpr.com/qpr2022-1/index.html?supported_parameters.htm]
+|'''attributes''' (string array)||Element attributes visible in the report. The attributes are defined as QPR Web Service attributes. A list of all attributes: [http://kb.qpr.com/qpr2023-1/index.html?supported_parameters.htm http://kb.qpr.com/qpr2023-1/index.html?supported_parameters.htm]
 It is also possible to use an attribute syntax relationName#attributeName, for example parentobjects#name. This syntax will first make a parentobjects query and then returns name attribute for that object.
 |-

@@ Line 20: / Line 20: @@
 # Take backup copies of your existing templates and web content
-# Download the QPR Portal Add-on feature package for your version of QPR Suite here: https://devnet.onqpr.com/pawiki/index.php/QPR_Product_Downloads#QPR_Suite
+# Download the QPR Portal Add-on feature package for your version of QPR Suite here: [[QPR_Product_Downloads|QPR Products Downloads]]
-# Copy the contents of the '''Templates''' folder to the '''WAS''' subfolder in your templates folder of your instance, e.g. '''C:\ProgramData\QPR Software\QPR 2022\2022.1\Servers\Templates\WAS\'''
+# Copy the contents of the '''Templates''' folder to the '''WAS''' subfolder in your templates folder of your instance, e.g. '''C:\ProgramData\QPR Software\QPR 2023\2023.1\Servers\Templates\WAS\'''
-# Copy the contents of the '''Web server''' folder to '''qprsoftware''' folder under the web content root folder, e.g. '''C:\inetpub\wwwroot\qpr2022-1\qprsoftware\'''
+# Copy the contents of the '''Web server''' folder to '''qprsoftware''' folder under the web content root folder, e.g. '''C:\inetpub\wwwroot\qpr2023-1\qprsoftware\'''
 # Save the file model '''QPR ODM – Impact Analysis Support.qpream''' as a QPR server model (for a global configuration model or as an example for reports configurations)
 # In '''impactanalysis.tpl''' configure the variables

@@ Line 21: / Line 21: @@
 # Take backup copies of your existing templates and web content
 # Download the QPR Portal Add-on feature package for your version of QPR Suite here: https://devnet.onqpr.com/pawiki/index.php/QPR_Product_Downloads#QPR_Suite
-# Copy the contents of the '''Templates''' folder to the '''WAS''' subfolder in your templates folder of your instance, e.g. '''C:\ProgramData\QPR Software\QPR 2019\2019.1\Servers\Templates\WAS\'''
+# Copy the contents of the '''Templates''' folder to the '''WAS''' subfolder in your templates folder of your instance, e.g. '''C:\ProgramData\QPR Software\QPR 2022\2022.1\Servers\Templates\WAS\'''
-# Copy the contents of the '''Web server''' folder to '''qprsoftware''' folder under the web content root folder, e.g. '''C:\inetpub\wwwroot\qpr2019-1\qprsoftware\'''
+# Copy the contents of the '''Web server''' folder to '''qprsoftware''' folder under the web content root folder, e.g. '''C:\inetpub\wwwroot\qpr2022-1\qprsoftware\'''
 # Save the file model '''QPR ODM – Impact Analysis Support.qpream''' as a QPR server model (for a global configuration model or as an example for reports configurations)
 # In '''impactanalysis.tpl''' configure the variables
@@ Line 98: / Line 98: @@
 |}
-When using gap analysis, both left and right side models must be included in the report. In addition, note that the gap analysis only compares connections between the first and last node, and it doesn’t take into account any differences in the middle of the path. Also, the gap analysis doesn’t show any differences when properties of elements have been changes (e.g. element name), only connections between elements matter. For comparing changes in element attributes, use the '''''Model comparison''''' function (http://kb.qpr.com/qpr2019-1/model_comparison.htm).
+When using gap analysis, both left and right side models must be included in the report. In addition, note that the gap analysis only compares connections between the first and last node, and it doesn’t take into account any differences in the middle of the path. Also, the gap analysis doesn’t show any differences when properties of elements have been changes (e.g. element name), only connections between elements matter. For comparing changes in element attributes, use the '''''Model comparison''''' function ([http://kb.qpr.com/qpr2019-1/model_comparison.htm http://kb.qpr.com/qpr2022-1/model_comparison.htm]).
@@ Line 108: / Line 108: @@
 |'''elementTypes''' (string array) ||List of element types which belong to the node. Asterix (*) refers to all element types.
 |-
-|'''filter''' (string) ||Condition to filter out elements. Filtered elements are not used in the report as part of the paths. Filtering condition syntax is same as the criteria parameter in QPR Web Service QueryObjects operation: http://kb.qpr.com/qpr2019-1/index.html?queryobjects.htm
+|'''filter''' (string) ||Condition to filter out elements. Filtered elements are not used in the report as part of the paths. Filtering condition syntax is same as the criteria parameter in QPR Web Service QueryObjects operation: [http://kb.qpr.com/qpr2019-1/index.html?queryobjects.htm http://kb.qpr.com/qpr2022-1/index.html?queryobjects.htm]
 |-
 |'''instance''' (boolean)||Determines whether elements or element instances are used in the node.
@@ Line 128: / Line 128: @@
 !Report attributes (only defined for the first path)
 |-
-|'''attributes''' (string array)||Element attributes visible in the report. The attributes are defined as QPR Web Service attributes. A list of all attributes: http://kb.qpr.com/qpr2019-1/index.html?supported_parameters.htm
+|'''attributes''' (string array)||Element attributes visible in the report. The attributes are defined as QPR Web Service attributes. A list of all attributes: [http://kb.qpr.com/qpr2019-1/index.html?supported_parameters.htm http://kb.qpr.com/qpr2022-1/index.html?supported_parameters.htm]
 It is also possible to use an attribute syntax relationName#attributeName, for example parentobjects#name. This syntax will first make a parentobjects query and then returns name attribute for that object.
 |-

@@ Line 20: / Line 20: @@
 # Take backup copies of your existing templates and web content
-# Download the QPR Portal Add-in feature package for your version of QPR Suite here: https://devnet.onqpr.com/pawiki/index.php/QPR_Product_Downloads#QPR_Suite
+# Download the QPR Portal Add-on feature package for your version of QPR Suite here: https://devnet.onqpr.com/pawiki/index.php/QPR_Product_Downloads#QPR_Suite
 # Copy the contents of the '''Templates''' folder to the '''WAS''' subfolder in your templates folder of your instance, e.g. '''C:\ProgramData\QPR Software\QPR 2019\2019.1\Servers\Templates\WAS\'''
 # Copy the contents of the '''Web server''' folder to '''qprsoftware''' folder under the web content root folder, e.g. '''C:\inetpub\wwwroot\qpr2019-1\qprsoftware\'''

@@ Line 20: / Line 20: @@
 # Take backup copies of your existing templates and web content
-# Downloand installation package from here: https://community.qpr.com/node/2409
+# Download the QPR Portal Add-in feature package for your version of QPR Suite here: https://devnet.onqpr.com/pawiki/index.php/QPR_Product_Downloads#QPR_Suite
 # Copy the contents of the '''Templates''' folder to the '''WAS''' subfolder in your templates folder of your instance, e.g. '''C:\ProgramData\QPR Software\QPR 2019\2019.1\Servers\Templates\WAS\'''
 # Copy the contents of the '''Web server''' folder to '''qprsoftware''' folder under the web content root folder, e.g. '''C:\inetpub\wwwroot\qpr2019-1\qprsoftware\'''

@@ Line 19: / Line 19: @@
 Follow the installation instruction below. Instructions may need to be adjusted depending on the installation environment.
-# Take backup copies of your existing templates and web content.
+# Take backup copies of your existing templates and web content
-# Downloand installation package from here: https://community.qpr.com/node/2409.
+# Downloand installation package from here: https://community.qpr.com/node/2409
-# Copy the contents of the '''Templates''' folder to the '''WAS''' subfolder in your templates folder of your instance, e.g. '''C:\ProgramData\QPR Software\QPR 2019\2019.1\Servers\Templates\WAS\'''.
+# Copy the contents of the '''Templates''' folder to the '''WAS''' subfolder in your templates folder of your instance, e.g. '''C:\ProgramData\QPR Software\QPR 2019\2019.1\Servers\Templates\WAS\'''
-# Copy the contents of the '''Web server''' folder to '''qprsoftware''' folder under the web content root folder, e.g. '''C:\inetpub\wwwroot\qpr2019-1\qprsoftware\'''.
+# Copy the contents of the '''Web server''' folder to '''qprsoftware''' folder under the web content root folder, e.g. '''C:\inetpub\wwwroot\qpr2019-1\qprsoftware\'''
-# Save the file model '''QPR ODM – Impact Analysis Support.qpream''' as a QPR server model. (for a global configuration model or as an example for reports configurations)
+# Save the file model '''QPR ODM – Impact Analysis Support.qpream''' as a QPR server model (for a global configuration model or as an example for reports configurations)
 # In '''impactanalysis.tpl''' configure the variables
 #* USE_GLOBAL_CONFIGURATION_MODEL (is there one configuration model for the whole system)
@@ Line 30: / Line 30: @@
 #* OUTPUT_DATE_FORMAT (date format for representing dates in the report)
 #* NUMBER_FORMAT_LOCALE (locale for formatting numeric values; available locales http://code.google.com/p/jquery-numberformatter)
-# Restart QPR service or clear WAS template cache.
+# Restart QPR service or clear WAS template cache
 ==Configuration of Reports==

@@ Line 14: / Line 14: @@
 Variable '''''USE_GLOBAL_CONFIGURATION_MODEL''''' determines the used configuration strategy (see [[QPR_Impact_Analysis#Reporting platform installation|Reporting platform installation]]).
-Impact Analysis also supports gap analysis. The gap analysis compares two Impact Analysis reports and displays differences between them, i.e. which connections have been deleted and which are new.
+Impact Analysis also supports <u>gap analysis</u>. The gap analysis compares two Impact Analysis reports and displays differences between them, i.e. which connections have been deleted and which are new.
 == Reporting platform installation ==

@@ Line 13: / Line 13: @@
 *	'''''Local configuration model''''': The configuration is read from the model itself which is currently open. Alternatively the configuration model can be supplied as a parameter to the report.
-Variable '''''USE_GLOBAL_CONFIGURATION_MODEL''''' determines the used configuration strategy (see next chapter).
+Variable '''''USE_GLOBAL_CONFIGURATION_MODEL''''' determines the used configuration strategy (see [[QPR_Impact_Analysis#Reporting platform installation|Reporting platform installation]]).
 Impact Analysis also supports gap analysis. The gap analysis compares two Impact Analysis reports and displays differences between them, i.e. which connections have been deleted and which are new.