Issues resolved in TeamForge 17.1

Here's a list of few noteworthy issues fixed in TeamForge 17.1.

Some of the issues fixed in TeamForge 17.1 have been delievered with TeamForge 16.10 Update 1 in advance and therefore not listed here.

• An issue that caused the "maximum open cursor exceeded" exception (on Oracle) has been resolved.
• Fixed an issue with ETL processing that did not allow special characters in text flex field values.
• A "Jump to ID" search for an object that's not covered by the scope of the license owned by a user throws the "Permission Denied" error as expected.
• Fixed a page break issue that caused artifacts with lengthy description to have the description printed on a new page.
• Fixed an issue that prevented inline editing of flex field if the field name includes a colon (":").
• Document sub folder access permissions were lost inadvertently once you view the Document permissions and click Save without any changes. This is now resolved.
• Deleting and adding tracker workflow transitions, if done in a single edit operation exactly in that order, fails to delete the workflow transitions, which is now fixed.
• A user's full name, if consists of special characters, is not displayed properly in the Assigned To field, which is now fixed.
• Team and AutoSummingPoint (Calculate Points) are now part of TeamForge artifact update events.
• Usage of special characters such as hyphen (for example, DATABASE_USERNAME=sf-admin) is now allowed for TeamForge DATABASE site-options.conf tokens.