Title: TeamPage 7.0

Welcome to TeamPage 7.0! This is a very important release for TeamPage customers and Traction Software. TeamPage 7.0 includes a deep refresh and review of core TeamPage components as well as major updates to foundational Java, Solar search, Jetty, Microsoft Entra ID and other libraries. Elements of this release have been planned, implemented, and production tested in Traction Software Support and other servers over the past year. There are many changes, large and small; here are a few highlights:



Please read on for further details. See the Upgrading section below for TeamPage Cloud and on premises TeamPage upgrade information.

Download TeamPage 7.0 (7.0.17)




Upgrading



Traction TeamPage Cloud hosted customers don't need to do anything: most TeamPage Cloud customers have already been updated to TeamPage 7.0 and Solr 9. The remaining TeamPage Cloud customers will be updated over the next two weeks to limit Solr 9 re-indexing delays. Please post any customer specific questions or requests to your customer support space on this TeamPage server. We will contact customers with dedicated TeamPage Cloud servers or other special configurations individually to plan your update. TeamPage 7.0 includes all improvements and bug fixes released since Customer5625: TeamPage 6.2.76.

Customers who host their own TeamPage deployments should read Customer5586 before upgrading, and upgrade to TeamPage 7 from earlier versions as soon as it is convenient. If you are using Apache Solr with TeamPage's Advanced Search module, please note that you must update your Solr installation concurrently, see Upgrade Guide. TeamPage 7.0 requires Solr 9.x, and a new Solr installation is required; your existing Solr installation can be moved aside and eventually deleted. Other than critical patches selected by Traction Software, the new baseline for TeamPage software maintenance is TeamPage 7.0.

Software Component Updates



Several of the key components that TeamPage uses have been updated to newer versions. Here are the most important.

Java 21



For a long time, TeamPage used Java 8 (1.8). Migrating TeamPage to Java 21 is the most important individual upgrade in TeamPage 7. This updated version of Java means that TeamPage benefits from all the improvements to the Java architecture and newer JVMs, including better memory management, improved performance, and increased security.

Jetty 10



TeamPage now uses a newer version of the Jetty web server. This new version incorporates many improvements over the old version, including many related to security, such as support for SNI, and first-class support for the HTTP-only and SameSite cookie attributes.

Apache Solr 9



TeamPage's Advanced Search module now supports (and requires) Apache Solr 9 or later instead of Solr 6.x. Solr data from version 6.x is not compatible with version 9.x. Therefore, this version of TeamPage and Solr will require re-feeding your TeamPage documents to a new Solr installation. Improvements include:

- Improved document duplication detection. Duplication works in four possible modes depending on what sort of document is being indexed: unique mode for entries (which are never considered duplicates); fuzzy text matching, for other documents that contain text; exact matching, for files types like images and other binary types for which exact duplicate detection is most meaningful; and configurable custom content hash matching, which supports specifying the fields to use to calculate the hash.

- TeamPage supports configuration a connection to Solr using SSL/TLS, and specifying credentials to authenticate. Customers using Solr with TeamPage are strongly encouraged to follow the instructions linked from the Solr Search support area to enable and make the best use of these features.

- TeamPage 7's search engine index administration UI has been simplified and improved. (See below.)

Microsoft Azure AD / Entra ID



The Microsoft Graph Client and other embedded libraries that TeamPage uses to support Microsoft Azure AD / Entra ID have been updated. These newer versions offer improved performance, and work better with Microsoft's current cloud directory services.

TeamPage Updates and Improvements



Entry Previews



The "Preview" button now appears in forms that support it, such as TeamPage's built-in Article, Task, Project, Milestone, and Event forms. This allows users to see what an entry will look like after it's been saved.

Status Updates



TeamPage's Status Updates page has been given a behind-the-scenes overhaul. It now operates much more efficiently, and with fewer quirks. For example, media embedded in the page can be played without having it interrupted when the page view is updated. Users can also choose whether to have updates applied to the view automatically (the default), or whether instead to receive a notification when updates are available with a link to click to load them on demand.

External Search Engine Index Integration with Improved Support for Draft and Published Entries



The index administration setup interface has been revamped to make it easier to use. It also supports locking admin operations to avoid inadvertent changes.

The search engine index synchronization process has also been improved. This includes some fixes for some issues that could prevent the index being properly kept up to date when published and draft versions of entries are both in circulation, and overall support for published vs. draft indexing and searching has been greatly improved.

TeamPage also now supports designating a maximum age for documents to be added to the external search engine index, which can be useful in environments in which older documents are not relevant to end users searching.

Query Performance Improvements for Faster Dashboards



Searches for "native" TeamPage queries that include scoping to the title or a particular paragraph -- e.g., i(n(0) and c(foo)) (i.e., "the title contains the text foo") -- now operate more efficiently, particularly with search expressions involving full-text search terms. This is a common type of query for both customizations and built-in features, often used in dashboards and other pages.

Type-Ahead Suggestion Improvements



Performance of TeamPage's "unified search" feature has been improved. This will improve performance in the many places where unified search is used to provide type-ahead suggestions: the search box at the top of every page; the search box at the top of setup pages; form fields for email addresses, users, special types of entries; and more.

In many cases, performance of the underlying queries has been improved. Besides this, queries targeting entries (tasks, projects, articles, etc.) now always make use of the external search engine when the Advanced Search module is available.

The scoring that is used to rank results from these queries has been greatly improved, both in terms of performance and behavior. The most relevant results need to appear first, but other results that supply suggestions based on fuzzy or otherwise imperfect query matching are also important, since everyone makes typing mistakes from time to time, and even more often on mobile devices.

Customizable Policy for Automatically Capturing External Resources



TeamPage now offers configurable support for automatically capturing external resources to be attached to content entries. This includes those that may be referenced by URL in the src= attribute of IMG tags in the content of the entry. New settings under server settings > Network > Outgoing HTTP Requests > Automatically Captured Resources allow administrators to customize the policy applied to determine whether such an automatic capture request will be allowed, and/or in what situations.

Only fully qualified HTTP and HTTPS URLs are eligible to be automatically captured. Also, TeamPage will never automatically capture URLs that have a host component that is any of the following: a loopback address; any known host name or IP address that refers to the TeamPage host server itself; unqualified host names; host names that belong to "testing" domains (e.g., example.com); or a multicast IP address. But the settings allow further customization of whether TeamPage should allow requests for automatic capture.

Administrators are encouraged to make use of these settings, but should keep in mind they apply to requests being made for the purpose of automatically capturing embedded resources. To apply custom filtering for all outgoing HTTP requests made by TeamPage, instead consider using the existing support for a proxy server.

WebP and HEIF Images



TeamPage now has support for the WebP and HEIF image formats. Specifically, images using these formats can at least embedded in content, and that TeamPage supports determining their dimensions and other metadata, just as with other standard image formats.

Please note that although the TeamPage server supports these formats in addition to other common formats, it is important to make sure users' browsers also support a particular format before adopting it in wide usage. In the case of .heic and .heif files, for example, only the Safari browser currently has native support. (See this page for details.)

User and Space List Export



TeamPage's server settings > People and Spaces pages now offer administrators a way to export a lists of users or spaces. This was a common request, and formerly may have required a custom plug-in or other modification. The links appear under server settings > People > Browse and server settings > Spaces > Browse, respectively. Simple HTML and CSV formats are available.

Performance Logging



TeamPage's internal JMX-based performance monitoring framework now also includes logging (to traction.log or debug.log) of operations, queries or other things that take "too long" based on reasonable and general assumptions about performance. This can be helpful when attempting to diagnose possible performance issues.

For Developers



HTTP Client APIs



TeamPage's com.traction.sdk.util.httpclient package and associated APIs have been extensively updated and improved, and an SDL tag set supports customizations that make use of this from SDL. We'll soon have a separate article describing the details of these capabilities and some examples of how to use them.

Other Issue / Bug Fixes



• Fixed a bug that could prevent certain PDF export operations from working correctly. The error message reported in this case was "java.lang.IllegalArgumentException: Only non-null Positions with an index can be checked" (Server94098)

• Fixed a bug that prevented folder/file descriptions from being displayed properly in single folder/file views. (Proteus17901)

• Fixed the file name used for files that are automatically downloaded and attached to an entry when the request required to retrieve the file involved an HTTP redirect. The file name used in this case will now be based upon the redirect URL rather than the originally requested URL, if possible. (Server100076)

• Fixed a bug that could prevent a user's custom subject and body from being included as expected in an email message created with the Email Articles feature, when the "Log Message Content" option was not selected. (Server98619)

• Fixed a mistake in TeamPage's localized admin resources that prevented the full text of the tip text for the "Include in External Search Engine Indices" space setting from being displayed. (Server100523)

• Updates to status update views no longer interrupt or otherwise interfere with video and audio playback, or other interactive elements that appear in user authored content. (Proteus8380)

• In the Status page, the highlighted background of newly created status updates now correctly automatically fades when the containing window or tab still has focus, without having to switch to another window or tab and back again. (Proteus18009)

• Fixed a bug that could prevent the correct set of results from being displayed for certain TeamPage native queries involving multiple conditions joined by "OR". (Server101028)

• Fixed a longstanding issue / limitation that prevented log files from being accessible when TeamPage's logs folder is symlinked to another disk volume. (Server101483)

• Fixed a bug that caused some parts of TeamPage's section editor interface to be displayed with incorrect or redundant label text in certain cases, such as when selecting "Tasks" or "Events" for the section's type. (Server102117)

• Fixed some minor alignment/margin with the icons used for entries and other documents appearing in feed views. (Proteus18717)

• Fixed an issue that prevented TeamPage's administrator-configured time zone from being correctly used when applying the log file rotation schedule. This is a relatively minor issue, but could cause some confusion for administrators who have set a different server level default time zone to the default from the host operating environment, which would usually only happen if the host machine is located in time zone other than the main one for the servers administrators or user base (Server101507)

• Fixed -- hopefully once and for all -- some issues that could prevent the proper operation of the Proteus skin's stylesheet customization dialog (Setup > Design | Customize). These issues could, in certain circumstances, cause problems editing or deleting draft stylesheets, and other problems. (Proteus18669)

• Fixed a bug that prevented differences in certain fields, such as task start date and due date, from being reflected in the compact diff rendering used when a feed view displays an update to an entry that included modifying one of those fields. (Proteus18679)

• Fixed a bug that could prevent the correct types of entries from being displayed in a User Profile > Activity > Feed view. In particular, even when unchecking all checkboxes in the "Filter by Type" control, not all types of entries would appear. The view now correctly displays the selected types of entries -- or, when no entries are selected, all types of entries. (Proteus18722)

• Fixed an issue that could cause URLs generated for single entry views to be wrong in certain cases. (Server101623)

• Fixed an issue that prevented date range navigation from working properly when viewing a section table. (Server102270)

• Fixed an issue which might, in certain special cases, prevent a generated digest from being sent to the user as expected. (Server102692)

• Fixed an issue that could, in certain very rare circumstances related to a damaged TeamPage installation, cause TeamPage to report that a metadata index rebuild process had succeeded when it had actually failed due to an unrecoverable error (usually missing libraries or other components, a problem solved by re-installing to fix the damaged installation). (Server102816)

Other Improvements



• The Trust Store Manager, which is used to manager server keys and certificates for SSL/TLS (HTTPS), as well as managing which certificates retrieved from external sources are considered trusted vs. untrusted, can now be accessed without a current journal. This can be helpful for administrators trying to diagnose and resolve issues related to certificates -- e.g., in case SSL/TLS is not configured properly, but the current TeamPage journal is configured for authentication against an external directory service that require HTTPS. (Server101169)

• A color selected by a user for an event, task, project or milestone will now appear at the right edge of the entry's block in worklist views. (Proteus18707)

• Improved the appearance and visibility of the Location event entry field. (Proteus18667)

• Improved TeamPage's UI responsiveness to dragging and dropping things like titles and Traction IDs as they appear in various places. Dragging and dropping an entry title, for example, out of TeamPage and into another application should now work predictably and produce the expected result (e.g., that the entry title text appears where the title was dropped). (Proteus18071)

• Improved the positioning and alignment in the display of task entry data such as assignees, priority, and due date. (Proteus17770)

• Modified TeamPage's rich text editor setup (powered by TinyMCE) to remove the default width of 100% that was previously being applied to all tables created via the table insertion controls. This was causing various issues, including preventing custom table column widths from being properly reflected in TeamPage's interface after saving the containing entry. (Server92778)

• Improved the error messages reported back to users in the case of failed file download requests. The error messages were previously generic and unhelpful, and didn't always include the correct HTTP response status code. (Server101171)

• Fixed an issue in TeamPage's very minimal and rarely used "Simple Skin" that prevented certain types of entries from being displayed correctly in advanced search views. (Server101155)

• Modified TeamPage's handling of requests it considers to originate from a "bot" to avoid creating a persistent session. Most bots ignore sessions, and particularly for publicly facing servers, which may be subject to automated requests for search engine indexing or other content scraping, it doesn't make sense to create persistent sessions. Administrators that need to disable this behavior can shut down TeamPage and add the line session_robots_allow=true to Traction.properties, and then start TeamPage again. (Server102907)

• Improved the way TeamPage interfaces with logging performed by the SLF4J library, which is used in various software components that can be used (either as part of the core product, or as part of optional plug-ins) in TeamPage. Log levels are now handled in a way that is consistent with the equivalent levels in TeamPage. Developers who want to enable finer log levels that are otherwise ignored by default can shut down TeamPage and add the line debug_detailed=true to Traction.properties, and then start TeamPage again. (Server102941)

• The statistics TeamPage collects via JMX now includes information on JDBC connections, including connection pools. (Server102920)

• Changes made to the JDBC settings used for TeamPage's auxiliary data store now take effect the next time TeamPage is restarted. Previously, some changes may have been applied immediately, which in certain cases, could cause problems for internal components that use the auxiliary data store. See Customer2050. (Server97647)

• Simplified built-in support for various user agents (browsers). Support for Chrome, Edge, Firefox and Safari have all been consolidated, and special handling for very old versions of those browsers has been removed. Support for rich text editing and uploading files in TeamPage forms has been added for all modern browsers, including mobile versions. Note that in keeping with industry trends, and Microsoft's own product support, Internet Explorer is no longer supported in TeamPage 7.0: it may continue to work, but its use is strongly discouraged; and users who encounter problems should switch to a modern fully supported browser. (Server102823 / Proteus19008 / Proteus19007)

• Improved error reporting in the Advanced Search Index Administration interface so that the administrator has enough information to be able to resolve the underlying problem without having to inspect a log file. This includes reporting the error message that came from the search service, along with the associated HTTP response code (if available). (Server102706)



Attachments:
teampage_logo.jpg
Related Articles
references (1)
Customer5625: TeamPage 6.2.76
Article: Customer5636 (permalink)
Categories: :Doc:changelog, :Doc:r70
Date: June 29, 2025; 3:19:41 PM Eastern Daylight Time

Author Name: Dave Shepperton
Author ID: shep