Some settings inherited by a task, workflow, or activity may not be appropriate for it. You can use the combine attribute (set to remove) in order to eliminate settings from a given context. You can remove the following items:
Specific buttons, using the
<operation>tag.Specific tabs, using the
<tab>tag. If you remove a tab using this tag, be sure to remove it from the<tab-order>tag as well.Specific tabs from the ordering list, using the
<tab-id>tag.Specific views on a tab, using the
<view>tag. If you remove a view using this tag, be sure to remove it from the<view-order>tag as well.Specific views from a tab’s ordering list, using the
<view-id>tag.Set of view mapping settings including the mode, name, and affected item types with a different set, using the
<view-mapping>tag.
You might find that, for example, the Review task doesn’t require users to edit items, so no buttons should be visible for this task. You might also remove the Content Groups and Targeters views if a reviewer only looks over User Segments. The following code removes the unnecessary resources:
<task> <task-name> review </task-name> <tabs> <tab id="browse"> <views> <view-order> <view-id combine="remove">personalization.segmentsAndTargeters. contentGroups</view-id> <view-id combine="remove">personalization.segmentsAndTargeters. targeters</view-id> </view-order> </views> </tab> </tabs> <operations> <operation combine="remove">create</operation> <operation combine="remove">duplicate</operation> <operation combine="remove">delete</operation> <operation combine="remove">move</operation> <operation combine="remove">link</operation> <operation combine="remove">unlink</operation> </operations> </task>
In this example, the two views are removed from the drop-down list used to select a view, so they aren’t available to the Browse tab. If you decided to remove the view identified to display initially (personalization.segmentsAndTargeters.userSegments), you’d need to specify a different initial view.
On the bottom of the page, the <operations> tag removes several buttons. Notice the placement of the <operations> tags. When <operations> tags exist directly beneath a <task> tag as they do here, they apply to all displays used by the task. It’s possible to nest an <operations> tag in <view> and <tab> tags so that they apply only to a given view or tab.
