// layoutProfileMapping indentifies what layout to link to what profile
<layoutProfileMapping profile='default_oob_profile'
layout='standardLayout'/>
<layoutProfileMapping profile='vendor_oob_profile'
layout='standardVendorLayout'/>
<layoutProfileMapping profile='sourcingManager'
layout='sourcingLayout'/>

// layoutDefinition is the name of the layout you are defining,
// this is linked by layoutProfileMapping
<layoutDefinition name='standardVendorLayout'>
//Each layoutDefinition id made up of columns, 1 or more
// you can set the width of the column as well to help with display
<column width='500'>
//each column is made up of components
//A component is a literal page/report to display within the column
<component>
//ID is the actual activity name to use, so ex: in activitycontroller properties NOTICES links to the controller
<id>NOTICES</id>
// params is any param you want to pass to the report.
// This is useful for different layouts,
// where the same report can be used but you can trigger different
// views in the report based on the param passed and each layout
// can pass a different param.
<params>
// in this ex templateType is the actual param being passed on the request
// to the page/report
<templateType>COMPONENT</templateType>
</params>
</component>
<component>
<id>ORDER_CONFIRMATION_SUMMARY</id>
<params>
<templateType>COMPONENT</templateType>
</params>
</component>
<component>
<id>PRODUCT_SAMPLE_SUMMARY</id>
<params>
<templateType>COMPONENT</templateType>
</params>
</component>
</column>
<column width='500'>
<component>
<id>SEASON_SUMMARY</id>
<params>
</params>
</component>
<component>
<id>RFQ_SUMMARY</id>
<params>
</params>
</component>
<component>
<id>MATERIAL_SAMPLE_SUMMARY</id>
<params>
<templateType>COMPONENT</templateType>
</params>
</component>
</column>
<layoutDefinition>