This is an old revision of the document!
Release Notes for Stages V7.4
Stages version 7.4 adds the capability to maintain processes in multiple languages, allows end users to see changes between process versions directly in the models, and has many more user experience enhancements.
Multilingual Processes
…
Show Process Changes
End User is being notified of new process version
Can start compare mode
Compare Process Versions
…
Valid Process Version History
…
New process elements are sorted by creation time
…
Use description templates
…
Jump to headings in descriptions
…
Create new files from templates
…
User experience enhancements
Navigation can be folded
Descriptions can be folded
Tabs are better visible
Colors have been optimized for better readability.
New search result layout.
Multilevel Selection for Tailoring Dependencies
Integration with Sharepoint Online
…
Other 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.
New 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 allow these operations. Experienced project managers can now be empowered to perform the full process lifecycle without the help of users with Modeling licenses: select process modules, tailor the processes through the tailoring assistant, perform manual tailoring optimizations, create a process versions, and release it as valid for the process participants in that project.
Users with Viewer licenses can now also see compliance mappings. To enable, add a read permission with domain “Compliance” to the respective user group.
New Permission Domains
None
Mandatory Manual Upgrade Steps for Version 7.4
These actions need to be executed after upgrading to Stages 7.4 from previous Stages 7 versions:
Known Issues
Multilingual Processes
When a monolingual workspace is made multilingual, the workspace language shall be set to the current language of the process content. Otherwise original element descriptions could be accidently overwritten on editing if element descriptions are edited in the new workspace language.