Start of Content Area

Procedure documentation Configuring Collaboration Services  Locate the document in its SAP Library structure

Use

You can determine which collaboration services are available on the Collaboration Launch Pad (CLP), in the Room Member List, on the user interface of the User Details iView, and in the context menu for each user throughout the portal.

Users launch the services using menus. Exception: On the user interface of the User Details iView, links are provided for launching services that are frequently required.

Note

SAP delivers predefined groups of services that you can activate during the basic configuration. You only need to configure the services if you want to provide company-specific groups of services.

Overview

The graphic below uses the CLP as an example to illustrate the configuration steps required to make services available in the Collaboration menu.

This graphic is explained in the accompanying text

..

     Grouping the commands (1) for launching services in one main group, which can consist of subgroups or individual commands.

     Assigning the main group to the configuration object (Type) that corresponds to the purpose (2) – in this example, to clpType.

     Assigning the technical key for this type (resource type key) to the CLP iView (3).

     Testing the corresponding links in the CLP iView (4).

Procedure

Make Services Available in Menus

       1.      In the portal, choose Content Administration Collaboration Content Collaboration Launch Pad Administration.

       2.      Group the commands for launching services.

Each command (link command) controls the launching of a service through the corresponding link. For each service, SAP delivers two command variants – one for the Collaboration menu and one for the context menu.

Caution

Do not change the commands delivered by SAP.

The following applies when grouping the services:

     You can create subgroups of commands to structure the menus, for example, a command group for synchronous services. As with main groups, you create subgroups as command groups.

     You can assign both command groups (command groups) and individual commands (link commands) to the main group.
Exception: You cannot create subgroups for links to services that are provided on the user interface of the User Details iView.

       3.      Assign the main group of commands to the application.

The application – the iView that provides the commands for launching services – is represented by a type (for example, clpType for the CLP).

To define the application for a main group of commands, assign the main group to one of the following attributes of the corresponding type:

     Services for CLP, Member List, or User Details
Assign the corresponding main group of commands to the contextmenu_commandgroup attribute for the type.

     Services in the context menu for displayed users or user groups
Assign the corresponding command group to the contextmenu_commandgroup attribute for the type. In addition, assign the command for launching the User Details iView through a mouse-click (left mouse button) to the leftclick_command attribute.

Note

Note the implementation of the commands:

      For services in the CLP Collaboration menu and the Member List, you must use only commands with the implementation CLPUICommand.

      For the remaining cases, you must use only commands with the implementation UILaunchCommand.

       4.      Assign the type to the resource type that provides services in the menu (type mapping). These resource types include:

     Users or user groups

     iViews such as the CLP and the Member List

Note

To make the corresponding group of services available in the Collaboration menu, the resource type must be entered in the iView properties in the Type Mapping Key field.

       5.      Test the settings by launching the menus in question.

Restrict Services for Portal Roles

...

       1.      Copy the commands to a separate namespace, if you want to restrict the roles they can be used by. This ensures that you changes are retained after an upgrade.

       2.      Enter the ID of the portal role in the attributes of the corresponding command below portalRoles. For example, for room creation, you should enter the ID of the corresponding portal role. You use a comma to separate more than one portal role.
If no portal role has been entered, the service is available for all portal users.

Configure the Collaboration Menu for the Room Member List Differently to the CLP Collaboration Menu

By default, the configuration of the Collaboration menu applies to both the CLP and the Room Member List. If you want to provide different services in the Room Member List to those in the CLP, proceed as follows:

...

       1.      Create a new command group for the Member List and assign the required commands to this group.

If required, you can create subgroups of commands and assign these to the main group of commands for the Member List.

       2.      Create a new type for the Member List and in contextmenu_commandgroup, assign the main group of commands defined for it to this type.

       3.      Assign the new type to the Member List iView.

To do this, you enter the resource type in the properties of the Member List iView in the Type Mapping Key field.

Note

You can also make available a separate group of services for each room template. To do this, create a separate Member List iView for each room template and configure the services required as described above.

See also:

Standard Configuration

Assigning Portal Roles for Collaboration To Users

iViews with Collaboration Services

 

 

End of Content Area