
The navigation structure of a room or room part that is created on the basis of a particular template is represented by a workset in the Portal Content Directory (PCD). A workset is structured using pages. A page can contain several iViews - the actual applications.
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 unique assignment between the template and the workset means that you can change the workset for the copy of the template. The changes only relate to the assigned template. They affect only the rooms that a user creates 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.
| Type of Template | Folder in the PCD |
|---|---|
|
Room template |
TemplateWorksets |
|
Room part template |
RoomPartTemplate Worksets |
Change the workset structure.
| 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.
Translate the workset.
If the rooms are to be provided in a particular language, you must translate the workset for the template, 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 in the PCD |
|---|---|
|
Room template |
TemplateWorksets |
|
Room part template |
RoomPartTemplate Worksets |