Traction® TeamPage 6.2.39 includes a round of improvements to the Signature Requirements module, and a small set of bug fixes, including a bug introduced in TeamPage 6.2.37 which could in certain cases cause TeamPage to fail to process incoming content and cause journal data corruption. Customers currently using TeamPage version 6.2.37 or 6.2.38 are advised to upgrade to this new version as soon as possible. Please read on for the full list of changes.
• Fixed a bug introduced in TeamPage 6.2.37 which could, in certain cases, cause TeamPage to fail to process incoming content, such as incoming email message content, and the content of other new entries or updates to existing entries. The issue could lead to TeamPage journal data corruption. Please upgrade from 6.2.37 or 6.2.38 as soon as possible. (Server92761)
Work in Progress
In a recent version of TeamPage, the way that Work in Progress ("Private Draft") data are stored and retrieved was changed to improve performance. This was a particularly important change for certain TeamPage use-cases which commonly involve very large articles, and corresponding very large Work in Progress records. This release includes a fix for some issues that some customers experienced related to this migration process.
• Fixed a bug that could prevent the Work in Progress migration from completing properly. This would prevent TeamPage from starting up on the first attempt to launch after upgrading between certain combinations of versions. Subsequent attempts to start TeamPage would work fine, but the the content of users' existing Work in Progress would not be available, even though the data were not lost. This migration issue has been fixed: TeamPage server startup will now complete normally when applying a Work in Progress data migration; and the full content of all Work in Progress records will be accessible. (Server92604 / Server92525)
Email Ingestion
• Fixed a bug that could cause certain kinds of unexpected configuration problems to stop TeamPage's background email processing altogether. This would prevent any mailboxes from being read until the mailbox connection properties were corrected and the TeamPage service was restarted. (Server92605)
• Fixed the way that certain invalid or mailbox connection properties are handled in the most graceful possible fashion. In some cases, TeamPage can apply heuristics to determine the intended correct property value, and will still be able to connect to the target mailbox; and in other cases, TeamPage will now log more helpful diagnostic information so that the problems can be addressed by an administrator, or with the help of Traction TeamPage support staff. (Server92606)
Query Results
Three issues have been fixed related to TeamPage's "native" queries (as opposed to queries using the Advanced Search module).
• Fixed a bug that could prevent certain kinds of queries from working properly when certain combinations of search expressions using "AND" or "OR" operators is present. (Server92517)
• Fixed a bug that in some cases could cause the last result in a "chunk" of paged results to be repeated in the next chunk. (Server92690)
• Fixed a bug that could, in some cases in which fulltext or tag search terms were present, cause results to be returned that were not from the requested space or spaces. (Server92744)
Other
• Fixed a bug that could, in certain rare cases, cause the spaces created using an existing space as a template (instead of using an already saved space template) to include copies of system tags and certain configuration properties that should not be copied. (Server92730)
• Improved the error messages displayed to users when external search engine queries fail. Previously, many error messages were vague and unhelpful, and failed to give the user some idea of whether the error was something which might require the intervention of an administrator to resolve. Also, in some cases, error messages might have included identifying information about the external search engine (such as its IP address or host name). These issues have all been resolved. Diagnostic logging of the underlying errors has also been improved, including ensuring that the logged messages have been distilled to a suitable format while still retaining enough detail to assist administrators or Traction TeamPage support staff in diagnosing issues. (Solr1230)
Improvements
Signature Requirements Module
This release includes some small but helpful improvements to the Signature Requirements module.
• Added a space setting allowing administrators to designate a group to be filled into the Supervisors field by default when creating a new Signature Requirement for an entry in that space. Also, if no default has been designated, the user creating the new Signature Requirement will be added to the Supervisors field by default instead. (Proteus16068)
• Added a new "Signature Requirements" group to the Filter menu, and support for filtering signature requirement entries by the supervising user or the type of requirement. (Proteus16086)
• Added the list of users who are supervisors to the display of both Signature Requirement entries and Signature entries. (Server92424)
• Added a column to the server-level (all spaces) Signatures tab that displays the space of each signature, and allows filtering by that space. (Server92426)
General
• Improved the performance of several of TeamPage's most commonly used text transformation and cleanup capabilities. These improvements will be most noticeable in environments in which, for example, users often create entries with a large amount of content.
• Changed the default behavior for the user menu in the Proteus skin so that the status update panel always appears regardless of whether the user's account has a valid designated default space for status updates. The status panel includes as many as 3 of the user's most recently created non-reply status updates, plus a mini-form for posting a new status update. (Proteus16061)
