ActiveView Perspective Manager

OpenText™ Content Server

This help is for ActiveView users and other power users that
create and manage perspectives for Smart View.

CSAV200300-APG-EN-01
ActiveView Perspective Manager
OpenText™ Content Server
CSAV200300-APG-EN-01
Rev.: 2020-June-09
This documentation has been created for software version 20.3.
It is also valid for subsequent software releases unless OpenText has made newer documentation available with the product,
on an OpenText website, or by any other means.

Open Text Corporation

275 Frank Tompa Drive, Waterloo, Ontario, Canada, N2L 0A1

Tel: +1-519-888-7111
Toll Free Canada/USA: 1-800-499-6544 International: +800-4996-5440
Fax: +1-519-888-0677
Support: [Link]
For more information, visit [Link]

Copyright © 2020 Open Text. All Rights Reserved.

Trademarks owned by Open Text.

One or more patents may cover this product. For more information, please visit [Link]

Disclaimer

No Warranties and Limitation of Liability

Every effort has been made to ensure the accuracy of the features and techniques presented in this publication. However,
Open Text Corporation and its affiliates accept no responsibility and offer no warranty whether expressed or implied, for the
accuracy of this publication.
 Table of Contents
Part 1 Using the Perspective Manager 7

1 Getting Started with perspectives ........................................... 9

1.1 Understanding ActiveView perspectives ............................................. 9
1.1.1 Differences between ActiveView perspectives and perspectives
that use the new perspective node type ............................................ 10

2 Create a new perspective ....................................................... 13

2.1 Create a new perspective ................................................................ 13

3 Choose a component .............................................................. 17

4 Define rules .............................................................................. 21

5 Choose a layout ....................................................................... 23

6 Choose and configure widgets .............................................. 25

7 Edit an existing perspective ................................................... 27

7.1 Edit a perspective ........................................................................... 27

Part 2 Configuring widgets 31

8 Content Sharing Widget Configuration ................................. 33

8.1 My Shares and Manage Shares Configuration .................................. 33

9 Connected Workspaces Widget Configuration .................... 35

9.1 Header widget ................................................................................ 35
9.2 Related Workspaces widget ............................................................. 37
9.3 Team widget ................................................................................... 40
9.4 Metadata widget ............................................................................. 40
9.5 Workspaces widget ......................................................................... 41
9.6 Configuration Volume widget ........................................................... 42
9.7 Discussion widget ........................................................................... 43

10 Communities Widget Configuration ...................................... 45

10.1 Discussion Widget Configuration ...................................................... 45

11 Standard Widgets Configuration ........................................... 47

11.1 Favorites Widget Configuration ........................................................ 47
11.2 My Assignments Widget Configuration ............................................. 47
11.3 Node Browsing Table Widget Configuration ...................................... 47
11.4 Recently Accessed Widget Configuration .......................................... 47
11.5 Custom View Search Widget Configuration ....................................... 48

CSAV200300-APG-EN-01 OpenText™ Content Server iii

Table of Contents

11.6 Search Results Widget Configuration ............................................... 48

11.7 Shortcut Group Widget Configuration ............................................... 48
11.8 Welcome Header Widget Configuration ............................................ 48
11.9 HTML Tile Widget Configuration ....................................................... 49
11.9.1 To Configure the HTML Tile Widget .................................................. 50

12 Collaboration Widget Configuration ...................................... 51

12.1 Activity Feed Widget Configuration ................................................... 51

13 Extended ECM for Engineering Widget Configuration ........ 55

13.1 Configuring a Extended ECM for Engineering perspective ................. 55
13.1.1 Creating an Extended ECM for Engineering perspective .................... 56
13.1.2 Making the Extended ECM for Engineering perspective available ....... 59
13.2 Configuring a Connected Workspace perspective ............................. 59
13.2.1 Creating the Extended ECM for Engineering Connected Workspace
perspective ..................................................................................... 60
[Link] Creating the perspective .................................................................. 61
[Link] Configuring rules for the perspective ................................................ 61
[Link] Configuring the Overview tab ........................................................... 62
[Link] Configuring the Documents tab ........................................................ 63
[Link] Configuring the Vault tab ................................................................. 64
[Link] Configuring the Projects tab ............................................................. 65
[Link] Configuring the Related tab ............................................................. 66
[Link] Configuring the Reports tab ............................................................. 67
[Link] Configuring the ArcGIS Map tab ....................................................... 70
13.2.2 Making the Extended ECM for Engineering Connected Workspace
perspective available ....................................................................... 71
13.2.3 Enabling Connected Workspaces in Content Server core .................. 71
13.3 Updating terminology in the Search tile ............................................. 72

14 Extended ECM for Office 365 Widget Configuration ............ 73

14.1 Office 365 Information widget ........................................................... 73
14.2 Conversations widget ...................................................................... 73
14.3 Calendar widget .............................................................................. 73
14.4 Notebook widget ............................................................................. 73

15 Physical Objects Widget Configuration ................................ 75

15.1 Physical Objects Widget Configuration ............................................. 75
15.2 Physical Objects Reports Widget Configuration ................................. 75

16 Records Management Reports Widget Configuration ......... 77

17 Security Clearance Reports Widget Configuration .............. 79

18 Content Intelligence Widget Configuration ........................... 81

iv ActiveView Perspective Manager CSAV200300-APG-EN-01

 Table of Contents

18.1 Configuring the Nodes List WebReport Widget .................................. 82

18.1.1 To Configure the Nodes List WebReport Widget ............................... 83
18.2 Configuring the HTML WebReport Widget ........................................ 84
18.2.1 To Configure the HTML WebReport Widget ...................................... 85
18.2.2 Using Javascript in the HTML WebReport widget .............................. 86
[Link] Loading Smart UI SDK Modules ....................................................... 87
[Link] Commonly Used Third-Party Libraries .............................................. 87
18.2.3 Example Scripts for the HTML WebReport widget ............................. 87
[Link] Example 1: Using Standard Javascript ............................................. 88
[Link] Example 2: Using JQuery ................................................................ 88
[Link] Example 3: Using Marionette ........................................................... 89
18.2.4 Instructions to create a WebReport to return data for a Smart View
TABLEREPORT ............................................................................. 89
[Link] Method 1: Instructions to perform collection processing in the
WebReport ..................................................................................... 90
[Link] Method 2: Instructions to perform collection processing in the data
source ............................................................................................ 92
18.3 Configuring the Widget Carousel Widget .......................................... 97
18.3.1 To Configure the Widget Carousel Widget ........................................ 99
18.4 Configuring the Visual Count Widget .............................................. 100
18.4.1 To Configure the Visual Count Widget ............................................ 104
18.4.2 Choosing a Reportview Template ................................................... 105
18.4.3 Examples and Walkthroughs of How to Use the Visual Count Widget 107
[Link] Scenario 1: Simple Chart with Static Data ....................................... 107
[Link].1 Preparing to Visualize a Very Simple Chart ..................................... 108
[Link].2 Step-by-step Walkthrough for a Simple Chart with Static Data .......... 109
[Link] Scenario 2: Filter-enabled Chart ..................................................... 111
[Link].1 Preparing to Visualize a Basic, Filter-enabled Chart ........................ 112
[Link].2 Step-by-step Walkthrough for a Basic, Filter-enabled Chart ............. 114
[Link] Scenario 3: Filter-enabled Chart for Larger Data Sets (Application
Layer) .......................................................................................... 116
[Link].1 Preparing to Visualize a Filter-enabled Chart for Larger Data Sets ... 118
[Link].2 Step-by-step Walkthrough for a Filter-enabled Chart for Larger
Data Sets ..................................................................................... 119
[Link] Scenario 4: Filter-enabled Chart for Very Large Data Sets (Data
Layer) .......................................................................................... 121
[Link].1 Preparing to Visualize a Filter-enabled Chart from a Very Large
Data Set ....................................................................................... 122
[Link].2 Step-by-step Walkthrough for a Filter-enabled Chart from a Very
Large Data Set .............................................................................. 124
[Link] Scenario 5: Scheduled Data Chart for Very Large Data Sets (Data
Layer) .......................................................................................... 129
[Link].1 Preparing to Visualize a Scheduled Data Chart for Very Large Data
Sets ............................................................................................. 130

CSAV200300-APG-EN-01 OpenText™ Content Server v

Table of Contents

[Link].2 Step-by-step Walkthrough for a Scheduled Data Chart for Very

Large Data Sets ............................................................................ 130
18.4.4 Preparing WebReports for the Custom Buttons ............................... 134
[Link] Passing Parameters to a WebReport Associated with a Custom
Button .......................................................................................... 134
[Link] Custom Button Example: Export to a CSV File ................................ 136
[Link] Custom Button Example: Email Data to the User ............................. 138
[Link] Custom Button Example: Save a Snapshot of the JSON Data .......... 140
[Link] Custom Button Example: Change the Owner of Filtered Documents . 144

19 Workflow Widget Configuration ........................................... 147

19.1 Workflow Tracking Widget Configuration ........................................ 147
19.2 Workflow Monitoring Widget Configuration ...................................... 148

20 Extended ECM for SAP SuccessFactors Widget

Configuration ......................................................................... 149
20.1 Inbox widget ................................................................................. 149
20.2 My Team’s To-Dos widget ............................................................. 150
20.3 Employee workspace widget .......................................................... 151
20.3.1 Customizing Effective Date input option for document generation ..... 152
20.4 Tasks widget ................................................................................ 158
20.5 Activity Logs widget ....................................................................... 160
20.6 Document Self Service widget ....................................................... 163
20.7 Reports widget .............................................................................. 165
20.8 Create Documents widget .............................................................. 165
20.8.1 Configuring user name display ....................................................... 166

21 Extended ECM Platform Widget Configuration .................. 169

21.1 Business Attachments widget ........................................................ 169
21.2 Dossier widget .............................................................................. 171
21.3 Header widget with business object information .............................. 172
21.4 Scan barcode widget ..................................................................... 174

vi ActiveView Perspective Manager CSAV200300-APG-EN-01

 Part 1
Using the Perspective Manager
Chapter 1
Getting Started with perspectives

Important
• Starting from version 20.2, Content Server introduces a new perspective
node type. OpenText recommends all legacy ActiveView perspectives be
converted to use the new perspective node type.
• This system has not yet converted its legacy, ActiveView perspectives.
Although, you can temporarily continue to create and use ActiveView
perspectives, Content Server will eventually no longer support them.
• For information about how to convert ActiveView perspectives to use the
new perspective node type, see ActiveView Administration in the Classic
View Content Server Administration Help.

ActiveView perspectives allow you to control what various users see in the Content
Server Smart View interface. The Perspective Manager is a tool that allows you to
create and edit a perspective without needing to work in JSON format.

For details about more advanced tasks beyond creating and editing an ActiveView
perspective, see ActiveView Administration in the Classic View Content Server
Administration Help.

1.1 Understanding ActiveView perspectives

Important
Starting from Content Server 20.2, OpenText recommends that you convert all
ActiveView perspectives to use the new perspective node subtype. For
information about how to convert ActiveView perspectives to use the new
perspective node subtype, see ActiveView Administration in the Classic View
Content Server Administration Help.

For a given part of Content Server, such as a folder, a perspective allows you to
define which users will see a customized view, as well as what customizations those
users will see. You can select functional elements, known as widgets, place those
widgets on an area of the page, called a tile, and then rearrange the tiles on the page
to achieve a custom view.

Smart View starts with two unchangeable, default perspectives: one for the Landing
page and one for the container view. While you cannot edit these default
perspectives, you can create new perspectives to override the defaults. For details,
see “Create a new perspective“ on page 13.

Notes
• The Perspective Manager supports creating and editing a few basic
perspectives. For more advanced perspective customization work, see

CSAV200300-APG-EN-01 OpenText™ Content Server 9

Chapter 1 Getting Started with perspectives

Customizing Content Server Using ActiveView in the Content Server Help

available in the Classic View.

• If you choose to temporarily continue creating and using ActiveView

perspectives, be aware of the differences between them and the perspectives
that use the new perspective node type. For more information about these
differences, see “Differences between ActiveView perspectives and
perspectives that use the new perspective node type” on page 10.

• A perspective takes effect as soon as you create it.

• Advanced users, who have been assigned the appropriate object and usage
privileges can use the Edit Page tool in Smart View or the Perspective
Manager tool to edit an existing perspective if they have Modify permission
for that perspective.

• If you are unsure about your perspective configuration, consider applying it

on a test server, or only applying it locally, to a particular folder, or to a
limited set of users. For more information about limiting the impact of the
perspective, see “Choose a component“ on page 17 or “Define rules“
on page 21.

1.1.1 Differences between ActiveView perspectives and

perspectives that use the new perspective node type
Starting from version 20.2, Content Server introduces a new perspective node type.
OpenText recommends that you convert all ActiveView perspectives to use the new
perspective node subtype. For information about how to convert ActiveView
perspectives to use the new perspective node subtype, see ActiveView Administration
in the Classic View Content Server Administration Help.

“Differences between ActiveView Perspectives and Perspectives that Use the New
Perspective Node Type” on page 10 lists the differences between legacy,
ActiveView perspectives and those which use the new perspective node type. To
facilitate the future conversion running smoothly, you should keep these differences
in mind when creating a new ActiveView perspectives.

Table 1-1: Differences between ActiveView Perspectives and Perspectives that

Use the New Perspective Node Type

Feature ActiveView Perspectives Perspectives that Use the

New Perspective Node
Type
Global container The Perspective Manager tool The Perspective Manager tool
provides the option to create does not provide the option
global container perspectives. for a global container
perspective. Instead, it offers
the option to create global
Workspace perspectives.

10 ActiveView Perspective Manager CSAV200300-APG-EN-01

 1.1. Understanding ActiveView perspectives

Feature ActiveView Perspectives Perspectives that Use the

New Perspective Node
Type
Priority Low, Medium, and High Priority not supported.
priority values configurable
on the Manage Perspective
tab.
Cascade The Perspective Manager tool The Perspective Manager tool
only provides the Cascading only the Cascading and Non-
and Non-Cascading values. Cascading values.
But for local container
perspectives, multiple
cascade values configurable
on the Manage Perspective
tab.
Rules Custom rules possible by Custom rules are not
editing rules logic on the supported.
Manage Perspectives tab.
WebReports tags Custom WebReports tags Custom tags are not
possible by modifying code supported. Code Editor no
using the Code Editor. longer available from the
Perspective Manager.

CSAV200300-APG-EN-01 OpenText™ Content Server 11

Chapter 2
Create a new perspective

Important

• Starting from Content Server 20.2, OpenText recommends that you convert
all ActiveView perspectives to use the new perspective node subtype.
• This system has not yet converted its legacy, ActiveView perspectives.
Although, you can temporarily continue to create and use ActiveView
perspectives, Content Server will eventually no longer support them.
• For information about how to convert ActiveView perspectives to use the
new perspective node subtype, see ActiveView Administration in the Classic
View Content Server Administration Help.

Your permissions determine whether you can create a new ActiveView perspective.
An administrator can create unlimited new perspectives for a component. An
advanced user, who has the appropriate privileges, can use the Edit Page tool in
Smart View and the Perspective Manager for certain actions.

Note: If you delay converting to using the new perspective node type and
continue using ActiveView perspectives, you should review “Differences
between ActiveView perspectives and perspectives that use the new
perspective node type” on page 10. Keeping these differences in mind when
creating a new ActiveView perspectives will facilitate the future conversion
process running smoothly.

Tip: If you ended a previous Perspective Manager session without saving your
perspective changes, for example from a session time out, that perspective will
be cached in your browser. When you next launch Perspective Manager, you
must decide whether to clear that perspective work and start over or to resume
your configuration.

2.1 Create a new perspective

1. On the General tab, select the Create new option.

Important
Selecting Create new will clear all settings and you will lose all unsaved
changes in Perspective Manager.
2. In the Title box, enter the name of the new perspective.
3. Choose the component and the audience as follows:

a. Choose a component – Decide which part of Content Server will have a

custom view by applying the perspective. The component could be a

CSAV200300-APG-EN-01 OpenText™ Content Server 13

Chapter 2 Create a new perspective

container, like a Project, Task, or Folder, or it could be the Landing page,

which all users see after signing in, or it could be a Workspace. For details,
see “Choose a component“ on page 17.

Note: If you are unsure about your perspective configuration,

consider applying it on a test server, or only applying it locally, to a
particular folder, or to a limited set of users. For more information
about limiting the impact of the perspective, see “Choose a
component“ on page 17 or “Define rules“ on page 21.
b. Optional Define rules – Set logical conditions to control which users can see
the custom view. For example, you can limit the perspective to users on a
particular type of device, users who belong to a specific group, users
assigned to a specific role, or even to a specific user by name. For details,
see “Define rules“ on page 21.

Notes

• If you do not define a rule, then the perspective will apply to all
users on all devices.
• If you are unsure about your perspective configuration, consider
applying it on a test server, or only applying it locally, to a
particular folder, or to a limited set of users. For more information
about limiting the impact of the perspective, see “Choose a
component“ on page 17 or “Define rules“ on page 21.

Tip: To test the effect of the perspective, apply a rule such as user is
<user name> or group is <group name>, and then sign in as the
specified user or as a member of the specified group. Doing this
allows you to see how the perspective functions without affecting the
experience of other users.

4. Choose the layout and configuration as follows:

a. Choose a layout – Select a framework in which you can arrange tiles. For
details, see “Choose a layout“ on page 23.

Important
Changing the layout selection will clear any existing tile arrangements
and configurations.
b. Choose and configure widgets – Drag each widget to a tile, then arrange
the tiles within the framework, and configure the widget options. For
details, see “Choose and configure widgets“ on page 25.

5. Optional In the header of the Perspective Manager window, click Clear to reset all
settings, rules, layout, and widget choices.

Important

• You can only reset all settings before you save the new perspective.

14 ActiveView Perspective Manager CSAV200300-APG-EN-01

 2.1. Create a new perspective

• If you click Clear while editing an existing perspective, you will lose
any unsaved edits and will return to the General tab to start over by
either creating a new perspective or selecting an existing perspective to
edit.

6. In the header of the Perspective Manager window, click the Create button and
the new perspective will take effect immediately.

Notes

• Starting from Content Server version 20.2, the new perspective node
type does not support custom WebReports tags, so Perspective Manager
no longer provides access to the Code Editor tool.
• Perspective Manager will require you to provide any mandatory values
needed by any of the chosen widgets before creating the perspective.
Mandatory values are indicated by asterisks (*). If you attempt to save a
perspective without entering a mandatory value, you will be prompted
to provide the value before you can save the perspective. In a tabbed
perspective, you might need to check each tab to locate the field with the
mandatory value.

CSAV200300-APG-EN-01 OpenText™ Content Server 15

Chapter 3
Choose a component

On the General tab, the Type selection specifies the type of component that is
affected by the perspective. Your permissions determine which component you can
specify.

• Landing page
Landing pages are visible immediately after a user signs in. To see the Landing
page options for a perspective, see “What Landing page options can you
specify?” on page 18. If you want different users to see their own custom
landing page, you can create multiple Landing page perspectives, define
different rules for each perspective, and then define a custom layout
configuration for the applicable widgets.
• Container
To see the container options for a perspective, see “What Container options can
you specify?” on page 18. If you want different containers to have a custom
appearance for different users, you can create a perspective for each type of
container or for a specific instance of a container, define different rules for each
perspective, and then define a custom layout configuration for the applicable
widgets.
• Workspace
A perspective for a business workspace is associated to a workspace type that
you have configured for this component.
For more information about business workspaces and workspace perspectives,
see the Connected Workspaces Help in the Classic View.

Tips

– OpenText recommends that you create a workspace perspective using

the business workspace layout that is available when you open a
workspace type object from the workspace type folder and from the
General tab, click Manage Perspectives for this workspace type.
– You can edit an existing workspace perspective using either a default
version of Perspective Manager (launched from ActiveView
Administration > Open the Perspective Manager) or a workspace-
specific instance of Perspective Manager (launched from Enterprise >
Connected Workspaces >Workspace Type).
– To migrate a workspace perspective created using Content Server 16.2.9
or earlier to use the new 16.2.10 workspace component type, see the
Connected Workspaces Help in the Classic View.

See “Define rules“ on page 21 and “Choose and configure widgets“ on page 25.

CSAV200300-APG-EN-01 OpenText™ Content Server 17

Chapter 3 Choose a component

What Landing page options can you specify?

Title A name for the Landing page perspective.

Type Set the perspective type to Landing page.

Landing pages are not associated with a container, so the following

container-specific settings are not applicable and are ignored:
• Scope
• Container type
• Container
• Cascading

What Container options can you specify?

Title A name for the Container perspective.

Type Set the perspective type to Container.
Scope Regular administrators can select the extent of the perspective.
Delegated Administrators are limited to Local scope components.
• Global – Affects all containers of that type across the system when
seen in Smart View.
• Local – Affects only a specific instance of a container when seen in
Smart View.
Container-type Regular administrators can select the type of local container from the list.
Delegated Administrators are limited to the local container from which
they initiated the Edit Page command.
Container Regular administrators can click to browse Content Server to select the
specific instance of local container that you want.
Delegated Administrators can accept the autopopulated value for the local
container from which they initiated the Edit Page command in Smart
View.
Cascading For a local container, set whether the perspective will impact child objects
within the container.
• No – Affects only the container itself and none of the child objects.
• Yes – Affects the container and all child objects.

What Workspace options can you specify?

Title A name for the Workspace perspective.

18 ActiveView Perspective Manager CSAV200300-APG-EN-01

 Type Set the perspective type to Workspace.
For more information about business workspaces and workspace
perspectives, see the Connected Workspaces Help in the Classic View.

Tips
• OpenText recommends that you create a workspace perspective
using the business workspace layout that is available when you
open a workspace type object from the workspace type folder
and from the General tab, click Manage Perspectives for this
workspace type.
• To migrate a workspace perspective created using Content
Server 16.2.9 or earlier to use the new 16.2.10 workspace
component type, see the Connected Workspaces Help in the Classic
View.
Workspace Both regular administrators and delegated administrators can select either
Type all workspace types or a specific workspace type that you want.

Perspectives for business workspaces, which were created with version

16.2.9 or earlier, determine their respective workspaces type with a rule:
"[LL_REPTAG_SOURCEID WorkspaceTypeId /]" == "136"

Starting with version 16.2.10, this behavior has changed: Workspaces are
now a component, like containers or landing pages. The workspace type is
selected as a parameter for the override. If you experience performance
issues, you may consider changing your existing rule-based perspectives
into override-based perspectives.
Cascading Set whether the perspective will impact child objects within the
workspace.
• No – Affects only the workspace itself and none of the child objects.
• Yes – Affects the workspace and all child objects within the workspace.

Tip: At any point, you can click Clear on the header bar to reset all settings,
rules, layout, and widget configurations and automatically return to the
General tab to start over.
If you were creating a new perspective, nothing is saved and no new
perspective is created. If you were editing an existing perspective, you will lose
any unsaved changes.

CSAV200300-APG-EN-01 OpenText™ Content Server 19

Chapter 4
Define rules

On the Rules tab, you have the option to define simple rules or logical conditions.
The system evaluates the rules in first-to-last order to determine whether the
perspective takes effect and who will see it.

Notes

• Your role, your group membership, or your permissions may affect which
Perspective Manager options are available to you.
• If you do not define a rule, then the perspective will apply to all users on all
devices.
• Be sure that you define rules that are both valid and logically correct.

What conditions can you define with Rules?

Logical Join When adding a new rule, specify the logical join between the new rule
and the preceding rules.
Type Choose whether to evaluate the rule against a user condition or a device
condition.
• Device
• Mobile Device
• User
• Group
• User Privilege
• Workspace Template – only available for Workspace components

Operator Choose the logical operator to evaluate for the rule.

Value Enter a value or browse to find the appropriate value to evaluate against.
See “Available Values” on page 22

Tip: At any point, you can click Clear on the header bar to reset all settings,
rules, layout, and widget configurations and automatically return to the
General tab to start over.
If you were creating a new perspective, nothing is saved and no new
perspective is created. If you were editing an existing perspective, you will lose
any unsaved changes.

CSAV200300-APG-EN-01 OpenText™ Content Server 21

Chapter 4 Define rules

Table 4-1: Available Values

Type Values
Device Choose from the following devices:
• iPad
• iPhone
• Blackberry
• Playbook
• Android
• Windows Mobile

Mobile Device Specifies a generic non-browser perspective condition that

is set to true.
User Browse to find a user.
Group Browse to find a group.
User Privilege Choose from the following user privileges:
• Public Access enabled
• Can create/modify users
• Can create/modify groups
• User administration rights
• eDiscovery rights
• System administration rights

Workspace Template Browse to find a workspace template.

22 ActiveView Perspective Manager CSAV200300-APG-EN-01

Chapter 5
Choose a layout

Discrete functional elements of Smart View, known as widgets, must be placed in

page areas called tiles. On the Layout tab, you can choose a framework that controls
both the distribution of tiles for the perspective, such as columns, rows, or
wrapping. The layout determines the potential behavior of the tiles after they are
added to the perspective, such as whether or not the tiles will resize in response to a
change in page size.

Important

• The layout selection available depends on the component selected.

• Changing the layout selection will clear any existing tile arrangements and
configurations.

Which widget layout do you want?

The Flow layout allows tiles to follow each other sequentially. When
Flow adding widgets, each new widget is added to the next available tile space,
indicated by the dotted outline next to the last tile added.

Tile size is predetermined according to the widget selected. After all

widgets have been added, you can drag to rearrange the tiles. If space on a
row is limited, tiles will wrap to the next row.

Notes
• The Flow layout allows you to drag the tiles to rearrange them.
• Tile widths are fixed and predetermined according to the widget
selected.
• Tile height is automatically determined by the screen size.
The Left-Center-RightL layout provides three columns for widget
eft - Center - placement: a left sidebar, a central section, and a right sidebar.
Right
On smaller screens, the three columns condense into a single column. The
tile in the central section becomes topmost, with the left sidebar tile
directly underneath, and the right sidebar tile at the bottom.

Notes
• The Left-Center-Right layout does not support dragging to
rearrange already placed widgets. Instead, you must remove the
existing tile and drag the new widget in its place.
• Tile height and widths are predetermined to fill the slot.

Tip: At any point, you can click Clear on the header bar to reset all settings,
rules, layout, and widget configurations and automatically return to the
General tab to start over.

CSAV200300-APG-EN-01 OpenText™ Content Server 23

Chapter 5 Choose a layout

If you were creating a new perspective, nothing is saved and no new

perspective is created. If you were editing an existing perspective, you will lose
any unsaved changes.

24 ActiveView Perspective Manager CSAV200300-APG-EN-01

Chapter 6

Choose and configure widgets

On the Configure tab, you can drag functional elements, called widgets, from the
Widget Library pane to the tile outlines in the working area. Then, you can
rearrange the tiles holding those widgets and configure any required widget
options.

Some widgets might use the Perspective Assets volume to store items that are
automatically generated when a perspective is created. To create a perspective that
contains such a widget, you require Add Items permission to the Perspective Assets
volume. If you are the system administrator or have been granted permissions, you
can also manually add items to the Perspective Assets volume for use when
configuring widgets and perspectives. For more information, see the OpenText
Content Server Admin Online Help - ActiveView Administration (LLESAV-H-AGD).

Note: Your role, your group membership, or your permissions may affect
which Perspective Manager options are available to you.

How can you configure widgets?

Drag Widgets Drag widgets from the Edit Page pane to the empty tile outlines in the
work area.
Arrange Drag the widgets to change their order and placement, as permitted by the
Widgets layout.

Note: Remember that the layout you select can affect the
arrangement and size of the widgets. For more information, see
OpenText Content Server - Smart View User Help (CSSUI-H-UGD).
Configure Each widget may have zero or multiple configurable options. After you
Widgets drag the widget to the work area, click the widget to open the
configuration panel. For more information about the configuration options
for the different widgets, see OpenText Content Server - Smart View User
Help (CSSUI-H-UGD).
Remove a Click the Remove button to remove a widget from the current page.
Widget

Tip: At any point, you can click Clear on the header bar to reset all settings,
rules, layout, and widget configurations and automatically return to the
General tab to start over.
If you were creating a new perspective, nothing is saved and no new
perspective is created. If you were editing an existing perspective, you will lose
any unsaved changes.

CSAV200300-APG-EN-01 OpenText™ Content Server 25

Chapter 7
Edit an existing perspective

Depending on your privileges and permissions, you can edit a perspective using
either the Perspective Manager tool or the Edit Page tool in Smart View.

Notes

• Administrators have full use of both the Perspective Manager tool and the
Edit Page tool in Smart View.
• Advanced users who have the appropriate privileges and Modify permission
for a perspective, can use both the Perspective Manager tool and the Edit
Page tool in Smart View to edit a perspective if they have Modify permission
for that perspective.

Tip: If you ended a previous Perspective Manager session without saving your
perspective changes, for example from a session time out, that perspective will
be cached in your browser. When you next launch Perspective Manager, you
must decide whether to clear that perspective work and start over or to resume
your configuration.

7.1 Edit a perspective

To edit existing perspective, use the Perspective Manager as follows:

1. On the General tab, select the Edit existing option.

Important
If you are creating or editing a perspective, selecting Edit existing and
choosing an existing perspective will replace any unsaved configurations
with those from the selected perspective.

2. Click in the Browse box and select an existing perspective from the storage
location in Content Server.

Tip: At any point, you can click Clear on the header bar to reset all
settings, rules, layout, and widget configurations and automatically return
to the General tab to start over.
If you were creating a new perspective, nothing is saved and no new
perspective is created. If you were editing an existing perspective, you will
lose any unsaved changes.

3. Optional Edit the component or audience as follows:

a. Optional Edit the component – Edit which part of Content Server will be
affected by the perspective. The component could be a container, like a

CSAV200300-APG-EN-01 OpenText™ Content Server 27

Chapter 7 Edit an existing perspective

project, task, or folder, or it could be the Landing page, which all users see
after signing in. For details, see “Choose a component“ on page 17.

Note: If you are unsure about your perspective configuration,

consider applying it on a test server, or only applying it locally, to a
particular folder, or to a limited set of users. For more information
about limiting the impact of the perspective, see “Choose a
component“ on page 17 or “Define rules“ on page 21.
b. Optional Edit the rules – Change the logical conditions to control which users
can see the custom view. For example, you can limit the perspective to
users on a particular type of device, users who belong to a specific group,
users assigned to a specific role, or even to a specific user by name. For
details, see “Define rules“ on page 21.

Notes

• If you delete all the rules, then the perspective will apply to all
users on all devices.
• If you are unsure about your perspective configuration, consider
applying it on a test server, or only applying it locally, to a
particular folder, or to a limited set of users. For more information
about limiting the impact of the perspective, see “Choose a
component“ on page 17 or “Define rules“ on page 21.
4. Optional Change the tile layout and widget configuration as follows:

a. Optional Change the layout – Change the framework in which you can
arrange tiles. For details, see “Choose a layout“ on page 23.

Important
Changing the layout selection will clear any existing tile arrangements
and configurations.
b. Optional Choose and configure widgets – Drag widgets to new tiles,
rearrange the tiles within the framework, and configure the widget options.
For details, see .

Important
Perspective Manager will require you to provide any mandatory
values needed by any of the chosen widgets before creating or
updating the perspective.
5. Click Update.

Important
Perspective Manager will require you to provide any mandatory values
needed by any of the chosen widgets before creating or updating the
perspective.
6. In the warning dialog box, click Update. This warning applies to advanced
perspective customization work that can be performed in the Classic View and

28 ActiveView Perspective Manager CSAV200300-APG-EN-01

 7.1. Edit a perspective

which can affect multiple perspectives at the same time. For details, see
Customizing Content Server Using ActiveView in the Content Server Help available
in the Classic View. The perspective changes take effect immediately.

CSAV200300-APG-EN-01 OpenText™ Content Server 29

 Part 2
Configuring widgets
Chapter 8
Content Sharing Widget Configuration

This section provides information about the Content Sharing widgets.

8.1 My Shares and Manage Shares Configuration

Using the Content Sharing widget, you can make the My Shares and Manage
Shares tiles available to users. No additional configuration is required. On the My
Shares tile, users can access the shares that they initiated and are coordinator for on
the Initiated by me tab. They can access shares that they did not initiate but are
coordinators for on the Coordinated by me tab. They can access items that are
shared with them on the Shared to me tab. On the Manage Shares tile, users can
access the Shared items in an error state tab, where they can review shared items
that are in an error state and then attempt to resolve the issues. They can also see a
list of all shared items on the All shares tab.

For more information about enabling widgets in Perspective Manager, see the online
help for OpenText™ Content Server Perspective Manager.

For more information about working with the My Shares and Manage Shares tiles,
see the online user help for OpenText™ Content Server Smart View.

CSAV200300-APG-EN-01 OpenText™ Content Server 33

Chapter 9
Connected Workspaces Widget Configuration

9.1 Header widget

The Header widget displays metadata like the name of the business workspace and
important attributes. Metadata is taken dynamically from category attributes, node
properties, and business properties. You can also add static text, line breaks, tabs,
and spaces.

You can also embed another widget in the Header widget, currently only the
Activity Feed widget.

Workspace Properties
Workspace properties are displayed in the left part of the Header widget in the
following top-down order, with the font becoming smaller. You can use the
suggested properties, add others, and combine attributes and properties with
text.

Property Description
Title Name of the business workspace, prefilled
with the {name} node property.
Type Name of the workspace type, prefilled
with the {business_properties.
workspace_type_name} business
property.
Description Description of the business workspace,
prefilled with the {description} node
property.

• Business properties must be configured with the business_properties

prefix, for example {business_properties.workspace_type_name}.

– {business_properties.workspace_type_name}: Name of workspace

type.
– {business_properties.workspace_type_id}: ID of the workspace
type, useful for testing and preparing perspectives.
• Node properties require no prefix, for example {name}.

– {name}: Workspace name.

– {description}: The workspace node description.

– {type_name}: Name of the Content Server item type: Business

Workspace.

CSAV200300-APG-EN-01 OpenText™ Content Server 35

Chapter 9 Connected Workspaces Widget Configuration

– {create_date}: Date when business workspace was created, formatted

according to the current formatting rules.
– {create_user_id}: Name of the user who created the business
workspace, formatted to the user's readable display name.
– {modify_date}: Date when the business workspace was modified.
– {modify_user_id}: Name of the user who modified the business
workspace, formatted to the user's readable display name.
– {owner_group_id}: Name of the group the workspace owner belongs to.
– {owner_user_id}: Name of the workspace owner, formatted to the user's
readable display name.
• Category attributes
Click Add Attribute to Field and select attributes from the categories that
contain information for this business workspace. You cannot use attribute
sets for this.

Widget
You can embed another widget in the header widget. It depends on your
system, which widgets are available.

Property Description
Embed Widget Select one of the available widgets to
embed it into the header widget. It is
displayed in the right half of the header
widget. Currently available is the Activity
Feed widget, which displays all activities
in relation to this business workspace and
its related child workspaces. You see
comments or recently added documents.
If you want to use the Activity Feed
widget, you must enable Content Server
Pulse and, optionally, create activity
manager objects. For more information, see
OpenText Connected Workspaces -
Configuration Guide (CSCWS-CGD).

36 ActiveView Perspective Manager CSAV200300-APG-EN-01

 9.2. Related Workspaces widget

9.2 Related Workspaces widget

The Related Workspaces widget displays business workspaces that are related to the
currently opened business workspace. You must configure the widget in both
collapsed and expanded view. You can display business workspaces that are in a
parent relationship or in a child relationship, and you can have more than one
Related Workspaces widget in a perspective. Relations must be configured in
Content Server.

General

Property Description
Title Title of the widget, typically the
workspace type name in plain text.
Workspace type Workspace type of the related workspaces.
Relation type Child or Parent.

Collapsed view

Property Description
Message for empty result Custom message if no business
workspaces of this type are available.
Preview pane The preview pane is a window that opens
when you hover with the mouse over a
related workspace in the widget. The
preview pane contains additional
information as well as team members of
this business workspace.
• Preview title – Title of the preview
pane, for example the workspace type.
The title is displayed in small font
above the display name of the related
workspace.
• Message for empty metadata – Custom
message if there is no metadata to
display.
• Name of role – Name of the role whose
members are displayed in the preview.
• Message for empty role – Custom
message if there are no roles or team
members to display.
Message that is displayed if the
specified role has no members. The
default text is No role members
assigned.

CSAV200300-APG-EN-01 OpenText™ Content Server 37

Chapter 9 Connected Workspaces Widget Configuration

Property Description
Metadata in preview pane The preview pane uses data from category
attributes. You select a category or single
attributes. To group attributes, enter a
group name and then select the categories
and attributes. Leave the group name
empty to add a category or attribute
without a group. Drag attributes or groups
to change the order.
• Group name – Name of a group of
attributes or categories
• Category or attribute – Category or
single attributes. You can use the
following data sources: A single
attribute or a complete category with
all its attributes.
Order by Orders the list of related workspaces by a
custom column and defines the sort
direction. The default sorting is ascending
by the name of the business workspace.
If you have not selected a custom column
in the Order by option, the workspaces are
ordered by the custom column configured
in Related workspace title. And in this
case, you can only use custom columns
that are configured for ordering. If you
selected a custom column that is not
configured for ordering, an error message
is displayed when the widget is loaded.
For more information about configuration
of custom columns, see OpenText Connected
Workspaces - Configuration Guide (CSCWS-
CGD).
If you want to have the workspaces sorted
by another order than by name, you must
explicitely define the column and the sort
order in the order by section.
• Default is an order ascending by name.
• Sort ascending by the column that you
want to display as Title: select that
column as Title, do not specify
anything in the Order by field.
• Sort descending by the column that
you want to display as widget title:
select that column as Title, additionally
select this column in the Order by field,
and select the sort order Desc.

38 ActiveView Perspective Manager CSAV200300-APG-EN-01

 9.2. Related Workspaces widget

Property Description
Related workspace title Name of the related workspace. You can
use the following:
Variables: {name}. It uses the name of the
business workspace, which may already be
assembled from several attributes.
{modify_date}. For this, the custom
column for Workspace Modify Date
must be configured and have the Used for
Sorting and Filtering option enabled.
Custom columns if they have the Used for
Sorting and Filtering option enabled
Related workspaces description Description of the related workspace. You
can use the following:
Variables: {name}, {description},
{type_name}, {modify_date},
{create_date}
System Default Columns: {id}, {size},
or {type}
Custom columns if they have the Used for
Sorting and Filtering option enabled
Metadata fields Additional fields to display metadata in
the widget. Enter a label and the value,
which can be a custom column or one of
the following variables: {name},
{description}, {type_name},
{modify_date}, {create_date}. The
{name} variable uses the name of the
business workspace, which may already be
assembled from several attributes.
To format a custom column to be
displayed in currency format,
add :currency within in the brackets, for
example: {wnf_att_fl14_
5:currency}. With this format, zeros are
displayed and thousands separators are
added.

Expanded view

Property Description
Order by Orders the list of workspaces by a custom
column and defines the sort direction.

CSAV200300-APG-EN-01 OpenText™ Content Server 39

Chapter 9 Connected Workspaces Widget Configuration

Property Description
Custom columns Custom columns to be displayed in the
expanded view. Select a custom column,
then click Add to array. You can drag the
columns to change the order.
You can enable sorting by date in the
Related Workspaces widget. For this, you
create a custom column for the Workspace
Modify Date data source and configure it
to be sortable and used for sorting and
filtering. No further configuration is
required in the widget. For more
information, see OpenText Connected
Workspaces - Configuration Guide (CSCWS-
CGD).

9.3 Team widget

The Team widget displays team members as well as roles that have no members.

Property Description
Title Title of the Team widget. Default is Team.

Title Title of the Team widget. Default is Team.

9.4 Metadata widget

The Metadata widget displays attributes of the business workspace.

Property Description
Title Title of the Metadata widget. Default is
Metadata.
Hide empty fields Hide metadata fields that have no value.
Default is False.

40 ActiveView Perspective Manager CSAV200300-APG-EN-01

 9.5. Workspaces widget

Property Description
Metadata The Metadata widget uses data from
category attributes. You select a category or
single attributes. To group attributes, enter a
group name and then select the categories
and attributes. Leave the group name empty
to add a category or attribute without a
group. Drag attributes or groups to change
the order.
• Group name – Name of a group of
attributes or categories. You can use this
option to visually group attributes.
• Category or attribute – Category or
single attributes. To add an attribute,
select the category and then select the
attributes that you want to display.

Note: Metadata groups in the

Related Workspaces widget must
not contain complete attribute sets.
However, you can select single
attributes from an attribute set.
Attribute sets with multiple rows
are displayed as a table in the
Metadata widget. Make sure that
the table width does not exceed the
width of the widget.

9.5 Workspaces widget

The Workspaces widget displays workspaces of a certain type. Workspaces widgets
are typically used on a Home page. You can have more than one Workspaces
widget.

General

Property Description
Title Title of the Workspaces widget, typically
the type of business workspaces listed
here. Default is My workspaces.
Workspace type Type of business workspaces that you
want to display.

CSAV200300-APG-EN-01 OpenText™ Content Server 41

Chapter 9 Connected Workspaces Widget Configuration

Collapsed view

Property Description
Title Title of the Workspaces widget, typically
the type of business workspaces listed
here. Default is My workspaces.
Message for empty result Custom message if no business
workspaces of this type are available.

Expanded view

Property Description
Title Title of the Workspaces widget, typically
the type of business workspaces listed
here. Default is My workspaces.
Order by Orders the list of workspaces by a custom
column and defines the sort direction.
Custom columns Custom columns to be displayed in the
expanded view. Select a custom column,
then click Add to array. You can drag the
columns to change the order.
You can enable sorting by date in the
Workspaces widget. For this, you create a
custom column for the Workspace Modify
Date data source and configure it to be
sortable and used for sorting and filtering.
No further configuration is required in the
widget. For more information, see
OpenText Connected Workspaces -
Configuration Guide (CSCWS-CGD).

9.6 Configuration Volume widget

The Configuration Volume widget provides access to configuration volumes in
Smart View, for example the Document templates volume. The user needs sufficient
access rights to see the widget and make use of it.

42 ActiveView Perspective Manager CSAV200300-APG-EN-01

 9.7. Discussion widget

9.7 Discussion widget

The Discussion widget shows questions and answers for a selected Forum object.
This widget is intended for use with Connected Workspaces but is found in the
Communities widget group.

Notes

• You must associate the Discussion widget with a Forum object.

• You can either create that Forum object in the business workspace template
beforehand, or you can create the Forum object in the business workspace
after adding the Discussion widget to the perspective. By leaving the Forum
object parameter blank when you configure the Discussion widget, it will
automatically link to the Forum object in the workspace.
• For information about how to create a Forum, see OpenText Content Server -
Forums (LLESFOR-H-UGD).

For information about how to configure the Discussion widget, see OpenText Content
Server ActiveView Perspective Manager - Online Help (CSAV-H-APG). For information
about how to configure the frequency of notifications if a user chooses to follow a
topic, see OpenText Content Server Admin Online Help - Notifications Administration
(LLESWBN-H-AGD).

CSAV200300-APG-EN-01 OpenText™ Content Server 43

Chapter 10

Communities Widget Configuration

This section describes the use and configuration for the following Communities
widgets:

• “Discussion Widget Configuration” on page 45

10.1 Discussion Widget Configuration

The Smart View Discussion widget is intended for a business workspace, allowing
users to ask questions, provide answers to those questions, and search through
previously asked questions and their related answers. This widget stores data in a
Forum object. To include a Discussion widget in a business workspace, the
associated workspace template must include the associated Forum object.

Notes

• The Discussion widget is intended for use in a business workspace.

• Although both Perspective Manager and the Smart View Edit Page tool
allow you to configure the Discussion widget outside of the context of a
business workspace, such use is not supported.
• Keep in mind that this Smart View Discussion widget is associated with a
Classic View forum object not a Classic View discussion object.

Discussion widget prerequisites

Set notifications
To support the Follow feature in the Discussion widget, you must configure
notifications just as you would for a Forum in Classic View. For information
about how to configure the frequency of notifications if a user chooses to follow
a topic, see OpenText Content Server Admin Online Help - Notifications
Administration (LLESWBN-H-AGD).

Set elink
To support the Follow feature in the Discussion widget, you must configure
eLink just as you would for a Forum in Classic View. For information about how
to configure eLink, see Administering OpenText eLink - Content Server Admin
Online Help (LLESELK-H-AGD).

Create a new perspective

To add a Discussion widget to an existing business workspace, you must create
a new perspective for that business workspace and then add the Discussion
widget to that new perspective.

CSAV200300-APG-EN-01 OpenText™ Content Server 45

Chapter 10 Communities Widget Configuration

Discussion widget configuration parameters

Parameter Description
Width Choose the size that you want for the Discussion widget.
For the Overview tab of a business workspace, the recommended size is
single width.
Forum object To associate the widget with the Forum object in the business workspace,
leave this parameter empty and the widget will automatically link to the
forum. Typically, the administrator creates a new Forum object in the
business workspace or in the business workspace template.

Notes
• If the business workspace does not include a Forum object, the
Discussion widget will display a message that no discussion is
configured. If you later add a Forum, the Discussion widget will
automatically link to it.
• If there is more than one Forum object in the business workspace,
the Discussion widget automatically links to the oldest Forum.

To associate the widget with a Forum object outside of the business

workspace, browse Classic View Content Server to find the appropriate
Forum object.

For information about how to create a Forum, see OpenText Content Server
- Forums (LLESFOR-H-UGD).

46 ActiveView Perspective Manager CSAV200300-APG-EN-01

Chapter 11
Standard Widgets Configuration

This section describes the use and configuration for the following standard widgets:

• “Favorites Widget Configuration” on page 47

• “My Assignments Widget Configuration” on page 47
• “Node Browsing Table Widget Configuration” on page 47
• “Recently Accessed Widget Configuration” on page 47
• “Custom View Search Widget Configuration” on page 48
• “Search Results Widget Configuration” on page 48
• “Shortcut Group Widget Configuration” on page 48
• “Welcome Header Widget Configuration” on page 48
• “HTML Tile Widget Configuration” on page 49

11.1 Favorites Widget Configuration

Favorites is a single-width widget that shows favorite objects of the current user.

11.2 My Assignments Widget Configuration

My Assignments is a single-width widget that shows personal assignments of the
current user.

11.3 Node Browsing Table Widget Configuration

Node Browsing Table is a full-width widget that provides a tabular view on objects
stored in a container.

11.4 Recently Accessed Widget Configuration

Recently Accessed is a single-width widget that shows the documents accessed
recently by the current user.

CSAV200300-APG-EN-01 OpenText™ Content Server 47

Chapter 11 Standard Widgets Configuration

11.5 Custom View Search Widget Configuration

Custom View Search is a single-width widget that displays a search form for the
selected query. To configure the Custom View Search widget, you must have an
existing saved Search query in Content Server. The search parameters that appear in
the widget depend on the parameters specified in the search query.

11.6 Search Results Widget Configuration

Search Results is a full-width widget that displays the objects found in a full-text
search query. From the Search Results widget, users can perform any available
actions on the objects in the list of search results.

11.7 Shortcut Group Widget Configuration

Shortcut Group is a single-width widget that provides multiple hyperlinks to
Content Server objects. Clicking each link navigates to its corresponding target. You
must specify a target object, volume fallback, and display for each individual
shortcut in the group.

Shortcut Group Widget Configuration Parameters

Parameter Description
Theme Choose the background theme from the list.
Target object You must browse Content Server to find the target object to which you
want to link.
Volume Choose the volume fallback from the list. Possible values include the
fallback following:
• Enterprise
• Personal
• Categories
Display name Enter the name that you want to appear in the hyperlink text.

11.8 Welcome Header Widget Configuration

Welcome Header is a double-width widget that shows initial information for the
user home page.

Welcome Header Widget Configuration Parameters

Parameter Description
Display Enter the text string that you want to appear on the tile.
message

48 ActiveView Perspective Manager CSAV200300-APG-EN-01

 11.9. HTML Tile Widget Configuration

Video Provide the URL to the thumbnail image to be used for the video.
thumbnail
Video location Enter the URL for the location of the video.

11.9 HTML Tile Widget Configuration

HTML Tile is a single-width widget that displays HTML content in a perspective.
The HTML content is stored in a wiki container, called the Target wiki for HTML
Content. When you add the HTML Tile widget to a perspective, you can specify a
wiki to serve as the Target wiki for HTML Content, or let the perspective create one
automatically in the Perspective Assets volume.

Note: You need to have Add Items permission for the Perspective Assets
volume to add or configure an HTML Tile widget.

After adding the HTML Tile to a perspective, you can set permissions in the tile to
determine which groups can edit its contents. Users with Write permissions to the
tile can add content to it.

HTML Tile Widget Configuration Parameters

Widget size The size for the HTML Tile widget in the Flow layout: Single width,
Double width, or Full page.
Title The title that appears at the top of the HTML Tile.
Target wiki for The wiki container that the HTML tile will use to hold the wiki page that
HTML Content stores the HTML content created for the tile.
• If you do not specify a wiki, the HTML tile will automatically create a
wiki in the Perspective Assets folder in the Perspective Assets volume.
That wiki will include a wiki page to store the HTML content for the
tile. The HTML tile will also automatically use a Records Management
Cross-Reference to link the Perspective Assets folder and the
perspective that uses the tile,
• If you specify an existing wiki container as the target, the HTML tile will
automatically create a wiki page in the specified target wiki container.
The new wiki page will store the HTML content for the tile.

Note: In order for a wiki to be created in the Perspective Assets

volume, you must have write permissions to the volume. As well,
Records Management must be enabled in order for the XReference
properties tab that displays Cross-References between Perspectives
and Asset Folders to be visible. For more information about the
Perspective Assets volume, see Customizing Content Server Using
ActiveView in the Content Server Administration Help available in the
Classic View.

CSAV200300-APG-EN-01 OpenText™ Content Server 49

Chapter 11 Standard Widgets Configuration

Template wiki The wiki page to use as a template for the HTML Tile. Templates are
page (optional) preconfigured wiki pages that you can use as starting points for adding
content to HTML Tiles. You can select one of the prepared templates
stored in the Perspective Assets > TemplateAssets > HTML Widget
Templates wiki. If you do not select a template, the HTML Tile is created
as a blank page with the message your content goes here.

With the exception of the preconfigured wiki pages in the Perspective

Assets > TemplateAssets > HTML Widget Templates wiki, users can
specify any existing wiki page in Content Server as the template wiki
page. The HTML tile copies the content from the template wiki page to a
new wiki page, which is attached to the target wiki. Going forward, the
new wiki page is independent of the template wiki page that served as the
source.

If you do not specify a template, the HTML tile creates a new, blank wiki
page that it attaches to the specified target wiki container.

11.9.1 To Configure the HTML Tile Widget

To configure the HTML Tile widget:

1. Optional If you want to select a target wiki to store content for the HTML Tile,
create the wiki.

2. In the Perspective Manager, create a new perspective or edit an existing

perspective. For more information, see “Create a new perspective“ on page 13
or “Edit an existing perspective“ on page 27.

3. On the Configure tab, click to expand the Content Server UI Widgets group,
drag the HTML Tile widget onto the perspective, and set Options for the
widget. For more information, see “HTML Tile Widget Configuration”
on page 49. Click Create or Update to save the perspective.

4. Optional To set permissions, browse to the location where the perspective is

applied, click in the tile, and then click View Permissions. To add a user
or group, click Add in the column header. To edit permissions for a user or
group in the list, click the permission name in the Permission level column.

5. Optional To edit the HTML content, browse to the location where the perspective
is applied, click in the tile, and then click Edit. The available actions are a
subset of the actions available for editing wiki pages.

50 ActiveView Perspective Manager CSAV200300-APG-EN-01

Chapter 12
Collaboration Widget Configuration

This section describes the use and configuration for the following Collaboration
widgets:

• “Activity Feed Widget Configuration” on page 51

To use the Collaboration widgets, you must include and configure each widget in a
perspective. For more information about creating perspectives, see the OpenText
Content Server - ActiveView (LLESAV-H-UGD) or the Online Help available in the
Perspective Manager.

12.1 Activity Feed Widget Configuration

The Activity Feed widget can appear at the following locations in Smart View:

• By default, the Activity Feed widget always appears on the on the Following/
Followers tab of each User Profile.
• Depending on configuration, in Smart View, the Activity Feed widget can
optionally appear on a landing page perspective or at the container level
perspective. For more information about how you can use perspectives to
customize how users see Smart View, see OpenText Content Server Admin Online
Help - ActiveView Administration (LLESAV-H-AGD).
• If you have Connected Workspaces installed, you can embed the Activity Feed
widget into the Header widget of Connected Workspaces.

Important
You must have the following prerequisites in place before you can begin to
configure the Activity Feed widget:

• Content Server 16 should be installed and running.

• The Activity Feed widget must be included in a perspective.

After you have included the Activity Feed widget in your perspective, you can
configure the following parameters:

Activity Feed Widget Configuration Parameters

Wrapper Class
Enter the wrapper class to be applied to the activity feed list. If the wrapper class
is set to the Hero tile view/black theme, then the activity feed will also be black.
Feed Size
Enter the maximum number of feed items or posts to be included in each feed
page.

CSAV200300-APG-EN-01 OpenText™ Content Server 51

Chapter 12 Collaboration Widget Configuration

Default = 20
Important
The minimum feed size must be 10 or higher or else the scroll bar will not
be available and users may not be able to view all feed items.
Feed Type
Optional. Enter the type of feed. Possible values include status, content, and
attribute.
Default = all
Feed Settings
Select the following feed setting options:

• Enable Comments – Select whether or not you want to allow comment and
replies on the activity feed posts.
Default = True
• Enable Filters – Select whether or not you want to enable the end user to
filter the activity feed posts that appear on the tile when the tile is expanded.
If set to True, the ActivityFeed widget will show the activity feed based on
the feed source setting with the filter enabled. If set to False, the ActivityFeed
widget will show the feed based on the feed source without the filter.
Default = False

Honor Feed Source

Select whether or not the widget will consider Pulse as the source of the feed. If
set to true, the feed will use the current container or folder and its descendants
as the source. If set to false, the feed will use the source set in the perspective.
Default = False
Feed Source
Specify the non-Pulse source for the feed posts.

• Source – Enter the name of the source of the activity feed to be displayed on
the tile. Possible values include: all, node, and pulsefrom.

– All – Any activity done in Content Server.

– Node – Only the activities of that particular item appear.
– Pulsefrom – The activities of that particular item and all sub-items
appear.

Default = all
• Id – If the Source is configured to be node or pulsefrom, enter the object ID of
the source of the activity feed to be displayed on the tile.

Updates From
Choose the source to be used for the feed.

• From – Possible values include: all, iamfollowing, myfollowers, following,

followers, myupdates, mentions, myfavorites, user, group

52 ActiveView Perspective Manager CSAV200300-APG-EN-01

 12.1. Activity Feed Widget Configuration

Default = all
• Id – If From is set to following, followers, user, or group, then you must
specify the User ID or group ID of the applicable user or group.

Config Settings
Specify the widget-instance level configuration settings.

• Activity Feed Auto-refresh Wait – Specify the time interval, in milliseconds,

to refresh the activity feed.
Default = 60000

– In Classic View, Pulse automatically refreshes the activity feed with

newer posts or comments.
– In Smart View, Pulse notifies the user with an Update button to indicate
that newer posts or comments are available so that the user can choose
whether or not to update the activity feed.
• Maximum Message Length – Specify the number of characters for the
maximum length for a comment or reply to a post. If this value is not
explicitly configured for the widget, then it will default to the same values as
that set on the Pulse Administration page for the Max Length for Status
Msgs /Comments (140–4000 characters)
Default = 1000

Example 12-1:

An example of the configuration code for an Activity Feed widget might

appear as follows:
{"sizes":
{"sm": 6,"md": 6,"lg": 6}
,"widget": {"type": "esoc/widgets/activityfeedwidget",
"options": {
"feedsize": 20,
"feedtype":"status,attribute",
"feedsource":
{"source":"all"}
,
"feedSettings":
{"enableComments":true, "enableFilters" : true}
,
"updatesfrom":
{"from":"myfavorites"}
}}}
]}

CSAV200300-APG-EN-01 OpenText™ Content Server 53

Chapter 13

Extended ECM for Engineering Widget

Configuration

To configure Extended ECM for Engineering in Smart View, you can do the
following:

• Import the Extended ECM for Engineering search template used by the Search
tile. For more information, see OpenText Extended ECM for Engineering -
Administration Guide (LLESENG-AGD).
• Create an Extended ECM for Engineering perspective that contains the tiles you
want to display on the Smart View home page.
• Create an Extended ECM for Engineering Connected Workspace perspective that
defines the tiles that appear when a user accesses a Project or Connected
Workspace from the Workspaces tile.
• Import the Extended ECM for Engineering Search for Engineering Assignments
template used by the My Assignments tile. For more information, see OpenText
Extended ECM for Engineering - Administration Guide (LLESENG-AGD).

Note: Perspective templates to help with setup are packaged with Extended
ECM for Engineering. For more information, see OpenText Extended ECM for
Engineering - Administration Guide (LLESENG-AGD).

13.1 Configuring a Extended ECM for Engineering

perspective
OpenText recommends that you configure the following Extended ECM for
Engineering tiles (or widgets) to display on the home page of Content Server Smart
View:

• Create: Users can initiate Bulk Load processes and create new engineering
objects, such as Controlled Documents and Equipment Tags, from a central
location.
• Jobs: Users can view all processes that are running in the background, and they
can view details about the processes that have finished. You configure how long
processes are displayed on the tile.
• My Assignments: Users can view and complete ProcessFlow and Workflow
assignments.

Note: Extended ECM for Engineering uses a custom My Assignments tile.

Be sure to select the My Assignments widget in the Extended ECM for

CSAV200300-APG-EN-01 OpenText™ Content Server 55

Chapter 13 Extended ECM for Engineering Widget Configuration

Engineering Widget Library and not the My Assignments widget in the

Content Server UI Widget Library.
• Overdue Items: Users can view a snapshot of work items that are overdue and
complete required actions.
• Search: Users can search for existing engineering drawings, designs, references,
and other engineering objects stored in Content Server.

Note: OpenText recommends that you configure the Search tile to span two
columns on the home page. The double-column layout makes more of the
search fields visible in the tile by default, which means a user might not
have to scroll in the tile to perform a simple search.
• Workspaces: Users can access shared engineering Project folders and workspaces
for effective collaboration.

OpenText also recommends that you configure the following Content Server tiles to
display on the home page:

• Shortcut: OpenText also recommends that you configure this tile to point to the
Enterprise Workspaces, so users can quickly access information in the Enterprise
Workspace.
• Welcome Header: Users can quickly see information you customize to appear on
the tile.

13.1.1 Creating an Extended ECM for Engineering perspective

Tiles designed for Extended ECM for Engineering are stored in the Extended ECM
for Engineering area of the Perspective Manager Widget Library.

Tips

• For information about tiles in other areas of the Widget Library, see
OpenText Content Server ActiveView Perspective Manager - Online Help (CSAV-
H-APG).
• Perspective templates to help with setup are packaged with Extended ECM
for Engineering. For more information, see OpenText Extended ECM for
Engineering - Administration Guide (LLESENG-AGD).

To create an Extended ECM for Engineering perspective:

1. In the Controlled Revision Tracking Administration section of the Content

Server Administration page, click the Create Extended ECM for Engineering
Perspective link.

2. On the General Settings page, click Create new, then type a name for the
perspective in the Title box. For example, type xENG Perspective.

3. In the Type area, select whether this perspective is visible to users as the
Content Server home page or from a container in Content Server. OpenText

56 ActiveView Perspective Manager CSAV200300-APG-EN-01

 13.1. Configuring a Extended ECM for Engineering perspective

recommends you set the type as a Landing page for the Extended ECM for
Engineering perspective. Depending on the type, provide values for other
required options.
For more information, see OpenText Content Server ActiveView Perspective
Manager - Online Help (CSAV-H-APG).
4. Click the Configure tab.
5. In the Widget Library area, click Content Server UI Widgets, then do the
following:

a. Drag the Welcome Header widget to the active area.

b. Click the Welcome Header tile, then in the Options area, set the
information that will display in the tile on the home page.
6. In the Widget Library area, click Extended ECM for Engineering, then drag the
following widgets to the active area:

• Search
• Workspaces
• Create
• Jobs
• Overdue Items
• My Assignments

Tip: No additional configuration is required for the Workspaces, Create,

and Overdue Items widgets.
7. Click the Search tile and in the Options area, do the following:

a. Select Double width in the Widget size list.

b. Click Browse for the Search query box, navigate to the Search Engineering
Objects search template in the Enterprise workspace, then click the Select
link for the search template. For more information about the search
template, see OpenText Extended ECM for Engineering - Administration Guide
(LLESENG-AGD).
c. Select Double Column in the Layout Mode list.
8. Click the Jobs tile and, in the Filter Processes list in the Options area, select a
general date range for the background processes you want to display on the tile.
For example, you can display all background processes or only those processes
from the past day, past week, or the past month.
9. Click the My Assignments tile and in the Options area, do the following:

• In the Widget size list, select Quarter width.

• Click Browse for the Search query box, navigate to the Search Engineering
Assignments search template in the Enterprise workspace, and then click

CSAV200300-APG-EN-01 OpenText™ Content Server 57

Chapter 13 Extended ECM for Engineering Widget Configuration

the Select link for the search template. For more information about the
search template, see OpenText Extended ECM for Engineering - Administration
Guide (LLESENG-AGD).

Note: This is not a mandatory field and if a search query is provided,

users will get redirected to the custom view search results page that
lists all the documents.

10. In the Widget Library area, click Content Server UI Widgets, then drag the
following widgets to the active area:

• Single Shortcut
• Recently Accessed

Tip: No additional configuration is required for the Recently Accessed

widget.

11. Click the Single Shortcut tile and in the Options area, do the following:

a. Click Browse in the Target object box, then select the Enterprise
Workspace in Content Server.
b. Select Enterprise in the Volume fallback list.
c. Select a color in the Background list.

Figure 13-1: Extended ECM for Engineering perspective in Perspective

Manager

58 ActiveView Perspective Manager CSAV200300-APG-EN-01

 13.2. Configuring a Connected Workspace perspective

12. Click Create and then click Close.

13.1.2 Making the Extended ECM for Engineering perspective

available
To make the Extended ECM for Engineering perspective available to users, the
Extended ECM for Engineering perspective must be the ActiveView Template.

To make the Extended ECM for Engineering perspective the ActiveView

Template:

1. In the ActiveView Administration section of the Content Server

Administration page, click the Manage Global Perspectives link.
2. Depending on how you set up your perspective, on the Manage Global
Perspectives page, click either Container Perspectives or Landing Page
Perspectives. For the Extended ECM for Engineering perspective, the type
should be landing page. For more information, see Step 3.
3. Confirm that the Extended ECM for Engineering perspective you created
appears in the ActiveView Template area, then click Save Changes.

13.2 Configuring a Connected Workspace perspective

When you configure the Extended ECM for Engineering perspective, the
Workspaces tile appears on the Smart View home page. You must configure which
tiles display on the landing page of a Connected Workspace when a user selects a
Connected Workspace or a Project from the Workspaces tile. You also configure tabs
that display on the landing page of a Connected Workspace. After you configure the
Connected Workspace perspective, you must make it globally available.

OpenText recommends you configure the following tiles to display on the landing
page of a Connected Workspace that users access from the Workspaces tile:

• Project Header: Users can view metadata for the Project or Workspace including
information such as the start date, end date, and manager. Metadata is created
when the Project or Workspace is created.
• Create: Users can initiate Bulk Load processes and create new engineering
objects, such as Controlled Documents and Equipment Tags, from a central
location.
• My Assignments: Users can view and complete Workflow and ProcessFlow
assignments related to the current Project or Workspace.

Note: Extended ECM for Engineering uses a custom My Assignments tile.

Be sure to select the My Assignments widget from the Extended ECM for
Engineering Widget Library and not the My Assignments widget from the
Content Server UI Widget Library.
• Overdue Items: Users can view a snapshot of work items that are overdue and
complete required actions.

CSAV200300-APG-EN-01 OpenText™ Content Server 59

Chapter 13 Extended ECM for Engineering Widget Configuration

• Metadata: Users can view attributes of the current business Workspace.

• Team: Users can view team members that belong to the business Workspace, and
roles that have no members.

For more information about configuring these tiles, see “Configuring the Overview
tab” on page 62.

OpenText recommends you configure the following tiles to display on the tabs of the
Connected Workspace landing page:

• Vault: Users view revision information for Controlled Documents in the Vault
for the current Project or Workspace. For more information, see “Configuring the
Vault tab” on page 64.

• Projects: Users view and access projects for the current Project or Workspace. For
more information, see “Configuring the Projects tab” on page 65.

• Node Browsing Table: Users view and access all of the documents and objects
available for the current Project or Workspace. For more information, see
“Configuring the Documents tab” on page 63.

• Related Workspaces: Users quickly access additional Workspaces related to the

current Project or Workspace. For more information, see “Configuring the
Related tab” on page 66.

• Visual Count: Users view WebReport results. For more information, see
“Configuring the Reports tab” on page 67.

• ArcGIS Map: Users view and can drill-down in to a map of Projects for the
Program. For more information, see “Configuring the ArcGIS Map tab”
on page 70.

13.2.1 Creating the Extended ECM for Engineering Connected

Workspace perspective
Before you can create the Extended ECM for Engineering Connected Workspace
perspective, you must create one or more business workspace types. For information
about how to configure workspace types and map workspace types to your
Programs, see OpenText Extended ECM for Engineering - Administration Guide
(LLESENG-AGD).

The Vault tab and Projects tab in the Extended ECM for Engineering Connected
Workspace perspective display revision information for Controlled Documents. To
display this information on the Projects and Vault tabs, you must create and
configure required custom columns in the Facets Volume. OpenText recommends
you create the custom columns before you add the Projects and Vault widgets to
your Connected Workspace perspective. For more information about creating and
configuring custom columns, see OpenText Extended ECM for Engineering -
Administration Guide (LLESENG-AGD).

60 ActiveView Perspective Manager CSAV200300-APG-EN-01

 13.2. Configuring a Connected Workspace perspective

[Link] Creating the perspective

Tip: Perspective templates to help with setup are packaged with Extended
ECM for Engineering. For more information, see OpenText Extended ECM for
Engineering - Administration Guide (LLESENG-AGD).

To create the Extended ECM for Engineering Connected Workspace

perspective:

1. Click Connected Workspaces on the Enterprise menu.

2. Click Workspace Types and then click the workspace type you want to create
the Smart View perspective for.

3. On the Change Workspace Type page, in the Perspective Manager area, click
the Manage Perspectives for this workspace type link.

4. On the General Settings page of the Perspective Manager, select the Create
new option.

5. Type a name for the Extended ECM for Engineering Connected Workspace
perspective in the Title box. For example, type xENG CWS Perspective.

[Link] Configuring rules for the perspective

To configure rules for the Extended ECM for Engineering Connected
Workspace perspective:

1. With your Extended ECM for Engineering Connected Workspace perspective

open in Perspective Manager, click the Rules tab.

2. On the Rules page, confirm the rule Workspace Type is <Workspace_type_

name> appears. If the rule does not appear, do the following to create it:

a. Click the Add Rule button .

b. Select Workspace Type in the first list.
c. Select is in the second list.
d. Select the Workspace Type that you are creating the perspective for in the
third list.

3. To configure the rule xECM for Engineering is Business Workspace, do the

following:

a. Click the Add Rule button .

b. Select AND in the first list.
c. Select xECM for Engineering Project Type in the second list.
d. Select is in the third list.
e. Select Business Workspace in the fourth list.

CSAV200300-APG-EN-01 OpenText™ Content Server 61

Chapter 13 Extended ECM for Engineering Widget Configuration

[Link] Configuring the Overview tab

To configure the Overview tab in the Extended ECM for Engineering
Connected Workspace perspective:

1. With your Extended ECM for Engineering Connected Workspace perspective

open in Perspective Manager, click the Configure tab.

2. If the Connected Workspaces Header widget displays, click the widget, then
click the Remove button.

3. In the Widget Library area, click Extended ECM for Engineering and drag the
Project Header to the active area.

4. Click the Overview tab. If the Overview tab does not exist, click Add tab,
double-click in the new tab, and type Overview.

5. In the Widget Library area, click Extended ECM for Engineering and drag the
following widgets to the active area:

• Create
• Overdue Items
• My Assignments

6. To configure the width of the Extended ECM for Engineering widgets, click
each tile and then, in the Options area, select One third in the Width list.

Figure 13-2: Overview tab configuration in Perspective Manager

62 ActiveView Perspective Manager CSAV200300-APG-EN-01

 13.2. Configuring a Connected Workspace perspective

Tip: OpenText recommends you include the default Connected

Workspaces Team and Metadata tiles in the workspace perspective.
Resize the width of the Team and the Metadata tiles to optimize the
usability of the layout.

[Link] Configuring the Documents tab

For information about the display options for the Node Browsing Table tile, see
OpenText Content Server ActiveView Perspective Manager - Online Help (CSAV-H-APG).

To configure the Documents tab in the Extended ECM for Engineering

Connected Workspace perspective:

1. With your Extended ECM for Engineering Connected Workspace perspective

open in Perspective Manager, click the Documents tab. If the Documents tab
does not exist, click Add tab, double-click in the new tab, and type Documents.

2. In the Widget Library area, click Content Server UI Widgets and drag the
Node Browsing Table widget to the active area.

3. Click the Node Browsing Table tile and then, in the Options area, select Full in
the Width list.

4. Configure other options as required for the widget.

Figure 13-3: Documents tab configuration in Perspective Manager

CSAV200300-APG-EN-01 OpenText™ Content Server 63

Chapter 13 Extended ECM for Engineering Widget Configuration

[Link] Configuring the Vault tab

When configured, the Vault tab displays revision information for Controlled
Documents in the Vault for this Workspace. The Vault widget can only be
configured at the Program level. You must create custom columns for the revision
information to display on the Vault tab. For information about creating and
configuring custom columns, see OpenText Extended ECM for Engineering -
Administration Guide (LLESENG-AGD).

Note: OpenText recommends you create custom columns and add them to the
Program Vault before you add the Vault widget to your Connected Workspace
perspective.

To configure the Vault tab in the Extended ECM for Engineering Connected
Workspace perspective:

1. With your Extended ECM for Engineering Connected Workspace perspective

open in Perspective Manager, click Add tab.

2. Double-click the new tab and type Vault.

3. In the Widget Library area, click Extended ECM for Engineering and drag the
Vault widget to the active area.

4. Click the Vault tile and then, in the Options area, select Full in the Width list.

Figure 13-4: Vault tab configuration in Perspective Manager

64 ActiveView Perspective Manager CSAV200300-APG-EN-01

 13.2. Configuring a Connected Workspace perspective

[Link] Configuring the Projects tab

When configured, the Projects tab displays the projects for this Workspace. The
Projects widget can only be configured at the Program level. You must create
custom columns for the projects to display on the Projects tab. OpenText
recommends you create custom columns and add them to Program Project folders
before you add the Projects widget to your Connected Workspace perspective. For
more information about creating and configuring custom columns, see OpenText
Extended ECM for Engineering - Administration Guide (LLESENG-AGD).

To configure the Projects tab in the Extended ECM for Engineering Connected
Workspace perspective:

1. With your Extended ECM for Engineering Connected Workspace perspective

open in Perspective Manager, click Add tab.

2. Double-click the new tab and type Projects.

3. In the Widget Library area, click Extended ECM for Engineering and drag the
Projects widget to the active area.

4. Click the Projects tile and then, in the Options area, select Full in the Width list.

Figure 13-5: Projects tab configuration in Perspective Manager

CSAV200300-APG-EN-01 OpenText™ Content Server 65

Chapter 13 Extended ECM for Engineering Widget Configuration

[Link] Configuring the Related tab

For information about the options for the Related Workspaces tile, see OpenText
Content Server ActiveView Perspective Manager - Online Help (CSAV-H-APG).

To configure the Related tab in the Extended ECM for Engineering Connected
Workspace perspective:

1. With your Extended ECM for Engineering Connected Workspace perspective

open in Perspective Manager, click Add tab.
2. Double-click the new tab and type Related.

3. In the Widget Library area, click Connected Workspaces and drag the Related
Workspaces widget to the active area.

4. Click the Related Workspaces tile and then, in the Options area, select Full in
the Width list.

5. Select a Workspace type and a Relation type.

Figure 13-6: Related tab configuration in Perspective Manager

66 ActiveView Perspective Manager CSAV200300-APG-EN-01

 13.2. Configuring a Connected Workspace perspective

[Link] Configuring the Reports tab

On the Reports tab, users view and use the View Percentage Completion Report in
Content Server Smart View. Configuring the Export button for this report lets users
export the report to a CSV file. For more information about this report, see OpenText
Extended ECM for Engineering - User Help (CSENG-H-UGD). For more information
about the display options for the Visual Count tile, see OpenText Content Server
ActiveView Perspective Manager - Online Help (CSAV-H-APG).

To configure the Reports tab in the Extended ECM for Engineering Connected
Workspace perspective:

1. With your Extended ECM for Engineering Connected Workspace perspective

open in Perspective Manager, click Add tab.

2. Double-click the new tab and type Reports.

3. In the Widget Library area, click Content Intelligence and drag the Visual
Count widget to the active area.

Note: For configuring the Active Documents based on Revision Types

report in the landing page, select the Extended ECM for Engineering
Landing page perspective in Perspective Manager and drag the Visual
Count widget to the active area.

4. To display the ProcessFlow Percentage Completion Report, click the Visual

Count tile, and then in the Options area, do the following:

a. In the Width list, select Full.

b. In the Title box, type a descriptive title for the visual report.
c. In the Chart Type list, select the type of chart that is used to display the
information.
d. To specify the source WebReport for the tile, do the following:

1. Click Browse in the Source WebReport area.

2. Go to the Reports folder in the Enterprise Workspace, and then select
the appropriate WebReport in the ProcessFlow Percentage Completion
Reports folder. For more information, see OpenText Extended ECM for
Engineering - Administration Guide (LLESENG-AGD).
e. In the Active Column box, type the active column name to include in the
report. For Programs, select one of the following:

• Project
• ProcessFlow
• State
• Revision Type

For Projects, select one of the following:

CSAV200300-APG-EN-01 OpenText™ Content Server 67

Chapter 13 Extended ECM for Engineering Widget Configuration

• ProcessFlow
• State
• RevisionType
f. Specify values for Values as Percentage, Group After, Sort By, Sort
Direction, Chart Options, and Expanded View.
g. To specify a button to display on the WebReport, do the following:

1. Click Button WebReports.

2. Click Custom Buttons.
3. In the Button WebReport area, click Browse.
4. Go to the ProcessFlow Percentage Completion Reports folder located
in the Reports folder in Enterprise Workspace, and then click the
Export Button WebReport.
h. In the Button Label box, type Export.
i. In the Button Tooltip box, type the sample text that appears when a user
points to the custom button.

Figure 13-7: Reports tab configuration in Perspective Manager

5. To display the Active Documents based on Revision Types report, click the
Visual Count tile, and then in the Options area, do the following:

a. In the Width list, select Full.

b. In the Title box, type a descriptive title for the visual report.

68 ActiveView Perspective Manager CSAV200300-APG-EN-01

 13.2. Configuring a Connected Workspace perspective

c. In the Chart Type list, select the type of chart that is used to display the
information.
d. To specify the source WebReport for the tile, do the following:

i. Click Browse in the Source WebReport area.

ii. Go to the Reports folder in the Enterprise Workspace, and then do the
following:

• For the Program Business Workspace and landing page, select

Report for Program for Active Documents and for the Project
Business Workspace, select Report for Project for Active
Documents. For more information, see OpenText Extended ECM for
Engineering - Administration Guide (LLESENG-AGD).
e. In the Active Column box, type the active column name to include in the
report. For Programs and landing page, select one of the following:

• Program
• Revision Type
• Project

For Projects, select one of the following:

• Project
• RevisionType
f. Specify values for Values as Percentage, Group After, Sort By, Sort
Direction, Chart Options, and Expanded View.
g. To specify a button to display on the WebReport, do the following:

1. Click Button WebReports.

2. Click Custom Buttons.
3. In the Button WebReport area, click Browse.
4. Go to the Active Documents based on Revision Types Reports folder
located in the Reports folder in Enterprise Workspace.
h. Select the Export Button for Active Documents Report WebReport.
i. In the Button Label box, type Export.
j. In the Button Tooltip box, type the sample text that appears when a user
points to the custom button.
k. In the Source Parameters section, perform either of the following:

• Type Revision_Types in the Parameter Name box and enter the name
of a revision type in the Parameter Value box.
• Type Days_in_RevisionTypes in the Parameter Name box and enter
the number of days in the Parameter Value box.

CSAV200300-APG-EN-01 OpenText™ Content Server 69

Chapter 13 Extended ECM for Engineering Widget Configuration

[Link] Configuring the ArcGIS Map tab

On the ArcGIS Map tab, users can view and drill-down into maps for their
Programs and Projects in Content Server Smart View. To make ArcGIS map
information available on this tab, you must apply the Geo Info Category to your
Programs and Projects. For more information, see OpenText Extended ECM for
Engineering - Administration Guide (LLESENG-AGD).

To configure the ArcGIS Map tab in the Extended ECM for Engineering
Connected Workspace perspective:

1. With your Extended ECM for Engineering Connected Workspace perspective

open in Perspective Manager, click Add tab.

2. Double-click the new tab and type ArcGIS Map.

3. In the Widget Library area, click ESRI ArcGIS Integration and drag the
ArcGIS Map widget to the active area.

4. Click the ArcGIS Map tile and then, in the Options area, select Full in the
Width list.

Figure 13-8: ArcGIS Map tab configuration in Perspective Manager

5. Click Create, then click Close.

70 ActiveView Perspective Manager CSAV200300-APG-EN-01

 13.2. Configuring a Connected Workspace perspective

13.2.2 Making the Extended ECM for Engineering Connected

Workspace perspective available
To make the Extended ECM for Engineering Connected Workspace perspective
available to users, the perspective must be the ActiveView Template. After you
make the perspective the ActiveView Template, when a user clicks a Connected
Workspace or Project on the Workspaces tile, the Extended ECM for Engineering
Connected Workspace perspective appears.

To make the Extended ECM for Engineering Connected Workspace

perspective the ActiveView Template:

1. In the ActiveView Administration section of the Content Server

Administration page, click the Manage Global Perspectives link.

2. On the Manage Global Perspectives page, click Container Perspectives.

3. Confirm that the perspective you created appears in the ActiveView Template
area, then click Save Changes.

13.2.3 Enabling Connected Workspaces in Content Server

core
Connected Workspaces and the underlying Template Workspaces modules are
installed with the Content Server core package. However, before you can configure
these modules, you must enable them on the Content Server Administration page.
Also, ensure that your license plan includes both modules. After you enable these
modules, you cannot revert the changes.

Note: You must restart Content Server core after you enable the Connected
Workspaces and Template Workspaces modules.

To enable the Connected Workspaces and Template Workspaces modules:

1. On the Content Server Administration page, click Connected Workspaces >

Enable Connected Workspaces.

2. Click Enable Template Workspaces and Connected Workspaces features.

3. Enter your name as a signature and confirm that you have read the terms of
usage and have a valid license in place.

4. Click Save Changes.

5. Restart Content Server core.

CSAV200300-APG-EN-01 OpenText™ Content Server 71

Chapter 13 Extended ECM for Engineering Widget Configuration

13.3 Updating terminology in the Search tile

The Search tile in Extended ECM for Engineering uses the term Program. In previous
versions of Engineering Document Management, the Search Engineering Objects
tile used the term Organization Segment. If you are an existing Engineering Document
Management customer, upgrading to Extended ECM for Engineering, update
CRTEntityID in the Search Region of Content Server to use the current terminology.

For more information about updating Search Regions, see OpenText Content Server -
Administering Search (LLESWBS-AGD).

To update terminology in the Search tile:

1. In the Search Administration section of the Content Server Administration

page, click the Open the System Object Volume link.

2. Click Enterprise Data Source Folder.

3. Click the Functions menu of Enterprise Search Manager, click Properties, then
click Regions.

4. On the Enterprise Search Manager page, find CRTEntityID.

5. In the Display Name box, delete Organization Segment and type Program.

6. Click Update.

72 ActiveView Perspective Manager CSAV200300-APG-EN-01

Chapter 14
Extended ECM for Office 365 Widget Configuration

If the OpenText Extended ECM for Microsoft Office 365 module is installed,
Extended ECM for Office 365 widgets are available in Perspective Manager.

To make the widgets available to users, you must configure a new perspective for a
business workspace type and then add the widgets to that perspective. For more
information, see OpenText Extended ECM for Microsoft Office 365 - Installation and
Configuration Guide (CSSOG-ICG).

14.1 Office 365 Information widget

You can use the Office 365 Information widget to manage connections to Office 365
groups or Microsoft teams. For example, you can use this widget to connect a
business workspace to a group or team, view information about the connected
group or team, and remove the connection to a group or team.

14.2 Conversations widget

The Conversations widget displays email conversations from the shared inbox of the
Office 365 group or Microsoft team that is connected to a business workspace.

14.3 Calendar widget

The Calendar widget displays events from the shared calendar of the Office 365
group or Microsoft team that is connected to a business workspace.

14.4 Notebook widget

You can use the Notebook widget to open the shared notebook of the Office 365
group or Microsoft team that is connected to a business workspace.

CSAV200300-APG-EN-01 OpenText™ Content Server 73

Chapter 15

Physical Objects Widget Configuration

To use the Physical Objects widgets, you must include and configure each widget in
a perspective. There are two types of Physical Object widgets and they are grouped
separately in the Perspective Manager Widget Library:

• Physical Objects – to display borrowed and requested physical items. These

widgets are available by default.
• Physical Objects Reports – to display pre-configured WebReports. These widgets
are available if Physical Objects reports are installed.

For more information about creating perspectives, see the OpenText Content Server -
ActiveView (LLESAV-H-UGD) or the Online Help available in the Perspective
Manager.

15.1 Physical Objects Widget Configuration

The following information about Physical Objects can be configured to display as
widgets in Smart View:

• My borrowed physical items – displays a list of the user’s borrowed Physical

Items. The expanded view of this tile allows the user to see additional circulation
metadata and to perform the Acknowledge and Flag for Pick Up actions.
• My requested physical items – displays a list of the user’s requested Physical
Items. The expanded view of this tile allows users to see additional request-
specific metadata and to perform the Cancel Request action.

15.2 Physical Objects Reports Widget Configuration

Physical Objects provides pre-configured WebReports, which can be used in
conjunction with the Perspective Manager, to display information as a widget in
Smart View.

The following Physical Objects reports can be configured to display as widgets in

Smart View:

• Physical Item Summary – provides a dashboard view of Physical Items in the

system. Users can sort by Physical Item type, Home Location, or Facility.
• Circulation Statistics – provides an overview of the number of Physical Items
borrowed, requested to borrow, waiting for acknowledgement, overdue,
returned, or flagged for pickup. You can click the active links for any of the
Circulation Statistics to view a list of items that are included in the statistic.

CSAV200300-APG-EN-01 OpenText™ Content Server 75

Chapter 15 Physical Objects Widget Configuration

• Storage Management – provides an overview of how the storage space is used.

Users can sort the results to see how much space is taken up overall, by Facility,
Area, or Locator.
• Transfers – provides an overview of the total number of Transfers, the number of
Transfers that have been sent or received, and the number of Transfers that were
sent but not received. Clicking a link from Transfers widget will redirect you to
the Transfers page in the Physical Objects Workspace (in Classic View).

76 ActiveView Perspective Manager CSAV200300-APG-EN-01

Chapter 16
Records Management Reports Widget
Configuration

Records Management provides pre-configured WebReports, which can be used in

conjunction with the Perspective Manager, to display information about managed
objects and Dispositions as a Widget in Smart View. For more information about
other available Widgets for Content Server Smart View, see the OpenText Perspective
Manager Online Help.

The following Records Management reports can be configured to display in Smart

View:

• Disposition actions pending – provides statistical information for Dispositions

that have actions pending. The widget enables you to see total counts based on
the Disposition actions (for example, Change Status, Delete Electronic, Mark
Official, Finalize Record). Users can refine the search results or sort and group
the results in whatever manner is useful to them. The Go to Dispositions button
takes users directly to the Records Management Dispositions folder in Classic
View.
• Managed objects statistics – provides statistics for managed objects based on
their statuses, RSIs, Official markings, and Essential record values. Users can
refine the search results, view the list of managed objects in Classic View, or send
to Search Results.

CSAV200300-APG-EN-01 OpenText™ Content Server 77

Chapter 17
Security Clearance Reports Widget Configuration

Security Clearance provides pre-configured WebReports, which can be used in

conjunction with the Perspective Manager, to display information for Security
Clearance as a Widget in Smart View. For more information about other available
Widgets for Content Server Smart View, see the OpenText Perspective Manager Online
Help.

The following Security Clearance reports can be configured to display as widgets in

Smart View:

• Supplemental Markings on objects – shows the number of items that have a

Supplemental Marking applied.
• Security Clearance on objects – shows the number of items that have a Security
Clearance Level applied.

CSAV200300-APG-EN-01 OpenText™ Content Server 79

Chapter 18
Content Intelligence Widget Configuration

This section describes the use and configuration for the Content Intelligence
widgets.

Note: You will need to have a valid WebReports license to see the Content
Intelligence widgets.

• Nodes List WebReport Widget

This widget shows an expandable list of data, such as a list of documents that
share a common metadata tab, based on a specified WebReports data source.
For more information, see “Configuring the Nodes List WebReport Widget”
on page 82.
• HTML WebReport Widget
This widget allows developers to show formatted text and images in a Smart
View widget.
For more information, see “Configuring the HTML WebReport Widget”
on page 84.
• Widget Carousel Widget
This widget allows you to display up to ten different slides in the space of one
Smart View tile.
For more information, see “Configuring the Widget Carousel Widget”
on page 97.
• Visual Count Widget
This widget helps visualize quantifiable data as a chart on a tile in Smart View.
For more information, see “Configuring the Visual Count Widget” on page 100.

To use the Content Intelligence widgets, you must include and configure each
widget in a perspective. For more information about how to create a perspective, see
the Online Help available in Perspective Manager.

Note: Any WebReport that you intend to display in the Smart UI cannot
contain custom parameters. Custom parameters can only be displayed in the
Classic UI. By default, any custom parameter screen executed from the Smart
UI will run in the Classic UI. A custom parameter is created on the Parameters
tab when you select “Custom” from the Type list.

CSAV200300-APG-EN-01 OpenText™ Content Server 81

Chapter 18 Content Intelligence Widget Configuration

18.1 Configuring the Nodes List WebReport Widget

The Nodes List WebReport widget shows an expandable list of data, such as a list of
documents that share a common metadata tab, based on a specified WebReports
data source. Similar to the standard Content Server Favorites widget, the Nodes List
WebReport widget supports scrolling and name filtering. This widget uses the
WebReports REST API along with the INSERTJSON content control tag and the
@NODESTABLEFIELDS directive to call the specified WebReport based on the Nodes
List WebReport Widget - Report JSON default reportview to return correctly
formatted JSON data. Additional tags within the template support sorting, filtering,
formatting, and pagination, and respond to parameters passed in by the client. For
more information about the @NODESTABLEFIELDS directive, and other directives that
specify WebReports Smart UI reports output, see the INSERTJSON tag.

End users can expand the tile containing the Nodes List WebReport widget to see a
full table view of the nodes. When expanded, the nodes table shows additional
columns of data, such as Type, Name, Size, and Modified. Similar to the standard
Smart View browse view, the expanded widget allows users to filter on name, sort
by column, and view the properties for each node.

Note: The expanded Nodes List WebReport widget does not replicate all
Smart View browse behavior. For example, the columns shown are only a static
subset of the default: neither the facet bar, nor the multi-action bar is shown.

After you have included the Nodes List WebReport widget in your perspective, you
can configure the following parameters:

Nodes List WebReport Widget Configuration Parameters

Title
Optional. Enter the title for the tile. Typically, this would describe the
WebReport that you are rendering.
Icon Class
Optional. Provide the CSS class for the icon that you want to appear in the top
left corner. For example: <Content ServerInstallDir>/support/csui/
themes/carbonfiber/[Link] contains icons such as title-assignments,
title-customers, title- favourites, title-opportunities, title-
recentlyaccessed, title-activityfeed, title-customviewsearch.
Default = title-webreports
Search Placeholder
Optional. Enter a custom string that will appear when the user clicks Search.
Default value = “Search NodesList Report.”
WebReport ID
Mandatory. Enter the ID for the WebReport that you want to appear on the tile.

Note: The WebReport provided must be based on the default WebReports

template for Nodes List WebReport Widget - Report JSON.

82 ActiveView Perspective Manager CSAV200300-APG-EN-01

 18.1. Configuring the Nodes List WebReport Widget

WebReports Parameters
Optional. Enter one or more “name”-“value” pairs for the parameters that you
want to pass into the WebReport.

18.1.1 To Configure the Nodes List WebReport Widget

To configure the Nodes List WebReport widget:

1. Create a new WebReports node using the Nodes List WebReport Widget -
Report JSON default reportview. For information about how to create a
WebReport, see OpenText Content Server - WebReports (LLESWEBR-H-UGD).

2. On the Source tab, set the data source of the WebReport to the database source
that contains a column called DataID, which references valid nodes that you
want to display in the widget. For more information about how to set the data
source, see OpenText Content Server - WebReports (LLESWEBR-H-UGD).

3. On the Content Server Administration > ActiveView Administration page,

click the Open the Perspective Manager link.

4. In the Perspective Manager, create a new perspective or edit an existing

perspective. For more information about how to create a new perspective or
how to edit a perspective, see the Online Help available in the Perspective
Manager.

5. On the Configure tab, do the following:

a. In the Widget Library pane, click to expand the Content Intelligence

widget group and drag the Nodes List WebReport widget to the page.
b. To open the configuration options, select the Nodes List WebReport
widget on the page.
c. In the Options pane, in the WebReport ID box, add the WebReport created
in Step 1 and edited in Step 2.

Note: For more information on the options available for the Nodes
List WebReport widget, see Nodes List WebReport Widget
Configuration Parameters on page 82.

6. Navigate to the location where the new perspective is applied to verify the
Nodes List WebReport widget output.

CSAV200300-APG-EN-01 OpenText™ Content Server 83

Chapter 18 Content Intelligence Widget Configuration

18.2 Configuring the HTML WebReport Widget

The HTML WebReport widget allows developers to show formatted text and images
in a Smart View widget. This widget calls a specified WebReport using the
WebReports Rest API and inserts the HTML output of the WebReport into the tile at
runtime.

Notes

• This widget supports HTML and CSS. For the 16.0.3 release and onwards,
this widget will also support Javascript. For releases prior to 16.0.3,
Javascript is not supported.
• Be sure to avoid style conflicts with the Content Server Smart View user
interface framework or any other widgets on the page.

The following sample reportview templates provide examples of how to construct

the HTML output of the WebReport content to avoid conflicts. They show how to
use CSS selectors to avoid style conflicts, images and icons, HTML tables and
dynamic data insertion using WebReports tags, including the new [LL_REPTAG_
WIDGETCONTAINERID /] data tag which can be used to obtain the ID current
container. They also include examples of how to make page elements responsive. It
is important to avoid including unresponsive content. For instance, inserting an
image with a fixed width will mean that when the page is resized or viewed on a
mobile device the page flow may not adjust as desired.

• HTML WebReport Widget - Image and Icons Report

• HTML WebReport Widget - Responsive Table Report

Important
Although these templates include examples using the bootstrap library,
OpenText does not officially support this library. If you use this library, you
must consult the published documentation. In addition, the Content Server
Smart View implements a customized version of bootstrap. It is expected that
in some cases the Smart View version of bootstrap will diverge from the
publicly documented behavior. In a post-Content Server 16 update, OpenText
will provide developer documentation with style guidelines as well as the
Smart View UI SDK.

After you have included the HTML WebReport widget in your perspective, you can
configure the following parameters:

HTML WebReport Widget Configuration Parameters

Widget Size
Mandatory. Select the size for the HTML WebReport widget in the Flow layout:
Single width, Double width, or Full Page.
Default = Double width.

84 ActiveView Perspective Manager CSAV200300-APG-EN-01

 18.2. Configuring the HTML WebReport Widget

Title
Optional. Enter the title for the tile. Typically, this would describe the
WebReport that you are rendering.
Default title = HTML WebReport

Icon Class
Optional. Provide the CSS class for the icon that you want to appear in the top
left corner. For example: support/csui/themes/carbonfiber/[Link]
contains icons such as title-assignments, title-customers, title-
favourites, title-opportunities, title-recentlyaccessed, title-
activityfeed, title-customviewsearch.
Default = title-webreports

Note: You can specify a custom icon within the WebReport template by
adding a CSS selector that uses background-image and then referencing
the selector in this option.

Header
Optional. Select the option for whether the tile will include a header area that
contains the title and title icon.
Default = True.

Scroll
Optional. Select the option for whether users can scroll through the content on
the tile. If scrolling is disabled, content will be truncated.
Default = True.

WebReport ID
Mandatory. Enter the ID for the WebReport that you want to appear on the tile.

Note: The WebReport provided must follow the HTML construction

guidelines and be based on either a blank template or one of the sample
WebReports templates, HTML WebReport Widget - Image and Icons
Report or HTML WebReport Widget - Responsive Table Report.

WebReports Parameters
Enter one or more “name”-“value” pairs for the parameters that you want to
pass into the WebReport.

18.2.1 To Configure the HTML WebReport Widget

To configure the HTML WebReport widget:

1. Create a new WebReport node using the blank reportview, the HTML
WebReport Widget - Image and Icons Report template, or the HTML
WebReport Widget - Responsive Table Report template. For information
about how to create a WebReport, see OpenText Content Server - WebReports
(LLESWEBR-H-UGD).

2. Edit the WebReport to contain the desired output using the guidelines and
general practices used in the sample reportviews.

CSAV200300-APG-EN-01 OpenText™ Content Server 85

Chapter 18 Content Intelligence Widget Configuration

3. On the Content Server Administration > ActiveView Administration page,

click the Open the Perspective Manager link.

4. In the Perspective Manager, create a new perspective or edit an existing

perspective. For more information about how to create a new perspective or
how to edit a perspective, see the Online Help available in the Perspective
Manager.

5. On the Configure tab, do the following:

a. In the Widget Library pane, click to expand the Content Intelligence

widget group and drag the HTML WebReport widget to the page.
b. To open the configuration options, select the HTML WebReport widget on
the page.
c. In the Options pane, in the WebReport ID box, add the WebReport created
in Step 1 and edited in Step 2.

Note: For more information on the options available for the HTML
WebReport widget, see HTML WebReport Widget Configuration
Parameters on page 84.

6. Browse to the location where the new perspective is applied to verify the HTML
WebReport widget output.

18.2.2 Using Javascript in the HTML WebReport widget

The HTML WebReport widget supports Javascript. It is important, however, to
understand which types of syntax are supported and which are not. Smart View is a
single-page application that uses RequireJS modules to load Javascript. All libraries
and components that are available for use within the official Smart UI SDK are also
available within the HTML WebReport widget. To use these libraries and
components, you must use the correct RequireJS syntax to load modules.

Important
Javascript used with the HTML WebReport widget must follow the standards
described in this help and in the Smart UI SDK documentation. Javascript that
is not written to be compatible with the Smart UI may conflict with the Smart
UI framework and result in unpredictable behavior.

Watch out for Javascript in your HTML WebReport widget that is not written to be
compatible with the Smart UI. The following situations may cause problems:

• If you include a WebReport that is written for the Classic UI, it may include
Javascript that conflicts with the Smart UI framework.
• If you use <script src="..." > syntax to load external Javascript files directly
on the page, such as new third-party libraries, these libraries may conflict with
the Smart UI framework. Including such an HTML WebReport widget on a
Smart UI page that is subsequently embedded in an external site may also cause
problems.

86 ActiveView Perspective Manager CSAV200300-APG-EN-01

 18.2. Configuring the HTML WebReport Widget

[Link] Loading Smart UI SDK Modules

Note: The Smart UI SDK is available starting from the 16.0.3 Content Server
release, so this approach is not supported for releases prior to 16.0.3.

If you add a script block to the WebReport that will be loading within an HTML
WebReport widget, you can access the csui global object. Then, you can use csui.
require to load modules and use of them in your application.

Example 18-1: RequireJS Example Syntax

<script>

// Wrap any calls to third party modules and Smart UI components using [Link].
[Link](['csui/lib/jquery', 'csui/utils/base'], function ($, base) {

// The 'jQuery' third party libraries is now loaded and

can be accessed by the '$' reference. e.g.
$('.myclass').show();

//The Smart UI 'base' utility is also loaded and can be

accessed by the 'base' reference. e.g.
[Link]();

});

</script>

[Link] Commonly Used Third-Party Libraries

• Backbone: csui/lib/backbone
• Handlebars: csui/lib/handlebars
• jQuery: csui/lib/jquery
• Marionette: csui/lib/marionette
• Underscore: csui/lib/underscore

18.2.3 Example Scripts for the HTML WebReport widget

This section includes example scripts for the HTML WebReport widget.

“Example 1: Using Standard Javascript” on page 88

“Example 2: Using JQuery” on page 88

“Example 3: Using Marionette” on page 89

CSAV200300-APG-EN-01 OpenText™ Content Server 87

Chapter 18 Content Intelligence Widget Configuration

[Link] Example 1: Using Standard Javascript

The following script shows the use of standard Javascript:
<style>

.binf-widgets .webreports-example-hello {
margin: 10px;
padding: 10px;
}

</style>

<div class="webreports-example-hello"></div>

<script>

[Link]("webreports-example-hello")[0].[Link] = "2px
solid #87CEFA";
[Link]("webreports-example-hello")[0].[Link] =
"10px";
[Link]("webreports-example-hello")[0].innerHTML = "Hello
World";

</script>

[Link] Example 2: Using JQuery

The following script shows the use of JQuery:
<style>

.binf-widgets .webreports-example-hello-jquery {
margin: 10px;
padding: 10px;
}

</style>

<div class="webreports-example-hello-jquery"><div>

<script>

[Link](['csui/lib/jquery'], function ($) {

$(".webreports-example-hello-jquery").css("border","2px solid #87CEFA");

$(".webreports-example-hello-jquery").css("border-radius","10px");
$(".webreports-example-hello-jquery").html("Hello World");

});

</script>

88 ActiveView Perspective Manager CSAV200300-APG-EN-01

 18.2. Configuring the HTML WebReport Widget

[Link] Example 3: Using Marionette

The following example shows how to use Marionette, the main library used for
rendering HTML in Smart View:
<style>

.binf-widgets .webreports-example-marionette-view {
margin: 10px;
padding: 10px;
border: 2px solid #87CEFA;
border-radius: 10px;
}

</style>

<script>

[Link](['csui/lib/jquery', 'csui/lib/marionette'], function ($, Marionette) {

var helloWorldView,
// Create a Marionette Region from our main div element
contentRegion = new [Link]({el: '#webreports-example-
marionette'}),
// Create a new Marionette view extending from the built-in ItemView
HelloWorldView = [Link]({
// Apply a class name to the view element
className: 'webreports-example-marionette-view',
// Override the render function to update the view.
render: function () {
this.$[Link]('Hello World');
return this;
}
});

// Create a new instance of our view

helloWorldView = new HelloWorldView();
// Show our view in the region
[Link](helloWorldView);

});

</script>

<div id="webreports-example-marionette"></div>

18.2.4 Instructions to create a WebReport to return data for a

Smart View TABLEREPORT
This section includes step-by-step instructions to create an HTML WebReport
widget for Smart View that returns data using the @TABLEREPORT directive. The
@TABLEREPORT directive enables you to specify how data is sorted, paged, and
filtered.

Collection processing refers to the paging, sorting, and filtering for the data. It can be
a webreport or datasource. If WebReport is specified then all the data from the data
source will be returned to Content Server and collection processing will be
performed by the WebReports engine. If datasource is specified then collection
processing will be performed by the WebReports data source.

For more information, see OpenText Content Server - WebReports (LLESWEBR-H-

UGD).

CSAV200300-APG-EN-01 OpenText™ Content Server 89

Chapter 18 Content Intelligence Widget Configuration

[Link] Method 1: Instructions to perform collection processing in the

WebReport
This example walks through how to create an HTML WebReport widget that
performs collection processing in WebReport using the @TABLEREPORT directive. For
more information about the @TABLEREPORT directive, see OpenText Content Server -
WebReports (LLESWEBR-H-UGD).

Important
Because this method does not perform pagination in the data source, all rows
will be returned to the WebReport for processing. Therefore, OpenText
recommends that you only apply this method for small to medium sized data
sets.

If you have a large data set, see “Method 2: Instructions to perform collection
processing in the data source” on page 92

To create an HTML WebReport widget that performs collection processing in

the WebReport:

1. Create a WebReport:

a. In Content Server, click Add Item, and then click WebReport.

b. On the Add WebReport page, in the Name section, enter a unique name for
the WebReport. For the purposes of this example, call your new WebReport
“WebRep CPWR01”.
c. From the Reportview File list, click Table Report Widget - Data
Processing in WebReport JSON.
d. In the Data Source section, click Browse Content Server.
Find, or create, a Content Server folder that contains multiple documents,
then click the Select link for that folder. You will use this Content Server
folder node as a data source.
This example will refer to the folder as “CPWR Folder01”.
e. Click Add.
f. From your new WebReport's Functions menu, select Properties > General.
g. On the General tab, copy the value in the Nickname box.

2. Edit the WebReport you created in Step 1, “WebRep CPWR01”.

a. From the Functions menu of the “WebRep CPWR01” WebReport, click

Edit Reportview.
b. In the Edit WebReport page, scroll to the end and edit the last section so
that it reads:
[LL_WEBREPORT_INSERTJSON @TABLEREPORT
COLLECTIONPROCESSING:"webreport"
INCLUDECOLUMNS:'["Name","MimeType", "SubType", "ModifyDate", "UserID"]'
FORMATCOLUMNNAMES:MimeType:"Mime Type":SubType:"Sub Type":UserID:"Owner"
FORMATCOLUMNS:SubType:"[LL_REPTAG=SubType

90 ActiveView Perspective Manager CSAV200300-APG-EN-01

 18.2. Configuring the HTML WebReport Widget

LABEL:SUBTYPE /]":CreatedBy:"[LL_REPTAG=CreatedBy
USERINFO:FULLNAME /]":ModifyDate:"[LL_REPTAG=ModifyDate DATE:LONG /]" /]

c. Click Add Version.

3. Create a second, new WebReport. For the purposes of this example, call your
second new WebReport “WebRep CPWR02”:

a. In Content Server, from the Add Item menu, click WebReport.

b. In the Name box, type “WebRep DPWR02”.
c. From the Reportview File list, click Blank Report.
d. Click Add. In the information message dialog informing you that you have
not selected a data source, click OK.
e. From the Functions menu of the “WebRep CPWR02” WebReport, click
Edit Reportview.
f. On the Edit WebReport page, edit the content so that it reads:
[/* Title: Blank Reportview */]

<script>
[Link](['csui/lib/marionette', 'csui/utils/contexts/page/
[Link]', 'webreports/controls/[Link]/[Link]'], function
(Marionette, PageContext, TableReportView) {

var contentRegion = new [Link]({el: '#content'}),

pageContext = new PageContext(),
tableReportView,
options;

options = {
context: pageContext,
data: {
id: 463381,
title: 'My Table Report',
header: false,
titleBarIcon: 'title-assignments',
columnsWithSearch: 'name',
sortBy: 'ModifyDate',
sortOrder: 'desc'
}
};

tableReportView = new TableReportView(options);

[Link](tableReportView);
[Link]();

});
</script>

<div id="content"></div>

[LL_WEBREPORT_STARTROW /]
[LL_WEBREPORT_ENDROW /]

g. Before you save your changes, edit the line:

id: 463381,

to put in the ID that you copied from the first WebReport in 1.f.
h. Click Add Version.

CSAV200300-APG-EN-01 OpenText™ Content Server 91

Chapter 18 Content Intelligence Widget Configuration

4. Open the Perspective Manager and create a new perspective. Choose, or create,
a specific test folder in which to save this perspective. For the purposes of this
example, browse to “WebRep TableReport Perspective”.
For information about the Perspective Manager, see the Online Help available in
Perspective Manager.

5. Configure your new perspective:

a. On the General tab, type a unique name for this perspective. For the
purposes of this example, call this perspective “WR-Persp01”.
b. On the Layout tab, in the Type box, click Left - Center - Right.
c. On the Configure tab, do the following:

i. In the Widget Library pane, in the Content Intelligence widget group,

select the “HTML WebReport” widget and drag it on the perspective,
in the Center position.
ii. In the Options pane, in the “HTML WebReport” widget options, in the
WebReport ID box, click Browse and choose the WebReport you
created in 3. For this purposes of this example, choose “WebRep
CPWR02”.
d. Click Create.

6. While in Smart View, browse to the test folder in which you saved the
perspective in 4. For the purposes of this example, browse to “WebRep
TableReport Perspective”.

[Link] Method 2: Instructions to perform collection processing in the

data source
This example walks through how to create an HTML WebReport widget that shows
a Table Report using collection processing in the data source with the @TABLEREPORT
directive. For more information about the @TABLEREPORT directive, see OpenText
Content Server - WebReports (LLESWEBR-H-UGD). This approach can be used to
support larger data sets. The data source for this needs to be configured in a specific
way to allow paging, sorting and filtering to be done correctly. Currently, only
LiveReport data sources are supported for this approach.

Important
Because this method performs pagination in the data source, only one page of
results will be returned to the WebReport for processing. Therefore, this
method can be used for larger data sets.

If you have a small to medium sized data set, see “Method 1: Instructions to
perform collection processing in the WebReport” on page 90

To create an HTML WebReport widget that performs collection processing in

data source:

1. Create a WebReport:

92 ActiveView Perspective Manager CSAV200300-APG-EN-01

 18.2. Configuring the HTML WebReport Widget

a. In Content Server, click Add Item, and then click WebReport.

b. On the Add WebReport page, in the Name section, enter a unique name for
the WebReport.
For the purposes of this example, call your new WebReport “WebRep
CPDS01”.
c. From the Reportview File list, click Table Report Widget - Data
Processing in Data Source JSON.
d. From the LiveReport File list, click “Table Report Audit Events”.
In addition to creating a WebReport, this will also create a new LiveReport
node. This LiveReport node will be called “Audit Events for This Week”
and will also automatically set the LiveReport as the data source.
e. Click Add.
f. From your new WebReport's Functions menu, select Properties > General.
g. On the General tab, take note of the value in the Nickname box. You will
need this value later in this procedure in 4.g.

2. Choose, or create, a sample Content Server folder node to use as a container. For
the purposes of this example, create a folder called “DatSrc TableReport
Perspective”.

3. Edit the WebReport you created in 1, “WebRep CPDS01”.

a. From the Functions menu of the “WebRep CPDS01” WebReport, click Edit
Reportview.
b. On the Edit WebReport page, scroll to the end and edit the last section so
that it reads:
[LL_WEBREPORT_INSERTJSON @TABLEREPORT
COLLECTIONPROCESSING:"datasource"
EXCLUDECOLUMNS:'["RowNumber"]'
FORMATCOLUMNNAMES:AuditID:"Event":PerformerID:"User"
FORMATCOLUMNS:AuditID:"[LL_REPTAG=AuditID
LABEL:AUDITID /]":SubType:"[LL_REPTAG=SubType LABEL:SUBTYPE
DEF:'' /]":PerformerID:"[LL_REPTAG=PerformerID USERINFO:NAME /]" /]

Note: If FORMATCOLUMNS is used with COLLECTIONPROCESSING and set

to “datasource”, sorting will be automatically disabled for the
formatted columns. This is because the sort values in the user
interface are not available for sorting in the LiveReport. If you need
formatted values that are also sortable you should do the formatting
in the SQL.
c. Click Add Version.

4. Create a second, new WebReport. For the purposes of this example, call your
second new WebReport “WebRep CPDS02”:

a. In Content Server, from the Add Item menu, click WebReport.

b. In the Name box, type “WebRep DPDS02”.
c. From the Reportview File list, click Blank Report.

CSAV200300-APG-EN-01 OpenText™ Content Server 93

Chapter 18 Content Intelligence Widget Configuration

d. Click Add. In the information message dialog informing you that you have
not selected a data source, click OK.
e. From the Functions menu of the “WebRep CPDS02” WebReport, click Edit
Reportview.
f. On the Edit WebReport page, edit the content so that it reads:
[/* Title: Blank Reportview */]

<script>
[Link](['csui/lib/marionette', 'csui/utils/contexts/page/
[Link]', 'webreports/controls/[Link]/[Link]'], function
(Marionette, PageContext, TableReportView) {

var contentRegion = new [Link]({el: '#content'}),

pageContext = new PageContext(),
tableReportView,
options;

options = {
context: pageContext,
data: {
id: 463411,
title: 'Audit Events for the Past Week',
header: false,
titleBarIcon: 'title-assignments',
columnsWithSearch: 'name',
sortBy: 'AuditDate',
sortOrder: 'desc'
}
};

tableReportView = new TableReportView(options);

[Link](tableReportView);
[Link]();

});
</script>

<div id="content"></div>

[LL_WEBREPORT_STARTROW /]
[LL_WEBREPORT_ENDROW /]

g. Before you save your changes, edit the line:

id: 463411,

to put in the ID that you noted from the first WebReport in Step 1.f.
h. Click Add Version.

5. Open the Perspective Manager and create a new perspective.

For information about the Perspective Manager, see the Online Help available in
Perspective Manager.

6. Configure your new perspective:

a. On the General tab, do the following:

i. Type a unique name for this perspective. For the purposes of this
example, call this perspective “DS-Persp01”.
ii. Choose a specific test folder in which to save this perspective. You can
choose to save this perspective in the folder you selected in Step 2. For

94 ActiveView Perspective Manager CSAV200300-APG-EN-01

 18.2. Configuring the HTML WebReport Widget

the purposes of this example, browse to “DatSrc TableReport

Perspective”.
b. On the Layout tab, in the Type box, click “Left - Center - Right”.
c. On the Configure tab, do the following:

i. In the Widget Library pane, in the Content Intelligence widget group,

select the “HTML WebReport” widget and drag it to the perspective,
in the Center position.
ii. In the Options pane, in the “HTML WebReport” widget options, in the
WebReport ID box, click Browse and choose the WebReport you
created in 4. For this purposes of this example, choose “WebRep
CPDS02”.
d. Create the perspective.

7. While in Smart View, browse to the test folder in which you saved the
perspective. For the purposes of this example, browse to “DatSrc TableReport
Perspective”.

8. Optional To modify the report to return different data, do the following:

Important
Following this next step requires a strong knowledge of SQL and
LiveReports.

This data source is just a sample to get you started. It is set up in a specific way
to work with the INSERTJSON @TABLEREPORT option when
COLLECTIONPROCESSING is set to “datasource”. For more information, see
OpenText Content Server - WebReports (LLESWEBR-H-UGD).

a. Rename the LiveReport that was automatically created in 1 to “Documents

Modified in the Past Week”. Edit the LiveReport “Documents Modified in
the Past Week”. In the Title box, type “Documents Modified in the Past
Week”.
b. In the SQL section, edit the “ResultSetSubQuery” SQL statement.
Remove the following section of code:
SELECT [Link] AS AuditID, [Link] AS AuditDate,
[Link] AS Name, [Link] AS SubType, [Link] AS
PerformerID
FROM DAuditNew
INNER JOIN DTree ON [Link] = [Link]
WHERE [Link] > %7
AND %8
~3

And replace it with this section of code:

SELECT [Link], [Link], [Link]
FROM DTree
WHERE [Link] > %7
AND [Link] = 144
AND %8
~3

c. In the Templates section, edit the “~1” template.

CSAV200300-APG-EN-01 OpenText™ Content Server 95

Chapter 18 Content Intelligence Widget Configuration

Remove this section of code:

SELECT Count(AuditID) as Count

And replace it with this section of code:

SELECT Count(Name) as Count

d. In the Templates section, edit the “~2” template.

Remove this section of code:
SELECT ROW_NUMBER() OVER(ORDER BY %2 %3) AS RowNumber, AuditID,
AuditDate, Name, SubType, PerformerID

And replace it with this section of code:

SELECT ROW_NUMBER() OVER(ORDER BY %2 %3) AS RowNumber, Name, ModifyDate,
ModifiedBy

e. Click Save and Exit.

9. Edit the WebReport you created in 1, “WebRep CPDS01”:

a. From the Functions menu of the “WebRep CPWR01” WebReport, click

Edit Reportview.
b. On the Edit WebReport page, scroll to the end and edit the last section so
that it reads:
[LL_WEBREPORT_INSERTJSON @TABLEREPORT
COLLECTIONPROCESSING:"datasource"
EXCLUDECOLUMNS:'["RowNumber"]'
FORMATCOLUMNNAMES:ModifiedBy:"Modified By":ModifyDate:"Last Date Modified"
FORMATCOLUMNS:SubType:ModifiedBy:"[LL_REPTAG=ModifiedBy
USERINFO:FULLNAME /]":ModifyDate:"[LL_REPTAG=ModifyDate DATE:LONG /]" /]

c. Click Add Version.

10. Edit the WebReport you created in 4, “WebRep CPDS02”. From the Functions
menu of the “WebRep CPDS02” WebReport, click Edit Reportview.

11. On the Edit WebReport page, edit the content so that it reads:
[/* Title: Blank Reportview */]

<script>
[Link](['csui/lib/marionette', 'csui/utils/contexts/page/[Link]',
'webreports/controls/[Link]/[Link]'], function (Marionette,
PageContext, TableReportView) {

var contentRegion = new [Link]({el: '#content'}),

pageContext = new PageContext(),
tableReportView,
options;

options = {
context: pageContext,
data: {
id: 463411,
title: 'Documents Modified in the Past Week',
header: false,
titleBarIcon: 'title-assignments',
columnsWithSearch: 'name',
sortBy: 'Name',
sortOrder: 'desc'
}
};

96 ActiveView Perspective Manager CSAV200300-APG-EN-01

 18.3. Configuring the Widget Carousel Widget

tableReportView = new TableReportView(options);

[Link](tableReportView);
[Link]();

});
</script>

<div id="content"></div>

[LL_WEBREPORT_STARTROW /]
[LL_WEBREPORT_ENDROW /]

12. Before you save your changes, edit the line:

id: 463411,

to put in the ID that you noted from the first WebReport in 1.

13. While in Smart View, browse to the test folder in which you saved the
perspective. For the purposes of this example, browse to “DatSrc TableReport
Perspective”.

18.3 Configuring the Widget Carousel Widget

The Widget Carousel widget allows you to display up to ten different slides in the
space of one Smart View tile. You can populate each slide with a child widget from
the Content Intelligence widget group.

Widget Carousel Widget Configuration Parameters

Widget Size
Mandatory. Select the size for the Widget Carousel widget in the Flow layout:
Single width, Double width, or Full Page.
Default = Double width.

Show Header
Optional. Select whether or not the tile will include a header that contains the
title and title icon. If set to True, the header will appear. If set to False, there
will be no header.
Default = False
Notes

• If the tile header is enabled and the child widget already has a header,
then both headers will appear.
• In most cases, you would only enable the Widget Carousel header if all
the included child widgets did not have a header.

Title
Optional. Enter the title for the Widget Carousel. If the header is enabled, the
title will appear on the header.
Default title = “Widget Carousel”

CSAV200300-APG-EN-01 OpenText™ Content Server 97

Chapter 18 Content Intelligence Widget Configuration

Icon class
Optional. Enter the CSS class for the icon that will appear before the Title in the
Header. For example: support/csui/themes/carbonfiber/[Link]
contains icons such as title-assignments, title-customers, title-
favourites, title-opportunities, title-recentlyaccessed, title-
activityfeed, title-customviewsearch.
Default = “title-webreports” (the WebReports icon )
Note: You can specify a custom icon within the WebReport template by
adding a CSS selector that uses background-image and then referencing
the selector in this option.
Behavior
Set the options that control the behavior of the Widget Carousel.

• Cycle automatically
Optional. Select whether or not the Widget Carousel will rotate through the
slides. If set to True, the carousel will automatically rotate through the slides.
If set to False, the carousel will only advance to the next slide if the user
explicitly clicks on the navigation controls.
Default = True
• Interval
Optional. If the Widget Carousel is set to cycle automatically, set the amount
of time, in milliseconds, each slide will appear before advancing to the next
one.
Default = 5000 (ms)
• Pause on hover
Optional. If the Widget Carousel is set to cycle, and this option is set to True,
the carousel will stop cycling if the user explicitly points to the current slide.
If set to False, the carousel continues to cycle, regardless of where the user
points the cursor.
Default = True
• Loop
Optional. If the Widget Carousel is set to cycle automatically and Loop is set
to True, the carousel will advance through all the slides in an endless loop. If
the Widget Carousel is set to cycle automatically and Loop is set to False, the
carousel will only show each slide once.
Default = True

Child widgets
Mandatory. Add and configure up to ten slides in the order in which you want
them to appear in the carousel. You can populate each slide by dragging a child
widget from the Content Intelligence widget group to the Child Widget Drop
Area.
For more information about how to configure child widgets from the Content
Intelligence widget group, see the following topics:

98 ActiveView Perspective Manager CSAV200300-APG-EN-01

 18.3. Configuring the Widget Carousel Widget

• “Configuring the Nodes List WebReport Widget” on page 82

• “Configuring the HTML WebReport Widget” on page 84
• “Configuring the Visual Count Widget” on page 100

Notes

• You cannot nest a Widget Carousel within another Widget Carousel.

• The total loading time of the carousel is affected by the loading time of
each child widget on a slide. In Smart View, a perspective that includes a
Widget Carousel widget finishes loading only after the first slide fully
loads.
After the first slide loads, the carousel advancement controls activate
only after the remaining slides finish loading.
For best performance, choose quick-loading slides, particularly the first
one, to include in the Widget Carousel.

18.3.1 To Configure the Widget Carousel Widget

To configure the Widget Carousel widget:

1. Create up to ten Content Intelligence widgets that you want to include on a

slide in the Widget Carousel. For information about how to create a WebReport,
see OpenText Content Server - WebReports (LLESWEBR-H-UGD).

2. To open the Perspective Manager, navigate to the Content Server

Administration > ActiveView Administration page, and click the Open the
Perspective Manager link.

3. In the Perspective Manager, create a new perspective or edit an existing

perspective. For more information about how to create a new perspective or
how to edit a perspective, see the Online Help available in the Perspective
Manager.

4. On the Configure tab, do the following:

a. In the Widget Library pane, click to expand the Content Intelligence

widget group and drag the Widget Carousel widget to the page.

Note: Each Perspective can only include one Widget Carousel widget.

b. To configure the Widget Carousel widget, do the following:

i. In the work area, click the Widget Carousel widget.

ii. In the Options pane, configure the settings for the Widget Carousel
widget as described in Widget Carousel Widget Configuration
Parameters on page 97.
c. To add and configure a child widget as a slide in the Widget Carousel, do
the following:

CSAV200300-APG-EN-01 OpenText™ Content Server 99

Chapter 18 Content Intelligence Widget Configuration

i. To add a child widget as a slide in the Widget Carousel widget, drag a

widget from the Content Intelligence widget group to the Widget
Carousel widget, into the Child Widget Drop Area.

Notes

• You cannot nest Widget Carousel widgets.

• Each child widget must call a unique WebReports node ID. You
cannot reuse or repeat the same WebReport on more than one
slide in the Widget Carousel.
• As you drag more widgets to the Widget Carousel, the
completion bar will indicate how much room remains for
additional child widgets, up to a maximum of ten.
ii. In the Options pane, expand the Child widgets section and click the
child widget that you want to configure.
iii. In the updated Options pane for the child widget, configure the
settings as appropriate for the type of Content Intelligence widget
selected.

• “Configuring the Nodes List WebReport Widget” on page 82

• “Configuring the HTML WebReport Widget” on page 84
• “Configuring the Visual Count Widget” on page 100
d. If needed, repeat Step 4.c for up to a maximum of ten child widgets.

5. To verify the Widget Carousel widget output, navigate to the location where the
new perspective is applied.

18.4 Configuring the Visual Count Widget

The Visual Count widget helps visualize quantifiable data as a chart on a tile in
Smart View. This widget is useful when you have a data source that has columns
with values that you would like to compare.

Each Visual Count widget depends on a WebReports object to format its data, which
can be any valid WebReports data source. For more information about how to create
these prerequisites, see “Examples and Walkthroughs of How to Use the Visual
Count Widget” on page 107.

You can use the Perspective Manager to configure the initial appearance of the chart
in Smart View, but, depending on the widget configuration, the end user may be
able to use the controls in Smart View to sort and filter the chart.

Smart View end users can change the filtering of the Visual Count widget in the
following ways:

• From the Tile view, if an administrator uses the Perspective Manager to set Enable
Tile Filtering Controls option to True.

100 ActiveView Perspective Manager CSAV200300-APG-EN-01

 18.4. Configuring the Visual Count Widget

• From the Expanded view, if an administrator uses the Perspective Manager to set
Enable Expanded View option to True. The expanded view also allows filtering
by multiple columns.

Visual Count Widget Configuration Parameters

Widget Size
Mandatory. Select the size for the Visual Count widget in the Flow layout: Single
width or Double width.
Default = Double width.
Title
Optional. Enter the title for the widget. The title appears in the tile header.
Default = “Visual Count”
Chart Type
Optional. Select the type of chart appropriate for your data. Options include Bar
chart, Donut chart, and Pie chart.
Default = Bar chart
Source WebReport
Mandatory. Browse for the WebReport that retrieves the data that you want to
visualize.

Note: You can use the following reportviews that have been specifically
created to use with this widget and edit them as required.

• Visual Count Widget - Grouping on Client JSON

• Visual Count Widget - Grouping in WebReport JSON
• Visual Count Widget - Grouping in Data Source Simplified JSON
• Visual Count Widget - Grouping in Data Source JSON

For more information about the @NODESTABLEFIELDS directive, and other

directives that specify WebReports Smart UI reports output, see the
INSERTJSON tag.
Active Column
Mandatory. Enter the name of the column from the data source that provides the
matching values to be counted.
Default = The name of the first column in the data source.
Notes

• When you enter the column name, you must be careful of the case
sensitivity if your data source is a LiveReport that queries a case-
sensitive database.
• Avoid choosing an Active Column that returns unique values because
the data will not be meaningful on a count-based chart. Ideally, this

CSAV200300-APG-EN-01 OpenText™ Content Server 101

Chapter 18 Content Intelligence Widget Configuration

widget works best for data with columns containing no more than 20
distinct values.
• Include fewer than ten columns to make the chart more user-friendly.
More than ten columns are more complex to configure and may
potentially have a performance cost.
• You can include and exclude columns by editing the reportview used for
the WebReports object associated with this widget.
• If Enable Tile Filtering Controls is set to True, a Smart View end user
can select a different Active Column value for the chart. For more
information, see Chart Options on page 102.
Values As Percentages
Choose whether to show the values as percentages of the total count. If False,
the values will appear as the actual count instead.
Default = False
Group After
Optional. Choose the number, from one to twenty, as the threshold for the
maximum number of discrete values whose total counts will appear on the
chart. Values that exceed this threshold are grouped as “Other” and will show
the combined total. Options include values from one to twenty and “Use Chart
Default”, which will use the default number appropriate for the chart type
selected.

• Bar chart default = 15

• Pie chart default = 5
• Donut chart default = 5

Sort By
Optional. Choose the sorting criteria for the chart. Options include the
following:

• Count – Sort numerically by the total count of similar values.

• Active Column – Sort alphanumerically, using the actual values from the
Active Column selection described in Active Column on page 101.

Default = Count
Sort Direction
Optional. Choose whether the criteria specified in the Sort By on page 102
setting are sorted in ascending or descending order.
Default = Descending
Chart Options
Optional. Choose whether Smart View end users can access the filter menu on
the Tile view of the chart to change how they want to filter the chart data. If set
to True, the end user can see the Configure button on the Tile view. If set to

102 ActiveView Perspective Manager CSAV200300-APG-EN-01

 18.4. Configuring the Visual Count Widget

False, then the end user cannot see the Configure button and cannot filter
the chart in the Tile view.
Default = False
Note: This setting only affects the end user ability to filter the chart in the
Tile view, not the Expanded view.
Expanded View
Optional. Choose whether Smart View end users can expand the Tile view of the
chart to see more chart details as well as change how they want to filter the chart
data.
Default = False
Button WebReports
Optionally, configure custom buttons for the Expanded view. Each button can
pass in fixed values and then launch the associated WebReport.

• Maximum Items to Process

Enter the maximum number of rows in the data set that the Button
WebReport will process. If the filtered data set exceeds this limit, the
WebReport launched by the button will return an error.
Default = 5000 rows

Note: There is a hard limit of 50,000 rows. If you try to set a value
higher than 50,000, you will get an error.

Custom Buttons
Optionally, add one or more custom buttons to the footer of the Expanded view.
Configure each button to launch the selected WebReport in a new window,
optionally passing in preset parameters.

• Button WebReport – Optional. Expanded view only. Browse for the

WebReport that will open when you click the button.
Default = If left blank, no custom button or footer appears.
• Button Label – Optional. Expanded view only. Enter a custom label that will
override the default label for the custom button.
Default = “Launch WebReport”
• Button Tooltip – Optional. Expanded view only. Enter a custom tool tip that
will override the default tool tip for the custom button.
Default = “Launch a WebReport in a new window using the current filters”

Source Parameters
Optional. If the Source WebReport that generates the data to be visualized
accepts parameters, you can specify them here.

• Parameter Name – Optional. Name of the parameter that you want to pass to
the WebReport that generates the data to be visualized.

CSAV200300-APG-EN-01 OpenText™ Content Server 103

Chapter 18 Content Intelligence Widget Configuration

• Parameter Value – Optional. Value of the parameter that you want to pass to
the WebReport that generates the data to be visualized.

18.4.1 To Configure the Visual Count Widget

Important
Be careful when using the Visual Count widget in a frequently loaded location,
such as the landing page.

To configure the Visual Count widget:

1. Create a WebReport to generate the data that you want to visualize as a chart
with the Visual Count widget. Choose from the following reportview templates
that generate data compatible with the Visual Count widget:

• Visual Count Widget - Grouping on Client JSON

• Visual Count Widget - Grouping in WebReport JSON
• Visual Count Widget - Grouping in Data Source Simplified JSON
• Visual Count Widget - Grouping in Data Source JSON

For information about which reportview template to use, see “Choosing a

Reportview Template” on page 105. For information about how to create a
WebReport, see OpenText Content Server - WebReports (LLESWEBR-H-UGD).

Note: You will need to open your data source and make note of the
column that you want to use to group the data. You will need this label to
configure the widget in Step 5.c.

2. Optional Create a WebReport for each action that you want end users to be able to
perform on the results in the Expanded view of the Visual Count widget. You
will be able to configure a custom button that end users can click to launch this
WebReport.

3. On the Content Server Administration > ActiveView Administration page,

click the Open the Perspective Manager link.

4. In the Perspective Manager, create a new perspective or edit an existing

perspective. For more information about how to create a new perspective or
how to edit a perspective, see the Online Help available in the Perspective
Manager.

5. On the Configure tab, do the following:

a. In the Widget Library pane, click to expand the Content Intelligence

widget group and drag the Visual Count widget to the page.
b. To open the configuration options, select the Visual Count widget on the
page.

104 ActiveView Perspective Manager CSAV200300-APG-EN-01

 18.4. Configuring the Visual Count Widget

c. In the Options pane, configure the settings as described in Visual Count

Widget Configuration Parameters on page 101.

• To select the WebReport to be visualized

In the Source WebReport box, click Browse and select the WebReport
created in Step 1.
• To add custom buttons to the Expanded view
i. Click to expand the Custom Buttons section.
ii. In the Button WebReport box, click Browse and select the Button
WebReport created in Step 2.
iii. In the Button Label box, enter a custom label for the custom button.
iv. In the Button Tooltip box, enter a custom tooltip for the custom
button.
v. Click Add to Array.
vi. Repeat Step ii through Step v to configure a button for each Button
WebReport that you have prepared
• To pass in parameters to the WebReport to be visualized
i. Click to expand the Source Parameters section.
ii. In the Parameter Name box, enter the name of the parameter that
you want to pass to the WebReport.
iii. In the Parameter Value box, enter the value of the parameter that
you want to pass to the WebReport.
iv. Click Add to Array.
v. Repeat Step ii through Step iv for each parameter that you want to
pass to the WebReport.

6. Browse to the location where the new perspective is applied to verify the Visual
Count widget output.

18.4.2 Choosing a Reportview Template

This section helps you decide which reportview template you should use for the
WebReport that generates the data that the Visual Count widget visualizes.

The reportviews available for the WebReport and specific to the Visual Count
widget include the following:

• Visual Count Widget - Grouping in Data Source Simplified JSON

• Visual Count Widget - Grouping on Client JSON
• Visual Count Widget - Grouping in WebReport JSON
• Visual Count Widget - Grouping in Data Source JSON

CSAV200300-APG-EN-01 OpenText™ Content Server 105

Chapter 18 Content Intelligence Widget Configuration

Figure 18-1 illustrates the factors you should consider when choosing the
appropriate reportview for this WebReport.

• The intensity of the data source resource query – Light, moderate, or heavy.
• The type of data source – The Visual Count Widget - Grouping in Data Source
Simplified JSON reportview works with a simple tab-separated text file. The
Visual Count Widget - Grouping on Client JSON reportview and Visual Count
Widget - Grouping in WebReport JSON reportview work with any data source.
While the Visual Count Widget - Grouping in Data Source JSON reportview
currently only works with LiveReports.
• Whether or not you want to allow end users to use client browser-based controls
to filter the data in the resulting chart.
• The frequency of access for the page where the Visual Count widget resides.

Figure 18-1: Type of Database Query Determines Which Reportview to Use

Tip: In any data source, to see which columns are available to use as an Active
Column, click the source WebReport to run it and view the JSON output.

Important

• Be careful of using the Visual Count widget in a frequently loaded location,

such as on the landing page. Frequent loading of even a small data set may
result in a significant impact on performance.
• If you do use the Visual Count widget on the frequently loaded page, such
as the landing page, make sure that you use a query with minimal
performance impact or the your run the query using the WebReports
scheduler and return the pre-grouped output such as described in
“Scenario 5: Scheduled Data Chart for Very Large Data Sets (Data Layer)”
on page 129.

106 ActiveView Perspective Manager CSAV200300-APG-EN-01

 18.4. Configuring the Visual Count Widget

18.4.3 Examples and Walkthroughs of How to Use the Visual

Count Widget
If you plan to use the Visual Count widget, you will need to prepare one or more
WebReports. This section includes scenarios that show how to configure these
WebReports to retrieve the data for the chart that you want. These scenarios should
be read in sequence as the examples progress from simple to more complex and each
includes a walkthrough that takes you step-wise through a real-world example
using Content Server data.

1. “Scenario 1: Simple Chart with Static Data” on page 107

2. “Scenario 2: Filter-enabled Chart” on page 111
3. “Scenario 3: Filter-enabled Chart for Larger Data Sets (Application Layer)”
on page 116
4. “Scenario 4: Filter-enabled Chart for Very Large Data Sets (Data Layer)”
on page 121
5. “Scenario 5: Scheduled Data Chart for Very Large Data Sets (Data Layer)”
on page 129

Optionally, after configuring the WebReport for the main chart, you can configure
additional WebReports, that the end user can launch from custom buttons in the
Expanded view of the Visual Count widget. For more information about how to
prepare these WebReports for the custom buttons, see “Preparing WebReports for
the Custom Buttons” on page 134.

[Link] Scenario 1: Simple Chart with Static Data

This section provides examples of how to visualize data that includes values with
variable totals to produce a simple chart that end users do not need to filter.
Example 18-2, “Employee Count for a Retail Store” on page 107 describes a
conceptual use case and the associated data. Then “Preparing to Visualize a Very
Simple Chart” on page 108 shows you how to prepare the template and “Step-by-
step Walkthrough for a Simple Chart with Static Data” on page 109 takes you
through the process of visualizing that data using the Visual Count widget.

Example 18-2: Employee Count for a Retail Store

Consider this simple data set that lists the employee count on various days at a
retail store.

Table 18-1: Employees

Weekday Employee_Count
Sunday 3
Monday 3

CSAV200300-APG-EN-01 OpenText™ Content Server 107

Chapter 18 Content Intelligence Widget Configuration

Weekday Employee_Count
Tuesday 4
Wednesday 6
Thursday 5
Friday 4
Saturday 5

In this example, the data is minimal. The data source already has a count
corresponding to the grouped data. All the employees who worked on a
Saturday have been grouped as “Saturday”, and their total is shown as
“Employee_Count”. Since there are no further details for each employee, such
as job title, gender, or name, there are no other criteria to count so there is no
point enabling tile filtering or expanded view. In this case, we want to show a
non-interactive “infographic” type of chart. The Visual Count widget allows
you to plot this data as a bar chart, showing the weekday on the x axis and the
employee count on the y axis. This kind of data is suitable when you need to
display a graphical chart and do not require the end user to interact with the
chart.

[Link].1 Preparing to Visualize a Very Simple Chart

To visualize a very simple data source that includes pre-grouped, static data, such as
in a tab-separated value (TSV) file or a comma-separated value (CSV) file, you can
use the Visual Count Widget - Grouping in Data Source Simplified JSON
reportview template.

• Size
Recommended for static, pre-grouped data where the size of the data used to
generate the grouped counts does not affect overall performance.
• Filtering
Does not support filtering.
• Data source
A very simple data source that includes pre-grouped, static data, such as in a
TSV file or a CSV file.
• WebReports object
Must use the Visual Count Widget - Grouping in Data Source Simplified JSON
reportview template. For an example, see “Step-by-step Walkthrough for a
Simple Chart with Static Data” on page 109.
• Visual Count widget configuration
No special configurations required.

108 ActiveView Perspective Manager CSAV200300-APG-EN-01

 18.4. Configuring the Visual Count Widget

• Performance

– Renders static data without user interaction on the client, so it has very little
additional impact on performance.
– Suitable for use in a frequently-accessed location, such as a landing page.

[Link].2 Step-by-step Walkthrough for a Simple Chart with Static Data

To step through the process of visualizing a very simple chart with static data

1. Create a file with pre-grouped, static data:

a. In Content Server, click Add Item to create a new text document.

b. On the Add: Text Document page, in the Name box, enter a name for the
file.
c. In the MIME Type area, select the Text option, then, in the Text list, choose
text/tab-separated values.
d. In the Text box, type the following, pressing TAB to separate the columns
and pressing ENTER to insert a line break:
Country Count
Germany 1500
Canada 2000
United States 1000

e. Save and close the document.

2. Create a WebReports object that will format the data as required:
For more information about how to create a WebReport, see OpenText Content
Server - WebReports (LLESWEBR-H-UGD).

a. In Content Server, click Add Item to create a new WebReports object.

b. On the Add: WebReport page, in the Name section, enter a name for the
WebReport.
c. In the Data Sourcesection, click Browse Content Server and choose the
static data file created in Step 1.
d. In the Reportview file section, from the list, select Visual Count Widget -
Grouping in Data Source Simplified JSON.
e. On the Source tab, in the Column Separator box, clear the comma and click
the Tab link to insert tab as the column separator.
f. Click Add.
3. Create a perspective to see the chart in Smart View:

a. Sign in to Perspective Manager and create a perspective.

For more information about how to create a perspective, see the Online Help
available in Perspective Manager.
b. Configure a Visual Count widget with the following settings:
For more information about how to configure the Visual Count widget, see
“To Configure the Visual Count Widget” on page 104.

CSAV200300-APG-EN-01 OpenText™ Content Server 109

Chapter 18 Content Intelligence Widget Configuration

• Widget Size
If using the Flow layout, choose either Single width or Double width.

• Title
Employees by Country

• Chart Type
Bar

• Source WebReport
<YourWebReportID> as created in Step 2.

• Active Column
Country

Notes

– Make sure to use the correct case because Content Server folder
columns are case-sensitive.

– Additional columns may be available depending on which

Content Server modules are installed.

– Many columns will contain unique values, such as Name, ID,

and so on, and will not be useful for a chart that counts items
with similar values.

• Show Values as Percentages

False

• Group After
Use chart default

• Sort By
Count

• Sort Direction
Descending

• Enable Tile Filtering Controls

False

• Enable Expanded View

False

c. Sign in to Smart View and verify that the Visual Count widget in the
perspective produces the bar chart as shown in Figure 18-2:

110 ActiveView Perspective Manager CSAV200300-APG-EN-01

 18.4. Configuring the Visual Count Widget

Figure 18-2: Simple Bar Chart

[Link] Scenario 2: Filter-enabled Chart

This section explores a scenario where you want to produce an interactive chart
where the end user can apply filters to highlight different aspects of the data, as
described in Example 18-3, “Detailed Employee Information for a Retail Store”
on page 111. Then “Preparing to Visualize a Basic, Filter-enabled Chart”
on page 112 shows you how to prepare the template and “Step-by-step
Walkthrough for a Basic, Filter-enabled Chart” on page 114 takes you through the
process of visualizing that data using the Visual Count widget.

Example 18-3: Detailed Employee Information for a Retail Store

Consider these first few rows of a larger data set that lists several kinds of data
for each employee in a local company.

Table 18-2: EmployeeDetails

EmployeeID Region Gender Function

12345 Eastbury Male Human Resources
12346 Midtown Male Sales
12347 Downtown Female Sales
12348 Northglen Female Finance
12349 Hillside Male Engineering
12350 Westfield Sales
12351

In this example, the count is derived by grouping whichever values are the
same in the column of data that is of interest, the Active Column.

CSAV200300-APG-EN-01 OpenText™ Content Server 111

Chapter 18 Content Intelligence Widget Configuration

If the Active Column is “Country”, we group all the rows with the same
country value and then count those rows with the following results:

• England = 3
• France = 1
• USA = 3

If the Active Column is “Gender”, we need to regroup and recount with the
following results:

• Male = 3
• Female = 3
• No value = 1

Notes

• If the data source has missing values, it is important to exclude them from
the resulting chart to avoid misleading information. We group them as “No
value”.
• The sum of each value count, including the count of missing values, if any,
should be the same as the total number of rows in the data source.
• This data source includes more information than we can easily display on a
bar chart or a pie chart. The more data that you retrieve, the more it affects
performance, so it makes sense to only bring back the columns needed for
the chart and to exclude the columns that are not needed.
• By enabling end-user filtering, the end user can choose an Active Column, so
that the same data can produce several different charts. It also allows the end
user to perform more complex analyses by combining filters. For example,
“Total count of Sales employees in Europe, by gender”.

[Link].1 Preparing to Visualize a Basic, Filter-enabled Chart

If you have a small data set from a standard WebReports data source query that is
minimally intensive, you can use the Visual Count Widget - Grouping on Client
JSON reportview template. This reportview relies on the javascript engine of the
client browser to filter the entire data set.

• Size
Recommended for small data sets where the results can quickly load to the client
browser.
• Filtering
Allows filtering by the end users using the client browser.

112 ActiveView Perspective Manager CSAV200300-APG-EN-01

 18.4. Configuring the Visual Count Widget

• Data source
Any standard WebReports data source.
• WebReports object
Must use the Visual Count Widget - Grouping on Client JSON reportview
template.
• Visual Count widget configuration

– No special configurations required.

– Supports a Visual Count widget configuration with Enable Tile Filtering
Controls = True or Enable Expanded View = True so that end users can use
the client browser to group and filter the data.
• Performance

– After the Visual Count widget finishes loading, end-user filtering will be fast
and responsive because no additional requests are sent back to the server.
– OpenText does not recommend using for a chart in a frequently loaded
location, such as on the landing page. Frequent loading of even a small data
set may result in a significant impact on performance.

– Not recommended for medium- to large-sized data sets.

Considerations for a Basic, Filter-enabled Chart

• Performance Considerations

– In this scenario, the entire data set is returned to the browser. The browser
filters the data using the client-side Javascript layer.
– The data set size is affected by both the number of columns and the amount
of data it contains. For example, a report with 10 columns that only contains
integers will process quickly. However, a report with only two columns will
process more slowly if that report includes a cell containing the lengthy
description field.
– It is a good practice to tune your LiveReport to only return the data that you
need. For information about how to optimize a LiveReport, see OpenText
Content Server - LiveReports (LLESREP-H-UGD).
• Advantages

– No requests are made to the server when the end user uses the browser to
change the Active Column or to choose other chart options.
– Performance is quick when the data set is small.
• Disadvantages
Performance may degrade if the data set is large. The browser will use more
memory to manipulate the data as the data set size increases. To address this
concern, see “Step-by-step Walkthrough for a Basic, Filter-enabled Chart”
on page 114.

CSAV200300-APG-EN-01 OpenText™ Content Server 113

Chapter 18 Content Intelligence Widget Configuration

[Link].2 Step-by-step Walkthrough for a Basic, Filter-enabled Chart

For this example we will use a Content Server folder as a data-source. To support
filtering by the end user, perform the following procedures:

To step through the process of visualizing a basic, filter-enabled chart:

1. Create a WebReports object that will format the data as required:

For more information about how to create a WebReport, see OpenText Content
Server - WebReports (LLESWEBR-H-UGD).

a. In Content Server, click Add Item to create a new WebReports object.

b. On the Add WebReport page, in the Name section, enter a name for the
WebReport.
c. In the Data Sourcesection, click Browse Content Server and choose a
folder that contains several different document types.
d. In the Reportview file section, from the list, select Visual Count Widget -
Grouping on Client JSON.
e. Click Add.
f. Optional Edit the reportview for WebReport created in Step 1:

i. Optional Add an INCLUDECOLUMNS definition:

INCLUDECOLUMNS:"{'MimeType','FileType','Sub
Type'}"

This definition is optional, but helps to improve the overall user

experience for the end user:

• Reduces the overall size of the JSON data returned by removing

unnecessary information.
• Removes irrelevant options from the Active Column list in the Tile
filter controls and in the Expanded view.

Note: Unless you explicitly use INCLUDECOLUMNS or

EXCLUDECOLUMNS, the Tile filter controls will list all available
columns.
ii. Click Add Version.

2. Create a perspective to see the chart in Smart View:

a. Sign in to Perspective Manager and create a perspective.

For more information about how to create a perspective, see the Online Help
available in Perspective Manager.
b. Configure a Visual Count widget with the following settings:
For more information about how to configure the Visual Count widget, see
“To Configure the Visual Count Widget” on page 104.

114 ActiveView Perspective Manager CSAV200300-APG-EN-01

 18.4. Configuring the Visual Count Widget

• Widget Size
If using the Flow layout, choose either Single width or Double width.

• Title
Documents by type

• Chart Type
Pie

• Source WebReport
<YourWebReportID> as created in Step 1.

• Active Column
FileType

Notes

– Make sure to use the correct case because Content Server folder
columns are case-sensitive.

– Additional columns may be available depending on which

Content Server modules are installed.

– Many columns will contain unique values, such as Name, ID,

and so on, and will not be useful for a chart that counts items
with similar values.

• Show Values as Percentages

False

• Group After
Use chart default

• Sort By
Count

• Sort Direction
Descending

• Enable Tile Filtering Controls

True

• Enable Expanded View

True

c. Sign in to Smart View and verify that the Visual Count widget in the
Perspective produces the pie chart as shown in Figure 18-3:

CSAV200300-APG-EN-01 OpenText™ Content Server 115

Chapter 18 Content Intelligence Widget Configuration

Figure 18-3: Basic Filter-enabled Pie Chart

[Link] Scenario 3: Filter-enabled Chart for Larger Data Sets (Application

Layer)
This section provides examples of how to limit the data retrieved from a potentially
large data set to produce a chart that end users can filter to get further information.
Example 18-4, “Employee Information Data for Acme National” on page 117
describes a conceptual use case for employee information from a national company.
Then it illustrates an example using file data from Content Server, while it steps you
through the process of visualizing the Content Server file data in a filter-enabled
chart using the Visual Count widget. Since the chart is filter-enabled, we can
optionally enable the expanded view for the chart to allow facet filtering. For more
information about how to use facet filtering, see OpenText Content Server - Documents
and Text Documents (LLESWBD-UGD).

Next, “Preparing to Visualize a Filter-enabled Chart for Larger Data Sets”

on page 118 shows you how to prepare the template and “Step-by-step
Walkthrough for a Filter-enabled Chart for Larger Data Sets” on page 119 takes you
through the process of visualizing that data using the Visual Count widget.

To produce a chart that performs well with larger datasets, we need to limit the data
returned from the server to only the subset of data required to visualize the chart.

You can limit the data by editing the data source or the SQL query to return only the
columns that you need. However, this is not always possible. The user creating the
WebReport may not have the SQL skills or permission to edit the LiveReport data
source. If you are comfortable working with WebReports, it may be more convenient
to edit the data at the application layer, by using conditional logic and sub-tags in
the reportview. You can also exclude columns by using directives, as illustrated in
the commented section of the Visual Count Widget - Grouping in WebReport
JSON reportview template. Rather than return all the data to the client browser in a
single request, the application layer can provide the Visual Count widget with the

116 ActiveView Perspective Manager CSAV200300-APG-EN-01

 18.4. Configuring the Visual Count Widget

minimum data required to create the chart. In this case, the application layer need
only return the data relating to the active column that contains the value counts that
we want to visualize. To show the chart for a different active column, or with
different filter criteria, you can make a new request to the server for fresh data that
contains the information you need.

Example 18-4: Employee Information Data for Acme National

Consider these first few rows and columns of a much larger data set that lists
several kinds of data for each employee in a national company.

Table 18-3: EmployeeInfo

Employe State Gender Function City Years Supervis ...

eID or
12345 Nebraska Male Engineeri Omaha 5 Smith ...
ng
12346 Texas Male Sales Austin 6 Jones ...
12347 New Female Finance Newark 12 White ...
Jersey
12348 California Female Sales Irvine 4 Lee ...
12349 Ohio Male Engineeri Toledo 5 Wilson ...
ng
12350 Arizona Engineeri Phoenix 7 Roberts ...
ng
12351 Wisconsi Female Human Kenosha 1 Hansen ...
n Resources

In this example, the count is derived by grouping whichever values are the
same in the column of data that is of interest, the Active Column.

If the Active Column is “Function”, we group all the rows with the same
function value and then count those rows with the following results:

• Sales = 2
• Engineering = 3
• Finance = 1
• Human Resources = 1

If the Active Column is “Gender”, we need to regroup and recount with the
following results:

• Male = 3
• Female = 3
• No value = 1

CSAV200300-APG-EN-01 OpenText™ Content Server 117

Chapter 18 Content Intelligence Widget Configuration

Note: If the data source has missing values, it is important NOT to exclude
them from the resulting chart to avoid misleading information. Even though
they have no value, they still need to be counted. For example, an employee
who has not specified their gender is still an employee and must still be
counted. In the Visual Count widget, these “unknown” values are grouped as
“No value”.

[Link].1 Preparing to Visualize a Filter-enabled Chart for Larger Data Sets

If you have a larger data set from a standard WebReports data source that requires a
moderately-intensive data source query, and if you cannot group and filter the data
in the data source, you can use the Visual Count Widget - Grouping in WebReport
JSON reportview template. This reportview groups and filters the data in the
WebReports object.

• Size
Useful for larger data sets that take longer to load to the client browser.
• Filtering
Requires filtering at the WebReports object.
• Data source
Any standard WebReports data source.
• WebReports object
Must use the Visual Count Widget - Grouping in WebReport JSON reportview
template.
• Visual Count widget configuration

– No special configurations required.

– Supports a Visual Count widget configuration with Enable Tile Filtering
Controls = True or Enable Expanded View = True so that end users can use
the client browser to group and filter the data.
• Performance

– Improved performance between client and server because it does not return
all data rows to the client browser.
– Performance dependent on data transfer between the database and Content
Server before the WebReports object can group and filter the data.
– OpenText does not recommend using for a chart in a frequently loaded
location, such as on the landing page. Frequent loading of even a small data
set may result in a significant impact on performance.

118 ActiveView Perspective Manager CSAV200300-APG-EN-01

 18.4. Configuring the Visual Count Widget

Performance Considerations for a Filter-enabled Chart for Larger Data Sets

Note: This approach suits larger data sets when you expect a moderately large
number of results and do not want to retrieve all the data at once.

• In this scenario, only a subset of the data set is returned to the browser. The
server-side WebReports application filters the data.
• Each time an end user changes the Active Column or changes the filtering
settings, the widget passes parameters to the WebReport, which then makes a
new server request that returns a new data set.
• It is a good practice to tune your LiveReport to only return the data columns that
you need.

[Link].2 Step-by-step Walkthrough for a Filter-enabled Chart for Larger Data Sets

To step through the process of visualizing a filter-enabled chart with a larger

data set:

1. Create a WebReports object that will format the data as required:

For more information about how to create a WebReport, see OpenText Content
Server - WebReports (LLESWEBR-H-UGD).

a. In Content Server, click Add Item to create a new WebReports object.

b. On the Add WebReport page, in the Name section, enter a name for the
WebReport.
c. In the Data Sourcesection, click Browse Content Server and choose a
folder that contains several different document types.
d. In the Reportview file section, from the list, select Visual Count Widget -
Grouping in WebReport JSON.
e. Click Add.
f. Optional Edit the reportview for the WebReport created in Step 1.

i. Optional Add an INCLUDECOLUMNS definition:

INCLUDECOLUMNS:"{'MimeType','FileType','Sub
Type'}"

This definition is optional, but helps to improve the overall user

experience for the end user:

• Reduces the overall size of the JSON data returned by removing

unnecessary information.
• Removes irrelevant options from the Active Column list in the Tile
filter controls and in the Expanded view.

Note: Unless you explicitly use INCLUDECOLUMNS or

EXCLUDECOLUMNS, the Tile filter controls will list all available
columns.

CSAV200300-APG-EN-01 OpenText™ Content Server 119

Chapter 18 Content Intelligence Widget Configuration

ii. Optional Add a FORMATCOLUMNS definition:

FORMATCOLUMNS:SubType:"[LL_REPTAG=SubType
LABEL:SubType /]"

This definition is optional. It will take all the values in the SubType
column and give them a friendly label. For example, “0” becomes
“Folder” and “144” becomes “Document”.
iii. Click Add Version.

2. Create a perspective to see the chart in Smart View:

a. Sign in to Perspective Manager and create a perspective.

For more information about how to create a perspective, see the Online Help
available in Perspective Manager.
b. Configure a Visual Count widget with the following settings:
For more information about how to configure the Visual Count widget, see
“To Configure the Visual Count Widget” on page 104.

• Widget Size
If using the Flow layout, choose either Single width or Double width.
• Title
Test
• Chart Type
Bar
• Source WebReport
<YourWebReportID> as created in Step Step 1.
• Active Column
MimeType

Notes

– Make sure to use the correct case because Content Server folder
columns are case-sensitive.
– Additional columns may be available depending on which
Content Server modules are installed.
– Many columns will contain unique values, such as Name, ID,
and so on, and will not be useful for a chart that counts items
with similar values.
• Show Values as Percentages
False
• Group After
Use chart default

120 ActiveView Perspective Manager CSAV200300-APG-EN-01

 18.4. Configuring the Visual Count Widget

• Sort By
Count
• Sort Direction
Descending
• Enable Tile Filtering Controls
True
• Enable Expanded View
True
c. Sign in to Smart View and verify that the Visual Count widget in the
perspective produces the bar chart, such as shown in Figure 18-4.

Figure 18-4: Filter-enabled Bar Chart (Larger Data Set)

[Link] Scenario 4: Filter-enabled Chart for Very Large Data Sets (Data
Layer)
This section provides examples of how to limit the data retrieved from a very large
data set to produce a chart that end users can filter to get further information.
Example 18-5, “Employee Information Data for GlobalMega Corp.”
on page 122describes a conceptual use case for employee information from a global
company. Next, “Preparing to Visualize a Filter-enabled Chart from a Very Large
Data Set” on page 122 shows you how to prepare the template and “Step-by-step
Walkthrough for a Filter-enabled Chart from a Very Large Data Set” on page 124
takes you through the process of visualizing that data using the Visual Count
widget.

To produce a chart that allows better performance with larger datasets, where the
filtering task is performed at the data layer. The SQL query of the LiveReport groups
all the values. To enable end users to change the Active Column and otherwise filter

CSAV200300-APG-EN-01 OpenText™ Content Server 121

Chapter 18 Content Intelligence Widget Configuration

the data in the expanded view, you can design the LiveReport to use input
parameters to make dynamic queries.

Example 18-5: Employee Information Data for GlobalMega Corp.

Consider these first few rows and columns of a much larger data set that lists
several kinds of data for each employee in a huge global corporation. If we
want a chart that shows the number of employees in each country, we can
create a SQL query that groups by country and counts the rows for each. By
changing the parameters, we can achieve different results to explore the data in
a different way, for example, by choosing to group by Gender instead of
Country.

Table 18-4: EmployeeData

EmployeeID Country Region Gender Function City

12345 USA Nebraska Male Engineering Omaha
12346 USA Texas Male Sales Austin
12347 USA New Jersey Female Finance Newark
12348 France Normandie Female Sales Rouen
12349 France Centre Male Engineering Paris
12350 UK Berkshire Engineering Reading
12351 UK Hampshire Female Human Southampton
Resources
... ... ... ... ... ...

[Link].1 Preparing to Visualize a Filter-enabled Chart from a Very Large Data Set

If you have a large data set, such as from a LiveReport data source, that requires a
heavily-intensive database query, you can group and filter the data in the
LiveReport data source and then use the Visual Count Widget - Grouping in Data
Source Simplified JSON reportview template for the WebReports object.

Note: The Visual Count Widget - Grouping in Data Source JSON reportview
template only works in conjunction with a LiveReport data source since it
depends on the LiveReport ability to group counts of a specific column in the
data source.

• Size
Useful for larger data sets that would take too long to return from the database in
full.
• Filtering
Requires filtering at the LiveReport data source.

122 ActiveView Perspective Manager CSAV200300-APG-EN-01

 18.4. Configuring the Visual Count Widget

• Data source

– Currently only works with a LiveReport data source.

– Must group and configure the data in the LiveReport.
• WebReports object
Must use the Visual Count Widget - Grouping in Data Source JSON reportview
template.
• Visual Count widget configuration

– No special configurations required.

– Recommended Visual Count widget configuration should specify Enable
Expanded View = False, as interactive filtering is not possible with this data.
• Performance

– Improved performance between client and server because it does not return
all data rows to the client browser. The rows are grouped and filtered in the
data source.
– OpenText does not recommend using for a chart in a frequently loaded
location, such as on the landing page. Frequent loading of even a small data
set may result in a significant impact on performance.

Performance Considerations for a Filter-enabled Chart from a Very Large

Dataset

Note: This approach is most suitable for situations where the amount of data
makes it more appropriate for the database engine to perform the task of
filtering and grouping the data.

• In this scenario, only a subset of the results are returned to the browser. The
server-side SQL code in the LiveReport filters the results at the data layer.
• It is a good practice to tune your LiveReport to only return the data that you
need.

Important

Each time an end user loads the page, the widget makes a server request and a
database request. Caution should be applied – if multiple users are likely to be
accessing the chart and interacting with filter parameters, the load on the
database could be significant. Before using this approach you can consider
either of the following strategies:

• Return a smaller, pre-filtered subset of the data and using the approaches
described in “Scenario 2: Filter-enabled Chart” on page 111 and “Scenario 3:
Filter-enabled Chart for Larger Data Sets (Application Layer)” on page 116.
• Schedule the data to be fetched from the database periodically and use the
cached results to generate a chart, as described in “Scenario 5: Scheduled
Data Chart for Very Large Data Sets (Data Layer)” on page 129.

CSAV200300-APG-EN-01 OpenText™ Content Server 123

Chapter 18 Content Intelligence Widget Configuration

[Link].2 Step-by-step Walkthrough for a Filter-enabled Chart from a Very Large Data
Set

Note: These examples have been tested for MSSQL and Oracle databases. If
you are using a different type of database, the syntax may differ.

To step through the process of visualizing a very simple chart with static data:

1. Create a filtered LiveReport data source:

For more information about how to create a LiveReport, see OpenText Content
Server - LiveReports (LLESREP-H-UGD).

a. In Content Server, click Add Item to create a new LiveReport.

b. Edit the report and provide a Title and a Record Limit.
c. In the Inputs section, add the following values:

# Type Prompt URL Parameter

1 InsertString ActiveColumn active_column
2 InsertString Sort Column sort_by
3 InsertString Sort Order sort_order
4 SQLList AuditID AuditID
5 SQLList SubType SubType
6 SQLList PerformerID PerformerID

• Values 1-3 are mandatory and ensure the Visual Count widget passes in
the correct active column and sort details to group and sort the data
when the user changes values in the widget controls.
• Values 4-6 are optional and are used by the filtering feature in the
Expanded view. For every column that you include in your report, you
need to include an input in this section.

Note: The URL Parameter name must match the data source column
name. The URL Parameter type must be SQLList so that the widget
can send in one or more filters for each column.
d. Edit the LiveReport to add the following SQL code to the SQL section:
SELECT %1, Count(%1) as Count
FROM DAuditNew
WHERE AuditDate > %7
AND AuditID IS NOT NULL
AND SubType IS NOT NULL
AND PerformerID IS NOT NULL
~1
~2
~3
Group By %1
ORDER BY %2 %3

After the parameters and conditional templates have been substituted, this
should build a SQL statement similar to the following:

124 ActiveView Perspective Manager CSAV200300-APG-EN-01

 18.4. Configuring the Visual Count Widget

SELECT AuditID, Count(AuditID) as Count

FROM DAuditNew
WHERE AuditDate > { ts '2017-01-07 [Link]' }
AND AuditID IS NOT NULL
AND SubType IS NOT NULL
AND PerformerID IS NOT NULL
AND AuditID IN ( 'Create','AddVersion' )
AND SubType IN ( 0,144 )
AND PerformerID IN ( 1000 )
Group By AuditID ORDER BY Count Desc

e. In the Parameters section, add the following settings:

# Type Options
%1 User Input Input #1
%2 User Input Input #2
%3 User Input Input #3
%4 User Input Input #4
%5 User Input Input #5
%6 User Input Input #6
%7 Last Week-End

• Parameter %1 maps to Input 1 and ensures the current Active Column

is used for all %1 values in the SQL.
• Parameter %2 maps to Input 2 and ensures the current Sort Column is
used for all %2 values in the SQL.
• Parameter %3 maps to Input 3 and ensures the current Sort Direction is
used for all %3 values in the SQL.
• Parameter %4 maps to Input 4 and ensures the current list of filter
values for the AuditStr column is used for all %4 values in the ~1
template.
• Parameter %5 maps to Input 5 and ensures the current list of filter
values for the SubType column is used for all %5 values in the ~2
template.
• Parameter %6 maps to Input 6 and ensures the current list of filter
values for the PerformerID column is used for all %6 values in the ~3
template.
• Parameter %7 will ensure only audit records from the end of the last
week will be shown. This will reduce the performance impact of the
report.
f. In the Templates section, ensure that the Auto-Where check box and Auto-
Comma check boxes are clear and then add the following values:

# SQL Source Include IF

~1 AND AuditID IN%4 No inputs set to flag

CSAV200300-APG-EN-01 OpenText™ Content Server 125

Chapter 18 Content Intelligence Widget Configuration

# SQL Source Include IF

~2 AND SubType IN%5 No inputs set to flag
~3 AND PerformerID IN%6 No inputs set to flag

Note: Ensure that the Options Flag Value is blank for all three values.

These three templates are used for the three filters for the AuditID,
SubType, and PerformerID columns. These ensure the filters are only
inserted into the SQL if a filter is applied for that column. For example, if
the Visual Count widget sends in the values “0” and “144” for SubType
(only show audit events for folders and documents), then the following line
will be added to the SQL in place of the ~2 marker:
AND SubType IN (0,144)

g. In the Report Format area, select Auto LiveReport from the list.
h. Click Save and Exit.

2. Create a WebReports object that will format the data as required:

For more information about how to create a WebReport, see OpenText Content
Server - WebReports (LLESWEBR-H-UGD).

a. In Content Server, click Add Item to create a new WebReports object.

b. On the Add WebReport page, in the Name section, enter a name for the
WebReport.
c. In the Data Sourcesection, click Browse Content Server and choose the
LiveReport created for this example in Step 1.
d. In the Reportview file section, from the list, select widget_visual_count_
grouping_in_data_source.
e. Click Add.
f. Edit the properties for the WebReport created in Step 2.b:

i. Click the Destination tab.

ii. In the Export MIME Type list, select application/json.
iii. Click Update.
g. Edit the reportview for WebReport created in Step [Link] the following
changes:

i. Add an INCLUDECOLUMNS definition:

INCLUDECOLUMNS:"{'AuditID','PerformerID','Su
bType'}"

The INCLUDECOLUMNS definition tells the Filtered Count widget which

columns are available for grouping and filtering. This list must match
the columns defined for filtering in the data source.
ii. (Optional) Add a FORMATCOLUMNS definition:

126 ActiveView Perspective Manager CSAV200300-APG-EN-01

 18.4. Configuring the Visual Count Widget

FORMATCOLUMNS:AuditID:"[LL_REPTAG=AuditID
LABEL:AuditID /]":PerformerID:"[LL_REPTAG=Pe
rformerID
USERINFO:FULLNAME /]":SubType:"[LL_REPTAG=Su
bType LABEL:SubType /]"

This definition is optional. It will take all the values in the AuditID
column, PerformerID column, and SubType column and gives them a
friendly label. For example, with the SubType column, “0” becomes
“Folder” and “144” becomes “Document”.
iii. (Optional) Add a FORMATCOLUMNNAMES definition:
FORMATCOLUMNNAMES:AuditID:"Event
Type":PerformerID:"[LL_REPTAG_'WEBNODE_LABEL
.User' XLATE /]"

This definition is optional. It gives friendly labels to the specified

columns. In this example, you can give the ID column a hardcoded
string, such as “Event Type”. Or you can use any WebReports tag such
as shown earlier where the XLATE tag replaces PerformerID with
“User”. This tag detects the user language and uses the appropriate
translation.
iv. After these changes, the final entire tag definition will be:
[LL_WEBREPORT_INSERTJSON @FILTEREDCOUNT
ACTIVECOLUMN:"[LL_REPTAG_&active_column /]"
INCLUDECOLUMNS:"{'ID','PerformerID','SubType
'}"
FORMATCOLUMNS:AuditID:"[LL_REPTAG=AuditID
LABEL:AuditID /]":PerformerID:"[LL_
REPTAG=PerformerID
USERINFO:FULLNAME /]":SubType:"[LL_REPTAG=Su
bType LABEL:SubType /]"
FORMATCOLUMNNAMES:AuditID:"Event
Type":PerformerID:"[LL_REPTAG_'WEBNODE_LABEL
.User' XLATE /]"
FILTERBY:"[LL_REPTAG_&fc_filters /]"
GROUPBYINDATASOURCE:"TRUE"
GROUPAFTER:"[LL_REPTAG_&group_after /]"
SORTCOL:"[LL_REPTAG_&sort_by /]"
SORTDIR:"[LL_REPTAG_&sort_order /]"
COUNTFORMAT:"SI" /]

h. Click Add Version.

3. Create a perspective to see the chart in Smart View:

a. Sign in to Perspective Manager and create a perspective.

For more information about how to create a perspective, see the Online Help
available in Perspective Manager.
b. Configure a Visual Count widget with the following settings:
For more information about how to configure the Visual Count widget, see
“To Configure the Visual Count Widget” on page 104.

• Widget Size
If using the Flow layout, choose either Single width or Double width.
• Title
Audit Events for the Past Week

CSAV200300-APG-EN-01 OpenText™ Content Server 127

Chapter 18 Content Intelligence Widget Configuration

• Chart Type
Bar
• Source WebReport
<YourWebReportID> as created in Step 2.
• Active Column
AuditID
• Show Values as Percentages
False
• Group After
Use chart default
• Sort By
Count
• Sort Direction
Descending
• Enable Tile Filtering Controls
True
• Enable Expanded View
True

c. Sign in to Smart View and verify that the Visual Count widget in the
Perspective produces the bar chart as shown in Figure 18-5.

Figure 18-5: Filter-enabled Bar Chart (Very Large Data Set)

128 ActiveView Perspective Manager CSAV200300-APG-EN-01

 18.4. Configuring the Visual Count Widget

[Link] Scenario 5: Scheduled Data Chart for Very Large Data Sets (Data
Layer)
This section provides examples of how to schedule data retrieval from a very large
data set to produce a static chart. Example 18-6, “Employee Information Data for
GlobalMega Corp.” on page 129describes a conceptual use case for employee
information from a global company. Next, “Preparing to Visualize a Scheduled Data
Chart for Very Large Data Sets” on page 130shows you how to prepare the template
and “Step-by-step Walkthrough for a Scheduled Data Chart for Very Large Data
Sets” on page 130takes you through the process of visualizing that data using the
Visual Count widget.

To produce a non-interactive “infographic” chart that allows better performance

with larger datasets, where the data is fetched periodically from the database
reducing concurrent load, the SQL query of the LiveReport groups all the values.

Example 18-6: Employee Information Data for GlobalMega Corp.

Consider these first few rows and columns of a much larger dataset that lists
several kinds of data for each employee in a huge global corporation. If we
want a chart that shows the number of employees in each country, we can
create a SQL query that groups by country and counts the rows for each. It is
not important that the data is “live”, in this case it is acceptable to see a
snapshot of the data so long as it is updated on a daily basis.

Table 18-5: EmployeeData

EmployeeID Country Region Gender Function City

12345 USA Nebraska Male Engineering Omaha
12346 USA Texas Male Sales Austin
12347 USA New Jersey Female Finance Newark
12348 France Normandie Female Sales Rouen
12349 France Centre Male Engineering Paris
12350 UK Berkshire Engineering Reading
12351 UK Hampshire Female Human Southampton
Resources
... ... ... ... ... ...

CSAV200300-APG-EN-01 OpenText™ Content Server 129

Chapter 18 Content Intelligence Widget Configuration

[Link].1 Preparing to Visualize a Scheduled Data Chart for Very Large Data Sets

Performance Considerations for a Scheduled Data Chart for Very Large

Datasets

Note: This approach is most suitable for situations where you might expect a
very large number of results.

• In this scenario, only a subset of the results are returned to the browser. The
server-side SQL code in the LiveReport filters the results at the data layer.
• The data is fetched from the database periodically. You can define how
frequently the scheduling report runs, achieving the best balance between
placing heavy demands on the database versus how accurate and up-to-date the
results are.
• It is a good practice to tune your LiveReport to only return the data that you
need.

[Link].2 Step-by-step Walkthrough for a Scheduled Data Chart for Very Large Data Sets

Note: These examples have been tested for MSSQL and Oracle databases. If
you are using a different type of database, the syntax may differ.

To step through the process of visualizing a very simple chart with static data:

1. Create the LiveReport data source.

For more information about how to create a LiveReport, see OpenText Content
Server - LiveReports (LLESREP-H-UGD).

a. In Content Server, click Add Item to create a new LiveReport.

b. Edit the report and provide a Title and a Record Limit. For this example,
the Record Limit is 6.
c. Edit the LiveReport to add the following SQL code to the SQL section:
SELECT UPPER(FileType) AS Label, (SUM(DataSize)) AS
Count
FROM DVersData
WHERE FileType IS NOT NULL
AND FileType NOT LIKE '.%'
AND FileType != ''
GROUP BY UPPER(FileType)
ORDER BY Count DESC

d. In the Report Format area, select Auto LiveReport from the list.
e. Click Save and Exit.

2. Create a WebReports object that generates a static data file and runs on a
schedule:
For more information about how to create a WebReport, see OpenText Content
Server - WebReports (LLESWEBR-H-UGD).

a. In Content Server, click Add Item to create a new WebReports object.

130 ActiveView Perspective Manager CSAV200300-APG-EN-01

 18.4. Configuring the Visual Count Widget

b. On the Add WebReport page, in the Name section, enter a name for the
WebReport.
c. In the Data Sourcesection, click Browse Content Server and choose the
LiveReport created in Step 1.
d. In the Reportview file section, from the list, select Comma Separated
Values Report - Scripted.
e. Click Add.
f. Open the WebReport Properties, click the Destination tab, and make the
following changes:

Field Name Setting

Output Destination Select the Content Server option.
Name Type the name that you want for the
CSV file. For example:
grouped [Link]

Duplicate Name Action Select the Add Version to Original

option.
Create In Click Browse and select the location
that you want.
Export MIME Type From the list, click text/csv.
Export if no Data Clear the check box.
Set Schedule Select the check box.
Next run after Select the date and time that you want
the WebReport to first run. For example:
01/17/2017, 11:06 pm

Run Select how many times you want the

WebReport to run. For example: 1
Every Select how frequently you want the
WebReport to run. For example: Select
the 5-Minute Increments option.
g. Click Update.

3. Create a WebReports object that will format the data in the required way to
support the Visual Count Widget:

a. In Content Server, click Add Item to create a new WebReports object.

b. On the Add WebReport page, in the Name section, enter a name for the
WebReport.
c. In the Data Sourcesection, click Browse Content Server and choose the
CSV file created by the scheduled WebReport as a data source in Step 2.
d. In the Reportview file section, from the list, select Visual Count Widget -
Grouping in Data Source Simplified JSON.
e. Click Add.

CSAV200300-APG-EN-01 OpenText™ Content Server 131

Chapter 18 Content Intelligence Widget Configuration

f. Edit the properties for this WebReport.

g. Click the Destination tab and set the Export MIME Type to application/
json.
h. Click the Source tab and in the Row Separate box, click Clear and then
click LF.
i. Click Update.

4. Edit the reportview for this WebReport by making the following changes:

a. In the Header Section, add the COUNTFORMAT:"BYTES" tag. The results

should appear as follows:
[LL_WEBREPORT_INSERTJSON @FILTEREDCOUNT
ACTIVECOLUMN:"[LL_REPTAG_&active_column /]"
COUNTFORMAT:"BYTES"
GROUPBYINDATASOURCE:"TRUE" /]

for the following reasons:

• ACTIVECOLUMN:"[LL_REPTAG_&active_column /]" tells the system to

use the active column specified when creating the perspective.
• COUNTFORMAT:"BYTES" tells the Filtered Count widget to format and
display the data as BYTES. It will automatically append a unit. For
example, KB, MB, or GB, to the values returned from the CSV.
• GROUPBYINDATASOURCE:"TRUE" tells the tag that it should expect pre-
grouped data.

For more information about the @FILTEREDCOUNT directive, see the

INSERTJSON tag.
b. Click Add Version.

5. Create a perspective to see the chart in Smart View:

a. Sign in to Perspective Manager and create a perspective.

For more information about how to create a perspective, see the Online Help
available in Perspective Manager.
b. Configure a Visual Count widget with the following settings:

• Widget Size
If using the Flow layout, choose either Single width or Double width.
• Title
Storage by File Type
• Chart Type
Donut
• Source WebReport
<YourWebReportID> as created in Step 3.

132 ActiveView Perspective Manager CSAV200300-APG-EN-01

 18.4. Configuring the Visual Count Widget

• Active Column
Label
• Show Values as Percentages
Use the default value.
• Group After
Use the default value.
• Sort By
Use the default value.
• Sort Direction
Use the default value.
• Enable Tile Filtering Controls
Use the default value.
• Enable Expanded View
Use the default value.
c. Sign in to Smart View and verify that the Visual Count widget in the
Perspective produces the donut chart as shown in Figure 18-6.

Figure 18-6: Scheduled Data Chart (Very Large Data Set)

CSAV200300-APG-EN-01 OpenText™ Content Server 133

Chapter 18 Content Intelligence Widget Configuration

18.4.4 Preparing WebReports for the Custom Buttons

In the Expanded view of the Visual Count widget, end users can click the results in
the chart to further filter the data. When you edit the widget, you have the option to
configure one or more custom buttons to appear in the footer of the Expanded view.
You can associate each custom button with a WebReport that can provide additional
functionality using the filtered data. For example, bulk-changing document
properties, exporting the data to a CSV file, or changing the status of a workflow; in
other words, any operation that can be performed using WebReports tags.

To configure a custom button to appear in the Expanded view, you must prepare a
WebReport for each button. For example, you could create the following
WebReports:

• “Custom Button Example: Export to a CSV File” on page 136

• “Custom Button Example: Email Data to the User” on page 138
• “Custom Button Example: Save a Snapshot of the JSON Data” on page 140
• “Custom Button Example: Change the Owner of Filtered Documents”
on page 144

Note: When using a custom button to retrieve data, the WebReport returns
document metadata to the user, not grouped counts. This means that you must
make sure to apply permissions filtering. Some data sources automatically
apply permissions filtering or can be configured to do so. For more information
about how to configure permissions filtering, see the documentation for your
data source. If the data source does not have permission filtering, you can edit
the Row Section of the reportview that generates the JSON data to exclude
nodes to which the user does not have permissions by adding the following
tag:
[LL_WEBREPORT_INCLUDEIF "[LL_REPTAG=DATAID
PERMCHECK:SEECONTENTS /]" == "TRUE" /]

[Link] Passing Parameters to a WebReport Associated with a Custom

Button
When you configure a WebReport that will be associated with a custom button in
the Expanded view of the Visual Count widget, the widget automatically passes
request parameters that detail the current state of the application. For example, you
can process the rows and have the custom button WebReport reflect the current
Active Column selection and which filters are currently applied. The following list
includes the valid parameters that are available and automatically passed:

Parameter Tag and Description

• Active Column
[LL_REPTAG_&active_column /]
Name of the column in the data source that the WebReport uses for filtering the
data.

134 ActiveView Perspective Manager CSAV200300-APG-EN-01

 18.4. Configuring the Visual Count Widget

• Count Column
[LL_REPTAG_&count_column /]
Name of the column in the data source that contains the count values.
• Column Names
[LL_REPTAG_&column_names /]
Comma-separated list that shows the current columns available for grouping and
filtering.
• View Value as Percentage
[LL_REPTAG_&view_value_as_percentage /]
Boolean that indicates whether the values are displayed as a percentage of the
total or as the actual count.
• Group After
[LL_REPTAG_&group_after /]
Current threshold that determines how many distinct data values should be
displayed before grouping the remaining values under the label “Other”.
• Sort Column
[LL_REPTAG_&sort_by /]
Name of the column currently being used to sort the grouped data.
• Sort Direction
[LL_REPTAG_&sort_order /]
ASC or DESC string that indicates whether the grouped data is currently sorted
in ascending order or descending order.
• Total Count
[LL_REPTAG_&total_count /]
Total count of the data rows, including applied filters.
• Filters
[LL_REPTAG_&fc_filters /]
JSON array of the currently applied filters.

CSAV200300-APG-EN-01 OpenText™ Content Server 135

Chapter 18 Content Intelligence Widget Configuration

[Link] Custom Button Example: Export to a CSV File

You can use the WebReports Export to Desktop feature to create a WebReport that
will export the currently filtered rows in the Visual Count widget to a CSV file and
then prompt the end user to download that CSV file. You can then associate this
CSV WebReport to a custom button in the Expanded view of the Visual Count
widget.

1. “To create a WebReport that generates the JSON data:“ on page 136
2. “To create a WebReport that converts the JSON data to a CSV file:“ on page 136
3. “To create a WebReport that calls the other two WebReports to generate and
convert the data:“ on page 137

To create a WebReport that generates the JSON data:

1. Create a WebReports node that uses the Visual Count Widget - Grouping on
Client JSON default reportview.

2. Edit the WebReport properties as follows:

a. Click the Source tab.

b. In the Data Source section, select the data source to match the data source
being used by the Visual Count widget from which you want to launch the
custom button.
c. Click Update.

3. Edit the WebReport reportview as follows:

a. Add the following line to the INSERTJSON tag definition:

FILTERBY:"[LL_REPTAG_&fc_filters /]"

For example:
[LL_WEBREPORT_INSERTJSON @FILTEREDCOUNT
INCLUDECOLUMNS:"{'TYPE','FILESIZE'}"
FILTERBY:[LL_REPTAG_&fc_filters /]
GROUPBY:"FALSE"
COUNTFORMAT:"SI" /]

b. Add any additional configuration to match the WebReport that generates

the data for the Visual Count widget. For example, set the INCLUDECOLUMNS
or EXCLUDECOLUMNS values.

To create a WebReport that converts the JSON data to a CSV file:

1. Create a WebReports node that uses the Comma Separated Values Report -
Scripted default reportview.

2. Edit the WebReport properties:

a. Click the Destination tab.

b. In the Export MIME Type section, from the list, select text/csv.

136 ActiveView Perspective Manager CSAV200300-APG-EN-01

 18.4. Configuring the Visual Count Widget

c. Click Update.

To create a WebReport that calls the other two WebReports to generate and
convert the data:

1. Create a WebReports node that uses the Blank Report default reportview.

2. Edit the WebReport properties:

a. Click the Destination tab.

b. In the Output Destination section, from the list, select Desktop.
c. In the Download File Name box, enter a name for the CSV file.
d. In the Export MIME Type section, from the list, select text/csv.
e. Click Update.

3. Edit the WebReport reportview:

a. In the Header Section, add the following content:

[LL_REPTAG_$GETJSON RUNSWR:fc_filters:
[LL_REPTAG_&fc_filters /] TRIM FROMJSON
SETVAR:chartData /]

[LL_REPTAG_$CREATECSV RUNSWR:DSREQUESTDATA:
[LL_REPTAG_!chartData
ASSOC:data /]:DSFILETYPE:OSCRIPT SHOW /]

Notes

• This WebReport will call the GETJSON sub-WebReport to retrieve

the data rows as JSON, passing in the current filter information.
ThisWebReport has grouping disabled so that it will return every
row of data rather than grouped counts. The WebReport will
convert the data from JSON to an Oscript data format and set it as
the chartData WebReports variable.
• This WebReport will call the CREATECSV sub-WebReport and pass
in the data rows using the DSREQUESTDATA feature. This sets the
data source of the sub-WebReport using the data array from the
chart data returned from the GETJSON report. The sub-WebReport
will convert the JSON data and return the CSV data. The main
WebReport will then return the output to the desktop as specified
in the Destination settings and will prompt the user to download
the file.
b. Click Add Version & Continue.

4. Define the constants as follows:

a. On the Header row, click the Constant link.

b. In the new Properties window, on the Constants tab,
c. To automatically create two constants: CREATECSV and GETJSON, click the
Extract Constants from Content button .

CSAV200300-APG-EN-01 OpenText™ Content Server 137

Chapter 18 Content Intelligence Widget Configuration

d. For the GETJSON constant, in the Constant Type box, from the list, select
Content Server Object, click Browse, and then select the WebReport
created in “To create a WebReport that generates the JSON data:“
on page 136.
e. For the CREATECSV constant, in the Constant Type box, from the list, select
Content Server Object, click Browse, and then select the WebReport
created in “To create a WebReport that converts the JSON data to a CSV
file:“ on page 136.
f. Click Update and close the window.

5. Return to the reportview editor and click Add Version.

6. Sign in to the Perspective Manager, for the Visual Count widget, configure the
Button WebReports settings to associate this WebReport to the custom button.

7. Sign in to Smart View and verify the custom button in the Expanded View of
the Visual Count widget.

[Link] Custom Button Example: Email Data to the User

You can use the WebReports Email destination feature to create a WebReport that
will email the currently filtered rows in the Visual Count widget to the current user.
You can then associate this Email WebReport with a custom button in the Expanded
view of the Visual Count widget.

1. “To create a WebReport that generates the JSON data:“ on page 138
2. To create a WebReport that converts the JSON data to an HTML table:
on page 139
3. “To create a WebReport that calls the other two WebReport to generate and
convert the data:“ on page 139

To create a WebReport that generates the JSON data:

1. Create a WebReports node that uses the Visual Count Widget - Grouping on
Client JSON default reportview.

2. Edit the WebReport properties as follows:

a. Click the Source tab.

b. In the Data Source section, select the data source to match the data source
being used by the Visual Count widget from which you want to launch the
custom button.
c. Click Update.

3. Edit the WebReport reportview as follows:

a. Add the following line to the INSERTJSON tag definition:

FILTERBY:"[LL_REPTAG_&fc_filters /]"

For example:

138 ActiveView Perspective Manager CSAV200300-APG-EN-01

 18.4. Configuring the Visual Count Widget

[LL_WEBREPORT_INSERTJSON @FILTEREDCOUNT
INCLUDECOLUMNS:"{'TYPE','FILESIZE'}"
FILTERBY:[LL_REPTAG_&fc_filters /]
GROUPBY:"FALSE"
COUNTFORMAT:"SI" /]

b. Add any additional configuration to match the WebReport that generates

the data for the Visual Count widget. For example, set the INCLUDECOLUMNS
or EXCLUDECOLUMNS values.

To create a WebReport that converts the JSON data to an HTML table:

• Create a WebReports node using the HTML Table Report - Basic Scripted
default reportview.

To create a WebReport that calls the other two WebReport to generate and
convert the data:

1. Create a WebReports node that uses the Blank Report default reportview.

2. Edit the WebReport properties:

a. Click the Destination tab.

b. In the Output Destination section, select E-mail.
c. In the Email Address box, enter the following:
[LL_REPTAG_USERID USERINFO:MAILADDRESS /]

which will resolve to the email address of the current user who runs this
WebReport.
d. In the Email Subject box, enter a subject.
e. Click Update.

3. Edit the WebReport reportview:

a. In the Header Section, add the following content:

[LL_REPTAG_$GETJSON RUNSWR:fc_filters:
[LL_REPTAG_&fc_filters /] TRIM FROMJSON
SETVAR:chartData /]

[LL_REPTAG_$CREATETABLE RUNSWR:DSREQUESTDATA:
[LL_REPTAG_!chartData
ASSOC:data /]:DSFILETYPE:OSCRIPT SHOW /]

Notes

• This WebReport will first call the GETJSON sub-WebReport to

retrieve the data rows as JSON, passing in the current filter
information. This WebReport has grouping disabled so that it will
return every row of data rather than grouped counts. The
WebReport will convert the data from JSON to an Oscript data
format and set it as the chartData WebReports variable.
• This WebReport will call the CREATETABLE sub-WebReport and
pass in the data rows using the DSREQUESTDATA feature. This sets

CSAV200300-APG-EN-01 OpenText™ Content Server 139

Chapter 18 Content Intelligence Widget Configuration

the data source of the sub-WebReport to be the chart data returned

from the GETJSON report. The sub-WebReport will convert the data
to an HTML table and return it. The main WebReport will then
email the output to the user as per the Destination settings.
b. Click Add Version & Continue.

4. Define the constants as follows:

a. On the Header row, click the Constant link.

b. In the new Properties window, on the Constants tab,
c. To automatically create two constants: CREATETABLE and GETJSON, click the
Extract Constants from Content button .
d. For the GETJSON constant, in the Constant Type box, from the list, select
Content Server Object, click Browse, and then select the WebReport
created in “To create a WebReport that generates the JSON data:“
on page 138.
e. For the CREATETABLE constant, in the Constant Type box, from the list,
select Content Server Object, click Browse, and then select the WebReport
created in To create a WebReport that converts the JSON data to an HTML
table: on page 139.
f. Click Update and close the window.

5. Return to the reportview editor and click Add Version.

6. Sign in to the Perspective Manager and open the perspective that includes the
Visual Count widget to which you want to associate this custom button
WebReport.

7. On the Configure tab, select the Visual Count widget and configure the Button
WebReports settings to associate this WebReport to the custom button.

8. Sign in to Smart View and verify the custom button in the Expanded View of
the Visual Count widget.

[Link] Custom Button Example: Save a Snapshot of the JSON Data

You can use the WebReports Content Server destination feature to create a
WebReport that will save a snapshot of the JSON data for later use. You can then
associate this Snapshot WebReport to a custom button in the Expanded view of the
Visual Count widget.

1. “To create a WebReport that generates the JSON data snapshot:“ on page 141
2. “To create a WebReport that calls the JSON WebReport and redirects the user to
the snapshot overview:“ on page 141
3. “To create a WebReport that visualizes the snapshot as a chart for a new Visual
Count widget :“ on page 142

140 ActiveView Perspective Manager CSAV200300-APG-EN-01

 18.4. Configuring the Visual Count Widget

To create a WebReport that generates the JSON data snapshot:

1. Create a WebReports node that uses the Visual Count Widget - Grouping on
Client JSON default reportview.

2. Edit the WebReport properties:

a. Click the Source tab.

b. In the Data Source section, select the data source to match the data source
being used by the Visual Count widget from which you want to launch the
custom button.
c. Click the Destination tab.
d. In the Output Destination section, from the list, select Content Server.
e. In the Name box, enter a name for the JSON file.
f. In the Duplicate Name Action section, select Add Version to Original.
g. In the Create In section, click Browse Content Server and browse to the
location that you want.
h. Click Update.

3. Edit the WebReport reportview as follows:

a. Add the following line to the INSERTJSON tag definition:

FILTERBY:"[LL_REPTAG_&fc_filters /]"

For example:
[LL_WEBREPORT_INSERTJSON @FILTEREDCOUNT
INCLUDECOLUMNS:"{'TYPE','FILESIZE'}"
FILTERBY:[LL_REPTAG_&fc_filters /]
GROUPBY:"FALSE"
COUNTFORMAT:"SI" /]

b. Add any additional configuration to match the WebReport that generates

the data for the Visual Count widget. For example, set the INCLUDECOLUMNS
or EXCLUDECOLUMNS values.
c. Click Add Version & Continue.

To create a WebReport that calls the JSON WebReport and redirects the user
to the snapshot overview:

1. Create a WebReports node that uses the Blank Report default reportview.

2. Edit the WebReport reportview:

a. In the Header Section, add the following content:

[LL_REPTAG_$CREATEJSONFILE RUNSWR:fc_filters:
[LL_REPTAG_&fc_filters /]:SHOWNODEID SETVAR:nodeID /]
[LL_REPTAG_URLPREFIX SETVAR:url /]
[LL_REPTAG_'/app/nodes/' CONCATVAR:url /]
[LL_REPTAG_!nodeID CONCATVAR:url /]
[LL_REPTAG_!url REDIRECT /]

CSAV200300-APG-EN-01 OpenText™ Content Server 141

Chapter 18 Content Intelligence Widget Configuration

Notes

• This WebReport will first call the CREATEJSONFILE sub-WebReport

to retrieve the data rows as JSON, passing in the current filter
information. This WebReport has grouping disabled so that it will
return every row of data rather than grouped counts. The
WebReport will write the data to a new JSON file stored in Content
Server . The DataID for the new file is returned using the
SHOWNODEID option and set as a WebReports variable called NodeID.

• Next, we need to build a Smart View URL to this node and redirect
the user to it using the REDIRECT sub-tag. Although this WebReport
runs using a Classic View WebReports URL, this is hidden from the
user who is only aware that they start and end in Smart View. The
resulting URL will take the user to the document overview screen
for the new document and will resemble: [Link]
nodes/12345
b. Click Add Version & Continue.

3. Edit the WebReport properties:

a. Click the Constants tab.

b. To automatically create the CREATEJSONFILE constant, click the Extract
Constants from Content button .
c. For the CREATEJSONFILE constant, in the Constant Type box, change the
value to Content Server Object and then browse to the WebReport created
in “To create a WebReport that generates the JSON data snapshot:“
on page 141.
d. Click Update and close the window.

To create a WebReport that visualizes the snapshot as a chart for a new Visual
Count widget :

1. Create a WebReports node that uses the Blank Report default reportview.

2. Edit the WebReport properties:

a. Click the Source tab.

b. In the Data Source section, select the data source to match the data source
being used by the Visual Count widget from which you want to launch the
custom button.
c. Click the Destination tab.
d. In the Export MIME Type section, from the list, select application/json.
e. Click Update.

3. Edit the WebReport reportview:

a. In the Header Section, add the following content:

[LL_REPTAG_$GETJSONSNAPSHOT GETTEXT /]

142 ActiveView Perspective Manager CSAV200300-APG-EN-01

 18.4. Configuring the Visual Count Widget

Note: This WebReport uses the GETTEXT sub-tag to read in the JSON
and then return it to the chart. The data in the JSON file is ungrouped,
so you must choose an Active Column to group the data when the
chart is run.
b. Click Add Version & Continue.

4. Define the constant as follows:

a. On the Header row, click the Constant link.

b. In the new Properties window, on the Constants tab,
c. To automatically create the GETJSONSNAPSHOT constant, click the Extract
Constants from Content button .
d. For the GETJSONSNAPSHOT constant, in the Constant Type box, from the list,
select Content Server Object, click Browse, and then select the WebReport
created in “To create a WebReport that generates the JSON data snapshot:“
on page 141.
e. Click Update and close the window.

5. Return to the reportview editor and click Add Version.

6. Sign in to the Perspective Manager and open the perspective that includes the
Visual Count widget to which you want to associate this Button WebReport.

7. On the Configure tab, select the Visual Count widget

a. In the Source WebReport box, enter the ID for the WebReport created in
this procedure.
b. In the Active Column box, enter a column name.
c. In the Enable Tile Filtering Controls, select False.
d. In the Enable Expanded View box, select False.

Note: Since this is a static snapshot of the data at a particular point in

time, you must not enable the Tile filtering controls or the Expanded
view.
e. Click Create.

CSAV200300-APG-EN-01 OpenText™ Content Server 143

Chapter 18 Content Intelligence Widget Configuration

[Link] Custom Button Example: Change the Owner of Filtered

Documents
You can use the WebReports NODEACTION:OWNEDBY tag to change the owner of all
selected documents, if the current user has the appropriate permissions. You can
then associate this Change Owner WebReport to a custom button in the Expanded
view of the Visual Count widget.

1. “To create a WebReport that generates the JSON data:“ on page 144
2. “To create a WebReport that calls the JSON WebReport and redirects the user to
the snapshot overview:“ on page 141

To create a WebReport that generates the JSON data:

1. Create a WebReports node that uses the Visual Count Widget - Grouping on
Client JSON default reportview.
2. Edit the WebReport properties:

a. Click the Source tab.

b. In the Data Source section, select the data source to match the data source
being used by the Visual Count widget from which you want to launch the
custom button.
c. Click Update.
3. Edit the WebReport reportview as follows:

a. Add the following line to the INSERTJSON tag definition:

FILTERBY:"[LL_REPTAG_&fc_filters /]"

For example:
[LL_WEBREPORT_INSERTJSON @FILTEREDCOUNT
INCLUDECOLUMNS:"{'TYPE','FILESIZE'}"
FILTERBY:[LL_REPTAG_&fc_filters /]
GROUPBY:"FALSE"
COUNTFORMAT:"SI" /]

b. Add any additional configuration to match the WebReport that generates

the data for the Visual Count widget. For example, set the INCLUDECOLUMNS
or EXCLUDECOLUMNS values.
c. Click Add Version & Continue.

Note: For this example custom button, you must ensure that the data
source consists of nodes and the output JSON data includes the DataID
column.

To create a WebReport that calls the JSON WebReport to retrieve the data and
change the owner:

1. Create a WebReports node that uses the Blank Report default reportview.
2. Edit the WebReport reportview:

144 ActiveView Perspective Manager CSAV200300-APG-EN-01

 18.4. Configuring the Visual Count Widget

a. In the Header Section, add the following content:

[LL_REPTAG_$GETJSON RUNSWR:fc_filters:
[LL_REPTAG_&fc_filters /] TRIM FROMJSON
SETVAR:chartData /]
[LL_REPTAG_!chartData ASSOC:data PLUCK:DataID
EACH:"NODEACTION:OWNEDBY" /]

Notes

• This WebReport will first call the GETJSON sub-WebReport to

retrieve the data rows as JSON, passing in the current filter
information. This WebReport has grouping disabled so that it will
return every row of data rather than grouped counts. The
WebReport will convert the JSON data to Oscript data format and
set it as the chartData WebReports variable.

• This WebReport extracts a list of DataIDs in the JSON data and calls
NODEACTION:OWNEDBY for each node in the list. If the current user
has the appropriate permissions, they will be assigned as the new
owner.

b. Click Add Version & Continue.

3. Define the constant:

a. On the Header row, click the Constant link.

b. In the new Properties window, on the Constants tab,

c. To automatically create the GETJSON constant, click the Extract Constants

from Content button .

d. For the GETJSON constant, in the Constant Type box, from the list, select
Content Server Object, click Browse, and then select the WebReport
created in “To create a WebReport that generates the JSON data:“
on page 144

e. Click Update and close the window.

4. Sign in to the Perspective Manager and open the perspective that includes the
Visual Count widget to which you want to associate this Button WebReport.

5. On the Configure tab, select the Visual Count widget.

a. In the Source WebReport box, enter the ID for the WebReport created in
this procedure.

b. Click Create.

CSAV200300-APG-EN-01 OpenText™ Content Server 145

Chapter 19

Workflow Widget Configuration

This section describes the use and configuration of the following Workflow widgets:

• “Workflow Tracking Widget Configuration” on page 147

• “Workflow Monitoring Widget Configuration” on page 148

19.1 Workflow Tracking Widget Configuration

The Workflow Tracking widget displays the status of Workflows that are managed
or initiated by the current user. The user can track in-progress and completed
Workflows using this widget. You can configure one or more Workflow Tracking
widgets to appear on the Smart View Home page.

Title
Type a title. The title is displayed as the name of the tile on the Smart View
Home page. By default, the title is Workflow Tracking.

Days Completed Workflows Display

Type the number of days that completed Workflows display on the tile. For
example, type 30 to display all completed Workflows for 30 days after the
Workflows are complete.

Workflow Type
Choose the Workflow Types that display on the tile. Options include: Managed
Workflows, Initiated Workflows, or Both managed and initiated Workflows.

Reference
Choose None, Parent, or Custom from the Reference list to filter the Workflows
that the widget shows:

• None does not apply a filter and shows all Workflows that are managed or
initiated by the current user.

• Parent only shows Workflows related to the container that the current
perspective is configured for.

• Custom only shows Workflows related to the item chosen in the Custom
Reference list.

Custom Reference
Click Browse to choose an item to filter Workflows with. The widget will only
show Workflows related to the chosen item.

CSAV200300-APG-EN-01 OpenText™ Content Server 147

Chapter 19 Workflow Widget Configuration

19.2 Workflow Monitoring Widget Configuration

The Workflow Monitoring widget displays Workflows that meet the search criteria
defined in a Workflow Status Item. A Workflow Status Item must exist before you
can configure this widget. For more information about Workflow Status Items, see
OpenText Content Server - Workflows (LLESWFW-H-UGD). You can configure one or
more Workflow Monitoring widgets to appear on the Smart View Home page.

Title
Type a title. The title is displayed as the name of the tile on the Smart View
Home page. By default, the title is Workflow Monitoring.
Workflow Status Filter
Browse Content Server to find and select the defined Workflow Status Item that
filters the Workflows that display on the tile.

148 ActiveView Perspective Manager CSAV200300-APG-EN-01

Chapter 20
Extended ECM for SAP SuccessFactors Widget
Configuration

20.1 Inbox widget

This widget can only be included in the HR Administrator landing page.

HR Administrator, Manager and Employees can upload documents to employee

workspaces. When an Employee or a Manager on behalf of his team members
initiates the document upload, a task request is created and the document is moved
into a temporary folder in Content Server. The task requests with their status are
displayed in the info-graphics view of the Inbox widget, where the HR
Administrator can view and process the tasks. For details how to use the Inbox, see
OpenText Extended ECM for SAP SuccessFactors - User Guide (EESU-UGD).

The HR Administrator can process the task as follows:

• Approve – The document is assigned to the employee file/workspace.

• Deny – The document is rejected by the HR Administrator.
• Forward – There may be more than one HR Administrator assigned to an
employee workspace. The task recipient can assign this task to another HR
Administrator available for the employee workspace.

CSAV200300-APG-EN-01 OpenText™ Content Server 149

Chapter 20 Extended ECM for SAP SuccessFactors Widget Configuration

This widget is part of the Extended ECM for SAP SuccessFactors module.

Widget options in the Perspective Manager:

• Title - enter title for the widget.

• Initial - enter the default task status which should be displayed clicking on the
Inbox title, for example open,new,approved,denied,forwarded.

20.2 My Team’s To-Dos widget

Implemented on the HR Administrator or Manager landing page, the widget lists
outdated or missing documents of the employees assigned to their team. In the
expanded view, you can view more details, for example missing and outdated
document types.

Widget options in the Perspective Manager:

• Title - enter title for the widget.

150 ActiveView Perspective Manager CSAV200300-APG-EN-01

 20.3. Employee workspace widget

20.3 Employee workspace widget

New: With installed update of September 2019, you can enable providing the
effective date of a generated document using Document Generation Quick
Action icon.

As HR Administrator or Manager, you can access the workspaces of the employees

that you are allowed to view in the Employee Workspaces widget. The Employee
Workspaces widget can be accessed on the respective Content Server landing page
or embedded in the SuccessFactors landing page. You can configure the Employee
workspace widget for Employee and Candidate workspaces.

Widget options in the Perspective Manager

• Width – define the widget width in relation to the screen size.

• Title - set title for the widget.
• Workspace Type - from the list, select Workspace type, for example, Employee.
• Display Document Generation - select True to show the Document Generation
icon in the widget or False to hide the icon. The default setting is False.
• Enable Effective Date Input - Select True to enable the effective date option. See
“Customizing Effective Date input option for document generation”
on page 152OpenText Extended ECM for SAP SuccessFactors - Customizing Guide
(EESU-CGD) for more information.

Note: The effective date option supports only the SuccessFactors user
business object and its data attributes.

CSAV200300-APG-EN-01 OpenText™ Content Server 151

Chapter 20 Extended ECM for SAP SuccessFactors Widget Configuration

20.3.1 Customizing Effective Date input option for document

generation
The Effective Date can be applied to a document to be generated. You must enable
the effective date option in PowerDocs ContentManager and for the HR
Administrator landing page in the Perspective Manager.

Customizing steps in PowerDocs ContentManager:

1. Log in to PowerDocs Content Manager.

2. Click Technical Settings > Integration. In the Scripts list, edit the SF Query
URL script.

3. In the Script box, enter the following text:

<xsl:stylesheet version="2.0"
xmlns:xsl="[Link]
xmlns:fo="[Link]
<xsl:output method="text" version="1.0" encoding="UTF-8"
indent="no"/>
<xsl:template match="/">
<xsl:apply-templates select="//businessobject"/>
</xsl:template>
<xsl:template match="businessobject">
<xsl:choose>
<xsl:when test="query/input/value and query/
input/value!=''">
<xsl:value-of select="mappings/map[
@name='module_name']"/>
<xsl:text>?</xsl:text>

<!-- FILTER-Part -->

<xsl:text>$filter=</xsl:text>
<xsl:for-each select="query/input/value[
@parameter!='asOfDate' and
@parameter!='includeInactive']">
<xsl:choose>
<xsl:when test="contains(@parameter,'/')">

152 ActiveView Perspective Manager CSAV200300-APG-EN-01

 20.3. Employee workspace widget

<xsl:value-of select="substring-after(
@parameter,'/')"/>
</xsl:when>
<xsl:otherwise>
<xsl:value-of select="@parameter"/>
</xsl:otherwise>
</xsl:choose>
<xsl:text>%20eq%20%27</xsl:text>

<!--xsl:value-of select="."/-->

<xsl:value-of select="."/>
<xsl:text>%27</xsl:text>
<xsl:if test="position()!=last()">
<xsl:text> and </xsl:text>
</xsl:if>
</xsl:for-each>
<xsl:if test="query/input/value[
@parameter='includeInactive' and .='true']">
<xsl:text>%20and%20%28status%20eq%20%27
inactive%27%20
or%20status%20eq%20%27active%27%29
</xsl:text>
</xsl:if>
<xsl:if test="query/input/
value[@parameter='asOfDate']">
<xsl:text>&amp;asOfDate=</xsl:text>
<xsl:value-of select="query/input/value[
@parameter='asOfDate']"/>
</xsl:if>
<xsl:text>&amp;</xsl:text>

<!-- SELECT-Part -->

<xsl:for-each select="properties/property/map">
<xsl:if test="position()=1">
<xsl:text>$select=</xsl:text>
</xsl:if>
<xsl:choose>
<xsl:when test="contains(.,'__metadata/uri')">
<xsl:call-template name=
"substring-before-last">
<xsl:with-param name="string1" select="."/>
<xsl:with-param name="string2"
select="'/__metadata'"/>
</xsl:call-template>
<[Link]>/</[Link]>
<xsl:value-of select="//businessobject
/mappings/map[@name='identifier']"/>
</xsl:when>
<xsl:when test="contains(.,'__deferred/uri')">
<xsl:call-template name=
"substring-before-last">
<xsl:with-param name="string1" select="."/>
<xsl:with-param name="string2"
select="'/__deferred'"/>
</xsl:call-template>
</xsl:when>
<xsl:otherwise>
<xsl:value-of select="."/>
</xsl:otherwise>
</xsl:choose>
<xsl:if test="position()!=last()">
<xsl:text>,</xsl:text>
</xsl:if>
<xsl:if test="position()=last()">
<xsl:text>&amp;</xsl:text>
</xsl:if>
</xsl:for-each>

<!-- EXPAND-Part -->

CSAV200300-APG-EN-01 OpenText™ Content Server 153

Chapter 20 Extended ECM for SAP SuccessFactors Widget Configuration

<xsl:for-each select="properties/property/
map[contains(.,'/')]">
<xsl:if test="position()=1">
<xsl:text>$expand=</xsl:text>
</xsl:if>
<xsl:variable name="substring-after-last">
<xsl:call-template name=
"substring-after-last">
<xsl:with-param name="string1"
select="."/>
<xsl:with-param name="string2"
select="'/'"/>
</xsl:call-template>
</xsl:variable>
<xsl:choose>
<!--xsl:when test="ends-with($substring-
after-last,'Nav')">
<xsl:value-of select="."/>
</xsl:when-->
<xsl:when test="$substring-after-last!
='uri'">
<!--xsl:value-of select=
"substring-before(.,'/')"/-->
<xsl:call-template name=
"substring-before-last">
<xsl:with-param name=
"string1"select="."/>
<xsl:with-param name=
"string2"select="'/'"/>
</xsl:call-template>
</xsl:when>
<xsl:when test="$substring-after-
last='uri'">
<xsl:choose>
<xsl:when test="contains
(.,'/__deferred')">
<xsl:call-template
name="substring-
before-last">
<xsl:with-param
name="string1"
select="."/>
<xsl:with-param
name="string2"
select=
"'/__deferred'"/>
</xsl:call-template>
</xsl:when>
<xsl:otherwise>
<xsl:call-template
name="substring-
before-last">
<xsl:with-param
name="string1"
select="."/>
<xsl:with-param
name="string2"
select="'/__metadata'"/>
</xsl:call-template>
</xsl:otherwise>
</xsl:choose>
</xsl:when>
</xsl:choose>
<xsl:if test="position()!=last()">
<xsl:text>,</xsl:text>
</xsl:if>
<xsl:if test="position()=last()">
<xsl:text>&amp;</xsl:text>
</xsl:if>
</xsl:for-each>

154 ActiveView Perspective Manager CSAV200300-APG-EN-01

 20.3. Employee workspace widget

</xsl:when>
<xsl:otherwise>
<xsl:text>odata/v2/</xsl:text>
<xsl:value-of select=
"mappings/map[@name='module_name']"/>
<xsl:text>?$filter=</xsl:text>
<xsl:value-of select=
"mappings/map[@name='identifier']"/>
<xsl:text>%20eq%20%27</xsl:text>
<xsl:text>0</xsl:text>
<xsl:text>%27</xsl:text>
</xsl:otherwise>
</xsl:choose>
</xsl:template>
<xsl:template name="substring-before-last">
<xsl:param name="string1" select="''"/>
<xsl:param name="string2" select="''"/>
<xsl:if test="$string1 != '' and $string2 != ''">
<xsl:variable name="head"
select="substring-before($string1, $string2)"/>
<xsl:variable name="tail"
select="substring-after($string1, $string2)"/>
<xsl:value-of select="$head"/>
<xsl:if test="contains($tail, $string2)">
<xsl:value-of select="$string2"/>
<xsl:call-template name="substring-before-last">
<xsl:with-param name="string1"
select="$tail"/>
<xsl:with-param name="string2"
select="$string2"/>
</xsl:call-template>
</xsl:if>
</xsl:if>
</xsl:template>
<xsl:template name="substring-after-last">
<xsl:param name="string1"/>
<xsl:param name="string2"/>
<xsl:choose>
<xsl:when test="contains($string1, $string2)">
<xsl:call-template name="substring-after-last">
<xsl:with-param name="string1"
select="substring-after
($string1, $string2)"/>
<xsl:with-param name="string2"
select="$string2"/>
</xsl:call-template>
</xsl:when>
<xsl:otherwise>
<xsl:value-of select="$string1"/>
</xsl:otherwise>
</xsl:choose>
</xsl:template>
<xsl:template name="substring-before-sfsfNavigation">
<xsl:param name="string1"/>
<xsl:choose>
<xsl:when test="ends-with($string1,'Nav')">
<xsl:call-template
name="substring-before-sfsfNavigation">
<xsl:with-param name="string1"
select="substring-before($string1, '/')"/>
</xsl:call-template>
</xsl:when>
<xsl:otherwise>
<xsl:value-of select="$string1"/>
</xsl:otherwise>
</xsl:choose>
</xsl:template>
</xsl:stylesheet>

4. Click Change.

CSAV200300-APG-EN-01 OpenText™ Content Server 155

Chapter 20 Extended ECM for SAP SuccessFactors Widget Configuration

To customize landing page perspective for HR Administrator:

1. Log in to Content Server as administrator and edit the HR Administrator

landing page in the Perspective Manager.

2. For the Employee Workspaces widget, select True for the Enable Effective Date
Input option.

3. Log in as HR Administrator. In the Employee Workspaces widget, click the

Document Generation icon for an employee workspace. The icon becomes
available when hovering over the workspace entry.

156 ActiveView Perspective Manager CSAV200300-APG-EN-01

 20.3. Employee workspace widget

4. The date picker for selecting an effective date displays. Click the Date
picker icon and select a date to define the effective date.

5. Click Create to start generating the document.

CSAV200300-APG-EN-01 OpenText™ Content Server 157

Chapter 20 Extended ECM for SAP SuccessFactors Widget Configuration

20.4 Tasks widget

This widget is placed in the Employee workspace container and shows the created
tasks for this specific employee workspace. If the user is an employee and opens the
employee workspace container, the Tasks widget shows only tasks created by the
employee. When a user is a Manager and opens the employee workspace of one of
his reporting employees, the Tasks widget shows only the created by the Manager
for this employee. Finally, when the user is a HR Administrator and opens the
employee workspace, it shows all tasks created by Employee or Manager.

158 ActiveView Perspective Manager CSAV200300-APG-EN-01

 20.4. Tasks widget

Widget options in Perspective Manager

• Width – define the widget coverage area

CSAV200300-APG-EN-01 OpenText™ Content Server 159

Chapter 20 Extended ECM for SAP SuccessFactors Widget Configuration

• Title – set widget title

20.5 Activity Logs widget

New: With installed update of September 2019, you can display documents to
be deleted in the Activity Logs widget by enabling the Display Deletion
Workflow option in the Perspective Manager.

The Activity Logs widget is included in the Employee workspace container for all
functional rights Employee, Manager and HR Administrator and shows the
document specific activities that happened on this specific employee workspace.

Note: The Activity Logs widget shows information from the Content Server
audit history. If the audit history has been cleared, activities in the Activity
Logs widget are not displayed either.

160 ActiveView Perspective Manager CSAV200300-APG-EN-01

 20.5. Activity Logs widget

Widget options in the Perspective Manager

• Width – define the widget coverage area

• Title – set title for the widget
• Display Deletion Workflow – select True if you want to display documents to
be deleted in the Activity Logs widget. The True option is set per default.

CSAV200300-APG-EN-01 OpenText™ Content Server 161

Chapter 20 Extended ECM for SAP SuccessFactors Widget Configuration

Note: The logged in user sees the information for which he has See
permission in Content Server. Since the See permission does not apply to
the Delete Document audit activity, by default all Delete audits will be
displayed. If you do not want to display any Delete Document Audit
activities, you must select the False option.

162 ActiveView Perspective Manager CSAV200300-APG-EN-01

 20.6. Document Self Service widget

20.6 Document Self Service widget

In the Document Self Service widget, all users with the functional rights Employee
and Manager can initiate document uploading and task creation. For details how to
use the Document Self Service widget, see OpenText Extended ECM for SAP
SuccessFactors - User Guide (EESU-UGD).

CSAV200300-APG-EN-01 OpenText™ Content Server 163

Chapter 20 Extended ECM for SAP SuccessFactors Widget Configuration

Important
For the document types in the DocumentType classification, you must have
assigned unique names. If you use duplicate document type names, uploaded
documents can be stored in the wrong folder.

Widget options in the Perspective Manager

• Title – set widget title.

• Width – define widget coverage area.

164 ActiveView Perspective Manager CSAV200300-APG-EN-01

 20.7. Reports widget

20.7 Reports widget

The Reports is only available for the HR Administrator. It provides the following
reports specific to the employee workspace:

• Documents you added

• Missing documents
• Outdated documents
• Last 10 added documents

Widget options in the Perspective Manager:

• Width – Define the widget coverage area

• Title – set widget title
• Hide Report – hide individual reports

20.8 Create Documents widget

In the Create Document widget available for the HR Administrator landing page,
you can process SAP SuccessFactors workflow steps for HR events, for example, a
relocation of an employee. In this workflow step, you can generate documents
required for the event and then store them to the workspace of the affected
employee.

For setting up the required configuration in SAP SuccessFactors, PowerDocs and

Extended ECM, see OpenText Extended ECM for SAP SuccessFactors - Customizing
Guide (EESU-CGD).

CSAV200300-APG-EN-01 OpenText™ Content Server 165

Chapter 20 Extended ECM for SAP SuccessFactors Widget Configuration

Widget options in the Perspective Manager:

• Title – set widget title.

20.8.1 Configuring user name display

You can configure how to display the user name in the widget.

To configure user name display:

1. On the Content Server Administration page, go to Configure User Name

Display.

2. Configure the name format to be displayed for users. For the Create Document
widget, we recommend to select the FirstName LastName and the Append Log-
in ID check box options.

166 ActiveView Perspective Manager CSAV200300-APG-EN-01

 20.8. Create Documents widget

CSAV200300-APG-EN-01 OpenText™ Content Server 167

Chapter 21

Extended ECM Platform Widget Configuration

21.1 Business Attachments widget

The Business Attachments widget displays documents and other Content Server
items that are attached to a business object. Business attachments usually are not
stored in a business workspace. If not configured otherwise and if the widget is used
in a workspace perspective, the widget displays business attachments for the
business object of the business workspace. You can also display business objects for
other business object.

Users can create a snapshot for all business attachments displayed in the widget.
Snapshots are folders in Content Server, which contain a Generation of the latest
version of each business attachment that is a document. A Generation is a copy of a
document, which is separated from the original document, unlike a version. For
more information, see the Content Server help. The snapshot contains a shortcut to
objects other than documents. The name of the folder starts with a prefix, which you
configure for the widget.

In the expanded view, you see additional information for each business attachment
such as description, location and version.

General

Property Description
Title Title of the Business Attachments widget.
Default is Business attachments.
Snapshot folder name prefix Prefix that is added to the snapshot folder
when you create a snapshot from this
widget. A snapshot freezes the current
version of all business attachments of the
business object and stores them in a folder.

Business attachment

Property Description
Business object ID Category attribute that contains the ID of the
business objects for which you want to
display business attachments.
Business object type Category attribute that contains the business
object type.

CSAV200300-APG-EN-01 OpenText™ Content Server 169

Chapter 21 Extended ECM Platform Widget Configuration

Property Description
Business application ID Category attribute that contains the ID of the
business application where the business
object type resides.

If you want to use attribute sets in these fields, you must use the following format:
{categories.<category ID>_<set number>_<attribute ID>}, for example,
{categories.37275_33_1_34}. If the attribute picker does not provide this format,
you must enter it manually.

• Category ID: 37275

• Set: 33
• Line of set: 1
• Attribute ID number: 34

To retrieve the attribute ID, run the following report: <URL of content server>?
func=[Link].

Collapsed view

Property Description
Message for empty result Custom message if no business attachments
are available.
Order by Orders the list of business attachments by a
column. The default sorting is ascending by
the name of the business attachment.

If you have not selected a column in the

Order by option, the attachments are
ordered by the name. If you selected a
custom column that is not configured for
ordering, an error message is displayed
when the widget is loaded.
Business attachment title Name of the business attachment in the
collapsed view. You can use one of the
following variables: {name},
{description}, {type_name},
{modify_date}, {create_date}. The
{name} variable uses the name of the
business workspace, which may already be
assembled from several attributes.
Business attachment description Description of the business attachment. You
can use one of the following variables:
{name}, {description}, {type_name},
{modify_date}, {create_date}. The
{name} variable uses the name of the
business workspace, which may already be
assembled from several attributes.

170 ActiveView Perspective Manager CSAV200300-APG-EN-01

 21.2. Dossier widget

Property Description
Metadata fields Additional fields to display metadata in the
widget. Enter a label and the value. You can
use one of the following variables: {name},
{description}, {type_name},
{modify_date}, {create_date}. The
{name} variable uses the name of the
business workspace, which may already be
assembled from several attributes.

Expanded view

Property Description
Order by Orders the list of business attachments by a
column and defines the sort direction.

Snapshot

Property Description
Parent folder name Folder in business workspace, where
Snapshots are created.
Snapshot name prefix The name of a snapshot consists of the prefix
and a timestamp.

21.2 Dossier widget

The Dossier widget displays all documents in the business workspaces.

Property Description
Default group by criterion Groups the documents by their creation date
or a classification.
Hide group by criterion dropbox Provides an option for users to hide certain
groups of documents. The default settings
display the dropbox.
Hide metadata Provides an option for users to hide
metadata of documents. The default settings
display the metadata.
Hide empty fields Hide metadata fields that contain no data.
The default settings display empty metadata
fields.

CSAV200300-APG-EN-01 OpenText™ Content Server 171

Chapter 21 Extended ECM Platform Widget Configuration

21.3 Header widget with business object information

The Header widget of the Extended ECM Platform module contains information
about the business objects and connections to the respective business application.

Note: Do not use multivalue attributes and multi-row set attributes in the
header widget.

Workspace Properties

Property Description
Title Name of the business workspace, prefilled
with the {name} node property.
Type Name of the workspace type, prefilled with
the {business_properties.
workspace_type_name} business
property.
Description Description of the business workspace,
prefilled with the {description} node
property.

Workspace properties are displayed in the left part of the Header widget in the
following top-down order, with the font becoming smaller. You can use the
suggested properties, add others, and combine attributes and properties with text.

• Business properties must be configured with the business_properties prefix,

for example {business_properties.workspace_type_name}.

– {business_properties.workspace_type_name}: Name of workspace type.

– {business_properties.workspace_type_id}: ID of the workspace type,
useful for testing and preparing perspectives.
• Node properties require no prefix, for example {name}.

– {name}: Workspace name.

– {description}: The workspace node description.
– {type_name}: Name of the Content Server item type: Business Workspace.
– {create_date}: Date when business workspace was created, formatted
according to the current formatting rules.
– {create_user_id}: Name of the user who created the business workspace,
formatted to the user's readable display name.
– {modify_date}: Date when the business workspace was modified.
– {modify_user_id}: Name of the user who modified the business workspace,
formatted to the user's readable display name.
– {owner_group_id}: Name of the group the workspace owner belongs to.

172 ActiveView Perspective Manager CSAV200300-APG-EN-01

 21.3. Header widget with business object information

– {owner_user_id}: Name of the workspace owner, formatted to the user's

readable display name.
• Category attributes
Click Add Attribute to Field and select attributes from the categories that
contain information for this business workspace. You cannot use attribute sets for
this.

Completeness check settings

You can configure rules that define which document a business workspace must be
contain. The completeness check displays the number of missing documents.

Widget
You can embed another widget in the header widget. It depends on your system,
which widgets are available.

Property Description
Embed Widget Select one of the available widgets to embed
it into the header widget. It is displayed in
the right half of the header widget. Currently
available is the Activity Feed widget, which
displays all activities in relation to this
business workspace and its related child
workspaces. You see comments or recently
added documents.

If you want to use the Activity Feed widget,

you must enable Content Server Pulse and,
optionally, create activity manager objects.
For more information, see OpenText
Connected Workspaces - Configuration Guide
(CSCWS-CGD).

Metadata settings

Property Description
Hide metadata Provides an option for users to hide
metadata of documents. The default settings
display the metadata.
Hide empty fields Hide metadata fields that contain no data.
The default settings display empty metadata
fields.

CSAV200300-APG-EN-01 OpenText™ Content Server 173

Chapter 21 Extended ECM Platform Widget Configuration

Property Description
Metadata The Header widget uses data from category
attributes. You select a category or single
attributes. To group attributes, enter a group
name and then select the categories and
attributes. Leave the group name empty to
add a category or attribute without a group.
Drag attributes or groups to change the
order.

You cannot use Boolean attributes in the

Header widget. Use the metadata widget to
display this type of data.
• Group name – Name of a group of
attributes or categories
• Category or attribute – Category or
single attributes. You can use the
following data sources: A single attribute
or a complete category with all its
attributes.

Favorite
You can hide the Favorite button in the Header widget.

21.4 Scan barcode widget

Scan the QR code of an object and open the business workspace of that object.

In the configuration of this widget, select one or more business object types. The
business object type must have a configuration for the category attribute, which
contains the barcode value.

For more information, see the following:

•
• OpenText Content Server Mobile - Configuration Guide (CSMOB-CGD)

174 ActiveView Perspective Manager CSAV200300-APG-EN-01