Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
73:releasenotes [2019/03/19 09:07] – [Mandatory Manual Upgrade Steps] twn | 73:releasenotes [2020/04/15 16:51] – emr | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Release Notes for Stages V7.3 ====== | ====== Release Notes for Stages V7.3 ====== | ||
- | Stages V7.3 comes with innovative features to support complex product development processes. Project and program processes can now be upgraded in flight. Already | + | 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 |
- | Modelers can design processes faster by using centralized element pools, for example for roles or tools. This improves process consistency and enables better | + | 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 |
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 9: | Line 9: | ||
===== Phase Freeze ===== | ===== Phase Freeze ===== | ||
- | Product Development Processes, etc. | + | 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. |
- | ===== Process Modules now allow on-demand integration ===== | + | [[https:// |
- | If you have a standard set of roles or tools you would like to use throughout all of your processes, | + | After the phase freeze, the processes |
- | ===== Direct Download of Templates, Checklists, etc. ===== | + | The phase freeze is controlled by scripts, so it can be adjusted also for customized process metamodels. |
- | Make templates, checklists, and other material directly available at activities, work products, or roles. | + | ===== On-demand Integration of Process Modules ===== |
- | ===== Workspace Tree Navigation ===== | + | A lot of organizations have a standard set of roles or tools that needs to be consistenly used in all processes. As these sets tend to grow large, Stages 7.3 now contains a on-demand integration capability, where only those elements are integrated that are actually being used in a workspace. |
- | … | + | 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. |
- | ===== Popular Process Elements ===== | + | [[https:// |
- | Popular | + | When selecting the element, it will be integrated into your local process |
+ | |||
+ | Details: [[: | ||
+ | |||
+ | ===== Direct Download | ||
+ | |||
+ | 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 new Unified Configuration 2.3 already uses the new capabilities to show direct downloads in the " | ||
+ | |||
+ | ===== Hierarchical Workspace Navigation ===== | ||
+ | |||
+ | Especially in more complex programs, product development processes are separated into multiple workspaces, e.g. one for system engineering and program management, one for hardware engineering, | ||
+ | |||
+ | {{youtube> | ||
+ | |||
+ | Clicking or tapping on ">" | ||
+ | |||
+ | To access a workspace by its name, click or tap on " | ||
+ | |||
+ | ===== Usage Statistics ===== | ||
+ | |||
+ | With version 7.3, most accessed process elements for each user are now shown on the landing page. This allows | ||
For process managers, more detailed access statistics are shown in the '' | For process managers, more detailed access statistics are shown in the '' | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | The statistics show popular process elements for the current or all workspaces, the most actively used workspaces, and a breakdown of process content accesses by element type. | ||
+ | |||
+ | ===== Process Feedback in Jira ===== | ||
+ | |||
+ | 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. | ||
+ | |||
+ | Details: [[: | ||
+ | |||
+ | ===== Integration with Sharepoint ===== | ||
+ | |||
+ | Stages 7.3 also contains an improved integration with Sharepoint, so you can manage project files, templates, checklists, and all other file-based guidance stored in Sharepoint directly from Stages. | ||
+ | |||
+ | The following Sharepoint versions are supported: | ||
+ | |||
+ | * Sharepoint 2010 | ||
+ | * Sharepoint 2013 | ||
+ | * Sharepoint 2016 | ||
+ | * Sharepoint 2019 | ||
+ | |||
+ | An integration with Sharepoint Online (Sharepoint 365) is planned for version 7.4. | ||
+ | |||
+ | Details: [[: | ||
+ | |||
===== Workspace Attributes ===== | ===== Workspace Attributes ===== | ||
- | Classifying | + | Workspaces can now have specific attributes that can be used in scripts to select specific |
- | ===== Admin Jobs ===== | + | [[https:// |
- | Automating role assignments, data export, etc. | + | Future versions of Stages will make use of those attributes to allow end users to easier find their workspaces. |
+ | |||
+ | Details: [[: | ||
+ | |||
+ | ===== Administrative Jobs ===== | ||
+ | |||
+ | Role assignments | ||
+ | |||
+ | We plan to expand the API in future Stages versions to also perform other administrative tasks. | ||
+ | |||
+ | Details: [[: | ||
===== Other Changes ===== | ===== Other Changes ===== | ||
- | A new link in the left side navigation now always points to the Stages online documentation. It can be configured to also point to customer-specific help content. | + | A new '' |
- | Processes can now also be copied. | + | Processes can now also be copied |
A ZIP file with exported process content can now be directly imported into an empty workspace. | A ZIP file with exported process content can now be directly imported into an empty workspace. | ||
- | Configuration variable properties can now be managed in the '' | + | Similar to users, permission groups are now also searchable by name. |
- | ===== Mandatory Manual Upgrade Steps ===== | + | |
+ | Administrators can now put Stages into maintenance mode via the '' | ||
+ | |||
+ | Configuration variable properties can now be managed in the '' | ||
+ | |||
+ | ===== New Permission Domains ===== | ||
+ | |||
+ | To manage access to the new features, [[: | ||
+ | |||
+ | ===== Mandatory Manual Upgrade Steps for Version 7.3 ===== | ||
+ | |||
+ | These actions need to be executed after upgrading to Stages 7.3 from previous Stages 7 versions. | ||
==== Remove outdated stages-cms implementations ==== | ==== Remove outdated stages-cms implementations ==== | ||
- | Remove existing | + | Remove existing |
==== Adapt the server.xml ==== | ==== Adapt the server.xml ==== | ||
- | The Resources definition in "< | + | The Resources definition in "< |
- | < | ||
<Context path="/ | <Context path="/ | ||
[...] | [...] | ||
- | | + | < |
[...] | [...] | ||
</ | </ | ||
+ | |||
</ | </ | ||
Line 68: | Line 145: | ||
<Context path="/ | <Context path="/ | ||
[...] | [...] | ||
- | | + | < |
< | < | ||
base=" | base=" | ||
- | | + | < |
+ | base=" | ||
+ | | ||
[...] | [...] | ||
</ | </ | ||
+ | |||
</ | </ | ||
+ | |||
+ | To be safe in case of any crashes/ | ||
+ | * Stop the Stages service | ||
+ | * Execute the update script: | ||
+ | * Windows: " | ||
+ | * Linux: " | ||
+ | * Restart the Stages service | ||
+ | |||
+ | ==== 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, " | ||