In the new Content Server Version 21.1 there are two new Report Widgets for Security Clearances and Supplemental Markings.
How does it look like?
Here, both are shown on a landing page. This Widgets can be expanded by clicking on thy symbol on the lower right.
Then the full page widget view will be drawn. The report can be refined by selecting several columns.
How to configure?
Simply add this widgets on the perspectives you want by dragging and dropping the widgets from the new group “Security Clearance Reports” to the widget area.
How to Install?
The widgets must be installed. They are based on several webreports and livereports. These reports are bundled in an Content Server App called OTRMSecReports. Open the “Applications Management” and install the application along with OTRMReports.
If its installed, you can check the components in “View Application”.
Ensure, that the version number is correct or correct the appropiate zip file.
Happy Security Clearance and Supplemental Markings Listing!
The Treebrowse Component is a new in Content Server 21.1. What’s a Treebrowse?
Let’s take a look at the index.html at csui/controls/treebrowse/test
This is an additional Window with the tree based display of all folders in a Content Server. It can be configured that a click on the top left icon will switch it on and off. This Treebrowse Control will then change the display of a Nodestable according to the folder pressed.
Additional Features
Lazy loading and prefetch options for performance. There are a couple of options to configure the loading of the nodes for performance. A “Show More” button can be configured
Tree Navigation is in sync with Table View in Nodestable view. The Nodestable is displays the children of the selected folder.
Multiple root nodes can be configured.
Enable
This Treebrowse is always there, but it must be enabled.
var NavigationTree = {
enabled: function (status, options) {
if (!!enableSystemLevel) {
return true;
}
var enabled = false,
moduleConfigCollection = new configCollection(moduleConfigs);
moduleConfigCollection.some(function (mConfig) {
enabled = mConfig.get('enabled')(status, options);
if (enabled) {
status.originatingView.treeData = mConfig.get('data')(status, options);
}
enabled = enabled ? true : enabled;
return enabled;
});
return enabled;
}
};
return NavigationTree;
});
As you can see, the Enablement on a system level can be done in OScript. Refer to this post, if you want so figure out how.
If you want to configure this control only for certain folders, you should do:
Implement methods enable and data in a separate file and return them in an enclosed object.
Register this file which returns object containing enable and data methods as an extension to the “csui/controls/treebrowse/navigation.tree” in the respective module.
Enable method should return a condition that specifies when the Tree Navigation should be enabled.
The data method should return data that must be passed to tree navigation while instantiation. This data should include configurable settings. If there is no data to be passed default settings are applied.
Example
define([], function () {
'use strict';
var RMTreeView= {
enabled: function (status, options) {
var supportMaximizeWidget = $("body").hasClass("csui-support-maximize-widget"); return (supportMaximizeWidget && $("body").hasClass("csui-maximized-widget-mode") === false);
},
data: function () {
return {
"lazyTree": true;
};
},
sequence: 50
};
return RMTreeView;
});
A more complex enabled function (like in the index.html) is
enabled: function (status, options) { var parent_id = status && status.container && status.container.get('parent_id'); return !!parent_id; }
Parameters
Parameters thats need to be included as part of module config:
sequence – number default: 100 Decides the priority of a module when multiple modules enabled treeview.
enable – function controls whether the treeview command should be visible or not. Need to return a logic whether tree view command is visible.
data – function Returns an object of data that are passed to treeview. The parameters that are returned by the data method are passed as options to the constructor of node.tree.view.
Parameters that can be returned by the data method are::
lazyTree – Boolean default: false Decides whether to prefetch items at one level ahead to display without any delay on clicking showmore button / to fetch the items after clicking show more button.
showItemsBlockSize – Number default: 10 Number of items that are shown on expansion of any node or clicking on showmore button.
rootNodes – Array of nodemodels default: top most ancestor node of the currently active node An array of nodes which are used as root nodes by the tree. If more than one root node is provided then multiples root nodes are displayed.
This is an brief overview on the highlights of Content Server 21.1. This is only a technical list without any screenshots.
In the following posts I will discuss some of the new features more in detail, of course with screenshots
What’s new? A brief overview.
This is an excerpt from the Content Server 21.1 Release Notes
Administration
Admin Server Processes have now names which follow the the schema AdminServer-NN.
Read-Only Partitions. They have been eliminated. During Upgrade, they will be converted to retired node.
New Indexing Control Rules. For new installations, they follow the best practices for configuration.
Transport Warehouse, The system was simplified.
Connected Workspaces
Folder Templates. Like creating documents and workspaces from predefined templates, Folders now can be created from predefined folder templates.
SmartView
Multilingual Metadata. The name and the description fields in the metadata now support the edit of these fields in the configured multilingual metadata
Search Forms. Search Forms, created in classic UI are now available from smartUI.
TreeBrowse. A new widget allows to browse the nodelist widget with tree like display (similar to the Windows Explorer) after enabling this widget.
OpenText Viewing
Is now available as Windows Installer in an non-containerized environment.
Perspectives
Perspectives now can be enabled or disabled
Content Intelligence
Three new full-page widgets.
Nodes Table Webreport -Full
Table Webreport – Full
Visual Count – Full
New full page Webreport destination supports the new full page widgets.
New Tags/Tag Options
Enable Row Filters: Automatically filter a Webreport data source if the report is used as a button within the Visual Count Widget.
Hidden Columns: INDLUDEHIDDENCOLUMS: <hiddencolumns to include> is a new option in Table Webreports to display hidden columns.
Records Management
REST
Add and remove users to a hold
Add and remove users to a user based hold
Execute a user based hold and apply or remove holds from content owned or modified by the user
Security Clearance
Dynamic Security Clearance. The Clearance can now be controlled based on organizational defined criteria, like network and device to provide a finer control of the Clearance. For example, a login from a coffee shop can receive a lower Clearance as one from the intranet.
User profile. Clearances and Supplemental Markings can now be displayed on the user profile.
Workflow
Initiation by Mime Type. Workflows can be initiated by mime type, such as a pdf in the proper format.