The personalization.editSegmentsAndTargeters task is a generalized resource that doesn’t map to a particular task or workflow in the Business Control Center. However, this task provides settings that are inherited by the configuration for the editSegmentsAndTargeters workflow.
The task definition starts as follows:
<task id="personalization.editSegmentsAndTargeters" inherit- from="personalization.browseSegmentsAndTargeters">
This tag specifies that the resource being configured is a task called personalization.editSegmentsAndTargeters. Because this task inherits settings from the personalization.browseSegmetnsAndTargeters activity that determine how UI displays user segments, content groups, and targeters in view-only mode, the task tag encloses only those setting required to overwrite previous settings or to supplement them with tools for editing those items.
The general settings are as follows:
<asset-editor> <page> /assetEditor/editAsset.jsp </page> <configuration> /atg/web/assetmanager/configuration/targeting/TargetingEditorConfiguration </configuration> </asset-editor>
The Navigation pane obtains its structure from editAsset.jsp. The configuration resources are specified in the TargetingEditorConfiguration component.
The necessary buttons are added to the tab defined in this task (Project) as well as the tab inherited from other resources (Browse), unless overwritten elsewhere in this file:
<operations> <operation>create</operation> <operation>move</operation> <operation>duplicate</operation> <operation>delete</operation> <operation>addToProject</operation> </operations>
These buttons are the same as those added to the personalization.user activity, but since this task doesn’t inherit settings from that activity, the buttons need to be specified here. Remember that these are a subset of the buttons available to the UI. For a complete list, see the ATG Merchandising UI Basics section of the Using the ATG Merchandising User Interface chapter in the ATG Merchandising Guide for Business Users.
The Browse tab settings are inherited by this task from the personalization.browseSegmentsAndTargeters activity. The Project tab is added as follows:
<tabs> <tab-order> <tab-id>project</tab-id> </tab-order>
When a resource is evaluated, inherited tags are ordered before directly specified ones. Hence, the Browse tab configuration is inherited by this resource, so in the Show drop-down list, the order is Browse tab, then Project tab. The initial tab is the Browse tab, which is another setting inherited by the task. This file could have provided a different tab order or initial tab by overwriting the inherited settings.
The Project tab is defined as follows:
<tab id="project"> <display-name-resource> assetManager.tab.project </display-name-resource> <page> /project/projectTab.jsp </page> <operations> <operation combine="remove">addToProject</operation> <operation>removeFromProject</operation> </operations> </tab> </tabs>
The Project tab, named as such by the assetManager.tab.project key in the resource bundle provided in the <default-activity> tags, relies on projectTab.jsp for its Navigation pane structure. The buttons defined in the beginning of this task are visible in the Project tab, although two changes are made to that list. There’s no reason to have an Add to Project button on the Project tab because all items visible in the tab have already been added to it, so that button is hidden from view. A Remove from Project button is provided in its place, permitting users to undo changes made to items in the current project.
The view mapping settings are modified as follows:
<view-mappings> <view-mapping mode="AssetManager.edit" combine="replace"> <item-mapping> <item-type>*</item-type> <item-mapping-name>AssetManager</item-mapping-name> </item-mapping> </view-mapping> </view-mappings> </task>
From the personalization.browseSegmentsAndTargeters activity, the current task inherits view-only access to all parts of the UI, meaning that regardless what map mode is specified by the JSP, AssetManager.view is returned to it. For AssetManager.edit map mode, this setting overrides the previous one. When a page requests this mode, it is used verbatim.
