 |
Download TeamPage 6.2 |  |
Error (HTTP response code 404)
A view could not be found that matches: view=home,home skin=proteus
com.traction.sdk.view.Section interface and its implementations have been modified so that its methods no longer require a com.traction.sdk.Context object. The Context object is now supplied at the time the Section instance is created, and is accessible via the Section interface's new getContext() method. This simplifies the API and brings the Section object into line with other per-request transient Traction SDK objects, such as com.traction.sdk.Entry and com.traction.sdk.File objects. The Section interface also now offers the getNumber() method, which returns the 1-based ordinal representing the location of the Section in its containing list (when applicable, e.g., in a list of dashboard sections), which can be useful for identifying the section in many cases. (Server88575)<sections> tag now correctly supports type=variable with a custom variable name specified by the variable= attribute. Previously, this support was incomplete even though the tag documentation indicated that it was supported. (Server88606)com.traction.sdk.view.ViewAction class, com.traction.view.action.NewRelatedItemEntry, extending com.traction.view.action.NewArticle has been added to support creating new entries related to the currently scoped Item in SDL using the forms API's task item dialog or event item dialog form containers. The NewTaskItem and NewEventItem ViewAction configurations use this new class to provide access to this functionality. Developers can now more easily set up custom links and buttons for allowing users to set up related tasks and event entries -- or "sub types" of tasks and events of their choosing -- equivalent to the way in which the "task" and "schedule" hover item menus work without having to manually create the "region token" encoding to trigger the appropriate type of form and dialog. (Proteus15020)Proteus.addHandler function. The event listener may return true to allow the form save operation to proceed, or false to veto it. For example:
(function() {
function myCondition(eventData) {
// ...
}
function onBeforeSaveForm(eventData) {
if (someCondition(eventData)) {
// Form submit vetoed.
return false;
}
// Form submit allowed
return true;
}
Proteus.addHandler(onBeforeSaveForm, "form-before-save");
})();
com.traction.sdk.SearchExpressions that are present on a com.traction.sdk.CJournalRequest/JournalRequest but which have been deactivated:com.traction.sdk.Context's createCleanJournalRequest() method now always provides a JournalRequest that has no SearchExpression. Previously, if a SearchExpression happened to be present on the Context's default CJournalRequest, it would still be present but deactivated via invoking setSearchActive(false) on the copied JournalRequest being used as the "clean" instance rather than being cleared by invoking setSearch(null). (Server88735)JournalRequest's addConjunctionOrSetSearch and addDisjunctionOrSetSearch now clear any inactive SearchExpression if one is present before setting the provided SearchExpression as the current one for the JournalRequest. This is more in line with the contracts for these methods, and more useful since clients using these methods do not generally want to have a search applied on top of an existing but inactive search. (Server88738)sample-data.png
sample-form-before-save-data.png
