Gold Best Practice RibbonBuilding Custom Page Layouts Best Practices

Keep the following set of best practice recommendations in mind when building custom page layouts for your projects:

  • Existing Accolade Project Page Layouts - The system includes active layouts that can serve as project pages, and contain pods that allow users to view and edit project and gate information as necessary.
  • The Project Home layout, that is automatically associated with process models on model creation and serves as a project's home and details page.
  • The Project Gates layout, that is automatically associated with process models on model creation and serves as a project's gates pages.
  • The Project Time View layout, which can be manually associated with a process model on model creation, and provides a high level view of the work to be completed on a project.

If you wish to customize these layouts to fit your company's purposes, Sopheon recommends creating copies of these layouts to customize them instead of modifying the system layouts directly, to ensure you do not lose the original layout pods and format. You will not be able to return to the original system layouts without contacting a system Administrator who can run a script to re-add the layouts.

  • Personalized Home Page Configuration - Accolade also includes layouts designed for use as customized home pages. While users can set their preferences for the information displayed in their individual view without having to configure the layout, Administrators and Process Designers with the Template Access role can make changes to home page layouts on a global level through the layout and pod configuration, for example, to add company landing page hyperlinks to the Quick Links pod for all users, or to add additional information at a company level. See Available Pod Types for more information.

Important! Do not delete these layouts. You will not be able to undo this action, and will have to contact a system Administrator who can run a script to re-add the layouts.

  • Know the Effects of Replacing Standard Project Pages - If you replace a standard project page with a custom project page, some functionality for users on projects may be lost. The information for the standard Home and Details pages are available in pods included in the system Project Home layout. Additionally, all functionality for the standard Gates page is included in the system Project Gates layout. However, functionality on other standard project pages may not be available to display in pods on page layouts.
  • Consider Information Type and User Needs - When building custom project pages, particularly for project pages that users access frequently for information such as the home and gates pages, understand what users on projects need visibility into and how this maps to available pod types. For example, allow team members to view and update project statuses by including the Project Status pod in the layout.