| Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision |
| 73:releasenotes [2019/04/04 11:17] – [Hierarchical Workspace Navigation] fnpk | 73:releasenotes [2020/04/14 11:16] – [Adapt the server.xml] vtbr |
|---|
| |
| To access a workspace by its name, click or tap on "Search" and start typing. All matching workspace candidates will be listed as you type. | To access a workspace by its name, click or tap on "Search" and start typing. All matching workspace candidates will be listed as you type. |
| |
| |
| ===== Usage Statistics ===== | ===== Usage Statistics ===== |
| Similar to users, permission groups are now also searchable by name. | Similar to users, permission groups are now also searchable by name. |
| |
| Administrators can now put Stages into maintenance mode via the ''Administration'' menu. In maintenance mode, no users except ''root'' can log into the system. Users that are currently logged on receive a warning message on their screen and an email. The maintenance mode is kept across service restarts until it is stopped by the administrator. | Administrators can now put Stages into maintenance mode via the ''Administration'' menu. In maintenance mode, no users except ''root'' can log into the system. Users that are currently logged on receive a warning message on their screen and an email. The maintenance mode is kept across service restarts until it is stopped by the administrator. Access to the maintenance mode feature can be controlled through the new ''Maintenance Mode'' permission domain. |
| |
| Configuration variable properties can now be managed in the ''conf/config.properties'' and ''conf/secret.properties'' files in Java property format and used in ''config.xml'' and other xml config files. The ''secret.properties'' is not contained in the pks runtime info, so it can be used to securely store passwords and other access credentials that should never leave an organization's network or the server. | Configuration variable properties can now be managed in the ''conf/config.properties'' and ''conf/secret.properties'' files in Java property format and used in ''config.xml'' and other xml config files. The ''secret.properties'' is not contained in the pks runtime info, so it can be used to securely store passwords and other access credentials that should never leave an organization's network or the server. |
| ===== New Permission Domains ===== | ===== New Permission Domains ===== |
| |
| To manage access to the new features, [[:73:users_groups_permissions|several permission domains]] were added in Stages 7.3. You might want to add those permission to the respective user groups. | To manage access to the new features, [[:73:users_groups_permissions|several permission domains]] were added in Stages 7.3. You might want to add those permissions to the respective user groups. |
| |
| ===== Mandatory Manual Upgrade Steps for Version 7.3 ===== | ===== Mandatory Manual Upgrade Steps for Version 7.3 ===== |
| [...] | [...] |
| </Context> | </Context> |
| | |
| </code> | </code> |
| |
| [...] | [...] |
| </Context> | </Context> |
| | |
| </code> | </code> |
| |
| \\ | |
| Finally run the Stages update script: | |
| |
| * Stop the Stages service | To be safe in case of any crashes/problems during the update, **back up your database** (dump) and finally run the Stages update script: |
| | |
| | * Stop the Stages service |
| * Execute the update script: | * Execute the update script: |
| * Windows: "…<font inherit/Courier New,Courier,monospace;;inherit;;inherit>\stages\bin\update.bat</font>" | * Windows: "…<font inherit/Courier New,Courier,monospace;;inherit;;inherit>\stages\bin\update.bat</font>" |
| * Restart the Stages service | * 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, "www.methodpark.de" needs to be replaced with "http://www.methodpark.de". | ==== URLs must contain the correct protocol ==== |
| | |
| Some changes for URLs attached to work products and Guidance elements: | |
| |
| * URLs are now displayed in the Stages UI exactly like they have been entered, URLs that do not contain ":" will no longer be prefixed with "http:". | The protocol needs to be set explicitly for all URLs that have been entered without a protocol. For example, "www.methodpark.de" needs to be replaced with "http://www.methodpark.de". Some changes for URLs attached to work products and Guidance elements: * URLs are now displayed in the Stages UI exactly like they have been entered, URLs that do not contain ":" will no longer be prefixed with "http:". * When accessing a URL, you simple click a link with that URL. The access will no longer be redirected to the actual URL by the Stages server. * This means that navigation to URLs will no longer be logged in the access log. For example, URLs will no longer appear in the "Recently Used Files" widget. * This makes "file:" URLs work (if they contain a host name after the "file:" part, and only in IE 11 and Edge). "file:" URLs with local folder names or drive letters are blocked by all current major browsers for security reasons. * This makes "mailto:" URLs work (issue 32942). // |
| * When accessing a URL, you simple click a link with that URL. The access will no longer be redirected to the actual URL by the Stages server. | |
| * This means that navigation to URLs will no longer be logged in the access log. For example, URLs will no longer appear in the "Recently Used Files" widget. | |
| * This makes "file:" URLs work (if they contain a host name after the "file:" part, and only in IE 11 and Edge). "file:" URLs with local folder names or drive letters are blocked by all current major browsers for security reasons. | |
| * This makes "mailto:" URLs work (issue 32942). | |
| |
| |