Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
74:releasenotes [2019/10/16 20:14] – emr | 74:releasenotes [2019/10/24 18:47] – emr | ||
---|---|---|---|
Line 1: | Line 1: | ||
====== Release Notes for Stages V7.4 ====== | ====== Release Notes for Stages V7.4 ====== | ||
- | Stages | + | More and more organizations develop products across different locations and time zones in international teams using several languages. To enable seamless communication, |
+ | |||
+ | The new version also allows end users to see changes between process versions directly in the models and has many more user experience enhancements | ||
+ | |||
+ | The major highlight for process users is certainly the [[: | ||
===== Multilingual Processes ===== | ===== Multilingual Processes ===== | ||
- | … | + | With the new version, Stages can manage the same process in different languages in a single model. |
+ | |||
+ | Process content can be translated directly in Stages or can be exported and re-imported for automatic translation. | ||
+ | |||
+ | The processes are then displayed in the language the users have selected in their profiles. Content that is not yet translated to the desired language will be displayed in the workspace default language. This also applies to seach results. This allows to translate a process step by step. | ||
===== Show Process Changes ===== | ===== Show Process Changes ===== | ||
Line 15: | Line 23: | ||
===== Compare Process Versions ===== | ===== Compare Process Versions ===== | ||
- | … | + | " |
+ | |||
+ | Select other version and/or workspace | ||
+ | |||
+ | Versions need to be derived from each other | ||
+ | |||
+ | Changes are calculated on first comparison and then stored, unless one of the version is a Working Version | ||
===== Valid Process Version History ===== | ===== Valid Process Version History ===== | ||
+ | |||
+ | " | ||
+ | |||
+ | ===== Scroll like Google Maps ===== | ||
… | … | ||
Line 23: | Line 41: | ||
===== New process elements are sorted by creation time ===== | ===== New process elements are sorted by creation time ===== | ||
- | … | + | Newly created process elements are now sorted by their creation time and not alphabetically. This removes the need to manually sort phases, milestones, or activities after creating them, because those are typically ordered on a time basis. |
+ | TODO: screenshot | ||
+ | |||
+ | Sorting elements alphabetically is still supported via the '' | ||
===== Use description templates ===== | ===== Use description templates ===== | ||
- | … | + | Descriptions for processes, roles, or metrics typically should follow a certain structure. For example, a role description should contain the necessary skills and authorities that a person fulfilling the role needs to possess. |
+ | |||
+ | To make it easier to follow this structure, description templates can now be defined via '' | ||
+ | |||
+ | TODO: screenshot | ||
+ | |||
+ | If you are using a process architecture with a common process module like " | ||
===== Jump to headings in descriptions ===== | ===== Jump to headings in descriptions ===== | ||
- | … | + | Process modellers can set links to headings and other parts of descriptions. In this way process viewers can jump quickly to the currently needed parts of the information. |
===== Create new files from templates ===== | ===== Create new files from templates ===== | ||
- | … | + | New files can be created directly from linked templates. This reduces effort, especially for reappearing tasks (e.g. uploading review protocols). |
===== User experience enhancements ===== | ===== User experience enhancements ===== | ||
Line 53: | Line 80: | ||
===== Integration with Sharepoint Online ===== | ===== Integration with Sharepoint Online ===== | ||
- | … | + | Repositories for project work products, templates, checklists, and other files in Sharepoint Online can now also be directly used in Stages. |
+ | |||
+ | See [[: | ||
+ | |||
+ | ===== Jira Feedback now supports access via API gateways ===== | ||
+ | |||
+ | …spezielle Variante die Renault mit einem Api-Gateway benutzt. Konkret: OAuth 2.0 Password Grant. Das kann nämlich zu Verwechselungen kommen. Jira selber unterstützt nämlich neben Basic Auth nur eine OAuth 1.0 variante, sonst nichts. | ||
- | ===== Other Changes ===== | + | ===== Other Enhancements and Changes ===== |
Process elements belonging to a process module that are moved within a target workspace now remain in their new location when the process module is being updated. This way, the hierarchy of a process module can be adjusted in a target workspace. | Process elements belonging to a process module that are moved within a target workspace now remain in their new location when the process module is being updated. This way, the hierarchy of a process module can be adjusted in a target workspace. | ||
- | ===== New Privileges for Project Manager and Viewer License Types ===== | + | Compliance mappings of processes against one version of a reference model can now be automatically transferred to a newer reference model version by executing the '' |
+ | ===== Added Privileges for Project Manager and Viewer License Types ===== | ||
- | Users assigned to Project Manager licenses can now be allowed to create new process versions and release those versions as valid, if their permissions | + | Users assigned to Project Manager licenses can now be allowed to create new process versions and release those versions as valid. Of course, the access to those features is still only possible |
* Select process modules | * Select process modules | ||
Line 73: | Line 107: | ||
===== New Permission Domains ===== | ===== New Permission Domains ===== | ||
- | None | + | Feedback (Provide Feedback in JIRA) |
===== Mandatory Manual Upgrade Steps for Version 7.4 ===== | ===== Mandatory Manual Upgrade Steps for Version 7.4 ===== | ||
Line 79: | Line 113: | ||
These actions need to be executed after upgrading to Stages 7.4 from previous Stages 7 versions: | These actions need to be executed after upgrading to Stages 7.4 from previous Stages 7 versions: | ||
- | ===== Known Issues ===== | + | * Custom implementations of the '' |
+ | * Custom implementation of process validators / constraint checks may need to be adjusted and recompiled against this Stages version | ||
- | === Multilingual Processes | + | ===== Known Issues ===== |
When a monolingual workspace is made multilingual, | When a monolingual workspace is made multilingual, | ||