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 too many improvements in this release of TeamPage to describe each of them in detail, but this article covers the most important changes. 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.



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