Defining Container Restrictions

Optionally, you can limit the content types that can be dropped on a container for layouts used in Web Page Composer (WPC). To do this, define restrictions for this container using the allowedDropTags attribute in the portalapp.xml file. This attribute contains a multivalue comma-separated list of the content types that can be dropped on this container. When a content item, such as an iView or page, is dropped on a container, the page builder compares the allowedDropTags attribute of the container with the com.sap.portal.ContentTemplate attribute of the item.

To define restrictions, add this attribute to the XML_Template property used by Ajax Page Builder, for example:

Example Example

<Container containerID="com.sap.portal.reserved.layout.Cont3">
	<TableCellData width="50%" height="100%" colSpan="1" vAlign="top"/>
	<ContainerBehaviors allowedDropTags="iview,wpc_weblinklist"/>
	</Container>
</ContainersRow>

End of the code.

For more information, see Adjusting Custom Layouts to Ajax Page Builder.

To support Accessible Area Management in WPC, which is running in Portal Runtime (PRT) Page Builder, define container restrictions in portalapp.xml, for example:

Example Example

<property name="com.sap.portal.reserved.layout.Cont1" value="left">
	<property name="title" value="Left Column"/>
	<property name="orientation" value="vertical"/>
	<property name="allowedDropTags” value=”iview,wpc_weblinklist”/
</property>

End of the code.

Note Note

These restrictions are applied only in an editing environment.

End of the note.