Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revision | Next revisionBoth sides next revision | ||
| 73:releasenotes [2020/04/14 11:16] – [Adapt the server.xml] vtbr | 73: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. | ||
| - | {{ : | + | [[https:// |
| 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. | ||
| - | {{ : | + | [[https:// |
| 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. | ||
| - | {{ : | + | [[https:// |
| 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 63: | 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. | ||
| - | {{ : | + | [[https:// |
| 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 88: | 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. | ||
| - | {{ : | + | [[https:// |
| 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 130: | Line 130: | ||
| ==== Adapt the server.xml ==== | ==== Adapt the server.xml ==== | ||
| - | The Resources definition in "< | + | The Resources definition in "< |
| - | < | ||
| <Context path="/ | <Context path="/ | ||
| [...] | [...] | ||
| Line 157: | Line 156: | ||
| </ | </ | ||
| - | + | To be safe in case of any crashes/ | |
| - | To be safe in case of any crashes/ | + | * Stop the Stages service |
| - | + | ||
| - | * Stop the Stages service | + | |
| * Execute the update script: | * Execute the update script: | ||
| * Windows: " | * Windows: " | ||
| * Linux: " | * Linux: " | ||
| * Restart the Stages service | * Restart the Stages service | ||
| - | |||
| ==== URLs must contain the correct protocol ==== | ==== URLs must contain the correct protocol ==== | ||