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:04] – [Mandatory Manual Upgrade Steps] twn | 73:releasenotes [2019/03/21 21:28] – 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 roles or tools. 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 ===== | + | {{ : |
- | 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 enable on-demand integration, |
- | ===== Popular Process Elements ===== | + | [[: |
- | Popular | + | For already added modules, you can change this behavior via the context menu of a module in '' |
+ | |||
+ | {{ : | ||
+ | |||
+ | To associate a process | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | When selecting the element, it will be integrated into your local process and associated with your current process element. | ||
+ | |||
+ | If you do not know the name of the element, use the '' | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | Then select the elements you want to associate. The elements will then be integrated into your local process and associated with your current process element. | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | When the common element pool is being updated to a newer version, use the existing process version management capabilities to also upgrade the integrated elements in your workspace. | ||
+ | |||
+ | ===== Direct Download of Templates, Checklists, and other Guidance Material ===== | ||
+ | |||
+ | 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. | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | 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. | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | The Jira item can contain the following information: | ||
+ | |||
+ | * Name and user ID of the user that initiated the feedback | ||
+ | * Summary | ||
+ | * Description | ||
+ | * Name of the workspace | ||
+ | * Link back to the process content where the feedback was initiated from | ||
+ | |||
+ | Details: [[: | ||
+ | |||
+ | ===== Integration with Sharepoint ===== | ||
+ | |||
+ | Stages 7.3 also contains an improved integration with Sharepoint. The following Sharepoint versions are supported: | ||
+ | |||
+ | * Sharepoint 2010 | ||
+ | * Sharepoint 2013 | ||
+ | * Sharepoint 2016 | ||
+ | * Sharepoint 2019 | ||
+ | |||
+ | TODO: See the Documentation how to enable it. | ||
+ | |||
+ | An integration with Sharepoint Online (Sharepoint 365) is planned for version 7.4. | ||
+ | |||
===== Workspace Attributes ===== | ===== Workspace Attributes ===== | ||
- | Classifying workspaces, e.g. for projects, products, product lines, etc. | + | Workspaces can now have specific attributes. Administrators can globally define possible attributes via the '' |
- | ===== Admin Jobs ===== | + | {{ : |
- | Automating role assignments, data export, | + | Attributes can be of type string or selection. Here is an example of how to define a selection and its possible values: |
+ | |||
+ | {{ : | ||
+ | |||
+ | After defining the attributes, they can be used in individual workspaces. To set an attribute to a specific value for a workspace, use the '' | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | In Stages 7.3, the workspace attributes can be used in scripts, e.g. to select only a specific set of workspaces: | ||
+ | |||
+ | < | ||
+ | var workspace = stages.getProjectByPath(workspacePath); | ||
+ | var modelYearAttribute = workspace.getAttribute(" | ||
+ | var modelYearAttributeValue = modelYearAttribute.getProperty(" | ||
+ | |||
+ | if (modelYearAttributeValue == " | ||
+ | ... | ||
+ | } | ||
+ | </ | ||
+ | |||
+ | Future versions of Stages will make use of those attributes to allow end users to easier find their workspaces. | ||
+ | |||
+ | ===== Administrative Jobs ===== | ||
+ | |||
+ | Role assignments or data exports can now be automated with the new jobs capability. Administrators can upload scripts via the '' | ||
+ | |||
+ | The existing Facade API can be used to navigate through the process content. For example, to assign a user named **'' | ||
+ | |||
+ | < | ||
+ | var user = stages.getUserByUsername(userName); | ||
+ | var project = stages.getProjectByPath(workspacePath); | ||
+ | if (user != null && project != null) { | ||
+ | var roles = project.getEntities(" | ||
+ | for (var i = 0; i < | ||
+ | var role = roles[i]; | ||
+ | if (role.getProperty(" | ||
+ | commands.execute(commands.newAssignUserCommand(role, | ||
+ | } | ||
+ | } | ||
+ | } | ||
+ | </ | ||
+ | |||
+ | Sample scripts can be downloaded here: | ||
+ | |||
+ | * [[: | ||
+ | * [[: | ||
+ | |||
+ | Please note, that these scripts are just samples and __need to be adjusted__ | ||
+ | |||
+ | We plan to expand the API in future Stages versions to also perform other administrative tasks. | ||
===== 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. |
+ | |||
+ | Administrators can now put Stages into maintenance mode via the '' | ||
+ | |||
+ | Configuration variable properties can now be managed in the '' | ||
===== Mandatory Manual Upgrade Steps ===== | ===== Mandatory Manual Upgrade Steps ===== | ||
- | | + | ==== Remove outdated stages-cms implementations ==== |
- | - | + | |
+ | Remove existing stages-cms-*.jar files from folders: < | ||
+ | |||
+ | ==== Adapt the server.xml ==== | ||
The Resources definition in "< | The Resources definition in "< | ||
Line 55: | Line 188: | ||
<Context path="/ | <Context path="/ | ||
[...] | [...] | ||
- | | + | < |
[...] | [...] | ||
</ | </ | ||
Line 65: | Line 198: | ||
<Context path="/ | <Context path="/ | ||
[...] | [...] | ||
- | | + | < |
< | < | ||
base=" | base=" | ||
- | | + | < |
+ | base=" | ||
+ | | ||
[...] | [...] | ||
</ | </ |