Stages Documentation

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
Next revisionBoth sides next revision
73:releasenotes [2019/04/04 11:17] – [Hierarchical Workspace Navigation] fnpk73:releasenotes [2020/04/15 16:51] – emr
Line 3: Line 3:
 Stages V7.3 comes with innovative features to support complex product development processes. Project and program processes can now be upgraded in flight, while already finished parts remain unchanged. This allows multi-year programs - typical for automotive or aerospace industries - to always use the latest development processes without changing their past. Stages V7.3 comes with innovative features to support complex product development processes. Project and program processes can now be upgraded in flight, while already finished parts remain unchanged. This allows multi-year programs - typical for automotive or aerospace industries - to always use the latest development processes without changing their past.
  
-Modelers can design processes faster by using centralized element pools, for example for roles or tools. This improves process consistency and enables better alignment across different business units.+Modelers can design processes faster by using centralized element pools, for example for tools or phases and milestones. This improves process consistency and enables better alignment across different business units.
  
 The new version also further improves process usability. Usage statistics provide valuable insights how processes are being used and lead the way into quantitative process improvement. The new version also further improves process usability. Usage statistics provide valuable insights how processes are being used and lead the way into quantitative process improvement.
Line 11: Line 11:
 Typical product development programs for vehicles, aircrafts, or medical devices run over multiple years. During that time, the product development process changes and improves. Of course, those improvements should be incorporated into the running programs without changing already executed phases and activities. For that purpose, Stages provides a new phase freeze capability. It allows process managers to freeze phases, activities, work products, etc., that have already concluded. For complex programs spanning multiple projects, the phase freeze can be executed consistently across all projects within one operation. Typical product development programs for vehicles, aircrafts, or medical devices run over multiple years. During that time, the product development process changes and improves. Of course, those improvements should be incorporated into the running programs without changing already executed phases and activities. For that purpose, Stages provides a new phase freeze capability. It allows process managers to freeze phases, activities, work products, etc., that have already concluded. For complex programs spanning multiple projects, the phase freeze can be executed consistently across all projects within one operation.
  
-{{  :73:phasefreeze-main.png?direct&800x450  }}+[[https://doc.stagesasaservice.com/lib/exe/fetch.php?media=73:phasefreeze-main.png|{{  :73:phasefreeze-main.png?direct&800x450  }}]]
  
 After the phase freeze, the processes can be upgraded to newer versions with the existing version management capabilities. When creating a new valid version for the program, the frozen process parts are merged with the upgraded processes in a consistent way. After the phase freeze, the processes can be upgraded to newer versions with the existing version management capabilities. When creating a new valid version for the program, the frozen process parts are merged with the upgraded processes in a consistent way.
Line 23: Line 23:
 To associate a process element with an element from a on-demand module, search for its name in the quick-assign dialog. In addition to the local elements, the search will now find also elements from the on-demand module. To associate a process element with an element from a on-demand module, search for its name in the quick-assign dialog. In addition to the local elements, the search will now find also elements from the on-demand module.
  
-{{  :73:ondemandmodules-quickassign.png?direct&400x322  }}+[[https://doc.stagesasaservice.com/lib/exe/fetch.php?media=73:ondemandmodules-quickassign.png|{{  :73:ondemandmodules-quickassign.png?direct&400x322  }}]]
  
 When selecting the element, it will be integrated into your local process and associated with your current process element. When selecting the element, it will be integrated into your local process and associated with your current process element.
Line 33: Line 33:
 To save users some clicks, it can be valuable to make templates, checklists, and other file-based guidance material directly downloadable from activity or work product pages. For example, an activity page can directly show all templates and checklists for all output work products of that activity. To save users some clicks, it can be valuable to make templates, checklists, and other file-based guidance material directly downloadable from activity or work product pages. For example, an activity page can directly show all templates and checklists for all output work products of that activity.
  
-{{  :73:directdownloads-activity.png?direct&800x473  }}+[[https://doc.stagesasaservice.com/lib/exe/fetch.php?media=73:directdownloads-activity.png|{{  :73:directdownloads-activity.png?direct&800x473  }}]]
  
 The same can be configured for work products, which can directly show download links for templates and checklists. The same can be configured for work products, which can directly show download links for templates and checklists.
Line 48: Line 48:
  
 To access a workspace by its name, click or tap on "Search" and start typing. All matching workspace candidates will be listed as you type. To access a workspace by its name, click or tap on "Search" and start typing. All matching workspace candidates will be listed as you type.
- 
  
 ===== Usage Statistics ===== ===== Usage Statistics =====
Line 64: Line 63:
 Users can now send feedback directly from the process content. Each feedback is automatically created as a Jira item, so you can efficiently track and process end user feedback. Users can now send feedback directly from the process content. Each feedback is automatically created as a Jira item, so you can efficiently track and process end user feedback.
  
-{{  :73:feedback-start.png?direct&700x333  }}+[[https://doc.stagesasaservice.com/lib/exe/fetch.php?media=73:feedback-start.png|{{  :73:feedback-start.png?direct&700x333  }}]]
  
 Among other data, the Jira item also contains a link back to the originating process element, so full traceability of process change requests is assured. Among other data, the Jira item also contains a link back to the originating process element, so full traceability of process change requests is assured.
Line 89: Line 88:
 Workspaces can now have specific attributes that can be used in scripts to select specific workspaces. This way you can distinguish different program types, target products, etc. Workspaces can now have specific attributes that can be used in scripts to select specific workspaces. This way you can distinguish different program types, target products, etc.
  
-{{  :73:workspaceattributes-selectattributes.png?direct&800x276  }}+[[https://doc.stagesasaservice.com/lib/exe/fetch.php?media=73:workspaceattributes-selectattributes.png|{{  :73:workspaceattributes-selectattributes.png?direct&800x276  }}]]
  
 Future versions of Stages will make use of those attributes to allow end users to easier find their workspaces. Future versions of Stages will make use of those attributes to allow end users to easier find their workspaces.
Line 113: Line 112:
 Similar to users, permission groups are now also searchable by name. Similar to users, permission groups are now also searchable by name.
  
-Administrators can now put Stages into maintenance mode via the ''Administration''  menu. In maintenance mode, no users except ''root''  can log into the system. Users that are currently logged on receive a warning message on their screen and an email. The maintenance mode is kept across service restarts until it is stopped by the administrator.+Administrators can now put Stages into maintenance mode via the ''Administration''  menu. In maintenance mode, no users except ''root''  can log into the system. Users that are currently logged on receive a warning message on their screen and an email. The maintenance mode is kept across service restarts until it is stopped by the administrator. Access to the maintenance mode feature can be controlled through the new ''Maintenance Mode''  permission domain.
  
 Configuration variable properties can now be managed in the ''conf/config.properties''  and ''conf/secret.properties''  files in Java property format and used in ''config.xml''  and other xml config files. The ''secret.properties''  is not contained in the pks runtime info, so it can be used to securely store passwords and other access credentials that should never leave an organization's network or the server. Configuration variable properties can now be managed in the ''conf/config.properties''  and ''conf/secret.properties''  files in Java property format and used in ''config.xml''  and other xml config files. The ''secret.properties''  is not contained in the pks runtime info, so it can be used to securely store passwords and other access credentials that should never leave an organization's network or the server.
Line 119: Line 118:
 ===== New Permission Domains ===== ===== New Permission Domains =====
  
-To manage access to the new features, [[:73:users_groups_permissions|several permission domains]] were added in Stages 7.3. You might want to add those permission to the respective user groups.+To manage access to the new features, [[:73:users_groups_permissions|several permission domains]] were added in Stages 7.3. You might want to add those permissions to the respective user groups.
  
 ===== Mandatory Manual Upgrade Steps for Version 7.3 ===== ===== Mandatory Manual Upgrade Steps for Version 7.3 =====
Line 131: Line 130:
 ==== Adapt the server.xml ==== ==== Adapt the server.xml ====
  
-The Resources definition in "<font inherit/Courier New,Courier,monospace;;inherit;;inherit>conf/server.xml</font>" has to be adjusted. The following Resources tag in server.xml+The Resources definition in "<font inherit/Courier New,Courier,monospace;;inherit;;inherit>conf/server.xml</font>" has to be adjusted. The following Resources tag in server.xml<code>
  
-<code> 
 <Context path="/stages" ...> <Context path="/stages" ...>
   [...]   [...]
Line 139: Line 137:
   [...]   [...]
 </Context> </Context>
 +
 </code> </code>
  
Line 154: Line 153:
   [...]   [...]
 </Context> </Context>
 +
 </code> </code>
  
-\\ +To be safe in case of any crashes/problems during the update, **back up your database**  (dump) and finally run the Stages update script:
-Finally run the Stages update script: +
   * Stop the Stages service   * Stop the Stages service
   * Execute the update script:   * Execute the update script:
Line 167: Line 165:
 ==== URLs must contain the correct protocol ==== ==== URLs must contain the correct protocol ====
  
-The protocol needs to be set explicitly for all URLs that have been entered without a protocol. For example, "www.methodpark.de" needs to be replaced with "http://www.methodpark.de". +The protocol needs to be set explicitly for all URLs that have been entered without a protocol. For example, "www.methodpark.de" needs to be replaced with "http://www.methodpark.de". Some changes for URLs attached to work products and Guidance elements: * URLs are now displayed in the Stages UI exactly like they have been entered, URLs that do not contain ":" will no longer be prefixed with "http:". * When accessing a URL, you simple click a link with that URL. The access will no longer be redirected to the actual URL by the Stages server. * This means that navigation to URLs will no longer be logged in the access log. For example, URLs will no longer appear in the "Recently Used Files" widget. * This makes "file:" URLs work (if they contain a host name after the "file:" part, and only in IE 11 and Edge). "file:" URLs with local folder names or drive letters are blocked by all current major browsers for security reasons. * This makes "mailto:" URLs work (issue 32942). //
- +
-Some changes for URLs attached to work products and Guidance elements: +
- +
-  * URLs are now displayed in the Stages UI exactly like they have been entered, URLs that do not contain ":" will no longer be prefixed with "http:". +
-  * When accessing a URL, you simple click a link with that URL. The access will no longer be redirected to the actual URL by the Stages server. +
-  * This means that navigation to URLs will no longer be logged in the access log. For example, URLs will no longer appear in the "Recently Used Files" widget. +
-  * This makes "file:" URLs work (if they contain a host name after the "file:" part, and only in IE 11 and Edge). "file:" URLs with local folder names or drive letters are blocked by all current major browsers for security reasons. +
-  * This makes "mailto:" URLs work (issue 32942).+