Custom Blueprint

This feature lets users dynamically render a page without sidebars and other navigation elements by passing a specific query parameter. By enabling this custom blueprint, users can focus solely on the page body without distractions from navigation elements. The feature is designed for URL-based navigation scenarios and supports dynamic control over the rendered UI blueprint.

Note:
  • This functionality applies only to the Kendo application UI and does not support Sapphire or Legacy UI platforms.
  • The custom blueprint currently does not support mobile devices.

Salient Features of Custom Blueprint

  • Hides the sidebar and application header dynamically via URL query parameters.

  • Displays only the page header and body while retaining the page context.

  • Seamless rendering with modern/traditional blueprints.

  • Custom blueprint rendering based on application settings or URL parameters.

The following changes can be observed when the custom blueprint is enabled via URL.

Component Changes
Component Changes

List View Page

Do not display

  • Actions: Convert, Clone, Send, Find Duplicates.

Record View Page

Do not display

  • Back to List Buttons.

  • Arrow Record Navigators.

  • Actions: Convert, Clone, Send, Find Duplicates.

Overflow menu (three dots)

Do not display

  • If no workflow actions or delete options are available.

Enabling the Custom Blueprint

The custom blueprint can be enabled by passing a query parameter in the URL from an iframe.

To enable the custom blueprint, pass the navDisabled=true query parameter in the URL.

  • If navDisabled=true, the custom blueprint is rendered

  • If navDisabled=false or the parameter is omitted, the default blueprint (as per application settings) is applied.

    For example:

    <iframe id="pageurl" width="100%" height="700" src="http://localhost:8080/prod1/m/main.jsp?pageId=31333&appId=31555&tabId=31540&id=31694&navDisabled=true" title="List View record view page">
    </iframe>

    Note: The navDisabled parameter is stored in a cookie, ensuring persistence across multiple requests. However, the cookie is cleared upon user logout.

  1. Pass the navDisabled=true query parameter in the URL using an iframe

  2. The custom blueprint is rendered when the user clicks on the New Record button, which opens the page in the same window.

The following changes can be observed when passing the navDisabled=true query parameter in the URL.

Component Changes

Sidebar Navigation

Not displayed

Application Header

Not displayed

Page Header

Displayed

Page Context

Remains unchanged, with all sections rendered consistently