Title: TeamPage 6.0.14


Traction® TeamPage 6.0.14 new features include: support for @ style user "mentions"; updated popup profile card, profile page, and unified search to make @ user names more visible; interactive @ name auto completion works in TeamPage articles, comments and status posts; a new combo-box control for entry forms that supports type-ahead completion for spaces, projects and milestones; and moving entries between spaces. The release also includes several bug fixes, improvements, and developer changes.

Download TeamPage 6.0


Features



@ Style User Mentions



TeamPage now recognizes @ style mentions of a person's name in a TeamPage article, comment, or status post. TeamPage turns the mention into a live @ short name reference, and notifies that person that someone has mentioned them. When your name is mentioned in an article, comment or status post, TeamPage will automatically notify you of any follow-on comments.

For example, Wile Coyote mentions Greg Lloyd in a comment:



Greg Lloyd will get a live notification (see Customer4621: TeamPage 6.0.09):



And an email notification with a link back to the original mention:



TeamPage automatically watches the comment for Greg Lloyd and will send notifications on any follow-on discussion. Greg Lloyd can delete the automatic Watch notification if he no longer cares about follow-on comments:



Click the name of a person mentioned in an article or article header to pop up a mini-profile including that person's @ name.



When using the type-ahead completion feature of the Search bar, a user name hit now shows the person's @ name. If you search using @ name, type-ahead completion will look for a name match.



Type ahead auto completion for @ mentions also works in rich text articles, comments, and status posts. To fill in a persons' @ name, type their first name, last name, part of their name, or email address, then pause. TeamPage will suggest one or more @ names that match your pattern; select the person you want to mention and TeamPage will fill in their @ name. At present, auto completion lookup requires generalTeamPage Address Book permission, which most customers grant to all people using their TeamPage server.

TeamPage Address Book permission grants people the right to look up people's account information by name, email address or other TeamPage profile field, which is sensitive information for some customer TeamPage deployments. Anyone can make an @ mention using the exact @ name shown with a person's profile, see screenshots above. If a person's @ name contains blanks or special characters, you need to type the name in square brackets, just as TeamPage shows it in that person's profile, for example @[a-complicated name].



Combo-Box for Space, Project, and Milestone controls



The default Space, Project and Milestone controls in all of TeamPage's forms have always been selectors that offered a potentially long list of choices - one line per space, project, or milestone - which would usually have to be loaded all at once. This can be slow if you have a lot of spaces, projects and milestones on your server. The new combo-box control allows you to start typing a few characters to filter the list to show just the space, project, or milestone choices you're most interested in. You can click the down arrow at the right edge of the selector if you want to see the full list.



Moving Articles



TeamPage makes it easy to choose a space when you post a new article - but sometimes you change your mind or choose the wrong space by mistake. TeamPage 6.0.14 makes it easy to move an article to a different space by creating a copy of the article and its attachments in a new space, then deleting the original article. When an article is moved, its original content and edit history are deleted, and the moved article is attributed to user moving the article, not the original author. The creation time moved article is the time the move happened rather than the creation time of the original article.



Other Features and Improvements



• Changed the way in which license limits on active user accounts and spaces is enforced so that even if the active licensed limit has been reached for users or spaces, they may be still be created in the inactive state. It would be unusual to need to be able to do so, but it can be useful in certain cases. (57abb0c214a1)

• Modified the way that search results are presented for customers using the Attivio AIE 3.5 TeamPage connector with the Attivio AIE 3.5 server so that duplicate documents are, by default, omitted from search results. (f7a18df411eb)

• Added support for Internet Explorer browsers versions 9, 10 and 11 when configured to use the "Compatibility View" feature. (f34ae52bdfca/add960d0f976)

• Added support for drag-and-drop uploading of files in Internet Explorer versions 10 and 11. (Proteus11132)

• Made it possible to configure the default behavior for including "empty threads" in the results for "Discussions" queries. Since version 5.2.51, non-comment entries that do not yet have any comments have, by default, been included in such results (please see Customer4107.072: TeamPage 5.2.51). If you need to change this default behavior, please file a support request. We can provide you with a plug-in that will allow you to edit a new server level setting governing the default behavior, allowing you to omit (by default) such "empty threads" from "Discussions" query results. (Server73915)

• Modified TeamPage's web-based login form so that it is backed by a single HTML FORM element, thus allowing proper functionality of login/password managers such as 1Password. (Server73910)

• For clarity, changed the label text for the subtabs of the User Profile > Notifications tab so that they now read "Feed" and "Watch List." (Proteus11020)

• The presentation of status updates on the Status tab (and in the Status popup window) has been updated for clarity and visual appeal. (Proteus11095)

• The space templates, as well as the default server-wide dashboard sections, have been updated and improved. The Project Team, Wiki and Intelligence templates have gotten a bit of an overhaul, and a new Management Team template has been added. (Proteus10814/Server73427)

• Inactive users are no longer listed in the "Space Members" list in the side column of single space scoped pages where it appears. (Proteus11059)

• Added basic support for the "ro" (Romanian) locale. The TeamPage interface has not yet been translated into Romanian (this is expected to happen in an upcoming release), but Romanian locale-specific preferred date, numeric, and other formatting preferences are supported.

• Added a digest skin preference, supported by the Block and Block 2 digest skins, that allows users to choose whether images embedded in their digest should be attached to the digest email message. This can be helpful for users of certain web-based email platforms, including Gmail, which will sometimes rewrite the embedded references to images in such a way that some or all images will not be loaded (depending upon the permissions required to retrieve the image resource from the TeamPage server). (See this helpful reference for further information in the case of Gmail.) (Server74299)

• Modified the way that some type-ahead matching is handled to ensure that exact matches (e.g., on a user account name or on a space's display name) are preferred over prefix, infix or ordered/fuzzy matches. (Server74426)

Bug Fixes and Other Changes



• Modified the date separators displayed in results for "tag changed" driven queries so that the date displayed is the date of the tag change operation rather than the date of the entry's creation. (Server73220)

• Removed, once and for all, any possibility that TeamPage will request a full "garbage collection" process when clearing various cached data. When such a full garbage collection operation is performed, it may cause the TeamPage service to become unresponsive for as long as it takes, which could be on the order of minutes or hours, depending upon how much memory has been allocated to the TeamPage Java process and the kind of environment in which the service is running. In TeamPage's default shipping configuration, the Java Virtual Machine will incrementally perform garbage collection in the background in parallel with other processing, so that any disruptions would be much shorter and much less noticeable. Now, the only way to request a full garbage collection is to use the "Cache Manager" view and to explicitly select the "Garbage Collection" option before clicking the "Clear Selected Caches" button (and there should generally not be any reason for customers to do this unless so advised by Traction Software support staff). (Server73703)

• Fixed an issue with TeamPage's entry form API which prevented certain field values from being correctly loaded. This was noticeable in the user profile form, where, for example, the Website and Bio fields would show up blank even if they had been previously filled in. (JPBO4578/Proteus11076)

• Fixed an issue that prevented editing entries if one of their attachments had been deleted or renamed. (Proteus11119/Server73763)

• Modified the display of Project and Milestone "Discussions" tabs to display all inline tasks, events and "shared by" blocks, the same way that inline comments were already displayed. (Server73722)

• Fixed a bug that prevented the "share" hover menu item from working in Attivio search views for search results representing attachments to entries, files in entry share folders, or files in space shared folders. (Server73247)

• Fixed two bugs that could cause TeamPage not to read messages from a mailbox even if it was enabled and all the required settings were specified. This could have affected either the server mailbox or a mailbox associated with a particular space. Concurrently, "mailthread" diagnostic logging has been improved to make it much easier to see when TeamPage is processing a particular mailbox configuration, what stage of that process it is on, and the reason, when applicable, that the process was aborted or skipped. (Server73726/Server73751)

• Fixed an issue that caused TeamPage not to generate notifications for users of tag change activity that was covered by their subscriptions. (Server73844)

• Fixed the date range displayed in the Print Version skin for an Attivio search view scoped by a date range (i.e., "between [date] and [date]"). (Server73753)

• Removed the long retired "Personal Note" and "Question" view actions from the context menu in a few places where they were still referenced. These view actions have been part of the com.traction.classic plug-in for some time. They never should have appeared in these contexts. (JPBO4730)

• Fixed an issue that prevented custom login messages configured for a TeamPage server not to be used on the login form. (JPBO4207)

• Fixed a bug that caused the time portion of the "End Date" field in the Event form to be displayed when editing an existing form even when the "All Day" checkbox was checked. (Proteus11309)

• Fixed a bug that prevented the digest email message from being sent for any user whose "Digest Spaces" setting was configured with the checkbox labeled "Automatically subscribe to digest spaces as they become available to me." unchecked. (Server74368)

• Fixed a bug that prevented email notifications of file activity from being sent if the target file's name contained certain characters, such as spaces. (Server74366)

• Modified the User Profile > Work in Progress page so that the Print Version and Syndication (RSS) links are no longer displayed near the upper right corner of the page. Previously, these links showed up and, if clicked, would bring the user to an error page. (JPBO3836)

• Various i18n and l10n tweaks, including some related to the Section Table widget and the Logo Manager view. (JPBO4635/JPBO4854/JPBO4568/JPBO4635/JPBO4728)

• Updated the Japanese language version of the TeamPage license agreement included in the installer. (JPBO4854)

• Modified the license agreements and other text based files and resources that are used in the installer to work around some issues with the installer framework that could cause text to extend horizontally past the edge of the display, or caused some characters to be rendered using the wrong encoding / character set. If you have problems seeing, reading or understanding any of the text you see in the TeamPage installer, please don't hesitate to contact our support staff, either in the Forum space, or by creating a new support request (click the "New Support Request" button displayed prominently in the side column of most pages here on our support server). (Server73742)

• Fixed the link "Go to the Front Page" link on the digest unsubscribe confirmation page. Previously, clicking this link did nothing. (Server74325)

• Fixed a minor issue that could cause a "java.lang.NullPointerException" error to be displayed when certain pages were generated. This issue was caused by improper handling of an unexpected error condition related to testing whether the requesting user has permission to view a record representing certain types of tag change operations. (Server74324)

• Fixed a minor but long standing issue that could cause the TeamPage server to attempt to perform certain settings changes twice. The second attempt would generally not result in any data being set again or modified, but could require needlessly setting up an operation that had already been performed. (49fec4de93e5/b7ae4760978b)

• Fixed a minor issue that could cause an error message to be displayed when attempting to load the "Viewed By" data. (Server73029)

• Fixed a minor issue that could cause the title tips used for the Project and Milestone entry titles in an entry's "locator" text (the part of the details block for an entry that indicating what space, project and milestone an entry belongs to) to be incomplete or to contain unexpected markup. (Proteus11048)

• Fixed some issues that could cause strange behaviors when a TeamPage server/journal has been set to read-only mode due to a license issue (e.g., when running with an expired license). (Help10115/Proteus11139)

• Fixed an issue with the login form on the simple skin, the interface used for legacy mobile devices. Users would have seen the following message: "Your browser ID, used to ensure the security of changes made to your TeamPage server, could not be verified. If you were trying to make changes to your TeamPage server, please report this issue." (Server74295)

• Fixed an issue that prevented the URLs for embedded images referring to files in the TeamPage file repository other than attachments, or other server-relative URLs, from being fully qualified when they were supposed to be (e.g., in the body of an email digest message). (Server74338)

• Fixed an issue that could, in the extremely unlikely (but still possible) case in which an entry was edited after being created to make it a comment on itself, cause any page that contained the entry to fail to load (most likely after taking several seconds or more trying to load), and for an error to be displayed mentioning a "java.lang.StackOverflowError". (Server51766)

• Fixed an issue that caused users to see an error dialog instead of an in-page error if the URL for a Documents tab contains an empty path= parameter. (Server74374)

• Fixed an issue related to the default value for the "Eligible for Inclusion in the Digest" space setting. This issue would cause the setting editor's checkbox not to be checked even though the effective default value for the setting was for spaces to be eligible for inclusion in the digest by default. We recommend that any customers who rely upon the email digest feature review the "Spaces Eligible for Inclusion in the Digest" setting (Server Settings > Email > Digest), to ensure that all the spaces that should be eligible for the digest really are (this setting editor allows batch changes to this setting for multiple spaces at once). (Server74390)

• The "Automatically Subscribe to This Space" space setting for the invitation feature now defaults to "no", so that space (or server) administrators must, by default, opt into this behavior. Also, the server default value of this setting is now available to be edited on the Server Settings > Defaults page. (Server74434)

• Fixed an issue that caused the "Last Updated" date for each tag listed on a space's Tags > Index page to be date/time of the earliest visible usage of the tag rather than that of the latest visible usage. (Server74481)

• Fixed the possibility of an issue that could prevent a user from attempting to email articles from TeamPage in certain rare cases (the error message "java.lang.IllegalStateException: STREAM" would be displayed). (Server73735)

• Modified the attachments list that can appear at the bottom of top level entries in Print Version, email notification messages, and syndication feeds to omit the numeric attachment ID and to show only those attachments which do not appear embedded inline in the content of the entry. (Server74765)

• Made "New Event" the default first option display in the add menu in various calendar views. (Proteus1131)

For Developers



• The signature of the com.traction.sdk.edit.EntryFilter interface's method process has changed from

public abstract void process(NewEntry newentry, UserContext context) throws SubmitException;


to

public abstract void process(Context context, NewEntry newentry) throws SubmitException;


This overdue change provides custom EntryFilter authors the opportunity to access all normal SDK fetaures via the com.traction.sdk.Context object (for the request on behalf of the submitting the new entry), instead of just a com.traction.sdk.UserContext. (In any case, the com.traction.sdk.Context abstract class implements UserContext, so the same API methods will be available.) We do not expect any customers to be affected by this change, but if you have built any custom EntryFilter classes in plug-ins now deployed on your TeamPage server, their Java source code for the EntryFilter class(es) must be updated to conform to this new signature, and will then have to be and recompliled and repackaged. We're sorry for any inconvenience; we do not anticipate needing to make further changes to this API.

• The com.traction.sdk.sdl.tag.LabelUrl class which implements the label.url tag has been refactored so that the source of the Label can be overridden.

• The following methods in the com.traction.sdk.TractionUrlGenerator interface have been deprecated:

public String label(Label label, Date sdate);

public String labelChanged(Label label, int status);

public String labelAdded(Label label);

public String labelRemoved(Label label);


These methods existed in order to provide the option of setting the sdate (start date) for a time slice on the URL for a tag query for a given Label instance, and to request the type of view associated with a particular label status.

In the case of setting an sdate on the URL, that should be done by creating a TractionUrl and invoking its setSdate parameter, and then retrieving the TractionUrlGenerator from its getUrlGenerator method: the URLs generated would have the appropriate sdate parameter set.

As for label statuses, Label instances already have a status (e.g., current, added-still-present, etc.) since they represent the label instance that appears on a particular item in a particular entry, within the context of a particular query. This makes it redundant to pass a status to have a URL generated for the type of tag driven view associated with the status. TractionUrlGenerator offers the following methods for generating URLs for tag driven views based upon one or more LabelName instances:

 public String label(LabelName labelName);

public String label(LabelName labelName, Date sdate);

public String labelChanged(LabelName l, int status);

public String labels(Project current, LabelName[] labelNames);

public String labelsChanged(Project current, LabelName[] labelNames, int status);

public String labelsChanged(Project current, String rsFormattedLabelNames, int status);

public String labelAdded(LabelName labelName);

public String labelsAdded(Project curproj, LabelName[] labelNames);

public String labelRemoved(LabelName labelName);

public String labelsRemoved(Project curproj, LabelName[] labelNames);


The newly decprecated methods will be removed in a future release.

• All classes in the package com.traction.sdk.digest have been deprecated. For your reference, these are:



These are not related to the current implementation of the Email Digest feature ("Executive Summary"); they existed mainly to support previous versions of the Export feature. These classes, as well as all references to them across the Traction SDK, will be removed in a future release. If you have any classes which implement or rely upon ImageFormat or LinkFormat for changing the rendering of embedded images and links, please use the very flexible and extensible token rendering API to override the rendering of image or various types of link tokens in the required context. See Custom Token Renderings and Custom Tokens for more information on tokens and token renderers.

• The following methods in the com.traction.sdk.form.FormParser abstract class have been deprecated:

public abstract DateRange getPerspectiveRange();

public abstract String getStylesheet();

public abstract String getLogoImage();


These methods are no longer used anywhere in the Traction TeamPage public SDK, or in the SDK implementation, and at least one method relates to a long retired feature. These methods will be removed in a future release.

• Implemented the com.traction.sdk.file.FileRef interface's move method for files stored in the Apache Slide / TeamPage WebDAV file repository, and optimized the implementation of the local java.io.File backed FileRef implementation of the move method. (0dbd325e1094)

• Added the methods logSevere and formatSevere, as well as a useful overloaded version of logError, to the com.traction.sdk.util.log.Debug class. logSevere is like logFatal, in that it logs to Debug.err, but it logs with the prefix "[SEVERE ERROR]" instead of "[FATAL ERROR]". "FATAL ERROR" is reserved for cases in which TeamPage can't start, or when it has stopped unexpectedly.

• Added support to the implementation of the variable.get/variable.value tag (and their variations) for treating an instance of java.lang.Iterable as an indexable variable. Doing so requires iterating through the Iterator produced by the retrieved object's iterator method, but does work, and could be useful in certain cases, such as when a custom SDL tag is putting instances of Iterable into scope when they are not also an instance of a List. The implementation's type requirements for treating maps and lists as indexed variables was also relaxed: instances of Map and List are now accepted instead of requiring instances of AbstractMap and AbstractList, respectively.

• Added the following method to the com.traction.sdk.Personal interface to support retrieving the collections belonging to the requesting user:

public IdCollectionSet getIdCollections();


• Added support for plug-in setting editors to be file upload controls. If you have written your own com.traction.sdk.settings.Setting/SettingEditor class, and need to take advantage of this capability, please add the following property to the plugin.properties file for your plug-in:

settings_form_multipart=true


• Improved the handling of certain kinds of configuration errors likely to happen during development of custom forms, both in the context of TeamPage's GWT-driven FormsService API and its supporting classes, and in the context of the "formdev" view which lists all the forms, including links to open them. (This is a useful view that allows you access to your form without having to wire it up to be opened from a section or section table add button, a view action, or other preferred mechanism. Enter /type formdev to open this page on your own server.)

• Concurrent with the mentions feature, the method getMentionedUsers has been added to the com.traction.sdk.Entry interface, along with the corresponding SDL tag, entry.mentionedusers. Also, the new method getHandle in the com.traction.sdk.User interface, or the corresponding SDL tag user.handle, may be used to render the @ mention style formatted version of the user name (which will differ slightly from the user name when the user name includes whitespace or punctuation) for a particular user.

• Custom SDL com.traction.sdk.token.TokenRenderers that make use of either tsi.sdk.token.ImageForHtml or tsi.sdk.token.MediaForHtml can now make use of the file.* tag set to retrieve information about the com.traction.sdk.File object representing an attachment or other file on the TeamPage server in the SDL template for the rendering. (Server74317)

• Modified the SDL used to display the "body tabs" for projects and milestones, as well as tag-based views, to make it easier to override them in a plug-in.



Attachments:
Demo2368_ Post a test article with one inline image and one .pdf attachment-3.jpg
Demo2368_ Post a test article with one inline image and one .pdf attachment-6.jpg
Sandbox1993_ Post a test article with one inline image and one .pdf attachment-1.jpg
Traction Software-6.jpg
Post a test article with one inline image and one .pdf attachment — Inbox.jpg
Demo2368_ Post a test article with one inline image and one .pdf attachment-2.jpg
re_ Post a test article with one inline image and one .pdf attachment — tractionsoftware.com (All Mail).jpg
JPBO5133_ Translate a few more resources.jpg
Profile_of_Greg_Lloyd_Watch_List_Items_Articles.jpg
New article example suggested 17Nov2014 700w.jpg
Related Articles
referenced by (1)
Forum6911: Custom Mention Links plug-in
references (2)
Customer4621: TeamPage 6.0.09Customer4107: TeamPage 5.2.51
Article: Customer4770 (permalink)
Categories: :Doc:changelog, :Doc:R60
Date: November 27, 2014; 1:50:08 AM Eastern Standard Time

Author Name: Dave Shepperton
Author ID: shep