Continuing with the example of adding three panels to the Customer Management page, the following properties will be changed for the panel definition. Please note that:
The
appIdproperty must be set toworkspacefor the panel to be loaded in Service CenterThe
accessRightmay remain the defaultGlobalPanelright or a specific right. If using a specific right, the right must be defined and assigned to Service Center users. Note: The access right must be defined or the tab will not be rendered
The following provides an example of code that adds three new panels, myNewPanel1, myNewPanel2 and myNewPanel3, to the WsCustomerPanelStack panel stack definition:
Create the
mypanel1.jsp,mypanel2.jspandmypanel3.jspfiles that will be called by the panel definitions. Create these files in the/panels/order/directory of your custom application.Create the
/atg/svc/framework/serviceFramework.xmlfile in your custom application directory.To this file, add a panel stack definition that contains the three new panels and their priorities. This appends your new panels to the existing information that creates the Customer Panel Stack. For example:
<panel-stack-definition>
<id>WsCustomerPanelStack</id>
<panel-ids>
<id-entry>
<id>myNewPanel1</id>
<priority>4</priority>
</id-entry>
<id-entry>
<id>myNewPanel2</id>
<priority>5</priority>
</id-entry>
<id-entry>
<id>myNewPanel3</id>
<priority>6</priority>
</id-entry>
</panel-ids>
</panel-stack-definition>Add a panel definition for each of the new panels. The following example displays the code for one of the three panels:
<panel-definition>
<id>myNewPanel1</id>
<app-id>workspace</app-id>
<enabled-yn>true</enabled-yn>
<object-type>PanelDefinition</object-type>
<resource-bundle>atg.commerce.csr.FrameworkResources</resource-bundle>
<template-ids>
<map-entry>
<key>panelTemplate</key>
<value>panelTemplate</value>
</map-entry>
</template-ids>
<panel-id>myNewPanel1</panel-id>
<content-url>/panels/order/mypanel1.jsp</content-url>
<other-context>MyWebApplication</other-context>
<title-key>myNewPanel1</title-key>
<visible-yn>true</visible-yn>
<show-title-yn>true</show-title-yn>
<panel-open-yn>true</panel-open-yn>
<allow-panel-toggle-yn>false</allow-panel-toggle-yn>
<available-yn>false</available-yn>
<content-open-yn>true</content-open-yn>
<allow-content-toggle-yn>true</allow-content-toggle-yn>
<tab-holder-yn>true</tab-holder-yn>
<always-tabbed-yn>false</always-tabbed-yn>
<tabbed-yn>false</tabbed-yn>
<allow-tabbing-yn>true</allow-tabbing-yn>
<allow-slots-yn>false</allow-slots-yn>
<tab-scroll-index>0</tab-scroll-index>
<panel-item-count>0</panel-item-count>
<access-right>NewPanel2</access-right>
</panel-definition>Repeat Step 3 for
myNewPanel2andmyNewPanel3.The new panels can be added to any existing panel stack by updating the
panelIdsproperty. Similarly, the panels may be added to a new panel stack.Note: The JSPs for the new panels should be housed in your custom application, so the
otherContextproperty of thePanelDefinitionshould be set to the value of the context root of the containing Web application.
