This section describes how custom summary pages are created.
What does this section cover?
Create Custom Summary Pages
For an introduction to summary pages, go to Summary Pages.
To create a new custom summary page, you need to create a single XML file under <custom_project>/web/WebContent/pages/summary/<module_name>.
If the new summary page will be used to override system's release functionality, must follow this naming convention: <page_filename>Custom.xml. If not, it just has to have a unique file path.
In the following example, a new summary filter and field needs to be added to the existing contact information summary page. To do this, you have to copy release summary page contactInformation.xml in your custom projects directory under <custom_project>/web/WebContent/pages/summary/contactInfo, rename it to contactInformationCustom.xml and add the new summary filter and field.
Templates Properties File
The templates properties file (templates.properties) is used for defining the default summary page, generally or per community, when one or more custom summary pages exist per release summary page. Templates properties file must be created under <custom_project>/web/WebContent/pages/summary.
To define the default summary page, you have to add the following line to templates.properties file: <release_summary_page_file_path>~organisation~default=<directory_name>/<custom_summary_page_filename>
To define the default summary page for a specific community, you have to add the following line to templates.properties file: <release_summary_page_file_path>~community~<community_id>=<directory_name>/<custom_summary_page_filename>
Note that .xml is omitted from definition_page_file_path.
If no default layout page is specified for a specific community, the default layout page will be used by the system. If no default layout page is specified either, the release layout page will be used.
For a full list of summary page attributes, go to Summary Pages Documentation.