Title: TeamPage 6.1.10

Traction® TeamPage 6.1.10 fixes several bugs and improves the Unified Search feature that lets you quickly navigate through TeamPage using the search box. It also introduces support for a new Signature Requirements module, which lets you require people to sign TeamPage articles either once or on a recurring basis. Signature Requirements can be used to collect approvals for publication, confirmation that a document has been reviewed or a process followed, or for any other situation where a set of users and groups must explicitly acknowledge that they have reviewed an article.

Download TeamPage 6.1


Features



Signature Requirements Module



We are pleased to announce that TeamPage now has a separate module that supports managing signature requirements. You can require selected users and groups to read, approve, authorize, or certify that they have taken some action associated with or described in a TeamPage article.



You can schedule signature requirements to be completed by a specific date, and you can also set them to recur automatically, for example to help clinical staff fulfill the requirement to review certain Standard Operating Procedures on an annual basis.

The types of requirement supported are extensible, so you can easily add custom types. The system reminds everyone involved of upcoming and overdue digital signature requirements, and managers can see exactly who signed when—and who has not yet signed—broken down by person, group, document, or space.

For auditability, signatures track the exact version of the document signed, and if a document has changed since the last time you signed it, the system shows you the exact changes between the versions.



Please contact sales@tractionsoftware.com to learn more.

Unified Search (Type-Ahead Completion)



There have been several small but useful improvements to TeamPage's type-ahead completion search features.

• Several types of search targets — such as spaces and users — now support "in-order" character-by-character matches. This means that if the letters in your query appear in the same order, even if they're not adjacent, they may still be considered matches. This makes it easier to find things even if you're not sure how to spell what you're looking for. For example, the user "David Shepperton" would be found as a search hit using the query text "dav shep" because the characters in the search query appear in that display name in order. Note that at this time, journal entry search results (such as for projects and milestones) do not support this type of matching. (Server74473)

• Tag names are now offered as type-ahead completion matches. (Proteus9903)

• Some of the type-ahead completer controls used in TeamPage's forms are now driven by the same unified search features that drive the main search box type-ahead completion features, making the user experience more uniform across all different areas of TeamPage where type-ahead completion is employed. (Proteus11183) This is an ongoing process, and more of these controls will be converted to use unified search in the future.

• Users who do not have "Access Address Book" permission will now be able to get type-ahead completion results (in various contexts) on other users, when the query text matches the user name or the user's display name. These users will continue to be prohibited from looking up other users by email addresses. (Server74331)

• For users who have Access Address Book permission, the Invite dialog will now match against users' "other" email addresses, rather than just against users' primary/preferred email addresses. (Server71517)

• When a user types search text that is just a number not preceded by a space name, and they're looking at a page focused on all spaces (e.g., the All Spaces Dashboard / Front Page view), they will no longer get a confusing completion option for the entry whose ID happens to have that number in the first active space from the journal, alphabetically ordered, in which they happen to have read permission. (Server74478)

• The groups of type-ahead completion matches now appear in descending order by maximum search hit score. This means that groups that contain better scoring matches will appear first. (Server74051)

Other Features and Changes



• When requirements are in effect for passwords for user accounts managed in TeamPage (e.g., minimum length or minimum number of special characters), a summary of the requirements will be displayed anywhere a user password can be set for either new or existing user accounts. (Server79236)

• When launching a work-in-progress of an update to an existing entry, the "Delete" link will no longer appear in the form. This will avoid confusion over the meaning of this link, so that users intending to delete their work in progress will not inadvertently delete the entry they're trying to update. (JPBO10035)

• The Mexico skin has been retired, joining other older skins (such as Ocean, Earth, Modern and News) in the "Classic Traction TeamPage Components" plug-in. No further development will be done on the Mexico skin. Please ensure you are using the "Proteus" skin, which has been TeamPage's main, actively maintained, up-to-date user interface for the past 5+ years. Customers who decide they wish to continue using the Mexico skin, either because they have users who still have to access TeamPage via Internet Explorer version 6 or earlier, should make sure that the "Classic Traction TeamPage Components" plug-in is installed and enabled. Note that this plug-in ships with TeamPage and is enabled by default as a courtesy for existing customers, but should be disabled in the absence of specific reasons to use it. Developers, please see the related note in the "For Developers" section below. (Server79388)

Bug Fixes



• Fixed a bug that could prevent files from being properly attached to entries when running TeamPage on Windows with a journal whose configuration details use a path that includes a drive specification, as when running a TeamPage server with a journal located on a volume or drive other than the one where the TeamPage software is installed. (Server79171)

• Fixed a bug that could cause an error to be presented to the user after having used the "Delete" control in an edit form to delete an existing article or other entry. (Server79420)

• Fixed a bug that prevented the "Replace" button from working properly. In some cases, the button would work the first time it was used and then fail to work from then on until the page was fully reloaded. (Server79496)

• Fixed a bug that could prevent filters created via the Filter menu's "Tags" option from being properly applied. In some such cases, the user would be presented with an error message in the resulting page. (Server79251)

• Fixed some issues with TeamPage's SEW (Social Enterprise Web) widgets, including a problem that prevented the discussion form from working properly. (Server79308 / Server79378 / Server79380 / Server79377 / Server79376)

• Fixed a bug that could cause an error to be presented to a user viewing the built-in Visitor account's user profile pages. (Server79309)

• Fixed a minor error that would sometimes occur during a native fulltext rebuild when processing user profile records. This error did not have any known user-visible side effects, but produced an error in the log file. (Server79537)

• Fixed an issue which could cause certain embedded attachments to be listed in the "Attachments" list at the bottom of the entry instead of in the "Embedded Images and Video" list, This also caused the counts associated with the two lists to be incorrect. (Server79459)

• Made a change to prevent certain diagnostic information related to TeamPage's WebDAV storage repository implementation from appearing on the console unnecessarily. It will now be logged to the "webdav" diagnostic stream, which can be activated when actively investigating an issue. (Server79468)

• Fixed a bug in the Print Version skin that prevented links to single spaces that appear in the "Locator" portion of an entry's details from working properly. (Server79601)

• Fixed a bug that could cause erroneously space-qualified rapid selector formatted values to appear in the list of relationship types in the "Edit Relationships" dialog. (Server79662)

• The Task Summary dialog has now been internationalized and localized in Japanese. (JPBO9531)

• Modified the way user records are verified to accommodate certain values that are not expected, but which can exist in customer journals created with early versions of TeamPage. If you have been unable to start TeamPage or rebuild your journal's indices since upgrading to TeamPage 6.x from an earlier version, and you saw an error message like "Unable to decode this user record," then this should address that issue for you. (Server79867)

• Modified the way that ACL entries are validated to ensure that administrators cannot configure an entry that denies certain permissions without also effectively denying permissions that represent higher levels of the same type of permission. This will in turn ensure that the following intended behaviors are observed correctly and will not lead to unexpected results related to the combination of multiple ACL entries applied to the same user account when at least one entry includes Deny rules for edit, read or delete permissions. The following specific changes have been made when evaluating individual ACL entries: denying Edit Own Articles permission will also deny Edit Articles and Edit Locked Articles permissions; denying Edit Articles permission will also deny Edit Locked Articles permission; denying Read Own Articles permission will also deny Read Articles and Read Draft Articles permissions; denying Read Articles permission will also deny Read Draft Articles permission; and denying Delete Own Articles permission will also deny Delete Articles permission. (Internal11318)

• Fixed an issue that could prevent separators that have been added to task lists from appearing until the entire page was manually refreshed. Separators now correctly appear immediately when they are added in a task list view. (Server79840)

For Developers



• The db.entries tag, which can be used as a way to iterate over journal entries based upon queries executed against externally defined database tables, now supports query result sets which include the same entry multiple times. (Proteus13724)

• TeamPage's GWT Forms API now properly supports forms for creating and editing entries that do not have any tag fields other than one for completion status ("to do" vs. "done"). Previously, if a field for selecting the completion status of the entry were the only tag field in a given form schema/definition, the field would not be properly populated with the correct current value on edit, and any changes to the field would not be applied when the form was submitted.

• TeamPage's GWT Forms API now also supports ignoring the "required" property of fields that appear in a form schema and/or definition, but which do not appear in the form layout presented to the user. This way, fields can be marked as required (users must specify a non-empty value), but can also be conditionally included in the HTML used for an authored form layout. Previously, if a required field did not appear in the form layout, the user would never be able to submit the form, because the server would always complain that the field had no value.

• TeamPage's rich text editor's Insert/Edit Widget control now correctly supports custom widgets whose htmledit TokenRenderer configuration file does not include any rskeywords= property. Such widgets require a rapid selector token that contains the "token" keyword, but previously, that keyword was not inserted when it was supposed to be, preventing the widget from being recognized (and thus preventing it from appearing in the resulting entry, and/or being edited while editing the entry).

• The SDL <user> tag now has more graceful handling for the case in which the SDL author specifies a principal= attribute with no value. Previously, using the <user> tag with an empty principal= attribute would cause an error.

• There is now a <principal> SDL tag which puts a com.traction.sdk.admin.Principal object into scope as the current principal, allowing the principal.* tags to be used. The encoding= attribute must be specified to indicate the encoding of the desired security principal.

• The new directory_users UnifiedSearchSource can now be used to query for users defined in any external identity server or servers that TeamPage is currently configured to use.

• EntryClass configurations may now specify whether they should be considered eligible for inclusion in the "normal" index entry type family, as well as whether they should be considered eligible to be included in the "content" (Article) and "comment" index entry types. This makes it easy for plug-in authors to make forms designed to create and edit entries which should not appear in query results for normal queries unless they are specifically requested, such as "Activity > Feed" or "Activity > Posts". The custom_entry_type_is_article and custom_entry_type_is_comment EntryClass configuration properties, along with the corresponding customEntryTypeIsArticle and customEntryTypeIsComment methods, which served part of the same purpose, are now deprecated in favor of this new more comprehensive and straightforward way of indicating whether entries belonging to certain EntryClasses should be considered members of the important built-in index entry types.

• Stylesheets and Javascript for the Mexico, Ocean and Modern skins, and the 3col and 2col "lib" skin view configuration files (which apply to these skins and others) have been moved to the com.traction.classic plug-in. If you have customizations that require any of these elements, they will still be available as part of the default TeamPage installation for the time being, but in future may require manually installing the com.traction.classic ("Classic Traction TeamPage Components") plug-in separately, since it will not be packaged with TeamPage in the future. The SDL files for the "lib" skins, mostly located in the src/com/traction/sdl/lib subdirectory of your TeamPage installation's server folder, are still present, but may also be moved or removed in a future release.



Attachments:
Acme2__This_IS_fun.png
Basic75__Something_else_on_my_worklist.png
Article: Customer4860 (permalink)
Categories: :Doc:changelog, :Doc:R61
Date: December 8, 2015; 3:11:52 AM Eastern Standard Time

Author Name: Dave Shepperton
Author ID: shep