Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
v7migrate:reports [2018/08/29 04:28] – [How to migrate reports] emrv7migrate:reports [2024/02/15 00:00] (current) – external edit 127.0.0.1
Line 1: Line 1:
-[[:7migrate:start|]]+====== Precondition ====== 
 + 
 +Whether you are migrating from V6 or V7.1, the process metamodel definition has been changed. Please [[:7migrate:metamodel|see here]] for more info on how to migrate your existing metamodel to V7.2.
  
 ====== How to migrate reports ====== ====== How to migrate reports ======
Line 5: Line 7:
 The reporting system has been simplified in V7. To migrate an existing report to V7, the following steps should be taken The reporting system has been simplified in V7. To migrate an existing report to V7, the following steps should be taken
  
-  * The Report Designer version 7.2.0 should be used. It is based on BIRT Report Designer 4.4.2. +  * The Report Designer [[https://www.methodpark.de/downloads/stages/birt/Birt_RCP_Designer_7.2.0.zip|version 7.2.0]] should be used. It is based on BIRT Report Designer 4.4.2. 
-  * The ''<font inherit/Courier New,Courier,monospace;;inherit;;inherit>PkitMetrics.xml</font>''  and the related "beforeOpen" scripts are not required anymore. To remove them, follow these steps for every Data Source in your report:+  * The ''PkitMetrics.xml''  and the related "beforeOpen" scripts are no longer required. To remove them, follow these steps for every Data Source in your report:
       * Click on the Data Source       * Click on the Data Source
       * Open the "Script" tab in the main edit window       * Open the "Script" tab in the main edit window
Line 13: Line 15:
       * Double click on the Data Source to open the "Edit Data Source" window       * Double click on the Data Source to open the "Edit Data Source" window
       * In the "Stages Data Source" selection, make sure that the "User Name" and "Password" fields are empty if you are NOT using the Report Designer preview. If you are using the preview, add your own user name and password in those fields.       * In the "Stages Data Source" selection, make sure that the "User Name" and "Password" fields are empty if you are NOT using the Report Designer preview. If you are using the preview, add your own user name and password in those fields.
- 
  
 ====== How to use new V7 scripting capabilities ====== ====== How to use new V7 scripting capabilities ======
Line 21: Line 22:
 === Guidance and Resources === === Guidance and Resources ===
  
-The newly introduced **Guidance **elements can be accessed via the new ''containsGuidance@SYSTEM'' and ''containsGuidanceIndex@SYSTEM'' entities, similar to ''containsActivity@SYSTEM'' or ''containsActivityIndex@SYSTEM''. As Guidance replaced Resources, ''containsResource@SYSTEM'' and ''containsResourceIndex@SYSTEM'' entities now returns empty lists.+The newly introduced **Guidance **elements can be accessed via the new ''containsGuidance@SYSTEM''  and ''containsGuidanceIndex@SYSTEM''  entities, similar to ''containsActivity@SYSTEM''  or ''containsActivityIndex@SYSTEM''. As Guidance replaced Resources, ''containsResource@SYSTEM''  and ''containsResourceIndex@SYSTEM''  entities now returns empty lists. 
 === Tailoring === === Tailoring ===
  
 Tailoring Questions and Answers can now be accessed via this data model:{{:v7migrate:tailoring_facade.png?nolink&863x1160}} Tailoring Questions and Answers can now be accessed via this data model:{{:v7migrate:tailoring_facade.png?nolink&863x1160}}
- 
-{{:v7migrate:tailoring_facade.png?nolink&863x1160}} 
  
 === Compliance === === Compliance ===
  
-As private compliance scopes are not supported anymore, the ''containsPrivateScope@SYSTEM'' entity now always returns an empty list.+As private compliance scopes are not supported anymore, the ''containsPrivateScope@SYSTEM''  entity now always returns an empty list. 
 === Permissions === === Permissions ===
  
-Reports are now always executed with the permissions of the current user. The ''asCurrentUser.run(…)'' script statement is not required anymore and can be removed. If left in the script, it has no effect anymore.+Reports are now always executed with the permissions of the current user. The ''asCurrentUser.run(…)''  script statement is not required anymore and can be removed. If left in the script, it has no effect anymore. 
 === General === === General ===
  
-The ''pkit'' variable has been superseded by the ''stages'' or ''$s'' variable, but the ''pkit'' variable still exists and works as previously defined.+The ''pkit''  variable has been superseded by the ''stages''  or ''$s''  variable, but the ''pkit''  variable still exists and works as previously defined.
  
-A new API call ''stages.getCurrentProcess()'' has been added as a shortcut for the existing ''pkit.getCurrentProject().getEntities("containsProcess@SYSTEM")[0]'' call sequence.+A new API call ''stages.getCurrentProcess()''  has been added as a shortcut for the existing ''pkit.getCurrentProject().getEntities("containsProcess@SYSTEM")[0]''  call sequence.