This version of Traction® TeamPage is focused on bug fixes, with a small set of updates and improvements for TeamPage's web-based Document Management views, as well as the Social Enterprise Web (SEW) features related to documents managed within TeamPage.
TeamPage now supports a single document view, like the existing Documents view, but focused on a single file rather than a folder. All the usual operations for a file can be accessed directly from within this page by users with the appropriate permissions. Customers licensed for Attivio Search and who are running Attivio AIE 3.5 will see the same document preview they would see in an expanded Attivio search result.
The details of the file or folder being viewed are now displayed prominently near the top of the center column of the page. For folder views, the UI for showing the expanded details or single document for an individual file or subfolder is now much clearer.
Social Enterprise Web (SEW) Enhancements for Documents Views
SEW features involving files and folders in TeamPage's file repository are now available directly from any folder or single document view. Customers licensed to use SEW will now see a "Describe This Folder" / "Describe This File" button in the side column of any Documents view for any folder associated with a single space (e.g., the space's share folder, or an attachment), and will see the hover menu offering the "comment," "tag," "task" and "share" actions that were previously only available for individual files returned in Attivio search results, allowing customers licensed for SEW to access all these operations without also having to be licensed for the Attivio Search module.
In a folder view, expanded details of individual files or subfolders now compactly display counts of the number of tasks and the size of the comment thread, when applicable, for the file or folder. Folder or single document views display all task and comment activity right in the page.
Automatic Attachment of Images Embedded as data: URLs
In some browsers, notably Firefox, dragging and dropping an image into TeamPage's rich text editor resulted in the image being added to the content in the form of a data: URL. Even though this is effective as far as most users are concerned, for various technical reasons, it is less than ideal. As of this release, images embedded as data: URLs will instead be automatically captured in a separate file, and the file will be added as an attachment to the entry being created or edited, as long as the user has "Add Attachments" permission in the entry's space.
Other Changes
- Changed the way in which feedback details are gathered for certain types of errors to make it easier to diagnose their underlying causes. (Proteus11338)
Bug Fixes
• Fixed a regression that would prevent TeamPage from shutting down when a shutdown in certain ways. The most common such case is that a shutdown requested from the Windows services control panel would not shut down TeamPage. (Server75319)
• Fixed an issue related to subtabs for views of Projects that could cause problems with certain plug-ins. (JPBO5479/JPBO5483)
• Fixed an issue that could cause a problem saving a new entry using certain custom form plug-ins. (Server74908)
• Fixed an issue that would prevent the recognition of entry class mail directives for entry class names that contain the underscore character. (ec8bed69ffcf)
• Fixed a bug that caused the back and forward buttons on the Project and Milestone > Calendar views not to function properly. (3a5aaff22535)
• Fixed a bug that could cause an infinite HTTP redirect on certain types of requests, including, e.g., the "Edit Sections" link in an ordinary New Article form (users may have seen an error message including "java.lang.StackOverflowError" when attempting to launch the section editor). (Server74972)
• Fixed support for section table widgets driven by Attivio Search sections. (Server75075)
• Fixed support in PDF export for section table widgets driven by Attivio Search sections; and fixed support in Print Version for section and section table widgets driven by Attivio Search sections. (fabc38eb08ea)
• Fixed a bug involving manually creating new TeamPage user accounts for security principals defined in an external system (e.g., Microsoft Active Directory service) connected to TeamPage. (Server75055)
• Fixed a bug related to unexpected Javascript errors experienced by users of Internet Explorer 8 and 9 when attempting to load a form to create or edit an article or other entry, and would prevent proper operation of the form. (Server75041)
• Fixed a bug that could prevent email replies to email notifications from being properly recognized and routed. (Server75307)
• Fixed a bug that prevented the collector from displaying properly when the "Show Collector" link was used by a user who had not yet defined any collections. (Server75134)
• Fixed an issue that could cause an the date for an entry in an RSS feed generated by TeamPage from being correctly displayed in certain RSS readers. (JPBO4640)
• Fixed a bug that prevented TeamPage's rich text editor from being visible and usable when the TeamPage URL did not start with "/traction". (Server75140)
• Fixed a bug that caused TeamPage to erroneously report that a user could not edit an entry if the entry has no published versions, and the user attempted to edit the entry from "Published" view mode. When this error happened, the user would have encountered an error such as "com.traction.gwt.forms.client.FormOperationException" with the detail message "com.traction.sdk.MessageException: There is a draft version of this article, but you do not have permission to read it." (Server75502)
For Developers
Entry Field Renderers
Introduced the concept of configurable "entry field renderers." The concept of an "entry field" is a completely abstract one; entries do not literally have "fields," but it is convenient to be able to declare a rendering so that it and its label display text may be referred to by name in the context of any entry.
Localized Date Formatting
By default, TeamPage formats dates according to the preferred locale of the requesting user. Some document formats have special requirements for date formatting, including a requirement that dates be formatted with respect to a particular locale (e.g., US English), irrespective of the requesting user's preferred locale. To make it easier to support such requirements, TeamPage's date format SDL tags now support a locale= attribute that can be used to specify the locale that should be used to format a date, e.g.:
<entry.date dateformat="short" locale="en" />
Article: Customer4787 (permalink) Categories: :Doc:R60, :Doc:changelog Date: February 4, 2015; 3:55:26 AM Eastern Standard Time
