Associations between elements of the same type must have a source and target role assigned. This extension of the migrateMetamodel script helps to fix associations that do not adhere to that rule.
When you were in the valid version you could not get associations of the working version with stages#getRemoteAssociations and vice versa.
"View groups and permissions" for a user required "Modify" permissions for "Users"
If SAML login failed because all available licenses were fully booked, no error message was displayed in the login screen.
Support infos did not contain stdout.log and stderr.log
There was no possibility any more to set the feedback system for a workspace to a 'default' feedback system that changes automatically when the default is changed in config.xml. Now, the feedback system for new workspaces will be set to the default system. The default system is either the one with default='true' in config.xml (see ST-36038 changelog entry) if there is exactly one, or the first one in config.xml (like before ST-34711). It is still possible to set the feedback system for a workspace to a specific system or 'None'. The feedback system will fall back to 'None' when it has been set to a specific system and this specific system is deleted from config.xml.
Migration script for associations with same source and target element type but without defined roles.
In the quick assign dialog only 10 dependent elements were available. The limit is now set to 50.
If the security level of an element was modified, the change was not propagated to dependent child elements (e.g. work product states).
It was not possible to associate a process element with different dependent elements to the same process element via search.
Wrong message ("You can continue working while the module selection is being added") was shown in update and remove module progress page.
The deprecated element type orgunit caused errors when used as association target.
Custom tooltips were not displayed when lazy link resolving in image maps was enabled (property "process.description.imagemap.lazyeval.threshold" was set to "0").
When an element type was switched to "folder" and the element had files, these files could still be found by global search although files are not displayed at folders.
Fix remote code execution vulnerability of Stages Security Advisory 2024-01.
Set Strict-Transport-Security/HSTS header with default values
Update CKEditor to version 4.25.0-lts for security fixes
Floating action button was not visible if there were no element subtypes.
A feedback system and host can now be marked as default in config.xml and is then set when new workspaces are created.
Custom attribute values of element types were not imported for the following element types (which are normally not used in metamodel): article, annotation, category, orgunit, ypuser.
Task reminders with the setting month led to an exception in the release automation.
Two backend requests were made (unnecessarily) when loading a visualization
A large number of database queries was made for API calls that fetched a large number of users when login-related information was queried for these users. Login-related information is now preloaded when fetching the users with pkit.getAllUsers(), userGroup.getEntities("containsUserGroup@System"), participant.getEntities("containsUser@System") or role.getEntities("containsUser@System")
The "Company" workspace was opened when an administration job was clicked in the list (only the "Edit" menu item worked for editing)
The ensureDatabaseIntegrity/ensureAssociationIntegrity script now can cleanup associations with invalid source or target process ids.
When searching for an element name in the link plugin, the current user language was always used, even when a different language was edited in the "Translate" view
The button "Send an error report" on the "Internal Error" page opened an empty page where no error report could be sent.
Button in workflow notification mail was not visible in GMail due to missing background color
Certain process element views with association widgets showed slow loading times, due to inefficient retrieval of comment only associations.
Update Tomcat to version 9.0.91
Added option to export files into simplified/flat folder structure during archiving. Enabled via new config property "archiving.useFlatFileDirectories" = true.
Adds warnings for missing files during archiving. Can be disabled via the new config property `archiving.disableMissingFileWarnings=true`.
PKit::getMostFrequentlyUsedFiles has thrown an exception if there were deleted files.
In some cases the transferMappings script set compliance coverage on elements of the new reference model incorrectly to "None" while they had the setting "Not covered" in the old reference model.
It was not possible to add files to a guidance element when the permissions were sufficient, if the parent element had a higher security level.
Process elements could have an incorrect sort order in some situations after pasting elements or creating new elements, when the element had both children in the left navigation and dependent elements
State that is used as state of previous valid version step was not created on workflow import.
The value of the "New state of previous valid version" field was not imported correctly when the state name consisted of more than one word.
Button was not aligned with dropdown arrow in Management > Process Versions
Now transferMappings script supports the option "--recursive" (-r) that you can use when you want to copy the compliance mappings and coverage for a target workspace and all of its transitive subworkspaces from an old to a new reference model.
The 'updateTarget' script is now trying to update the existing target table. The old behaviour (deletion and recreation) can be enforced with the '-d' option. There is also a new '-w' option for updating the target table only for individual workspaces
It is now possible to get the descriptions in all languages from a process element or process start page in a multilingual workspace using the property name "MultilingualDescription".
Upgrade of v6 databases failed when trying to recalculate the compliance ratings
Database cleanup script ensureDatabaseIntegrity did not cleanup anything, if parameter processIds was provided without explicit specification of step IDs to execute. Now all cleanup steps will be executed in this case for the given processes. Moreover, the possibility was added to specify workspace IDs (parameter workspaceIds) instead of process IDs.
Changed the default description text color
of dependent elements to black. Before it was grey/blueish and it was not possible to change it to black at all.
In the element translate dialog, it was possible to get an internal error after the translations had been saved.
Improved error message handling on cms test connection
Compliance ratings of reference models to reference models have not been exported.
Process elements with calculated associations could not be displayed in the diff if the diff was calculated with previous stages version
Removed RTC Feedback plugin 3.0 from default installation, due to vulnerabilities of its dependent libraries.
Footer in module warning summary was false aligned.
The confirmation dialog for removing a process module was not detailed enough
In rare constellations, push module updates by a process release workflow execution could fail with the error "java.lang.NullPointerException: End timestamp for validity expected here."
Update Tomcat to version 9.0.88
Updated SharePoint Online adapter to remove third-party dependency with security issue.
Update several dependencies for security fixes.
When there are invalid inputs (e.g. names containing "|") in the dialog for adding multiple successor activities, now the first invalid input field is focused when the save button is pressed.
Fixed text alignment in input field for new elements in dependent elements widget (states, ...)
Text in license statistics diagram was misleading: "Logged-in" is the number of used licenses for a license type, not the number of open sessions for users with this license type. Text was changed to "Used".
The transferMappings script was not working in Stages 7.9.
Modifying a compliance scope will no longer have the user wait for its completion
Reuploads of files did not affect the "Recently used files" list in the dashboard ("Home").
Under high load a login may have failed even when providing correct credentials.
"unsafe-hashes" in the "Content-Security-Policy" header was not set for Safari on iOS due to missing support in previous iOS versions. Now, it is always set unless the configuration property "global.secureMode.blockInlineScripts" is set to "false"
The script to transfer reference mappings and coverage settings from an old reference model to a new reference model version (transferMappings.bat) did not work if the new reference model elements were mapped to the old ones instead the other way around. This fix changes the behavior so that the mappings need to be made from new to old instead of from old to new.
Fixed a bug which required the user to compare versions multiple times before the selected language was compared in multilingual workspaces. Compared versions are precalculated in the correct language.
After replacing a working version in a workspace, an incorrect user name was displayed in subsequent locking error messages
An API method was missing. Due to this some reports like the "Unresolved Process Interfaces" report failed. Now the method is there again: stages#getAssociations(@Nullable String[] sourceProcessIds, @Nullable String[] targetProcessIds, @Nullable String sourceElementTypeIdent,@Nullable String targetElementTypeIdent, @Nullable String[] associationTypes, @Nullable String processVersionIdentifierOverride)
The computation of "Average hours per session" in the Administration dashboard was incorrect because the timeout interval was not subtracted from the duration of user sessions that were terminated by the session timeout
When paging through a user group with more than 200 users, only the first few pages were shown.
Improved error message when compliance rating recalculation fails, because two users add the same rating at the same time.
A visualization error could occur when a user received the permission to view the current process by a participant assignment that was made while the user was logged in
Simplify configuration for HTTPS, reports and PDF printing. The server.xml and database.properties do now support variables defined in config.properties and secret.properties. This simplifies configuration sharing between test and production server. Run update.sh|bat and restart Stages for configuration changes to become effective.
[revert]
It was not possible to find all remote associations (interfaces) of a process efficiently. Now you can easily use: stages.getRemoteAssociations(String[] sourceProcessIds | null, String[] targetProcessIds | null, String sourceElementTypeIdent | null, String targetElementTypeIdent | null, String[] associationTypes | null).
[revert]
When the %WORKSPACEPATH% variable was used in the image map of an image in a description that was remotely embedded in another workspace, it was resolved to the workspace in which the description was located. This was an unwanted behavior change - up to 7.10.3.0, it was resolved to the workspace that embedded the description.
Reduced number of live CMS connections.
[revert]
Improved error handling for closed web socket connections.
Not all of the languages supported by the unified configuration were installed upon configuration update, unless the configuration property "supported.languages" had been explicitly been set in the config.xml file.
Menu item Management was not available in process compare mode.
Creating/editing/deleting a dependent element or an association of a dependent element did not update the last change date and last change user of its dependent element container.
Fixed error ORA-00913 during module update on Oracle databases.
[revert]
Failed process modules could not be removed via context menu or multi-select
Adding modules to an empty workspace could fail when a very large number of modules (>50) was added at once
Many collisions occurred between retry attempts of asynchronous background operations. The retry interval is now including randomness to avoid these collisions.
Under some circumstances, the "Push module update" automation step replaced a valid version of a module with an older or non-valid version
It was not possible to assign a user to several release interface tasks inside the same step.
Assigning process elements to tailoring answers was very slow when there was a large number of process elements for an element type
When the same element was associated from a tailoring answer in multiple categories (e.g. "Remove if selected", "Add if other selected"). Copies (and versions) of the process contained only one of those associations.
Creating a process version could fail if a referenced process version was deleted concurrently.
Process version creation was very slow in case of many interface associations. Affects especially MySQL 8.
Collected associations starting from dependent elements displayed a random dependent element in the association list. Now the association is displayed for each assigned dependent element.
Sometimes, labels for associated elements were not aligned properly in the "Table" visualization
Saving a description with newline characters was rejected as false-positive finding in the web application firewall.
Update Tomcat to version 9.0.86
Update CKEditor to version 4.24.0-lts for security fixes
Restrict all API requests to an authenticated user session as prerequisite by default.
Forced visibility was inconsistently calculated after successive tailorings of the same element.
Menu in association browser was not usable when content was scrolled down.
It is now possible to find out if an association comes from a process module via property "FromModule". Additionally, the property "ModuleIdentity" returns the identity of the process module.
Remote associations were not sorted by target workspace name.
The initially created first valid version of a workspace V0 did not have a state when this was queried via API (e.g. for reports or process visualization diagrams). Now the initial state (e.g. draft) is returned by API as it is shown for V0 at "Management > Process Versions".
Default timeslot for database compute statistics is moved from daily 11pm to every Sunday 11pm.
Skipping document prefetch for a certain CMS type was not possible.
Comparing a process now continues automatically when progress is complete
Process execution failed when a process release state contained a "&" character
When the translation dialog for an element was open and you directly switched into the translation dialog for another element (via left navigation context menu), the new form still showed the name of the previous element.
Deleting an existing association comment lead to follow up errors during comment to state migration when using MySQL as database.
Process modules adopted elements by name even if they did not have the matching subtypes.
Associations of integrated module elements were deleted in some cases when they should not be deleted
When module installations were updated by release automations, "Superuser" was shown as the user who did the module update. Now, for future updates, the actual user will be shown who started the release automation.
Fix sorting of tailoring dependencies of tailoring answers. The elements are now sorted hierarchical.
Links originating from embedded descriptions were erroneously reported as broken by the readiness check when their target elements were not present in the valid version
Links in image maps that contained variables were erroneously reported as broken by the readiness check
Floating action button is now expanding card component to make sure all menu items are shown properly.
Could not move report folder to top-level.
Trying to change the workspace while copying/moving a report resulted in an error. Now the workspace selection is disabled when the clipboard for copying/moving reports is open because reports are generally not bound to a single workspace.
Update Tomcat to version 9.0.85
On mobile devices the menu was closed when the device was rotated.
Clicking cancel in the "Add Admin Job" form and "Add URL" form for files directly, without providing any input, did not work initially when the upper part of the cancel button was clicked.
When using Stages with an exact screen width of 1280 pixels the navigation drawer was overlapping parts of the content.
For some process element names, the facade returned process elements in a different sort order than the order that was visible in the UI
Importing a process will no longer import only one scope of every assigned reference model if there are multiple.
Files with content type "message/rfc822" (for example: exported emails) could not be uploaded in Stages
Could not import process with overwritten tailoring elements.
An error could occur when copying a process element with remote associations to overlaid elements.
Adding a new dependent element (e.g. state/quality level) directly in the search bar of associations will now create the correct type (sometimes a state was created instead of a quality level, even when a state was not allowed for associations of this type by the metamodel configuration)
Unified all occurrences of participants to show 50 participants before adding a second page
A temporary locking exception during task scheduling led to bypassing the configured retry mechanism.
Fixed some problems with readiness checks related to dependent elements:
- An "element not found" error occurred when trying to open a readiness check finding for a dependent element. Now, the parent element is opened.
- Association constraints were evaluated independently for dependent elements. For instance, a work product state or quality level that was not input for any activity caused a warning for "Checks if each work product is an input to at least one activity.". Now, association constraints are only evaluated against the parent element, and the associations of all dependent element children are merged before the constraint is evaluated.
Workspace search did not find workspaces in Chinese when the search term didn't start from the beginnig of the workspace name.
Upgraded search engine to version 7.17.15.
User and workspace search did not find anything when asian characters (e.g. Japanese, Chinese, Korean) are used and the search term did not contain the beginning of the user/workspace name.
An externally authenticated user could have been able to change his local password.
Under specific circumstances an internal error was returned when trying to authenticate with captcha login.
Updated feedback adapter dependencies for security fixes
SAML attributes could not be accessed in JavaScript snippets if the name of the SAML attribute was not a valid identifier name in JavaScript. Now, the mapped attribute name must be used.
When adding an external link with the name first before the URL, the name didn't show.
The fix for ST-35233 could cause an error when generating the table of contents in the PDF export for some processes
PNG images with transparency and CCITT type images were not treated correct during PDF generation.
The participants shown for users will now be correctly sorted by name
Changing process settings for a process in which the working version is also the valid version, will no longer result in an error.
An error could occur when changing the metamodel of a process when other versions of this process were deleted by a cleanup rule
Migrate metamodel no longer duplicates the element identity when using indexAsFolderName.
Removing associations from an association "from multiple workspaces" will now correctly update the association list.
Creating an element via the association widget would create wrong element subtype in some cases.
Send email steps and push module update steps did not set the configured process version state.
The process release details showed the wrong process versions of installed modules when the new valid version of the process also contained a newer version of the module.
Comment-only associations with a state will now display the state in the association list
Duplicate diagram idents for a widget definition or layout tab of a configured metamodel are now logged as warnings.
Alphabetical sort order of associations was not correctly maintained when adding new associations to the group.
Origin element links in module properties were displayed even if they did not exist in module process because the metamodel did not provide the element type.
Some menu items of the visualization card were erroneously removed when using non-unique diagram widget idents.
Update tomcat to version 9.0.82
After a certain number of failed username/password authentication attempts, the entering of a captcha text is required to login successfully.
User names for user IDs were disclosed in some error response messages
File system paths on the server were disclosed in some error response messages
Fixed permission check for deletion of cleanup rules and archives.
Added a new processId parameter to ensureDatabaseIntegrity and ensureOracleAssociationIntegrity. Using this parameter restricts the cleanups to the specified process.
A workspace was never deleted properly when there were Stages 6 issues for this workspace. This bugfix will delete all content related to the Stages 6 issue tracking functionality from the database.
In the small-screen "Permissions" view for a user group, a workspace name was displayed for permissions that had the "Adopt workspaces" flag set
updateTarget.bat displayed a misleading "Path not found" error message
Subversion repositories for work products were duplicated by release as valid version if 'use system user' is activated in working version.
Changing a Guidance repository in the working version also affected files from this repository in process versions if the elements of the files were overwritten. The effect could be visible when the overwritten element was restored.
Work product repositories could not be modified or deleted in the valid version
Tables could overflow the right margin in PDF exports (the table width was not enforced by breaking words)
Images could overflow the right margin in PDF exports when the paragraph containing the image was indented
In some situations, Stages compared the current valid version to itself when clicking the "Show Changes" button in the "new valid version" badge
When the feedback system that was selected for a workspace was deleted from config.xml, an empty feedback widget was displayed for the process elements, but in the workspace properties, the default feedback system was displayed as selected. The new behavior:
- There is now always an option "None" for the feedback system in the workspace properties
- The feedback system falls back to "None" when it has been deleted from config.xml. This will also happen when only the host has been deleted.
Concurrent process modeling could result in database inconsistencies.
If the source element was from a module and overwritten, the association was removable on the target element.
When adding a process module to another process, the compliance associations to the valid version of the reference model were copied. Now, the compliance associations to the working version are copied. V0 is no longer created when importing a reference model from a .zip file or copying a reference model from another workspace.
States were missing in some cases in the approval history and approval history menu entry was missing, if a step in a release automation failed.
The "Compliance Traces" report caused an error when the executing user did not have R, Processes permissions for one of the reference models. Now, these reference models are filtered away in the parameter selection.
Jira feedback supports Personal Access Tokens and more Jira field types
Generating a process diff lead to an error when one of the two process versions contained a description element that embedded itself (directly or indirectly)
Summary of translation import was broken and continue button was not displayed correctly on process import summary.
When an element was copied to another workspace and a there was an association between this element and an older process version of the target workspace but not with the working version, the association reappeared as local association on the copy.
The placeholder text for changing the source or target of an association reflects its functionality better now
Process module information in the "Properties" widget on a process element page was not updated properly when the process module version or workspace was renamed
Although a workflow was aborted, currently running system operations could create follow-up tasks.
Fix exception during Stages start up when process review and approval workflows need cleanup.
Long participant names destroyed group header styling.
Centered and right aligned process version descriptions were not displayed correctly.
After reloading the diagram (e.g. after modifying associations) the scroll position will now be at the position it was before the reload
In some situations the type filter on the search results page was missing or did not contain all types from the search results.
It was possible to edit workspace settings with any "Modify" permissions for other areas in "Administration"
Fixed displaying error message when having an empty name during editing of a workspace
Fixed breadcrumb navigation from Edit Workspace back to Workspace hierarchy
Cookie autologin did not work
Select All switch had no impact on child elements under some circumstances.
Path in Subversion CMS was requried
A file from the Subversion CMS could be disconnected from its repository in some situations after the container element had been moved or copied to another process, even if an equivalent repository was defined in the target process
An error occurred when trying to link a SharePoint Online file to a Guidance element when a file from the "Database" repository was already present on the same element
Log messages were truncated to often. For CMS document and structure prefetch failures, one message per failed file/repository is logged now.
Multiple "Show More" entries in the same list of associations will no longer interact with each other
Do not create "LOST+FOUND" elements for tailoring resources. The fix also deletes existing tailoring LOST+FOUND elements.
The creation of remote valid versions now uses the state of previous valid versions.
When there were no interfaces selectable the workspace was shown as selected.
When some Interfaces were preselected through MetaModel configuration and some Interfaces not. The preselection was deactivated when navigating into the detail view of the workspace selection.
A user could be assigned more than ones to multiple tasks of the same step. Now he can be assigned only once.
Show filter for process interfaces was shown in valid version and had no effect
Constraint check for required associations (e.g. required output activity on work product) did not handle dependent elements (e.g. work product states) correctly.
Selecting or deselecting a workspace in the "release interfaces" dialog will now correctly affect the associations in the workspace
The Visualization options of diagrams will no longer be incorrect after collapsing and expanding the diagram
The "License Usage" report did not display the license usage correctly when multiple license pools were defined. Now, the sum of license usages over all license pools is displayed for every license type. The license usage for the specific pool of the user that has just logged in/out is still written to the logfile.
Fixed some permissions for accessing user administration pages
Upgrade Tomcat to version 8.5.90
Update Guava to version 32.0.1 for security fixes
Only selected switch could not be activated in some cases.
Headings were not aligned properly in a description editor when the editor was inside a popup dialog (example: Edit process version description)
Updated dependencies of SharePoint Online adapter
Uploading very small files (<4 byte) produced an internal error.
Dependent elements were not filtered out of the file mangement plan
Fixed sorting error that might occur in file management plan after changing the metamodel.
Enable triggering of a file prefetch after modifying a repository configuration, to ensure the process baselines contains the intended file versions.
Comment-only compliance mappings had wrong source element types set after adding/updating them from a process module or importing them from a process ZIP export.
Fixed an error in the calculation of escalated tasks regarding the release automation
If an release automation contained an interface approval step but no user step (like a review step) an internal error occurred during the exection of the automation
An exception ("java.lang.IllegalArgumentException: Comparison method violates its general contract") could occur when running the "Compliance Overview" report if there were compliance associations to multiple process versions in the same workspace
Global Search: When you searched for multiple words (e.g. "supplier agreement") and there were elements containing these words with prefixes separated by underscores (e.g. "1234_supplier agreement"), search results containing the words in different sequence without prefix (e.g. "agreement with supplier") were listed before the prefixed results with the correct word sequence.
Added confirmation dialog for restoring participant assignments back to the default
Memory usage could become excessive for long-running admin jobs and reports
Fixed cron expression interpretation, added responsive behaviour and cron expressions examples to Edit Job
Clicking on the name of an administration job resulted in an error page. Now the edit page is opened for the job.
Selecting a date in the datepicker of "announce maintenance" or "schedule process version release" did not select the correct date when confirming with enter
When workspaces were partially selected through metamodel configuration, the "next button" in the release interfaces dialog was not activated in some cases.
Links to Stages content in PDF exports were broken.
Optimize memory usage of PDF printing.
Could not create new local associations to an element imported from an on-demand module
Push update was not executed when integrated version was deleted but was still integrated in the working version
The creation of a process version with the same name through multiple workflows or through manual and automation creation could lead to locks.
Closing the date picker for scheduled process releases and opening it again will now remember the previous selected time instead of the current time plus 1 hour
When starting the release automation and entering the version name, validation errors were not displayed correctly.
In case of a misconfigured constraint check (e.g. wrong validator class path in process.xml), an empty error section was displayed for this check on "Check readiness" page. Now an appropriate error message is displayed in this case.
Enable strong CSP for Firefox again after a compability fix in Firefox version 110. This reverts the workaround introduced with ST-34799.
Workspace attribute values were deleted under some circumstances
Selecting an element in the quick assign search dialog could add the wrong item.
Resizing images migrated from V6 resources was using an image conversion algorithm that caused transparent pixels to be converted to black making texts unreadable.
Updated dependencies of SharePoint Online adapter
Linux: Stages could not be started with latest systemd versions.
In a few special constellations the process element description diff showed some text striked through, though it was not removed.
An exception could occur when an association list with more than 25 entries was sorted in "Custom" order
Fixed various errors for scenarios in which process elements were imported from on-demand modules via association widget.
When workspaces were partially selected through metamodel configuration, these interfaces were not released in the release automation in some cases.
Made 'subject' and 'message' required for the 'send email'-step of the release automation to prevent an error that occurred with an empty message field
The process release details were empty for process releases that were created by automations running in Stages 7.8 (or earlier)
Interfaces are not preselected without extended metamodel configuration when unavailable interfaces were included.
Process Cleanup no longer requires that mail notification is configured.
Files were not deleted properly in a module import when a Guidance element was moved to another module and files were deleted there
In some complex scenarios on module updates when LOST+FOUND elements originally came from the modules to be updated but have been deleted in the meantime, StackOverflowErrors could occur.
Concurrent interface releases caused wrong process versions states on the interface workspace.
Links to tailored elements on landing pages were still clickable after disabling the user setting "Show tailored elements".
Uploads of executable files are now rejected by magic number and/or by file extension.
Simplified configuration of fonts for process visualization and pdf generation. Now Config.xml needs only one "global.font" property with the font file name as value.
Added script to migrate comments on input and output associations to states of the artifact.
Do not delete LDAP users in case the LDAP provider is not available.
Files could not be unlocked in Stages if they have been locked via Stages but have been unlocked directly in the external repository.
When the originally installed module version was renamed and the module installation was updated with a newer version in which elements were moved to different folders or sorted differently, these changes were not applied on module update.
When the user unselected an interface workspace before starting an automation, but navigated into the interface list for this workspace after unselecting it, the workspace was considered selected again
Increase robustness of release automation and extended logging.
Fixes incorrect english grammar in email notification subject.
Update visualization library to fix a regression in edge routing of back links.
The reports "Unique Users" and "Usage Report" were broken since version 7.9.2 because of a slight format change in audit.log. Print license type in audit.log
Deny all unused HTTP methods.
Update tomcat to version 8.5.87 to fix a regression.
Fix formatting of pdf name for prints on the index pages.
Editing the process start page was not properly recorded in the access log
Tailoring assistant result calculation took very long in certain situations.
When the working version was also the valid version in some cases association queries could deliver the wrong results for remote associations.
API user role assignment and unassignment command did not work anymore.
Fix performance of file revision access.
Pause and Resume menu entries where never available for admin jobs.
Prevented possible error when opening "View permissions" for a user in the user administration.
When a user with a personal license (or the superuser) had sessions in different browsers, every session was counted and the number of "logged in" licenses could be higher than the number of "active" licenses in the administration dashboard
The text input in the HTML section plugin was labeled with "undefined"
Allow to edit file properties in case of certain errors which prevented this before.
Pinned dependency of oslj4jena in RTC Feedback.
Sometimes, some process versions were not available for selection in the process version switcher at the tailoring root element
Extended migrate subtype step of the migrateMetamodel script in order to create element attributes from element subtypes (sourceSubtypeToAttribute) and/or to append association comments (appendAssocComment).
Fixed some cases in which the selection state of the parent item for element assignments to tailoring answers and for workspaces with process interface changes was not shown correctly.
When a process element view contained a widget with some readonly attributes (due to missing edit permissions) an edit icon was displayed nevertheless in situations when the corresponding element had other editable attributes.
Refreshing the 'Process Modules' page will no longer result in an empty page
The variables processVersion.name and processVersion.description are now available in email templates.
Some report error messages (e.g. timeout) were not displayed.
Reports had a size limit of about 10MB and are now mainly limited by available server memory.
Update tomcat to version 8.5.85 for security fixes.
Unwanted and possibly incorrect 3rdpartylicenses.txt file was accessible via URL.
Reduce CMS requests during document prefetch by remembering available repositories.
Password-protected archives could not be extracted when the password contained umlauts.
An error could occur when viewing the participant assignments of a user when one of the assignments was local to a workspace that was in process of being deleted.
Added missing chinese translations
An error was logged in stages.log every time a user with an existing session had to log in again after a Stages restart
Users can no longer start multiple pdf creations in parallel on the same dialog
PDF creation failed when the workspace name contained a slash.
The download button after creating a PDF will now always be scrolled into view if it was not visible.
Small descriptions of pdf-templates will no longer result in a broken styling of the pdf-download dialog
Fixed Jira feedback creation with gzip http conneciton
Fixed a bug that could prevent a workspace from being deleted.
Warning icons and progress spinners are now aligned with each other
Fix for the following scenario: Multiple process modules contained the same elements (frpm the same base module) but the elements had different associations in the modules. When these modules were added to the same process it depended on the sequence of the additions if the associations were there or not.
Stakeholder groups having more user assignments on the next page will no longer be missing assignments sometimes
It was not possible to release a process version as valid version, if there was no current valid version.
User created by SAML SSO could not be found by email address when searching in Administration > Users
Fixed error on startup, when cleaning up obsolete operations
Optimized performance of compliance scope view
Changing the name of a file in the "add files" dialog and pressing enter will now submit the upload instead of deleting it
Files can now be manually linked when the repository is browsable, but delivers no files
Firefox v108.0 did not load Stages any more when "global.secureMode.enabled" was "true". This fix disables "unsafe-hashes" for the CSP "script-src" when using Firefox (maybe temporarily until the problem is fixed in FF)
The group names in the message "there are more items on the next page for ..." will no longer be displayed with "???" before and after the group name for the participant-administration and the participant-workflow-preview
RPM upgrade renames license.xml to license.xml.rpmsave
Files renamed inside stages had no file extension in process archive pdf.
Mixed case language properties defined in metamodel can now be resolved in all cases.
The creation of dependent elements via quick assign lead to a no access error in read-only remote workspaces. Now it is no longer possible to trigger a create action without create permission in the remote workspace.
When a process module with files or user role assignments was added to another process module and then the other module was added to another process, the files and user role assignments from the module were missing in this process.
When a process module contained multiple repository configurations with the same settings, it was possible that the repository assignments were wrong for files from these repositories after module updates or additions.
Emails sent by the "Send E-Mail" step were empty when the workspace in which the automation was running was multilingual and the user language of the recipient was different to the workspace language
In some situations system tasks like 'Create process version' were executed multiple times.
Automations could be stuck in "Release process version" steps without even a possibility to teminate them.
Fixed incorrect use of parameters in some process release automation email texts
Optimized the deletion of tailoring associations
The version description is now shown the process release details.
Could not get process version description without visible tags. Now the new property "VersionDisplayDescription" can be used in this way: stages.getCurrentProcess().getProperty("VersionDisplayDescription").getDescription();
The view was not updated after removal of compliance mapping associations.
Upgrade from V6 to V7 failed with Oracle databases when the Oracle text package was not installed or the permission for the creation of fulltext indexes was not given. Now neither the package nor the permission is required anymore.
Image map areas with leading or trailing whitespaces in the coords attribute were rendered incorrectly.
In multilingual workspaces, suggested file paths for the file management plan used the process element names in the current language, so the folder in the CMS could depend on the user language of the user who uploaded the file. Now, the workspace language is used.
The suggested file paths in the file management plan in Stages 7 differ from Stages 6. Whitespace characters are removed whereas in V6 they are replaced with an underscore. Now the V6 behavior can be restored by setting the property "cms.file.path.suggestions.v6.style" to "true" in config.xml.
Links to landing pages did not open the correct landing page if it was not the first one.
The creation of archive progress is now split into steps represented with a percentage view and steps that show an endless spinner to better reflect when we can make no estimated time assumptions
If files were assigned to different SharePoint repositories and the repository configurations only differed in the SharePoint site names the wrong repositories could get assigned on process import.
When a process module was refactored by moving elements to other modules and renaming them there, it was not possible anymore to update the elements with their new module in processes where the old version of the module was installed. New elements were created then. Now this problem is resolved and there is a new restriction: Moving elements to other processes will not be allowed if some or all of the elements already exist in the other workspace (identities already exist).
Dependent element rename input field was empty when opened, closed and reopened again.
The state of a user workflow step was only set at the process version after the first user task had been completed.
The step "set state of previous valid version" will now use the previous valid version of the newly created version instead of the previous valid version of the current valid version.
The styling of the process versions management page was broken after starting an automation.
Process release automation emails were only sent to one user even when multiple users were assigned to a participant
When a task for approving process interface changes was opened from the todo list on the home dashboard, interfaces were falsely shown as unavailable in the following case: The target element in the valid version in which the release automation was started does not exist in the current valid version but the automation will release a new valid version later which will contain the element.
The tailoring browser now indicates whether child elements have been selected
Improved the access permission checks for temporary stored pdf documents.
If Stages was temporarily not available an "Internal Error" was shown. Now the "Server temporarily not available" page is shown.
Used OSS licenses are visible to the end user
Looking at the user permissions overview page could lead to a nullpointer exception when a role was associated from a process where the metamodel has no roles configured.
An error 'Incorrect string value' could occur when saving compliance rating notes with special characters and with a mysql connector version >= 8.0.29.
Reduced thread consumption in SharePoint CMS.
Line breaks had been removed on the version history page for comments on an uploaded file.
Files could not be download when being redirect from Stages 6 bookmarks.
The 'set state' operation on files will no longer ask for user credentials when 'use system credentials' is enabled for the repository configured in the file properties
Fixed comment handling in set state and revision history
Upload file, using a template from a cms repository defined in a remote workspace was not possible, when credentials for the cms of the guidance element where needed.
When lists with groups and multiple pages are displayed the message “There are more items on the next page for [group name]“ is shown. The message property for the group name was not translated.
Creating a pdf will now save the file on the server for the time specified in the config-property 'temporaryDirectoryCleanup.deletionAgeInSeconds' and can be downloaded afterwards. The browser no longer timeouts, waiting for the pdf.
The new default font for PDF printing caused some layout problems. The default font for PDF was changed to 'Source Sans Pro'.
When two process versions were compared, certain characters (e.g. German umlauts) were not shown correctly for added/modified badges on element shapes in process visualization diagrams.
Having a <span>-element inside a changed part of a description will now still be marked as changed.
Fixed dependency in RTC Feedback.
Updated dependencies in RTC Feedback.
Process exports from V6 could not be imported into V7 if they contained role notification settings.
Fixed various problems where reference model scopes or elements were not mapped after process import or compliance coverage settings were missing.
After switching the process version in the process settings the correct metamodel wasn't always displayed.
There was an error when deleting an association to an overwritten element using "Browse" when the deletion was attempted on the side of the other element, not the overwritten element itself.
Links to other workspaces on the "usage"-tag of the module management now work again
When a module process version was installed in another workspace and then the module version was deleted, the usage tab of the module management page showed no installations of the module.
In Management > Process Modules, the "Added" tab could show the previous contents of the "Usage" tab after switching from a process version with process type "Process Module" to a version with another process type.
If a participant group got deleted while there is a workflow started with this group, users associated with this participant group will no longer have a 'element not found'-message in their participants tab (administration -> users -> user xy -> participants)
Variable %USERFULLNAME% was not supported in step description.
The ST-34648 fix lead to an error when there was a running workflow with a "Notify users" step and two or more other steps with the same participant on Oracle
A participant was erroneously deleted when it was the recipient of a "Notify users" step in an automation for which an instance was running while Stages was upgraded to version 7.6.10.0, 7.8.5.0 or 7.9.1.1
An error occurred when clicking the "Show Changes" button in the notification email if the user had no read-permission for Process Version.
A participant of a remote workspace will no longer receive a todo for reviewing the version of the workspace the workflow was started in, when no participants were assigned to that step.
Implement %WORKSPACEPATH% resolution consistently as in Stages 6 to be backward compatible
When a task failed, the state was set on the affected process version nevertheless. Additionally, when the setting of the state failed, no approval history entry was created.
Release notification emails were not formatted correctly on Mac Outlook.
Stages crashing after a system task was created but not yet executed, will no longer result in an unresumable workflow.
The todo list on the home page vanished under certain circumstances when you switched the tab to another landing page.
"Send email" step fails when one email recipient has license type "None".
Improved error message when trying to release a process version that is already valid.
Interfaces of tailored elements are always shown and clickable in management
Opening the menu of the current index element when adding questions to the tailoring will no longer result in doubled menu entries
The menu entries for selecting and deselecting all elements and all elements in folders in the element browser work again
When toggling the "Show tailoring details" switch and then using the back link in the user settings an Internal Error could occur.
In the context menu of a process element the 'Reset tailoring' item was displayed even though the tailoring status had not been changed.
Avoid locking process baselines for calculation of process diff.
Versions with Error-marker had menu item Approval History.
Saving a new sort strategy for associations and opening the sort immediately after the save will now show the correct new sort strategy
Multi-delete of associations were not executed for associations revealed by "Show More"
Image maps were not clickable anymore after going back to the description using the browser back button.
Under some circumstances the add button for sequences could produce an error.
Reference cycles in description elements were always checked and therefore handled in the valid version which could lead to a StackOverflowError when rendering descriptions of other process versions.
Quick (de-)selecting of parameter switches lead to a de-synchronisation between visualization and switches
Run button was initially disabled for new reports.
Special characters in workspace name caused unresolvable reports
When you switched the search scope from current to all workspaces and back, sometimes details on the search results page were missing like the link that was shown when there were no results in the current workspace but potentially in other workspaces.
Improved confusing link text on search results page that is shown when you search in the current workspace and there are no results there but there may be results in other workspaces.
Updated Tomcat for security fixes.
Class names were displayed in the error message when sending invalid JSON to a REST endpoint
Anti-clickjacking header was not sent for all requests.
Do not duplicate underscores in association comments when retrieving them via API (e.g. for process visualizations).
Could not delete users that had stored issue filters in Stages 6.
Database upgrade failed if upgrading the default Stages 7.6 database because of inconsistencies in the start_parameter and field table.
Search indexing could fail sometimes on Windows (BindException) when too many short living TCP connections were created.
There was no getStableUrl function for process versions. A stable url is a link to the dedicated process version. This is important for valid versions when you do not want links tht always lead to the current valid version (this is what getUrl does) but to the version that was valid at the time the link was created.
When you called getUrl on a project (workspace) element, you always received a link to the process start page in the valid version of the corresponding workspace. Now the link leads to the process version from which getUrl was called. Additionally fixed NullPointerExeption that occurred when getUrl was called in a workspace that did not have a process. Now the generated URL will lead to the home page in the corresponding workspace.
Paths of archived files were not available via API....
The editor pen was not correctly updated after changing the viewed process version.
Upgrade CKEditor to version 4.19.1 for security fixes.
Creating a file from template when the property "use.system.account.for.download" is set to true will no longer ask the user for credentials on loading the properties of the guidance file. It will still ask the user for credentials after clicking on "download & create" to be able to lock the file.
SharePoint SDK
update fixed problem with to many requests
ST-34496 fixed ignored columns on set state
When additional languages were configured in the "supported.languages" property, all message properties could not be resolved for these languages. If you copied the English stages.properties file and appended the language-specific suffix (e.g stages_ja.properties) this copy was removed again by the installer when Stages was updated. Now the copy of the stages.properties file will be done automatically when the update script (update.bat/update.sh) is executed. If you want to translate message properties you can (still) do this by putting a local properties file with the language-specific suffix into the conf folder (e.g. local_ja.properties) and translate the message properties in it. The changes are applied when update script is executed.
When the "width" or "height" parameter was set in the @diagram directive of a PDF template, the generated image was cropped to these dimensions, not scaled
When an image was inserted multiple times into the same description, the image was reported as deleted and added in the process diff even when nothing was changed.
migrateMetamodel CLI tool did not migrate comment only associations in case there were no elements of the target type to migrate.
When multiple associations to identical target elements were combined, you could not delete them directly at the source element. Now there is a menu option "Delete" which open a dialog in which you can select the single associations to delete.
Completing the end step of workflows will no longer log a warning about no assigned stakeholders, because an end step cannot have any stakeholders
In the readiness check, a link in an embedded description was always reported as broken if the target element was not present in the valid version
An error could occur immediately when opening a process element, when the process element had associations to both a child element of another element and a dependent subelement of the same element
prevent log injection.
There was an internal error on the Administration dashboard after 3 minutes.
There was a scenario where automations with process interface version creation steps deleted some interfaces when this was not intended.
Links in process release automation emails were broken by the "Safe Links" feature of Microsoft Outlook
An error occurred when exporting an automation if the participant who was the recipient of a "Send E-Mail" step had been deleted.
Progress was not displayed accurately when multiple "Push Module Update" automation tasks were running
Menu entries for long context menus were sometimes invisible in the Chrome and Edge browser.
When sorting elements in custom sort order, the visual representation sometimes did not reflect the actual result.
Tooltip was not generated automatically when there is no title attribute defined and process.description.imagemap.lazyeval.threshold property is greater than -1.
Integrity: Fixed ThreadPool Leak
PDF printing for asian glyphs did not work without manual font configuration.
Fixed logging for error handling on feedback creation
Shortnames could be entered even though they were not displayed.
Show changes button in release automation e-mails caused an error if there was not recorded validity.
Fixes an internal error when switching the process version on Management Process Interfaces page in Safari.
When emails from release automations were opened in Outlook and Windows display scaling was active, some mail content (e.g. the image at the top) did not have the right size.
The legacy workspace path configuration setting was not consequently applied in all places.
Dashboard could not be openend if there were todos of deleted processes.
Workflow created interface versions even when no interfaces to release were selected
The task details that can be opened from the home dashboard always showed the name and path of the current workspace instead of the effective workspace for the task when the variables %WORKSPACENAME% or %WORKSPACEPATH% were used in the task description.
Error messages that were too long caused followup errors.
Image maps were not resized anymore according to resizing of the browser window.
Process version can now be released and the state can be set via an API command
Create PDF/A-2b conformant documents when archiving a process.
Process Feedback attributes from direct inherited process element
Improved performance of process module updates/installations for association update with many associations.
Process interfaces versions are tagged in the database.
If an automation step fails, the next execution time is now displayed.
Process interfaces and workspaces can now be selected individually for release.
Improved performance of...
Preselected interfaces can now be configured via metamodel
Improved accessibility and readability of email templates for the most common clients
Stages API threw an exception in case metadata for files with invalid repositories was requested. Now it provides the metadata that is accessible without repository access.
Permission counter on user groups tab of users groups and permissions view was always empty.
Users that agreed to the promotional terms and conditions in V6 were no longer able to login.
Searching for a link to insert into the editor did not display an error message when the search engine was not available.
Save properties was not possible if repository was NONE
Link file in guidance element with SharePoint default repository caused an internal error when file with URL only already existed in widget
Trying to perform file-operations with invalid cached cms-credentials will now always result in a login prompt (for entering new credentials) instead of an error message
In the navigation drawer the rearranged custom sort order could not be saved anymore.
When creating a interface release version, the progress spinner was jumping directly to 100% although the action was still in progress.
The REST API for PDF export did not check for the required permission.
Deleting a process execution script required delete permission on processes instead of process execution configurations.
When a process was imported from V6 that contained remote associations to file-based resources, these associations were not rewritten to point to the Guidance elements that were created for the file-based resources in the other process.
Process import failed with error "Duplicate entry" if a process was mapped to different reference models of same origin (one reference model was a copy of the other reference model), compliance ratings for both reference models existed, the mapped process was exported and then imported into a target system where only one of these reference models existed.
An error could occur after deleting a large process and importing the same process again immediately after the deletion.
A NullPointerException occurred when process elements with files were overwritten
Guidance files were not archived if they were stored in the same repository as work products.
Readiness check error did not show erroneous link or path
Since V7 the %PROJECTPATH% variable did not include the current workspace anymore. The previous behavior can now be restored by setting the property "global.variables.useLegacyProjectPath".
Default values for attributes will no longer be shown for attributes that were already saved with an empty text.
Stopping a workflow did not actually stop the operation executed by the workflow step.
Improve process locking for process version state changes to allow more concurrency.
When a precondition for a step in a running release automation failed (e.g. no state available to be set in the "Set state of the previous valid version" step), the automation was stuck and did not continue;
No progress was shown for running "push module update" steps
The available variables for the send email process release step were also displayed when adding different types of workflow steps to an automation.
The version description variable was inserted into emails with unnecessary spacing above and below the text.
The To Do popup displayed tasks from all user steps of an automation as related, instead of only those of the same step.
Approve process interfaces e-mail contained show changes button.
Workflows did not continue when a system task could not be executed due to a failed permission check. It was also wrong that workspaces were listed for the release of process interfaces that could not be released because their working version was their valid version.
It was not possible to move a tailoring answer immediately after adding it.
Interface release did not copy interfaces with older process versions.
Release Interfaces did only show changes when working version was active.
It was not possible to deny process interface release for a user with process release permissions.
The "Continue" button for "Management > Versions > Release Interfaces" did not lead back to the version management page.
Dependent elements assigned as target elements were not show in association list when filtered like artifact.artifact[state]:input
When viewing a process version that had never been the valid version, the valid version of other workspaces was shown instead of the working version
Variables where not escaped properly in process release emails.
List styling of entry pages in sort mode was broken
Manual sorting of child elements in navigation did not change mode from "A-Z" to "Custom".
When process module updates imported new process interfaces and the source and target elements in different workspaces were overwritten, database inconsistencies were created on Stages versions with fix ST-34318. This led to subsequent errors.
Added search field to Process Interfaces filter
Integrity: The file download and version history did not use the correct (latest) file versions if the files came from a shared Integrity subproject which was derived from a checkpoint.
Dropping a folder onto a file Drag&Drop area resulted in an incomprehensible error message.
The state of a process version can be set via an API comand: commands.newSetStateOfProcessVersionCommand(targetWorkspaceId, targetProcessVerisonId, stateTypeIdent)
Make message key resolver available for visualization scripts under the property named "messages".
Reworked notification service
Process interfaces can be filtered by element types
Workspace interface selection in workflow start screen is updating the participants preview
Showing interfaces for the selected process version in process_interfaces and show interfaces (for process versions). Implementing "show only changes" button for process interfaces
Added "approve interfaces" and "release interfaces" steps for modelling workflows.
Process Interfaces workspace list is now provided in management section
Long term process archives can now be created. They contain a PDF export of the process content and all guidance and project files. A re-import into Stages is not supported.
The association path syntax was extended to enable restricting the type of dependent elements that can be assigned in the association widget. (targetElementType.targetSubtype[targetDependentType]:associationType[sourceDependentType])
Associations to dependent elements will now display the correct icons
Multiple dependent element widgets can now be configured on the same site. A type can now have multiple dependent element subtypes.
Tasks of release automation system steps like process version creation will now be retried (11 times by default) with increasing delay when they fail due to concurrent operations. Additionally unfinished tasks of this category will be restarted when the Stages service is restarted. The same mechanism is also used now for manually triggered push updates of process modules.
In the workflow execution view the tasks of a step are now grouped and can be collapsed or expanded.
Completed Release Automations will now be deleted after a configurable period of time.
Show changes in approve process interfaces task.
End step with state is now recorded in approval history.
Conditions 'one participant must agree' and 'all participants must agree' are now considered per scope (workspace).
Improved encryption of support information.
Responsive data views are supporting now a select all at once option
It was not possible to get the participants and roles which were assigned to a user group via API.
Since Stages 7.7 the API combined associations with identical target elements in different workspaces (returned only one association instead of multiple associations). This behavior can now be changed to return all associations by setting the association filter "combine" to "false". Example: element.getAssociations("responsible::MODEL@LOCAL,combine=false")
The link "Request a license" on the administration dashboard did only work for the root user.
The link from a user group to a participant was clickable, even when the current user had no permission to open the participant.
Message property for failed script upload was missing under admin jobs.
When SSO is used together with multiple browser tabs, it was possible that more than one license was booked for this user.
When SSO is used the session timeout had not the indented effect in case the user was on a page that uses polling, as the user was immediately logged in again. Now the user is redirected to the logout page.
SAML response signature check was made required by default with ST-33837. Now the default is changed back such that at least one of response or assertion need to be signed. Improved signature validation error messages. In case Stages must accept only singed SAML responses, please set saml.response.signature.required in config.xml.
After a successful login via Kerberos SSO, it was necessary to clear the browser cache to be able to use Kerberos SSO again.
Dependent elements could be added to compliance scopes.
Some tooltips in the link plugin of the rich text editor were misleading.
The "Edit" icon was always enabled on description cards even when the user had no permission to actually change the description
Ensure file download is latest version from CMS
Fixes title of repository edit dialog.
Directories starting with the dot or the dollar symbol in the name are omitted in the runtime information, because they typically contain binary data.
An error occurred when clicking outside a menu after a menu was opened in Internet Explorer
The Stages UI should not use the browser language as fallback for resolving message properties, but instead show the missing property keys.
Associations of reference models have not been exported at all. Now only the mapping associations of reference models with other processes are omitted because this could be a big amount and then it would take too long to import the reference models.
error.log was created but not used
Preserve file encoding of metamodel properties files, instead of using default encoding of OS.
When Stages was installed to another path than "/opt/stages" on Linux, the service did not startup successfully because the path "/opt/stages" was hard-coded in the service unit file "stages.service". Now other installation paths are supported. Known limitation: The installation path must not contain whitespaces.
The filter in the workspace navigation was not cleared when navigating up or down.
Clicking the star icon for adding a workspace favorite had no immediate visual effect
Filtering of workspaces in the "My" tab was broken. Now the favorite workspaces can be filtered again.
PDF file name was no longer retrieved from the metamodel properties.
Fix resolution of metamodel specific message properties.
Fixed path to CSS for PDF printing.
Assignment of issue property can now be...
When you switched between different execution elements of the same type, adding new process element associations did not work when the menu entries from the card menu of the widget were used.
Fixed feedback issue creation with PTC-ILM 12
Images migrated from V6 can now be resized to their perviously specified width and height, fixing the respective image map, by use of the command: resizeImageResources.bat/sh (-w <workspace path>) (-recursive)
Adapted image sizes from image resources were ignored on import into V7 resulting in wrong image maps.
When a process .zip export was transferred between Stages servers with different values of the "supported.languages" property, the element names were not adjusted
Users without process version read permissions were allowed to copy a process into an empty workspace not being able to see the result.
In association subgroups it was possible to select an element which was already assigned again for a new association. This led to an error.
Dependent elements can now be translated immediately after creating them, not resulting in an internal error
It was not possible to assign a dependent element in case a subtype restriction was used for the association widget.
Process interfaces of process versions were lost in a certain complex module update scenario.
In some situations, unwanted associations to overwritten elements were created when updating a process module.
Association browser did not use the correct process version when an older version of an on-demand process module was installed.
Dependent elements were not correctly displayed in process interface list
The links for the "work on it button" in emails will now work for process versions that have parentheses in their names
Sending emails during a workflow execution could fail. Now the execution is more stable.
The Approval History of System Steps which were not successful and had no failure transition modelled was wrong. Now the correct state in the history is shown.
Reassigning a task to a user who is no participant created a wrong approval history entry. Now there is no participant connected to this history entry instead of the initial step participant.
The tailoring forced visible flag was not set for subelements of elements added back into the process.
Associations from tailored dependent elements were not displayed stroke through.
No process versions could be created when the metamodel of the process had no validators configured
No new validity record was written for the working version when it automatically became valid on deletion of the valid version.
The changes of an integrated user role in the working version was overwritten by the integrated module when a new valid version was created. Now the changes in the working version are preferred.
Lazy links in image maps were not correctly rendered under Management > Descriptions.
Workspaces variables in the values of workspace variables were not replaced.
Associations widgets that referred to indirect element children in the association path syntax (like "activity:children@SYSTEM(10)|artifact:output") did not display all associations any more
In a rare scenario when associations with identical target elements were combined, the subtitle "From multiple workspaces" was not shown.
Icon was not changed when association subgroup was collapsed.
Role subtype Team was not displayed with the correct icon
When you selected the valid process version in the version switch ("_vv" parameter in url) and clicked on a local process element in the process visualization, the url was changed so that it referenced the current process version by its name and not generally the valid version ("_vv") anymore.
Client connections will now be closed and there should be no logger warnings about Resteasy automatically closing client connections anymore
Rendered report output could not be larger than 10 MB.
In some cases just a generic error message was shown instead of the root cause message of the reporting error.
Switching from reports with parameters to a report without parameters produces wrong report menus. Now the menu is correctly activated.
Search hits for dependent elements (e.g. quality levels, states, ...) now show the appropriate subtype icons in the search results page if an icon is available. Otherwise the default icon (tag) is shown. Additionally, if the search hit was in the description of a dependent element, now the dependent element name is also show in the search hit on the search results page.
When the description of a dependent element (e.g. quality level) was changed, you could not immediately find it by searching for a term from the changed description.
Results flyout of search input field was not closed in various locations where different kind of selections could be made. At some locations this led to conflict errors when the same icon was selected twice.
Update dependency jquery-ui to latest version 1.13.1
Process usage charts are now accessible only with process management permissions.
Update front-end dependencies: Migrate akita to elf and rxjs to version 7.5.5.
Update tomcat to version 8.5.76 for security fixes
Log4j 2.17.1 is now used for Stages itself
The list of used Open Source components (with their exact versions) is now loaded from the backend and viewing it in the Administration dashboard requires "Read" permissions on the "Maintenance" permission domain.
Exchange ElasticSearch Log4j JARs with version 2.17.1
Card was collapsible with the description editor opened.
Mozilla stopped supporting webkit selectors for scrollbar styling. This fix aligns the Firefox scrollbars with the general product design again.
Profile settings header was not able to display long usernames
Updated feedback and cms adapter
ensureProcessIntegrity is now deleting orphaned "diff" table entries
Fix loading of changelog icons
Long workspace names broke dialog layout in description editor plugins
Entering dependent element names with "|" characters in the name led to an internal error on save. Now these characters are not allowed in the input field anymore.
When identical associations with dependent elements from multiple workspaces were combined, the links to them did not work.
When a dependent element (e.g. work product state) was renamed and you search for this element in the global search, the corresponding search result still showed the old name.
Exchange ElasticSearch Log4j JARs with version 2.17.0 and delete SQL CLI JAR
It is now possible to create associations with dependent elements as source elements.
In some cases participant elements had the wrong users assigned
An error occurred when more than 200 users were assigned to a user group and some user-group assignments had no creation date in the database
Cyclic MySQL table optimization failed with the MySQL connector 8.0.27.
File download from SharePoint Online failed if the Stages URL in the browser contained "index.html".
The "Comments" tab was displayed (and showed "None") even when the user had no permission to view process element comments.
Tooltip was missing on navigate to child button in navigation drawer
Now it is possible to check if dependent elements are configured via 'element.getPkitClass().isAssociationValid("hierarchy::HIERARCHIC@LOCAL,targetRole=dependentElements")'.
Elements can be tailored via an API command: command.newScriptTailoringCommand(process, tailorAdd, tailorRemove, justification)
Target elements of associations have the property "Combined". Its value is "true" multiple identical associations hav been combined.
Workspaces can be created by the following API command: commands.newCreateWorkspaceCommand(targetParentId, workspaceName)
The tailoring wizard can now be executed by a script: commands.newAutomateTailoringWizardCommand(targetWorkspaceId, selectedAnswers).execute()
Workspace variables can now be saved by a script: commands.newSaveWorkspaceVariablesCommand(targetWorkspaceId, variables ).execute()
Process module installations can now be updated by a script: commands.newUpdateModuleCommand(workspaceId , installationId).execute().
Process versions can be created/deleted by the following API commands:
commands.newCreateProcessVersionCommand(targetWorkspaceId , versionName , stateTypeIdent , releaseAsValidVersion);
commands.newDeleteProcessVersionsCommand(targetWorkspaceId , versionsIdsToDelete)
Processes can be copied to an empty workspace by the following API command: commands.newCopyProcessCommand(targetWorkspaceId, sourceProcessId).
Process modules can initially be added to a workspace by the following API command: commands.newAddModulesCommand(targetWorkspaceId, moduleSelections).
Now we can get the dependent elements of an element with 'element.getEntities("hierarchy::HIERARCHIC,targetrole=dependentElements")'. The container element of an dependent element can be retrieved with 'getEntities("hierarchy::HIERARCHIC,targetrole=containerElement")'. Additionaly dependent elements return "true" as value of the property "Dependent".
Update freemarker to latest version
Added name and type to feedback mapping
The workspace collection memberships are now used on process import, when process modules are added or updated and when processes are copied into empty workspaces.
The user now needs to confirm the creation of a new dependent element with a name that already exists
Dependent elements can now be translated
Dependent elements can now be sorted alphabetically or custom. The initial sort order is the order they got created.
Associate new or existing dependent elements via "quick-assign" search box in association widget
Adding a dependent-elements-list widget to the metamodel.
Created a new widget for viewing and editing dependent elements
If the working version is the valid version and the valid version is selected in the version selection, the version will be treated like other valid versions (modeling is prevented)
A "Show Changes" button is now displayed in process release notification emails
When a new Working Version is initially created in a workspace, now additionally an empty Valid Version is created. This avoids complex situations in process element views that occur when the Working Version is also the Valid Version. Moreover process viewers now will see the empty Valid Version instead of the unreleased Working Version process until a new Valid Version is oficially released.
Display associated dependent elements in association lists with links to the process elements to which they belong to.
If the working version is the valid version, the version selection now has two entries for the working version (valid working version and working version).
Visualizations are now collapsible.
Process elements now can also be found by names and descriptions of their dependent elements (like maturity levels).
Global search now finds process elements by custom attribute values (types: "STRING", "TEXT", "INTEGER" and "SELECTION") without having to adapt the metamodel for this. However, if you don't want certain attribute types to be included in search, you have to set 'searchable="false"' on their metamodel definitions.
Stages now provides alt tags for all image elements, labels for form elements, proper structured html hiearchies for lists, a lang attribute on the html element and attributes on interactive elements that improve the readability for screen readers. The code monitoring to keep the functionality on a high level will be done by a ESLint accessibility rule set.
It was not possible to get information about user-participant associations for workspaces
It was not possible to control if the remote associations were retrieved to working or valid versions via stages#getAssociations. They were always filtered by the currently viewed process version (Associations with working versions were returned when you were in the working version or the current process version was never valid before. Associations with valid versions were returned when you were in the valid version). Now you can call getAssociations with last parameter "_wv" (getAssociations(sourceProcessIds, targetProcessIds, sourceElementTypeIdent, targetElementTypeIdent, associationTypes, "_wv")) when you want to get all associations with working versions. Set last parameter to "_vv" if you want to get all associations with valid versions. Set last parameter to "null" if you want to get associations to all process versions unfiltered. If you call getAssociations without this last parameter the behaviour will be like before.
stages#getAssociations always returned 0 results
Changing file stream API to not need a revision for a file in stages db
License agreement was not accessible from the administration dashboard.
Non-ASCII characters where not properly encoded in maintenance mode notification emails
Switching the time range in the user session or user base diagram on the Administration dashboard sometimes led to an error.
Errors could occur when displaying or editing permissions for a user group when one of the permissions referenced a workspace that was being deleted.
Derive file management plan script was not able to create cms file path for guidance elements
"Browse" for role assignments on a user group was unresponsive when a large number of roles was assigned.
When switching the workspace language and converting a workspace from multi-language to single-language simultaneously, the process element names are now changed to the names in the new language.
The roles of a permission group could not be opened fór assignments to processes marked as deleted.
Groups and Permissions administration was not usable in case thousands of roles or users were assigned to a group.
Workspaces could not be moved anymore.
Ensure HTTP-Session on SSO authentication
Added saml.response.notBefore.tolerance.millis configuration property to handle IDP - SP sync problems with unclear root cause.
Improve SAML IDP response validation.
Set the default value for config property "autologin.username.allowAtCharacter" to "true" for new installations
SSO / SAML usernames were truncated at the "@" character. Now, this behavior can be changed by setting the config property "autologin.username.allowAtCharacter" to "true". The current default value is "false" for backwards compatibility.
Template for SAML username and email
The left navigation was not filtered any more in compliance mapping mode
The "migrateMultiLanguageProcesses" script did not merge names and descriptions for Guidance elements that were not migrated Stages 6 resources. This could happen if the metamodel migration script ("migrateMetamodel") was executed before the multi-language migration.
When a reference model was referenced by a process model using only local scopes in Stages 6, the database upgrade did not create a reference model assignment. Now, in this situation, the upgrade will create an assignment of the scope that was the default workingset of the reference model in Stages 6.
In the directives plugin of the description editor the insert buttons were inactive.
Table zoom was not shown after changing tabs in the landing page.
Border formatting was not visible on all borders of a table cell when the border width was set to 1px
Upgrade CKEditor to version 4.16.2 for security fixes.
Artifact instances with process id null lead to an error when executing the script. The script now ignores artifact instances where the process_id is null and logs a warning instead
Investigated exception in AESCryptoUtil.encrypt() after login
Fixed improper web socket connection request handling
Multiple versions of cmd-lib/stages-cli.jar and tomcat/lib/stages-containerauth.jar existed after upgrading Stages 7.7.x to a newer version on Windows.
Stages upgrade via RPM failed in case stages was not running.
Fixed button color for multi-delete of tailoring and enactment elements
The copy / paste mode of descriptions was closed when the user navigates to other workspaces. Now the clipboard stays open as expected during the workspace navigation.
Diff markers were shown on all perspectives even though changed associations were viewable only in specific perspectives.
Performance improvement for deleting process elements with change markers.
It was possible to remove associations in the "Execution Configuration" widget in valid process versions.
HTML escaping was erroneously applied to enactment script code in "script" and "script library" resources when importing a process that was exported from Stages 6
Image maps were lost when importing a process that was exported from Stages 6
Fixes a no Access Error when sorting description templates.
Process version switch was not working on management pages.
migrateMetamodel script did not consider process element translations.
Reflecting changes to the sort order of associations immediately in the visualization
Changing process perspective via toolbar is now possible again
Links to anchors with a quote in the name lead to an Internal Error.
Menu entry for translation of management descriptions was missing.
Push updates for installed process modules were automatically enabled when process versions were created.
Only adopt Tailoring queries and answers in case the whole parent hierarchy matches.
Add button in visualization was missing on core protected elements
Link to process elements were not displayed correctly in emails generated by a "Send email" automation step.
A process version state change associated with an automation task was ignored when the user completing the task did not have sufficient permissions.
Older versions of executed workflows could lead to duplicate entries in the approval history of process versions.
In certain cases it was not possible to abort a running process release.
Task could not completed when scheduled release date was assumed from another task.
The variable for the process version description (%VERSIONDESCRIPTION%) was not replaced in email notifications.
Changing suggested process release time to be in future
Switching off the "show tailoring details" button now correctly removes the tailored elements from the navigation
No clear error message was displayed in the process version readiness check when web sockets were not supported and no readiness check results could be received.
API v1 process validity returned outdated process version name.
Tailored identical associations were inconsistently shown strike through in the association list and the association browser.
When a remote association existed between two multilingual workspaces, there were a few cases in which the remote element in the visualization was displayed in a different language than in the association list.
Clicks on internal lazy references within image maps resulted in a reload of the whole page.
Process element views could not be loaded in special constellations when they contained derived associations with comments.
Scrolling on a process page while the visualization is loading leads the view to the top of the page when the visualization finished loading. Now the scroll position ia preserved.
Requests from the reporting webapp did not have an origin header and were therefore rejected by CSRF protection.
Could not enter valid value for report parameters of type "time" in Chrome browser because seconds could not be entered
Report parameter were loaded from previous reports. Now the parameters for the current selected report are displayed correctly.
Some changes were not immediately reflected in the search results: Children of deleted elements could still be found for some time. Parent elements that were imported with one of their children from an on-demand module could not be found for some time.
Search for workspaces by name requires too much input to find workspaces.
Target element search in association list found folders when the targetSubtypes were not restricted by the metamodel. Now folders will never be found there.
All elements in a workspace were found when you searched for the workspace name in the global search. This produced many irrelevant results. Now elements will not be found by their workspace names anymore.
Removed plugin for the search of German compound words. Search indexes will be rebuild. It may take some time (dependent on the size of the database from some minutes up to a few hours) until this is completed and everything can be found again.
Exact search (when the search term is put in quotes) found inexact hits based on the same root words as the search term.
When the searched term was found exactly in an element description, the corresponding search hit was shown after inexact search hits in element names.
Readiness check for process versions didn't show results.
The origin header verification could not be disabled selectively. Now, this is possible by setting the new configuration property "global.secureMode.enableOriginCheck" to "false".
Reviewed some settings for report upload
The "Strict-Transport-Security" header could not be disabled selectively. Now, this is possible by setting the new configuration property "global.secureMode.enableStrictTransportSecurity" to "false".
Set the default value for configuration property "global.secureMode.IEAccess" to "no_one" to prevent Internet Explorer usage due to its inherent security risks.
Reviewed some settings for replacing working versions and release automation
Update tomcat to version 8.5.72 for security fixes.
Email addresses are now validated additionally at the backend.
Object deserialization was potentially unsafe for some objects
Sanitizing of uploaded .rptdesign files (also as database upgrade step)
It is now checked that WebSocket requests have their origin from the same site (CSRF protection), unless IE access is allowed via the configuration property "global.secureMode.IEAccess". If the "origin" header field is set, the value is checked in any case (i.e. independent of configuration settings and browser detection)
It is now checked that modifying requests have their origin from the same site (CSRF protection), unless IE access is allowed via the configuration property "global.secureMode.IEAccess".
The access with Internet Explorer has been restricted due to its inherent security risks. There is a new configuration poperty "global.secureMode.IEAccess" with the possible values: "no_one", "non_root", "all_users". The default value is "non_root" which disallows root access with Internet Explorer.
Image map markup is now sanitized at the backend.
Reject authentication attempts when currently delaying the response for a previous failed authentication attempt ("tarpit") and use this mechanism in additional places
Rich Text cleanup is now invoked for step descriptions when importing a workflow XML export
Rich Text cleanup is now invoked for translated descriptions when importing a translation .zip export
Rich text cleanup is now invoked for all descriptions when importing a process .zip export, and when custom rich text attribute values are displayed. Set the config property "import.description.cleanup" to "false" to opt out of this.
Cross-site scripting (XSS) was possible on IE11/Safari in richtext descriptions
Do not store passwords for CMS and remove already stored passwords
"Release Notes" and "Latest Changes" now have a link icon and text instead of a download icon and text
Fix Stages start in Linux non-root environments
Creating a diff for an entire process failed when an exception occured during the comparison of a single element. Now, this exception will be logged and an error message will be displayed instead of the diff for this element.
Fixed missing codebeamer dependency
Additional fixes related to ST-33517 for IE 11
API call 'getEntities("containsCoreProcess@SYSTEM,sourcerole=CoreProcess")' did not return any process when it was called on the Valid Version of a process module and the process module was not installed in Valid Versions, only in Working Versions of other workspaces.
It was no longer possible to create a PDF of a process in case the user had no modeler license.
When you opened the browse view for associating execution elements (e.g. activators with scripts), the root node (e.g. Scripts) was displayed as it was possible to navigate one level up from it.
Keep current version name in url when navigating to other local elements via process visualization diagrams or association lists
When an image file name contained multiple whitespaces in succession and the image was added to a description (e.g. description of a process element), the image was not show after the description was saved.
Firefox asked for the login credentials again when running a report that contained an image (for example, a chart)
Chinese, Japanese and Korean were not configured for the participants search (at user groups).
Users could not be found by their names or email addresses in some constellations when the terms contained underscores or hyphens (e.g. could not find user 123_test when searching for test and could not find user 123-test when searching for 123_test).
Workspace search could not find workspaces with underscores in their names (e.g. 123_MyProject) if only the part after the underscore (MyProject) was entered into the search field.
Fuzzy search for workspaces did not work when it was activated by setting the config property "search.workspaces.fuzzy" to "true" ("false" by default).
In external links of process element descriptions and in file properties, URLs were not validated. Invalid URLs caused subsequent errors (e.g. when they should be exported to Excel by a report). Now the URLs are validated with this pattern: "^[A-Za-z][A-Za-z\\d.+-]*:\\/*(?:\\w+(?::\\w+)?@)?[^\\s/]+(?::\\d+)?(?:\\/[\\w#!:.?+=&%@();\\-/]*)?$". The pattern can be changed with the config property "url.pattern".
The workspace navigation in the association browser always opened the favorites tab. Now the last opened tab is stored and preselected.
The date time picker was not correctly positioned after window resize.
If an activity was associated with another activity as predecessor and successor, the diagram showed only one of these associations.
Fixed XSS vulnerbility in reports.
Added chinese, japanese and korean search configuration.
The transferMappings script did not consider the target workspace parameter (-t) in case of ratings. When you specified a target workspace (!= *), compliance ratings (coverage) were created for the new reference model from all processes that had ratings for the old reference model.
Landing pages were editable for users that have no permission when a user with permission was logged in before on the same browser.
It was not possible to allow state changes in a file lifecycle definition with the rule "Role:Project".
When cms credentials needed to be entered in order to change the state of a file, to upload a new file version or to create a new file from a template, an error headline and an additional cancel button was shown. In this case, files from templates could not be created.
If a process metamodel ident contained uppercase letters in Stages 6 and this process was exported, it could happen that files which had lifecycles assigned in Stages 6 got no lifecycles assigned on import into Stages 7.
Process element names and descriptions could not be translated to Chinese via "Translate" dialog.
An association target search hit in a related workspace is now filtered away if there is a search hit with the same identity in an on-demand module, because importing the on-demand element is preferred to creating a remote association in most situations.
Precondition: A process module was installed as on-demand module and push updates were enabled for the installation. Error: After an element from the module was imported by creating an association to the module, the push updates were deactivated.
When a manual step had a step description, the step description was displayed in place of the process version description in the task details pop-up.
Clicking on a visualization item twice made page scrolling impossible.
The Tomcat version information was shown on an error page in case of a bad requests due to an invalid URL.
Workspaces can now be deleted by the script deleteWorkspaces.bat/deleteWorkspaces.sh. They can be specified by paths and ids.
Associations of target elements with same identities are now "combined" as it is done in the association lists of process views too. This means that only one association is returned when their are actually target elements with the same identities associated. In this case, the new association property "Combined" has the value "true".
Exchanging the left and right y-axis of the administration user sessions per day chart for easier readability.
Hashing algorithm for local passwords now complies with NIST and FIPS-140 standards
Added new mode to the transferMappings script. Set option -m="identities" when elements in the new reference model shall be found by identities instead of explicit mappings between new and old reference model elements.
You can now opt out of the default table styling change that came with version 7.6 (ST-32901) for a single table by setting the "stages75" CSS class in the table properties dialog
Implement optional script evaluation on feedback submission.
Introduced new permission domain "PDF Export" that controls in which workspaces PDF document creation from processes and process elements is allowed. By default it is allowed in all accessible processes.
Added feedback link system type
Multiple feedback systems and hosts can now be configured in config.xml
<widget:index> can now be configured to hide the shortname of an element (set "hideShortname" to "true")
Migrate Metamodel script is able to migrate attributes to a different attribute type, including mapping of attribute values for a certain data types.
Process Element Associations can be sorted now
Push the core process association sorting only in case it was changed in the core process since last update. In case of module updates from a working version of a module the sorting is always pushed as the previous state is no longer known.
Manual automation step now contains a switch for allowing users to schedule the process releases by setting a date via a date picker on user tasks.
The process versions to display process interfaces for are now determined in the following way: Interfaces with working versions are shown when you are in the working version or the current process version was never valid. Interfaces with valid versions are shown when you are in the valid version.
Combined associations can be sorted now.
Associations with identical target elements from different workspaces are now shown only once in association lists.
When associations are grouped with "group-by" attribute in the metamodel, all associations that do not belong to a corresponding subgroup are listed in the subgroup "Other". Now the message property for the name of this subgroup can be configured in the metamodel at the corresponding association-list or association-group element by the attribute "translateOther".
Associations can now be grouped (e.g group activities assigned to phases by their parent elements or group activities assigned to roles by the phases they are executed in). For this purpose the "group-by" attribute is used in the metamodel on "widget:association-list" or "widget:association-group".
Reports can have a security level now: You can only view and execute reports if you have the "Reports" or "Report Administration" permission in any workspace with the appropriate security level. For report edit actions you need "Report Administration" permission for the desired operation (create, modify or delte) with the appropriate security level in any workspace.
Added a shadow to the search flyout to
increase contrast
Creating a new association via quick assign will now prompt the user to confirm the creation, if there is already an existing element with the same name.
Mozilla's "Intermediate" HTTPS configuration is now used in server.xml in new installations, see https://wiki.mozilla.org/Security/Server_Side_TLS#Intermediate_compatibility_.28recommended.29
It was not possible to retrieve the creator of a process version via the facade v1. The process now has a property named "Creator".
When a process was deleted which once was the valid version, trying to retrieve the process or process id from the validity element via API lead to an error.
It was not possible to retrieve process version validity information via API.
Upgrade failed for large Oracle databases with ORA-300036.
MergeUserGroups script failed with Oracle database.
In case password form login is disabled, the license limit exceeded error message was never shown.
Fixes error handling for administrator notification emails.
Database upgrade steps 5022 and 5248 could run very long when there was a huge amount of records in the table "target".
Database upgrade failed with JDBC drivers for Oracle 11 or older (e.g. ojdbc6.jar, 11.2.0.4).
Files on index elements caused an error in the search indexer and are not supported in the UI. Now, there is a new "ensureDatabaseIntegrity" step (11) that moves these files to the LOST+FOUND element
Oracle error ORA-22275 could occur with some databases in content upgrade step 4429 (UpgradeComplianceRatingsAndExternalMappings)
Links to anchors with a quote in the name lead to an Internal Error.
Some message properties for the search flyout in the link plugin werre missing.
Allow more than one document type in SharePoint Online
Fixed error for default Sharepoint Online document library and document libraries with spaces
Unknown network errors (status code 0) directly resulted in an error page
Make Content Security Policy (CSP) response header even more restrictive to guard against cross-site scripting (XSS) attacks. (see https://infosec.mozilla.org/guidelines/web_security#content-security-policy)
Upgrade failed for large Oracle databases with ORA-01555
Creating a pdf with base64-images in descriptions will now include those images. Creating a pdf with an empty visualization no longer prints an error to the log.
Menu entry for Overwrite was not filtered away in cases where overwrite is not possible.
It was possible to edit process attributes of the process start page in a baseline.
An error occurred when creating an element with a name starting with more than 32 characters followed by a ":"
It was not possible to open a linked description element for editing.
Working version was selected instead of valid version when adding modules
Removed "containsTask@SYSTEM" association on ApprovalHistory facade element because it will always throw an error after the fix to ST-33263 in 7.6.2.2 (tasks no longer exist in the database after a workflow has been completed)
When importing an automation that was exported on another Stages server, the recipient of the "Send E-mail" could be set incorrectly.
When a workflow was started with local participant-to-user assignments in one workspace, and then started in a second workspace, the participant-to-user assignments from the first workspace were used instead of the global ones (or those in the second workspace)
When starting an automation, the global participant-to-user assignments were displayed instead of the local ones.
The compliance reference associations had a random ordering. Now they are sorted regarding the element index.
Rendering of descriptions containing image maps with a number of references was slow. Now it is possible to configure by which number of image areas, references will be resolved lazily (use configuration property "process.description.imagemap.lazyeval.threshold").
Images with an image map that were the parent element of a file-based resource in Stages 6 were migrated to Guidance folder elements for which the image map was displayed as a description which caused various problems in display and PDF export.
Reduced log level for textual reference fallback queries from level warn to level debug.
Could not open file urls in search results if they contained whitespaces
When the workspace filter on the results page was changed and the user clicked into the search input field again, the workspace filter was not applied for the results in the flyout.
Update tomcat to version 8.5.68 for security fixes.
Allow external iframe source (e.g. videos) for Content Security Policy (CSP) by adding space-separated domains or URLs (https://www.w3.org/TR/CSP/#directive-frame-src) to the configuration property "global.secureMode.csp.additional.framesrc".
Fix the Content Security Policy to allow only images from the Stages server. In case external images are needed in Stages, additional domains can be white listed via configuration property "global.secureMode.csp.additional.imgsrc".
Remove Access-Control-Allow-Origin:* for font loading as it is no longer needed.
Change markers were not shown in visualization diagram in non-multilingual workspaces when the user language was not the workspace language
Improved accuracy of user group, scope and participant search results.
An error occurred when trying to insert a link in a landing page description in Stages 7.6
Collection of the user session statistics caused unnecessary database statements.
Fix parsing of config.xml for enabled saml and secure.cookies property.
Upgrade failed when no message properties for process version states were configured.
Upgrade CKEditor to version 4.16.x for security fixes.
Tab Key is now working on external link page from link-plugin
Copy & paste of internal links into the description editor led to broken links.
In the editor link plugin the selected link target was not automatically scrolled into the view
Native browser spell checking was disabled for the description editor.
Could not link to anchors with ampersand characters in the name.
Could not link files from subfolders or subprojects of Integrity development paths
CMS error dialog can now responsive display long error messages
In some cases, the CMS file progress spinner was not shown after triggering a file action.
Fixed multiple prefetch of same file and repository
The "No Access" error page was show for file operation conflicts (e.g. when somebody tried to lock a file that was already locked). Now the actual error is shown instead.
When creating a new file from a template, files of templates that the current user was not allowed to read could be used.
Some validation errors were not displayed in the repository edit forms for Integrity and Subversion.
In some MS Office documents, "#" in links may be escaped to "%23". Stages is now able to redirect these links to the correct Stages URL.
If you have this problem in an existing Stages installation, insert the following inside the "/stages" context in conf/server.xml, after the first "Valve" element:
<Valve className="de.methodpark.stages.containerauth.FixMsOfficeLinkValve"/>
Fixed breeadcrumbs for editing descriptions and editing elements
Fixes phase freeze overview widget as well as updating of the process visualization after a phase is frozen.
Change marker was not shown on description menu entry below management.
An error occurred when editing elements when no proces state with the name 'Draft' existed.
Fix missing refresh of navigation after a process element is deleted.
Guidance elements with mulitple files pointing to the same URL were not updated correctly.
An error ocurred in Management > Process Modules > Added when attempting to delete existing module installations and failed module installation attempts together using multi-delete.
Various errors occurred when executing automations when no states were defined at all, or when the state that was set for a "Create process version" or "Release process version" step was deleted.
On workflow start all participants were shown for a workflow with a user step without participant.
Descriptions of tailoring elements were not refreshed properly after translate
Changing the "process.metamodel.default" configuration property could affect the visibility of elements and associations in old process versions when the metamodel was never set explicitly for the process. Now, the metamodel is set explicitly to the default metamodel for all processes in the database where it has not been set explicitly, and for new processes.
It was not possible to delete existing process versions and failed process version creation attempts together using multi-delete.
Creating a process version was possible while modules were being integrated into the working version and lead to an incomprehensible error message. Now, the "Create process version" button is invisible while a module integration is running in the same workspace.
The data for the process start page was loaded twice, resulting in unnecessary page load time.
Attribute default values are now longer shown in the process view. Attributes with default values can now be resetted to an empty value.
Popular process element widget didn't display element abbreviations.
Image map areas had a thick black outline when focused in the latest versions of Chrome
Visualization zoom toolbar was overlapping container border. Tabs are now scrollable
Optimize visualization rendering performance under high load.
It was not clear that a report with an error was not uploaded at all. Now the error message is clear and the error marker is red.
Focussing a new report while add mode is
active is now possible
Fixes several report view refresh issues during report hierarchy modifications.
Start step could not be saved if there were no states available.
Searching reference elements in the compliance widget of a process element sometimes produced no results when there should be results. This happened for example when only few reference elements were in the mapped compliance scopes and you searched for frequently used terms like "Determine".
Elements could not be found by certain terms in their names like "IT", "FOR" or "TO" because these terms were ignored (stopwords). Now this is possible and these terms are only ignored for the search in descriptions.
The process version switch was changed to default when a new search was executed from the result page. Now the defined process version is preserved on further searches while the result page is open.
Reload of search result page with multiple filter categories returned no results
Element type search filter was always resetted when modify the search term
The "Results in other workspaces" section in the search flyout caused confution. Now you can restric the search scope to the current workspace or extend it to all workspaces if there is a chance to find more/better results.
Set client ident cookie secure
Stages restart was sometimes displayed as errror message to the user. Now the user is always redirected to the login page.
In various forms (e.g edit process element, edit process, edit workspace, checkin file) it was not always easy to see why the submit button was disabled when a required field had no value and there were many fields. Now the submit button can be pressed and, in case of missing required inputs, the page is scrolled to the first field with an error marker.
Push updates now are disabled by default for new and existing module installations.
It was not possible to migrate comment only associations that do not contain textual references. Restored frontend validation for all whitespace passwords.
Update tomcat to version 8.5.63 for security fixes.
On user administration page it could happen that some users were not visible when the viewing user had no transitive permission to create modify or delete users.
It was no possible to enforce password rules. This can now be done via properties "user.password.regex" and "user.password.minLength".
Runtime information did not contain all needed log and configuration files when Stages was upgraded from an older version than 7.4.7.0 or 7.5.3.0.
Fixed rendering of images and links in query table
Stages startup failed when it was upgraded from V6 to V7 and the database contained "ProcessDeletionJobs" for module import preview baselines.
Process version readiness check did not report broken links in image maps.
An empty diff was displayed for users that could only see the valid version when "Show Changes" was clicked in the "new valid version" notification and "_wv" was in the URL
When the execution widget on a process element page showed a warning and the warning popup dialog was opened and closed again, the page content on the right was hidden below the perspectives toolbar.
When the user opens the add modules dialog after he already added a module an Error was thrown.
When a compliance sensitive element was tailored in the confirmation popup the background color was almost the same as the highlighting cover.
Resolving of textual references to image resources migrated from V6 was slow.
When an association group with derived associations was defined in the metamodel, and a derived association had multiple original associations pointing to the same target element, only one of the original association comments was displayed. Now, all association comments are displayed, sorted by comment text and separated by ", "
If an associations or execution widget on a process elements page had closed sections, the sections were shown as expanded for a short time when the page was loaded. Then they were closed again.
Back button on remote description popup view was not working correctly
An error was shown if a user started the first time a process compare from the to-do-list on the dashboard.
When the navigation drawer was open on a smartphone, the search icon (magnifier) was visible but the search bar was not opened when it was clicked. Now the search icon is not shown anymore when the navigation drawer is open on a smartphone.
When a user group was associated with multiple roles in multiple workspaces that originated from the same role in a process module, every role was displayed only once in the "Roles" tab when viewing the user group.
Fixing logout by returning clear LogoutResult instead of null
Using the browser back button in management and administration not updated the navigation drawer.
When a process module working version was installed somewhere and then the Working Version was replaced by a Zip import of a different process, the module management page showed a wrong version name for the module installation.
The search index was not updated immediately when a participant was added, deleted or renamed. This lead to the following problems when trying to associate a participant with a user group:
- Newly added participants were not found
- Renamed participants were not found when searching for the new name
- Deleted participants were still found and an error occurred when selecting them
When config property "import.project.attributes.from.modules" is set to "true" and a new valid process version is released, project-scope attribute values shall not be overwritten by the values from the previous valid process version.
Enabled feedback and comments in compare view.
It was not possible to use the process execution export in case the Stages server is not able to access its public URL. Now a localhost connection can be used. This needs to be configured via property "processor.serverAddress", e.g. http://localhost:8080.
Adding associations from workspaces in the same workspace collection could run into an error when the working version was equal to the valid version in the local workspace and different in the remote workspace
The workflow steps of running workflows in process version management page were not sorted in the order in which they were actually done.
The tasks in the active workflow view and the approval history were not explicitly sorted. Now they are sorted by the date of creation.
Compare process versions button in the task details was clickable without Process Version READ permissions.
Renamed workflow to automation.
Workspace could be added to workspace collection multiple times.
Compliance mapping widget in Management section showed "In other workspaces" category.
In the Compliance Mapping View, it was possible to select other elements than defined in the scope. The elements were not added to the mapping but it was a lack of clarity. Now only elements in the compliance scope are selectable for the mapping.
Many irrelevant error messages were displayed by ensureDatabaseIntegrity for Stages 6 resources that were migrated to description or Guidance elements ("Non pseudo element resource found without realid, contentid and url")
Progress dialog for process comparison had no title
Fixing error by disabling button when user hasn't the required right
Workflows failed and version page was not accessible after a state of a running workflow has been deleted.
In the Release Details now the user is shown the Decision of the Step instead of the new State of the Process Version.
Could not upload images to landing page descriptions anymore
Continue button didn’t work when replacing the working version
Readiness check showed wrong warnings about too many responsible roles in the following case: An activity was assigned to a role from a remote process. The local process was both: Working and Valid Version. The remote workspace had different Working and Valid Versions and the role with the assignment to the activity existed in both process versions.
When the valid version of a process module is added to a process, now the installation can be updated with the same valid version again. This is for example helpful if you want to check whether previously shown warnings are resolved.
Editing long Enactment-Scripts no longer results in weird scroll behaviours.
The selectable associations in the association browser were not filtered regarding the defined type in the MetaModel.
History entries for history entries were created.
Task with empty comment could not be approved.
Process review and approval is now part of the Stages API / facade.
[Internal] Improve Tomcat SSL and AJP connector configurations: disable TLS v1.1, disable reverse lookups, limit list of ciphers
Updated link to online online help.
Improved the default style for tables created in the rich text editor, tables are now displayed with cell borders by default.
The maximum number of parallel background operations (e.g. creation of process versions, process module updates) was limited to 40. Now you can change this number with the config.xml property ("global.backgroundJobThreadPool.size").
A permanent banner can now be displayed at the top of the Stages application using the config property "global.main.showBanner". The banner text is set using the properties "global.main.bannerCenterText" and "global.main.bannerLeftRightText" in local.properties. HTML can be used in the values of those properties.
The users name and date of pdf creation can be added to each pdf page as a watermark. This needs to be enabled via config property pdf.watermark.enabled=true.
If config property "import.project.attributes.from.modules" is set to "true", project-scope attributes will be imported and updated with process modules.
The push module update system step is now pushing the current version instead of the last valid version
Preferred process workflow can be set
In the richtext input fields for edit step and start workflow it is now possible to use the link plugin and the html-template plugin.
An escalation time can now be set for steps. Users that are assigned to tasks derived from the step will receive an additional email message when the escalation time has passed, and the to-do item is highlighted in the dashboard.
Process version name will be validated on workflow start
The Release Detail View should show less detailed data regarding the history of the created processes.
Adding "Push module update"-system step to process release workflows
Compare button in task details dialog was hard to find, compare is now outside the dialog in the to-do list available.
Due date is now part of the template model for emails.
Due date is shown in task details.
Process element type names were resolved from the methamodel of the current process instead of the metamodel from the process element.
In user group administration the input fields for filtering the user/roles list and adding users/roles by typing had the same placeholder text. Therefore it was not so clear which input field had which purpose.
Workspace deletion failed when there were local participant-to-user assignments for this workspace
Changing state name limit to 32 characters
Deleting broken and unused scripts migrateResources and migrateSubversion
">" was prepended to the root workspace name in Administration > Workspaces > Collections
In the Compliance Mapping View, it was possible to select other elements than defined in the scope. The elements were not added to the mapping but it was a lack of clarity. Now only elements in the compliance scope are selectable for the mapping.
The error message "Required" was shown twice in the file properties dialog when the name filed was empty.
Adding new policy to check if user is allowed to change/update file repository authentication
It is now possible, to download files in subversion via the file history regardless of the current repository configuration and added user based caching for documents
No file state was selectable in "Set state" dialog if the file had no state in the repository.
Added missing message property to mobile view of file revision history.
Multiple instances of "database optimization" and "temp directory cleaner" background threads could run at the same time. This lead to less available worker threads for other background operations (e.g. file uploads, process version creation, process module update) and - in the extreme case - these operations had to wait.
Continue button in compare dialog was scrolled out of view.
Fixes no access errors in management execution.
Association browse dialog could not remove property or script association from activator or vice versa
An exception occured when attempting to import a v6 .zip export into v7 that was part of a multi-language workspace group
Replacing the working version with a .zip import failed when the process had project-scope attributes
Not configured element types created too many log entries.
When the valid versions of two process modules were added to a target workspace one after another, there was a special constellation in which certain local associations between elements of the two added modules were not created.
When process modules were added or updated in some scenarios wrong warnings about unresolvable remote elements were shown.
When a new process module was added to a workspace, the switch for push updates was not enabled by default.
Long task comments were not supported.
When starting a workflow all participant groups were shown instead of only those who participate in the workflow.
When a user was locally assigned to a participant (in one workspace), and another user globally unassigned later, the unassignment was also executed locally.
The end step of a workflow was not executed properly when the transition leading to the end step was auto-approved. The workflow was not terminated, and the process state that was defined on the end step was not set.
Very long step names could not be displayed in the workflow's editable step list.
In the approval history the transition names were shown instead of process version state names.
In the Release Details and Approval History the Username was in short form. Now the full username is shown. In Release Detail view also the System Tasks are show by System and not by Root User.
Running workflow instances were visible without process release read permission
Comment input could not be enforced for approval task completion.
The value of the "State of the previous valid version" field was not imported correctly when the exported workflow contained a "Set state of previous valid version" step.
A user step that had the "No state change" option set could not be saved
Workflows could not be imported if they contained users whose names matched existing users case-insensitive but not case-sensitive.
Deleting a process version with an active workflow instance made the process version management inaccessible due to internal errors.
Process version creator was not set in case the baseline was created via a workflow.
When changing the current language the state names were only updated after reload.
Association constraints defined in the metamodel were not only checked for source elements with equal subtype ident, but also when the subtype ident in the constraint was a substring of the element's subtype ident.
Process versions could not be created and modules could not be imported if there were no states configured.
When the user typed in an invalid process version explicitly in the URL there could be a mismatch between the process shown and the information in the process version switch. Now both suit together.
Show better error message if the creation of a process version fails (e.g. when trying to create versions in parallel for the same process or for different processes with remote associations)
"Fit to page" switch was duplicated if users switched between flow and grid layout in Internet Explorer on a page with multiple diagrams.
Words in non-latin characters were broken with a hyphen ("-") in visualization shape text.
Navigating via the process visualization resulted in a process version jump to the valid version in case the process version name contains special characters.
Compare button was not shown in task details dialog.
Reports sometimes were displayed in the wrong language when browser language was chosen in the user settings.
States were partially used from configuration property instead of as defined in administration.
Removed current workflow step from options for the next step.
Buttons in workflow sidebar overlapped the card
Initial state hint was not shown in list view.
Search flyout results did not change when the search input field was focussed after switching the workspace.
When search scope was set to "My workspaces" no search hits from current workspace were found.
Aggregations in global search flyout (number of hits per type which is shown below the search input field) could count results from the wrong languages. Therefore it might seem there were results for the language viewed in the current workspace but the search results page then showed no results. This count is more realistic now in many situations but it still is (and can only be) an approximate number which may be higher or lower in the search flyout than on the actual search results page due to permission filtering or hits in different languages.
Users can be assigned to user permission groups via participants.
Reworked workflow modeling UI.
Export / import process release workflows
Created unit tests for workflows, states and steps. Added delete-functions to Peers. Fixed wrong types of StoreExceptions. Mini-refactoring of WorkspaceCollectionService-Unittests. Refactored html of states and workflows. Fixed not being able to rename Workflow.
Management for workspace
collections backend
Moved electronic signature flag from workflow transition to workflow step.
Workflow transitions can now be managed.
Review and approval Workflows can now be managed.
Workflow steps can now be managed.
Management for workspace collections frontend. 7fb3135e
Added administration for stakeholders and states of process releases in commit e0e37a4a
SAML responses with encrypted assertions are now supported
It is now possible to disable login via username and password. Attention: This will also disable login of the root user.
Compliance references can now be created from the process element view (using browse)
Compliance references can now be created from the process element view (using search)
"Module pulldown" mode for migrateMultiLanguageProcesses.bat: Migrate a process module, but look for translations in processes that integrate this module.
Enhanced logging of unavailable repositories and optimized performance by de-duplicating repositories.
Add a to-do list to the dashboard.
Increase resolution of diagrams in pdf export
Introduced Enactment 2.0
Extend process compare for process execution elements.
Process execution export to Rational Team Concert now needs license feature "RTCExecutionExport" and export to Jira needs "JiraExecutionExport".
Implemented support for process execution elements to be tailored by the tailoring assistant.
Implemented manual tailoring for process execution elements.
Added activator subtypes step_by_step and transition_wf_v2
Map identity in enactment format
Now you can allow or deny process module push updates by a switch at the module installation.
New valid versions of process modules can now be pushed to the process working versions in which the module is installed. This can be started from the "Usage" tab in the module management page of a process module.
Compliance coverage is now imported when adding/updating process modules when the coverage was set in the module and the setting from the module is higher than the local setting (if existing).
Names of steps and their transitions are now shown in the current language
Show Review and Approval History for Process Versions in Management.
Process versions can now have a version description in richtext format.
Workflows can be started with parameters
- Adds REST endpoints to get all needed start parameters for a workflow and to start a workflow with parameters
- Adds a UI dialog to set the value for all start parameters and to view and change the stakeholders
Updated appearence of stakeholder edit dialog according to ux feedback
Review and approval workflow state widget is shown on process versioning page. Users can comment on their step decision.
Process baseline specific stakeholders can be edited and resetted to defaults.
It is now possible to define visualization user parameters in the metamodel that are only available to users with process execution permissions.
Release details can be shown on process start page
Set status of previous valid version (system step). Adjusted process-version-list and validities-list to reflect new state-colors
Tasks can be automatically completed after a certain duration.
Provide css classes for link customization
on support tile. Also open links in new tabs if demanded. See
documentation
Renamed delete association to remove association.
Enables login page to show additional help
desk information
Enables the supporting tile on
dashboard to display custom links, email addresses and telephone numbers
Comment permission was necessary in root workspace and the workspace of the comment in order to retrieve comments (containsComment@System). The permission in the root workspace is now no longer required.
Adding new participants switched to the first page and the previous page could not be opened anymore.
Stages shutdown could take very long with MySQL when database optimization background thread was running during the shutdown.
Users with "Process Viewer" license had no access to user assignments on roles even when the "AnonAccessRoleAccess" license feature was active
Workspace deletion failed in case role based permissions exist for the workspace to delete.
showing roles leads to internal error
User settings could not be edited without setting the password.
Reduce amount of memory used by long running admin jobs.
Editing the landing page, when the current workspace has no process, will no longer result in an error
Added tomact.basedir to rc script to fix missing tomcat logs in support info
Error message on setting user setting (with user ID) discloses user name in clear text.
The description of a landing page was deleted when the page was made the default landing page.
After Chrome browser update to version greater than 80 the new sameSite Cookie behaviour was introduced. Through this the user came into a redirect loop between the IDP and Stages when using SAML. Now the new default behavior regarding the Cookies was adjusted.
When a compliance element was mapped from an element view, the browse dialog had a link for workspace selection which always led to the root workspace. Now this link is disabled.
Fixed namings of save and cancel buttons of compliance coverage notes
Transfer mappings now assigns all scopes
from a new reference model to the mapped process.
Compliance Rating performance improvements.
An error occurred when the "Compliance" widget was visible for a process element (in the process model) and an index element in a reference model was associated.
Process change records from Stages 6 could cause workspace and process deletion failures. The remainig data then could lead to other follow-up problems (e.g. you could not view the permissions of a user who once hat a permission for one of the affected workspaces/processes).
Fixes sporadic internal errors caused by a 'No operations allowed after connection closed' exception.
Analyzed various "Lock wait timeout exceeded; try restarting transaction" errors that may occur with MySQL when modeling concurrently.
Textual reference resolution for migrated Stages 6 resources became case-sensitive which could break links that were intact in Stages 6
In IE11 links to anchors could only be clicked once on a page.
Save or cancel editing an inline description before the description is visible deletes the description/causes an internal error
[Internal] fix for the "editor already open" case
Ensure proper functionality of cms property "use.system.account.for.download".
Show the correct user and date for frozen guidance files, in the case a locked file is getting frozen.
When a user authenticates to sharepoint for the first time, the domain (from config.xml or file management) is automatically prepended to his log-in username.
File presets were not copied when creating a new process version
Repository access data for SharePoint Online was lost on process export/import and process moddule addition/update.
When an CMS error occurs, send more information to the client.
Fixed styling of compact file history version display and introduced message key for version label.
Fixes a thread leak for process that are migrated from V6 and used a Sharepoint repository for resources.
Open login dialog when refresh of access token fails
Fixed issue, where the root folder could contain false folders.
It was possible to link a file without specifying a filename.
File download not possible in IE11 for some cms
The "allow" option for state transitions in the artifact lifecycles of the metamodel was not recognized.
When users had to enter their credentials for an external repository, the label of the corresponding send button was wrong.
Added config properties to adjust
the memory cache size of the CMS-cache. Use
cms.structure-prefetch.memorycache.max.repositories to set size for the
repositories cache and cms.prefetch.memorycache.max.documents to set
size for the documents cache.
On file multi-upload sometimes the metadata was not automatically updated in the file widget.
Upload file form shows empty lifecycle dropdown, when repository default lifecycle is set to NONE.
Sometimes while the progress of operations (e.g. deletion of process versions or update of process modules) was shown in lists, an internal error (NullPointerException) could occur.
When adding an element and then directly navigating, the add mode was still partly active.
Links and images on landing pages were not rendered correctly when the root workspace had a process that was not readable for the current user.
PDF creation can interrupt with UnknownHostException.
Printing a section containing an empty description produced a Null Pointer Exception.
Umlauts used in the pdf templates were not correctly encoded in the resulting pdf.
PDF printing was not possible in case the Stages server could not access its external URL. The URL to use can now be configured via property "pdf.serverAddress".
Links to embedded description elements and from image maps to process elements were not rewritten correctly when phase freeze was used in multilingual processes
Excessive memory consumption could occur when comparing processes (this should improve the behavior even when the diff algorithm is called many times)
Excessive memory consumption could occur when comparing processes (this fix greatly reduces the number of calls to the diff algorithm, which should also greatly improve execution time)
Added missing custom attributes for process feedback: originWorkspaceName, originWorkspacePath, originWorkspaceFullPath, creatorEmail
Feedback widget caused an error if no feedback system was configured.
Fixed additional context attributes for process feedback
Fixed additional custom attributes for process feedback
Fixed internal error on second feedback request
Number of progress counter was not centered correctly
When importing a .zip process export from Stages Composer, targets for multi-lang correspond associations were not found for element types that were not in the metamodel in Stages Web
The "database" repository was not available for files on Guidance elements when the process had been imported from a v7 .zip export
The progess display of process imports was very inaccurate.
The "database" repository was not available for files on Guidance elements when the process had been imported from a v7 .zip export
migrateAssociationComments.sh|.bat create association comments with only whitespace in some situations. Now the comments are trimmed.
Fixed multiplied display of
validator warnings from the same constraint type
Edit was visible for description elements integrated from module.
Abbreviations could be edited in process element edit forms, even when element types were not configured to have abbreviations in the metamodel (shortname="false").
An exception could occur when a role or user group was deleted
An error could occur when importing a translation .zip file that had non-ASCII characters in names of zipped files or folders
Copying process elements became very slow with a large number of elements (number of elements squared)
With the firefox browser navigation items could not be sorted by drag and drop.
migrateAssociationComments.sh|.bat script created illegal associations to index elements. Comment associations that would be migrated to such illegal associations are ignored now.
Importing V6 processes with resources of the outdated resource subtype 'artifact' resulted in corresponding guidance elements without a file.
It was not possible to configure a custom attributes widget for the process start page. An error occurred when opening the widget.
Do not overwrite locally changed compliance coverage values or comments by process module updates if the coverage values from the module are not higher.
In case all files were deleted from a guidance element in a process module, module updates at locations where the module is installed did not propagate the deletion of these files.
Process module update did not update files on guidance elements.
Files on guidance elements were lost on process module updates.
If the Working Version of a module was installed and the Valid Version of the module was not set to type "Process Module", the module installation could not be updated anymore (with the module Working Version) and the module management page showed no link to the module.
If a process module version was added to a process and the version was renamed after that, the module management page still showed the old version name.
Added missing message property.
No validation error was displayed in the creation dialog for process versions when a duplicate process version name was entered.
Fixed a problem, which caused files to be not frozen when creating a new process version. File versions for guidance elements are now created from the cached version history and not from the actual version of the external system.
Releasing a process version as valid version could fail when multiple LOST+FOUND elements existed.
Link to Working Version in process versions overview was not clickable.
If the process version name is empty the version list could not be opened. Now the process version is marked with an error icon and a popup message tells the user to give it a valid name.
If Stages was upgraded from an earlier Stages 7 version to 7.4 or 7.5, some images embedded in element descriptions were not displayed (if textual reference started with "[[resource" instead of "[[description" and description element in "Management" was never modified and saved). The error did not occur if Stages was directly updated from version 6.x to 7.4 or 7.5.
Images on process element pages were not displayed properly when all of the following conditions were true:
- The process element was viewed with Internet Explorer 11
- The process was created by importing a .zip file that was exported with Stages Composer (up to version 6.6.11)
- In Stages Composer (up to version 6.6.11), a file with an uppercase file extension was stored for the image
This fix will correct the content type for .zip file imports and in the database.
Menu items for visualization options were not displayed correctly when there were both multiple visualization tabs and multiple visualizations in one of the tabs
Update process visualization when a file status change happens in the files widget.
Fixed internal error when the target element was not found on the flow-visualization
Excessive memory consumption occurred on the server when many process elements with visualizations were viewed with browsers that request process visualizations in SVG format (all browsers except IE 11)
Files widget was not displayed if guidance files were collected and user had no file read permissions. Now process read permissions are sufficient.
File could not be downloaded from Excel exported reports.
Search results of current workspace were wrong after language change
In some situations the search results did not show the localized element names for multilingual workspaces.
Search type filter were not available for
additional languages
[Internal] Merge desaster on commit 5a5abf726a
Updating tomcat to version 8.5.61 for security fixes
Redirect to external login and external logout pages did not work because of CORS restrictions.
Update tomcat to version 8.5.57 for security fixes.
Images used in custom.css were overwritten on stages update. Now you can place your images in conf/img folder and deploy them via update.bat.
Fixes view when dialog is closed
Close user settings on router navigate
Landing pages were rendered on every click on the home button resulting in slow responsiveness.
Disabled checkboxes were not easily recognizable
Additional support links (see ST-32127) could not be displayed only for one language, or they were not updated when the user language was changed.
IE11 headings styling was wrong
Add button was missing on newly
uploaded file at guidance element
Fix for IE11 styling issue on
dashboard
Tomcat rewrite valve was broken. Therefore it was not possible to download files or resolve V6 links.
Profile picture upload was broken in IE 11 when the "global.secureMode.enabled" config property was set
Profile picture upload was broken in IE 11 when SAML authentication was used
Custom rules can be added to the rewrite.config by editing /conf/rewrite-customer.config and executing update.bat/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 config, create a file named "rewrite-prefix-customer.config" in the conf directory.
Zooming deeper into the visualization is now possible
Process visualization parameters of multiple visualizations in a common card are now merged into one menu switch. This can be disabled in the metamodel via <widget:diagram ... mergeParamters="false">.
Tabs at entry pages and visualization are now scrollable
The properties "TypeNameSingular" and "TypeNamePlural" of tailoring elements did not have the tranlated type names as values.
In Groups and Permissions two workspaces with the same name were grouped together. Now the path of the workspace is considered in the group by workspace perspective.
The Session Info Graph displayed the "average hours per session" in decimal format. Now the time is formatted in hour:minutes in the Tooltip.
Improve visual separation between groups of permissions with same domain/workspace
Workspace attributes won't disappear anymore, if another tab was clicked before.
User statics werent able to handle
longer session ids
Changing workspacesettings concerning languages is no longer possible, if only one language is supported
Session timeout was not considered when browser was not closed.
Compliance rating lead to internal error. TypedId in UpdateRating was not lowercase ensured
Incorrect transaction isolation level was logged.
Hide up-/home button in file-browser when showing root folder of repository
When connections with external repositories failed, the corresponding error messages did not show the affected repository names.
Could not open work product or guidance element in rare cases when the element had an invalid repository inheritance setting in the cm plan.
In the file lock dialog the lock button was not disabled when the user has no change packages. Now the form is invalid and can not be executed when the user has no change packages for that file.
There was an error "Something went wrong. The request could not be processed." when a user tried to open a file link and the user was not logged-in.
It was not possible to access Stages with Safari browser in case global secure mode was enabled.
After upgrading Stages on Linux in some cases it was not possible to login without stopping and restarting the service.
There was an "Element not found" error, when a workspace was deleted and the current workspace in the navigation was either this deleted workspace or one of its descendants.
Images on landing pages were only displayed correctly when the user had "Read" permissions for the "Landing Pages" permission domain.
Description elements that were embedded in a custom rich text attribute of an element (and not in the main description) were not handled properly when:
- Freezing an element
- Integrating an on-demand element from a process module (see also: ST-25019)
In the "Activity" widget, the names of multilingual process elements were always displayed in the workspace default language
Access to an element with a referenced description image with the same name as the abbreviation of the element leads to a NPE.
When an on-demand element from a process module was integrated, description elements that were embedded by this element were not integrated.
The OnDemand import operation 'Add Element / Create Mapping' does not set the entire process to read-only, now.
Tailoring assistant showed an error if an element to be tailored had compliance references and the corresponding reference mode was not readable.
After releasing a process version as Valid Version, files got the wrong repositories assigned in some cases, when there were multiple Subversion or SharePoint Online repositories. The same error occurred with process imports and process modules. Be aware that process exports from older versions of Stages 7 may still lead to this error.
Could not open validity tab on process versions management page after deleting a former valid process version.
Fixes an internal error during visualization rendering.
The line break of label text in process visualizations was incorrect in some cases involving words that don't fit into a single line.
Edge crossing style was not considered in case the visualization was rendered as SVG.
Reports could not be executed in an empty workspace.
Association quick assign was broken in case only one supported language is configured.
The hit counter and search scope in the search flyout was confusing under some circumstances. Now the hit counter is simplified and depends on the user search scope settings.
Update tomcat to version 8.5.55 for security fixes.
Landing page tab status was not saved when navigating by a link between different landing pages.
Stages did not scroll to top of the page after a route change. Sometimes Stages scrolled to the end of the page after adding oder deleting associations.
User groups are now part of the stages API.
Repository name is now part of the API (instance.getEntities("containsRepository@SYSTEM")[0].getProperty("Name")).
The attributes "licensePoolIdent", "defaultLicenseType" and "defaultRolesUsername" in the element "identity-provider-attribute-match" of a SAML configuration can optionally contain a JavaScript expression (instead of a static string representing the value). This expression can be used to interprete SAML attributes returned by the SAML Identity Provider and return the according value. An expression is detected and interpreted, if the attribute value starts directly with an equals sign. JavaScript control flow statements, the "throw" keyword, newlines and logging statements can be used. Example (using "licensePoolIdentOfX" for SAML responses where the attribute "organization" equals "x" and otherwise using the default license): licensePoolIdent="= organization=='x' ? 'licensePoolIdentOfX' : ''"
The secure mode is enabled by default now. This means that certain security-relevant headers will be set in 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.
It is possible now to administer and display multiple entry pages for different parts of the organization.
Added a commandline script (mergeUserGroups) that merges usergroups with identical permissions. Execute the script with -d option first in order to perform a dry-run (-h show all other available options)
User group administration is now accessible with read permissions. Group role assignments can be modified with Role-to-User Group Assignments permissions.
Last login and login count in user list can now be disabled (configuration property: administration.users.showLastLogin).
Permission tab is now accessible if an administrator is only allowed to view permissions and edit user groups.
Added permission domain for assigning process roles to user groups.
Recently added permission groups are shown on top of the permission list
User groups can be linked from process role page.
Assignment of roles can now be deactivated for a user group.
Search for users within an usergroup is now possible
Search for roles within a group is now possible
Assignment of a license pool is now supported in the LDAP configuration ("ldap-provider" element) and SAML configuration ("identity-provider-attribute-match" element)
License statistic can be filtered by license pool.
License details are now displayed for all license pools in the Administration dashboard
Updated styling and wording for permission list.
Show user's roles and groups
Assignments between user groups and process roles are now instantiated with modules.
Show name of process role in user permissions list.
User permission list can now be grouped by workspaces or permission domain
Additional license files can now be put into conf/licenses. An additional license file defines a license for a license pool. Users can be assigned to a license pool and their license is booked against the pool license. Stages will start when a pool license is invalid or expired, only users from this license pool will not be able to log in any more.
Added new chart to the administration dashboard which visualizes the user base growth of the last month quarter or year. All users are counted that logged in at least once.
Process roles can no be added and removed to user groups with a process role browser.
Show workspace path in user group administration.
A new usage statistics diagram with the following information is added: logged in user per day; sessions per day; average session duration per day.
Workspaces can now be browsed when adding permission groups
Number of assigned roles is visible on user group list.
User permission list now considers all permissions if the user is assigned through a process role to the permission group.
Permissions of user groups can now be filtered by permission domains and workspaces.
Consider role to user permission group assignments for authorization filtering.
User groups can now be linked with process roles.
Changes for oracle 19c support
Stages is now supporting MySQL 8
Stages 6 databases with multilingual processes (workspaces connected by _multiLangCorrespond associations or multilingual descriptions) can now be migrated to Stages 7 using a command line utility.
The HTML plugin was disabled in the rich text editor when the config property "global.secureMode.enabled" was set. Now, it can be enabled even in secure mode with the new config property "global.secureMode.allowHTMLPlugin"
Root folder configuration for SP and SPO
- Root folders can be set in repository configuration for SP and SPO
- The host name in config.xml can contain a path for SP, SPO and Subversion
- The path set in the repository configuration (PATH for Subversion / SITE for SP and SPO)
will overwrite the path set in the config.xml
Integrity change packages are supported again
Released Integrity adapter 2.0.0.1.4.0
Added feedback implementations for redmine and RTC
Introducing new feedback API. Feedback Systems are now delivered as separate Jar-Files.
Process feedback can fill reporter, assignee and user picker fields
Enable PTC ILM as ticket system for feedback widget
Description widget is now hidden if there is no description, the user has no process edit permissions and the widget attribute hideEmpty is true (<widget:description hideEmpty="true"/>).
Added a metamodel option in order to sort association lists alphabetically. (e.g. <widget:association-list path="artifact:relevant" sort="alphabetical" translate="process.phase.artifact.relevant" translateNone="none"/>)
Provide migrateAssociationComments.sh|.bat script to migrate V6 associations with comments that are not supported in V7.
Support rich text custom attributes (<attributeType type="RICH_TEXT" .../>) for process elements and the process itself.
The visualization script is able to access the array of 'availableFontFamilies' to choose one of them.
Do not display empty process visualizations
Added zoom and drag functionality to visualizations.
Hide group, user assignment and file widgets if the user has no permissions.
The server address for reporting self requests can now be configured (e.g. http://localhost:8080). By default the server address from client reporting requests will be used. This change replaces ST-31896 from Stages 7.4.4.1.
Internal requests from stages to reporting web application are done via localhost.
Show workspace name in search flyout.
Updated search engine
The "Feature-Policy" HTTP header is now sent when "global.secureMode.enabled" is set in config.xml
The "Content-Security-Policy" HTTP header is now sent when "global.secureMode.enabled" is set in config.xml
Floating action button now supports up to 10 entries (subtypes).
Only valid V7 element types should be accessible via facade.
Name translations were not part of the API. Now all element names can be get via property MultiLingualName (String get(final String language); public Map<String, String> asMap();).
The bulk deletion of entry pages gave no feedback to the user when the deletion is still in progress. Now a spinner shows that the action is still progressed on the corresponding entry pages.
In editable name fields the text was cut off while renaming
Pressing the Return key in the form where users are created or edited closed the form. Now the form is submitted if its input is valid.
In the form for the creation of new users, the field validation was not triggered when tabbing through fields. Moreover the first field was not focused when the form was opened.
Tomcat version was not shown on administration page.
Fixes the breadcrumb links on Administration > Users edit pages.
Link Groups with user roles: Workspace was not selectable on permissions-tab in mobile view
White space between workspace name and transitive was missing in permissions mobile view
The role browser for user groups could not be opened without any process in the current workspace.
Users that were assigned to a pool license were displayed like being assigned to the main license in the user list
adding workspace permissions derived from roles did not work under certain circumstances.
Script upload for admin jobs is now working properly
Quartz connection pool was trying to reuse timed out connections.
Role count was not shown in filtered user group list
Adding roles (with the same name and from different workspaces) to a usergroup with the associationbrowser was not working correct
Deleting a workspace with baselines could show an internal error in the end of the action.
Step 5 of ensureDatabaseIntegrity ("ensureAssociationIntegrity") is now executing the same cleanup steps as ensureOracleAssociationIntegrity when MySQL 5 or later is used. Some of these cleanups steps have been optimized so that they are much faster with large databases.
Fixes ensureDatabaseIntegrity for resource with content.
Fixed styling for autocomplete component
Deleted roles don't show up anymore on page reload
Speed up workspace deletion to prevent MySQL lock wait timeout exceptions.
Linux installations received a startup error while trying to generate editor directives from the process metamodels.
Log a warning in case a config variable is defined twice.
In the user groups table view, the member count was not vertically aligned.
An access error occurred when a user clicked on a usergroup name in the user permission list without sufficient privileges in order to view user groups. The link is now disabled in this case.
The version check was registered as user interaction, so there was never a session timeout
It was not possible to enforce https usage in an upgrade safe way. This is now possible via web-customer.xml.
Clicking on labels / the containers of labels modified the corresponding switch values
A workspace could not be moved when it had a workspace variable with an empty value.
Fixes handling of parallel SAML requests from the same browser.
Custom SSO filters can be configured in conf/web-customer.xml such that such a configuration is no longer overwritten on the next Stages upgrade.
Element subtype was not considered in order to display icons for compliance associations.
Compliance references from different reference model process versions were displayed in process element views. Now only the compliance references with reference model working versions are shown.
After adding compliance associations using quick search, the list of compliance associations was not displayed expanded.
Compliance associations could not be created via quick assign if the user had no process version read permission on the reference model.
In compliance view the link back to the mapped element led to the valid version instead of the working version
Elements from on-demand modules were no imported as local elements via association browser if the module process version was renamed.
When executing migrateMultiLanguageProcesses.bat for a workspace with description-only multilinguality, the workspace was not correctly converted into a multilingual workspace.
ensureDatabaseIntegrity did not fix processes with no version name that were not the working revision. Now, for these processes, the version name will be set to "Version <process GUID>"
Improved performance of Stages version 6 to 7 upgrade of large MySQL databases.
Through duplicate history records, the upgrade from stages 6 to stages 7 could get cancelled. Now a script is called automatically during the upgrade to clean the duplicates. Furthermore a constraint is added to prevent the creation of such duplicates.
Rich Text attribute display in attributes widget was in wrong text color
Custom editor directives were not available in the process and process element edit pages.
Fixed problem causing error when pasting a table from MS Word
In the image dialog of the description editor the image map field was to small and not resizable.
In Chrome, newlines were not preserved when pasting text from applications that copy unformatted text into the clipboard (text editors and some other applications)
In the editor link dialog, trying to open the preview of an element other than the current one resulted in an element not found error.
In the editor link dialog, description anchors with the ampersand character let the browser become unresponsive.
For editor directives, that have been declared in the metamodel, the corresponding icon images and CSS were not generated.
When a link was double-clicked in an editor in the Translate dialog, the link was erroneously marked as invalid when the editor language was different to the current user language. Changing the "inline"-switch of a link in the translate dialog had no effect.
Links to elements in other workspaces were created with incorrect target path when there were three or more parents.
When double-clicking multiple links in the description editor, the wrong link could be selected in the link dialog.
Allow path for hostnames in config.xml
Some message properties were not translated in SP Online Authentication popup.
File list was not sorted correctly when files were checked out.
Subversion adapter can now download relocated files
Shared Integrity subprojects were not visible in link-file-dialog (cms browser).
Fix permission check for download/link operation
Changed files component to check non HTTP URIs if they are valid.
Improved error handling, when interacting with files.
Association filtering did not consider the marked deleted flag for the target process.
Ensure Stages service is running under a local system account on windows.
Errors could occur when opening "Home" when there were access log entries that referenced deleted processes or workspaces. These access log entries made widgets like "Recently Used Files" crash.
The back-button of the navigation (the up arrow) did not work while trying to add new activities
Images could not be embedded in PDFs. Now an image directive is provided (usage: <image src="image.jpg"/>). The images must be provided within the metamodel (.mm) files in the pdf folder.
API didn't return change markers in multilinugal processes and thus visualization couldn't display them.
Change markers of collected files were not shown.
An exception occurred when comparing two process versions when a custom attribute with type SELECTION had a value that was no longer supported by the metamodel
Fixes locking during process compare calculation.
URL escaping for links in area maps was wrong for space.
Compare mode now uses plural naming for index elements
Comparing processes failed if an empty description was inlined in the process description.
When diffing multilingual processes, the progess bar jumped to 100% too early.
Processes could not be imported if the exported processes were mapped to multiple process versions of a reference model.
Comment-only compliance mappings were duplicated by process imports when the mapped reference model had multiple process versions with the comments. The affected processes need to be exported again to fix this.
Prevent exceptions after deleting the process of a workspace and directly importing a new process.
Remote process locking for concurrency handling on process copying and versioning was incomplete.
Ensure that readiness checks of different metamodel do not interfere with each other.
Index widget could not be used in multi column layouts.
Fixes a NullPointerException in migrateMetamodel.bat|sh when migrating overwritten elements.
The association browser was showing elements already as assigned when they were only assigned in one of the modules and not in the integrating process.
Association comment could not be set in association browser.
Stages will no longer try to translate into unsupported languages
An error occurred after three deletions of associations of one association type and source element when multi-delete was used.
After adding associations to an empty association list using "Browse", the association list was not displayed expanded.
When a process element was copied, moved or integrated from a single-language to a multi-language workspace, it appeared untranslated into all languages in the "Translate" view and in the "Translations" validator when executing a readiness check. Now, it will be displayed as having a translation in the default language of the new workspace.
Project variables were not expanded in descriptions.
Tab handling in add-sequence dialogues was broken.
It was not possible to use a description template with only process modeling permissions.
When a process is imported or copied into a workspace group which is also a common element provider, the parent workspace of the group is now considered as possible target for process interfaces - even if its name does not match the name of the original target workspace.
Process module update showed an error if the process to update was assigned to a reference model process version which was recently deleted.
In some cases the compliance warnings in multilingual workspaces could consists only of the abbreviation. Now the element is displayed with abbreviation and at least the default element name if there is no corresponding translation available.
Replacing a working version could be very slow. Fixed performance problem.
In case release as valid version failed, there was no way to retry the operation.
Delay deletion of old working version in case of replace working version operation.
Process version creation and process version comparison need a process lock.
"Open in new tab" was no longer displayed in the browser context menu for readiness check findings
Changed validators to check description and name for all supported languages.
Pressing the browser back button on adding a process version resulted in an error
Importing a ZIP file that didn't match the correct format, resulted in an incomprehensible error message
Whitespace was not rendered properly for "pre" elements in HTML sections (for instance, when HTML sections were used for code snippets)
Image maps were shifted by some pixels in IE/Edge browsers or after editing the description.
Image maps in descriptions were not adapted responsively after sliding the navigation drawer in or out.
Element index was not clickable after editing an element directly via the navigation menu.
Font in visualization was not working reliable. Implemented links directly in the svg to make css import via svg possible. Established font family css file for configuring font-families efficiently and ensure the ability of adding unicode ranges.
Scrolling to the selected element was not working reliable. Maximizing the window with the maximizing button resulted in unexpected behavior with the visualization-zoom.
Visualization was not rendered on old edge. Initial fit to page parameter did not work
In Stages 7.4.2.1 and later, visualization shapes with non-latin characters were sometimes not rendered when the platform default encoding was different to "UTF-8"
Font in diagram was wrong, when font was not installed on client PC. Now font is embedded. Therefore config property diagram.font.list has to be added to config.xml. Example configuration: <property name="diagram.font.list" value="Arial:C:/Windows/Fonts/Arial.ttf" />.
Switching visualization options too fast resulted in an internal error. Navigating to the file history with the browser back button resulted in an internal error.
When a user-param for a diagram widget was deleted from the metamodel, the value for this parameter could still be set in the UI when it was set at least once before the metamodel change
OpenSource List typo and missing heading
If reporting server address is predefined with config property "metric.serverAddress", it is now used for all reporting requests.
.rptdesign files with non-latin characters could not be uploaded in reports when the platform default encoding was different to "UTF-8"
The more report run was called the smaller the report became
Metric reports were cut on using the browser zoom
When elements with files were removed or added by tailoring, the tailoring status had no immediate effect on the file search results.
The search index was not immediately up-to-date after manual tailoring and so removed elements were still found until next cyclic search indexing pass.
Stages Search log files could grow infinitely in number and size, filling up the available disk space. Now, at most 10 log files with at most 10 MB are created (same setting as for stages.log)
A user that executed an unauthorized action (for instance, saving a process element after "Modify" permissions were removed) was redirected to the login page. Now, the "access not allowed" error page is displayed again.
Referrer-Policy was not set in response headers. Now it is set to "origin-when-cross-origin" when the config property "global.secureMode.enabled" is set to "true".
Update tomcat to version 8.5.51 for security fixes.
Update tomcat to version 8.5.50 for security fixes.
Consider global.secure.mode setting for error details.
Stages users with Users read permission were able to retrieve the user information (email, id, username, license) of all users via a direct REST request. Now a user needs some kind of user management permission i.e. Users [C|M|D] to be able to retrieve this information.
Disclosure of server type and server version information within the error page
There was no loading spin in the translation dialog
While editing user details in the administration area a workspace change could produce an error. Now the formular data is more robust.
While viewing the permission of a user group the change of the current workspace with the navigation drawer lead to duplicate permission entries in the list.
Feedback permissions were not cloned from comment permissions during upgrade.
An error occurred in the global dashboard when a file in the "Recently Used Files" list had a lifecycle assigned and was accessed multiple times with different workspace IDs as the current workspace
File download links from the Stages facade were broken.
It was not possible to install Stages on Windows with AdoptOpenJDK out of the box.
PDF Printing progress indicator did nether finish in case only one print template was available.
PDF Export failed with an error when there was an inline link to a description element somewhere in the exported element and the workspace was multilingual
When import a large process export as a zip file the upload round progress showed no updates.
Navigation drawer was scrolled to top after renaming a navigation entry.
Fixed wrong color of the "Update" button in the bulk module update dialog and the name of the button in the confirmation dialog for removing a single module.
The links to search results in process start pages lead to "Home" instead of the process start page.
Internet Explorer reacted very slowly when a large number (hundreds) of elements were on the same hierarchical level. Now the number of elements in list views is limited in Internet Explorer. It can be configured by the config property value "list.limit.ie" (default: 200). Moreover a progress indicator is shown in the left navigation if it takes more than 1 second to load.
Added archived property to project element
Change markers are now shown on perspectives
Icons for value chain
Removed unnecassary functions. Added vertical scrollbar to visualization. Enabled "fit to page"-behavior on initial load. Removed possibility to scroll the visualization with the mouse wheel
Querying compliance ratings with "containsComplianceRating" with a processFilter (",process=") produced an error when the corresponding reference element had no ratings.
Stages shutdown took very long.
selection attribute values goes lost when tabs are changed.
The displayed language was wrong when the workspace language was changed but the preferred user language was different.
If the path name for a keystoreFile (used for SAML authentication) was relative (e.g. "conf/keystore.jks"), Stages tried to open the keystore file relative to the workspace directory where Stages was started. Now Stages searches relative to the Stages root directory.
The password was not deleted for an existing, non-SAML user who was converted to be a user authenticating via SAML
Compliance elements in compliance mapping view could not be opened when they had a rating and a mapping.
In a newer Microsoft Edge version trying to open the editor link plugin or html template plugin produced an Internal Error.
Plain text containing angle brackets could not be correctly copy-pasted into the editor.
In the translation export empty span elements were part of the description content causing unnecessary translation segments.
The description editor was closed after the column layout was changed by resizing the browser window.
With the default configuration it was impossible to define editor formats for headings with h4, h5 and h6 elements. The automatic conversion to h3 has now been removed from the default configuration. To reactivate the configuration property global.editor.format.migration has to be set explicitly.
The description template plugin of the editor did not show the content of description templates with tables correctly.
In chrome browsers closing an editor dialog was changing the window scroll position.
Wrong message was displayed in editor description template plugin when there were no templates in the folder.
Translate dialog could not be opened if a process was imported with unsupported languages.
The element browser in the description editor in translate dialog used the current user language instead of the language of the translation.
Some editor items were not usable in edit mode
Pasted images from the same element were equal to the original images and therefore could not have different image maps.
Changes in image map could not be saved in the edit element dialog.
Selected text was changed by inserting an anchor link in the description editor.
Drag & drop within the description editor was enabled with unwanted side effects.
Recently added files were not highlighted correctly.
Fixes a potential thread leak caused by various element copy operations when a Sharepoint repository is used.
Repositories that were imported from process ZIP files did not work when the ZIP files were exported with an older Stages version than 7.2.
Locked file could not be updated via Drag&Drop
Fixed thread leak and NPE in prefetch
- Added isAlive check when creating cms connection because SP online connections
can always be instatiated
- Using cache to get connection in cms repository constructor
Prevent creation of multiple sharepoint online profiles in file management
Dashboard description is not visible when multilanguage is enabled for root workspace.
In certain constellations the translate dialog was jittering due to a race condition in repositioning the editor toolbar.
Content scrollbar was not disabled when navigation drawer has been opened.
In rare cases under high server load, the workspace navigation could fail with an Internal Error (Duplicate key).
Added missing default stylings for process element descriptions in PDF print outs.
PDF download error message was not available for Internet Explorer.
Change markers on perspectives were not shown in case of compliance association changes.
Process diff could not be opened with IE11.
Added and modified badges were shown together.
Added badges are now shown on both sides of an association if the target element has been added.
Stored diffs were not recalculated after updating the metamodel.
Compare button was visible even if there was no version
Secondary workspace cannot be selected. For loading the message key has changed to --loading--
An exception was logged after a process has been deleted.
A description was stored in the workspace default language when importing a translation .zip and the description was empty before
Moving an element to non-existent process threw an error
Changed CopyProcessPolicy to check if target workspace has no process versions so copy process is only possible if no process exists.
Compliance rating could not be recalculated if the user could not read reference models.
Input field was not closed after creating and viewing an element
Translated elements were not found instantly in search when the translate dialog was used.
Translate option was available in multilingual workspaces even if there was only one language configured.
Adding a process module failed when the Valid Version of the module workspace was no module and the user was not allowed to read the other process versions.
During migration of Stages V6 Tailoring Q&A to V7 the tailoring associations to Descriptions and file based Guidances were lost. Those associations are now reconstructed.
A process version with a name containing a '+' sign could not be viewed
Changed description link validator, state validator and multi language validator now ignore tailored away elements.
After the page was scrolled down by clicking an anchor link, it was not always possible to return to the top of the page with the browser back button.
Links to guidance elements showed different behavior depending on the user's access rights.
AddionalNodeLabels always stretched the enclosing node in case the label is larger than the node width. This is sometimes undesireable and can now be configured for each node label via AdditionalNodeLabel.setStretchEnclosingShapeToFitInto(stretch:boolean); The default value is true, such that existing visualizations are not affected.
Management descriptions could not be opened anymore.
When dynamic report parameter values could not be loaded due to report script errors, the complete report page could not be opened. Now the page can be opened and the error detail can be viewed in the parameters section.
The search for processes to copy and modules to integrate was broken.
Opening a single search result in the search overview dropdown with the keyboard did not open the single search result but all results
Tailoring questions and answers from monolingual processes were not found anymore.
Fixes a security vulnerability in the Stages login procedure that can result in users being able to impersonate another Stages user. The vulnerability can only be exploited when SAML is enabled.
After module browser usage the workspace selector in navigation drawer was filtered by installable modules and the styling was broken.
Window titles on some pages were not set correctly corresponding to the process element. Now the window titles show the translated process element or the name of the area the user actually visits.
Tabs where wrong aligned in edit workspace and edit user details view
Process Viewer licenses now include compliance read permissions and Project Manager licenses include Process Version and Release permissions. Process create is no longer required in order to add process versions.
Removed obsolete permission domains.
The mappings and ratings of an older reference model version can be transferred to a new referrence model version by the script transferMappings.bat/transferMappings.sh (call bin/transferMappings for usage help). Precondition for the transfer is the mapping of the reference elements from the old version to the reference elements from the new version.
When two process versions are compared, added and modified change markers can be queried from facade elements via "containsChangeMarker@SYSTEM".
Provide stable links to elements of a specific process version (i.e. former valid versions). Use new facade property "StableURL".
Released the adapter for sharepoint-online and added a new version of the CMS-API.
Cleanup of the file suggestor API structure.
New files can now be created based on the linked templates.
Hover effect in workspace navigation on workspaces with child elements is now visually split into to click areas.
Reports can be run directly from the parameters widget.
Changes are now also shown in process index when comparing processes.
Table and list views of collected process elements can now be shown.
Process element names (including description and tailoring elements) and descriptions can now be entered in multiple languages, if "Use multiple languages" is checked for the workspace
Process compliance association are now considered when comparing processes.
Process attributes are now considered when comparing baselines. Improved image comparison.
different permission domains for comments and feedback.
Associations are now included in process diff. History of valid version can be shown.
Added, deleted and renamed elements are now shown in process diffs (compare).
Process descriptions can be diffed now. Change markers are shown in the process navigation.
Custom sort order is now the default sort order for process elements. New process elements will be filed by the order of their creation.
CMS auth dialog now has a loading spin for login connection display
Description editor plugin dialog to insert description templates into other process descriptions.
Multilingual processes can be exported and imported. At import time, the workspace setting for the default language and the setting for the usage of multiple languages is also taken from the export.
Metamodel files can now bring their own jars, e.g. for validators
Association browser now supports selecting an element and all of its children
Visualization scripts can now create links for the visualizations that include additional visualization parameters.
Added a notification widget that informs the user about new valid versions on process start page.
OAuth 2.0 Password Grant for Jira Feedback Widget
Added switch to multilanguage import in order to control whether stages internal translations should be overwritten by external translation or not.
When a multilingual process is copied to another workspace, the workspace language and "Use multiple languages" setting is also copied from the source workspace to the target workspace.
Translate dialog provides now responsive design for mobile devices
Push the core process hierarchy and sorting only in case the it was changed in the core process since last update. In case of module updates from a working version of a module the hierarchy and sorting is always pushed as the previous state is no longer known.
Multilingual process modules are supported.
Missing name and description translations are now shown as validation findings when creating a new process version in a multilingual workspace.
Improved readability of tab styling. Added hover for navigation drawer icons
Changed button color of 'delete' and the remove confirmations in commit a9ac05e7
Changed button color of delete and the remove confirmations in commit a9ac05e7
Context menu in dialog was not working properly.
Navigation drawer can now be hidden by user
Show counters for selected association targets in the tailoring association browser.
Description Widget is now collapsible
Modified flag in the API was not set if associations were modified
An Exception was thrown when requesting configuration management information through the stages facade. Visualizations could not be rendered if there were configuration management errors
Added check for a new Stages version on the server. In case a new version was installed a dialog is shown that asks the user to reload the application.
Improved error handling on Stages start up.
"Update.bat" failed when Stages was running and a metamodel contained a JAR file (e.g. validators.jar in unified configuration). Now "update.bat" recommends to stop the process or run "Update.bat -Dforce=true"
Administration job scripts could not be uploaded anymore
Local users were not converted to SAML users when their email addresses matched
An error occurred when deleting a workspace when the workspace had news entries in the "Metrics" category in Stages 6.x
When uploading an admin job script file with wrong content type, the database table could have remained in locked state.
Changing the workspace language did not have an immediate effect without browser refresh.
credits.html was not updated.
The source (LOCAL, LDAP or SAML) of the users in the user administration list was not displayed without user modification permission and the layout was broken.
Users that were imported via SAML had the option to change their passwords in their settings (which had no effect). Now the password change section is not shown anymore to this users.
Swapped assigned and limit in license chart on administration dashboard
Setting the configuration properties "access.log.flush.interval.inMinutes" and "access.log.clean.interval.inMinutes" had no effect, access log flush and clean could only be configured using cron expressions.
SPNEGO autologin did not work without enabling tomcat autologin. Now configuration of autologin mechanisms is independent of each other.
RPM upgrade failed under some circumstances
Fixed internal error when clicking up-arrow in files broswer in root folder.
database repo for guidance has a lifecycle. There is no lifecycle for database repo.
Fixed order of attributes in file dialog
validateFilename and validatePath are unnecessary in config.xml. Now these entries and their dependencies are removed from config.xml
in guidance uploaded files did not show cms repository if there was only one. Now the cms repository is showed with readonly even if there is only one cms profile.
Edit Database repository causes internal error.
Changes on the File Management overview page are not updated.
Fixed resource leak in sharepoint cms implementation.
Not configured cms type in file management lead to an internal error
Added migration step to change subtypes for elements which names match a given pattern
Adding and Removing of elements to the compliance scope could result in heavy server load. Now the calculation is calculated in a bundle to reduce calculation time on the server.
A compliance scope could not be edited any more when it contained a work product, role or guidance element and the element was deleted.
Adding reference models to a process via search as you type did not security filter its results. Therefore it was possible to select a reference model scope that could not be added due to missing permissions.
When assigning elements to a scope quickly enough, the number of actually assigned elements could be lower than displayed.
An error occurred when creating a compliance association using the "Browse" button if the process model also had the process kind "Reference Model".
When an error occured during workspace delete a database lock was not released as expected.
Fixed performance problem: Prevented unnecessary database queries for the current process during process navigation.
Database cleanup (ensureDatabaseIntegrity script) step 9 "cleanDescriptions" failed.
Direct upgrade from Stages 7.1 to Stages 7.3 failed at upgrade step 4415.
EnsureOracleAssociationIntegrity was not prepared for new element type Guidance. Therefore valid association were deleted.
Database cleanup script (ensureDatabaseIntegrity) could not clean parent element references with value '0'.
Description Template Plugin showed "Internal Error"
Copy & paste of an image from one description to the other did not work.
File Downloadlink for facade, Search Result page, files can not be downloaded.
A null pointer exception was thrown by pkit.getElementByIdentity when the queried element didn't exist.
Artifact instance elements can now be queried via facade, e.g. stages.getElementByIdentity("_Dwzh4Pr2cJevdOxL4Qrf4A", "ArtifactInstance", "437")
Baseline filtering for remote associations was wrong in pkit#getAssociations.
Compliance ratings were not filtered regarding the baseline of the target element. Now they are filtered in the Facade API.
It was not possible to ask comment only elements for processId. Now it is provided via Facade API.
Cms-types, which are not configured in the config.xml file, cannot be added anymore in the files management.
Two file widgets on the same page didn't work together.
The required input field in the File-Dialog has not shown an error when the user navigates to the next input field using tabulator. Now required fields are validated when moving to other form fields.
Improve performance of files widget especially for large amounts of collected files.
Download file names with UTF-8 characters were not correctly encoded.
When navigating a "mailto:" URL attached to a Work Product/Guidance element, an empty browser tab was opened in addition to the mail client
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).
It was possible to view and update files in process versions that were not readable for the current user in the "Recently Used Files" widget, and when files were collected from elements in other workspaces using the "path" attribute in the configuration.
Styling of workspace navigation in navigation drawer was broken.
Update tomcat to version 8.5.43 for security fixes.
An internal error was shown when a profile image file was uploaded and its content was illegal or its file type was SVG or WebP.
Internal error by calling the file properties of some files from recently used files widget.
SAML Auth: Assign default user groups to new created user.
Ignore navigation during the same login-navigation and do not create login URLs with "redirectTo=%2Flogin"
Navigation to a deep link was not possible, if the user was not logged-in and not on a Stages page
Update tomcat to version 8.5.40 for security fixes.
Profile image could be broken after browser reload.
Update tomcat to version 8.5.39 for security fixes.
getComplement() for Contraintchecks are not available.
Home and current workspace is marked as favorite in workspace browser search tab.
Improve performance of tailoring resource migration from V6 to V7.
Breadcrumb navigation in "Reports" did not work correctly and always lead to the "Company" workspace
Starting a report before the parameters are loaded resulted in an internal error.
RPTDESIGN files larger than 1 MB could not be uploaded.
Renaming an element must not translate its description.
process deleting causes to integrity contraint error
Each validator in the process version readiness check did not display more than one finding for any process element name that occurred in the process. For instance:
- When multiple process elements with a finding had the same name, only one finding was displayed.
- When the description of a process element contained multiple invalid links, only one finding was displayed.
Parts of process element state management were visible in release as valid version and process settings form. The switches are now no longer visible until process change/state management is fully implemented.
It was possible to select Workspaces in the association browser which have no readable process version for the user. This led to an no access error page. Now such workspaces are not provided in the association browser search. The search results for the default workspace navigation is not changed.
Association Quick-Assign: Element name is more than 255 characters.
When requesting a specific process version without process version read permissions, the view was not consequently switched to the valid version.
Textual reference path with quotes or backslashes is not resolvable.
Quick assign of elements with only two characters wasn't possible.
Link to guidance elements with a cms managed files were rendered as text and not clickable.
Deleted process version was shown with identity as name in validity table.
CMPlan Path with more than 255 characters gives an internal error.
Changing the branch of a guidance cms repository could have led to pinning the wrong cms file revision on process version creation.
In some cases the readiness check results on frontend were not properly divided into warnings and errors.
Images were lost after export/import when the source of the image was an installed process module.
When removing an integrated core process, keep local and overlay elements and move them to the LOST+FOUND folder.
For processes that integrated unversioned process modules, a module update for those modules was not possible. Now unversioned process modules can be updated anytime.
Tailoring wizard mode of a process module was not adopted.
Deleted associations from a core process were not deleted from the corresponding elements on core process update when the elements were overlaid before the update and the overlays were cancelled during the update.
When the root user assigned an element from an on-demand module in a process version other than the Working Version, either a remote association was created or the operation failed. Now the on-demand element is locally imported into the current process version and a local association is created.
not resolvable textual references don't have hint text, which they showed before.
Editor directive plugin threw an error when custom directives were configured in the metamodel.
Description anchors could not be selected as link targets in the editor link plugin.
In secure mode the editor HTML plugin is now disabled. In order to activate secure mode, set the config property "global.secureMode.enabled" to value "true".
When searching elements in a remote workspace in the "Insert/Edit Link" dialog, the current workspace was changed to this remote workspace.
It was not possible to insert images in a description in case the image name contained umlauts.
It was not possible to delete imagemaps from images
Wasn't possible to insert images with HTML special characters in file name
A process element could not be viewed any more when malformed image map code was in the description of the element.
Summary page with warnings shown after process import could not be scrolled.
The externalURL attribute for process elements was not set any more in .zip exports
Process Validation error message resolving did not consider metamodel specific message properties
Pdf print failed if description resources were embedded in description resources.
Trying to access the files of an artifact or guidance element in a pdf print script resulted in a NPE.
Delete on overwritten tailoring question lead to an exception
DiagramScriptLoader cached is ambiguous.
Ensure the visualization of one metamodel cannot influence the visualization of another metamodel.
Some errors during visualization rendering prevented displaying the process element page at all. Now the visualization just displays an error marker.
The process visualization was incorrectly scaled for IE11 on windows 7.
Change marker icon was not layouted correctly on index pages.
Process compare didn't work together with collected child element associations.
Process version switch at "Management Tailoring" did not work when the working version of a process was viewed and new process modules were added to the working version or existing process modules were updated there.
The end user response time for process navigastion was bad while the Access Log entries were written to the database.
[Internal] Two process elements were created when a process element name in Korean was entered using IME input in the left navigation (IE 11, Chrome on MacOS and possibly other browsers).
Selecting a character from a list of alternatives (e.g. Kanji characters) using "Return" also submitted the entire input string in some browsers.
Fixed to early reactivating of delete button.
Editing links and images in the dashboard description was not possible without a process in the root workspace.
Modification of show tailoring setting had no effect until reloading the element page. This reload is no longer necessary.
Overlaid elements of a removed process modules were still write-protected, when they were automatially moved below a Lost&Found element at the time of the module removal.
If the creation of the process version failed, the resulting error marker could not be deleted again from the view.
'none' was not shown if an attribute was empty.
Table zoom did not work in IE11 with the table width set to 100%.
When rendering descriptions with a textual reference cycle in inlined elements a StackOverflowError occured.
Message properties for tailoring questions and answers were missing
Reports could not be executed when the user had no read permission on domain "Reports" or "Report Administration".
Request notification sporadically sent out wrong email body text.
The search input field was not closed on mobile devices when the search results page was opened.
It was not possible to scroll in the mobile view of the search result page. Now the scrollbar is enabled.
In the search filter for process version selection it was not clear which version is the valid version. Now the valid version is marked to ease the identification.
Search results for default search scope all were wrong.
Changing the search scope in the user settings needed a browser refresh to recognize the scope change in the search. Furthermore the current search term now remains in the search input field and the workspace scope in the search filter settings is also used for the next search request.
If the search engine is not reachable the search tab for workspaces showed an endless spinner. Now a message informs the user that the search engine is currently unavailable.
Calculation of search pages was imprecisely so it could happen that pages were shown even though no results were existing. If there are no search results for the current filter the previous filtertypes are now available.
If "Recommended workspaces" was configured as search scope in the user settings, the search suggestions in the flyout were wrong (form other workspaces than the recommended workspaces).
Update CKEditor to version 4.12.1.
IE 11 card headline styling was wrong
Workspaces without child workspaces where not correctly vertically aligned in the workspace carousel. This style problem only occurred only in IE-Browsers.
Default user group showed zero members in counter. Now it shows "all users"
If an external links that was generated with Stages V6 was unresolvable (e.g. if linked element did not exist anymore), the browser was redirected to "Home" page instead of displaying the "Element not found" page.
Some Automotive SPICE experts were confused by the usage of the term "rating" in compliance views. Now the term is replaced by "coverage".
Users were always redirected to Home when another workspace was opened. Now reports and also administration sections stay open on workspace change. This enables running reports in different workspace contextes easily.
An error occurred when the users were synchronized from an LDAP server if the database had been migrated from Stages 6 and the "default" user was assigned to any roles in Stages 6
Fixes an SQL syntax error in upgrade step 4415.
Search workspace tab in workspace navigation uses now the search engine and is much faster.
Reworked workspace navigation. Added a new workspace tree.
Updated unified configuration to version 2.3.
Renamings in files widget because the possibility to add links was not found sometimes.
Admin Job names could be assigned twice by renaming the job.
Uploaded scripts for reports and jobs could be larger than 16 MB, which caused a database error. Now the upload file size is checked for these types of file uploads.
Admin job of a user without a license was still allowed to execute.
Logging the files which could not be prefetched (cache could not be updated) and mailing the list to the administrator failed.
Fixed file operation 'Download & Lock'
Comments on process elements can now be fetched with element.getEntities("containsComment@SYSTEM")
The file status for files that had a lifecycle in the past was not displayed in MS Edge
The security level could be set for files attached to Guidance elements, which was meaningless, because only the process element security level is relevant for these files.
Files for Guidance elements that were uploaded to a "Database" repository could not be larger than 100 MB
An exception occurred when saving an element when a linked element existed for the element, the linked element was in a process with a different metamodel and a custom attribute that was configured for the real element did not exist for the linked element.
Invalid mail address could be stored in user settings cache. Now cache is cleared when data is invalid.
In the editor link dialog the element search suggested links to the element index for all elements.
Process elements could not be found by their custom attribute values after cyclic search index updates.
When creating associations using "Browse", associations with target elements in different workspaces could not be created at once - only the selected target elements in the last opened workspace were remembered.
"No Access" error occurred when trying to edit process elements in the Working Version while requesting another baseline.
It was not possible to suppress the update button in the phase-freeze-overview-widget. This is now possible in the metamodel via the showUpdateButton attribute of the phase freeze overview widget.
There was an internal error when a non-root user tried to save its settings after logging-out as Superuser
Files and collected files could not be used together on one page
Sometimes, an error occurred while browsing elements when inserting a link into the dashboard description
Script execution errors of administration jobs are now logged in script.log.
Enable access to images embedded in process element descriptions. getProperty("DisplayDescription").getImages(): Image[]
Files can now be collected, e.g. <widget:file-list translateNone=files.none path=artifact:*/>
Cleaned css files and removed plyr dependencies
EnsureDatabaseIntegrity step 3 failed, due to no longer existing database table.
Jobs for which the creator no longer exists are now paused. A message is displayed in the UI and the first user that edits an "orphaned" job becomes the new executing user. Jobs are now sorted like other objects in "Administration" and "Management" (recently added jobs first)
Add button was shown in bulk-delete mode. Now adding jobs while in delete mode is disabled.
Admin jobs operations/Quartz jobs and triggers were multiplied through renaming of admin jobs. The callbacks were not unregistered.
Administration job page was inaccessible when the scheduling of the administration job after the script upload "partially" failed.
Administration jobs expression is not a required field.
After Stages restart admin jobs lost their current state and next run trigger.
Adding a workspace with the pipe symbol in name lead to an error. Now a corresponding warning is shown to the user.
Administration job names could be longer than 80 characters (constraint from Quartz).
Workspace attribute identifiers can now start with a digit
It was not possible to edit the default user's settings in case mail notifications were active.
An error occurred when deleting an Administration job
Normal users (!= root) could not change home workspace settings in the user administration.
Updated stages message properties were not correctly loaded without a stages service restart.
When creating or editing a job, a cron expression could be entered that would never be executed. An exception occurred when these jobs were scheduled. Now, cron expressions with no next execution date in the future are handled like syntax errors.
When adding a workspace attribute of type "Selection", an error occurred when one of the options was renamed after the options had been rearranged
When editing an existing job, the "?" button inside the "Cron Expression" input field was not clickable in Firefox
Removed the state identifier "No Versions" in the files widget.
No CMS authentication dialog was opened, if a new version of an existing file was uploaded and the user was not logged in.
External URLs at Guidances and Artifacts were not clickable.
An error occurred when uploading a file on an element, if the repository that was used for files on this element had a repository type that was no longer configured.
Reverting a file lock failed in case the user was not yet authenticated against the CM system.
File properties validation of name, path and version implemented.
Images were not resolved when a process description was rendered via the facade e.g. for PDF generation.
Spinner did not disappear when CMS authentication dialog was closed by pressing the Esc key.
Security filtering of big amounts of workspace navigation entries was incorrect. This resulted in missing workspaces in the navigation as well as an internal error in the "navigate" tab of the workspace navigation.
Links in process elements element descriptions that were opened in a new tab (target="_blank") were rendered without rel="noopener". This was a potential security problem (see https://developers.google.com/web/tools/lighthouse/audits/noopener)
Hierarchical security filtering of workspaces did not work. Therefore it was possible to access a child workspace even if the parent workspace was not accessible.
An error occurred while displaying the "Recently Used Files" widget under some circumstances
In the navigation drawer the Descriptions item was shown without access permissions.
Windows installer created useless file null.
Upgrade of the reporting up failed.
Description elements could not be browsed when inserting a link in the Rich Text editor. Now they can be browsed (even without "Process Management" permissions) and there is a switch for the link type (normal link vs. inline embedding)
The description on the process start page was not correctly refreshed after inline editing the description.
migrateMetamodel script did not handle old target table entries correct when using an Oracle DB.
Existing associations or association comments were silently deleted after the following sequence of steps:
- Elements from two different folders (Folder 1 and Folder 2) are associated
- Modify associations using "Browse"
- Navigate into Folder 1, uncheck association
- Navigate into Folder 2
- Then, the association to the element in Folder 2 was not checked and it was deleted together with the first association when clicking "Save"
TWiki-Links to Description elements that are not defined in the Working Version could not be resolved.
Text in management charts was not correctly escaped
Process versions could not be renamed in the mobile view. The same error occurred when the rename operation was cancelled without saving.
The process version creation date was displayed twice in the process version list.
An error occurred while updating a process module when a tailoring element from the process module was overwritten
When processes with module installations were exported on one Stages server and imported on another Stages server, the installed modules sometimes could not be found (even if they existed at the same workspace path as on the other server).
After the export and import of processes with installed on-demand modules, the on-demand settings were not activated.
Sometimes, the Management > Process Modules page and the left navigation bar became empty after removing an installed module (observed with Edge and Firefox)
External links in descriptions could not be edited with the link plugin.
Process version export in Chrome was broken for process version names containing a comma
Phase freeze failed due to incorrect handling of the default element subtype
It was not possible to start an update of the valid version from the phase freeze overview widget.
It was possible to add new files to a frozen element.
Comment compliance associations got duplicated after update of the valid version.
The new inline descriptions were not considered correctly during phase freeze.
Only one user was notified request onchange handler when there were multiple recipients.
Memory usage could become very high when the global search indexer had to index a large number of files
Management charts were not displayed correctly in Safari
Increased weighting of search hits in user names to sort them even more to the top than search hits in full names. The config property "search.users.username.boost" now has the default value "16".
Administration job execution environment for Stages facade commands.
Administration > User Groups is now searchable similar to Adminstration > Users
Reactivated maintenance mode and reworked administration dashboard"
Workspace attributes and their values can now be accessed in scripts (facade v1)
Jobs can now be deleted.
Users can now be assigned to roles and unassigned from roles.
Added an optional setting to custom date attributes in order to show an absolute date. (<widget:element-property ... format="absolute|relative">)
An attribute help text can be displayed if the message property attribute.<ATTRIBUTE_TYPE_IDENT>.help is defined.
Process elements from on-demand modules can be imported selectively in assignment browser.
Allow deletion of imported on demand module elements
Elements from on-demand process modules can be imported by selecting them in the quick-assign field.
Provide phase freeze overview widget for process start page.
Phase freeze information can now be shown in element properties widget (Properties: 'frozen', 'freezePhase').
When a user tried to move a workspace below itself an Internal Error was displayed instead of a validation error message.
Adding a user to a group throws an error. Now creating groups and adding users works without failure.
Released new CMS packages including API, SharePoint, Subversion in version 1.2.1.
Fixed performance issues.
Released new CMS packages including API, Sharepoint, Subversion in version 1.2.0.
Anon user can now download files
Configuration property cms.browser.activated is now disabling/enabling the cms browser correctly
In the CM plan view, the lifecycle setting 'default' now uses the lifecycle, which is defined in the CMS profile of the corresponding repository, which is assigned to the work product.
Using correct translate keys for file start dialogs
Database upgrade from Stages 6 to Stages 7 failed when file-based resources (checklists, examples, templates or arbitrary files) existed which were linked by other resources and then were converted to element folders.
Files and Lifecycles were not accessible via Facade V1
Wrong process version was returned when calling pkit.getCurrentProject().getEntities('containsProcess@system')[0] and printing a process element
Upload file dialog didn't respond if CM system was not available.
An error occurred after downloading a file with Safari
Start options for files were not displayed correctly with Microsoft Edge
Download & lock was lost
The table width was only half as big as before after a rename of a group or workspace attribute in the Edge browser.
Deleted elements were not removed from popular elements
Element types of images were stored with incorrect case
In the MS Edge browser text was selected automatically after switching tabs in the workspace selection.
After copying a process with Microsoft Edge Browser the company process was opened instead of the copied process.
Roles with user assignments could not be opened anymore.
Initial process import with warnings resulted in a missing action menu on the working version in the process versions list.
Lifecycle settings of files from process modules were not adopted with module imports/updates.
When process modules were added, the first selected module was not preselected in the "Choose start page" step of the assistant.
When searching for process elements in the editor link plugin a sporadic error occurred.
Updated ARIS import DTD in oder to support newer ARIS versions.
Database upgrade failed if there were multiple tailoring roots.
In Internet Explorer 11 on Windows 7, the clickable areas in process element visualizations did not match the actual image content when the visualization image was scaled down.
oldDatabaseValue property had the wrong value when notification mail was created from mail template.
Calculation of the approximate number of search results was wrong when many identical results were merged. This led to wrong paging of the search results and could cause multiple empty result pages. Now the calculation is more accurate and the pager is correctly updated when an empty page is hit.
Search index update failed when a single process version could not be indexed due to database inconsistencies.
Search index cleanup of obsolete workspaces failed when more than 1024 workspaces were indexed.
Some useful security http response headers could not be activated. Now setting the config property "global.secureMode.enabled" to "true" will add the following headers to Stages server responses:
"Strict-Transport-Security: max-age=31536000; includeSubDomains"
"X-XSS-Protection: 1; mode=block"
"X-Content-Type-Options: nosniff"
Margins of attribute widget were not set correctly. "None" was not displayed.
Values can now be assigned to workspace attributes when editing the properties of a workspace.
Config variable properties can now be managed in the files conf/config.properties and conf/secret.properties in Java property format and used in config.xml and other xml config files
Workspace attributes can now be configured in Administration > Workspaces > Configure Workspace Attributes (menu item). There is a new permission domain (Global Attribute Management) that is needed for this action.
increased performance for rating updates
External links to elements that were migrated from one type to the other are now recorded and thus stay valid
Popular workspaces, process elements, process element types and guidance are now shown on management dashboard.
Workaround for IE11 hanging in redirects: now using HTTP 301 instead of HTTP 308. Value can be configured via new 'statusCode' servlet parameter.
Access logger now also logs process element read accesses
Workspace navigation allows navigating in a tree
Processes can now be copied. Added modules, identities and restrictions are reset.
Reworked JIRA feedback UI"
Process modules that are already (fully) integrated can now be turned into on-demand modules in Management > Process Modules (and vice versa)
Processes can now be imported from ZIP files on the process start page of empty workspaces.
Added documentation link as help to the support section.
Rename and adding a user group to a name that already exists lead to internal error. Now an already exists message is shown and the user can change the name.
The user was incorrectly logged in with SAML if the login credentials on the login page were incorrect. Now, the the user remains on the login page and an "Login incorrect" error message is shown.
Added missing headings for file-management, settings and user settings
Paging in the user groups administration lead to an internal error.
When SSO is used, the retrieval of the application context had produced useless error logs.
SAML users were displayed as local users in Administration > Users
SAML identity-provider-attribute-match could not match on SAML subject
When SSO is used, the retrieval of message properties produced useless error logs.
User profile was not updated in navigation bar. Now after save the picture of the user is instantly updated.
Load external libs from stages.lib folder
The "Select all" checkbox was not refreshed after changing folders in the CMS browser
An error occurred when clicking the "Up" button in the CMS browser before the folder was loaded
When the version of a file in the files-widget is fixed via the property menu, a click on that file will trigger the download for that specific version of that file.
Fixes a possible deadlock during recalculation of compliance ratings.
Migration of V6 image and description resources to V7 descriptions failed if the corresponding resources were overlaid.
Validation of file name length is set to 255 in file dialog.
Renaming a file in the file upload dialog does not cause an error anymore.
The cancel button of the files upload dialog now works like intended.
If a file is marked as "non-downloadable", it is no more clickable in the files widget as well as in the files history view.
Opening the file properties from the recently used files widget led to an internal error.
Fixed multiple problems that occurred when navigating inside process versions that contained a space character or other punctuation characters ("+", "?", "[", "]" and many other) in the name
- v6-style links to process elements were not redirected to v7 URLs properly
- Links in visualizations were not clickable
- Stages switched to the valid version when clicking a textual reference, instead of navigating inside the process version
Unfinished user operations (e.g. process module updates, creation of process versions) were not cleaned when Stages was restarted. This meant that these operations were shown as unfinished (rotating spinners) and could not be restarted.
Recently added objects were not displayed at the top of the list in various subpages of "Administration" and "Management"
Unix line endings (LF) were used for configuration and batch files instead of Windows line endings (CRLF), which complicated support with notepad.exe
Migrated images from version 6.x were always marked as invalid links in the process readiness check.
In a few cases an Internal Error was shown in case the user tried to view a process element that has associations to elements not readable by this user.
Description resources were not accessible without process management permissions.
The setting "process.resource.freezeRevisionsInBaselines" was ignored during process version creation.
In case a user opened a link to a process version he cannot read, he was not redirected to the readable valid version.
Switch for Common Elements was missing on workspace edit page
Description content could be lost when double-clicking "Save" in the inline description editor.
Replacing the working version of a process with a .zip export failed when the export contained the string "${...}" anywhere (names, descriptions, string attributes...)
DB Upgrade to V7 failed in case of image resources without a content name.
Fix handling of tailoring root during add/remove module. The tailoring root is handled as local element.
Equal search results were not merged in some cases.
In mobile views a blank was missing in the target workspace label of transitive user permissions.
In table view mode details of the working version were shown. Now only the name of the working version is shown (as it already works in list view).
Progress listener was not updated when ratings where recalculated
Permissions for the same workspace were not properly sorted by permmission domain
LDAP synchronisation messages were made more precise
Switching between process element edit pages lead to an internal error.
Switching from edit process version site back to
readiness check and back again lost details.
After switching between the usage and added modules tabs an ElementNotFound error occured.
The element search in the editor link plugin returned tailoring resource elements as search results.
Fixes an internal error on the tailoring answer page, that was caused by tailoring dependencies that were overlayed.
Internal error when logging in with no longer valid deep link.
Enable workspaces to be moved to another sub workspace.
The data source for a user (Local/LDAP/SAML) is now displayed in Administration > Users
LDAP ondemand mode was unable to save users
CM-Plan tab was inactive during clicking on plan elements.
Update tomcat to version 8.5.35 for security fixes.
Set focus and cursor to the end of a <input/> text
Switching fast between different tabs in workspace selection produced an error. Also favorites were not updated without closing the workspace selector. Now no error is produced on fast switch and favorites are updated instantly on tab switch.
PDF Diff Print produced empty pages instead of the Diff in 7.2.
Jira feedback now also supports creating "components" fields and "workspaceComponents" system attribute
Display a better message text in the search result flyout if there are zero or one search hits in other workspaces.
Upgrading a MySQL database from Stages 6.x to Stages 7 failed when the time zone of the server was east of UTC + 1h (Central European Time)
Findings1: wrong recommendation for WorkProduct Index Path, Finding2: Path recommendation for level 3 for none not as above suggested if the path edited and cleared
File Author is unknown, if file is uploaded via svn client without commentar and author tag
Wrong CM plan elements are available in different process versions.
The dashboard description was only editable from within the root workspace.
Comment-only mappings on reference elements could not be retrieved via Stages Facade API. Now this can be accomplished by using the association type "containsComplianceComment" in the "getEntites/getAssociations" query on a reference process element.
User feedback on process start and process index
User feedback into Jira Customfield of type "Select Lists"
Search results were only displayed after the 3rd character was entered. This was a problem for example when the search term was written in Easter Asian alphabets like (Chinese, Japanese, Korean). Now the search starts after the first entered character.
Clicked URL from files widget opens
in new tab.
Enable copy and move for tailoring questions and answers.
The logged in users page was not updated after a user session was logged out by the administrator.
Lifecycle names were hardcoded for the unified configuration process type.
Index elements could not be mapped to
reference model elements in the compliance widget by searching for index
element names.
Compliance Rating was not aggregated correctly under certain circumstances. Database update of compliance ratings was slow and performed in a single transaction. Now multiple transactions are used.
It was not possible to get the value of the process element property "Mandatory" via Facade API.
Clicking on a new report in the index view did not redirect to the report view.
Copying elements with associations in a process with a valid version resulted in associations between baselines.
Process module installation properties were not displayed on elements of installed modules when the origin process modules were deleted.
Media Switch through resize of browser window caused an error. Now Editables are cleaned on dataView when they are destroyed.
Links to guidance elements with a file were rendered as download links instead of a link to the guidance element.
Links in dashboard description always referenced the process elements in the valid version.
Character escaping in editor link plugin for textual references was wrong.
The error page "Element not found" was shown when a perspective was set which does not exist in the current metamodel view. Now the view falls back to the first perspective but the perspective setting in the toolbar stays in place. A corresponding message is logged to the browser console.
Allow Linux files to be owned by non-roon user
Link of View Permission at Users in mobil view is defect. Defect link navigates to workspace home but not to permissions of user group
User form fields where not correctly disabled when editing ldap, externally authenticated and system users.
It was possible to rename the user group "default" which removed all default permissions for users
File management was not available directly after creating a new process.
The process version switch was available when editing a compliance scope
A null pointer exception occurred if reference models were versioned in compliance management and process element views using the process compliance widget.
There was no autofocus on editing
notes in compliance rating widget
After changing the compliance
rating, unsaved had been lost.
Dependency associations of tailoring answers with process elements were not filtered by the process element types configured in the metamodel.
When a tailoring answer had a Description resource as tailoring dependency and the target of the dependency association was resolved, it had the wrong type (ProcessElementElement instead of DescriptionResourceElement).
Element with warning in files widget was
copied. Click on the warning icon at the copied element lead to internal
error.
The visual display of a lifecycle state which did not exist in the current lifecycle of a file was wrong (with question marks) in IE11 and Edge.
Project variables in URL from files widget
where not interpreted correctly
View and lock was not updated after canceling file operations from authentication dialog
File URL name character length was not visible.
UploadFilesDiaglog shows doubles the same named files without warning.
File link can now be copied through browser context menu.
update.bat restarts Stages
SAML POST responses might not be correctly recognized if they do not contain SAMLResponse URL parameter; 'autologin.tomcat.enabled' does not need to be set to 'true' for SAML (but '<authentication enabled="true"...>' still has to be set); 'assertionConsumerUrl' and 'logoutUrl' do not need to be configured anymore; fixed logout
Display newly added items at the top of the list in
- Administration > Groups and Permissions
- Administration > Groups and Permissions > Members
- Management > File Management > Repositories
- Management > Compliance > Reference Models
- Management > Compliance > Scopes
In Management > Compliance > Reference Models, paging should not occur any more and newly added scopes from a reference model appear first under the reference model.
Newly added users were not displayed at the top of the list in Administration > Users > All.
The first or last entry in a menu could be a delimiter if items were disabled.
Arrow ico was not avialable in reporting move dialog.
It was allowed to move reports among each other. Now reports can only be moved below folders.
Reporting move dialog contains workspace selection ico.
In assoc browser, dont display the workspace
when it contains baseline only or the user is not allowed to draw
associations between different process versions
After changing the metamodel, process element types of the previously selected metamodel were shown until the browser has been reload.
Inherited subtypes from process element parents were not migrated from stages 6."
Sorting process elements was not possible on touch devices
Switching to a Process Version with parenthesis in the name produced a routing error. Now parenthesis in PV Names get encoded.
It was possible to leave the Edit-Mode with Enter even though a required warning was shown. The old name was used. Now the user stays in Edit-Mode and the required error message is shown.
PV rename to existing pv name was resulting in internal error. Now a message is displayed and the user can edit the pv name.
deliver new metamodels on stages update
Double Submit on creation of empty processes was possible. Now button is disabled after submit and spinner is shown.
The email address of users was not displayed in the search box of user assignments to roles and permission groups though it had impact on the search results.
The user fullname was not weighted enough in user searches. Now the weight can be configured by the config properties "search.users.username.boost" (default 10) and "search.users.fullname.boost" (default: 4).
Users found by the search in the user administration were sorted by name and not by search score. So the best hit was not at the top of the list.
When creating a new process from module the summary page led to an empty page and not the process start page.
On IOS devices several clicks on the username/password input were necessary in order to open the internal keyboard.
The property "TargetRole" could not be retrieved from tailoring dependency associations.
The subtype property name was inconsistently written for process elements ("SubType") and tailoring dependency associations "Subtype". Now the process elements and tailoring dependency associations support both writings.
Report script upload was broken (in Stages 7.2.0.2 only).
In rare cases choosing 'select all' in
navigation selection mode (e.g. buld delete) did not select all
elements.
An internal error occurred after shortening the search term to less than three characters and pressing enter.
New elements could not be created when search result page was open.
Renamed compliance rating levels to none, incomplete, fair and complete.
The url of process elements or the process start page is now returned by invoking the method "getUrl" on the corresponding objects.
V6 style direct links are now supported"
Support & feedback phone numbers and email address on dashboard are now message properties.
Users that were deleted in Administration > Users did not disappear from the list (only after a page change or refresh)
Repository modifications are possible in process baselines.
When an element with a compliance association was copied or moved from the process model to the reference model or vice versa, a local compliance association was created which is not allowed. Now, compliance associations are not copied or moved with their elements in this case.
Compliance management modifications are possible in process baselines.
File icon and number of typed characters were not shown, table row was only partially highlighted when renaming files.
"Create" on "Processes" was required for uploading new files on Guidance elements, which was too restrictive (only "Modify" should be required)
Escape key had no effect when file was renamed; aborting rename dialog (e.g. with a click outside) and opening again did not reset name to original name
An error occurred when the user attempted to delete a file or URL and clicked "Cancel"
Restore animation on opening a popup dialog, opening the navigtion paste mode (clipboard) and switching to another workspace. In mobile view keep navigation open as long as the clicked entry has children.
An error occurred when navigating to a workspace without a process (using the workspace navigation) from the following locations inside a workspace with a process:
- Management > Compliance > Reference Models
- Management > Process Modules > Added
Report execution failed for users who had the Report Administration read permission without the Reports read permission.
Autogrow sets wrong initial height for textareas in popups
Progress was completed too early in case of creating a baseline that is also released as valid version.
Disable action buttons until switching the workspce in the navigation paste mode is completed.
Deleting the current element using the element menu did not update the view.
Process element links in descriptions were not displayed struck-through when the target element is tailored.
Restored v7.1 behavior and appearance of CMS browser:
- Last change date is not displayed for folders
- "Go to parent folder" and "Go to root folder" toolbar buttons are hidden in the root folder
- Height of CMS browser dialog is not depending on number of files and subfolders
- Fixed checkbox column width when last change date column is hidden in small resolutions
- Several other visual details
Add Files must not be available if the process is locked
In Internet Explorer 11, the table zoom placeholder was always shown for a table with images when the screen resolution was too low for displaying the images. Now, images in tables will be scaled down if the table width is a percentage ("%"). The zoom placeholder will be displayed if the table width is an absolute number ("px") or not set. Some other bugs have been fixed together with this issue:
- Table zoom placeholders were not replaced by the original tables when the window became larger.
- The scrollable area in the table zoom popup could have an incorrect width.
The setting "Use system account" in Subversion CMS profiles was not correctly imported with process exports from older Stages versions (< 7.1).
When a work product file was created in the Valid Version which also existed in another process version and then the Valid Version was replaced with the other process version, the file was duplicated.
When a user in users is edited,
the Toast appears two times with following message process version changed
An error occurred in IE11 when navigating from an page with an image using a image map to another page without an image and then resizing the browser window or changing the tab.
Do not allow version switches to versions that are not available.
Remember collapse state of element properties categories.
Use plural type the naming for the tailoring answer dependencies.
Added SAML authentication filter including user auto-onboarding and support for redirect and POST binding. Can be configured in new <authentication> section in config.xml.
The association browser selection was not up to date.
Association widget did not notify visualization about removed associations and modified comments.
Ensure security filtering for facade and TWiki Links considers baseline read permissions.
Module integration failed with an UnsupportedOperationException.
Show only the newly tailored elements after reexecution of the tailoring wizard.
Sorting of tailoring questions was not possible for questions from a module.
Do not collapse the menu when menu item is a switch.
Rework styling of tailoring assistent and fixed several bugs.
Navigation via the process visualization resulted in a baseline switch to the valid version of the process.
Reference models can now be added/removed via browser.
Provide widget to display the compliance associations of a process element grouped by reference model.
Added project variable support for descriptions, image maps and file pathes.
The tailoring preview does now warn about compliance mappings that will be violated by this tailoring.
Implemented Tailoring-Assistent
Adopted compliance API / facade to new compliance model.
Compliance rating and reference
model mappings are added/updated with process modules.
When a process element with child elements was moved to another process no new identity was generated. This caused a database constraint violation if one of the child elements was already added to the process by a process module.
The view storage location can be changed in CMS Profiles.
Process elements can now be assigned und unassigned in compliance scopes
switched workspace selectors and added close function
The currently viewed process version of a project can be retrieved by 'project.getCurrentProcess()'. The currently viewed process version of the current project can be retrieved by '$s.getCurrentProcess()'.
Added "stages" and "$s" aliases for variable "pkit".
Reports with cascading parameter groups are
now supported.
Reports in Stages are now always executed in the context of the current user whereas the Birt Designer uses the datasource user. It is not necessary anymore to wrap the report script in an "asCurrentUser.run" section because the behavior with and without this is now the same.
edit report descriptions
added pv switcher to reports
Parameter will be loaded after report site has been opened. Improves speed of report navigation.
A permission domain different to "Processes" can now be required for reading/creating/updating/deleting associations with a specific type by setting the "domain" attribute on the "association-type" element in process.xml
Tailoring root, questions, answers and their dependent elements can be retrieved via facade for reporting and diagrams.
Added widget for tailoring details
based on properties grid.
An error occurred when navigating between pages in Administration > Users > View permissions
Update tomcat to version 8.5.32 for security fixes.
Database upgrade failed with error "Index CONTENT_GUID_IDX not usable".
Fixes Database Upgrade Step 4222. An index was dropped incorrect.
Ignore cookies containing illegal characters. Log those cookies to a cookies.log for further analysis.
Wrong last modification date in SharePoint cms browser.
Reports could not be executed successfully in Stages without specified user credentials in their datasources. Now user credentials in the report datasources are only needed for previews in the Birt Designer and not anymore for report executtion in Stages.
Fixes a possible NullPointerException during process element description rendering.
The "Update" action for updating multiple process modules was not displayed when there were no updateable process modules on the current page, even if there were updateable process modules on other pages (fixed with previous commit e0cf69fb51a81e600479769fa098a5d7c4ae85a0)
Rendering a single word text that is slightly longer as the maximum renderable text length caused an exception in case the last character was a wide one (e.g. w, m).
Uploaded profile images where displayed too small when showing the crop preview
Rebuild script for closure tables and triggers added. Run script with 'rebuildClosureTablesAndTriggers'. Ensure that database user has sufficient permissions for CREATE TRIGGERS.
List of assigned reference models can no be displayed in compliance management.
Compliance scopes can now be added and deleted.
Added compliance and scope management.
Rating is displayed in the left navigation.
Migrating description images now tracks progress
Further performance improvement for the migration of resources to guidances
The database record for an uploaded file was duplicated whenever a process or process element had to be copied (for instance, when creating a process version or integrating a process module). Now, a hash value is computed for file content and the database record will be reused. Existing file content will not be de-duplicated.
Save parameter values in preferences service. Scroll to invalid input on renderaction and if closed, open dropdown.
Report parameters can now be entered.
Exporting reports to e.g. pdf is now available
Handle errors in report rendering.
play button and report dummy for rendering section in reports
Added downloadfunction to the script component
Script-upload is available for reports
All user permission groups which had creation, modification or deletion permission for reports receive an additional permission with the corresponding settings for the permission domain "Report Administration". Moreover the permission domain "Data Collectors" is removed.
Enable overwrite and restore of tailoring resources.
Enable sorting of tailoring resources.
Enable creation of tailoring resources.
Enable deletion of tailoring resources
Provide tree of tailoring resources in management section.
Enable manual tailoring of process elements.
Stacktraces of client-side exceptions are now mapped using the javascript source map files to be logged in the stages.log file on the server
LDAP synchronization failed when "generateDn" was set to "true" and LDAP search queries returned absolute search results.
The message "No users were found" was not displayed for empty user groups
"Add" mode was left after adding a new member to a user group
Ensure that the permission cache is updated in case the user is assigned to a new role or is assigned another license type.
JvmOpts were not set during installation of Stages service.
LDAP synchronization did not handle email addresses.
Add files dialog is responsive again
fixed cms path validation in mobile view
The query for existing content objects to reuse was implemented very inefficiently with #33219. Now, much less data is transmitted from the database.
Content hash column index is missing.
Fixes for overlay base association handling in comment, guidance, image and description upgrade steps.
Fixes the database upgrade for archived projects containing metric data collectors.
The upgrade of comments on process elements failed in case the comment contained textual references to other workspaces.
Log progress of closure table creation
New command line tool to fix Oracle database indexes for case sensitive columns.
Collected associations of processes with the type "containsComplianceExternal" did not have the reference process elements as targets.
Associations (pkit.getAssociations) were not baseline filtered.
Diagram rendering was slow especially if a lot of associations have been loaded. Associations can now be queried in bulk from pkit object.
An exception occurred when updating a Guidance file in a "Database" repository using "Add Files" > "Upload Files"
Update tomcat to version 8.5.28 for security fixes.
Update tomcat to version 8.5.24 for security fixes. This should also fix SSL keystore handling.
It was not possible to navigate from the workspace start page to the process start page after copying process elements.
Copying processes with guided tours having local corresponding elements of tour stops caused database inconsistencies (unidirectional association). This lead to followup problems (e.g. with Stages Composer roundtrip).
Associations in merged or derived association lists (e.g. when more than one target element subtype is collected) are now always sorted alphabetically by target element label. Associations appear before comments.
Associations of guided tour stop corresponding elements werre multiplied when a process with an corresponding element was copy or exported/imported.
Accessing a read/write locked process (e.g. during module integration) did not produce an accurate user notification.
Add missing association index to improve performance.
Process version switch loading was too slow.
Fix upgrade step to ensure unique process version names.
Associations were lost in the following scenario: A core process (A) was integrated into another core process (B) and then B was integrated into a process (C). In C elements were overlaid that were originally from A. After integrating A into C and removing B from C the associations of the overlaid elements were gone.
Stages used a very old user agent string (IE 6) when checking external URLs with "Analyze" > "Errors in process description", which caused some URLs to be falsely reported as inaccessible (because HTTP error 403 was returned)
Link to core process elements in an integrating process were lost after process export and import/composer roundtrip.
The working version could not be replaced with a .zip file exported from Stages Composer when the server had no Internet connection
Fix overlay base handling during metamodel migration.
fixed wrong display of "&" in translations
PDF print failed in case a multi lingual description was printed.
Ensure the correct localization context is set for diagram rendering.
Reduce memory usage during search indexing and priorize important process versions.
Improve performance impact of search indexing.
fixed quick assign for associations
Users without licenses received emails.
updated commentassoc custom filter. Commentassocs
with wrong or non-existent subtype are now displayed below the
defaultsubtype
Log progress of file based resource migration
visualized fixed version in context menu
and version history
Provide a script for content migration of Unified Configuration 1.1 processes to be compatible to Unified Configuration 2.0.
JPG files could not be downloaded from Stages CMS.
Cancelling the user authentication at a CMS repository led to logout from Stages.
File action "Set state" was not displayed when files had states that were not defined in the lifecycle configuration.
Images could not be inserted on process start page. Inline edit was not available on process start page.
Roles could not be opened after Stages 6.x upgrade.
Descriptions on process start page were not saved.
fixed wrong title in repositories section.
Asking now for state params scope and not for stateparams scope
Database upgrade (Oracle) failed when creation date and creater were copied from history table.
In some cases the search filter was shown twice when the browser window was resized.
When the type filter on the search results page was used and the workspace filter was then changed to a selection which does not contain the selected type, the type was not displayed anymore in the filter but it still had impact on the results. Now previously selected types which are not contained in the current workspace selection are shown in the type filter until they are unchecked.
Element type names in the search results filter options were not properly translated when they were not defined in the metamodel of the current process.
Enable Enactment Export
Display license details on administration dashboard. Also added fix for permission error on logged-in user tab
new names for licenses
Multiple files can now be linked at once using the CMS browser.
Existing files can be linked by entering the file path manually even if the CMS browser is not available for some reason (not supported, disabled in configuration, structure prefetch hasn't run yet...)
The CMS browser has been redeveloped for Stages 7, and existing files in Subversion, ClearCase, SharePoint and Integrity can be linked to a process element now.
Enabled individual file operations (and
authentication) for external configuration management systems.
Allow user to add information from external systems
Enabled API cache by default (scripting.api.cache.enabled)
Paths in the CM plan are now validated against the "validatePath" pattern that can be configured for a CMS type in config.xml. Validation happens only when the path is changed in the input field.
Recently added files are now shown first in the file lists/tables sorted by their creation date.
If the CMS systems allows file attributes for checkout (e.g. Serena Dimensions) a dialog is shown when the user clicks on "Download & lock"
Files that are stored in the "Database" repository, and URLs now have a timestamp and last change user that is independent of the timestamp and last change user of the process element. The timestamp and last change user of database-managed files is only updated when new content is uploaded, not when changing the file properties. The timestamp and last change user of URLs is only updated when the actual URL is changed, not when only the display name is changed.
Immediate upload and set lifecycle
state allowed.
Improved responsivity of several file actions because required permission checks and initializations are now executed asychronously.
New permission domain for revert other users files.
SharePoint: It is possible to configure per lifecycle state whether major or minor versions shall be created when the state is set (Example: <state ident="draft" majorVersion="false"> means that a minor version will be created when the state is set to draft). Major versions are created by the default when nothing is configured in the lifecycle or no lifecycle is used. This default behavior can be overwritten in the CMS host properties by setting '<cms-property
name="major.versions" value="false"/>'.
Files can now be updated via drag and drop
File states can be changed.
CMS file attributes can be edited
Download & lock a file in a single click in the context menu.
File errors are now shown in file list. Content of database managed files can now be replaced.
Implemented file properties dialog and inline rename of files.
Reworked file list on element pages. Added date, author and state.
Stages Restrukturierung
refactored and updated whats new section at dashboard
Enabled inline-editing for custom-attributes
Custom process attributes are editable on the process (element) page and can be displayed in the element properties widget.
Allow custom process validators by specifying names of classes implementing the Validator interface.
User role assignments can now be shown and edited.
Show the "Files" widget only if the current user actually has the permissions to view files (don't show an empty widget if not).
File presets (settings from cm plans) are no imported with new file container elements (artifacts, guidance) of process modules.
Process module installations/updates now will create missing repositories for files.
New structure for metamodells, all required files for a single meta-model will be contained inside an archive.
The "file-table" and "file-list" widgets can no longer be restricted to a single file in the metamodel with the "single-file" parameter. Multiple files and URLs can now be added to Guidance elements, because the hard-coded restriction to a single file has been removed. Navigating a textual reference to a Guidance element with multiple files will open the element.
Implements PDF creation via freemarker templates for V7. Integrate a progress indicator for PDF generation.
The default search scope can be modified and stored in the user settings.
The global search can now find files by their display names, physical names or urls.
custom attributes can now be displayed next to search results
Choose the correct baseline for ALM export
Enable Stages 7.1 update
Renamed user group into group.
Users with a user name containing a space or comma were no longer able to log in to Stages, due to tomcats stricter cookie handling.
The first character was cut off when entering a path manually in the CMS browser without a leading "/"
Work Product could not be opened if a file was not accessible.
Show checkout user when file is checked out. When the file is checked out in the CMS only the CMS username is displayed except when Stages uses a system account for this CMS. In that case only the lock icon is shown but no checkout user at all.
When a file was uploaded and a file with the same (physical) name existed in the CMS folder configured in the CM plan, the existing file was linked without any message to the user, and the uploaded file was not used at all. Now, a warning icon is displayed.
The "password" field was auto-filled with the Stages password when adding a repository in Management > File Management, if the Stages password was saved in the web browser.
CMS browser could not be suppressed at resources with cms property 'cms.browser.activated'.
Fixed file upload to ClearCase server.
Wrong version number was displayed when an older file version was selected by the Config Spec.
Display the committer username instead of the claim in the file revision history.
fixed path suggestion for linked files
fixed savebutton behaviour on form validation
and setstate translation for set version state dialog. Also fixed internal error at setState Dialog for processversions.
added form validation and missing css classes to edit.html. Changed file dialog button styles from ok to save
Unreserved checkouts caused wrong version history display and wrong current version.
Upgrade failed and roles could not be viewed using oracle database.
When creating a Diff PDF Export, no diff was displayed at the location where a description resource was included, because the description resource was always included from the current process version.
When a .zip export from Stages 6 or Stages Composer was imported, the lifecycle was set to "None" for files that had the lifecycle set to "Inherit from document"
Prefetch didn't work.
File state of checked out files could be set.
Wrong file path was used under certain circumstances.
Locked files were not updated via drag and drop."
A message property was not resolved in file management plan."
File management is now accessible with file management permissions (file permissions are no longer required). Fixed security exception in file management plan when a process element was not readable due to it's security level.
Uploading a file after adding it produced an error.
Newly created repositories were also visible in the management sections of other workspaces until the browser page was refreshed.
Fix upload progress bar for IE11.
Ensure that only one file can be uploaded in checkin use case. Improved conflict handling for the add files use case.
When uploading a new version for an existing file, the display name was set to the file name of the uploaded file
Lifecycle was not set on newly linked files.
It was possible to change the repository of a file from "Database" to a CMS repository (and vice versa) in the File Properties dialog, which lead to various errors.
When elements with files were copied, the file copies were not accessible because no repository was set. Now the file copies are assigned to a repository if a matching one is already available in the target process.
When displaying the version history of a file, the author was only displayed for versions that had been checked in with Stages Web. Now, the author from the configuration management system will be displayed if the author in the commit comment is empty.
fixed state display of files. If
there is no version, nothing is displayed. Else the state is shown
Guest user (anonymous) could not download file when it was necessary to enter credentials for an external configuration management system.
Login as guest was marked as link
When a users home workspace has been deleted it was possible that in certain cases the user was no longer able to log into Stages.
When a single file checkin or module installation failed, the other items that were added could be displayed as "in process" forever without any chance of removing the item.
Update tomcat to version 8.5.20 for security fixes.
Process element abbreviation was not included in ms project export. Element type names are now translated correctly.
Fixes the validation of metric collector intervals. The end date must be in the future.
Inline rename of process elements with abbreviations was not possible.
Ensure alignment is considered for embedded images that are migrated from V6 image resources.
When an element description was changed using the "Edit" button in the "Description" widget, an incorrect user name and change date was recorded in the element history ("Activity" widget)
Use correct URL schema for management descriptions.
It was not possible to edit the description index element.
Moving a process element to another workspace and deleting the source process could have led to exceptions in the process element history (activity stream).
Permissions were not checked correctly in Management > Descriptions, and the demo database contained some other incorrect column definitions.
A scrollbar was shown below process element descriptions if a large image was embedded.
Releasing a process version as valid version didn't copied repositories.
It was not possible to release a valid version in case the process referenced a CMS type that is no longer configured in config.xml.
Could not create a process version when an overwritten guidance with file existed in the Working Version.
It was not possible to view the module integration summary, when a new process was created from modules.
Process modules created with Stages V6
could produce duplicates for Guidance and Description elements on module
integration.
New images in element descriptions were not imported when updating an integrated process module
An exception occurred (in Stages 6.6.5.1, 6.5.10, 7.0.0 and newer) when integrating a core process in which a public scope of a non-existing reference model was referenced.
When an element in a core process was renamed and a new element was created with the old name, core process updates using the "Adopt existing elements" option could fail with a constraint violation or produce incomplete results.
The navigation bar animation was displayed when executing "Overwrite" or "Restore" on a process element.
The tailoring user and tailoring date for tailored elements were not preserved properly when these elements came from a core process and the core process was updated.
Elements with a backslash character at the end of the element name could not be linked nor embedded in description texts.
In the latest versions of Edge, the Rich Text Editor lost focus after pasting text and opening dialogs, and did not have focus after it was opened.
"Insert directive" dialog styling was broken in Chrome
Paste from plain text editors (e.g. Notepad) into the rich text editor pasted no content in Chrome
Images in process element descriptions could be falsely considered unused and deleted even the rich text editor was quit with "Cancel"
After importing a Stages 6 process export, the included and migrated url-only files could not be downloaded. Now the migation is done correctly and already incorrectly migrated files are fixed.
Fix validation of preset report parameters without a preset value.
Support user parameters for visualizations in PDF print.
Do not duplicate content during resource to guidance migration
Resources of deprecated resource type 'artifact' could not be edited anymore.
Resources could not be downloaded on process element pages in no portal mode.
Fix splitting of long element names to multiple lines of text.
The experience level for the Anonymous user was not returned correctly by User.getProperty("Profile.ExperienceLevel") in the facade, if no cookie for the experience level was set. One effect of this was that a visualization that did not match the preset experience level was rendered in process views for the Anonymous user.
The issue filter selection was lost when switching between different pages of a paginated issue list. The details of the selected issue filter were not restored correctly after navigating to a different workspace and back to the issues of the original workspace.
Fixed position of filtername input field.
Requests were not filtered by the selected request filter after switching between workspaces.
Fixes a NPE that could have occured in case a lot of users were notified about a changed request via a ftl email template.
Issue filtering did not work for save onChange attributes using the not defined filter option.
It was not possible to restrict issue fields to dates in the future. It is now possible to specify an earliest and a latest offset relative to the current date for validation on change, by defining period values in the "earliest" and "latest" attributes at the date field definition in the PKitRequest.xml. The values need to be written in the period notation as in java.time.Period. Example for the current date: "P0D".
Request tracking using java scripts with database queries was slow. Added an api cache which can be activated through the following configuration property: "scripting.api.cache.enabled". This also improves the performance of visualizations. In order to use this cache when storing issues in the database the configuration property "request.write.cache.enabled" needs to be activated too.
Stages shutdown failed when search indexing was running.
Search index was not updated when custom attributes were edited inline.
Heading in confirm dialog was out of alignment
fixed doubled slash at uploaded file
Introduce new security domains for module management, module override and process management. Users with permissions Processes RMCD secret will receive module management and process management permissions on upgrade. Users with Processes M secret will receive Module Override permissions.
Settings of a workspace can be edited. The following workspace settings are supported: name, language, archived and (project) group.
An overview of all user permissions can no be shown.
It is possible to rename user-permission via the context menu.
Existing URLs that are attached to Guidance elements can be edited now.
Added file version history in the UI.
The "Log out" entry in the navigation bar is now smaller to prevent an unintended log-out when clicking on the "Floating Action Button" (Plus-Sign).
The G1 garbage collector is used by default which generally performs better.
Dashboard for the Administrationsite to display information about Stages and it's supporting technologies
Convert the image resources to description resources. Adapt textual reference resolving to the new element and resource types.
The menu-item for multi-delete/copy/move of process elements is available, if at least one of the child process elements can be deleted/copied/moved.
The name of a process element can be changed via the element context menu.
It is now possible to delete all process versions in a workspace on the "Management" page, so that the workspace is reset to an empty workspace ("Delete Process")
Support for comment-only associations
Fixed comment count and updated layout
Shortnames are now displayed in the UI when they are enabled in the metamodel
Added process modules can be updated with newer Valid Versions.
Widget to show properties of module-elements
Display progress and errors in Module Management for operations that add or remove modules. Also, show an error message if the creation of a process from modules failed.
Added process modules can be removed in module management page.
New process modules can be added in module management page.
Process modules can be selected from a workspace tree.
Overwrite and restore of single or multiple process module elements.
List of added processes modules and list of updateable processes can now be shown in process management.
Improved progress display during process module integration.
Responsive handling of tables with a fixed or minimum width in process descriptions.
Oracle fulltext indexes are no longer needed.
Install elastic search as Windows service named Stages Search
Configured session timeout was not applied.
Pager was not visible on process module page.
Grants for permissions that are independent of scope and level (e.g. User Group administration permissions) could not be overwritten by denies.
The settings tab on the user administration page could not be opened in Firefox when the login credentials were saved for the edited user.
Introduce the new permission domain 'process import/export'. User with this permission are able to import and export the whole process without restrictions.
Fixes the storage format (master_guid) for migrated CMS profiles with MySQL.
Files stored in the database repository had a download filename without extension. Now the extension of the uploaded content is preserved.
Ensure only a single database repository can be created. Ensure a new process has always a guidance database repository.
Associations between resources and tailoring answers were incorrectly upgraded.
Process owner roles were migrated to user groups.
Fixed resource to guidance migration.
Facade API call to retrieve active compliance scopes for a process was missing; new entity 'containsComplianceActiveScope@SYSTEM' added
The properties "IsDeputy" and "Comment" can be retrieved from the "containsUser" associations. The "containsUserRole" association has been removed.
The property 'Name' was not available in facade v1 for process elements and index elements.
The properties "IsDeputy" and "Comment" can be retrieved from the "containsUser" and "containsRole" associations. The "containsUserRole" association has been removed.
Not all properties of Metric Reports could be read via facade.
Messages in confirm dialog were escaped twice.
A fallback for unsupported browser languages was missing. Now the first supported language is used when the browser language is requested but not supported.
Workspace name was not escaped correctly in workspace selection
Stages 7 could not be opened after upgrade from older stages versions due to a cached redirect to index.jsp. Now all .jsp requests are redirected to index.html.
Creation date of process elements was set to a wrong date in mysql5
License errors (e.g. "License has expired") are checked sooner. A warning is shown on the login page, if the license will expire soon.
Enabling the configuration property "global.secureMode.enabled" also enabled IP address change detection. This was undesired for some use cases, so IP address change detection will be enabled with a separate configuration property ("global.preventIPAddressChanges.enabled") now.
Update tomcat to version 8.5.13 for security fixes.
Do not package mysql and oracle driver due to license issues.
Preserve the jdbc driver jar (mysql.jar or ojdbc.jar) during Stages upgrades.
Processes with linked resources could not be deleted after upgrade to Stages 7.
Fixed multiple problems that occurred when adding/changing/deleting associations using the association target "Browse" dialog:
- The association comment input field was not displayed in the "Browse" dialog
- An error occurred when adding an association together with a comment for the same association using the "Browse" dialog
- An error occurred when changing an association comment and deleting the same association using the "Browse" dialog
- The association list was not updated properly when only association comments were changed using the "Browse" dialog, without any deletions or additions of associations in the same action
fixed overwrite/restore update problem
Inline editing on process start page was defect.
An incorrect element type label was displayed for readiness check errors that were reported for the process itself (for example, description link errors on the process start page)
Multiple and fast mouse clicks on the save button when editing process elements produced a "Cannot transition to abstract state '^'" error.
Ensure hover text is available on the process index pages.
Fixes a security exception when trying to delete an association of an integrated process module.
When displaying process elements, links were resolved with an incorrect process version of the target process.
The start page of a deleted process was not displayed correctly.
Process Version Management was not available without security level secret on domain Processes.
In IE11 the context menu for a process version could not opened directly after renaming it.
Element type names in validation messages of process constraint check were not translated.
renamed logmessages from core process to process module. PkitProperties for module updates are changed to single expressions while module add properties are described as module selection.
After selecting multiple process modules for an update and clicking "Update", the module list was not switched back from selection mode to normal mode
An exception occurred when attempting to view the usages of a process module if the user did not have the permission to add other process modules to the module
When creating a new process from modules, an empty process was displayed instead of a progress page.
In IE browsers newly inserted tables in the description editor had too small cell heights.
Fixed element search in link plugin.
Individual metric report parameter settings were imported as preset parameters for all users. Now the individual report parameters are not exported anymore. This means that operations like process imports, core process updates and replacing working revisions from ZIP export files will provide/replace the preset report parameters and will overwrite individual parameter settings.
Process imports could produce StackOverflow errors when they contained linked elements (shadows) and the remote (real) target elements could not be retrieved while their workspaces could be retrieved.
An Exception was thrown in pdf diff under certain circumstances.
Process Locking was not considered for determination of available operations. Also the check whether an element can be moved was not correct for protected elements.
It was not possible to delete a process containing an overlay element in case process element history was activated.
Element descriptions in the search results were not correctly escaped.
The search indexer failed completely when an exception occurred during the indexing of a single element. Now, an error message is logged and this element is skipped.
Long file names were not wrapped correctly in the "Files" widget in IE11 and Edge when the table view was displayed
The edit context menu for process elements was available on management and administration pages in the mobile view. Now it is hidden there.
Clicking on a workspace selection (User Settings -> Start Workspace, Administration -> Users -> {any user} -> Start Workspace, Administration -> User Groups and Permissions -> {any permission} -> permissions -> Workspace) with Firefox did not open the workspace selection dialog.
Added a filtering search-as-you-type box in the user administration.
Added file management plan.
File repositories can now be displayed in process management.
Introduced transaction safety for MySQL. Tables are converted to the InnoDB engine.
Implement file policies.
Implemented basic file operations (add file, add url, checkin, checkout, revert, refresh).
Implement security filtering for settings dialog
New delete process elements ui. Keep scroll position when navigating to sibling elements.
Navigation entries are now grouped into categories.
Moved workspace navigation into navigation drawer. Added a service section to navigation drawer.
Added my and archived workspaces tab to advanced workspace selection.
Initial version of MessageProperties service.
Replace milonic action menus by the new menu framework
Implement Access Control Lists evaluation
Introduce license service for filtering e.g. NavigationEntries for whether an app feature is active.
SSL client authentication can now be used for SSO setups.
Switched to a frameless application layout.
Moved process export and import to version management.
File repositories can now be managed.
Work Products of the "Unified Configuration" metamodel had misleading role names for associations to Activities.
Processes of kind PROCESS_MODEL are migrated to CORE_PROCESS in database and ZIP import. The search index (not the whole process) is updated when settings are changed.
The state of a process version can be changed, optionally updating the states of all process elements. It is also possible to release a process version as the Valid Version, including the state change options.
The working version of a process can now be replaced with another process version. Project data is copied from the previous working version if it is also the valid version. When creating a new valid version, project data is copied from the previous valid version. Ongoing process version operations are now displayed in the process versions list. Clicking an ongoing process version operation will display the progress indicator for this operation.
The process element comments are fetched on demand (paging).
Fixed a merge conflict. Fix for commit: b7796768ecfb982a342ee2fe94b139e22ead1a47
Implemented deletion of process versions. Single or multiple versions can be deleted. This is a very fast operation, because the selected process versions disappear instantly and are deleted in a background job.
Configured perspective is now preserved.
Process versions are now created in the background
The creator of a process version is now stored in the database and displayed in the UI
Process versions can be created now in Management > Process Versions
Process versions are now displayed in the "Management" section
New UI for quick (search as you type) process element assignments.
Group associations per target role or target element type
Added copy process elements feature.
Introduced new floating action button in order to add new process elements.
Initial version of process element creation based on subtype.
New process element comments view can be displayed by adding the element "widget:comments" to the view of a process element (sub)type in the metamodel.
Introduced new process element type "guidance".
Implement process element browsing backend.
Developed new process navigation ui (browser).
Unique process version names are now be ensured.
Process version name can be edited.
Display warnings and errors of process version creation operations.
The currently selected process version can be switched in the process views.
Before creating a new process version, the process can be validated (e.g. process element state validation).
New process can be created from modules.
New editor link plugin to create and edit links to process elements
Upgrade CKEditor to version 4.5.2.
Make GWT code runnable with AngularJS.
The working version can be replaced with a process from a .zip file now
Group associations by association type or target element subtype
Tabsets are now supported in metamodel views.
Internationalized messages can be configured using widget:translate and widget:translate-values.
Element, index element and process start page layout can now be defined via PKitProcess.xml.
Introduce metamodel specific views for the process start page.
The allowed subtypes for new child elements can now be configured in the metamodel (see Metamodelling Guide for details).
Introduce perspectives for metamodel views in new metamodelling scheme.
Enable process visualisation for new metamodelling scheme.
Enable configuration of attributes and element description in the new metamodelling views.
Basic association-list tag.
Support user defined visualisation settings.
When processes are both - valid and working versions - process interfaces will also be shown with both process versions.
Added baseline filtering in the global search.
Provide process element history timeline as a view component.
Workspace list can now be filtered by name.
No message was displayed when the search engine is not available.
Correctly set the focus on the first input field of both tabs of the form for editing users.
Workspaces could not be deleted while another workspace was still being deleted.
Password of ldap users was editable.
Ensure database upgrade step 2722 is more robust in case of database inconsistencies.
Tomcat log was not created anymore on Windows Servers
LDAP synchronization could overwrite system users (e.g. "root") if such users with matching upper-case names were imported.
prevent assignment of admin license to other user then root
Permission exception on the user notification settings page.
Run of update metamodel as administrator, can cause error.
The workspace property 'workspace is not active (e.g. stopped or archived)' now also disables background jobs (CMS Prefetch, Structure Prefetch, Resource Synchronization) in addition to metric collectors. This avoids irrelevant administrator notification mails. Also clarified consequences of inactive workspaces in the displayed message.
Fix caching of non existing file links on Overview page.
Management overview could not opened when a file configured to be displayed in the management overview had a CMS error.
Fixes a potential ClassCastException in Integrity adapter in case the file does not yet exist in the CMS.
Files with fixed revision display lock icon of wrong revision. Invalid file version was exported (via CMS Documents Export or HTML Export), if fixed version was set.
CMS browser could not be deactivated if desired. It can be globally deactivated now by setting the configuration property "cms.browser.activated" to "false". Note: If there is no intention to use the resource synchronization feature either, the background job "CM Structure Prefetch" can be also deactivated by setting "cms.structure-prefetch.activated" to "false".
Copying process does not consider the predefined CMS comments.
Predefined comments in CMS profile could not be edited.
NPE error during execution of 'restoreCheckouts.bat' script.
in combination with mysql instead of the latest the oldest version of Resources and ArtifactInstances was displayed
No Config Specs was wrongly identified as a configured Config Specs with MySQL
Whitespace at the end of a Change Package Id was not deleted.
When a Subversion CMS profile was saved and a wrong url for a subversion repository was used, the subsequent error message did not point to the wrong url in some cases.
Create and modify operations were available for Subversion documents even if a read-only system account was used for all operations.
A missing SVN host configuration was not correctly detected and logged.
Subversion authentication failed sometimes although valid credentials were given.
When credentials for a CMS connection were changed in the meantime, the manual CMS authentication was not triggered again.
An Exception was thrown, while checking an availability of a sharepoint file.
Workaround for illegal SharePoint responses with control characters not allowed in XML 1.0.
Change State without file upload failed under certain circumstances
svn tortoise can create invalid properties, we will now handle gracefully
Core protected reference model assignments cannot be deleted.
No spinner visible during loading compliance reference mappings.
Username and password column (oracle) for repository configurations was too short.
Recreating the existing foreign key constraints for the InnoDB MySQL database engine (all existing FK constraints were not created in MyISAM). Converting all columns, tables and the database to use UTF-8 character set and the utf8_bin collation. All new columns and tables will be created with the UTF-8 character set. Capitalizing the quartz table names due to case sensitive file systems (e.g. ext3/ext4). The last changed timestamp wasn't updated after changing an element in the element table, as well as in the history table in the database. Updating the MySQL connector from version 3.1.12 to 5.1.40.
Refix for 30141: Cleanup of duplicate mapping attribute associations (e.g. custom ratings and custom comment in Compliance Workbench) failed sometimes.
Database cleanup script could not handle duplicate mapping attribute associations (like comments of custom types in the Compliance Workbench).
Sometimes records were being saved more than once if no modifications were applied.
Clob values produce error during database upgrade with oracle
Clients with unusually long FQDNs were unable to use Stages because the values could not be saved into the database. Increased the maximum length of the corresponding database column.
Association with domain SYSTEM fetches all elements which leads to poor performance. New system association filter fetches only local elements (e.g. process.getEntities('containsRole@SYSTEM,elementClass=local').
User role attributes are not available in facade V1.
Queriying custom comments or custom ratings via Facade V1 resulted in an error when the reference element had more than one of those.
A NullPointerException occurred when a no longer configured metamodel was used and accessed via facade.
In freemarker facade (v2) the way to determine whether the working revision of a project is locked was inefficient. Now projects have the new method "isWorkingRevisionLocked()".
Under heavy load it was possible that freemarker process element views produced an IllegalArgumentException.
Resource revision properties not available in facade V1.
Multiple Resource properties, the effective user language and lifecycle information for Artifacts and ArtifactInstances where not accessible, further CoreProcess mappings for Processes and ProcessElements where missing
Attribute change link not available in Facade V2.
Resolving all roles of a user could lead to SecurityException in case one of the roles is within an unreadable workspace. Those roles are now filtered out correctly.
Using an empty string as filter (as intruduced with 28726) can lead to various problems and has been disabled again
ProcessElementClass filters do now apply to Comment-only too
It took very long (minutes) to open file upload dialogs or the loading even failed when a big number of users (thousands) could be selected to be notified by email. Now the number of users to be displayed is limited by the configuration property "user.view.limit" (default value: 1000).
Downloading CMS-managed resources in process versions via associations or search results always delivered the latest file revisions. Now the fixed revisions (which were the latest resource file revisions at the time the process version was created) will be downloaded in process versions.
When lifecycle state names contained whitespace characters their names were not displayed correctly in email notifications about status changes.
Update tomcat to version 8.5.9 for a Security Fix and fixing a potential BufferOverflowException.
Fixed a client-side memory leak on the dashboard caused by embedding videos.
New tomcat version 8.5.8 that includes several security fixes.
Fixed broken links in listing of used open source frameworks.
Update of Oracle JDBC driver to the latest version
Tomcat 8 uses UTF-8 URIEncoding by default.
Name-based external links were broken if the names contained UTF-8 special characters.
External packages codemirror and ckeditor came with unused javascript files on Stages installation
When Internet Explorer and Kerberos SSO is used, it was not possible to relogin after a logout without a browser restart. Furthermore negotations with multiple roundtrips did not work and resulted in failing authorizations.
Remove Stages Support contact information on the login page.
upgrade Tomcat to 7.0.64 for various security and performace fixes
Index elements were not displayed in plural naming mode in navigation drawer
When a process with an integrated core process was copied which contained associations with assigned enactment scripts and overlaid source or target elements, the process copy contained errors: Enactment scripts from the original process were referenced. This lead to the follow-up problem for RTC exports that the affected :associations were exported with the default enactment script.
Tasks with remote association (e.g.mappings to reference model) to element type 'Phase' are not exported to MS-Project.
Don't fail during process update if multiple LOST+Found folders exist
In Stages Composer, the state of a process element was updated when the value of a project attribute was changed. Now, the scope of custom attributes is exported in .zip exports so that Stages Composer can handle them properly.
The state of a process/process element was not updated when the value of a custom process attribute was changed.
Use Pkit.properties to translate attribute values
Project attributes for which default values were defined were not initialized with these default values until the attributes were edited.
When default options were defined for a custom multi-selection attribute, these default options were always selected when editing the attribute, even when "no options selected" was saved before.
UserRole assignment was unusable slow when high numbers (> 50.000) of Users are assigned to a Role
Logout and Return button performed no action.
Adding or replacing users in role assignment dialog displays errors or wrong assignment information.
make user role assignment dialog more robust
Process element index can be extended beyond a-z by using the "process.index.characters" ConfigProperty, for special characters like § oder ÄÜÖ or Japanese/Chinese ... languages tomcat and stages must have an UTF-8 setup
Two images with a name only different in umlaut/non-umlaut could not be uploaded in the description of one process element.
Unicon validators did not check process elements (including shadows) which would be shown as having the default (=first configured) subtype, but actually didn't have it in the database.
Error markers for process version names and user names which were shown after a server-side check for uniqueness were not removed after a change of the input field
It was possible to create two Valid Versions in one workspace by two concurrent 'Release as Valid Version' actions. The second action will now fail with an error because the Valid Version is locked.
When a new process element was created in association list it got the wrong subtype.
Prevent ConcurrentModificationException in assignement dialog.
Copying/linking elements could cause illegal parent element references when user session were shared in multiple browser tabs (which is not supported). Now copy/link actions will fail in these cases instead of causing database inconsistencies. Additionally, the dababase cleanup script (ensureDatabaseIntegrity) now moves process elements to top-level when they wrongly have a parent element from anoter process.
"Analyze local elements" function also listed integrated core process elements. Now it only lists elements which are not dependent of a master in another process: No links to other elements (shadows) and no integrated core process elements.
While changing the resource type of a CM managed resource to image without uploading an image no proper error message was displayed.
When a process model was instantiated, local reference model scopes of the process model appeared as public scopes in the derived process instances.
Switching to unsafe mode without process lead to a NullPointerException.
Pressing the return key in the association comment field caused an unintended form submit. The return key is ignored now.
Analyze errors in process description returns incorrect cycle.
Process elements with short names had different sort order in element index tree and element children list.
Unclear error message when privileged state was set automatically.
Link of process version was corrupt in case the version was created with warnings.
It was not possible to leave the process version rename mode via return without changing the version name.
Fix styling of process readiness check.
Global and association constraints can now be configured with a severity of either 'error' (default) or 'warning'.
Adapted constrait checks in Unified Configuration: missing responsible roles have severity 'error', missing output work products have severity 'warning'. Global checks (state, links in descriptions) are enabled. No other checks are configured.
Process readiness check was not available as a standalone operation.
The import, deletion and release of a process could be executed when an operation was already in progress which could lead to inconsistencies
Fixed permission check for the process import in case the working version is also the valid version.
If 'process state management' is disabled, it is still possible to set the state of a process version, but updating the state of all process elements is not available in the dialogs for 'Release as Valid Version' and 'Set State'. Additionally, the icon and dialog title for 'Release as Valid version' has been improved.
Improve process version list usablility.
Multiple process version creation possible by double submit.
Fix order of menu entries.
When selecting multiple process versions for deletion, a click on a page button would leave the selection. The paging buttons are now not available during selection.
Creation of a new valid version was not possible in case the process contained images.
When a new valid version was released it was not possible to copy the project data from the previous valid version but skip the metric reports. Now this can be accomplished by setting the config property "copy.project.data.releaseValidVersion.skipMetricReports" to "true".
Deleting remote associations in process baselines possible.
Updating an integrated core process failed if a comment-only association was deleted in the source core process and the affected core process element had multiple comment-only associations.
The core process update option "Import all, replace existing and delete irreplaceable" for metric reports and data collectors had no effect if another option was chosen for files.
Releasing of an integrated process baseline as valid version removes master_process_identity of project data.
The parent/child hierarchy between overlays was lost when replacing the working revision
Update link in list of integrated core processes was displayed, even if process create or delete permission on level secret was missing. In this case the core process update failed.
Could not add user role assignments to roles of integrated core processes which had restricted permissions.
Permissions were removed on core process update in the following scenario: A user is assigned to a role that was imported with a core process. The role grants permissions to the user. The user would not have these permissions without the role. When the user updated the core process, the permissions were removed from the updated role.
Repair database inconsistency concerning duplicate external references (compliance) due to which core process updates failed.
If an integrated core process was updated, associations without target elements were created in some cases when the option "Delete obsolete elements" was selected. This had the following consequences: Process elements with these inconsistent associations could not be viewed anymore and subsequent core process updates failed in some cases with ElementNotFoundExceptions.
Multiple core process elements could adopt the same element. The core process import could fail due to this error if custom attributes were configured. Now the elements will not be adopted if there are multiple core process elements with the same names.
If annotated core process elements were overlaid, the annotations were lost when cancelling the overlays.
Permissions were duplicated if an overlaid core process role had a permission with the current workspace as scope, the process was copied and the overlay was cancelled in the target workspace.
Compliance mapping of index pages and external reference mappings from a core process were not removed when the core process was removed.
No update link was diplayed on "Analyze core processes" page in the following case: The original core process was exported, then its workspace was deleted and a new work space with the same name but a different path was created where the core process was imported again.
Compliance mappings of index elements and external mappings were never protected from changes when integrated with a core process. In a special case this lead to the duplication of external mappings by core process updates.
When a core process contained a core process with a comment-only association and it was then integrated back into its original source core process, the comment-only association was duplicated. This could cause the failure of subsequent core process updates.
The process update preview always executed the process update even in case the user decided to abort the operation after previewing the results.
Ensure collected historical metric results are not deleted in case the metric collector is replaced by a core process update.
It was not possible to define clickable image map areas that have no link target (href=[[#]]).
If the user tried to link to another workspace in the editor link dialog, the initial link name was overwritten.
Even if a user was only allowed to view the valid process version, it was possible to navigate to a different process version via TWiki link.
It was possible to open the image upload dialog, even when the user didn't have the permission to add images.
The editor failed to render descriptions (StackOverflowError) with content looking like Java stacktraces.
Improve performance for textual reference parsing in image maps.
Rendering of process descriptions could take a long time for links within quotes and trailing whitespaces.
Color picker table and cell properties was not always closed with Internet Explorer.
Default textual references in the editor embed resource dialog did not contain the full element path for non-image resources.
The editor diff view showed an exception message when the language browser cookie could not be read.
Internal links with an inner textual reference were converted to unmanaged sections and not cleaned.
Cycles of textual references lead to a StackOverflowError when analyzing a process for description errors.
The advanced tab in the table cell dialog did not show the property values for id and class.
prevent concurrent import problems by locking the target process before reading the (potential huge) zip data
When exporting a process with a local shadow-real relationship to a .zip file and importing it to another workspace, the shadow element was referencing the real element in the original workspace. This replaces the fixes for #31842 and #31811 with a more general solution that works even for use cases without Stages Composer. However, Stages Composer 6.6.4 is needed when the process is imported into Stages Composer and exported back.
When an element was linked to another element in the same process, the link relationship was lost when replacing the working revision of the process with a .zip export of the same process.
Sorting of remote associations was lost on export and re-import of processes.
HTML Export of freemarker based views does not contain image-maps for visualisations.
Properties for attributes of compliance references (Percentage, URL, Commentary, Doc-Record Comment etc.) were not exported to Stages Composer
The value of selection and multiselection attributes with default options was not exported correctly to Stages Composer: For new process elements in which the "Advanced" section has not been opened while creating the element, an empty value was exported instead of the default value.
ZIP import failed when imported process contained associations from overlaid elements to other elements which were no core process elements.
Default process state was lost, after export/import roundtrip.
Large process ZIP exports (>500MB) could not be imported into Stages.
External IDs (needed for ARIS import mappings) were lost when a process was exported and reimported (for example when a process was modified in Stages Composer and then exported back to Stages Web).
Comment-only associations were not shown for editing when using upper case letters in target subtypes.
Fixes the PDF Diff print.
PDF print did not print strike through text in case the text had a background color. This is fixed by an additional CSS style in printBasePDF.css.
When a user locked a process during an ongoing resource synchronization, resources in the CM system were synchronized regardless of process state. Now, if a user locks a process during a background resource synchronization, new or existing CM resources will not be synchronized after the lock is set.
An exception occurred when viewing a description resource that was embedding itself directly or indirectly. Now, an error message is displayed when the user attempts to save a resource with circular embedding.
Resource overview could not be generated with resource names containing double quote characters.
Exceptions that occured during rendering of visualizations were logged without stacktrace, which prevented root cause analysis.
Search term of global search in input field was lost after page reload.
New items in lists (e.g. new users) were not highlighted with lower screen resolutions (e.g. tablet, smartphone).
Virtual keyboard in mobile devices was kept open after logging in.
Multiple members remove does not exit the delete mode.
Active users can now be displayed in user management.
Newly added permissions are highlighted.
Added an "Open" item in the workspace context menu in workspace management.
New users can immediately be found and added to permission groups. When users are deleted they cannot be found anymore at once.
For user groups, the assigned users and permissions can be edited now.
Users can now be edited in the management section.
New user groups can be created.
Permissions for a user group can be displayed now
New users can be created in the management section.
Display list of user groups in Management > User Groups and Permissions.
Introduce User-Permission-Groups. Migrate user role assignments to user permission group assignments.
Responsive table of users.
Users can now be deleted via new ui.
The existing users are now listed in the management section.
Reworked workspace administration (Display, add and delete workspaces).
Support CVSPLM as configuration management system
Files can be uploaded for artifacts and guidance elements now (Stages Database only)
Files are displayed in a responsive table now
New license type 'Authenticated Process Reader' is available. This new type corresponds to the type 'Anonymous' with the difference user must logon.
Enabling gzip compression in tomcat for various mime types (e.g. html, css, json, svg).
Different error pages are displayed for "object not found" (HTTP 404), "internal server error" (HTTP 500) and "conflict" (HTTP 409)
The currently selected workspace is listed in "My Workspaces" so it can be easily added to the "My Workspaces" list.
Server-side validation errors are now displayed like client-side validation errors when editing users, user groups and permissions. The user is no longer redirected to an error page.
In case of errors an error report (runtime information) can be sent to the Stages support (the mail address configured as "support.email.address").
Combined icons in an icon font.
Refactoring the Stages login modules (SPNEGO, Basic Authentication, SSL) to use container authentication.
Invalidate browser cache after version upgrades or metamodel updates.
Collapse single entry menus with icon to a simple clickable icon.
Scroll position is kept on tab change.
export to enactment systems (JIRA / RTC) has been reworked
Workflows can now be created easily via add button from the visualization card.
When deleting an association or user permission group a confirmation dialog will be displayed.
When deleting a process element, the element name is displayed in the confirm dialog.
Association comments can be edited directly in the association list without opening the "Browse" dialog (only associations with target element, no comment-only associations yet)
The perspective can now be switched using the element "Edit" menu, even at small resolutions when the perspective bar is not available
[Internal] The maximum process element comment length is now hard-coded to 1000 characters and validated on the client similar to other input fields
Implement rearrange of process elements.
Security Filtering for Delete Associations Command and Delete Process Elements Command.
Assure correct sorting of process element associations. Associations may be sorted alphabetically, manually or by target elements. Comment-only associations will always be placed after normal associations.
Multiple associations can now be deleted via new ui.
Dialog for editing process properties.
Implement user specific security filtering of available operations.
Responsive full-screen dialog for editing process elements.
Empty processes can now be created via the new ui process start page.
Provide workspace selection in association target browser.
Enable creation and modification of association comments in the associations browser.
Provide browser for associating multiple associations via target element browsing.
Process elements can now be moved to a new parent element in the same process or in another process. When a parent element is moved, all its children will be moved together with it.
Process elements can now be copied across workspaces in new ui.
Single element can now be deleted from navigation drawer. A confirm dialog is shown.
Applied new design for the process element actions "copy" and "delete".
Adapt styling of activity stream according to the style guide.
Comment-only associations are now displayed together with normal associations
Process elements can now be deleted from process element page. A confirm box is shown.
Input field in association list is now scrolled into view when adding new elements. Added a new context menu to association groups in order to add new elements.
Associations can now be deleted directly from the association list.
Re-styling of editor plugin dialogs
Editing of image maps in editor image plugin.
Temporarily removing the HTML template, Link and Resource plug-in from the Rich text editor.
Images can now be uplaoded via browse button in new upload ui.
New editor image plugin
Adapt and style element descriptions according to style guide
Added .zip import/export of processes in Management > Workspaces
An automatic index can now be displayed for the process start page (widget:index)
Allow guidance refine associations for all guidance subtypes except folder.
Metamodels now support layout templates, widget libraries and media queries.
Display compliance references for process elements.
Implement support for svg icon recoloring.
Visualizations can now be fit to page or shown 1:1.
Extending the search-backend to merge equal search results. The merged results are displayed as alternative of one search result.
Search results can now be filtered by recommended workspaces. Recommended workspaces contain the current workspace, workspace favorites ("My workspaces") and workspaces that have process interfaces with the current workspace.
Moving the declaration of attribute types from PkitConfig.xml to PkitProcess.xml. For each metamodel a list of attribute types can be declared and later used in the model part of process, process element and artifact instance. Attribute types declared as searchable (currently supported types are: STRING, SELECTION, INTEGER, TEXT) will be considered when searching for elements.
Use all workspaces as default search scope for the anonymous user.
Search results from the favorite workspaces have higher score than results from other workspaces, but a lower score than results from the current workspace (current > favorites > other).
Do not display a menu if it has zero enabled, non-separator items. Do not display a separator if it is the first or last displayed menu item. Merge multiple subsequent separators into one in the displayed menu.
In paged views newly added items are now displayed on the top of the first page.
A new profile image can be selected from a section of an uploaded image file.
Users can upload a profile picture
Edit/Delete menu entries for user permission groups were visible without the required permissions.
Removed the hover effect from the placeholder if no further workspaces exist.
Encode HTML special characters in workspace names.
The "Delete" menu item was displayed for the root workspace in Management > Workspaces
Concurrently adding associations now results in the 'conflict' error page instead of the internal error page.
An exception occured when importing processes by dragging and dropping a file, sporadically in Internet Explorer/Edge.
When importing a process, a dropped .zip file was rejected in some browsers because the file type was not detected correctly.
LDAP synchronization failed, when matchUsersMode was set to 'email' and the email address of a previously synchronized user on the directory server was changed to the email address of another synchronized user.
Users cannot be assigned to roles anymore when the config property 'user.view.limit' for the maximum number of users in lists is set to 5000 or more (default value is 1000) and this limit is reached.
Checking if the user has the necessary permissions to perform process and management operations in the navigation drawer.
Ldap synchronization could not assign floating licenses to newly imported users when the license limit for concurrent user sessions was already reached.
LDAP authentication by rebind was broken.
Default user can be deleted because this user account was not recognized as system user.
Open Stages external url from MS-Excel (2013 or later) uses Stages license which can not be returned.
LDAP synchronization mode cannot be set.
The session timeout could be defined with very small value. Now the minimal session timeout value is set to 30 minutes.
Login to Stages was not possible in case the browser did not accept/provide any cookies.
Exception occured in handling of cm profiles with checkouts but without configuration in PKitConfig.xml.
Prevent a single SSO user from using up all floating licenses by not logging out of Stages but just closing its browser.
CMS File Browser and Structure Prefetch could not be disabled per CMS Type.
A NullPointerException occurred when cms browser button without cms profile was clicked.
Detection of pending revisions was broken.
CMS Structure Prefetch failed for Integrity projects with unreadable subprojects. As a consequence the CMS browser showed no files at all for the corresponding Integrity projects.
CMS Structure Prefetch failed to determine the item tree for the CMS browser when an Integrity subproject was located in folder whose name ended with ".pj".
Duplicate reference mapping shell script causes NullPointerException when match mode is set.
Compliance mappings that were created on protected core process elements were deleted by the core process update when the working revision of the process had been replaced between the creation of the compliance mapping and the core process update.
User database caches weren't properly invalidated when deleting a user.
EnsureDatabaseIntegrity script was not able to handle processes that contained a duplicate index element for any type.
Compliance mappings could not be filtered by process id (containsComplianceElement@SYSTEM,process=ID).
Report script uses property from wrong metamodel.
It was not possible to retrieve element version history entries. Usage: var versionHistoryEntries = element.getEntities("containsHistory@SYSTEM"); (Properties: Id, VersionId, Name, Description, DisplayDescription, Date, CreatedBy, State)
It was not possible to retrieve other versions of a process element from the other baselines. Usage:
var elementInOtherBaselines = element.getEntities("baselinedElements@SYSTEM");
The JSON response to failed login attempts indicated if the password was wrong, or if the user was not existing
Anonymous users were unable to navigate between workspaces.
Input character counter was not reset to zero when another input field was added.
When the stages server is not available an error page is displayed indicating that no further operations can be executed.
The "Browse" button in the file upload widget did not work with IE 11.
Right toolbar reserved space even if not visible.
Long menu items were not shortened.
Incomplete Support-Infos where generated.
Prevent login to Stages and show error page in case Stages could not be started successfully.
Implemented a more reliable way to display localized placeholder texts.
ISO control characters were not filtered in the custom attribute values.
Attribute 'none' has no effect on element views for change management traces. Attribute 'attributeChange' can optionally used as follows to enable 'New issue' link: <attributeChange scope='process' newIssueLink='true'/>.
Action icons in association lists were not aligned and scaled correctly.
Fixed an error that occured in rare circumstances when clicking the button for inline editing of descriptions.
Multi-language correspondence associations were not exported in Process.xml. This made it impossible to reintegrate multiple language versions into one process in Stages Composer. This functionality is now available in Stages Composer 6.6+
When association were sorted by target element order, the workspace names were always compared, even between local and remote associations. The effect of this was that remote associations could appear before or after local associations depending on the name of the current workspace. Now, remote associations always appear after local associations when the associations are sorted by target element order.
Opening an element view which was not configured in the metamodel resulted in an internal JavaScript error. Now "Element not found" error is displayed.
Workspaces with unreadable processes were not accessible.
Ensure the process visualization is updated after modification of an association comment.
An "Edit" icon was displayed in the "Description" widget even when the user had no editing permission.
Use only valid URI characters in the association path syntax to prevent encoding issues.
Workspace selection did not correctly filter the available workspaces according to the users permissions.
Do not check the subtype against the set of allowed subtypes when saving a process element, because this makes it impossible to edit many elements in the "Software Engineering" sample process after the latest unified_configuration changes
All subtypes were assignable in association browser.
The menu items for creating children in the element context menu were not immediately updated after changing the subtype of the element.
The illegal character '|' in element names is now suppressed when adding new process elements.
If a process element has no valid subtype, the default subtype is pre-selected when editing the element.
On the page for editing process elements, the names of subtypes are now translated more reliably, especially after page refresh.
After deleting a process element, in some situations child elements or the parent element was selected, which lead to inconsistent behaviour.
No process was displayed when revisiting a workspace in which a new process had been created previously
Add new child element from element menu was broken
The margin in edit element card layout was too big.
An exception occurred when browsing target elements for associations from activities to guidance elements in the "unified_configuration" metamodel.
Creation of external link in resources was possible in FreeMarker based metamodel.
No view perspective was selected after user login.
Releasing a new valid version with the setting "Copy project data from previous valid version" could create LOST & FOUND elements as containers for the copied project data. This behaviour can be unwanted because the LOST & FOUND elements cannot be deleted when a valid version is not the working revision. Now the creation of LOST & Found elements can be disabled for this scenario by setting the configuration property "copy.project.data.releaseValidVersion.createLostAndFound" to "false".
When a new valid process version is released, project data can be copied from the previous valid version. The target process elements for this project data are retrieved by internal identities, element paths or - as last fallback - element names. Matching by element paths or names can be problematic for some use cases. Now it is possible to enable matching by internal identities only by setting the configuration property "copy.project.data.matchElementByIdentityOnly" to "true".
Core process import/update report does not contain permission and user assignment updates.
Copy & paste was not working in inline edit mode
The native browser spell checker is no longer disabled in the rich text editor. Use Ctrl + right click to access the context menu with the spell checking suggestions. Browser spell checking is available in Google Chrome, Mozilla Firefox (english version) and Microsoft Internet Explorer (Windows 8 and newer)
List position is not displayed correctly, when image text flow is set to 'right'.
Newly created process descriptions were not displayed after a ZIP import.
Web export generates HTML tags in diagram shapes for comment-only associations.
Replacing the working revision failed with an exception when artifacts with artifact instances had a "\" character at the end of the name, the artifacts had to be looked up by name, and "Copy project data from previous working revision" was enabled.
Database inconsistencies (e.g. reference model mapped to itself) occurred when a reference model was copied and both - the original model and the copy - were deleted and reimported or imported on another Stages server.
Fix handling of association groups containing multiple target element types or synthetic associations.
Visualization widget did not reflect user parameters added after initial rollout.
Additional node labels were positioned in the wrong table cell in case many labels are added to the same cell. This is fixed now.
Prevent diagram reload on tab switch. Allow the browser to cache diagrams caching. Provide a mechanism for the web ui to enforce a reload of the diagram.
The image map was not correctly scaled after changing a visualization parameter.
Fix a performance bottleneck when using packageImport statement in visualization scripts.
Workspaces name had too much relevance for the order of search results.
Performing an exact search for a substring resulted in elements containing that substring.
The displayed total number of search results did not match the actual number of results when there was only 1 result page.
Anonymous users had no "Current workspaces" filter option in the "Workspaces" search results filter.
Adjusting the search filter to ignore process filtering on workspaces without process.
Many search requests cause high server load.
Ensuring search suggestion prefer process elements over process element folders.
The user icon of the Anonymous user appeared clickable in the navigation drawer.
Process elements that were never manually or alphabetically sorted by a user were displayed in different orders. In the process navigation on the left they were ordered alphabetically. When they were shown as target elements of associations in most cases they were ordered by creation time. Now the sort order is always alphabetical if elements are not manually sorted.
When an invalid username or password was entered, the password input field is now focused
Headings of dialogs no longer wrap but are shortened now. Also, the font size on small devices has been decreased.
Support information contains tomcat.log and rc.conf (linux only).
File path proposal can be disabled via config property 'process.file.cmsFilePath.proposal.enabled'.
Support subversion servers 1.9 and read-only system accounts
Added Property "CreationDate" to ProcessClass.
Added compliance model to facade.
Added methods (newRequestFilter() and getRequests(projectId, filter)) to pkit facade in order to get filtered requests.
Guided Tour provides external direct links.
Upgrade Tomcat to version 8.0.30.
Support Java8
adjust maximal file upload size to 2 GB (maximal supported filesize)
Enable resolving users by their username in metric scripts through pkit.getUserByUsername() call
Integration of new BIRT version 4.4 for process reporting.
Upgrade CKEditor to version 4.5.7 to provide for Microsoft Edge support
Resources provides multiple cms profiles.
Enhance performance logging of diagram rendering
Added parent and children attribute.
Attributes of dependent requests can be set when an issue is saved.
Issue filter can now be project independent (<request-config ... globalFilter="true">). Process element state can now be set via an issue tracker event (<onchange condition="isInNewState('completed')"><setElementState state="released"/></onchange>). Change management traces are now displayed as real links when using the CHANGE_REQUEST attribute type. Core process identity is now available via Facade v1 (coreProcessIdentity).
remove old sandbox based subversion interface
Provide fallback in case file system exists check does not work for clearcase documents.
Metric reports could not be rendered in case an Apache HTTP server was used as front end server for Stages.
Always support SVG rendering for exporting metric reports to PDF. Fix content encoding for SVG rendering in the HTML report. SVG rendering for HTML can be enabled via configuration property "metrics.svg.enabled".
The root cause of metric report rendering errors was not always logged.
PDF export for reports supports rendering of SVG images.
Metric reports containing control characters couldn't be rendered.
In case of metric report script errors only a generic internal error was displayed. Now the detailed error message is shown. There is also a new BirtDesigner (3.0.1)
Reports did not work when they contained dataset columns of type "Date" and the corresponding dates were read from a database as java.sql.Date values.
Rendering the tailoring justification in a metric report failed for elements tailored via tailoring assistant.
Report export to MS-Excel and MS-PowerPoint is invalid on report show page.
Adding a collector interval with invalid date string causes an error.
It was possible to reset the tailoring state of elements that were tailored using the tailoring assistant. Now, only manually tailored elements can be reseted.
Allow tailoring reports also for non-released process versions.
Incorrect labels were displayed when viewing tailoring answers and a FreeMarker-based metamodel was used.
Linked tailoring resources were not editable.
Reexecution and reset of the tailoring assistant did not reset all unselected answers in certain cases.
The tailoring justification was only visible to users with permissions to execute tailoring, but it is specified that process read permissions are sufficient.
Trace between request and process element was not set when sending email notfications.
Fixes an exception on creation of a new change request for the process description.
Disable sequence cache for request ids to lower probability of gaps which consfuse the end user.
Sending notification emails failed in case one of the notified users had no read permissions on that request.
Fixes a possible SecurityException when using a global request filter.
concurrent request modifications resulted in DB inconsistencies. Now an error message is shown and the concurrent modification is prevented.
Fixed filtering for issues without assignee.
Improved performance of displaying request tracker overview page and individual issues, that contain many history entries.
User attribute filter can not find issues with modified fullname of related user.
Excel-Import warning dialog can not be closed.
It was possible to accidentally create change management traces if the user did not complete the change management trace creation and edited/saved another change request.
User filter types with text input had differnt filter comperators.
Long user list is truncated. User request types can now be searched via like-search, when attribute 'filterAsTextInput' is enabled.
A Security Exception occurred under certain circumstances when notifying users.
Fixed performance issue in loading issue tracker overview page.
Unreadable infocenter entries falsify search results.
translations for various search hit types where missing.
Prevent Subversion-Server from crashing when handling files in the root-folder of the repository
Remote references in image maps cause dead links in HTML Export.
It was not possible to create subdepartments.
Allow filtering for 'no versions' and 'no files' no matter whether a file has a lifecycle or not.
For the unified_configuration, we can define better constraint checks, which also check the quality of the process:
- Understandability: No process or group should have more than 8 activities
- Efficiency: No process or group should have more than 4 involved responsible roles
- Robustness: No process or group should have more than 5 responsibility handovers
The Efficiency and Robustness checks only apply to non-automated processes, i.e. when one of the activities has an execution work item type set in the enactmentWorkItemType custom attribute, the whole process is excluded from the constraint checks.
The actual limits and metamodel idents are hardcoded into the consistency checks, because there is currently no way to specify parameters in the config file and the consistency checks should have no dependencies to other config mechanisms (e.g. config properties).
To enable, use the "unified_configuration" metamodel from Method Park and add the following lines at the start of the metamodel configuration in PKitProcess.xml:
<global-constraints>
<global-constraint className="de.methodpark.pkit.process.constraintcheck.check.unicorn.UnicornTooManyActivitiesProcessQualityAnalyzer" />
<global-constraint className="de.methodpark.pkit.process.constraintcheck.check.unicorn.UnicornTooManyRolesProcessQualityAnalyzer" />
<global-constraint className="de.methodpark.pkit.process.constraintcheck.check.unicorn.UnicornTooManyHandoversProcessQualityAnalyzer" />
</global-constraints>
Selecting a file from a CM system is now easier as you can browse the CM structure from within Stages. This is available for documents and resources as long as one of the following CM systems are used: Sharepoint, Integrity 2009 and newer, Subversion (New), ClearCase.
New files can now be created based on templates.
Rules for synchronization of resources can be managed per CMS profile.
The Linux init script will now take system configurations in /etc/default or /etc/sysconfig into account and will no longer expect Latin-1 file encodings.
Improved performance of freemarker based views.
Resources can now be synchronized from the CM system. This is supported for Sharepoint, Integrity 2009 and newer, Subversion (New) and ClearCase. It needs to be activated by setting the property "process.resource.sync.enabled".
Automatic synchronization of resources with a folder in the CMS. Depends on a cache for the CMS structure which is independently fetched.
Resource overview in excel was extended such that it provides direct links back to Stages Web and full CM path for CM managed resources.
Prevent accidental modification of the set of assigned dependent elements of a tailoring answer.
The tailoring justification is now required for single element tailoring.
Disable the deprecated description add on tailoring by default. To reenable the feature set property "process.tailoring.enable.addon.tailoring" to "true".
Rename user setting "show invisible elements" to "show tailoring details". Show all tailoring details like justifications and date and user of tailoring only if this setting is activated.
Allow the tailoring assistant to start with an empty process and add elements as needed instead of removing obsolete ones.
Provide a detailed justification for elements tailored via the tailoring assistant.
For elements that are tailored implicitly by their parent or child element an appropriate note is displayed.
Log and show date and executing user of tailoring changes.
Improved "edit properties" dialog for file-based and url-based resources. Now the content location (Stages database, external CM system or an url) can be selected and only the relevant properties for the chosen type will be displayed.
Improve user feedback functionality by sending the feedback via the local mail application to ensure a valid email address is available for call backs.
Whitespace characters were not escaped correctly. In this case image maps did not work.
Ensure the Stages version information is not accessible without logging in.
Insufficient security filtering at Overview Page, resulted in SecurityException
CMS physical path names were not validated against the configured validation pattern
CMS Credentials are no longer shared among anon users
Racecondition during prefetch with multiple workers could lead to CMS_ERRORS in subversion
The page for resource synchronization rules is now hidden if the config property 'process.resource.sync.enabled' is set to 'false'.
CMS-managed resources could not be directly checked in after being checked out without reloading the page.
It was possible that a cache entry for a not accessible Integrity document was not persistable due to a not serializable exception.
CMS cache keys were not unique in some cases. Therefore the same metainformation (version number, date, ...) was shown for files with identical names/paths from different SharePoint document libraries of the same sites.
support new claim based user identification
checked out files, that where moved/renamed could led to errors during prefetch
Associations retrieved via facade v1 were not correctly sorted.
Resolving associated elements via the Stages facade resulted in SecurityExceptions, due to incorrect security filtering.
Overlay state (Property: Overlay), Core Process Element state (Property: CoreProcessElement) and Association to Core ProcessElement (Association: containsCoreProcessElement@System) were not available via stages facade.
Improve styling of CMS file browser UI
Physical CMS path in "new file" dialog was not updated correctly in some cases.
Ensure folders are always displayed at the top of the list in CMS browser.
CMS browser did not consider the users local date format.
replace invalid characters in suggested cms path and file name.
The comment column of the file history collapsed in case the browser window was small.
Add dist file for PKitCaching-customer.xml as template for modifications
Import of process exports with older format versions could lead to remote associations to process versions other than the working revision.
Project Scope attributes were editable in all process versions. Now they are only editable in the working revision and valid process version.
Composer webservices must not book any license
Moving process elements could fail when the the user had no write permission to the news application and tailoring visibilities needed to be recalculated (affected by the relocation of the elements).
A user was not able to create another user in case the executing user had no user create permission on its default workspace.
Process elements with names starting with umlauts were not listed in the process element index.
Clicking on a link to a guided tour stop which was removed by tailoring resulted in an error. Now tailored tour stops are displayed in the guided tour with their names struck through when the corresponding option is selected in the user settings.
Fixes a possible NPE on caching an error during CMS prefetching, in case the CMS Exception has no message.
Creating a process version of a process containing an association to an overlayed element of another process, resulted in loosing this association in case the overlay was canceled.
In some cases integrating multiple associated core processes into one process lead to both - remote and local associations.
If two core processes with mutual remote associations were integrated into the same process, the integrated associations of the first integrated core process were not protected from changes anymore after the integration of the second core process.
Core process integration/update failed if the source core process had a reference element mapping with one of its index page elements.
Modifications of process element index pages by core process updates were not documented in the update report.
Core process update deleted mandatory associations between overlayed elements.
Image map area with a textual reference without display name following one with display name could not be rendered.
Analyze description errors produced a StackOverflowError on a reference loop within image maps
Links with an inner image resource were not converted to unmanaged sections when they contained additional HTML tags
Image map validation was not strict enough in some cases and gave no information about which areas are affected.
Legacy image maps from old data could not be migrated to Stages 6.x
Analyze description errors gave no reference to the embedded resource that contains broken links.
Legacy image map areas were ignored when they were mixed with the new strict syntax.
Table cell formattings were not preserved when pasted into the editor.
Native links to anchors (not defined as textual references) from Stages version 5.x could have been broken after migration to version 6.x. Anchor links inside of unmanaged sections remain unchanged.
Duplicate anchors with the same name in multilingual descriptions are now reachable by clicking the link.
It was not possible to copy and paste a link to an anchor using FireFox or Chrome.
Process exports from some older Stages versions (e.g. Stages 5.0) could not be imported into current Stages versions due to DTD error.
Predefined comments of CM profiles were missing in the process exports.
Imports of processes containing tailoring answers with dependent elements or guided tour stops with corresponding elements failed.
Process imports and core process updates led to NullPointerExceptions in combination with process locking when the imported process contained remote associations to overlaid elements.
On some older jvm versions it was not possible to open the pdf template selection dialog.
Use system credentials for accessing CM managed resources as they are owned by the process and therefore must be accessible for all users that have access to the process.
CMS managed resources where wrongly reported as resources without content.
The tailoring wizard justification listed the influencing tailoring answers in the wrong order.
Positive tailoring caused a SecurityException in case one of the tailorable process elements was not readable.
Ensure tailoring details are only shown in case user setting "show tailoring details" is activated an tailoring permissions are available.
Copying a process with a tailored element that was overlayed caused an exception.
HTML structure elements were accepted as tailoring justification. Now the tailoring justification needs to contain at least one text character.
Textual references in tailoring justifications were not resolved.
It was not possible to execute the tailoring assistant after leaving the modify tailoring dialog without using cancel.
The date format in the tailoring report did not consider the user locale.
Leaving the assign dependent elements dialog via cancel does now correctly reset the changes.
Separate system and user config for web.xml, log4j.xml and PKitCaching.xml
Include license log in Supportinfos.
Resource overiew now shows all resources which are asscoiated to an element in the currently viewed process version. The document filter has been replaced by a resource type filter.
The anonymous user now can access the resource overview in the Overview application.
Admin can choose for each subversion repository whether he would like to use indivial user authentication or not.
Associations are now displayed in the configured order
Added the possibility to get informations about the health of Stages via the RESTful interface.
Provide facade properties to access Enactment parameter
Provide facade properties to access the TypeName and SubtypeName in sigular and plural
Return the associations and child elements in the same order as they are shown in the gui
Html descriptions of process elements and processes can be queried via the facade.
Index elements can now be easily queried via the facade, e.g. process.getEntities("containsActivityIndex@SYSTEM")[0].
Allow customer so specify login and logout redirects
Arbitrary languages for the Stages GUI can now be specified in the "supported.languages" property [default: "en,de"] and providing the respective PKit_*.properties files or PKit_*.utf8 files in case UTF-8 characters are used. A call to updateConfig.bat|sh will convert the utf8 files to properties files in the desired format. Known limitation: The rich text editor is not fully translatable.
with the config property "global.secureMode.enabled" a X-FRAME-OPTIONS = SAMEORIGIN header will be added to every response, preventing the application to be embedded into IFrames.
Tomcat has been upgraded to version 7.0.54
Service section can now be disabled via configuration property service.portlet.enabled.
Provide default enactment script resource for export to Rational Team Concert.
Enactment script errors contain a line number for easier debugging.
The new enactment script method 'setTargetProjectArea' enables the ability to change Project Areas.
Comments of enacted successor associations can be exported and used in Rational Team Concert.
Ability to set default enactment script at resource to Rational Team Concert export.
Improves performance of the metric collector tab. Collector scripts are now validated only after editing and when the collector is triggered.
Added a new property named "Lob" to collector results which can be used to store serialized data.
Changing a process element state now updates the last modification time and user of the element.
The default children subtype set by the parent element is now also proposed as default for the elements children.
Process element state assistant can now set the states of an element and its subelements.
Export editor directive names for Stages Composer
Log entry when user has been assigned to or unassigned from a role.
Added horizontal rule plugin which provides a command to insert Horizontal Rule (<hr> element) in description. In order to use this feature the value 'HorizontalRule' must be appended to the config property global.editor.extraPlugins.
Added remove format which makes it possible to remove all text styling (bold, font color, etc) applied to the selected part of the description.
Editor has been upgraded to version 4.4.3 and is now minified for better performance.
Added property "Variables" to ProjectElement which returns a Map. Added getProjectByPath(String path) to Pkit in order to query projects by path.
The values of custom attributes of type "selection" with "alphabetical=true" are now displayed in alphabetical order in Stages Composer, too
Resources may be downloaded without authentication by specifying "unauthenticated.resource.download.user" property, the given user will be used for the download
Links to anchors of the same description will now work even if an identical anchor name is used in multiple descriptions of the PDF printout.
List PDF print templates on element index pages.
Description selectors can be freely defined in the meta-modell and can be edited in the editor
Added PDF printing to the process start page. The Freemarker/Facade template functionality introduced by 27579 allows for custom printouts of whole processes.
Freemarker templates can now be used for more flexible PDF printing. The PDF print selection page was changed to a list of direct download links, one for each option. The old functionality is included in this list. For more information please refer to the updated PDF Print Guide.
It is now possible to define multi label node shapes within the visualization. Tooltip text can now be defined separately from node or label text. See unified Configuration for an example.
Save and restore PKitMetrics.xml and PkitMetrics.xml during update
The root cause of JSP errors was not logged, which prevented error analysis.
Permission error was thrown when changing the user settings and deleting users.
Stages Admin may choose to show server information to anon users by enabling the config property "info.allow.anonAccess"
With log level DEBUG enabled also user passwords were logged.
It was not possible to start command line tools like EnsureDatabaseIntegrity in case the new Subversion interface was activated in PKitConfig.xml.
MKS (old interface) did not book individual user licenses.
If an existing workspace was migrated from the old to the new Integrity interface or from the old to the new Subversion interface, previously locked files could not be checked in or unlocked.
A NullPointerExcpetion was thrown when viewing a ClearCase ConfigSpec.
Development path revisions were shown in the version histories of files when no development path was specified in the CMS profile.
It was not possible to download a file on the version history page when pending revisions existed. On other pages the latest version could not be downloaded when the latest version was a pending revision. The predecessor version was downloaded instead.
New files could not be created in existing subprojects if the corresponding CMS profiles referenced Integrity projects whose identifiers did not end with "project.pj".
Invalid Subversion host configuration could lead to missleading errors
It was not possible to specify in the CMS host properties whether major or minor versions shall be created on checkin for files without lifecycle (e.g. resources). By default major versions are created. This can now be changed by setting '<cms-property name="major.versions" value="false"/>' in the corresponding cms-host section in PKitConfig.xml. The cms-host-specific setting can still be overwritten in document lifecycle definitions per state.
Reverting a file was incorrectly using the system account. This was caused by a mismatch of the locking username reported by Sharepoint. The username is now correctly parsed and fully qualified default domains are also handled.
When a reference model was copied, its custom ratings and external references were also copied whereas its reference element mappings were not copied. Now the custom ratings and external references are also not copied.
Process elements with shortnames could not be adopted.
Ensure all passwords are stored in a secure way
Encrypt cms passwords that where initially stored in plain text
Database upgrade step selected too many entries.
EnsureDatababaseIntegrity script failed when the following database inconsistency occured: An overlayed element had no process id in the database.
EnsureDatababaseIntegrity script failed when the following database inconsistency occured: Attributes existed which were not referenced.
Preserve annotation index elements that were deleted by upgrade step 2040.
AssociationElement#isRemote() now returns true in case of remote associations.
Non hierarchical element configuration in meta model prevented child element query in index elements
Facaden API returns a Description object for DISPLAY_TAILORING_JUSTIFICATION, DISPLAY_DESCRIPTION and DISPLAY_NAVIGATION_DESCRIPTION
With Internet Explorer 11 the file context menu entries for WebDAV editing were missing.
Do not display a lifecycle state for hyperlinks (e.g. when associated files are listed for a phase/milestone).
Adapt ThreadSafeDateParser for JAVA 8 compatibility.
Non ContextFilter failed for non http requests
Browser warning was shown in IE8 with disabled ActiveX.
Tree in the Wiki application and in the process element notification page did not work with IE9.
Shortened button label.
RPM (linux) installation overrides config settings in rc script
Workflow configuration was generated incorrectly.
Rational Team Concert export or process data analysis cannot be executed on Linux operating systems.
Metrics with short names could not be resolved on report display
Buttons on the page where reports are shown were not working with IE8.
Metric results were not stored within the same transaction.
The script variable currentUser did not contain the logged in user in case the report was not viewed in Stages, but exported e.g. to Word or PDF.
Prefer PNG over JPG if no SVG output can be produced.
Reducing permissions due to the license type, did not work in case of write only deny permissions. Write only permissions are now ignored for users that do not have write privileges due to their assigned license type.
It was not possible to change the custom attributes of the process itself.
Custom attibutes on files lost their values when a valid process version or working revision was replaced and option "Copy project data from previous [valid version/working revision]" was selected. Note: As a consequence of this bugfix, custom attributes on files are now always regarded as project scope attributes.
After copying a process with artifacts using a cm profile the cm profile of the source process was assigned to the artifact in the target process. Now the copied cm profile is used. A Database cleanup step on startup fixes incorrectly assigned profiles.
diagramPopup can no longer be used for code injection
User language settings was not honored during PDF print via REST service
Validate user experience level
Don't delete Attributes when multiple Processes Elements are edited in a row.
Tailored element headlines no have the usual texthight
Changing the tabs in the assignment dialog won't loose comment modifications anymore.
Security labels could not be selected anymore for permissions.
Fixes a NullPointerException that occured when an element with a remote association to an overlayed element is copied.
Style class on subelement heading was not set reliable.
Copying a process element with annotations did only copy the association between the element and annotation. Now annotations are no longer copied together with process elements.
Fixed performance issue in index element tree.
Custom attributes of type 'boolean' can not be disabled.
Accessing resources via image maps were not logged.
Anonymous could not view state report.
Some icons in navigation portlet are not visible, when workspace name is too long.
External process element links didn't work when links were build manually and no elementType parameter was specified.
EnsureDatabaseIntegrity didn't fix unidirectional tour correspond associations.
Multilanguage associations were not handled correctly during process versioning.
Update of experience level in user settings has no effect on the processes view filter.
The print-out of a process element of the working revision could include a wrong process version name. In case of printing a working revision element there should be no process version name at all.
Resource icons were interpreted as language icons for filenames of the corresponding syntax but no ISO language identifier.
Tables which contained inlined arbitrary descriptions with paragraphs were not correctly formatted when config property "global.editor.directInlining" was set to "true".
Process elements on the index page were not correctly sorted in some cases.
Coping processes, instantiation process models and creating process versions was extremely slow, when the source process (version) had many remote associations.
An exception occurred when assigning a new resource while editing an artifact.
The browser window title was escaped twice.
Saving a resource url with more than 1024 characters lead to an exception. Input field has now been limited to 4000 characters.
An association without type in the metamodel lead to a null-pointer exception after clicking save in the association assignment dialog.
Process element title was rendered in display and print mode for linked resources like arbitrary descriptions.
Process element index pages were always displayed empty when no local process elements of the corresponding type existed. This was incorrect when process interfaces existed and the display of remote interfaces on element index pages was activated (by configuration property "process.element.display.remoteElementsInIndex").
Reduced the font size on the version history detail page and correctly display unknown version creator.
It was not possible to view older metric versions from the elements history.
Creation of resources below "Lost+Found" caused problems (for example the operation "Replace working revision" failed when the old working revision contained file-based resources that were saved via WebDAV by the operation "Checkout and Edit").
Metric report parameters were not copied when creating a process version.
Some process versioning pages were not displayed correctly with IE8.
Role mail notifications got lost on process export/import.
Process element attributes were editable in process versions in case individual attribute change links were configured in the element view.
In case more than 1000 active users existed for a process, all were notified about new baselines even if it specified otherwise by the user.
Working revision replacement produces duplicates of role permissions with security label.
Copying processes, instantiating process models and copying single elements with remote associations could lead to changes of process versions in other workspaces because all remote associations to all process versions were copied. Now only those associations are copied which are pointing to working revisions.
Role notfications could be changed in process baselines that are not the valid baseline.
Fixes an exception during core process integration in case multiple comment associations of the same identity are to be integrated.
Descriptions of updated elements were not migrated.
The local sorting of overlayed core process elements was not updated when the option "Apply sorting from the core process" was chosen on core process update.
A core process update deleted the image map of updated image resources. This was caused by the fix done for Error 27289.
Copying or versioning a process or copying multiple associated elements in one step could result in protected (restricted) associations on integrated core process elements without the necessary internal master process identity. The consequence of this inconsistency was that affected associations were not removed by core process updates in scenarios when they should be removed.
Fixed typo in German localization.
Core process update creates unnecessary content for content-based linked/shadow resources.
The core process update report did not include updates of resource contents like uploaded files.
Integration of several released core processes that are mapped to the same reference model produced multiple equal default scopes.
Integrated core process element could not be opened (NullpointerException) under the following conditions: The integrated core process also contained a core process in which the element was overlayed. Additionally the core process integration was not done with usage of the "import/update functionality" but with usage of the "copy process functionality" instead.
Copying a core process containing an overlayed element with a comment only association produced an inconsistent result. The integration of such an inconsistent core process was aborted with a NullPointerException.
Empty div elements could lead to broken description rendering after conversion to unmanaged sections.
Language of a description was saved even when support for multiple description languages was not configured.
Broken image was inserted when manually entering an unresolveable textual reference in the embed resource plugin.
Email recipients email role link texts were not updated after a change in user/role assignments.
Textual references from Stages version 5.x could lead to an StackOverflowError on description rendering.
Images embedded as shadow resources from other workspaces could not be shown in HTML exports.
Guided Tours were not opened in a separate pop-up window when referenced from image maps
Clean up of unescaped project paths did not handle type names surrounded by whitespaces and the format string "null".
Automatic conversion of images nested inside of links into unmanaged sections could fail during database upgrade.
Font tags inside of display names of TWiki links lost the color or background color value upon conversion to safe mode
For some descriptions the rendering engine omitted the white space positioned after a formatting tag
Format styles in arbitrary descriptions could get lost on embedded rendering with the direct inlining option.
Role email references where converted to external mailto links.
Links with an inner image could get lost on migration from version 5.x.
Textual references from version 5.x could contain multiple formatting strings concatenated by the slash symbol that lead to unresolvable links.
Image Map area tags from version 5.x could contain invalid characters that lead to unresolvable links.
Local anchor links were not clickable in printed PDF documents.
Image map areas with unresovable link targets were not rendered at all producing unexpected behavior on area overlap.
In image maps alt and title attributes could not be overriden by specifying them in the <area> tag.
Anchor links within image maps pointing to a local anchor were inoperable.
Links to roles with a project path defintion were broken on migration to version 6.x.
Editor description clean-up removed non-empty span elements without inner text but other child elements.
Textual references without explicit display name were not shown as tooltips in image maps.
Empty script tags in process descriptions were breaking the rendering in the browser.
Links in process descriptions at the start of text line were removed after pressing enter.
Unlink button of the process description editor toolbar was missing.
Tables in process descriptions from Stages version 5.x with a HTML border attribute were not correctly displayed in version 6.x.
Textual references with empty display names created with Stages version 5.x could not be rendered.
Tool tips were not rendered for image maps with textual references that have a display name.
Special characters like umlauts in process decscriptions were converted to html entities.
Text alignments in process descriptions from version 5.x were not correctly migrated.
In PDF print the font color within table cells could not be set by CSS classes.
In process descriptions links were rendered in default text color when they should be in default link color.
In IE8 table cells could have an incorrect content alignment taken from outer DIV elements.
Invalid border attributes on table cells were not removed but shown as cell borders.
In process descriptions from version 5.x, the color of table cells containing DIV or P elements could not be applied to their contents.
Support for tables within list items in process descriptions.
After migrating from version 5.x, the inner cell borders of tables were not shown anymore.
Links were always shown in the default color, changing of the font color had no effect.
Correct escaping of formatters in textual references introduced by upgrade step of issue 27023.
Deprecated formatting strings in textual references from version 5.x were escaped in migration to version 6.2.x resulting in invalid links.
Rendering of invalid textual references to process index elements could produce a null pointer exception.
Navigation descriptions that contained formatting tags in the display text of textual references were not cleaned.
Old external links with javascript targets in the href attribute were always cleaned on editor open.
Guided tour stops could not be switched into unsafe edit mode.
In IE8 table border width and cell border width could not be saved.
Fix multi-cell editing of cell properties. Now only changed properties are propagated to the cells.
For multilingual process start pages language selection was not possible in "noportal" mode.
After ckeditor upgrade some tooltips and popup messages did not show up..
If the description of a process element was not editable due to the "mandatory core process element" setting, the decription html source code was displayed in the editor.
NoPrint directive was not considered in pdf print.
Project variables were not considered in image maps.
Empty list items were not removed when process descriptions were displayed.
Table borders in old descriptions were not displayed after upgrade to Stages 6.x. Now they are displayed before clean-up of the description, and a clean-up will migrate them to the new format. Limitation for display before clean-up: only the values 0 to 5 for the old border attribute are displayed correctly, greater values are displayed with a border width of one pixel.
Editor description template plugin was too large for smaller screens or display resolutions. Now it is smaller by default and resizable.
CM Profile assignments were lost, when the Working Revision was replaced by a ZIP import including the project data from the import.
The order of various elements in Process.pkitmetamodel could change between subsequent exports, which led to errors in Stages Composer ("There is already a metamodel registered with name xyz and it differs from the new one.")
"Also applies to subworkspaces" on role notifications was always false after a .zip export and import
Preset parameters for metric reports are now preserved in a Stages Web/Stages Composer roundtrip.
With short session timeouts the stages is working for you splash screen did not vanish. Now the import of process descriptions runs in background if the user has an email address and the notification system is enabled.
The "show in dashboard" attribute for metric reports was lost when a process was exported/imported.
HTML export was aborted on links to guided tour stops in an image map.
CMS passwords will now be saved encrypted for process exports.
A remote assoc to an element protected by a security label will not abort the zip import if the importer has not sufficient permissions.
Contents of linked resources were missing after ZIP import if the linked element was deleted after the ZIP export. Now contents are always exported so they can be reconstructed on import.
Fixes a NPE in case an association constraint in the metamodel has no associationTypes attribute which is declared to be optional.
Page margins in printouts are now controlled by a CSS rule for paged media ("@page" instead of "body") in printbasePDF.css. The old "body" margin of 4em is now set to zero. This avoids unintended borders on the first and last page. The new "@page" margin is 2cm for top and bottom and 0.5cm for left and right.
External links in PDF documents are now clickable.
PDF-Print did not take css configuration via printbasePDF.css and printoutPDF.css into account.
PDF print did not show the currently selected language of a multilingual description.
It was possible that concurrent user edits and process updates could lead to tangling system process locks.
In rare cases a transaction rollback could lead to an endless recursion.
Fixed confusing naming of result column in resource overview excel report. The column 'Checks' is now called 'Findings'.
If a fixed revision was defined for a cms-managed resource, the wrong revision was used for downloading (latest revision instead of fixed revision).
Fixed handling of CMS managed resources. It was not possible to checkin a new revision.
For the width and height of image resources, the input was not validated and any string could be entered.
Cm managed resources were not instantly synchronized after save.
Fixes the Tailoring-Report for elements added by the tailoring assistant. The report should only mark "modification tailored" elements as status M.
It was possible to trigger modification tailoring for tailoring resources which is not supported.
Migration of the tailoring status for process imports from zips generated by Stages 5.1 did not work in some cases where the tailoring assistant existed, but was never executed.
SVG Icons Drop Shadow is now grey and can be turn on/of with getDropShadow.
Visualization scripts can now define a critical path to correct problems with backloops in a flow.
Minus (-) and underscore (_) characters in association type idents broke visualization.
Implemented a compiled script cache due to performance issues
The corresponding element of a guided tour stop must now be in the Working Revision of the target workspace. If the Working Revision is not accessible, the workspace cannot be selected and a hint is shown if the user clicks on it.
Clicking an Actions menu item that contains a submenu loaded a broken link with Chrome as browser.
RTC enactment scripts could not be overlayed if they were assigned directly to a process element.
No database error message will be displayed when global.secureMode.enabled is set
"Overview" was used in the process navigation and for the overview application. The main page of the processes application has been renamed into start.
"Home" icon was not displayed for anonymous users.
Wrong element type names were shown in left navigation in web export.
Webexport with freemarker failed if process.element.display.remoteElementsInIndex was enabled.
Tailored Elementnames are shown according to tailoring setting
Removed functionless magnifying glass icon for visualization diagrams in web export.
Added new Serena Dimensions CM interface.
Improved example configuration for MySQL-based cache stores in PKitCaching.xml. Also provided an example for Oracle.
Refactoring of Revision Properties
PIID export now also contains the tailoring justification in the "Evidence comments" row.
Change state from a lifecycle state to itself is now possible.
Added new demo confiuration with new visualization scripts and metamodels.
Upgraded Tomcat to version 7.0.42.
Enactment script content is Base64-encoded for avoiding dropped whitespace characters when the script content is read in RTC.
Enactment script assign function.
Enactment association type "workflow" allows to perform workflows across multiple process element types.
Several new helper objects and methods for workflow element enactment scripts. Detailed list and the usage of helper objects can be found in "Process Management for IBM Rational Team Concert" Guide.
Workflow and associated elements contain all relevant process element attributes.
Workflow configurations contains all associated child elements from element with association enactment type "associated".
Enactment association type "connect" allows to perform workflows across multiple process element types.
Changing the state of a process element will be logged into the process model change log.
Added description template plugin to the editor.
Show input help on border width input field in table plugin dialogs.
Introduced separate menu entry for the editing of process navigation descriptions. Moreover changes in process navigation descriptions are now documented as process changes.
Implement unsafe editor mode.
Default table width is now set to 75%.
Added table plugin and table properties dialog.
Upgrade CKEditor to version 4.2.
It is now possible to retrieve the status of the tailoring assistant as project variable to use it as a query parameter for external URL e.g. of a template generator. If config property "process.tailoring.as.project.variable" is enabled project variable %TAILORING_STATUS_AS_URL_PARAMS% is available.
A secondary timeout for long-running visualizations now respects the config property "process.visualization.timeoutInSeconds".
NodeStylingShapePath Enhancements etc. Fixed Dropshadow for NodeStylingShapePath. Added Recoloring for OverlayIcons by a given oldColor, newColor e.g. var overlayIcon = new OverlayIcon(resourceLoader. getResource("test.png"), -0.5, -0.5,Color.black,Color.blue); Fixed addAssociation so that associations can be found. Added method getEntities to MockElements to avoid scripting errors. Returns a zero length array. Added default implementation for NodeStylingShapePath getNodeHeigth. It sets the heigth by using the path aspect ratio.
The global method script.include can now be used in the visualization scripts to include scripts based on the webapp/WEB-INF/conf/diagram/scripttemplates folder: e.g. script.include("test.vm");
Node Shapes now are able to place node labels in center-center position. Therefore LabelAutoSizePolicy.AUTOSIZE_NODE_WIDTH and LabelAutoSizePolicy.AUTOSIZE_NODE_HEIGHT set label-size to the minimum of either shape size or label-height and -width. NodeStylingShape now has default implementations for all methods except getText(...).
TableDiagramConcept now supports properties to control graph density.
Visualization Shapes now support overlay icons, color gradients and shadows.
Added table tools plugin and cell properties dialog.
A license could be lost with single sign on under certain circumstances.
EnsureDatabaseIntegrity failed for processes without a project.
Stages service shutdown took too long due to a component that was not shut down as expected.
The link for anonymous login can now be hidden from the login page. The config property "license.features.suppressList" set to "AnonAccess" will hide the link. If no anonymous user exists, the link is not shown at all. The link is also not shown in maintenance mode.
Anonymous license could be assigned to more than one user.
MySQL: Upgrade steps fetched too many descriptions for cleanup, due to wrong pattern escaping.
LDAP Entries including a "/" character could not be synchronized into Stages.
Fix inconsistent audit log format for autologin.
The config property "global.strictNotification.enabled" did not have the intended effect: The email address of a user was not overwritten by LDAP synchronization when the user has saved his notification settings once before.
The document status filter is now handling status names case-insensitive.
CMS credentials are no longer saved for the anonymous user. Existing credentials of anonymous users are purged from the database.
Old MKS interface could run into endless loop when the history returned by the SI RLOG command was incomplete but did not signal an error by its exit value (e.g. when the Integrity database connection was closed while the command was running).
Dimensions interface: Entering draft request ids for file operations caused Dimensions error. Now draft requests are not accepted anymore.
Repository- and Module-Path are now validated during subversion configuration profile creation
Don't leave server transaction behind on subversion 1.7 and 1.8
SharePoint connections were being reset by the SharePoint server due to an excessive idle timeout.
Fixed caching of PVCS sandbox document metadata.
CMS authentication form in "New file" dialog could not be left when the file had required custom attributes.
Command line client could not handle blocked reads due to non-released locks in the CMS.
Provide default value for cms prefetch initial start hour to prevent warnings in the log files. Prefetch will start after Stages startup.
Refresh file link was not displayed in case of CMS errors.
Files which were unlocked in the CMS would still be displayed as locked in Stages.
Old MKS interface: Hostname and port from PKitConfig.xml were ignored.
Fixed direct server download for new subversion interface. Note: From now on direct download is disabled by default for all CMS. To enable it set config property cms.direct.download.enabled to true.
Added the host-specific config property "date.language" to avoid errors when parsing the server date. Default is "en".
PIID Report included tailored away elements. Now those elements are omitted or rendered strike-through based on the users profile setting for tailored away elements.
When generating an Evidence Collection (PIID) Excel sheet, text cells were not correctly formatted as text.
Timestamp columns in MySql tables were automatically updated to the current timestamp when the value of any other column in the row has changed from its current value.
Index elements were not found under rare circumstances.
Composer facade: UTF-8 characters in user credentials were not supported.
Display name of comment only associations is now processed correctly.
Wrong experience level for anonymous user was returned from facade.
Lifecycle state idents could not contain whitespaces.
In rare situations the checkout link for a file with assigned lifecycle was not rendered although the user had the necessary permissions.
Files and urls could not be deleted if freemarker templates were used.
State change link was rendered even if there was no successor state available for the user.
Disabled SSL authentication workaround for checkout and edit, as it can cause additional problems in some environments.
Footer was not displayed correctly.
Cursor positioning in script editor didn't work correctly (IE10).
ToggleContainer fixed for IE8.
Stages installation failed on 32-bit systems with jdk 1.7.21 or newer.
Core process updates and process element overlays could cause multiple enactment script associations on a process element. Moreover cancelling the overlay on an enactment script deleted to much enactment script assignments if the enactment script was assigned to multiple other elements.
Full linking of process elements could lead to multiple enactment script assignments on the element links (shadows). Now adding an enactment script to a link target element (real element) leads to the replacement of the enactment script assignments of the linked elements. Additionally modifying the comment of an association on a link target element now no longer leads to an error when the association does not exist on an element link to this target element.
When a successor workflow element was deleted, an incorrect enactment script was used for workflow configuration successor element.
The name of the successor work item was generated with a leading ":" when the workflow element had no shortname.
Script editor crashed in IE 11. Upgraded code mirror script editor to version 3.20.
In case of metric report errors the error cause is shown on screen, not only in the log file. Watchdog threads for scripts are terminated as early as possible to reduce server load.
During database upgrade (5.1 to 6.1) datetime values where converted twice
The progress indicator was missing while the metric reports were being rendered.
Metrics reports that are wider than the available browser window, now provide a horizontal scroll bar.
The last line of pixels was not visible for rendered metric reports.
It was not possible to access a database from a metric as the jdbc drivers were missing.
An invalid cookie was set and navigation was broken if an user opened a process element displaying it's associations as tree and the user user language was german. (with Tomcat 7)
Editing an element with linked elements caused an error when the user was not allowed to read the workspaces of the linked elements.
Styling of guided tour corresponding element assignment dialog was corrupt.
Always retrieve name and abbreviation for all objects
It was not possible to create a new process view filter as long as such a filter was active.
Process overview and index page access was not logged in download.log.
Attribute change links from the metamodel were also rendered in print and HTML export view.
The activation of the unsafe editor mode caused errors in combination with versioned process elements.
Lifecycle states for artifact instances that are only hyperlinks were rendered as 'No versions'.
Process deletion was not possible in case the process contained multiple elements with the same name. I.e. in rare cases process element sorting was not possible on Java 7.
The back to overview/file buttons are now rendered with the correct click area.
Process elements with a dollar sign in their name could not be printed in PDF format when the name was referenced in the document footer or header.
Assign element links were not displayed if the element was integrated from a core process and freemarker templates were used.
Fixed spelling error on replace working revision page.
CMS file status was shown as "No versions" even though CMS version information is not available.
If the section "Advanced" was not opened in the core process update form, the process element hierarchy of the core process was not adopted by default.
Links to applications in guided tours now open in the stages main windows, not in the guided tour pop-up
Textual references from Stages versions earlier than 6.0 could contain unescaped characters in project paths that resulted in unresolvable links.
Style format was removed from table rows when saving a description.
Color picker in the table dialog was hidden after scrolling in long descriptions.
Formatting tags inside of textual references are now unwrapped and cleaned during upgrade and process import.
Allow direct inlining of arbitrary descriptions without surrounding paragraph using the configuration property "global.editor.directInlining" set to value "true"
External links from a native HTML anchor tags with href attributes could not be checked for description errrors
References to uploaded images were not set to 'inline' by default.
Restrictive ActiveX settings would prohibit AJAX requests in IE8.
Resizing tables and images in process descriptions by object handles produced invalid HTML code.
Table color value could not be converted in properties dialog.
Show description errors did list used resources as unused, when referenced in multi language descriptions.
Links to arbitrary file resources did not show file type icons for external URLs.
In PDF footers and headers variables within unmanaged sections weren't replaced.
Selection ranges could not be extended over several paragraphs and links by using SHIFT and cursor keys.
In the editor link plugin, index elements are now named the same way they are displayed in the process navigation.
Process element links (shadows) must be in unsafe edit mode when their link targets (real elements) are in unsafe edit mode. Moreover it must not be possible to switch the unsafe edit mode mode for linked elements on/off directly.
Save and convert buttons were not visible in compare view when editing process elements or switching the unsafe mode off. Now the compare view is displayed in an iframe.
IE8 in Compatibility View did not correctly display empty lines (26528) and allow cursor insertion below the last line of content (26518).
The layout of the editor context menu was broken with IE8 in Compatibility View.
In some cases table cell borders were not correctly visualized in the editor.
Newly inserted tables without borders were not visible in the editor. Now they are surrounded by dotted lines.
Instantiation of a process model done by a user with only some of the permissions used in the model, resulted in only a reduced permission set for the roles in the new process.
Exported metamodel file for the Stages Composer (Process.pkitmetamodel) contained association constraints with wrong target roles in some cases. This led to an error message when the process was imported into the Composer.
ZIP export files created with project kit 4.1 could not be imported when they contained Compliance Workbench scopes from a core process.
The comment for the opposite direction of remote associations was not set correctly on process import.
In some cases the default workspace language was not set as current language when a process was exported.
Visualizations were not shown in the HTML web export.
Enactment types in metamodel were not exported to stages composer depending on the element type order.
Special characters in links to file resources for HTML exports were not correctly escaped.
ZIP export created an invalid file if not all state transitions were correctly configured.
Importing process zip export files with the deprecated export format version 6 failed with a StackOverflowError.
ZIP export was broken if an association had only a comment on the opposite side.
ZIP Export: Filter non exportable projects in project tree.
Using an "assoc" tag with style "files" or "reports" in combination with "fromId" caused problems when no elements or comments were assigned.
Comment associations are no longer shifted to the left if the assoc attribute "indent" is "true" and none of the other associations are top-level process elements.
Comments on subtype specific associations were not stored correctly using freemarker templates.
Collected files ("assoc" tag with style "files") are now alphabetically sorted. Moreover custom attributes are never displayed for collected files (even if showInTab="true" is configured for artifact instances in the metamodel).
Comments of parent/child element relations (<assoc target="parent" [...]/> or <assoc target="children" [...]/>) were displayed with the wrong comments if the parents/children appeared multiple times on the page and at least 1 direct association to them with a comment existed.
In rare cases a transaction rollback could lead to an endless recursion.
Links from Wiki descriptions to PWB resources did not open the respective resource element.
On double submit for saving a CMS based resource a NullPointerException occurred.
A null pointer exception was thrown if a cms managed ressource was downloaded and ressources were linked via assoc tag in the metamodell view (not using the ressource tab). Direct download is now always deactivated for ressources.
Anonymous user must provide cms login information for ressource download if configuration property "cms.authenticate.anon" in PKitConfig.xml is set to true (default is false).
Ensure the elements of the tailoring assistant result are sorted by their type and full name.
Pictures in the descriptions of tailoring questions/answers were not displayed in the tailoring assistent.
In rare cases, updates to the set of selected process elements of a tailoring answer were lost.
Tailoring justification was not visible in the tailoring report due to an unnecessary line break.
When Stages was upgraded from 5.1 to 6.x some tailoring states were lost.
Prevent duplicated computation of tailoring compliance conflicts.
Process Diagrams with size boundaries in only one dimension were not scaled correct, which led to much white space.
Diagram zoom pop up window could not render diagrams with specific parameters.
Added missing translation property for the navigation bar in case of an empty process.
Support users with same names in the issue tracker. Assignees and editors with the same names are differenced by appending the username in brackets. If a user is deleted, the full name (possibly with bracketed username) remains in the issue table. Filters now use the username, but old stored filters external URLs still work. If a user name becomes ambiguous, the old filters will find all users with that name. If a user name becomes ambiguous between an Excel export and import, the first user will be chosen and a warning is logged.
An error occurred when assigning an user with a comma in his name (only if using javascript in PkitRequest.xml to determine the user).
Search threw an exception if a request was found belonging to a project without a request tracking configuration.
The favicon was not displayed correctly in IE11.
Shape gradients by default only for new Shape-Stylings. Legacy look for FlowDiagramNodeShapeParams.
Some text based reources like HTML templates were not available in the web export.
Header in web export was not adopted to new styling when using freemarker templates.
Comment-only associations between wiki categories and articles caused error messages and led to a Stages startup problem.
New LDAP synchronization mode "ondemand": Users are automatically created from LDAP directory if a) they try to log in b) an admin tries to assign them to a role. The normal user synchronization is being replaced by updating the existing users individually with unique queries. To enable this mode, use <ldap synchronize="ondemand" ...> mode and set config property "sync.ldap.autocreate" to "true". Then configure the "ondemandFilter" to find unique users. The '%' char will be replaced by the userId of the newly created user, e.g. "(sAMAccountName=%,cn=Users,dc=methodpark,dc=com)".
Authenticate user based on external HTTP header that can be configured with config property "autologin.header.userIdentifier". This can be used to perform external authentication (e.g. via SAML) and pass the user to Stages. WARNING: should only be used in conjunction with a Tomcat filter or realm (e.g. OpenAM) that validates the HTTP headers. Using this option without a filter or realm opens a security gap.
Document tab can now also be opened if there is no cm profile available.
Renamed artifact folder into document folder.
CMS prefetch can start faster due to reduced preparation overhead.
This enhancement is for the deprecated Integrity interface (for Integrity versions prior to 2009 SP7): As a workaround for OutOfMemory problems of the Integrity client, Stages can be configured to restart the client process after a certain number of command executions (specify desired value with cms-option "clientMaxCommands").
Editor could not be opened in IE compatibility mode. This mode is now ignored.
Provided analysis function which tests if process workflow data are ready to be published to Rational Team Concert.
Stages user who is assigned to a responsible role will be exported to Rational Team Concert and assigned to a task as work item owner.
New permission domain "Process Execution Configuration" for Rational Team Concert export.
Process element state management handling is now fully configurable. The new config properties process.element.state.transitions.<sourceState>.<op> = <targetState> replace the existing "element.state.keepOnModify" property. <op> must be either "modify" for the state transition when modifying the element or "associate" for the state transition when modifying an association to the element. Per default, all elements are changed to "draft" state if they are modified or an element is associated with them. This is also the previous behavior. State management is now enabled by default for newly created processes.
Enabled usage of pdf header/footer variable $
If successor or predecessor elements are created through the "[New]" link, we activate the newly create element instead of the originating element to faster create sequences.
Upgrade CKEditor to version 4.0.1.1.
The editor link plugin will now scroll the currently selected element into view.
Textual references with relative paths can now be manually entered in the editor plugin dialogs to allow for robust links.
Visualization scripts (velocity .vm files) now support an include mechanism for script libraries. Scripts can be included using #include or #parse, e.g. #include("MY_SCRIPT.js"), #parse("MY_TEMPLATE.vm").
Exchanged position of URL and name filed in edit URL properties dialog.
Repeated login and logout was not possible when SSO was configured.
Login with default user was possible.
Changed default value of parallel prefetch worker threads to 1, to prevent the risk of corrupt SVN sandboxes. It can be adapted with the property "cms.prefetch.workersCount".
SVN checkout/checkin performance was unacceptable when the document had many revisions.
Integrity: Download produced an empty file when running on Java 7 and property cms.direct.download.enabled=false.
Downloads with individual user credentials don't ask twice for credentials.
Checkout and edit did not work in case a manual CMS authentication was required.
Integrity Next Generation interface: Uploading files to Integrity failed when the corresponding top-level Integrity project was created in a subdirectory of the repository.
Pending revisions are now shown as read only files.
Layout of mapping tree was broken.
Replacing the Working Revision of a reference model caused the deletion of all local scopes for this reference model.
When creating a process baseline with activated public scopes, the scope assignments were not copied to the new baseline.
Rating tab was not recalculated after assigning elements.
EnsureDatabaseIntegrity didn't honor Stages encoding settings. This could lead to broken characters in descriptions.
Checkin of a Webdav edited file with state change could result in a double submit, which prevents the checkin.
Starting updateMetamodel as Administrator on Windows did not work.
Application History Navigation did not work in case the user had no Wiki and People workspace read permissions.
SSL client cert is checked for each request to prevent session hijacking
Wrong attribute name "securityDomain" was used instead of "securityDomainName" in infocenter demo configuration.
Predecessor and successor association was inverted in best practice metamodel for the activity subtype decision.
BIRT HTML reports are now rendered as styled in the report designer and are no longer influenced by common stages styles.
Page break in pdf scripts did not work together with freemarker templates.
Defect process navigation links could render navigation useless in some browsers.
Layout of Import/Update process page was broken in IE10.
When copying an integrated core process with overlayed elements associations to elements in the source process were created. These associations became visible when canceling the overlay.
Fixed disabling of buttons in order to prevent double submits.
Scrollbars in compare elements popup were not displayed correctly.
Adoption of an overlayed element caused an exception in the update conflict dialog.
Textual References without display name are no longer supported. Old references are migrated now.
Arbitrary descriptions could not be selected in the link element dialog.
German umlauts were not displayed correctly on paste splash screen.
With IE it was possible to insert incorrect textual references to image resources by manually entering them in the embed resources dialog.
No links to arbitrary file resources with an URL (hyperlinks) could be inserted with the editor link plugin.
Improved the error messages for image map validation errors.
For IE the editor image upload dialog reported a warning message that a resource under the same name would already exist even if the resource name had been modified.
Fixes a NPE for editing workspace descriptions containing TWiki links.
Text color and background color could not be applied at the same time.
CMS managed resources could not be linked via link plugin.
Insertion of an image using the editor image plugin with Internet Explorer did not correctly replace a currently selected link.
Alignment format in textual references and indentation were not correctly migrated to the new editor description format.
An exception could occur in the editor link plugin when editing a workspace description without instantiated process.
Copy & Paste of lists changed list formatting.
Non-leaf editor tree items were not correctly sorted by alphabetical order.
By default, <img> tags are now converted to unmanaged sections on cleanup.
It was possible to produce duplicate anchor names, due to incorrect trimming.
Fixes creation of resources via the context menu of an unresolvable textual reference on a process overview page.
Directly linked guided tour stops were not opened correctly.
Custom and external ratings of a process baseline against a referenceModel were lost, when the reference model working revision was edited in the Stages Composer.
Associations from the working revision to baselines of remote processes were lost when editing a process in Stages Composer.
Standby overlay during core process update caused the error "No bean found attribute key processImportForm".
When generating an MS Project export activities belonging to multiple phase process elements where exported with associations of the wrong export task.
When creating a process baseline from a process export, shadow elements were not converted to real elements in the target baseline.
Guided tours without tour stops caused an Exception.
Comments could be assigned to guided tour stops.
File and image resources were not updated if a file with the same name was uploaded (on mysql).
An incomplete diagram was rendered in case an exception occurred in the visualization script.
Promotional agreement of a first time Stages user was not stored correctly.
Wiki overview page did not work in IE 10.
Images from OLE definitions in ARIS process descriptions can now be imported and referenced as Stages resources by specifying the attribute "importImages" with value "true" on the corresponding <model> element in ARIS mapping.
Limited support for formatting styles in ARIS import.
Extended ARIS content import with support for ARIS 7.2 data format (only plain text content, no images in StyledElement tags).
Stages attributes can now be mapped to fixed values: <attribute> <bind-field name="securityLevel"/> <value>5</value> </attribute>
Resource type can now be easily set via subtype attribute: <map-to-element type="resource" subType="template"/>
Validate if resources have either an url or content.
Element types orgunit, ypuser, category, article, standard and training can now be mapped.
Freemarker templates can now be used in order to bind aris attributes to stages fields.
Notification mails about obsolete user accounts that could not be deleted due to maximumDeletionPercentage setting now will only be sent if there are new obsolete user accounts. The complete list of obsolete user accounts is contained in synchro.log.
When executing "Update Metamodel" from start menu link, the command window keeps open so the user gets informed about success of the execution.
CMSPrefetch process will now log its progress.
Do not double command.log entries in pkit.log
Only query the LDAP attributes that are required. Previously, all LDAP attributes were retrieved when using an LDAP filter which could cause performance or privacy problems.
Support MS Office 2007 Mimetypes.
First-Level-Support mail address can now be configured by specifying a custom mail address in "support.email.address" property.
Enhanced logging of progress during ensureDatabaseIntegrity. Enabled detailed configuration of the steps to be performed. The script accepts parameters and the ConfigServlet uses the config properties added to PkitConfig.xml. <property name="database.cleanup.processes" value="true"/> <property name="database.cleanup.repositories" value="true"/> <property name="database.cleanup.targets" value="true"/> <property name="database.cleanup.processElements" value="true"/> <property name="database.cleanup.associations" value="true"/> <property name="database.cleanup.associationAttributes" value="true"/> <property name="database.cleanup.mailNotification" value="true"/> <property name="database.cleanup.attributes" value="true"/> <property name="database.cleanup.descriptions" value="false"/>
Session timeout for root can be specified using the config property "global.session.timeoutInMinutes.root". If the property is not configured, a timeout of five hours is set.
Initial LDAP synchronization after startup can be suppressed by setting the attribute "synchronizeOnStartup" in the ldap element in PKitConfig.xml to "false".
A cron expression can be specified for the configuration of the times when the ldap synchronization is done. For this purpose the attribute "synchronizeCronExpression" can be used in the ldap element in PKitConfig.xml instead of the setting "refreshIntervalMinutes". When both settings are not specified, the ldap synchronization will be done every 2 hours.
User permission caches are preloaded at system startup when configuration property "global.caches.preloadOnStartup" is set to "true" [default: false].
Project names are now normalized before saving. This will remove additional spaces (double spaces, spaces at beginning or end of project name) that would cause linkage errors that are very hard to detect.
Added developer (floating) and project manager (floating) as new license types.
Enable auto submit for artifact folder selection to allow more intuitive usage of document and resource tab.
Enabled resource overview as default.
CMS Prefetch now updates all documents which belong to Stages Workspaces that were accessed during the last 30 days.
Introduced warm caching of revision information of CMS managed documents.
Changed default value of parallel prefetch worker threads to 4. It can be adapted with the property "cms.prefetch.workersCount".
CMS prefetch does not notify the administrator about the same problems multiple times.
CMS Document prefetch can now be configured to use multiple worker threads, to reduce the runtime. See CMSPrefetchGuide for details.
CMS Prefetch problem notification mail now include more detailed informations about failed documents.
Improved logging of CMS prefetch status. Logs are written to a separate log file called cms-prefetch.log.
New MKS Integrity interface
User authentication data is now stored and will be reused after relogin or server restart. This change applies when individual user authentication is required by the CMS, e.g. MKS.
Improved caching of document revision properties.
The type of a new CMS profile can now be selected directly in the "Actions" menu.
SVN performance could suffer when working with large repositories.
MKS: When a file state is changed and no new revision is created, the state change and the corresponding comment are documented as extension of the current revision comment.
Ensure only Stages managed files are checkedout and updated from the SVN repository. This is only possible for SVN version 1.5 or later. In case an older version is used the following config property has to be set: <cms-property name="useOldApi" value="true"/>
Optimized caching of version information saves one CMS request in many cases (e.g per file and CMS prefetch pass).
New commandline script "restoreCheckouts.bat" can be used to restore checkouts of CMS-managed files that are marked to be locked in Stages but not checked out in the CMS. The CMS type must be specified as command argument.
Changed caching policy reduces waiting times for pages containing revision information.
Project path is now shown in organization-wide Gap Analysis in brackets and in the corresponding project selection page as tooltip on the project name.
Improved build time of reference model tree.
Performance improvement for compliance workbench.
Use cached sequences to improve insert performance on Oracle databases.
Improved performance of association integrity checks for oracle. Use EnsureOracleAssociationIntegrity instead of EnsureDatabaseIntegrity in order to check association integrity with oracle.
Process versions can be deleted using a facade command.
Projects can be deleted using a facade command.
An optional disclaimer can be configured for ArtifactInstance checkin and create dialogs, by defining the process.artifact.instance.disclaimer property
Project name is now included in document lifecycle notification mail subjects.
If a WebDav file can not be deleted, Stages logs an error message instead of throwing an error.
Simplification of file creation.
Lifecycle state changes can be allowed for all roles in the project with the metamodel setting 'allow ="Role:Project"'.
Lifecycle state change notifications can be activated for all roles in the project with the metamodel setting 'notify ="Role:Project"'.
The configuration property "cms.download.filename.extension" can be set to "true", if the file version and checkin date shall always be included in the proposed download names of CMS-managed files.
Superuser can now access the properties of checked out files.
CMS file path suggestion can be disabled via configuration property process.artifact.instance.create.useArtifactParentPath.
Exchanged script editor.
Improved performance of displaying files.
The LDAP provider attribute "overrideIdent" specifies, if the LDAP datasource ident for an existing user shall be overriden if he is updated by a different ldap provider than he originates from. (Default: "true")
Reverse hostname lookup may not be always possible, therefore use IP address for spoofing checks.
Configuration property 'info.allow.forceLogout' is now 'true' by default.
Added attribute caching to attributable Elements. This improves the performance e.g. for at a glance page.
Improved performance for baseline retrieval.
Allow anonymous feedback on login page by setting config property "login.feedback.enabled" to "true".
When Autologin is enabled the popup indicating an automated relogin due to session timeout can be suppressed by setting the config property "global.session.suppressReloginPopup" to "true".
5.1 release documentation is now available on info page.
Tomcat has been upgraded to version 6.0.24
Tomcat has been upgraded to version 6.0.35.
Infocenter entries are no longer marked as already read due to system performance. This behavior can be reactivated via configuration property infocenter.newsCreator.enabled.
SvnKit 1.3.8 libraries are now preserved during a Stages version upgrade.
Minor Tomcat upgrades preserve the service configuration. Major upgrades do not start the service automatically. This enables the administrator to reconfigure the service - especially runas configuration - before the first startup.
Ensure compatibility between Stages Web and Rational Team Concert version 3.0 and 4.0. VERSION file contains installed Rational Team Concert version information.
Rational Team Concert versions 3.0 and 4.0 supported.
Rational Team Concert plugin "gmrtc" renamed to "rtc".
Allow HTTPS for process export via web service.
The document "Stages Process Management for IBM Rational Team Concert" can now be found linked on the Stages Info page.
Config property "process.export.rationalTeamConcert.jazzTeamServer.ccm.url" can now be used for multiple URLs to Rational Team Concert servers (comma-separated). In the export dialog you then can choose your target server or may set the URL manually.
Tailored Enactment Scripts are now displayed crossed out in the Association dialog.
Workflow transformation now considers tailored elements and enactment scripts. Tailored elements are handled as non-enacted elements and tailored enactment scripts are ignored (and replaced by the default script where applicable).
Enactment Scripts now are displayed in a better layout.
New export function of enactment data in a process to Rational Team Concert. Only available with corresponding license feature in your Stages license.
New configuration properties for Rational Team Concert support. Use - process.export.rationalTeamConcert.jazzTeamServer.ccm.url - process.export.rationalTeamConcert.jazzTeamServer.userName and - process.export.rationalTeamConcert.projectAreas to configure the interface to your Jazz Team Server.
New attribute for association-type: enactment.
Use script 'installRtcClientLib' to copy the necessary JAR files for Rational Team Concert support from a specified location to the Stages server.
Improved performance of MS Project export.
Update of integrated BIRT engine to version 3.7.2. The corresponding BIRT RCP Designer version is 2.0.0.
Metric exports could not be opened in MS Office 2010.
Enhanced logging during report creation.
Timeout for Stages Datasource calls can be specified via config property "global.metric.report.stagesDataSource.timeoutInMinutes". [Default: 3]
Improved performance of metric script execution.
Default values can now be specified for the following custom attribute types: string, text, boolean, integer, date. The variables "currentUser" and "currentDate" can be used as special default values for string, text and date attributes (only "currentDate" possible). They will be replaced with the name of the current user / the current date when they are displayed. Additionally, the setting 'autoUpdate="true"' can be used. This ensures that the default value is always set for the corresponding attribute in the edit form and that the value cannot be changed by normal users (only root can change it).
A description can now be displayed at the top of edit pages for project or process scope custom attributes. The descriptions can be configured with the following message properties: "attributes.project.description" and "attributes.process.description".
Custom attributes can be configured in the metamodel to be shown in the file tab. Therefore the new attribute showInTab was introduced. e.g. <attribute typeIdent="myAttribute" showInTab="true"/>
Improve tree performance for webkit browsers.
The modification date of URL-based resources is now hidden.
Simplified action menu entry names.
Renamed display name of resource type "HTML Template" to "Description Template".
A process can now be created, instantiated and copied with processes create secret permission.
The role assignment notification checkbox is now unchecked by default.
Attribute comments can now be displayed on the edit pages by specifying an attribute message key with ".comment" suffix.
Process version creation is now executed in a background job if the current user has a valid email address and e-mail notifications are configured.
Cache ProcessElements on ProcessElement Index page.
Set User-Agent to IE 6.0 during search for invalid links in descriptions.
Give extended information for inaccessible URLs in Process Analysis and Resource Overview.
Allow selective column transfer.
Show locked page in case of requesting a concurrent modifying operation on the same process version.
If a resource is CMS managed then its corresponding CMS version and timestamp is shown in the resource tab.
If config property "process.element.display.remoteElementsInIndex" is set to "true" and config property "process.element.display.associations.mode" is set to "suppressBetweenModelAndProcess" then remote associations between models (source) and processes (target) are not displayed on index pages.
Improved search algorithm for retrieval of remote target elements for associations on process import and process copying: Target process elements can now be retrieved by internal identities even if their names were changed.
When the current element gets deleted, its parent element is shown instead of the corresponding element type overview page.
Improved depiction of interfaces to other processes on index pages if using ConfigProperty "process.element.display.remoteElementsInIndex".
Copying permissions and user role assignments now require corresponding permissions.
Tailoring of mandatory protected core process elements can now be modified.
Introducing view filters in Process Workbench: dependent on configuration in process metamodels users can define personal view filters displaying only filter-relevant process elements and associations.
The WYSIWYG editor is now used for entering tailoring justifications.
Remote elements are now also shown in index pages (lists and trees) export when configuration property "process.element.display.remoteElementsInIndex" is set to "true". They are also included in Excel exports if configuration property "process.element.display.remoteElementsInExcel" is set to "true". Default for both cases is "false".
Process copy option "Copy as model" renamed to "Do not copy project-specific data", because this is what it does.
Analyze menu is now in all process versions available.
Improved performance of process and resource overview page.
Reset process element state for updated elements if config property "element.state.keepOnModify" is enabled.
Reduced latency on element index pages.
Linkage of CMS managed resource revisions to process versions during process version creation can be disabled setting the config property "process.resource.freezeRevisionsInBaselines" to "false" (default: "true").
Rework CMS caches to improve cache hit rate.
The user now always must confirm the replacement of a working revision.
Replace existing working revision directly from an existing process or zip import.
When trying to find elements in other baselines, the element identity is now used first before using name matching.
Splash screen is now shown when working revision is replaced.
Ordering of elements can be configured during process update.
Protected elements can be moved. The process update can be configured to push the hierarchy from the core process or to preserve the local hierarchy.
Core process update option to save a detailed report was not checked by default.
Analyze core processes view now shows the project path of the integrated core process as tooltip.
Removed the export option "Protect core process content" for core processes. Now all newly exported core processes can be used either for process integrations/updates or import of core processs for further development in new projects or process versions.
Replaced "Protect" option for core process export and copying with the options: "Integrate" and "Further development/backup".
Tailoring justifications from core processes are now appended to element descriptions on core process update.
Core process report in Infocenter now contains project name and process version to ease version tracking.
Enabled keyboard shortcuts for 'undo' (CTRL + z), 'redo' (CTRL + y), 'save' (CTRL + s), 'bold' (CTRL + b), 'italic' (CTRL + i) and 'underline' (CTRL + u).
Editor widgets were not displayed correctly in IE6/7 and Webkit.
Added new rich text editor.
New web services are available to retrieve and write-protect the current working revision from the Stages Composer and to replace it by the new version created in Composer. Please note that Stages Composer 0.57 or later is required.
CMS Profiles are now filtered according to users permissions during process export and core process update.
A linked import element that does not have a real element in the target environment is now imported as a real element.
remove choice "Export linked elements as normal elements". Without this enabled import won't work properly.
Do not import data that have a higher format version than is supported by this version of stages.
Improved performance and reduced load.
Excel export ('Process overview'): Elements linked from other processes can now be marked by a character string in front of the element's name. Use ConfigProperty "process.element.display.markShadowElementsInExcel" to activate this feature and PKitProperty 'process.xls.shadowElement' to change the marker character string (default '>').
Demo installation contains now activity oriented metamodel and cmmi 1.3 metamodel as default.
Introduced new tag <attributeChange /> for metamodel views. The tag can be used to render a change link for custom attributes.
For generated diagrams with freemarker templates now image is shown before image-map request is finished.
Renamed "write protection" into "lock". The lock menu is now located in the edit menu.
It is now possible to set a write protection on a process in Stages Web to prevent concurrent changes e.g. while the process is reworked in Stages Composer.
New Parameter for TableDiagramLayouterParams setEnableAlternativeNodePlacer(boolean) available. Default is true.
Magnifier is now displayed on the upper left side of diagrams.
Setting the "zoomPopupRemainsOpen" attribute of a meta-model diagram tag to the value "true" will keep the visualization pop-up open after navigation by clicking on one of the diagram nodes.
TableDiagramConcept now supports option for consideration of label length when layouting an edge. Option is TableDiagramLayoutParams.setEnableEdgeLabelConsideration(<boolean>). Default value is "true".
In TableDiagramConcept it is now possible to adjust text color of row and column labels via TableDiagramStyle.getTextColor(). Default is Color.BLACK.
The optional property "URL_TARGET" for flow diagrams specifies the browser target window to open an external URL with.
Support multiple diagrams per page.
Diagrams can now be scaled by only specifying either the width or the height attribute.
Speedup for diagram rendering.
Exceptions to the root processes have been extensively harmonized. Delete, create, import, copy, use as well as all process versioning actions are now available.
Review readiness check will be executed in background. The user will be notified about the result via email.
Project name is shown in each tab of the review board.
Project name is shown in the mail subject.
Introduced additional performance tracing and a first set of performance improvements.
Avoid synchronization of documents with the configuration management system to improve response time.
Registering a new project review triggers a document cache refresh.
Reduce latency for initial Project Review Board dialog.
Project Review Board registration is now executed in a background task.
Do not set focus on id search field so that label is visible.
The new request tracking attribute "external-references" allows specifying URL patterns for references to external systems.
Request editing can now be finished via shortcut; e.g. Alt+Shift+S for saving.
The default search scope can now be modified with the property "global.search.defaultScope". Possible values are "local" (search in current project only), "hierarchic" (search in current project and its subprojects) and "global" (search in all projects).
Enable highlighting of fulltext search results
Restrict fulltext search to selected projects and visible baselines.
Initial index creation for solr fulltext search
Oracle search strictness is now fault-tolerant by default.
Tables for process element history display now have fixed and harmonized column widths.
Easier removal of Quicklist entries.
Added special "View Menu" on PWB main, index and view pages to allow user to switch between views quickly. Views (= experience levels) can now be arbitrarily configured via configuration property "process.experienceLevels.values". View menu can be enabled by setting configuration property "process.experienceLevels.viewMenu.enabled" to "true". Default is off. WARNING: all users will be reset to "basic" view / experience level!
Adjust spacing in project navigation
Moved feedback link to info area on login page.
PROJECTPATH and PROJECTNAME have been deprecated, use WORKSAPCEPATH and WORKSPACENAME instead.
The wiki start page is no longer maintained via the stages user interface. The page is now included in freemarker templates.
Wiki Root-node name could not be set. The message property "wiki.overview.tree" can now be used to set the name.
Improved overall Wiki performance.
Performance-Improvement for Wiki Overview-Page. Avoid repeated loading of Article during tree navigation.
Improve performance of Wiki category and article tree.
Wiki and Yellow Pages are now fully renamable.
Anonymous user can now be granted read access to Yellow Pages feature.
Wiki and Yellow Pages are now classified as common element providers, so it is possible to assign elements from within project groups.
User was logged out when navigation through element index trees if session cookies were disabled in tomcat.
CommandHandler caused ArrayIndexOutOfBoundsException when processing commands in threads.
Models could not be imported as images if there were no gfx objects.
ARIS process update was not possible when the option to delete obsolete elements was selected and obsolete elements had a hierarchical relationship.
HTML entities in ARIS import were not properly decoded.
ARIS date attributes like last change date could not be converted and mapped to stages attributes.
Some stages attributes were not updated.
All element states were reset. In order to identify changed elements correctly the ARIS Export must use the same encoding as the Stages server.
Fix import of linefeeds in description fields; linefeeds are now imported and displayed correctly.
Fixes Java classpath for script execution.
Added missing library to CLASSPATH of Linux scripts.
RTC-Client-Libraries are deleted while Stages version upgrade.
Users are now logged out when the license type was changed.
Classpath used by database scripts was out dated.
Compress generated JSP views, below java limit.
LDAP synchronization failed when using the "groupMemberAttribute" configuration attribute.
Adapt the JVM options such that the exception stacktrace is always logged.
"Show list" feature of the info page was slow because of missing database indexes.
Fix error on logout with secure mode enabled.
Fixed possible ConcurrentModificationException on current sessions info page.
The deletion of a user failed when the actor was not allowed to delete role assignments of the user.
Upgrade step might deleted too much webdav files.
The LDAP distinguished name of a user entry could be overwritten with a null value if the user entry was matched by multiple ldap provider settings in PKitConfig.xml.
WebDav files were not deleted when they are no longer used. The upgrade procedure will cleanup the WebDav folder.
Corrected product name in initial title of Infocenter and Process Workbench email notifications.
EnsureDatabaseIntegrity could fail trying to delete corrupted child process elements under certain circumstances.
Database cleanup script crashed when trying to delete an element which had an association pointing to a no longer existing target element.
When viewing a process element no log entry in "download.log" was created if freemarker templates were used.
Added logging of users adopted from LDAP.
Opening the list of currently active users could fail with with the error message "Null property for value 'locker'".
When LDAP synchronization on startup was disabled, user authentication was not possible.
"Show user list" caused exception if a valid Tomcat session existed for a user that has been deleted in the meantime.
Authentication of LDAP users against the LDAP directory did not work when the LDAP synchronization mode was set to "off".
Changing the license type of an user as non-root user caused ConcurrentModificationException.
Under certain circumstances email notifications regarding file state change or user role assignment were written in the wrong language if the user language setting was set to "project".
Users deleted by LDAP synchronization could lead to ElementNotFoundException under certain circumstances.
Permissions could not be displayed if their scope was not readable due to security settings.
User search did not consider all license types.
A Javascript error occurred in case a CMS profile was configured, but no artifacts.
An exception occurred on resource overview when a comment only resource was assigned.
Parent documents without files were unnecessarily listed as results of some filter queries.
Resource links to description-only resources work again.
Filtering for "Not yet assigned" lifecyle state is now possible with all CM systems.
In most cases no state was displayed in At a Glance for documents with activated file lifecycles and no files.
At a Glance resource tab (quickview.resourcesTab.enabled) didn't show the timestamp of CMS managed resources correctly (see also 15403).
CMS document cache update failed in some cases (e.g. after initial checkin to ClearCase).
File could not be checked in under certain circumstances if the user logged in with domain\username.
Optimized resource management of warm caching.
Integrity change package descriptions were not displayed correctly when Stages was configured for UTF-8 encoding.
Integrity (new interface): Version comments were always extended with the system user account instead of using the individual user accounts.
Editing a ClearCase config spec with invalid branch specification led to an error.
File state has not been refreshed after a state change.
Integrity: Trying to leave the checkout/checkin/change state dialog without specifying a change package caused an exception when change packages were mandatory.
Deprecated Integrity Windows project identifiers of RCS repositories were not supported. They are supported now because these identifiers are not changed when Integrity repositories are migrated from the file system to the database.
Integrity interface: Failed to create (upload) new files when change packages were set mandatory in the Integrity policies.
Caching error caused inheritance of CMS profile from artifacts to fail (wrong CMS profile was used).
Cache was not invalidated when an existing CMS profile was saved again.
In rare cases a CM profile with unsaved changes was cached.
Switching the CMS type during creation of a new CM profile could have led to exceptions.
Subversion: Adding a new file to the repository or referencing an existing file could fail if the directory of the file existed in the repository but not in the sandbox yet.
When the process description of another project was copied or instantiated, all CMS profiles that were inherited from the document were directly assigned to the files in the copy. So subsequent changes of the default CMS profile had no effect on the copied files.
Handle integrity connection timeout more gracefully.
Subversion: An error (NullPointerException) occured when a file existed in the sandbox that did not exist in the repository.
Subversion: Fixed potential error on initial file upload: "Error writing file for document".
In branched subversion repositories the shown revision numbers of unchanged files were taken from the parent branch.
Fixed performance issue on document properties cache access.
The CMS type in the selection box of a new CMS profile were not sorted in the sequence in which they were defined in PKitConfig.xml.
If Subversion was the first selectable CMS type in a CMS profile, fields preconfigured in PKitConfig.xml (e.g. username, password) were not filled out automatically.
In some cases the creation of new CMS profiles had problems when the CMS type was switched after certain other fields (generic) have alredy been filled out.
ClearCase: Creation of a new file in a directory failed if a subdirectory of the directory was checked out.
ClearCase: Unreserved checkouts in ClearCase prevented file modifications in Stages.
Older revisions of a document could not be retrieved from SVN repositories if the document was renamed.
NullpointerException occured in resource tab of artifacts in other process versions than the Working Revision in the following case: A cms-managed resource is assigned to the artifact which has a "frozen revision" but the file does not exist in the corresponding sandbox anymore.
MKS: Checkout failed if MKS configuration management locking policy was not set to "Exclusive".
ClearCase: It was not visible to the user if ClearCase-managed files referenced by Stages were checked out by other users. This caused error messages when a user tried to checkout such a file in Stages.
Subversion: Multithreading performance was poor.
ClearCase: If a file was checked out by Stages and only version 0 existed in the current branch an exception occurred.
Dynamic views were not guaranteed to be started on first access.
When Stages was running on Windows 7 no CVS, MKS and Synergy commands could be executed.
After the creation of a CMS profile for Subversion or MKS the corresponding files were not accessible at once (e.g. on At a Glance page).
ClearCase: Config spec check for dynamic views was done in the wrong directory. So the config specs were always recreated on initial view access after the Stages startup.
ClearCase: Directory versions in snapshot views were not always updated when needed. Because of that certain file operations like checkout could fail and refresh operations did not resolve the problems.
CMS prefetch logged end of run at the wrong time (and too often).
Argument 'full' for commandline script "listCheckouts" was ignored.
Invalid cms configuration caused NullPointerExceptions.
NumberFormatException could occur during date parsing under high server load.
Under certain circumstances subversion files could not be added.
MKS passwords were logged.
Public scopes could not be deleted.
PIID gegenation was broken.
Activating public scopes in a process could cause core process scopes to loose their protection and update capabilities.
When process elements mapped to a single reference element were tailored away, the reference element was shown multiple times in the tailoring assistant compliance violations list.
Assigning new reference models assigned additional (not selected) reference models under certain circumstances (core process restriction).
DuplicateReferenceMappings script did not work if a match mode was specified.
Core process update could break valid links to resources after resource name affixes had been modified.
For MySQL some missing indexes resulted in poor performance for specific use cases.
Upgrade step for allowing 255 characters in artifact instance names was missing.
Added some missing indexes on foreign keys for Oracle.
Overlaying integrated core process elements with remote associations could result in database inconsistencies (unidirectional associations).
In the Downloadcenter the list of topics could not be loaded on the first page load if a topic name contained single quotes.
Using the anonymous access it was not possible to download infocenter attachments that belonged to a infocenter entry of category type "common documents".
Projects with out dated request configuration could cause NullPointerExceptions in certain metric scripts.
IAssociationElement.getOpponentAssociation() did not return an association object with all expected properties.
Accessing metric collector properties could lead to an exception.
Trying to retrieve property "Profile.ExperienceLevel" of a user object caused exception.
Under certain circumstances retrieving the FileStream property of a file revision failed.
It was possible to render view links to non-accessible processes or process elements resulting in a SecurityException upon activation.
The file version properties "logMessage" and "user" could not be retrieved successfully for usage in metrics or visualization scripts.
Method getElements() in CoreProcess threw exception if the core process contained workingsets.
Obtaining experience level as anonymous user failed if cookie was not set.
Error message was not HTML escaped.
It was possible to create documents with URL references that contained only whitespace characters in their names and URLs.
Temporary webdav files remained on the Stages server in many cases when the corresponding artifact instances were deleted.
File copies in other process versions were reverted when deleting a process version.
MS Project files could no longer be edited via WebDAV.
Editing a file on a server which requires SSL client authentication was not possible due to MS Office not displaying the client certificate prompt.
When a file was downloaded, non-US-ASCII characters in file names (e.g Japanese kana and kanji or German umlauts) were replaced with underscores. Now, if the Stages installation is configured for utf-8, these characters are not replaced anymore.
Changing a file's state caused the file's content to be empty afterwards.
It was possible to create files with (logical) names that only consist of whitespace characters.
The set of possible operations for a certain file on the documents overview page differed from the set of operations on the corresponding document page.
Initial file upload could fail with error message "no current permission manager".
Upload path could be set to an invalid path in IE7.
Wrong default CMS file path was preselected in the edit dialog when creating a new file.
If a CMS file was referenced for the first time, in certain cases it was not accessible at once without refresh.
Under certain circumstances a security exception occured when editing file properties.
Lifecycle settings was reset to "inherit" if the lifecycle has been deactivated before and the file properties have been saved again later.
Not readable users or roles in notification list of files with a lifecycle could lead to security exception.
Generated list of users to notify about state changes of files (because of lifecycle definition) did not ignore reference mappings.
If a document page has been opened by an external link via button "Manage file", the file table in the page was missing.
Anonymous user could see sharepoint tab.
No radio button was selected on file conflict page shown when a new file was created and uploaded referencing an already existing file in the cms.
Deleting a locked file caused an exception. Locked files (in stages) cannot be deleted anymore.
Both attributes physical name and url were set for some files and could lead to errors.
File paths starting with slashes could lead to errors on Unix-based OS.
Tomcat upgrade to 6.0.36 due to security issues. See http://tomcat.apache.org/security-6.html for details.
Changing user names of logged-in users caused their session to stop working.
Stages URL on info page was broken.
Fixed spelling error on management overview page.
SSO sessions were not redirected correctly to the Stages main page because of changed server parameter handling in Tomcat 6.0.33+.
Editing the process workbench display setting "Process elements tailored away" for other users also applied the setting for the current user session (until next logout).
When editing quicklist all projects where removed whose folders were closed in tree.
While working on a locked project or a process that is being deleted uncaught exceptions were thrown.
Because of a bug in some versions of Internet Explorer, tooltips were not shown for images.
Changed "strike out" to strike through"
The project quicklist could not be displayed anymore when a parent project of a quicklist project was not readable.
Using multiple browser windows at a time could lead to the unexpected use of an old user session after clicking the anonymous login button.
Database config errors where shadowed by consecutive errors.
Some actions (e.g. tailoring report generation) permanently lowered the thread priority. So all subsequent operations of this thread were executed with lower priority.
Profile manipulation was not double submit protected.
Check username and client IP to prevent session hijacking (global.secureMode.enabled).
Escape stacktraces and make disclosure of stacktrace to the user configurable (global.secureMode.enabled). Check the Referer to ensure only valid requests are processed (global.checkReferer.enabled).
Do not send empty feedbacks from login page.
Check SSO Cookie to ensure that Tomcat-Autologin can not be exploited with client SSL authentification (PKI).
Single-Sign-On license validation was not working properly.
Automatic distribution of associations to shadow elements failed in full linking mode with incompatible metamodels.
Under certain circumstances upgrade could fail if "full linking" was enabled.
JavaScript on login page was broken.
Loading objects by guids caused full table scans.
Tailoring messages included escaped html.
Infocenter import is possible again.
Infocenter imports including entries with attached documents caused the import to fail.
Documentation files were copied to the wrong directory on Linux and Solaris.
Local process view directory has not been updated.
64 bit installations could not be started on Tomcat installation or upgrade without modifying the Java settings.
Upgrade used wrong installation directory on 64bit installations if Stages was installed not in the default directory.
Shadow enactment scripts were not displayed in association dialog.
Export to IBM Rational Team Concert is executable only with configured interface user in Stages configuration file (PKitConfig.xml).
Enactment Script Libraries were not exported to the Stages workflow configuration in the RTC Process Configuration.
The getUrl() method for workflow elements in enactment scripts did not return the URL to the corresponding Stages process element, but only an empty String.
The export to Rational Team Concert of a process with an enacted association to another process which had an ampersand in its project path failed due to a wrong URL encoding.
The export to Rational Team Concert of a process which had multiple enacted associations to another process took too long due to an inefficient implementation. Now the export time is significantly reduced.
The export of a process was terminated with an error message when there was an element index, an element, or a resource which was referenced from a guided tour stop in another process.
The export of a process was terminated with an error message "No value was set" when there was an entry for a custom attribute, but its value was not set.
Enacted successor references to non-enacted elements (missing work item type attribute or tailored away) which are the end of a (partial) workflow (i.e. no enacted successors) have been exported to Rational Team Concert by mistake. Now such successor references are discarded by the workflow transformation.
The 'Analyze > Errors in process description' function now handles Enactment Scripts correctly.
Associations of created process versions referenced the enactment scripts of the process version source (usually the working revision) rather than the scripts in the new process version. Subsequently imports of processes exported from such process versions failed (e.g. core process imports).
An exception occurred when exporting a process with a comment-only-association to Rational Team Concert.
A wrong warning occurred when exporting a workflow with a non-enacted parent element to Rational Team Concert.
MS Project Export could not properly handle predecessor/successor relationship between tasks that were exported multiple times.
MS Project export could contain circular task relationships.
MS Project export failed if a summary task was modelled as a predecessor of one of its child tasks in Stages.
The data set script variable currentUser is now set to the report viewing user in case the report is rendered from within Stages Web; when rendered from BIRT the data source user is set.
User language was not considered when rendering reports.
Filter open and close icons were not displayed.
Escape metric name and path
German umlauts were not displayed correctly in html reports.
Replacing a metric report by another one with incompatible parameters caused an exception on report rendering.
Metric report exports to Excel were corrupt. The corresponding BIRT RCP Designer version is 1.4.0.
Images were missing in metrics reports.
Transaction handling was not considered when deleting result columns of a metric collector.
Report parameters of type "date_time", "time" and "date" were not properly handled and could not be processed in some cases.
Default option could not be set for selection attributes.
Fixes the display of the initial attribute value, if there is a default value as introduced by Enhancement 24271.
Accessing the attributes of a linked element caused a Security Exception under certain circumstances.
Empty Attributes of type String have been wrongly exported as String "null".
Attribute caching caused an exception in the context of different meta models and linked elements.
Null values of multi selection attributes were exported as null strings and could lead to null pointer exceptions after re-import.
Adopting a process element with a linked element duplicated attributes and caused an error after editing the linked element.
Honor resource type constraints for initial view during creation.
Fixes a NPE on resource index pages with linked resources.
Check for unused resources now works with <noprint> and <nodisplay> environment.
External links to artifact instances did not work.
Process Analysis didn't check links in image maps.
Files are no longer displayed on the artifact index page by default. To reenable this set property "process.artifact.instance.showInArtifactTree". Improved performance of index page for Webkit browsers.
Project paths where not escaped in association listings.
Annotations were not deleted when a process element was deleted.
Special characters in ArtifactInstance names were not escaped and therefore broke the generated html.
Analysis of errors in process description listed used tailoring answers as unused resources.
Associations could not be saved if fulllinking was enabled, an association was deleted on the linked element and this association was modified on the origin element.
A Guided Tour Stop below a Guided Tour Stop could not be created.
Opening the assignments dialog caused an exception under certain circumstances.
Project variables in the names of cms-managed files were not replaced in the file download dialog.
Always use Working Revision of the source project during copy of process elements. Regardless of users preferred process version.
Name of process view filter was not escaped.
Process specific download file names now always contain the version name or "working revision" in case of the working revision, respectively.
Update Model did not cleanup temporary files in error situations.
State assistant for associated elements did not consider elements of the same type as the current element.
There was no "back link" in pages showing associated description-based resources.
Some boolean properties (e.g. element folder setting or the values of boolean custom attributes) could not be deactivated for artifacts when the section "Advanced" was closed before the artifact was saved.
NoPortal Mode works again.
The wrong language of a multilingual process element description was chosen for printing, if the user had selected a language with empty description in the editor before that.
A combination of associations with and without type idents caused an exception in the assignment dialog.
When elements were copied, assignments to elements with the same name were not created.
"noportal" mode: links in element trees were broken.
In dialogs where a process version of a source project could be selected, the default selection was not always the latest released version.
Assigning process elements from another process with different metamodel and subtype configuration failed with a NullPointerException.
Derivation of a new process version from the Working Revision could fail or cause database inconsistencies if the Working Revision contained a link (shadow) pointing to an overlayed core process element.
In rare cases it was not possible to copy a element with an association to an overlayed element.
If a process element was assigned to a process element the current user was not allowed to read, opening the assignments dialog caused an exception.
There were resource cache conflicts in case more than one freemarker metamodel was in use.
Inconsistency analysis function for resources was showing false-positives with guided tour stops.
Startup error could occur if UTF-8 was configured as default encoding and certain characters were used in a metamodel.
Insufficient permissions when operating on annotations were not properly handled.
File download failed (e.g. PDF print) in case the file name contained special UTF-8 characters.
Replace working revision failed if the user missed maximum modify permission on "Process Workbench" domain.
Deletion of a project could fail if its issue tracking configuration was invalid or deleted and issues still existed in the database that referenced that project.
Retrieving a user's profile could produce many database queries.
After deletion of the Root Process, the default role was missing system permissions.
An exception could occur accesing a CMS managed resource if the resource was referenced in more than one project.
Deletion of a process caused exception or at least a database inconsistency in the following scenario: The process contained an overlayed element that was linked.
Error in cache invalidation could prevent the creation and editing of process elements and their dependent data.
If a process version was created in a background job no infocenter entry was created in Stages.
Fixed possible NPE in assignment dialog.
Creation of two overlay process elements for a core process element at the same time was possible. This caused a database inconsistency.
Creation of two empty process descriptions for one project at the same time was possible. This caused a database inconsistency.
The icon for process element state "darkred" referenced in standard.css was stored in the wrong location and thus was not retrievable by Stages.
The icon for process element state "ReadyForReview" referenced in standard.css was missing.
If a user had permission "read" and "create" on domain "File", he could only see the file tab for a document if at least one instance existed for the document.
Permissions granted to the anonymous user were ignored instead of being reduced to read access in some cases.
Creation and assignment of a new process element in one step via "New" link could cause inconsistencies. These inconsistencies for example caused the failure of process version creation in the affected projects.
Creation and assignment of a new process element in one step via "New" link failed if the source element was an integrated core process element.
In rare circumstances it was possible that a Permission check returned an out dated result.
An error in the permission cache, could have caused an exception during user reassignments.
Using multiple browser windows at a time could unexpectedly overwrite a process overview description while editing another one.
Added extended logging for errors during association assignments.
Using multiple browser windows at a time could lead to modifying or deleting the wrong project, process or process element.
In a special case the Anonymous user was able to delete process elements.
Handle missing users more gracefully during sending of notifications.
Fixed arrangement of elements in rearrangement dialog.
A wrong data input form was displayed if a resource was created from an element page in case the resource type was explicitly specified in the metamodel.
Setting new starting project was not saved.
HTML export and PDF print did not work properly when Tomcat autologin was enabled.
Changing an association comment reset the state of the associated target process element.
Added additional logging.
Copying of a reference model threw an exception.
Association assignment dialogs had a potential XSS security issue.
Fixes handling of case insensitive columns in SQL Criterias.
Concurrent setting of the default baseline in the same project lead to an exception.
Association sorting was broken.
A security exception could occur when editing file properties. Now "CMS Profile" and "File" modify permissions are required to edit file properties.
Tailored elements were considered for determining lifecycle specific operations (state change allow, state change notification).
If a new user was created he could be assigned to a default user role that was not part of the valid version of its corresponding project.
Linked process elements could not be deleted if process element history was enabled.
Process element state manager did not display any element if option "all states" was selected.
If a resource was created out of the document file tab (using the '+' symbol), the resource data input mask did not correspond to the resource type initially selected in the corresponding dropdown menu.
Under certain circumstances an infinite loop occurred accessing Stages via an external link.
Support mail address in error.jsp could not be configured.
Frameset could not be loaded completely if user had no read permission on "Permission".
Under certain circumstances a exception ocurred when a new user was created.
Anonymous user could not see description add-ons made in "Modify tailoring" dialog.
The headline of "This element has been tailored" of a description add-on did not disappear when the corresponding text was deleted in "Modify tailoring" dialog.
In case the meta model association defines no targetsubtype, provide a list of all subtypes.
In the process overview pages the links to switch between languages were not rendered using freemarker templates.
Fix permission check for analysis of process interfaces
No default display name properties for annotation tabs in process element views were defined.
HTML anchor links contained in an element description loaded in the right section in split-screen mode forced a reload of the page when being clicked even if the destination anchors were defined in the current page.
External links in tailoring justifications were formatted incorrectly.
Process types having an ident longer than 32 characters cannot be assigned to a process. The length of every process type ident is therefore now checked during startup.
Analyze function "Links to other processes" did not display all project names.
Analyze function "Links to this process" did not display all project names.
When a new process element was created for an assignment (via link "New"), all subtypes of the corresponding target element type could be selected. Now the targetSubtype restriction of the metamodel is considered.
Invalid HTML could cause PDF print to fail with an incromprehensible error message.
Linked PDF print header and footer were not considered for the creation of a PDF document.
Description only elements were not handled correctly for linked elements under certain circumstances.
The security level of linked elements was not updated when the security level of the origin element had been changed.
In the core process view some update links were not shown because of wrong permission checks.
Under certain circumstances Artifacts could not be displayed to non-root users (infinite loop caused error message).
Role pages could not be opened when the feature "Yellow Pages" was allowed by the license but the necessary metamodel was not configured.
A security exception occurred if an artifact instances or cms managed resources referenced the same document in the configuration management.
Sequence of role menu entries for adding permissions and assigning users was no consistent with the sequence of the displayed permissions and assignments in the overview.
PDF document print did not contain visualisation graphics.
PDF print did not work when being logged in as anonymous user.
Links to anchors ('#') did not work.
No portal mode was broken.
State of process element index pages was not reset to its default when saving.
When copying two baselined processes with remote associations to each other from one project group to another project group the copied remote associations were duplicated and caused subsequent errors.
Ensure a valid version of a process always exists.
Metric collection interval was duplicated when replacing the working revision or valid version.
Metric collection interval was not copied when creating new process versions.
If a new process version was created fixed resource revisions were not copied from the selected source process version.
Replacing the working revision deleted all documents of the old working revision even in case they were modified in WebDAV. Instead those documents are preserved or copied to LOST+FOUND.
When the source of a new process version was from another project, security filtering of permissions was incorrect.
Under certain circumstances replacing a working revision with process exports from ZIP source could lead to duplicated metric reports and collectors.
Importing a zip export into the root project could lead to the root process being deleted when using a MySQL database.
Changes in the CMS profile were not saved after automatic revert of all locked files.
Cleans up the handling of cache invalidation for the process version caches.
Concurrent modifications of process versions caused conflicts. E.g. two valid process versions for a single project.
Process version cache invalidation did not work.
Fixes caching of default baselines and working revisions
Fixed performance issue on showing the user notification list when setting a new valid baseline.
Individual User Baselines are now correctly cached.
The creation date of new process versions was not the current date.
"Replace" action on working revisions failed for all users except "root".
New baselines were not listed in the 'Process Versions' view as long as they had the default meta-model assigned.
Non-viewable system processes (bootstrap processes) could be selected as sources for new process versions. This could lead to follow-up problems.
Under certain circumstances an exception occurred when editing a process baseline.
Project data import failed in case of overlayed elements in exported process.
Unfreeze resources when replacing working revision by a baselined version.
Process versioning notification emails (e.g information about the release of a new process version) contained a link that pointed to the Issue Tracker of the corresponding project. Now it points to the Process Workbench (as expected).
When a new baseline was created from an existing project baseline, the new baseline was assigned to the project the source baseline was chosen from.
Malformed button in ClearCase configuration profile if config spec has been customized.
ClearCase configuration profile could not be deleted if config spec has been customized.
External links to element index pages located in another baseline than the currently selected did not divert to the desired target.
Page notifying user about link targets in other process versions did not work.
Creating a process version duplicated metric reports and collectors.
State change infocenter entries were not created in project language.
Process version without any name was created if the user session timed out.
It was possible to assign process elements from baselines.
Process version state changes could not be documented in infocenter.
A security exception occurred in the element assignment dialog if the security level of an associated, integrated and overlayed element has been increased and the core process had been integrated again.
Fix for 24258: Some local modifications could not be saved to Lost+Found when the original parent element from the core process was deleted. In certain cases this lead to complete failure of the process update.
Core process update failed when update option "Delete obsolete elements" was selected and a parent element of an overlayed element was deleted by the update.
Wrong "Update" link on core process analysis page was displayed in some cases when the original project of an integrated core process did not exist anymore.
"Update" link on core process analysis page could lead to an error (NullpointerException).
Save all lost local modifications during core process update to LOST+FOUND
A process element with associations to an overlayed element was not accessible if the overlayed element was readable for the user before being overlayed and was unreadable after being overlayed.
In the core process analysis view the update link was never shown when the integrated process version had been deleted.
An integrated core process containing files with physical names but no CMS profiles could not be updated.
The core process copy option "Further development/backup: An identical new core process shall be created" did not work.
User was logged out when he tried to remove a core process and another user concurrently started an operation (e.g. core process update) which locked the process in the meantime.
Releasing a valid version after copying a process, lead to the process being duplicated.
Ensures that scripted core process updates are applied to the selected baseline.
An exception occured during core process update in case an element was overlayed in the target process and moved in the source process.
Fixed concurrency problem of element overlay: Errors occurred when a user assigned a process element that another user has overlayed in the meantime.
Overlay conflicts were not handled on core process updates with import preview.
Improved robustness of core process import in case a mapped reference model is not available.
If two integrated core process elements were associated and overlayed, core process associations could get lost when both overlays were cancelled in a certain case.
If two integrated core process elements were associated and overlayed, core process protection was not set correctly for their core process associations in some cases.
Analyze core processes view could not be opened when origin core process was not retrievable anymore.
User role assignments of overlayed roles and locally added associations of overlayed elements could get lost when the overlay was cancelled.
Core process update failed in some cases when process elements with child elements were to be deleted.
Role assignments were lost when a process with an integrated core process was imported into another project and updated with the original core process.
Updating a copied process duplicated permissions of roles. Now identical permissions that were already available in the project are replaced by the core process permissions.
Update links in the overview of the integrated core processes were never displayed when the core processes were moved or when the projects were transferred to another server.
In some cases updating a core process with option "Adopt existing elements" caused an error.
The tailoring comment of a core process element was not appended to the description when the core process was imported/updated and the process element description was created or modified by Stages Composer.
Tailoring comment of a not overlayed integrated core element (tailored but not tailored away) was not kept on update with core element also containing a tailoring comment (also tailored but not tailored away).
Updating an integrated core process with option "Delete obsolete elements" failed if assignments with the deleted elements existed.
On core process update list of process element changes (e.g. displayed number of new associations) was incomplete or wrong in some cases.
Fix sorting of process versions. The latest one shall be on top of the list.
Tailoring status of integrated process is now preserved on update process.
The alignment of an image was not displayed correctly after copy & paste.
Copy & paste does no longer create a new paragraph for the inserted text.
In the editor upload image plugin the selected file was not automatically uploaded when clicking OK.
Text was not formatted in automatically created unmanaged sections.
Nested textual references with whitespaces within the display names were not correctly migrated to the new editor description format.
Local anchor links were not correctly migrated to the new editor description format.
Guided tours could not be linked from Wiki descriptions.
Display of selection trees in the editor plugins was slow.
Starting a Guided Tour from within another one was not possible.
Elements with short names and resources with name affix could not be linked with the help of the editor link assistant.
Uploaded image with special characters in its name was not displayed in the editor.
Language tab for default language was not shown when no description languages were configured and the description already contained a description in another language.
Nodisplay and noprint directives could not be edited nor inserted with the new rich text editor.
Links to cms-managed resources were not rendered as download links.
Anchors in process element descriptions no longer need to be prefixed by 'H'. Existing anchors will be corrected.
Editor content has been entity escaped and links in the process description didn't work if there were escaped entities inside.
In rare cases invalid textual references (e.g. [[[EXAMPLE]]]) caused the problem that element descriptions could not be edited anymore (StringIndexOutOfBoundsException).
In some cases the analysis function to find unused resources returned too many results. Now also inconsistent guided tour stops and tailoring answers or queries are considered.
Remove wysiwyg.editor.useGZIPCompressor Config Property, because of security problems.
The getter method for process descriptions in the facade could not handle multilingual descriptions in a monolingual environment.
The analysis operation to find inaccessible URLs in descriptions could not cope with HTTPS URLs.
Tailoring descriptions were duplicated on multiple core process imports.
Heading 4, 5 and 6 will now be migrated to Heading 3. In order to change this behavior adopt the config property global.editor.format.migration.
The validation message for creation of new anchors in the anchor editor plugin was too strict.
When creating new anchors with the editor anchor plugin, anchor names were not automatically trimmed.
Selected text in the editor was not used as preferred name for anchor links in the 'Contents' tab.
Resource images were not scaled to their specified size directly after inserting them with the image plugin.
Legacy textual references containing HTML can now be rendered as in Stages 5.1 by disabling the config property "legacy.description.reference.displayText.escaped".
Enable migration of old Rich Text Editor description format styles.
The artifact setting "Only one file allowed" is now ignored when multiple files are to be imported.
Export of all CMS documents: Allow configuration of target encoding for ZIP entry file names by property "global.zipentry.filename.encoding" (defaults to "UTF-8").
Workspaces are no longer available for Import/Update if none of their process versions are accessible.
Resolve file name conflicts when exporting all CMS documents.
The way metric reports were written to the xml export was invalid with respect to the DTD definition.
Initial web service import via composer used wrong internal command.
Permissions modified in Stages Composer are now updated and no longer imported as additional permissions. Project specific import now updates already existing permissions.
The operations "Replace working revision", "Release as valid version" and the import of project-specific data could lead to new process elements without any project data below "LOST+FOUND".
Replace working revision from a ZIP file always copied the project data of the previous working revision.
Metamodel constraints specifying multiple element subtypes of the same constraint type were not exported correctly to the Stages Composer. This resulted in doubled warnings about missing associations in the Composer. Use 'Import > Update matching metamodels from Stages Web ...' to update your processes already loaded in the Composer with the now corrected metamodels.
A process element type without view tag in PkitProcess.xml caused HTML export errors, due to missing jsps.
The export process command interface did not export the project's CMS repository configurations by default.
Replacement of a working revision from a ZIP export did not set the process overview page description.
Baseline settings (e.g. name, state) were not set when creating a new baseline from a ZIP export.
Fixes missing import of Metric Collection intervals and improves error handling during import.
The import/update preview failed after repeated core process imports with Oracle databases.
Failure of initial process import was not displayed correctly.
Some Composer message properties have been missing in process exports from Stages Web.
Import could fail if a contained repository configuration was invalid (e.g. due to a missing/invalid repository specification in PKitConfig.xml for the specific cms type).
When importing a process baseline, its state could be chosen but was not set without process release permission.
Compliance Workbench scopes could be lost during import if the target reference model was changed in the meantime. Scopes are now additionally looked up by identity in order to overcome that error.
When exporting shadow process elements, some attributes were not taken from the real element.
HTML Export of processes with visualizations could in rare cases fail with a NullPointer exception.
An exception occured if the target project of a linking element had no process.
A linked element could link to a real element in a non working revision.
Custom ratings were associated with the wrong process if a new process version was created based on a process export file.
Under certain circumstances no rollback was performed if import failed.
Fixed JavaScript error on process export page.
Exporting multiple processes as a single ZIP file did not work correctly if the export contained projects with the same name.
Process text properties were not exported correctly to composer.
List subprojects even if parent process is not readable.
Fixed permission check for the process lock overview menu and the process analyze menu.
When a new resource was created for an assignment (via resource tab or link "New" for associations), all resource types could be created. Now only resource types that are allowed by the metamodel for assignments to the respective element type are allowed.
Tailoring states of linked elements were determined from the origin in element trees.
Reset tailoring did not reset the answers of the tailoring assistant.
Evaluate tailoring state during import of legacy process.
Tailoring answers that contained a " character caused an exception during tailoring assistant execution.
It was not possible to create a tailoring report with restricted permissions.
Tailoring priority is now handled correctly.
Tailoring resources should not be tailorable.
Fix logging of tailoring justification.
Repeated tailoring of a process element with child elements caused inconsistent results.
Tailoring reset and tailoring of single elements was not logged to the Infocenter.
Fixed determination of reference compliance conflicts for a manually tailored element.
Modify tailoring menu entry was present in other process versions than the working revision.
Properly escape tool tips.
Fix memory leak during PDF printing.
Ensure java scripts are always shutdown in a clean way.
In some cases illegal characters were generated for imagemap names.
MockAssociations: setProperty didn't work.
Process export webservice could be called without all required privileges.
Magnifying glass was shown in print and PDF print views.
Allow process deletion with Application of process rights
External links could lead to endless relogin loops on the client in case of the anonymous user has no read permission for the link target and config property "global.external.linktype" is set to "name".
Association links in the tree view were ill formated in case the noportal mode was used.
Replacing the working revision in the root project caused an error.
Tree honors startOpen-parameter again and stores open/closed-state again in cookies.
Invalid link was sent if there were no documents associated that can be used for review-readiness check.
A wrong maximum waiting period was used for Project Review Board registration.
Review registration as superuser is now possible.
Unsaved association comments get lost if enactment scripts were assigned or unassigned.
Assignment between an enactment script and an association was not saved if both were created at once.
When editing requests, entered URLs got lost after adding of attachments.
SQL syntax error in filters for issues.
While creating a new issue, the initial value for the security level was inconsistently the maximum possible, not the minimum level.
Caching could lead to SecurityExceptions.
Accessing an issue by id caused exception if the issue belonged to a project with a not configured or invalid configured issue tracking.
In Request Tracking filters, searching for terms with characters '%' or '_' in an Oracle database could produce wrong search results.
Saving an issue could lead to security exception under rare circumstances.
Entering text with % in issue tracker fields could cause problems.
Selecting a search result in Wiki or Yellow Pages could result in an exception during paging of search results.
Users could not find resources belonging to integrated core processes directly (only process elements were these resources were assigned could be found).
Process analysis on all projects caused an exception in case there are several thousand projects.
If a name affix was defined for a resource having cms managed content, an exception occured when clicking on the download link.
Take tailoring state into account during process analysis.
Recently viewed Wiki articles were missing in the result set of subsequent searches.
Advanced search and Process Data Analysis menu items are only visible if search index building is enabled. ConfigProperty: global.search.buildIndex.enabled
The user defined search area restriction of the process analysis caused an exception. An issue regarding missing permissions for processes to be analyzed is also fixed.
Database upgrade caused problem in search functionality.
Yellow Pages elements were not searchable.
Two delimiters were displayed in copy dialog.
Association lists with activated indent (metamodel setting) have not been displayed correctly in current FireFox versions.
Explanation for artifact setting "Element folder" was not correctly aligned.
Some styles defined by custom.css (e.g. heading styles) were not applied.
Users with active Stages session were disconnected and logged in as anonymous users when they used external Stages links that have been generated by an anonymous user.
Some opened Stages windows were not closed on user logout.
Validation errors in numeric user settings replace entered values with a zero.
Changed user setting was not saved correctly.
Navigation links in HTML exports were not working in Chrome.
Home link opened wrong element.
Links to tailored resources were displayed as errors in Web Export.
Internal checklists are now rendered in the same way in the export as they are in Stages.
Optional right header logo was not contained in web export.
Web export failed if custom attribute values were configured to be displayed in export views.
footer.jsp was not included in print and HTML export sites.
When opening the info page in the context of the Wiki application, clicking in the Wiki navigation resulted in an error message that the referenced jsp could not be found.
Column sorting on Wiki start page was broken.
Wiki Overview page did not show the article tree after importing a Wiki.
In some cases a SecurityException occurred on saving an article.
Links from a process element description in Wiki (e.g. from an article) to the Process Workbench overwiew of another project did not work correctly: The user was forwarded to the last visited project.
New categories were not shown on Wiki overview page unless the user performed a re-login.
Prevent SecurityException in Wiki.
Fixed race condition in article filter.
In the Yellow Pages the wrong navigation item could be selected after switching back from another application.
Allow write access to Yellow Pages departments and overview page for users without QM License. Therefore two new permission domains are introduced: "YellowPages-Users" and "YellowPages-Departments". Additionally the Wiki permissions domains were cleaned up.
Using an external link on a yellow page profile when not already logged in could result in defect process navigation in the yellow pages.
Uploaded yellow pages pictures were deleted if LDAP attribute "strictSynchronization" was set to false.
New attribute "defaultRolesUsername" may be used in <ldap-provider> statement to define the name of the user that is being used for assignment of role for newly imported LDAP users. Default: "default" (old behavior). Only used if "defaultRoles" attribute is set to "true".
PKitConfig.xml CMS-Properties for validatePath and validateFile changed. The following characters are not allowed in file path and file name: @,;'|
Extended logging when notification could not be send.
Update model does not perform database upgrade anymore.
In the core process view, now also the processes are shown that integrate the current process. For integrated core processes a direct update link is available.
Existing files (to update or to keep) are now also retrieved by their logical names.
Review reports can now be deleted from review page.
Default language is set to English.
Check for username changes in session.
If a reference model was assigned to at least two core processes and a custom rating was defined on the same reference model element in at least two core processes then importing that processes into another process caused an exception. Custom ratings and commentary types are no longer imported in the course of a core process import. This is also valid if a process description is copied and option "protect core process content" is selected.
Using Oracle a few combined indexes have been function-based by mistake. This correction will increase the overall performance of Stages, especially on importing and tailoring.
Configuration property "global.beanCache.limit" was ignored.
Internet Explorer bookmarks on the Stages urls did not always correctly redirect to the login page.
Zip export now considers metric triggers and pauses them after import.
Uninstaller was not written.
Installer did not check if recommended Java version was installed.
Under certain circumstances metric reports could not be rendered on Stages if SSL was enabled.
If a process copy was used for updating a core process integrated into its own source process, an infinite loop could occur under certain circumstances.
When a core process has been copied and the copy option "Protect core process content" has been used, index pages could be lost when the integrated core process was removed later.
Core process was not "protected" when it was exported or copied and the corresponding option was not visible.
Identities of project data were always changed on initial import. This could cause problems in combination with process updates or imports of project data.
Process import did not consider the permissions of the user doing the import regarding creation of permissions and user role assigments. If the user does not have sufficient permissions, user role assignments and permissions are not imported anymore.
Process elements with shortname were not sorted correctly.
Review irrelevant documents are now listed in latest version.
Attribute constraints can now test whether an attribute is present or absent using the new xml attribute state on the attribute constraint element.
The UpdateTarget script now creates log entries for a better monitoring of the cleanup progress.
Current project group membership is displayed in project administration.
Specific LDAP attributes can now be shown on user view page. LDAP attribute names must be specified as comma-separated value list in configuration property "user.view.ldapattributes". Only LDAP attributes that are defined via <ldap-attribute/> tags in <ldap> section in PKitConfig.xml can be used.
Warning message is shown, when role assignments or permission modifications are performed in process version that is not valid.
Modifying role assignments now requires PM or QM license.
Users with developer license may now read compliance mappings (previously required PM or QM license).
Users with PM license type may now edit CM plan.
LDAP users can now be locally authenticated by setting configuration property "sync.ldap.authentication" to "local". This can be used for importing users from LDAP servers that do not support authentication. The default password for each newly imported user is his/her username.
New license model enabled: license types QM, PM, Dev, Anonymous and Admin with respective privilege rights.
New license feature "Stages" contains all features that will be enabled in Stages. If customers do not want to use specific features, some features may be suppressed by configuring a comma-separated-list with their names in the "license.features.suppressList" configuration property.
Both autologin methods (SPNEGO/Kerberos and Cookies) are now both disabled by default. They can be enabled by setting the configuration properties "autologin.spnego.enabled" or "autologin.cookie.enabled" to "true".
Autologin via SPNEGO is now only enabled if license feature is available and configuration property "autologin.spnego.enabled" is set to "true".
Autologin via cookies is now only enabled if configuration property "autologin.cookies.enabled" is set to "true".
Projects may now be marked as "inactive" that suppresses them from being shown in lists of active projects.
Maintenance mode modified: - Maintenance mode can now be stopped via "Info" page. - Maintenance mode stays enabled across server restarts.
Important system and database parameters are now logged to logfile before generating support info.
E-Mail notification now sends E-Mail to admin and writes message in logfile instead of stopping to work.
Login data can now be preserved over user sessions if config property "autologin.cookie.enabled" is set to "true" (default). Users can enable this option via checkbox in their login dialog. The cookie login is ignored for system users (e.g. "root", "default"). If config property "autologin.cookie.deleteOnLogout" is set to "true" (default: "false"), the cookie is deleted on every logout. The default case is not to delete the cookie. Cookies can then be deleted by logging in without the "autologin" checkbox enabled.
"download.log" now contains session id.
Session timeouts and server restarts are now signalled to user on login page.
If the type of a imported associaton or process element is not specified in the metamodel then the corresponding association or elment is not created. A warning is shown in such cases.
Role assignments can now also be performed much faster in "At A Glance: Roles and Persons" tab.
Splash screen is now shown when at a glance is loaded.
Metric reports can be configured to be shown in the project state overview.
Even if the license allows usage of the configuration management system "CM Synergy", the Synergy release filter section will not be displayed on the At a Glance page as long as no Synergy CMS profiles exist.
New tab "Resources" added, that shows the list of all artifacts with their assigned resources. Display is equal to the resource list in the artifact view. To enable this, set configuration property "quickview.resourcesTab.enabled" to "true" (default: "false").
Modifying project state now always requires comment to be given.
Improved performance of CMS Prefetch (background synchronization of files managed by a configuration management system).
ClearCase: Customized config specs can be defined in new CMS profiles. This expert feature can be enabled in the ClearCase CMS properties of PKitConfig.xml by specifying: <cms-property name="editableConfigSpecs" value="true"/>
ClearCase: Dynamic view support can be be enabled by configuring the following additional ClearCase CMS properties: - viewType="dynamic" - vws (path to view storage root directory) - mvfsDrive (Multi Version File System drive; by default M: on Windows operating systems) All snapshot or dynamic views with CMS profile representation in Stages can be deleted with the command bin\removeCCViews <view type> that can be run from the Stages root directory. You have to specify either "snapshot" or "dynamic" for <view type>.
ClearCase views are now removed when corresponding CMS profiles are deleted and they are not needed anymore.
ClearCase Snapshot Views can now be updated in existing (previously saved) CMS profiles by the administrator (root).
ClearCase: Stages now ensures that the referenced VOBs are mounted.
ClearCase: Reduced amount of update commands for trying to load new files into the views.
Subversion: The property svn:needs-lock can be set in the cms profiles.
ClearCase elements from main/LATEST can now be loaded into the view of another branch by specifying a config property in the ClearCase section of PKitConfig.xml: <cms-property name="mkbranchSource" value="/main/LATEST"/> This causes a config spec rule to be applied like: element * /main/LATEST -mkbranch somebranch By default the config spec rule is: element * /main/0 -mkbranch somebranch
Accessing information from MKS Source now requires user authentication.
CMS prefetch is now more robust when the determination of the sandbox documents to prefetch fails.
Added project property "Disable CMS accesses" to simulate old behaviour of switching a process to a process model.
Subversion integration
Changed default value for PKitConfig.xml property that specifies the maximal CMS prefetch workload (busy time in the configured interval): cms.cache.maxWorkloadForPrefetchThread=0.9
Oracle statistics will now be computed by default every day at 11 PM.
Oracle performance improvement: Don't use UPPER function in WHERE clauses for GUID columns anymore. Indexes on non-GUID character columns changed to function based indexes (UPPER) in Oracle. Added some useful new indexes.
Oracle 11 is now supported.
Database cleanup script can now create missing target records and fix the source or target element type of Compliance Workbench comment associations. Additionally it can delete obsolete process element mail notification records and association attributes.
Corrected and reactivated creation of missing index pages and removal of processes without projects in database cleanup script.
Improved cleanup in MySQL database after process import, process copying or process model instantiation failed.
MySQL 5.0 TIMESTAMP fields do not autoupdate anymore. SQL can now be used again for directly manipulating data. WARNING: this does not apply to MySQL versions 3.x and 4.x!
Process metamodels that contain their lifecycle information in other elements than phases are now supported in PM export (e.g. RPlan, MSProject). To use this, annotate the respective element in PKitProcess.xml with "lifecycle='true'".
Phases to be exported to RPlan can now be selected by the user.
Task WBS export to ACTANO RPlan was upgraded to version 9.3 of the RPlan API. Export parameters that can be modified by the user are project ID, user ID and cost carrier identifier of target RPlan system.
Export of task wbs to ACTANO RPlan project management tool is now supported.
Added new property that can be queried from process elements: TailoringJustification.
Added new properties that can be queried from artifact instances: Id, FileUrl, LockerId.
Improved load times of document index and document pages when document lifecycles are enabled.
File context menu action "Checkout and edit" can be disabled by setting the configuration property "process.file.checkoutandedit.enabled" in PKitConfig.xml to "false".
Lock message of files may now include the name of the process version in which the file is locked.
Attaching external document libraries now supports user-defined URL attributes.
Modified behavior of artifact instance physical prefixes when attaching to external document libraries.
External document libraries can now be configured to use artifact instance physical prefixes for name generation.
File tab on artifact page is only shown if files are already present or user has privilege to create files.
Lifecycle states are now always shown in file history, regardless if they are set or not.
New menu item "Checkout and Edit" for locking file and automatically opening it via WebDAV.
Tomcat has been upgraded to version 6.0.26
Added mdb to mime mappings.
If configuration property "global.strictNotification.enabled" is set to "true", the user may not change his e-mail address in the "Notification" dialog and may not disable the notification mechanism.
License statement now contains usage section, e.g.: User licenses are granted on a personal basis. Admin accounts ("root", "default") may only be used for administrative purposes. At no time may log ins be used that allow multiple Users under one license.
MySQL databases can automatically be optimized.
Support for user defined project variables added: - "Edit project" now allows definition of names and values of arbitrary variables, that can be referenced via "%variableName%" syntax in project and process descriptions, file paths and file names. - "Add used" extracts all the variable names used in project or process and adds them to the list if not present. - Variable expansion can be disabled by enabling "Suppress project variable expansion" project property.
Compound display of username and fullname removed from issue tracker and user role assignment due to privacy issues.
project kit supports now UTF-8 encoding. UTF-8 encoding requires a Oracle or MySQL 5 database and can be configured by setting the config property: global.defaultEncoding. Possible values are UTF-8 and ISO-8859-1 (default value). UTF-8 prerequisites for Oracle Databases: 1. NLS_LENGTH_SEMANTICS parameter must be set to CHAR 2. NLS_CHARACTERSET and NLS_NCHAR_CHARACTERSET must be set to UTF-8 3. The project kit database has to be converted to UTF-8. UTF-8 prerequisites for MySql Databases: 1. The following my.ini or my.cnf parameters must be added or adopted: [mysql] ... default-character-set=utf8 ... [mysqld] ... default-character-set=utf8 character-set-server=utf8 collation-server=utf8_general_ci ... 2. The project kit database has to be converted to UTF-8. 3. Ensure that the torque.database.default.url property in database.properties uses unicode and UTF-8 encoding like: "jdbc:mysql://localhost/pkit?useUnicode=true&characterEncoding=UTF-8" Common UTF-8 prerequisites: 1. URIEncoding paramter for http and https connector in servel.xml must be added and set to UTF-8. 2. The notification paramter encoding in PKitConfig.xml should also be set to UTF-8.
Improved performance of logentry news creation.
Project state changes are now automatically logged in Infocenter when category "status" exists and is writable for the user changing the project state. Because project state is sensitive information, the "status" Infocenter category can be set to the permission domain "Project State" by configuring the category as follows: <category ident="state" securityDomain="ProjectState" ...
Action menu is now also used instead of submit buttons when viewing an Infocenter entry.
Metric reports could be downloaded having Report read permission. Now Report modify permission is necessary for that.
The project id can now be retrieved in the facade via property "Id".
Up to eight options are now shown concurrently for List Box report parameters which allow multiple selection.
Java packages that are needed by a data collector script can now be specified via the configuration property "metrics.dataCollector.importPackages"
Cascading report parameters are now supported by Stages.
If a project is marked as inactive, all data collectors belonging to that project are paused.
If a data collector could not be run due to an error, a logentry is now added to the "metrics" infocenter category.
Collectors can now be specified to delete old results after a successful run, e.g. only the results of the last successful run are stored in the database.
Improved performance of BIRT webservice query processing.
The size of parameter input textboxes is doubled.
Show notice "project kit is working for you" while rendering a report.
Excel adapter prepares a method to check a cell for emptiness.
Schedulers are now editable.
Birt webservice supports parameter for limiting the number of results being returned.
User can set report parameters.
Report tab and collection tab show number of contained elements.
Only one tabset containing reports, collectors and resources is shown for metric elements.
Excel adapter can read out of files administrated in a cms.
Birt reports can now be exported as pdf, ppt, xls and doc.
Reports and Collectors are rendered with the permissions of the user who made modifications to the specific element at last.
Report parameters can be set.
Project variables can now contain '%' characters in their value fields.
Process CMS cleanup script removes non-system associations to index elements
The element shortname is available via variable "$[elementShortname]" in PDF print header and footer.
Optimized performance of user notification overview when changing the state of a file.
Element trees may now use subtype specific icons. If element has subtype, icon key "<TYPE>_<SUBTYPE>" is searched first before the normal "<TYPE>".
Mark linked elements in element index and element view pages when configuration property "process.element.display.markShadowElements" is set to "true". Default is "false". If the user has no write access to the element, the link icon is not shown.
Projects can now be marked as providers of common elements for project groups. When a new process is created in one of these project groups (e.g by importing a ZIP export), assignments of process elements in other projects may not only be created within the group: They may also target an element in one of the projects providing common elements.
Project groups are now considered when a process is copied/instantiated.
Optimized memory usage of large user lists.
User role assignment dialog does not show all users in the current project if there are more than 100 user.
After creating a new associated element via the "[New]" link below the association list, the newly created element was shown. Now, the original element is shown.
When elements are created via "
Multiple user can be set as process owners for a project.
Stages facade: Property "RevisionIdentifier" of artifact instance revisions now returns the real version number instead of the revision identifier object.
Extended Stages facade: - Associated process element attributes with process elements ("requestAttributeElement@SYSTEM"). - Associated user attributes with users ("requestAttrUser) ("requestAttributeUser@SYSTEM").. - Added association filter "review" for being able to filter associations with review attributes (e.g. review=relevant). - Review jobs (contain information about reviews of certain file versions) can be accessed. They have associations to requests and artifact instances.
The process version properties "Version", "VersionDescription", "ValidVersion" and "WorkingRevision" can be retrieved via Stages facade.
Process versions can be accessed via Stages facade. The currently viewed process is always the first element in the collection returned by "getEntities("containsProcess@SYSTEM")". The working revision (if readable) is the second. All other readable process versions come next (sorted by creation date).
Process tailoring permission has been renamed into application of process. In addition to the tailoring permission this domain also allows deleting and instantiating processes.
New submenu "Advanced" added to "Action > Edit". The menu contains options "Create new identities" and "Make all linked elements local". WARNING: currently no confirmation propmpt for both options! The menu is accessable with PWB Modify Level 5 privileges. It can be enabled by setting configuration property "process.edit.advanced.enabled" to "true".
If a user checked out a file he can now edit, revert or checkin the file in all processes.
In the course of the definition of an element group regarding the pdf print function, a delimiter can be specified for every group element.
Initial upload, checkout, checkin and revert of files is allowed in all process versions (adequate permissions required).
Edit element is now the first entry in the action menu.
The user id can now be retrieved in the facade via property "Id".
The user notification format (html or text) can now be retrieved in the facade via property "Notification.Format".
Process elements as well as element groups can be printed in PDF format. This feature can be enabled via config property "pdf.enabled".
The config property "process.resource.printDescriptions.includeChildren" can now be used to specify if child resources of arbitrary descriptions should be shown in print views.
Process element state management can now be automatically enabled for newly created processes by setting configuration property "process.element.state.newProcess.enabled" to "true" (default: "false").
Process elements can be linked within their own processes.
User role assignments can now be commented.
Renamed copy subelement, link subelement, rearrange subelements and new subelement.
When copying process elements, existing associations may now be deleted before updating them.
"Link" and "Copy" subelements are now also available in process element view page "Action" menu.
Process element display is now cache based. This results in a faster user feedback when process elements contain complex associations or trees.
The full process element path is shown as tooltip when hovering over associated elements. This tooltip can now be disabled by setting the config property process.element.display.associations.suppress.tooltip.
Copying elements from same process is now supported.
"Select/unselect all" icon is now also shown when copying or linking process elements.
Improved performance of process import, copy process description and usage of predefined process model.
Process elements normally fall back to "Draft" state when associations are modified. This is performed for both involved process elements (source and target). To disable this, configuration property "process.element.state.association.resetState" can be set to "false". Default is "true".
Project variable expansion (e.g., "%VAR%") now also works in assignment comments.
Security domains are now sorted alphabetically.
The Process Workbench now supports multilingual descriptions of process elements, process element indexes and process overview pages. To activate desired languages, these have to be specified in config property "process.description.languages" as comma separated list of language codes according to ISO 639-1.
Process annotations do not have "Advanced" button anymore.
Process element index now starts with no letter selected. This speeds up the display time for very large processes. Setting config property "process.elementIndex.startEmpty" to "false" brings back the old behavior with "A" selected on startup.
Resources can now also be managed in CM systems. This applies to templates, checklists and arbitrary files.
Resources now also display date and time of last modification and the name of the user that performed the modification.
Resources now show content preview on view page for images, tours, tourstops and internal checklists
Performance improvement for creation of process versions
Improved performance of file open/checkin dialog.
New process versions now can also be created by importing a process export (ZIP file) or using an existing process version of another project.
The working revision can be replaced by an existing process version of the same project.
Valid process versions can now be separated from non-valid process versions by modifying CSS styles ".processVersionValidBaseline" and ".processVersionNotValidBaseline".
Added quick selector for process version to user settings.
Behavior of external links adapted to process CMS.
Deactivated process configuration management.
Full export/import of process version information is now possible.
Element history now also shows process baselines.
Element history can now also be displayed for elements with only one version.
Process version is now automatically converted to default baseline. Process version field is not supported anymore.
When changing the state of a process version a warning is shown for users that have no email address specified and thus cannot be notified.
A user can only modify a process if the valid process version is set to CHECKEDOUT or HEAD. Switching baselines is possible when user has the "Process Version" read privilege or "Process Workbench" create, modify or delete privilege.
Process CMS cleanup script can be launched on project project kit startup by defining and setting the following config property to "true": "process.cms.cleanup". Caution: This is only needed for repairing inconsistencies in the Process CMS and shall not be used unnecessarily.
Display always currently selected baseline as process version on each process element page.
Added caches for process element children.
Added caches for user baselines, head baseline, sandbox baseline and current baseline.
During process instantiation and copy, a specific baseline can now be selected for the source process. Note: the "Work in Progress" (SANDBOX) baseline can NOT be instantiated.
Renamed "Latest version" into "HEAD" and "Work in progress" into "CHECKEDOUT".
Process release workflow changes: - Process element state "Review" was replaced by "Ready for Review" and "Ready for Release" - Baselines states are now same as process element states - When setting state of baselines, a list of users is show that can be notified by email about the new baseline (i.e. to inform reviewers to start the reviewing). The user list is taken from all active users in the project (all users assigned to a role in the process). - Setting process as "valid process" is now a separate menu and puts notification into Infocenter.
When instantiating or copying a process and the CMS is enabled, the active baseline of the source process is copied to the target process and set as the default baseline.
The current baseline name is now displayed in the Downloadcenter and on the At a glance-Page.
The currently selected baseline is now displayed on the top right side of the main frame.
The current baseline of a process element will now be displayed in the headline after the element name.
Copy of process caused errors.
Actions menu in "process versions" is not shown if user has not the permission to create a new process version.
Improved performance of core process updates.
Core process update: When updates are available for overlayed elements, the user can open a popup in the conflict handling page which contains a comparison (of description and assignments): The previously updated version (as it would be visible after cancelling the overlay) is compared with the current update.
The core process overview page (accessible via "Process Workbench > Analyze > Core processes") now contains information about the creation date of the integrated core process version and the latest released core process version. The creation date will not be available for core process integrations and exports done with a Stages version older than 5.0.12.0.
Core process icons next to element names now contain link to origin core process element.
Process elements are now recorded as updated elements in import summary and report when their properties (name, description, element folder setting, ...), custom attributes or assignments to other process elements were changed. Before this enhancement the decision whether an element was listed in the import summary and report as updated element was only dependent of the properties name and description.
Import report now also lists modified existing process element assignments. A modification is for example the change of the assignment comment or of the mandatory setting.
Improved overlay function of core process elements: When the overlay is canceled, no core process update is necessary anymore to roll back changes done during overlay on the protected core process contents of the element.
Core process update now considers overlays and mandatory settings of process elements and assignments.
Conflict handling: When elements of an integrated core process are overlayed and the core process is updated the user can decide what to do in case of the following conflicts: 1) Updates are available for an overlayed element. 2) The overlayed element is obsolete.
Mandatory flag for core associations
Mandatory flag for core process elements
Changed default selection and sequence of import source in import/update process form from "ZIP file" to "Process of an existing project".
On core process import, process elements originating from the same core process (matching identities) but imported from another core process are now implicitly adopted.
A root element of the tailoring resources is not imported, if an appropriate root element already exists.
Speedup for (undo) overlay of core process elements with many associations or long association chains
Added details to import form for making import options more precise and easier to understand.
Added possibility to select the core process version (baseline) to import. All readable process versions except the sandbox version can be chosen.
Protected core process elements can be tailored.
Removed superfluous core process import option "Use transaction". Now the import operation is always performed as transaction.
The tooltip of a core process element icon now contains the name of the corresponding core process.
An imported process released as core process only keeps its identity when it is derived from a process export created for the further development of the core process itself (exported without core process protection).
Improved layout of Excel import report
If a process element is adopted during a core process import, its associations are adopted, too. "Adoption" means here that an association of the adopted element is converted into a core process association when the imported core process contains a corresponding association.
Core process element overlay can be undone with the process element action "Undo element overlay". This action activates the protection of the core process element again. It does not restore the core process version of the element and keeps the modifications done while the element was overlayed. However, these modifications will be reverted when the corresponding core process is updated in the project.
Elements of an integrated core process can be overlayed to make them modifiable.
The process elements of a core process integrated in a process can now be listed in the Process Workbench with the "Analyze > Core processes" function.
Protection of core process content now covers user assignments, permissions, and the following Compliance Workbench content: Reference element mappings, commentary types, commentaries, ratings, reference model mappings, workingsets.
Both, core process import and project-specific data import, can now be started with the function "Import/Update process" on the import/export page.
Core processes can now also be imported by selecting an existing project that has a process description released as core process. The old possibility of importing a core process from a process export (ZIP file) still exists.
Processes released as core process and processes containing core process can be used to create a new process description of a project. This can be done by instantiating a corresponding process model or importing or copying a corresponding process. If the instantiated/imported/copied process is released as a core process, the core process will be integrated into the new process description. If it is not released as a core process but contains core processes, its core processes will also be core processes of the new process description.
When a single core process element is copied from another process, the copy is a normal process element (no core process element).
The process of a project released as core process exported without protecting the core process content against modifications. This is useful for being able to work on a new core process version in a project where the exported core process is imported as new process description. Only users that are allowed to release the core process in its original project (domain "Process Release", operation "Modify", security level "Secret") have the option to copy the core process without protection.
The process of a project released as core process can be copied to another project without protecting the core process content against modifications. This is useful for being able to work on a new core process version in another project. Only users that are allowed to release the copied core process in its originalproject (domain "Process Release", operation "Modify", security level "Secret") have the option to copy the core process without protection.
After a core process import, an import summary is displayed to the userand a detailed report can be opened in Excel. The detailed report can also be saved to the Infocenter (category "Process changes") if an Infocenter and the category is activated for the project and writable for the user.
New script "duplicateReferenceMappings.bat" copies the reference mappings from one reference model to another (after update of a reference model). You have to specify the ids of the old and the new process model as parameters.
Core processes can be deleted from a process description.
Performance improvement for initial process import (import into an empty project)
When importing a process version other than a working revision two process versions are created: A working revision and a specific process version.
The user can now select a base for the folder structure creation when calling the processor webservice.
The project-specific import now considers permissions.
Process import can be performed using a webservice while stages is running.
A process import can be done from command line using the script "simport".
In the settings of a project now a project group can be activated. A project group consists of the project and its subprojects. Then, during process imports assignments of elements from other processes are only created within the group.
Introduced performance improvement for importing processes with assignments of elements from other processes.
Reenabled warning messages when user does not have read privileges for role assignments or permissions.
Multiple process descriptions can now be exported in a single action. The process export then consists of a ZIP file that contains the ZIP exports of the selected processes. The ZIP file has a "_multiproject" name in this case. CMS repository configurations are also included in export and can also be re-imported if they do not already exists in the project. Repository data is only included if the user has "CMSConfiguration" create privileges to be able to re-import the data.
Processes are automatically checked in after their initial creation by copying the process of an existing project or by instantiating a process model.
All process import functions now require maximum modification permissions for the domain "Process Workbench".
Mode "suppressBetweenModelAndProcess" for config property "process.element.display.associations.mode" considers now core processes too.
New attribute "shadows" in "assoc" tag allows associations be taken from shadow elements instead of normal elements. This allows modeling specific elements (e.g. roles) in a central pool and linking the elements from there.
User names were only shown when user had email address defined. From now on, user names are shown as normal text instead of the role name.
"linkstyle" attribute is now also supported in "reference-asssociations" metamodeling tag. Valid: "link" (default), "popup".
The view tag <assoc> now supports specification of a target project using the new attribute 'targetProject'. As value the complete project path separated by '|' has to be specified (e.g. 'Company|Wiki'). When using this attribute associations with the given target and type can only be created to the specified project.
New <assoc> attribute "linkstyle" can now be set to "popup" causing linked elements to be shown in a popup window. The attribute is ignored for resources.
Process element types 'Article' and 'Category' now only are permitted in Wiki metamodels (license feature). They are now assigned to own permission domains 'Wiki-Articles' and 'Wiki-Categories'.
All CM managed resources are now also baselined when a process baseline is created. This works by assigning a specific CM revision to the resource. The CM revision may also be specified manually via the new "Revision" field in the resource edit dialog.
Resources can now directly be created in resources tab of process elements. New resources are automatically created in the element folder of the first assigned resource that has the same type (e.g. checklist).
Message properties for the buttons "Add" and "Remove" in "Modify Tailoring" dialog now dependent on visibility of element.
If message property "process.multitailoring.tailorSingleElement.message" is defined, the message is shown in the "Modify Tailoring" dialog. The message is empty by default.
Message property displaying tailored elements was split into "process.multitailoring.main.justification.visible" and "process.multitailoring.main.justification.invisible".
Tailoring state of all elements is now also contained in tailoring report. Elements that are modified via tailoring show "M", elements left away via tailoring show "R".
It is now possible to tailor elements, but to leave them visible in the process (= modify them via tailoring). The user may now choose this in the dialog for tailoring single elements. Tailoring justification is now shown below element description if the element is left visible in the process. If the element is invisible, the justification is shown below the name (= old behavior).
Multitailoring assistant now also has "Previous Query" button.
The tailoring scissors icon will no longer be displayed on process element pages for the new process tailoring feature.
Dynamically rendered graphics are now loaded after the update of the navigation and header frame. This results in a much faster user feedback on pages with complex dynamic graphics.
New Visualization Concept "LeveledFlowDiagramConcept" available.
New FlowDiagramNodeShapeParams and FlowDiagramNodeIconParams Methods can be implemented in visualization scripts: LabelModel getLabelModel(element) LabelPosition getLabelPosition(element) LabelAutoSize getLabelAutoSizePolicy(element) TextPosition getVerticalTextPosition(element) TextPosition getHorizontalTextPosition(element) Insets getLabelInsets(element) Alignment getTextAlignment(element) double getLabelDistance(element) double getLabelOffsetX(element) double getLabelOffsetY(element) double getTextRotationAngle(element) double getLabelWidth(element) double getLabelHeight(element)
New property "RealElement" provides access to the real element in visualisation scripts.
If new diagram parameter "renderLinksToRealElements" is set to "true", the URLs created for the process elements point to the real element in case of linked elements. This supports the setup of process flows that connect elements from a process library.
Visualisation scripts can now set the URL of all elements individually via the 'setProperty("URL", ...)' method. This is supported for all elements that are shown in HTML maps. When URLs are set this way, a new browser window is opened upon activation.
Date attributes can now be configured to be displayed in different styles. For this purpose an additional attribute named "dateStyle" can be configured in PKitRequest.xml for date elements. The attribute can have the values short, medium or long.
Process element attribute types now link to the referenced process elements.
Attachments can be added to issues. Syntax: <attachment ident="attachment" />
Roles in default baseline of current user in the current project are accessible via scripting variable "userRoles" (can be used in visible, writable, required attributes).
Scripting functions can be defined in functions section: Syntax: <request-config ident="changeManagement"> <functions> function foo(p1, p2) { return p1 + p2; } </functions>
Possible assignees can be defined via user property. Syntax: <assignee ident="reviewer" user="var a = new Array(); a;"/>
Behavior of journaled attributes can now be specified by setting the save property to - always (default) The request attribute is always saved when the request is saved - even if it's value has not been changed. - onChange The request attribute will be saved when it's value has been changed. - initialAndOnChange The request attribute will be saved when the request is saved the first time. This ensures that the value is listed in history. After that the attribute is only saved when it's value has been changed. Journaled attributes are now be initialized with their old values when the property initialValue is set to "old": Syntax: <string ident="title" journaled="true" save="onChange" initialValue="old" />
Infocenter entries can be created on events.
The 'request' object in scriptable attribute properties like writable has been replaced by request element form stages facade.
Edit views can now be customized using freemarker templates.
Modify permission is no longer required to create an issue.
Change requests can now be created via the process workbench action menu. This requires a issue tracking configuration for process change management: <request-config ... processChangeManagement="true">
State attributes always add their own state as possible successor state. This behavior can now be configured via the property includeSelfTransition. Syntax: <state ident="state" includeSelfTransition="false" ...>
New attribute type 'process-version' showing the currently viewed process version. Syntax: <process-version ident="process-version" writable="false" .../>
Default notifications can be disabled via sendNotification property. Syntax: <assignee ident="assignee" sendNotification="false"/>
Notifications can be triggered on events.
Notification views can be customized using freemarker templates.
URL Attribute type supports now doors URLs.
Attributes can be specified to be settable only if a user is assigned to one or more certain roles.
The current user (currentUser) and the stages facade (pkit) are now provided as scripting objects.
Request filter will be applied when enter key is pressed.
Month and year can now be selected via a dropdown in the calendar popup window.
Issue attributes can now be defined as double attribute type.
Optimized advanced search performance.
The tooltips of file and resource tabs can now be configured individually for the views of process element type artifact. The following properties have to be used for this purpose: - process.artifact.instance.tab.tooltip - process.artifact.instance.resources.tab.tooltip
Added icon for Powerpoint templates (POT).
The icons for opening and closing the user parameter configuration section and for opening and closing the document filter section on "At a glance" are adjusted to the corresponding icons of the issue tracker filter section.
Buttons for creating a process version, for instantiating a process and for importing a core process now are deactivated after first click.
Quicklist entries now show the full project path when user hovers over entry. This helps in distingushing between multiple entries with same name.
Pager "(1-2 of 20 results)" is now always shown as "(20 results)" even if it is not needed for paging. This allows users to quickly see the number of entries.
Issue Tracker now contains a new icon to quicker create new issues.
Instant feedback mechanism added: small portlet where users can immediately type their question and send it to the admin with one click. Uses the given feedback infrastructure that can be configured in PKitConfig.xml (see there). Can be activated by setting configuration property "feedback.instant.portlet.enabled" to "true".
Project name link in header now leaves user in selected application instead of switching to Process Workbench
Show "none" when no security labels are defined.
Wiki now has breadcrumb path in header again.
Mailto-links of users are replaced by links to the user profile in the Yellow Pages if profile exists and read permission is granted.
Added Yellow Pages to Stages search.
Quick link to user's profile on start page.
New metamodel <view> tags for Yellow Pages metamodels: <ldapattribute/> and <picture/>
Enhancement of LDAP interface for the import of arbitrary attribute values in the Yellow Pages
New process element types 'ypuser' and 'orgunit' for module 'Yellow Pages'
Infrastructure for new module 'Yellow Pages' - New license feature 'YellowPages' - New portal element - New Permission domain 'Yellow Pages' - New attribute 'yp' for <processtype> metamodel tag
Element states of linked elements were not shown correctly.
Deleting obsolete elements deleted elements that should not be deleted under some circumstances.
User permissions were not correctly refreshed when license type was modified.
Under certain circumstances clicking on "Show users" on the info page caused an exception.
Users with activated process element notifications could not be deleted in Oracle databases.
Using LDAP attributes on user view page could lead to NullPointerException.
Role overview always displayed the current project as permission scope.
Do not show guest login button when maintenance mode is active.
Deleting multiple processes with defined scopes at the same time caused orcale dead lock.
Exception was throws when user unassigned itself from role and lost the privileges to do so.
Also be able to search for users which have a "None" license type.
License type changes sometimes had no effect before a restart of the Stages server.
Role assignment permissions for users with developer license have been ignored.
Upgrading anonymous user license was broken.
"Show Users" caused an error.
Editing a permission reset domain to project.
Management overview showed state documents of all baselines instead of the default baseline.
Files accessed by URLs instead of CMS profiles have not been displayed in At a Glance anymore since version 5.0.90.0.
Changing the project status on At a glance page led to an error message if Infocenter category 'status' was not defined.
Management overview caused an error if user had only project read permissions but no permissions for the Process Workbench.
At a glance could not be displayed if a file was moved and its former artifact was deleted.
In some cases changes in specific fields of CMS profiles (e.g. username, password) had no effect at once.
An error during creation or deletion of a CMS profile could cause processes without default CMS profile and inaccessibility of the CMS profile overview page.
Changing the default or resource setting of CMS profiles was not possible.
Subversion: Usage of SVNKit library could cause a memory hole.
Subversion: All directories in the sandboxes were deleted and created again after Stages restart.
Deleting ClearCase CMS profiles caused errors when Oracle was the database backend.
Inheritance of repository configuration did not work for files if the repository configuration of the corresponding artifact was changed.
ClearCase: Starting multiple updates on the same snapshot views at the same time caused cleartool processes that did not end. Now it is ensured that no concurrent update processes are started. The user will maximally have to wait a configurable period of time for his update process to start. If this is not possible within this time an error message will be displayed and the user will have to try again later. The timeout can be configured by ClearCase CMS property "updateLockTimeoutMillis" (default value 60000).
If the creation of a CMS profile failed, a security error message was displayed in certain cases.
ClearCase: VOBs are not mounted with cleartool mount command anymore if snapshot views are used because this fails when MVS was not installed and was not necessary for snapshot views.
Parallel creation of independent CMS profiles was not possible.
If saving a CMS profile failed with errors because of a typing error in an input field, the error could not be corrected without closing and reopening the CMS profile.
MKS: Anonymous user did not see the CMS login page and could not access pages where MKS-managed files are referenced.
CMS prefetch failed with the error message "NullPointerException" in correlation with resources managed in the configuration management system under the following condition: CMS-managed resources are links to resources of another process and a CMS profile for resources exists in the process of the link target but not in the process where the link is defined.
When a CMS profile (type "Stages CMS") was stored a useless empty directory "VIRTUAL\<module name>" was created.
Core process imports could fail if option "Delete obsolete elements" has been selected and files managed in ClearCase would have been deleted.
When creating a new CMS profile with default flag or resources usage flag activated, an error message coming from the CMS and a following canceling of the profile creation resulted in corrupt CMS profiles overview page.
Default repository configuration has been set to a specific configuration when editing an artifact or artifact instance with opened advanced section.
Subversion: Existing sandboxes could not be accessed (error message: failed to create sandbox directory).
MKS authentication: Fixed automatic authentication with login user name and password.
CVS: Label creation (currently used for feature "Compound documents") failed.
MKS: Some missing subsandboxes could not be created in a sandbox if names of other subprojects in the project did not end with "project.pj". This error could lead to a NullPointerException.
File locks set in an external Subversion client have not been determined correctly.
File locks set in an external Subversion client could not be removed.
CMS-managed resources displayed on resource tabs have been synchronized with the CMS on each access. This could substantially increase the loading time of resource tabs.
In some cases cached version information should be deleted but were not deleted when an error occurred while executing a CMS command.
CMS prefetch and manual refresh delivered wrong checkedout information for files versioned with CVS in different branches.
Allow definition of files also when no CMS configurations are defined.
Subversion: Under certain circumstances files could not be created or synchronized (ArrayIndexOutOfBoundsException).
Association deleted in the CHECKEDOUT process version did not get a DELETED state on checkin. This could cause subsequent problems: For example, deleted process interfaces were still displayed by the action "Analyze > Process interfaces".
MKS: Checkin failed.
CMS Prefetch thread sent error mail notifications because it tried to synchronize resources not managed by the CMS.
CMS configuration considered wrong permission levels.
Under certain circumstances DuplicateReferenceMappings script did not duplicate all custom ratings, external reference mappings and additional comments.
Assignment operations in the Compliance Workbench do not longer create new versions of scopes and target process elements in the Process CMS.
Assignments of external elements have not been put under version control of Process CMS.
Custom rating could not be removed
Reference models were not able to display reference associations to other reference models.
Edit rating as well as edit comment icon was always enabled if no reference element was selected and the the logged in user was superuser.
DuplicateReferenceMappings script failed.
In some cases changing or deleting assignments caused database inconsistencies.
Repeated adding and saving of assignments for the same reference model element caused an error.
User defined commentary types were not displayed.
Custom rating was not displayed.
Normal users could not assign reference models or cancel existing assignments.
Normal users could not edit custom ratings and justifications.
Scopes could not be created when instant checkin was enabled.
Reference mapping could be modified if the process was write protected.
Reference mapping could not be deleted if not yet checked in elements were assigned.
Added missing indexes on history table.
Topics with short names could not be searched.
Elements with only linked resources could not be found in Downloadcenter.
Downloadcenter showed invisible elements even if user chooses to supporess them.
Downloadcenter threw Security Exception if process elements were not readable.
Only show "Checkout & Edit" menu if browser supports it.
If a file url contained quotation marks its corresponding file context menu could not be opened anymore.
File state change was available even if the user had insufficient privileges. An exception was thrown in that case.
File action "Problem resolution" was broken.
PowerPoint presentations could not be edited via webdav.
Under certain circumstances lifecycle state names have not been correctly displayed in notification emails about state changes of files.
Creation and change of artifact instances caused errors.
Changing the state of a file caused an error under certain circumstances.
Change of license of a user did not invalidate the central user permission cache. A restart was necessary.
Localization of file "web-security.xml" was not robust enough on Linux.
Initalization of webdav was very memory consuming. An out of memory exception was thrown.
The file web-security.xml could not be found under Linux.
User permission cache caused the execution of many unnecessary database queries when it was not filled and was accessed concurrently.
Customer specific Tomcat security settings configured in file web.xml were lost when updating Stages.
Autologin: User has been logged in even if maintenance mode was enabled.
Clicking on breadcrumb path did not work if portal element was overlayed by settings or notification dialog.
Fixed problem regarding autologin: External links did not work correctly after a user logged out.
Fixed problems regarding tomcat autologin: - Metric reports containing Stages datasources could not be rendered - PDF print did not work
Fixed problems regarding tomcat autologin: - Tailoring report could not be downloaded - Nothing could be downloaded from the info page, e.g. User Guide
Runtime information could not be downloaded when tomcat autologin was enabled.
Fixed problems regarding tomcat autologin: - User could not login again after a manual logout. - An exception occurred when the session of an automatically logged in user expired. The user could not log in again after that. - Kerberos autologin was processed when enabling tomcat autologin. This caused exceptions.
If the user session expired the user could not login again when autologin was enabled.
Caching algorithm caused NullPointerExceptions under certain circumstances.
Project navigation vanished under very specific circumstances.
In some cases autologin did not work if anonymous access was enabled.
User license types now react as described in Administration Guide.
Project variables are now also supported in URL resources.
HTML mails were not sent correctly.
Startup errors were not shown to user.
Fullscreen symbol was always displayed in checkin and select baseline dialog.
Database upgrade did not work. License is now loaded before upgrade.
When older reference model exports (until dtd version 1.3) were imported the created processes were not automatically set reference models.
New Infocenter entries about project state changes had an incorrect title (undefined message properties).
Attachments pointing to tWiki links threw exception.
Users without e-mail address showed up as "null" in Infocenter view.
Property logbook.list.sortmode was not defined for the Important Dates category in the Infocenter.
Clicking on Infocenter search hit did not update header and navigation frame.
SVNkit libraries were lost during Stages update.
Issue tracker configuration files were lost during Stages upgrade.
Diagram folder has not been backuped when upgrading tomcat.
Parent elements which are deleted in the sandbox could be checked in without the need to delete and checkin the child elements.
MS Project export could contain cycles.
MS Project export failed if element type "Phase" was not configured in the corresponding process metamodel.
MS Project export ended in an infite loop if the exported process contained an association cycle.
Under certain circumstances predecessors of a task were not set correctly.
Wrong task constraint type was used in MS Project Export.
Copying a metric also copies the triggers and results of its collectors and pauses the triggers. Creating a process version copies the metric triggers and metric results of its collectors. Releasing a process version as valid version replaces the metric triggers and results.
Viewing a metric report caused a null pointer exception under certain circumstances.
Splash screen was not shown when applying or resetting parameter values.
If multiple data collectors with the same name were specified for a metric, only one of these collectors was shown.
Metric collector script evaluation was sometimes run in wrong user context.
Images retrieved from a database BLOB field were not displayed in a metric report rendered in Stages.
User report parameters were not deleted when the corresponding user was deleted.
Metric collectors could not store explicit "null" values in data schema result columns.
A data collection failed without a warning if it tried to store data which exceeded the maximum data size.
Under certain circumstances metric reports could not be opened in the BIRT RCP Designer when they've been downloaded from Stages.
Reports were not shown correctly if autologin was enabled.
Editor for defining data collector scripts did not work if an upgrade from project kit to Stages was performed.
Using radio button parameters caused exception in some cases.
Upgraded version of metric collector script editor due to display errors occurring in Firefox 3.
Reports did not get rendered when applying or resetting user parameters using Internet Explorer.
In some cases grouped report parameters could not be stored.
Adding a collection interval to a data collector caused the creation of a second but incorrect collection interval.
In some cases security labels of metric collectors were not saved correctly.
Empty strings were accepted as result columns of a data collector data schema.
Added missing properties.
In some cases a wrong default value was set for a report parameter.
Report parameter of type "Boolean" were not displayed correctly.
Report parameter with names containing whitespaces were not handled correctly.
"Current metric" links in Stages Data Sets where not correctly set before querying report parameters.
Security labels of data collectors and metric reports were not imported correctly.
Unsupported cron expression led to exception.
Opening of a metric element failed if an associated metric report document was invalid. Uploading of invalid report documents is not possible anymore.
Empty strings were not correctly encoded by the BIRT webservice.
Rendering of a report failed if the name of the corresponding metric was changed.
After editing a metric, associated reports and data collectors were temporarily not shown in the corresponding tab.
Umlaut in "currentMetric" field caused exception.
Referencing the excel adapter from within the Birt RCP Designer did not work in some cases.
Creating subelement of metric element failed.
Imported metric elements were not assigned to their corresponding parent elements.
Scheduler date format check wrongly failed.
HTML export didn't export metric elements when "Metrics" license feature was enabled.
Excel adapter could handle formulas.
Embedded images in a birt report were not shown when rendering the report in project kit.
A process element could not be deleted if an association of that element was not defined in the used metamodel anymore.
Association logic was not robust enough handling unidirectional associations.
In the dialog for the assignment of users to a specific role, the assignment status was lost for unsaved assignments while adding other users.
Under certain circumstances comments of calculated process element assignments where not shown correctly.
When deleting a permission the wrong permission scope was displayed.
If a visualisation graphic was taller than the available page height, it was displayed starting at the second page leaving the first page empty.
Usage of PDF print header and footer variable "$[elementState]" caused exception if element state management was not enabled in the corresponding process.
Failed to delete processes and projects in some cases when ClearCase CMS profiles existed.
Screen view differed from print view when elements were tailored away and configuration property "process.element.display.suppressInvisibleElementLinks" was enabled.
Under certain circumstances releasing a process version as valid version caused a security exception.
Process deletion failed in some cases when CMS profiles were directly assigned to artifacts or resources.
Under certain circumstances a shadow process element referenced itself as parent element.
PDF print did not include header and footer when freemarker templates were used in the corresponding process.
"Distribute process elements" failed with error "currentElement not set".
Folders of remote elements in index tree could not be opened if configuration property "process.element.display.remoteElementsInIndex" was set to "true".
Under certain circumstances a process model in an unprivileged state was available for instantiation.
Deleting an annotation displayed in append mode could produce broken following page.
After adding an annotation the description of the corresponding process element was shown instead of the annotation page.
Trying to print a process element as anonymous user failed.
Under certain circumstances duplicate username entries could be stored.
When comments existed in comment tab of process element assignments and the comments were modified or new comments were added, the comments vanished when the changes were saved.
Superuser could not perform state changing operations (e.g. create, checkin) on files with lifecycles in other process versions than the valid version on rare occasions.
If a new user was created he could be assigned to a default user role that was not part of the valid version of its corresponding project. (was 20303 in 5.1)
Some buttons (e.g. for using process models) had no function in latest release.
Property keys for an element type having subtypes was built up incorrectly on the element type's index page.
The context menu of a file was broken if function "refresh" was called for that file before and a visualization diagram was shown for the corresponding artifact element.
Printing an element description containing a visualization diagram caused a javascript error.
Copying more than one element with associations assigned wrong target elements on rare occasions.
Under certain circumstances Ldap users could not be deleted if they had defined user-specific settings.
A subelement with subtypes could not be edited if no default children subtype was set for its corresponding parent element, e.g. due to metamodel change.
An Association with a resource as target could not be accessed within visualization scripts if the association has not been modeled via <resources> tag in metamodel.
Copy elements did not consider tailoring state of hierarchic elements if these elements were newly created in the target process.
Under certain circumstances copy elements created multiple elements with same identity.
Copy elements function did not consider tailoring state of hierarchic elements.
Shadow elements (element links) have not been created below a parent element - even if they had parent elements in their source processes and elements with matching names and types existed. PWB Import/Export]
Multitailoring dependencies have not been handled correctly by copy process elements function in some cases.
Resource contents were not updated although extended copy option "update properties and assignments of existing elements in target process" was selected.
Extended copy option "Use element names to find existing elements in target process" had no effect in some cases.
When copying a process element with its assignments, the comments of the original assignments were not copied in some cases.
Process element could not be linked if it was a shadow and has been moved to a new parent.
Updating a non readable process element caused an error.
Under certain circumstances updating a process element caused an stack overflow.
When a process element has been copied, existing process elements have not been retrieved by name by default. This could cause that existing process elements have not been used as parent elements or association targets when they should.
Under certain circumstances the permissions assigned to a role where not shown to a user although the user was allowed to read that permissions.
Process elements could not be updated via copy dialog if copies of process elements with the same names have been created before.
Icons of assigned resources were not rendered correctly when resources were links.
Comment associations have not been displayed subtype-specifically on process element pages (e.g. resources of type "checklist" have been displayed in the listing of templates). Additionally problems occurred when associations with subtypes have been modified or deleted.
Changes of artifact instance properties made in the section "Advanced" have not been saved when the Advanced section was closed before saving the artifact instance.
Coping process elements with activated option "Use element names to find existing elements in target process" caused infinite loop when copied elements in a parent-child-relationship had the same names.
"Copy subelement" was broken with some browsers.
Copying a process or creating a new process version failed if associations with source and target roles were not configured in metamodel anymore.
Creating annotations in process versions failed.
When copying process elements, matching existing elements based on names may now be turned off.
When copying process elements, element hierarchies and association sort order is now correctly transferred to the new process.
CMS Profiles were lost when copying a project.
Failed to copy a process and to create baselines in the following case: The affected process was not a reference model but it has been a reference model before and other processes have been assigned to it in the Compliance Workbench.
Allow processes to be instantiated when user has only tailoring privileges, e.g. when user has PM license type.
A process could not be deleted if the corresponding project was mapped against a reference model which has been deleted in the meantime.
UpdateTarget command sometimes generated the wrong entries when "shortname" metamodel flag was used.
Some features of "Copy element" dialog were broken.
Creating new elements could cause excessive database query under Oracle.
Creation of subelements of type "standard" failed.
Errors in Process Description page used wrong property keys from some process element types.
Instantiating and copying processes could fail with wrong error message about duplicate associations.
Associations were not correctly transferred when copying or linking process elements.
Link for creation of a new process element as association target was displayed even if no create permission was granted.
Adding external links in editor was broken.
In some cases the user was not warned about the consequences of editing or deleting a linked element.
Adding and editing of association comments did not work reliably.
Rearranging of associations did not work.
Lifecycle state display caused NullPointerException under certain circumstances.
Commentary assignments were not displayed on process element pages when a target subtype was configured in the metamodel for the corresponding association type.
Deleting a process as a normal user yielded exception. Process lock was not removed after that.
Linking or copying of metric or artifact elements failed, if the user did not have the permission to create the corresponding metric instances or artifact instances in the actual project. Now the instances the user is not allowed to create are ignored. PWB Distribution]
Instantiating a process model or copying the process of an existing project failed for normal users when process elements were mapped against a reference model.
Instantiating a process model or copying the process of an existing project yielded a Security Exception because of missing Baseline privilege in process owner role.
The project language was not returned correctly as default language in multilingual processes.
HTML code was displayed in HTML template descriptions after saving the resource multiple times.
State report of process element states showed wrong number of elements.
Element could not be created if a user had only create permissions.
Improved performance for hierarchic find operations
Creating new process element notifications failed under MySQL5.
Clicking on active tab on edit pages for multilingual descriptions quit edit page
Notifications caused problems when used with process cms
Upload of images in editor failed
Element order associations weren't displayed correctly.
File management is now also possible in process models.
Notification emails about changed and deleted elements now have better messages and subject is set to a default if it is not set by the user.
Process version modify permission was not sufficient in order to release a process version as valid version.
Version history page for metrics was missing.
Prevent IsLockedException (and following NullPointerException) when trying to create a new process version (also on registration for project review). When a process version now is generated, other process versions can only be created subsequently.
Process version could not be set as valid version under certain circumstances.
Releasing a process version as valid version now adds and replaces project data. Added new option "add and replace" to project specific import.
Cached process descriptions could be obsolete. This could cause that a user did not see the latest description on the process overview page.
Process element history page caused error if an element version was not readable by the user (e.g. because of higher security level).
Copying a role caused the target project to be the scope of all copied permissions. Instead of that, the permission scope must only be changed if it is the project of the original role.
Changing the user process version could cause system freeze.
Checking in a process element created two versions of every association pointing to the process element.
Failed to create comment-only associations.
Names of process versions now have to be unique. Names of system process versions cannot be used anymore.
Reverting process changes concerning remote associations did not remove the corresponding baseline element records.
Deleting an user did not delete entries in UserBaseline table.
Associations between Yellow Pages and Wiki could not be deleted.
Resources now also have "Version history" menu item.
Resource content (e.g. templates, examples, images) is now correctly version controlled.
Reverting changes now also deletes dependent data (e.g. resource content)
Menus for selecting source baselines in instantiating and copying processes should not show SANDBOX baseline when auto-checkin is enabled.
Process element history should not show "create menu" for non-existing elements. Normal error message is now shown instead.
Privilege problem when instantiating and copying processes fixed.
After deleting a process version no other version has been selected.
Setting valid process version was not properly checked.
Modifying baseline state to a normal state always needed "Process Release" modify privileges instead of "Process Version" modify privileges.
Split process element chains were accidently added to head baseline by process CMS cleanup script
Process CMS cleanup script removes wrong parent information from elements.
The process version was set to CHECKEDOUT after having made a reference model element assignment although instant checkin was enabled.
Motification of association could cause wrong state of prior versions.
Process element history displayed 'null' when user who changed the process element was unknown.
The checkin of an element deletion showed a warning that all children of that element need to be seleted for checkin, too - even if they have already been selected.
Users were several times listed in file state change notification view.
Process CMS cleanup script caused ConcurrentModificationException
Process Workbench did not handle multiuser access to the same elements.
Historical versions of remote associations stayed visible when other associations where added.
Trying to create a process element assignment failed with a NullPointerException when the corresponding association type was not defined in the metamodel.
Process CMS cleanup script did not finish repairing process element dependent data records in some cases.
Assignees in the Issue Tracking component cannot be selected if several revisions of their roles exist.
Could not create more than one commentary assignment.
In some cases users still used a process version that was a valid process version before but in the meantime another user made a different version the valid process version.
Users could enable/disable automatic checkin of process changes when they did not have the necessary permission to modify the process version.
Process CMS cleanup script failed to handle role assignments that pointed to the wrong role versions.
Modification of associations did ignore instant checkin
Process version change state dialog did not show button control in internet explorer.
In some cases when linking a process element (creation of a shadow element) the wrong version (not the origin) of the target element (real element) was associated. This caused several problems: For example the process element index page containing the link could not be displayed anymore after deleting the real element.
Creation of external associations could cause error.
Creation of comment associations caused error.
SANDBOX process version could remain selected when instant checkin is enabled.
SANDBOX elements could exist in instant checkin processes after update from older versions.
Failed to checkout resources with content in some cases.
Project-specific data (e.g. files, metric reports, ...) have not been visible anymore after upgrading from project kit 4.1 to project kit five, when a version history for the corresponding process element type with multiple versions had existed.
Baseline dialog could not be opened under certain circumstances
Deletion of associations did not work under certain circumstances.
Select process version dialog did show CHECKEDOUT baseline for instant checkin enabled processes
Creation of a new process version caused error if only create rights were granted.
Linking/Copying of process elements did ignore instant checkin settings.
Checkin of process elements did not consider user permissions correctly.
Changing an element did not update the element view.
Process import caused errors when automatic checkin was enabled.
Remote associations were not created correctly.
Instant checkin caused error in association assignment dialog.
Association assignment dialog did not update association list correctly.
Process CMS did not show pictures in compare view
Buttons in change process version dialog did not work.
Process version could be created without name.
Corrected text of revert dialog
Select baseline page did not notice user baseline change on checkout.
Creating an annotation does not create a new version of the associated process element anymore.
Activating automatic checkin caused an exception if associations had not been checked in.
Revert caused an error if the process element to be reverted was associated with other elements and was never checked in before.
If there are no process elements that can be checked in a message is displayed in the checkin view.
A version history is also displayed for index elements.
Process element history was not displayed with new process CMS when history contained elements not readable for the user.
Instantiation of a process model baseline failed
Check-In failed if write access for a remotely associated element was not granted
Checkin/Revert elements caused an error if no user baseline is selected.
Process version was not displayed on resource overview page.
Changing elements of integrated core processes (e.g. creation of new associations) failed.
Fixed error when checking in deleted parent of shadow elements.
Fixed problems finding too many shadow elements
Checkin view did not show process element children anymore
Element names were not escaped in checkin dialog.
Document lifecycle management did not use the privileges from the process default baseline correctly to calculate the user's permisssions.
Write protection for non-changeable baselines did not work properly.
Checkedout elements without a head version were deleted improperly.
Delete baseline option was visible for non-deletable system baselines
Upgrade of process containing history elements caused problems in element hierarchy
Check for hierarchic checkin/revert did not work correctly
Baseline privilege handling fixed: - users without "Baseline" read privilege may only see default baseline (= valid process version) - switching between baselines requires "Baseline" read privilege - creating, modifying and deleting baselines requires the respective "Baseline" privileges - setting valid process version requires "ProcessRelease" modify privilege - changing baseline to a normal state requires "Baseline" modify privileges - changing baseline to a privileged state requires "ProcessRelease" modify privileges
Role assignment, permission creation and role notification should only be accessible from roles that were checked in before.
Baseline timestamp is now shown in user/project language.
Shadow elements always point to the HEAD revision of a CMS managed process element. Thus, they must only be creatable from elements that were checked in at least once.
Viewing the "sandbox" version of a document caused exception if a "latest" version of the document exists and the document has a file assigned.
Process element history did not expand twiki links.
Shadow elements that point to elements that are not yet checked in caused exceptions.
Deleting a currently selected baseline caused an error.
Assigning elements to tailoring answers duplicated the process element in some cases.
When enabling process CMS, HEAD and SANDBOX baseline now have the default state instead of hardcoded "released" and "draft".
Deleting a process failed under some circumstances.
Use pre-defined process model failed if the target element of an association was located in another process and had more than one version.
Change baseline dialog seemed to allow name change for system baselines.
Checkin/Revert view cached old element views and comments.
Checkin of hierarchic elements caused error, if deleted parent was checked-in, but child was not. Error also occured if newly created child of a newly created parent was checked in, but parent was not.
Guided Tours were not visible.
Process element state was not properly shown if PCMS was enabled and "Set State" menu was used.
Permissions of roles deleted in the CMS are now correctly ignored.
Process element index pages were not managed by CMS
New/Edit element links were shown for elements of non-editable baselines
Display of compare view did not have the same style.
Use pre-defined process model created head baseline twice.
CMSException is now much more chatty.
Lifecycle management for artifacts now uses default baseline of process to determine authorisations and notifications.
On process duplication elements have been added more than once to the sandbox baseline.
Dependent data was not correctly associated when linking or copying a process element.
Process CMS and converting old to new tailoring dependencies did not work.
Old process version is now automatically converted into a CMS baseline. Process version is now disabled and replaced by default CMS baseline name.
Checkin/Revert elements and select baseline was present in no portal mode.
Checkin/Revert elements and select baseline was present if write protection is enabled.
Checkin/Revert elements and select baseline was present if the project has no process description.
Reference model could not be assigned.
Various fixes to process CMS
Associations deleted at overlaying process elements where exported even for core process imports.
Editing the mandatory flag of optional core process elements integrated into another core process was only possible for root.
Process update did not create local associations when matching local target elements could be determined and import option "Create process interfaces" was not selected.
Core process update failed when integrated core process elements had additional associations (not defined in the core process itself) and the elements were overlayed.
Superuser was not able to delete protected core process elements and associations
Resolved performance problem in association reporting of core process updates.
Process element index pages could be lost on update under certain circumstances.
Failed to import a core process that contained the root element of tailoring questions and answers into a process in which this tailoring root element already existed.
Importing a process (process type = process) with an integrated core process made all integrated core process elements be displayed without core process icon.
Core process update activated compliance scopes multiple times if adopt was not set.
Process element assignments of newly imported process elements have not been listed in import report.
Under certain circumstances the core process import preview failed.
Wrong warnings about associations not configured in the metamodel have been displayed after core process import when resource assignments existed.
Under certain circumstances additionally defined assignments with elements of integrated core processes were lost on core process update.
Under certain circumstances overlayed resources could lose their content (file attachment) when the overlay was canceled or when the resource was updated.
Integrating the same core process into other core processes and then integrating the other processes again into another project could lead to the loss of process element assignments, if these assignments were not defined in all integrated core processes.
In some cases core processes could not be integrated in Process descriptions created from Stages Composer exports.
Core process import and process content import did ignore artifact setting 'Only one file allowed'. Now files are ignored for import if such a file already exists and adoption is not selected.
Comment assignments lost their core process protections and update capabilities when they were saved in the assignments dialogue.
Assignments of kept obsolete core process elements were still protected from changes.
New process elements imported by a core process update were created on the wrong hierarchical level (top level) in the following case: They were child elements and their parent elements already existed before the update.
TWiki links on core process elements did not work in some cases when elements have been moved by a core process update from a child hierarchy level to the top level.
Import setting "Use heuristics" was deactivated when import was started directly after import preview.
The process version selected on the Import/Update process page was not correctly displayed on the following import pages.
Importing a core process with a Compliance Workbench scope for a not existing reference model failed.
Preview of core process update failed when the source or the target of an importable element assignment was overlayed in the target process.
After copying a process with integrated core processes or creating a new process version of such a process, the integrated core processes were not visible in the new process (e.g. by clicking "Analyze > Core processes" in the Process Workbench actions menu).
Exported and reimported overlayed core process elements lost their overlay status.
Core processes containing permissions that have been exported with Stages 5.0.15.0 could not be imported again.
Adoption mechanism for existing process elements did not consider the exact element path.
Importing a remote association as local association failed when the export also included an identical local association.
Core processes were shown in the instantiate model dialog.
Adding user assignments to a role of an integrated core process caused user assignments defined in the core process to be removed from the role.
Core process update removed user assignments from core process roles that have been added to the roles where the core process was integrated.
Updating a process caused an error if no core processes were available.
Inconsistencies in exported process could cause core process importer to create unidirectional associations or not to create affected associations.
Core process import changed UTF-8 characters.
Function "Analyze core processes" displayed "unknown" in the version column if the working revision of a core process was imported.
Under certain circumstanes a core process could not be updated if a reference model was assigned to that core process.
Core process scopes were lost during core process update.
Using core processes with large process version names may cause an error.
Overlay element action was missing in actions menu of resources.
Some process element attributes that should not be changed have been modified by core process updates: tailoring justifications, lifecycle settings, CMS profile settings and attributes used for resources managed in the CMS.
Security labels and some type-specific attributes of process elements (e.g. resource tags) have not been updated.
When a shadow element (element link) was overlayed and converted to an element copy the following problem occurred: After the overlay was canceled and the core process was updated, the process element was still a copy instead of a shadow element.
Resources with content could not be updated if they were shadow elements (element links).
Updated shadow elements (element links) lost their reference to their real elements (the link targets).
Comment assignments added to elements of integrated core processes were lost after the core process has been updated.
Comment assignments of elements from integrated core processes have not been protected from changes.
Importing a core process with assignments to a local and to an identical remote process element failed.
Index elements and process element types undefined in the metamodel sometimes have been displayed in the import report category "Kept obsolete process elements".
Integrated core processes were not retrievable via "Analyze > Core processes"-function and could not be removed in the following case: A process description has been copied from another project and the source process was a normal process that contained a core process.
Elements of an integrated core process could not be tailored via "Actions" menu on process element pages.
Updating a core process with reference element assignments multiple times failed.
Failed to create new comment associations for core process items.
Reimport of previously removed core process failed.
Undo overlay used wrong language to mark the process element to be updated.
Under certain circumstances process element associations were lost during imports when remote associations should be converted to local associations.
Under certain circumstances associations of overlayed core process element were lost when the core process was updated.
Resource update was broken.
Function "Overlay element" did not checkin all changes when core process associations were overlayed. This caused database inconsistencies.
Core process name was missing in tooltip of core process element overview.
Elements of a process with integrated core processes could loose their core process identities on import. This caused problems when trying to update the integrated core process or to view the list of their elements.
Imports or updates of core processes with mutual process element assignments failed with error "Trying to change an outdated version".
Overlay of core process elements failed.
Obsolete assignment of remote process element has not been removed on core process update in some cases.
Released state of imported or copied core processes has not been set to "Released as core process" when the original process has been exported/copied without core process protection.
Import report generation could yield security exception.
Import failed when multiple bidirectional associations for the same source and target element were imported.
Subsequent imports or import previews with the import option "Adopt elements" failed.
Import preview displayed wrong results in some cases.
Import report wrongly listed existing role assignments under the category "Deleted role assignments".
If all changes done during the import belonged to the same change category, the summary table in the Excel import report contained no entries.
Failed to save import report to Infocenter automatically, if the importing user was not the Superuser.
Association replacement on core process update has not been done correctly in some cases. This caused the core process update to fail.
"Overlay element/Undo overlay element" failed in some cases when "instant checkin" was enabled.
A process initially created by copying a core process lost all its index elements after the removal of the core process.
If elements of multiple core processes have been associated with each other, the following problem occured when these core processes have been integrated into another process: After the completion of all core process imports the remote associations of the process have not been replaced by local associations.
Process elements lost their master process identity when copying or editing and the process cms was enabled.
Core process protection was activated when a process element was modified in a process released as core process.
Existing permissions and role assignments have been displayed in the core process import report under the category "New permissions".
Umlauts were encoded as HTML entities which resulted in search not being able to find them.
Correction of html escaped entities in wysiwyg description fields.
Correction of html escaped umlauts in wysiwyg description fields.
German umlauts were broken in html templates.
MSPE-Webservice export could contain cycles.
Branch specification of CMS profiles was not respected by project data imports in some cases and the wong CMS profiles were assigned to the imported files.
Old project kit exports could not be imported when the exported process had the inconsistency "association with index pages".
Exception on RPlan export when not all phases had been selected for export.
In rare cases invalid XML was created in association elements of the process export file (process.xml).
Project specific import did not consider import option "Add new, replace existing" correctly.
Importing a ZIP export that was created from another baseline than the working revision failed for other users than "Superuser".
Same core process update could be triggered multiple times.
MS Project export failed if a remote element was assigned. Remote elements are now ignored.
Missing response headers caused proxy caching, e.g. when downloading runtime information.
MS Project export failed if a comment was assigned as predecessor or successor. Comments are now ignored.
HTML export did not work when HTTPS and tomcat/kerberos autologin was enabled.
The XML tree export could produce non-predefined entities which could not be processed by XML processors like Web browsers.
Setting new valid process version with copying the project data from the previous valid version or performing a project data import could cause unnecessary process element creations below "LOST+FOUND".
Simultaneous instantiation of a process model failed in some cases.
Overwrite option "Import missing" did not work for metric reports and collectors. Existing reports and collectors were always duplicated.
Fixed problem concerning overwrite settings of metric instances.
An empty file was already loaded in Import/Update process dialog.
Process version number was incorrect in HTML export when non-working revision version was exported.
MS Project export failed if comment only roles were tried to be exported (as resource groups).
Process import displayed warnings about missing lifecycle configurations named "".
The HTML export contained a wrong process version label.
Import option "Use heuristics" could not be deactivated.
The MSPE-Webservice exported resources for summary tasks. This cannot be handled by MS Project.
Update of processes (content import) or copying of project data from a previous valid process version (Stages 5.0 and above) could produce unintended process elements in the LOST + FOUND folder if elements with the same name existed in source process.
Default scope in reference model exports has not been exported correctly.
Very large files could not be imported.
Selecting no import file caused an exception.
Under certain circumstances the command line based process import did not delete all process versions of a project.
The command line based process import failed if the server Stages was running on could not build up a network connection for xml import file validation purposes.
Local Compliance Workbench scopes were missing in process exports. This caused their reimport to fail.
Aris import failed if it was not executed by the superuser.
In some cases Compliance Workbench default scopes have been published multiple times to the assigned processes during process import.
CMS profile name was not exported and imported.
CMS default profile flag was not exported and imported.
Importing old process exports did not assign correct CMS profiles to artifact instances.
Xml Export referenced unavailable dtd.
Import of a process with assignments of elements from another process failed in some cases when neither the project of the other process nor a project further above in the project hierarchy had the project group flag activated.
The option 'Store process description within a single transaction' is obsolete and has been removed.
Importing process elements from ZIP file that did not have a "timestampAsString" attribute threw exception with some databases.
Import functions were available in write-protected processes.
Process import failed due to error in recent enhancement 12078.
Could not import process with multiple reference models of the same name assigned.
When importing project-specific data the replacement of existing files did not work in the following case: For the imported file the reference to a physical file was specified by file name and file path (not by an url).
Could not import external reference associations and associations with custom rating or commentary attributes (used in Compliance Workbench).
Projects with '&'-characters in their names cannot be imported.
Process import failed in the following case: Elements of the process to be imported were associated with elements of another project and this project existed without having a process description, yet.
Fixed potential NPE in ZIP export
Process ZIP export is now always accessible with "Process Workbench" read privileges
ZIP import might contain cms configurations that are not valid on the importing system. These configurations are now ignored.
The export of a mapped reference model was not well-formed.
Enabling Process CMS for newly imported processes failed when the importing user was not the Superuser.
Process import of reference processes caused errors.
Importing processes with repository configurations was broken.
Export to MS Project was broken.
Association target elements could be found by their GUID that were not the current versions of the elements in the Process CMS. So the corresponding associations were not created correctly by the import.
Fixed process element state management in combination with process cms.
Security exception occurred when user did not have privileges to read role assignments and "showUsers" was set to "true" in "assoc" element.
"
<assoc ... showStatus="true"/> rendered </div> tag even in case of no files with status.
System associations now have their own common properties: tailoring dependencies, reference associations, working sets, corresponding elements.
Wrong property was used if a subtype was given the same name as the element type.
Multiple usage of the <userlevel> tag within an element view section caused exception.
CHECKEDOUT process version was displayed after initial process creation by import, process model instantiation or copying the process of another project. This must not happen because "automatic checkin" is enabled by default and so the CHECKEDOUT process version must not be visible.
Cancel button in delete process element dialog did not work.
Properties of checked out files could be edited.
Comments (arbitrary descriptions) created in the resource tab of documents (artifacts) were not listed as associated resources.
When copying a Guided Tour Stops, the associations to the corresponding elements were not created.
If a resource was copied after another process element which should be assigned to the resource, the assignment was not created.
Assigning a Guided Tour Stop and it's corresponding process element did not work properly if the guided tour stop was new.
Updating a guided tour stop assigned a second tour correspond instead of updating it.
Editing CMS resources via WebDAV had problems with refreshing the document.
Guided tour stop descriptions were displayed twice in resource view.
Image of an image resource could not be changed.
Ignoring tailoring queries and answers and HTML templates when checking for unused resources.
Deleting CMS configuration that was marked for use for resources was broken.
Conflict handling was not straight-forward in case of removal of a parent and adding of a child element.
Reset tailoring was not resetting the "tailored but kept in the process" elements correctly.
New tailoring model introduced in 15644 did not show tailoring info for pseudo elements and HTML export.
Tailoring of process elements is no longer implicitly granted by operation "M" of domain "Process Workbench". Tailoring requires permissions on domain "Process Tailoring" or domain "Process Tailoring (unrestricted)".
Process elements that have been tailored away were not shown as such elements.
Tailoring justification still has been displayed on process element pages after the tailoring of a process element has been revoked.
Display was not correctly updated after tailoring element.
Under certain circumstances multitailoring did not handle element hierarchies as specified.
Start the new multitailoring assistant after process instantiation instead of the old one.
"Delete invisible elements" should not delete core process elements.
Start the new multitailoring assistant after process instantiation instead of the old one.
Tailoring dependencies were not stored correctly.
Start rendering more than one diagram in the same millisecond failed.
URL could not be set for mock elements.
Comment only associations did not work in flow diagrams.
Visualization caused NullPointerException due to recent changes.
Project variables in the description of a reviewed project have not been displayed correctly on the review page.
Review registration failed if the current user was not allowed to read one of the milestones.
Review documents were not accessible if case sensitivity was wrong.
Review documents were not accessible if a cms problem occurred.
Review registration could be performed when a former review registration has not been finished yet. This could cause invalid registration results.
If a user sequentially registered more than one milestone in the same session, the proposed process version name and label was not updated.
Subversion: New versions had all labels of the previous versions (relevant for project review).
Subversion: Label creation in combination with the project review feature always caused new file versions to be committed.
Double submit of review registration from internet explorer 6 was not handled.
Under certain circumstances a blank page was shown in the main frame when executing a project review.
Review registration failed when files were managed by Subversion.
Files accessed by URLs instead of CMS profiles were not displayed for review.
Review-relevant and -irrelevant documents were not sorted. Now the sort order of the document index page is applied.
Filter containing a single quote did not work.
Add attachment did not work using internet explorer 6.
Request attributes of type "modifier" could not be filtered if the corresponding user name contained a comma.
Journaled attributes were not stored under certain circumstances.
Issue history is now exported in several rows.
Fixed unresolved property "request.error.required" for warnings about required attributes that have not been specified.
Fixed umlaut problem.
Under certain circumstances german umlauts have not been stored correctly.
Email notification templates were evaluated in context of the sender instead of the receiver.
Attachments could not be opened under certain circumstances.
Attachments could not be downloaded or deleted when using internet explorer 6.
Users with roles that are tailored away are now ignored in issue tracking.
Attachments of new requests could not be opened.
A user could not be assigned to an issue if his name contained a comma.
Add attachment link was present in request view popup and attachments could not be opened.
Change requests can now be created via the process workbench action menu. This did not work for process element overview pages without process workbench modify permissions.
Values in request history were not html escaped.
Request could not be modified if user had read, modify and delete permission.
Changing issue tracker configuration caused an error under some certain circumstances.
Icon to create new issues was not visible.
Request filter did not work if user language was german.
Selecting a project search result opened the "At a Glance" page instead of the "Process Workbench" of the corresponding project.
Advanced search index was not updated when an element name was changed.
Clicking on search hits of resources managed by a CMS led to HTTP 404 response or Exception, resp.
Optimized updating search index.
Search results showed JavaScript code and html tags were replaced by empty strings.
Search terms with german umlauts were not shown correctly after search in the search input field.
Search result contained outdated Wiki articles and Wiki categories.
Search did not work correctly on linux machines.
Improved combined representation of process type, process version and element state.
Finalized colors for process element state management.
UI was broken if configuration property "info.access.control.enabled" was enabled and user did not have privileges to access info page.
Improved terminology of process version dialog
TabSet (e.g. on edit pages for multilingual descriptions) is now multi-click-save
Radio buttons in "Import/update process"-form were not aligned correctly in FireFox.
Wiki start page did not show correct height in Firefox 3.
Unnecessarily displayed input field for description on process navigation (left side) on edit pages of Wiki and YP overview pages.
Using an external link to an element in the Wiki or the Yellow Pages when not logged-in led to an exception.
Improved permission check on Yellow Pages domain for user links on At a Glance and Process Workbench pages.
Overview of assigned users to a role could cause NullPointerException if one of the users got a Yellow Page profile.
The search in the Yellow Pages did not consider comment-only associations (arbitrary descriptions).
YpAttributes were not deleted if a corresponding Stages user was deleted who had no YP profile (i.e. corresponding Ypuser did not exist). This could result in getting an error message in the Stages search window on searching the Yellow Pages.
The Yellow Pages project now is considered in the popup windows of the WYSIWYG editor.
Instead of permisssion Modify, the presence of permission Create was checked on picture upload in a profile.
The Infocenter could not be displayed if users with a YP profile had created Infocenter entries and the viewing user had no permission on permission domain Yellow Pages.
Minor permission problem with the quick link to a user's profile on the YP overview page fixed.
Associations between Yellow Pages and Wiki have been displayed multiply if multiple versions of the associated Wiki element existed.
Print-views did not use the same base URI as other views. Now all views use the Stages root context path (default 'pkit') as base URI.
Importing hierarchical structures is now supported and can be modeled using the stages association type _parent and a targetRole attribute which can be either "parent" or "child". Example: <map-to-association type="_parent" targetRole="parent"/>.
Now able to use config properties in JavaScript code (e.g. for setting the IVIEW name for SAP Portal integration).
Additional information (user, ldap-provider) is logged in synchro.log if a retrieved ldap attribute (e.g. "mail") has no value.
Support LDAP group member retrieval. If the "groupMemberAttribute" attribute of the is set to "member" (or the respective name of the member attribute), a subquery is started for each member. Note: the LDAP "authenticationUsername" attribute must be defined, e.g. via '<ldap-attribute name="authenticationUsername" id="dn"/>'. Note: this operation mode this puts additionaly load onto the LDAP server.
Server now logs current working directory upon startup.
Login page now shows info if user need to login because of clicking on a direct link.
New Windows commandline tool "ListCheckouts" lists the files checked out by project kit with the corresponding sandbox locations. It can be used in the project kit directory in the following way: bin/listcheckouts <CMS type name>. The following CMS types are supported: ClearCase, CVS, MKS, PKitDB, PVCS, Synergy.
ClearCase: Synchronized view creation (mkview) and update (setcs).
Introduced utilility "duplicateReferenceMappings.bat" which helps to introduce new versions of reference models.
Links in PIID report are now labeled as "Process" (link to process description), "File" (link to CMS file) or "Info" (link to external URL).
Database cleanup script (ensureDatabaseIntegrity.bat) now removes target records referencing non-existent process elements.
Database upgrade logged non existing errors.
New message with property "downloadcenter.comment" is shown together with downloadcenter results if config property "downloadcenter.commentAbove" is set to "true".
Added functionality to attach external document libraries to artifacts.
Project variables of source project are now merged into target project when instantiating or copying a process.
Footer with copyright message is shown again if config property "global.footer.showFooter" is set to "true". The footer was removed in 4.0.
Infocenters can be exported and imported when user has maximum level creation privileges and configuration property "infocenter.export.enabled" is set to "true". WARNINGS: Exported Infocenter entries that are shown in multiple Infocenters are only imported into the current Infocenter. Users will not be notified per email about imported Infocenter entries.
Deleting all entries is now possible when displaying an Infocenter category.
Installer now finishes installation even when 'projectkit' or 'mysql' services refuse to start or 'updateModel' command could not be run.
"Delete All" button is only shown in process element state manager if the manager is started via the main menu.
Speedup of editing process elements for processes with many resources.
Process elements can be updated using the copy action even if the source element name has been changed in the meantime.
The process element status assistant can now be called for associated elements of a certain process element.
Process elements can be deleted using the process element status assistant.
Process element states can be configured to be changeable only manually.
The process element states are now displayed in "Copy element" and "Link element" dialogues. Additionally the process elements to be copied/linked can be selected by their state.
When modifying process elements, space characters at the start or end of the name are eliminated. Multiple spaces within element names are replaced by a single space.
tWiki-links to guided tour starts and guided tour elements are now properly supported.
File format icons can be shown for external links by setting config property "global.icondisplay.externalLinks" to "true". Example: "http://www.methodpark.com/guide.pdf" would be shown together with a "PDF" icon.
Process navigation can be configured to be shown above project navigation in Process Workbench by setting config property "process.navigation.portlet.position" to "top".
When TWiki link "
tWiki-links are not matched case sensitive when only one suitable link target exists.
Position of description on process navigation can now be configured by setting the "process.navigation.description.position" config porperty. Possible values are: "bottom" and "top" (default value: "bottom")
Added additional constraint check option "none".
Constraint check properties are now subtype specific if a constraint is also defined subtype specific.
Language icons for resources (e.g. templates, checklists) are now also displayed when listing them via "assoc"-tag.
When config property "process.element.display.suppressErrors" is set to "true", a "Suppress errors in process description" property can be enabled for a project. If this property is enabled, all linkage error messages (e.g. specifying [[xyz]] for non-existing xyz elements) are not shown and the "Analyse > Process Errors" menu is not shown
Introduced new create link in association view of process elements to quickly create a new association including its target in a single step.
Introduced notification system for process elements. project kit users may now subscribe e-mail notifications to get notified about changes of a specific process element. The subscription can be activated at the respective process element or in the user's notification settings.
New resource type 'HTML Template' introduced. This can be used to load predefined HTML pages in the new WYSIWYG editor.
Major enhancement: The process workbench now provides a WYSIWYG editor for process element, index and overview pages. The usage of the tWiki notation becomes obsolete (tWiki links are still supported). The WYSIWYG editor supports easy inserting and uploading of resources such as pictures or documents. For full display control HTML source code editing is supported.
Invalid links now provide a context menu to quickly create the referenced process element.
New process element type 'Annotation' with separate permission domain 'Annotations' introduced. This can be used to attach additional information (e.g. comments or discussions) to other process elements. To use annotations they have to be added to the metamodel as process element and associated with the desired process elements. Annotations provide a multiple associations view by using the metamodel element attribute 'appendMode'. Access to annotations is provided by a tab set on the associated process element page when privilege to permission domain 'Annotations' is granted.
Lifecycle management for process elements: - Process element state management can be enabled via "Edit > Properties" in process main menu. - Possible element states can be defined via config property "process.element.state.validStates" - Privileged element states can be defined via config property "process.element.state.privilegedStates". These states must also be defined in "process.element.state.validStates" first. Privileged states can only be assigned when user has the "Process Release" MODIFY privilege with the security level of the element. - The preconfigured states are "draft" (default), "review" and "released" (privileged). If other states are added, respective CSS entries for ".elementstate_STATEIDENT" styles must be added to custom.css. - Element states are shown on the normal element page. - Element states can be modified via the "Set state to" menu on the element page. - If elements are modified, their state is set to the default state (ususally "draft"). When associations between process elements are modified, this applies to all affected process elements. - A status report of all element states can be generated via the "State > State report" menu on the process main page. - A state management assistant can be started via "State > Start assistant for state > State" menu or via the state report. The state assistant starts a popup window allowing manipulation of multiple elements in a single operation. Every time the assistant shows an element, the respective element page is opened in the main window. This allows easy and fast process element reviews.
List of processes to be instantiated is now sorted by project path.
On process import, copying and instantiating, identities are only left unmodified for core and reference process elements. This is necessary to improve the precision of process update mechanisms. The option "Keep identity" in the process copy form is not available anymore.
Association dialogue can be opened for imported core process elements. Associations that are part of the core process are protected from change and deletion. Additional associations can be created, changed and deleted.
Resource assignment dialogue can be opened for imported core process elements. Assignments that are part of the core process are protected from change and deletion. Additional assignments can be created, changed and deleted.
Introduced first version of revision history for process elements. This can be enabled by adding the attribute 'versions' with value 'true' to the desired element tag in the metamodel.
The import of restricted relased process ZIP exports as core processes for existing process descriptions is now possible. This can be used for both: Initial import of a core process or update of a core process which is already part of the target project's process description.
Elements that do not support TWiki links are now excluded from list in WYSIWYG link dialog.
Reenabled warning messages in export dialog when user does not have read privileges for role assignments or permissions.
Added export id to xml tree export again for backward compatibility of external tools.
Process Export/Import uses guids now.
Display of remote associations can now be limited by setting the "process.element.display.associations.mode" config property: "all": show all associations (default) "suppressBetweenMetalevels": suppress remote associations between processes and models and vice versa "suppressBetweenModelAndProcess": suppress remote associations in process models when they link to processes
"
Guided Tour Stops and theirs corresponding process elements are now assigned via real associations.
Guided Tour corresponds can now be selected via selection dialog.
The page "Guided Tours" now illustrates the Guided Tour hierarchy by indenting each hierarchy level.
Speed up of generate resource overview with consistency check. URL checks can now be concurrently processed and a timeout can be configured by setting the config properties: process.check.urls.threads (default value: 20) process.check.urls.minThreadTimeout (default value: 60000)
Added URL field for resourcetype arbitrary file
Tailoring single elements with multitailoring system now works via action menu items instead of links near the element name.
Multitailoring report now contains justification for single element tailoring.
Multilevel/multidimensional tailoring - All new features are protected by license feature "ProcessWorkbenchMultiTailoring". - New resource types "tailoring query" and "tailoring answer" added. - Elements can now only be made dependent on tailoring answers in four alternatives: - answer applies, elements are contained in process - answer applies, elements are tailored away from process - answer does not apply, elements are contained in process - answer does not apply, elements are tailored away from process - Elements already handled by parent tailoring answers can be suppressed in dependency assignment dialog. - New tailoring assistant leads through the defined tailoring queries and tailors process according to the above dependencies. - New Excel tailoring report shows a matrix of tailoring queries and answers, the process elements and their relationships. - Old tailoring conditions can be converted to new tailoring queries via "Convert tailoring conditions" in process tailoring main menu.
Elements that have been tailored away can be deleted for speedup with "Delete invisible elements" in process tailoring main menu.
When config property "process.element.display.suppressInvisibleElementLinks" is set to "true", twiki links to elements that are tailored away are not shown at all instead of shown as striked out. This only takes effect when the user has NOT set the "Process Workbench" display setting "Process elements tailored away" to "show striked out". WARNING: setting this to "true" this might cause incomplete process descriptions if twiki links are used within normal text!
New Visualization Concept OrganicDiagramConcept available now.
SwimlaneDiagramConcept supports now edges across lanes.
Added new method to SwimlaneDiagramConcept: public boolean existsAssociation( PkitAssociation association, PkitElement sourcePhase).
Visualization component FlowDiagram concept now supports concept-parameter "GridDistance".
Changes in facade comment only association handling
Added action buttons for pasting as html, word or plaintext.
WYSIWYG editor toolbar is customizable by property
Combined drop-down control in WYSIWYG editor for format and style selection
Sort order of Wiki overview table changed. "Read count" and "Change date" are now sorted descending by default.
New constraint checks shows elements that have same names. Constraint checks now show element type and full name of element. To enable the check for a process type, add <global-constraint className="de.methodpark.pkit.process.constraintcheck.check.DuplicateElementsAnalyzer" /> to its "global-constraints" section in the PKitProcess.xml file.
Filter settings can now be saved project and user dependent. The filterable option default is now true.
Edit restrictions are now directly evaluated when changing a dependent attribute. Submitting the form is no longer required.
Annotation tab can now be customized via style sheet.
The actions menu is now structured by separators.
The files/resources tabset now displays the number of files and associated resources in brackets.
Default values for email notification are now taken from default user instead of using hardcoded values.
Wiki quickfilter allows partial word search using * on word start
New portal component 'Wiki' introduced (license feature). This is a platform for comprehensive management of knowledge throughout the whole company. All knowledge on process development can provided centrally and without redundancy.
New process element types 'Article' and 'Category' introduced, required for new project kit feature 'Wiki'.
ARIS import failed when using an oracle database, importing more than 1000 elements and deleting obsolete elements.
ARIS connector could not be imported if a comment attribute to be mapped could not be found.
The target role of imported associations was not set.
Added missing properties required for the FindPredecessorSuccessorTask.
Cancel button on aris import options page did not work.
ARIS content import did not invoke tasks and procedures for attributes.
Deleting multiple projects at the same time caused orcale dead lock.
User permission overview displayed source project name instead of target project as permission scope.
Script 'testConfig' for validating required properties adapted to metamodel-specific syntax.
User role list threw SecurityException when role was not readable.
Propagating changes in permissions did not work properly when modifying the target project of the permission and "full linking" was used.
Role overview did not contain full project path in permission display.
Creating mock elements might cause "Unable to create an URL" exception if URL property is not set.
Opening a process element from 'At a Glance', returning to 'At a Glance' and opening the same process element again caused the display of an empty page.
ClearCase: In some cases the created config specs could not load the latest file versions in branches.
Fix for 11131: Infinite loop could be caused.
Fix for 6181
MKS: Errors occured in version history and At a Glance page when a file to be displayed on these pages had no initial revision (1.1).
MKS: Files modified directly in the sandbox could not be checked out.
MKS: Failed to create multiple CMS profiles for the same MKS project.
CM Synergy: A NullPointerException could occur when determining version information in a Work Area where no release is configured.
Fixed synchronization problem that could cause the wrong cached information to be cleard after the execution of a modifying or updating project kit file action (e.g. checkin, refresh).
If a new cms configuration contained an error, the used database was Oracle and the option "use global predefined comments" was enbabled, an exception was thrown.
CVS: project kit did not handle the following CVS weakness: The checkout of a CVS module into a new sandbox causes the edit flags of the files in the module to be reset. Therefore project kit displayed the warning "Only locked in project kit by [...], not in CMS". Now project kit restores the edit flags when the files are being synchronized (e.g. by CMS Prefetch).
Using a former reference process as process model (i.e. instantiating that process) resulted in project kit 4.1 (not Stages) in inconsistent new process if other processes were assigned to the source process by Compliance Workbench.
Reference element assignments created by script "duplicateReferenceMappings.bat" have not been committed.
Database cleanup script (ensureDatabaseIntegrity.bat) now corrects comment only associations with missing target processes.
Document names in file tab on artifact pages were not escaped correctly.
Downloading files may add "-" chars to path.
Files containing '&' could not be downloaded
Users may now use new "click here for return to normal login" link when not being able to log in after direct link.
Stages server did not start if the config property help.anonymous.enabled was present. The system property help.selective.enabled is no longer supported and has been replaced by the config property global.help.enabled.
Metamodel tag <last-change/> has thrown SecurityException if user had no permission Read on domain Users.
Checking access on user level sometimes did not check security level which led to SecurityExceptions.
User did not see an understandable error message when an invalid value for property "cms.cache.maxWorkloadForPrefetchThread" has been specified in PKitConfig.xml.
Moved bugfix 11089 from 5.0 to 4.1 for displaying startup errors to the user.
Project variables are now also supported in URL resources.
In some cases, project kit jumped out of the IFRAME.
Adding arbitrary links to quicklist did not work for URLs with path after server name (e.g. "http://www.methodpark.com/products/projectkit").
Project navigation did not display all projects under some circumstances.
Set java parameter MaxPermSize to 512m.
project kit service startup parameters were cut away under some circumstances.
Creating a new metric element caused an exception if metric license feature was enabled.
Control characters of reports got lost when exporting them
Description only elements without a description could exist in the database.
Invalid description only elements were not completely recovered for linked elements with Stages version 4.1.29.0.
Coping a role copied permissions to the role to be copied.
Coping a role failed if users were assigned.
External reference associations and custom ratings from the Compliance Workbench have not been copied correctly by copy process elements function.
Linked process elements (shadows) sometimes could not be overwritten and updated by copy elements function.
Formatted link display names (e.g. bold style) have not been displayed correctly in the print view.
Umlauts in links to process elements have not been correctly displayed in the print view.
Element hierarchies were destroyed when copying elements with the "override" option set.
In some cases child elements had an empty subtype when they should have a subtype. This caused view problems when these elements were moved to the top of the hierarchy: The element description was invisible and some text properties were not displayed correctly.
Analyzing errors in process description caused exception.
"Check errors" popup opened links to index pages in popup instead of main window.
Empty abbreviations of process elements might lead to problems with name display in association lists or trees.
Resource elements did not have status management menu.
Twiki links to guided tour elements now also work correctly within image maps and have alt and title attributes.
Process element could not be deleted if it was associated with an element the user had no read permission for.
Merging variables when instantiating or copying process threw exception.
When editing links to anchors (via "#Anchorname"), the wrong css style was used.
Element links were broken by editing if element names contained space characters at start or end.
Modifying element states should only be possible when process can be modified.
Showing mailto links via
When multiple association comments were specified and the associations were shown in tree style, only the first comment was shown.
When association comments contain tWiki links with non-existing targets and the associations were shown in tree style, JavaScript code was shown instead of an error message.
Subelements could not be assigned to their parent elements.
HTML parsing sometimes broke customer JavaScript code.
Including a URL resource into a image map resulted in exception.
"noportal" display was broken for process main pages.
"Check process description" showed "mailto" links and relative links ("../bla") as inaccessible. They are now ignored if config property "process.check.urls.suppressMalformed" is set to "true".
tWiki-links matched the wrong elements in some cases because only the last part of the top level parent element's name in the given path was to match. Example: [[A|B]] matched element "SomethingA|B" when element "A|B" did not exist.
Dead tWiki links were not rendered correctly.
"Change" and "Reason" fields were not shown for artifacts.
Insert/edit link created inaccessible links if the project or process element name of the link target contained special characters like backslash.
WYSIWYG Editor did not consider horizontal rules created in tWIKI notation.
Fixed problem concerning the config property "process.element.display.suppressInvisibleElementLinks". "Null" was displayed instead of hiding the affected links.
Refix of: Deleting a project or a process did not delete history process elements.
Links to anchors ('#') were not resolved correctly due to recent changes.
Links in editor can cause problems when an internal line break is present
Old project kit search wrongly found workingsets.
tWiki Links in Guided Tour were broken.
Implicit links like www.methodpark.de in WYSIWYG descriptions did not work under some circumstances.
If property "process.element.display.suppressErrors" is set to "true" and project property "Suppress errors" is enabled, "Analyse > Process Errors" menu is suppressed and creating non-existing elements via popup menu is not possible.
Imported associations might become unmodifiable (restricted) while their source or target element was modifiable.
Only element states other than the current state can be set.
Annotations and Workingset elements are ignored by the assistant.
In the advanced settings of process elements now only those security labels are displayed for which the user has privilege to read and to modify or create, resp.
Filenames with "#" chars are supported now for downloading.
Case sensitive search was not always used when elements shall be found exactly for a certain name and path. For example this caused the failure to find tWIKI link targets when the path specified in the link existed more than once with different use of capital and small letters. A similar problem could occur in ARIS import: When there were two elements of the same type and with nearly identical names (e.g. "ELEMENT1" and "element1", both elements got the same resources assigned when they should be associated with different resources.
Core process export was broken: Exported core process items had the wrong identities. So elements of an integrated core process could not be updated with these exports.
A process created by an initial process import was "restricted released" (released as a core process) when the imported process was "restricted released". The new process shall not be released instead.
Superuser was not allowed to delete imported associations that were part of a core process.
Core Process update failed when an element to be updated has been renamed in the master process.
Importing a process containing core processes failed in Oracle because core process import timestamp could not be read.
When trying to insert a link to a file, the 'Insert link' button in the popup window of the WYSIWYG editor had no effect.
"nodisplay" and "noprint" areas were broken in WYSIWYG editor.
XML export could not be completed when any assigned reference model of the process to be exported was not readable.
Project specific import did not overwrite files.
tWiki-links to guided tour starts and guided tour are now shown as normal names in HTML export.
When importing ZIP process descriptions, element names with spaces are cleaned.
Web export contained "../.." or "\" style ZIP names under some circumstances.
Web export did not render all icon links correctly under some circumstances.
Web export showed hyperlinked files in document management tab with download menu instead of normal link.
Web export showed all links as "external" and opened content in new window.
Web export display of arbitrary description elements was shown as text without graphical frame.
When a resource was included via
Process export was not well-formed if process elements were not accessible under some circumstances.
Import report was not shown after project specific import.
Project specific import failed to handle child elements because the corresponding parent elements could not be assigned
Resource files with the same names and paths but different upper and lower case letters could exist in the ZIP-export of a process description (e.g. example.doc and example.DOC). This caused problems when the archive should be unzipped on a Windows system.
Importing linked resources did not work.
Attribute 'targetSubtype' could not be used in view-tag 'assoc' if also 'style="tree"' was used.
Metamodel specific names were not correctly used when creating a new process.
Double process elements are now properly eliminated again when merging two <assoc> collections. This also applies to assigned comments.
Creating new process elements via "
Nested <assoc> tags showed "
"assoc" tag threw NPE when "filterBy" set was empty.
Raw HTML code was displayed in the guided tour list.
Tailoring state was not considered in copy dialog.
Tailoring conditions were not properly sorted.
In some cases the selection of an element type was lost or got duplicated when editing a rule of a tailoring answer.
In some cases the tailoring dependent element type did not match the element type of the dependent element selection list.
Modifying tailoring questions did not update linked tailoring questions correctly under some circumstances.
Tailoring answers are now only found as "unused" if they do not have any process elements assigned.
"Resources" tab in artifact view showed wrong number of resources when resources were tailored away.
Copying or linking tailoring answers did not re-establish tailoring dependencies correctly.
Process element search now always ignores elements that are tailored away.
Tailoring domains did not show up in permission management if Multitailoring was enabled and normal tailoring was disabled.
Reset tailoring wrongly required modify permission for domain "Process Workbench".
Multitailoring assistant used wrong query path in some cases.
Editing multitailoring dependencies sometimes did not work properly.
NPE in multitailoring when tailoring toplevel elements to "visible".
Multitailoring did not find tailoring queries when elements are shadows.
Showing more than one diagram per page should work fine now.
Zoom icon for element visualisation should not be displayed when printing page.
Linking to projects did not work in web export
Swimlane lables were not shown in fullscreen mode.
Font color could not be set in swimlane diagrams
Visualization used up server memory
Visualization component caused display of pages without content
Facade classes ProcessElement, ProcessElementElement and ProjectElement do no longer allow to access the project kit internal classes Process, ProcessElement and Project due to security reasons.
Date was not written to the diagram.log.
Link in magnifier were broken.
Visualization did not render correctly when comment only associations were present
Visualization did not render correctly when mock-elements were used
Visualization were not always clickable.
Visualization rendering did not always work on multicore systems.
Visualization rendering was corrupted in HTML export.
Debug information was written to command line
Modifying elements in process model might reset tailoring status and lead to twiki linking problems if "fullLinking" is enabled.
Description errors were shown if links were pointing to non-readable elements.
Inserting links between brackets
URLs containing \ in descriptions and artifact instances were not accessible.
Usage of external images caused error in WYSIWYG editor.
It was possible to insert empty images into the description text.
Image uploaded in the WYSIWYG editor was not automatically selected after upload.
Imagemap was not stored in WYSIWYG editor on resource creation.
tWiki-URLs in commentar areas and inside tags were resolved.
Links to other project kit domains were not possible.
Links to process main pages were not possible.
The attribute stateEnabled was not existent and the attribute targetProcessIdentity was marked as required but is implied in pkit-process-tree_1_2.dtd, pkit-process-tree_1_2.xsd and pkit-data_1_2.dtd.
The attribute masterProcessIdentity was misspelled in some dtds.
WYSIWYG editor linking dialog showed wrong process element type names
WYSIWYG editor did not support short names in links
WYSIWYG editor table cell properties dialog was formatted wrongly
WYSIWYG editor table row properties dialog was formatted wrongly
WYSIWYG editor inserted "f" if CTRL+F was pressed
Assigning more than one arbitrary description to an association caused exception
Upgrade from version 3.0.x or 4.0.x to 4.1.2 caused reset of timestamps
Links to resources with URL caused dispaly errors when used in image maps
Link created with the WYSIWYG editor to the same project were referenced absolute, not relative
Image alt text was changed in WYSIWYG editor
Usage of noprint and nodisplay tags could result in description text loss
tWiki-Image links with name were not handled correctly
Icons for the process elements training, article, category and metric were not displayed in the index tree.
"file:\\xyz" and "\\xyz" URLs are handled as links in WYSIWYG editor
Creation of resources without description caused NullPointerException
Whitespaces in tWiki links caused linking errors
Umlauts in process element names caused linking errors
NullpointerException in Process Workbench occured if access to Wiki was limited.
Various WYSIWYG editor linking problems fixed
SortKey-Property for MockedElements was mandatory. Now if not defined, default is zero.
Security levels the user is not allowed to read, write or modify cannot be selected anymore.
Some characters were not correctly submitted.
New request icon was always visible even if the user had no create and modify privileges.
Direct links with filter settings and special characters like german umlauts did not work.
File url view link did not work.
Leading or trailing whitespaces of an issue id entered in the field ("Go to issue with ID") was not ignored.
When resources are found (e.g. templates, examples), the respective assigned process element (e.g. artifact) is shown as a hit, if it is located in the same process. This only applies if the user has no write access to the process description, because if write access is granted, the resource is directly shown as a hit.
Correct button labels in the create-link dialog in the WYSIWYG editor.
Web Export did not complete if some types of description errors occured.
Web export generated file tab on artifact pages even if process.export.artifactInstances.enabled was not set.
Some images were not included in Web Export.
Unreadable link targets caused error messages in web export.
Errors in Web Export, XML Export, Excel Export and Print View if annotations were configured and the user did not have read permissions for annotations. Now annotations are handled in the following way: 1. Web Export does not inlcude annotation overview page anymore. All annotation are exported anyway and are accessible if they are linked with another process element. 2. XML Export considers annotations. 3. Excel Export and Print View do no longer include annotations.
Links to index elements were broken.
HTML export failed if the exported process contained resources the user was not allowed to read.
The Wiki project now also can be set as home project.
"Read count" column in Wiki changed if a user read his own article.
Using a certain permission configuration a SecurityException could occur on logout.
Resource specific attributes can now be set.
Improved ARIS error handling.
LDAP synchronisation email notification now also contains list of users that could not be synchronized when maximumDeletionPercentage is exceeded.
Automatically login users via SPNEGO Single Sign On. See "LDAP and SSO guide" for more information how to configure this.
Do not show project state in At A Glance Quicklist anymore.
Possibility to filter the document instance versions displayed on the 'At a Glance' page
If a CMS prefetch pass is completed (no abnormal termination) and the update of certain documents failed, it sends a list of the affected documents to the administrator by email. When the problem is resolved the administrator receives also an email.
Introduced caching of revision information. This will improve performance especially on pages like "At a Glance", that list many files and file revision information.
On creation of the first version of a compound document instance, new versions of all other compound document instances with existing sandbox documents are created and get a unique label. This is necessary for being able to open the current compound document version later (e.g. on the version history page) after the creation of new compound document version.
Automatic labeling of compound documents in ClearCase on checkin
Automatic labeling of compound documents in CVS on checkin
Automatic labeling of compound documents in PKit CMS on checkin
CMS prefetch thread now also refreshes cached revision history information
Changed default value of PKitConfig.xml properties for the configuration of the CMS prefetch thread: cms.cache.lastAccessIntervalForActiveProjectsInDays=4; cms.cache.maxWorkloadForPrefetchThread=0.75
Changed sort sequence of Synergy document versions on 'Previous versions' page: The listing starts with the newest version and ends with the oldest version.
CMS labels are shown on 'Previous versions' page (except file is managed by CM Synergy)
Changed default value of PKitProcess.xml lifecycle attribute "forceNewVersions" to "true." Thus a new version of associated CMS documents is created on each state change.
Changed default value of PKitConfig.xml property "cms.comment.required.stateChange" to "true." The consequence is that a comment has to be entered on each document instance lifecycle state change.
Renamed mandatory scopes into required scopes. The required flag is now shown in reference model and scope selection.
Speed up database upgrade which is no longer performed within a single transaction.
Oracle statistics can now be regular computed. This feature should be activated if using oracle 9i and the Oracle Cost Based Optimizer (CBO). The feature can be configured using the following config properties: - database.compute.statistics.enabled - database.compute.statistics.method - database.compute.statistics.cronExpression
Updated Oracle JDBC driver to version 10.2.0.3
The project kit user guide is now available in English and can be found on the info page.
Changed symbol to signal that a file is checked out in the CMS but not by project kit. The normal lock symbol is used instead of the lock error symbol.
a temporary file version from the WebDAV store now is visible and can be opened on the version history page for the user who has created it.
When a user has checked out a file and saved a temporary file version to the WebDAV store, a '*' behind the version number on the document page will be displayed to him. He may edit, download or checkin this temporary file version.
Support infos do not include webdav folder anymore.
License agreement can be opened on info page.
Database adapters other than MySQL now need to have a license entry.
Tomcat has been upgraded to version 6
Removed project types organization and process. Now there are only projects.
Autoscroll to bottom after adding/deleting attachment or adding/deleting entry to other Infocenters.
Adding entries and marking all entries as visited is now also possible when displaying an Infocenter category.
When upgrading from project kit 3.x to 4.x custom folder 'local' and custom style file 'custom.css' are stored as local.pkit3 and custom.css.pkit3. Standard files are used instead.
Jar files named "pkit-ext-*.jar" in WEB-INF/lib are now preserved over upgrades. This allows extension packages (e.g. metamodel specific constraint checks) to survive upgrades.
Link for creation of new process elements requires now "create" permission only.
Associated elements can now be rearranged.
Changing the resource type does not delete associations anymore.
Added help for tailoring assistant.
Rearrange process elements now supports rearranging more than one process element at the same time.
Dynamic table of contents is not longer supported. (description.toc.disable)
After downloading a file via directlink, a new button allows managing the file directly. Additionally, the navigation and the breadcrumb shows the artifact where the file belongs to.
Beside use element also copy element is integrated in the drop down menu.
Create, checkout, checkin, cleanup and revert options for files are now hidden, when a lifecycle is used and the lifecycle is not defined in the metamodel (e.g. it has been renamed or deleted). In this way the occurence of subsequent errors is prevented. The problem can be solved by defining the used lifecycle in the metamodel or by assigning a valid (defined) lifecycle.
Elements can now be processed subtype specific in PKitProcess.xml with the <assoc> tag by specifying targetSubtype attribute.
Improved usability of process element assignment dialog.
Improved resource management: 1. All resources assigned to a process element are displayed on the process element page on the resource tab in a single list with their comment and last modification date. The assigned resources are sorted by type first and then by name. 2. The composed resource type 'Document template / Example document and Checklist' has been subdivided into corresponding resource types. 3. Prototype does not belong to the resource type arbitrary file any longer. It is treated as an own resource type. 4. The resource categories like 'Images', 'Document templates / Example documents', 'Guided Tour Stops' have been removed. All resources are now categorized by real process elements. 5. Checklists and internal checklists do not exclude each other anymore. 6. Internal checklists can be configured like all other resource types in the metamodel now. In order to use checklists and internal checklists the resource section should look like <resources> <types>internalchecklist checklist</types> </resources> The attribute 'checklistType' of the processtype metamodel element is obsolete. 7. Assigned internal checklists are not composed together anymore. Each internal checklist can be opened standalone. 8. The internal checklist setting 'common checklist' is no longer available. 9. Resources can be rearranged and the resource index page is editable now. 10. Resources are always displayed with their name. The config property process.resource.assignmentDisplay.fullname is obsolete. 11. A Guided Tour has to be modeled using the new resource type 'Guided Tour' and the corresponding stops as 'Guided Tour Stops'. A Tour Stop with enabled 'only contains subelements' option does no longer define a Guided Tour. 12. Classical Guided Tours (Tour Stops as top level process elements) are no longer supported. 13. Former process exports are importable and all resources are migrated automatically.
Elements specified by "a|b|c" notation in target links are now also matched by elements in sub-hierarchies (example: element "x > a > b > c" will match the above specification). To enfore top-level specifications, add "|" at the beginning of the path (example: "|a|b|c" will only match element "a > b > c").
Process element types do not have certain resource types assigned by default anymore.
Parent elements can now be processed in PKitProcess.xml with the <assoc> tag by specifying target attribute "parent". Example: <assoc target="parent" style="list"/>
Elements can now be sorted alphabetically by clicking the new "Alphabetically" button in the rearrange dialog.
MP internal: added order management
View sections in PKitProcess.xml file may now apply to multiple modes by specifying all modes separated by spaces (e.g. '<view mode="screen export">').
Process constraint check is now part of the normal Process Workbench license. Compliance Workbench license is not required anymore. Feature is now accessible through "Process" submenu on main process page options.
The export of a process description contains metamodel informations and display properties for external use.
Binary files with the same filename keep their extensions in the export of a process description.
Old versions of compound documents that have been checked in by project kit 4.0 are displayed and can be opened on the corresponding version history page.
Moved metamodel, process language and version settings to the new page 'change process'
Removed process element type directory.
Process element type names can be declared metamodel specific in the property files
Beside the custom rating a rating justification can be documented.
Artifacts are now also listed as an evidence in the piid report beside artifact instances (files).
Dates can be easily entered into a form field, by selecting it from a calendar popup window.
The actions menu will now stay open when clicking on a menu item with a submenu.
Improvement and restructuring of the menu and the wording of menu entries
After clicking the back link in the detailed view of an infocenter entry the user is redirected to the formerly visited category and not anymore to the beginning of the main page.
Mailto-links are now marked by icons
Added "select all" and "select none" icons in the process element assignment page.
The process language has been replaced by a project language. This language is used everywhere inside a project. Users may select the project language, browser language, german or english on their settings page. The default is the project language. New projects are going to be created in a default language which can be set via the configuration property 'default.language'. This property is also used to send email notifiactions if the user selected project language or browser language on the settings page.
Copyright infos for content removed from Info page. This was not used anyway and cluttered the Info page design.
Restyling of HTML installation menu
Changed position of External link and print icon from right to left
Removed Reset-Buttons in forms
Changed list headings of "At a glance" document list to the generally used expressions.
Exchanged process and project navigation
Attribute mapping rules below an object mapping rule were not considered
Invisible association occurrence may cause an exception
ARIS import could not be started under some circumstances.
Searching for an user threw an exception if the user performing the search had no read permission for the found users project. Those users are now filtered.
Privilege to read permissions did not allow user to access permission view pages.
Labels were not shown in role list of users.
Increased robustness when sending emails to users.
Creating users without role assignment privs may cause exception
Term 'document' was not completely replaced by 'file' on the At a Glance page.
Label filter caused a javascript error if a cms error occurred.
An error occured when trying to open a search result that led to an At a Glance page of a project and no At a Glance page has been visited before during the user session.
Sporadically the error "no current permission manager" occured on reload of the At a Glance page.
MKS: Failed to import subsandboxes for certain subprojects into existing sandbox.
Locked files for a certain CMS profile have been determined wrong in a special case. This problem might only occur when a CMS profile was saved. It caused the mistakenly denial to save the CMS profile because of locked files.
Version history displayed checkin date in wrong language format under some circumstances.
PVCS: NullPointerException was displayed in 'At a glance' and document pages when a file had version labels assigned that were floating with the tip revision and additionally the file had no non-floating version labels assigned.
ClearCase: File error "Only locked in project kit by
ClearCase: Label creation for compound documents failed. Compound document files could not be checked in.
ClearCase: View storage directory configured with vws option was not used.
CM Synergy: Refreshing a file did not update/delete the corresponding cached information if the work area file was writeable.
Error messages on CMS error pages displayed HTML <br/> tags in plaintext.
Version numbers of compound documents have been listed in ascending order on version history page but should be listed in descending order.
Older file versions from project kit CMS could not be opened.
CMS command invocations that only needed to affect the cached information for one sandbox deleted all CMS caches.
Errors found in validation of CMS profiles have not been displayed to the user.
Refresh button did not refresh contents.
Organization-wide Gap Analysis calculated an incorrect rating under some circumstances.
Scope could not be created when reference model is write protected
Database upgrade did not work if there was a top level resource named 'Guided Tour' present.
"devFlag" is now automatically cleared when upgrading to project kit 4.0
Element folders (pseudo elements) could be found in Downloadcenter.
Could not open MS-Office-files in WebDAV-Mode when there were '+'-characters in the file names.
Download function for files did not download temporary file versions from the WebDAV store for the users that have created them.
Copying a file (artifact instance) deleted the corresponding temporary file in the WebDAV folder. So changes to a file that have not been checked in yet could be lost.
Checked out file can neither be checked in nor be reverted when a lifecycle is configured that does not (anymore) exist in the used metamodel.
An unknown error occurred if license has expired.
Customer specific contents were not displayed on the info page anymore.
Users without project navigation privilege could not log in.
Quicklist portlet did not have vertical spacing below.
Description field was marked as "required" even if attachment was provided.
Infocenter categories showed up as links with Firefox.
Backup does not use temporary directory as default anymore. As default directory C:\backup\projectkit is used.
project kit could not be installed on windows 2000 systems because of the number of characters that may be used in the command line.
project kit could not be installed on windows servers missing msvcr71.dll in the system32 folder.
Clicking save button on element assignment page several times assigned elements more than once.
Process element description popup was not completely translated.
Reference models in the Compliance Workbench used metamodel specific process element type names from the process instead of the reference model.
Assigning a process element caused a security exception when the user was not allowed to modify the target process element.
Rearranging associated resources did not have any effect.
Linking a process element without its parent element did not work and might duplicate the source element.
Resource tab was not visible under some circumstances.
Copy process element linked the element instead of copying it.
Name field in resource edit form was not marked as required.
Web export breadcrumb on index pages is now compatible to online version.
Web export now only contains used resources, but resources may now be located in others processes.
Web export contained broken links when referencing resources via "<assoc>" tag or when referencing elements in association comments via "[[..]]".
Deleting a process element with successor predecessor relationships did not deleted all dependent associations.
Document process changes recorded assignment changes incorrect.
Persons to notify did not show any person if there was only one person to notify.
Breadcrumb did not show process element index.
Breadcrumb was broken when changing project.
Tailoring assistant leaves wrong breadcrumb.
If no associated elements were found the text 'none' has not been printed in a separate line.
Highlighting in the process navigation was broken for process element index.
Process interfaces were not correctly displayed in analysis if association type was empty.
Creating sub-project directly below root project fails with error message if user does not have the correct privileges.
Modifying linked elements might throw Security Exception under some circumstances.
Some element attributes were not correctly copied when transforming a linked element into a copy.
'to the beginning' and 'to the end' on the rearrange process elements page didn't work.
Do not generate location information for element pages when in "noportal" mode
<assoc> with target "parent" or "children" erroneously renders "[Change]" link
Wrong colspan in file tab of document and version history table when no lifecycle has been activated
Resource migration deleted tailoring dependencies.
Child elements were shown incorrectly in tailoring list if parent was tailored away.
Pseudo elements were shown incorrectly in tailoring list.
Action menu used 'new element', 'use element', 'rearrange elements', ... instead of 'new activity', 'use activity', 'rearrange activities'.
Click on document type icon destroyed document tree.
Fixed display of file lists on document pages in Web Export.
Compound document file names and option menues were missing in Firefox.
Compound document functionality did not work.
If file creation was not allowed to a user by a product lifecycle, the file create option was offered nevertheless.
Removed Javascript error when opening the guided tour
Tailored resources are now shown striked out if set so in settings.
Security labels are now completely removable
Process Export of description only elements does not contain attributes "targetProjectName" and "targetElementNameProces" anymore.
Message about the non-support of compound documents was displayed for every document (even for non-compound-documents) when the browser was not Microsoft Internet Explorer.
Corrected sequence of setting locker id and creating WebDAV name
Editing a typed commentary caused an error under some circumstances.
The context menu entries 'Edit Properties' and 'Cancel Assingments' did not work when assigning reference elements using Internet Explorer 6.
Tabsets in Compliance Workbench did not use 100% height using the FireFox browser.
Not all external mappings were listed in PIID report.
PIID report could not be opened with Internet Explorer using Excel 2003 when connected via https.
An external link to unconfigured Request Tracker caused an exception.
External links including filter settings could not be generated when selected filter criteria contained a single quotation mark (').
The usability of exporting issues was improved. The template selection was also integrated in the drop down menu.
Link for viewing associated issues did not work.
If files had lifecycles configured but no lifecycles were defined in the metamodel anymore, the file rows on the document pages were not correctly displayed.
Users with modify rights for the Process Workbench domain did not see the write-protection-icon on the Process Workbench main page.
The filter in the file tab of the 'At a glance' page generated no message when there were no results for the given filter criteria.
In the export process explanation unsuitable button names were used.
Scrolling on the login and project selection page is now possible.
Empty subtypes might show unwanted messages, e.g. in process navigation.
When using the slider the grey lines in the portlet headers in the left navigation did not scale.
Reduced line spacing and padding for descriptions displayed in the process portlet in the left navigation
When viewing an element list, the breadcrumb navigation in the header was not entirely clickable.
Checkin textarea for comments was enlarged.
Input fields in the infocenter marked as required had different star-icons.
Line-breaks in twiki-description did not work anymore.
The back button on the first screen of the tailoring assistant and the forward button on its last screen was removed.