The structure of the rooms and room parts is represented by a workset for each template in the Portal Content Directory (PCD). The workset for a template defines the navigation structure of the rooms that users create based on the template.
A workset is structured using pages. A page can contain several iViews - the actual applications. If required, you can add special applications, for example, BI analyses or ERP Web Dynpros, to the worksets for the templates.
Role-Specific Workset Structure
In the template, you define for each room role the access permissions for pages in the room. Therefore, the grouping of the iViews on the pages must correspond to the responsibilities of the room roles.
Unique Assignment Between Workset and Template
The assignment of the workset to a template is one-to-one, so that changes to the assigned worksets affect only the respective template. When copying a template, the system creates both a copy of the template properties and a copy of the workset for the source template.
The assignment between the workset and the room is also unique. If you change the workset for a template, the changes affect only the rooms that you create using the new version of the template.
Your user has a portal role, for example Content Administration, with write permission for the com.sap.ip.collaboration PCD folder.
1. Create or open workset.
Reason: When you create a template, the system suggests only the worksets in this folder for assignment to the template.
You can change these worksets, however, the changes do not affect existing templates.
You can also add suitable worksets from other folders to the folder of available worksets (as a copy or as a delta link, which takes into account changes to the original object).
Type of Template | Folder of Available Worksets (Create) |
---|---|
Room template |
Worksets |
Room part template |
RoomPartContent |
Reason: When you assign a workset to a template, the system stores a copy of the template in the folder for the assigned workset.
Changes to the workset apply only to the associated template.
Type of Template | Folder of Assigned Worksets (Change) |
---|---|
Room template |
TemplateWorksets |
Room part template |
RoomPartTemplate Worksets |
2. Define the room structure in the workset.
Folder with Pages and iViews for Worksets | Use |
---|---|
TemplateAndPartContent → Generic |
Room and room part templates |
RoomPartContent → Generic |
Room part templates |
To retain clarity, you should create the new pages and iViews for template worksets in the folders listed above or copy them to these folders.
To make sure that new iViews have the necessary properties for displaying parameter values such as the room ID, use the iViews in the com.sap.netweaver.coll.appl.ui.room portal component as templates as far as possible.
3. Optional: Translate workset.
If you require rooms in more than one language, you must translate the workset for the template in question, that is, the user interface texts on the associated pages and iViews, in the PCD folder in which the system stores the assigned worksets:
Type of Template | Folder of Assigned Worksets |
---|---|
Room template |
TemplateWorksets |
Room part template |
RoomPartTemplate Worksets |