Differences

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

--- 72:msproject [2018/11/07 13:40] – emr
+++ 72:msproject [2024/02/15 00:00] (current) – external edit 127.0.0.1
@@ Line 11: / Line 11: @@
 To install the pre-defined scheme into your global MS Project preferences, follow these steps:
-  * Download a template MS Project plan that contains the scheme
+  * Download {{:72:stages-export-template.mpp|this template MS Project plan}}  (Do "Left Click > Save link as ...") that contains the scheme
   * Open this plan in MS Project
   * Go to ''File > Organizer''
@@ Line 22: / Line 22: @@
 Navigate to the workspace and process version you would like to export.
-The process data can be exported via the ''Project Planning''  report found here. In a typical Stages instance, this report is already installed as ''Reports > Exports > Project Planning''.
+The process data can be exported via the ''Project Planning'' report found [[http://www.methodpark.de/downloads/stages/Standard_Reports/ProjectPlanningExport.zip|here]]. In a typical Stages instance, this report is already installed as ''Reports > Exports > Project Planning''.
-{{  :72:msproject-report.png?direct&799x441  }}
+[[https://doc.stagesasaservice.com/lib/exe/fetch.php?media=72:msproject-report.png|{{  :72:msproject-report.png?direct&799x441  }}]]
-**<font inherit/inherit;;#ffffff;;#e74c3c>(1)</font>**  Select the processes you would like to export via the ''Processes to export''  parameter. You can select multiple processes by holding the CTRL or SHIFT keys during the selection.
+**(1)**  Select the processes you would like to export via the ''Processes to export'' parameter. You can select multiple processes by holding the CTRL or SHIFT keys during the selection.
-MS Project currently only supports importing one predecessor per task. As activities in Stages might have multiple predecessors, the import of those will result in an import error (which can also be simply ignored). With the ''Use only last predecessor''  option, you can control if all predecessors should be exported or only the last one.
+MS Project currently only supports importing one predecessor per task. As activities in Stages might have multiple predecessors, the import of those will result in an import error (which can also be simply ignored). With the ''Use only last predecessor'' option, you can control if all predecessors should be exported or only the last one.
-<font inherit/inherit;;#ffffff;;#e74c3c>**(2)**</font> Then run the report. If you do not need to see the exported data, this step can also be skipped.
+**(2)** Then run the report. If you do not need to see the exported data, this step can also be skipped.
+**(3)** Export the report results to MS Excel via the ''XLSX Export'' menu.
-<font inherit/inherit;;#ffffff;;#e74c3c>**(3)**</font> Export the report results to MS Excel via the ''XLSX Export''  menu.
 ===== Run the MS Project import =====
-Open MS Project and select ''New from Excel Sheet''. Switch from the "XML Format" to the "Excel Sheet" filter and select the XLSX file you generated with the Stages report.
+To import the process data into MS Project follow these steps:
+  * Open MS Project and select ''New from Excel Sheet''.
+  * Switch from the "XML Format" to the "Excel Sheet" filter and select the XLSX file you generated with the Stages report.
+  * Select either ''Use Existing Scheme''  if you have already set up the import scheme (see above) or ''New Scheme''  if you want to do the attribute mapping yourself.
+  * Select "Tasks" and "Import with headers" in the import assistant "schema options" page.
+  * Check the import preview. If necessary, adjust the attribute mappings and save the import scheme.
+  * If import errors occur, you can either click "Yes" to ignore all of them or use the ''Use only last predecessor''  option when running the Stages report.
+As a result, your imported process will show up in MS Project.
+{{  :72:msproject-result.png?direct&801x365  }}
+For example, you can see that
-Select either ''Use Existing Scheme''  if you have already set up the import scheme (see above) or ''New Scheme''  if you want to do the attribute mapping yourself.
+**(1)** All process activities are imported as tasks, including their hierarchy and order
-Select "Tasks" and "Import with headers" in the import assistant "schema options" page.
+**(2)**  The default duration is set to 1 day, but it can be also modeled in Stages as an attribute.
-Check the import preview. If necessary, adjust the attribute mappings and save the import scheme.
+**(3)** Predecessors and successors as well as input/output dependencies have been transferred
-If import errors occur, you can either click "Yes" to ignore all of them or use the ''Use only last predecessor''  option when running the Stages report.
+**(4)** There is a hyperlink from every task back to Stages
-Your imported process will show up in MS Project.
+With this capability, the project managers can start planning the tasks in MS Project and your users can use the hyperlink to directly start working on the activity. It is only once more click to access templates and checklists and even input and output work products, independently where they are stored.
 ===== Supported MS Project versions =====
@@ Line 54: / Line 68: @@
   * Microsoft Project 2016
-Please let us know when you were able to make it work also with other versions or tools, then we will add those to this list.
+It will surely work also with other MS Project versions. Please let us know when you were able to make it work also with other versions or tools, then we will add those to this list.