The assetManager.defaultBrowse activity maintains general settings that other activities inherit. This activity provides view-only access to items.
Defining General Activity Settings
<activity id="assetManager.defaultBrowse"> <page> /assetManager.jsp </page> <asset-editor> <page> /assetEditor/editAsset.jsp </page> </asset-editor> <configuration> /atg/web/assetmanager/ConfigurationInfo </configuration>
The first set of tags identify the page that provides the structure to the Asset Manager UI Framework, assetManager.jsp. Among other settings, assetManager.jsp defines a two-panel structure for the UI. The structure for the Details pane is determined by editAsset.jsp. The ConfigurationInfo component specifies the Task Configuration Manager as well as other resources used by the Asset Manager framework to generate the UI. Note that both AssetUI and DPS-UI files use the same Task Configuration Manager, which means an inheritance dependency exists between them. Any other uses of a <configuration> tag in these files provide view-specific settings.
Defining View Mappings
The view mapping settings specify item mappings that control the display of properties in the Details pane. They also let you override the view mapping mode. Specify one <view-mapping> tag for each <item mapping> tag. These tags identify the UI resource (item mapping name) and type of access (view mapping mode) provided to properties of the specified item types.
Keep in mind that sometimes you may want to provide view-only access to some items and edit access to others. For example, you might want an activity to provide read-only access to items that are otherwise editable. To accommodate this requirement, the JSP uses the task configuration file to assign the map mode based on the item type, giving you the option to pass a different map mode to the JSP.
The following view mappings are specified in assetManager.defaultBrowse:
<view-mappings> <view-mapping mode="AssetManager.edit"> <item-mapping> <item-type>*</item-type> <item-mapping-name>AssetManager</item-mapping-name> <view-mapping-mode-override>AssetManager.view</view-mapping-mode-override> </item-mapping> </view-mapping> <view-mapping mode="AssetManager.multiEdit"> <item-mapping> <item-type>*</item-type> <item-mapping-name>AssetManager</item-mapping-name> <view-mapping-mode-override>AssetManager.view</view-mapping-mode-override> </item-mapping> </view-mapping> <view-mapping mode="AssetManager.view"> <item-mapping> <item-type>*</item-type> <item-mapping-name>AssetManager</item-mapping-name> </item-mapping> </view-mapping> <view-mapping mode="AssetManager.diff"> <item-mapping> <item-type>*</item-type> <item-mapping-name>AssetManager</item-mapping-name> </item-mapping> </view-mapping> <view-mapping mode="AssetManager.conflict"> <item-mapping> <item-type>*</item-type> <item-mapping-name>AssetManager</item-mapping-name> </item-mapping> </view-mapping> </view-mappings> </activity>
When AssetManager.edit or AssetManager.multiedit is passed from the JSP, the task configuration specifies the item mapping as Asset Manager and changes the mode from edit to view, which prevents buttons like Save from appearing in the UI. Thus the UI is in view-only mode regardless of the map mode initially received by the task configuration file.
Note the use of * as a wildcard value to indicate all items.
