Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision |
75:releasenotes [2020/05/20 22:29] – emr | 75:releasenotes [2020/05/26 14:53] – emr |
---|
| |
To provide more insight into the process models several visualizations were enhanced. | To provide more insight into the process models several visualizations were enhanced. |
| |
| [[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=3ad5d7&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/statechart.png|{{ https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/statechart.png?direct&800x239 }}]] |
| |
A new States diagram for work products shows a state chart which contains all states of a work products, the activities performing the state transitions, and the responsible roles for those activities. | A new States diagram for work products shows a state chart which contains all states of a work products, the activities performing the state transitions, and the responsible roles for those activities. |
| |
[[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=3ad5d7&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/statechart.png|{{ https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/statechart.png?direct&800x239 }}]] | [[https://doc.stagesasaservice.com/lib/exe/fetch.php?tok=be90bf&media=https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/sipocwroles.png|{{ https://doc.stagesasaservice.com/lib/plugins/ckgedit/fckeditor/userfiles/image/75/sipocwroles.png?direct&700x352 }}]] |
| |
The activities in the role diagram can now be grouped by their respective workflow, which is useful if the diagram contains many activities. A new "Phases" switch was added to lay out the activities by phase, which provides more insight into the timing perspective. | The SIPOC table diagram has been enhanced with a new switch that shows all involved roles for each activity. All roles are marked with (R), (S), etc., to show the type of involvement in RASIC style. |
| |
The workflow grid diagram can now also be grouped by responsible role. | A new "Phases" switch in the role visualization can be used to layout the activities by phase, which provides more insight into the timing perspective of each role. |
| |
Various other improvements have been made to the standard configuration, e.g. a standard duration attribute has been added for activities, which can be used in the process export for project planning applications. | Finally, the activities in the workflow grid diagram can now also be grouped by responsible role via the new "Grouping" switch. |
| |
===== Support for Multiple Organizations on one Instance ===== | ===== Support for Multiple Organizations on one Instance ===== |
| |
* PTC Integrity Lifecycle Manager | * PTC Integrity Lifecycle Manager |
* IBM Rational Team Concert | * IBM Engineering Lifecycle Management (formerly know as Rational Team Concert) |
* Jira Cloud | * Jira Cloud |
* Redmine | * Redmine |
===== Administrative Changes ===== | ===== Administrative Changes ===== |
| |
Custom URL rewrite rules can be added to the ''rewrite.config'' by editing ''.../conf/rewrite-customer.config'' and executing ''update.bat'' or ''update.sh''. The custom rules will be added to the end of the generated ''rewrite.config''. If custom rules are needed at the beginning of the rewrite configuration, create a file named ''rewrite-prefix-customer.config'' in the conf directory. | Custom URL rewrite rules can be added to the ''rewrite.config'' by editing ''…/conf/rewrite-customer.config'' and executing ''update.bat'' or ''update.sh''. The custom rules will be added to the end of the generated ''rewrite.config''. If custom rules are needed at the beginning of the rewrite configuration, create a file named ''rewrite-prefix-customer.config'' in the conf directory. |
| |
The secure mode is enabled by default now. This means that certain security-relevant headers will be set in HTTP responses and the HTML plugin in the editor will not be shown. If you need to deactivate the secure mode, you can do this by adding the property ''global.secureMode.enabled'' with value "false" to config.xml. If you want the secure mode to be activated, but still want to use the HTML plugin, set the ''global.secureMode.allowHTMLPlugin'' property to "true". | The secure mode is enabled by default now. This means that certain security-relevant headers will be set in HTTP responses and the HTML plugin in the editor will not be shown. If you need to deactivate the secure mode, you can do this by adding the property ''global.secureMode.enabled'' with value "false" to config.xml. If you want the secure mode to be activated, but still want to use the HTML plugin, set the ''global.secureMode.allowHTMLPlugin'' property to "true". |
| |
The new ''mergeUserGroups'' commandline script merges user groups with identical permissions. Execute the script with -d option in order to perform a dry-run and use -h to show all other available options. | The new ''mergeUserGroups'' commandline script merges user groups with identical permissions. Execute the script with -d option in order to perform a dry-run and use -h to show all other available options. |
| |
Displaying the last login and login count of each user can be disabled via the ''administration.users.showLastLogin'' configuration property (default: true). | Displaying the last login and login count of each user can be disabled via the ''administration.users.showLastLogin'' configuration property (default: true). |
| |
Search for users within a user group is now available and various other improvements were made in the user-group-permission management. | Search for users within a user group is now available and various other improvements were made in the user-group-permission management. |
[[:75:mandatory_manual_upgrade_steps_for_version_75|See here]] for full details. | [[:75:mandatory_manual_upgrade_steps_for_version_75|See here]] for full details. |
| |
Also, if you have customized readiness checks (a.k.a. validators) in your metamodel, those might need to be recompiled for 7.5. | Also, if you have customized readiness checks (a.k.a. validators) in your metamodel, those might need to be recompiled for 7.5. If you use the Unified Configuration metamodel ask your product consultant for the newest version. |
| |
===== Notes ===== | ===== Notes ===== |