Platform & Solutions by Prorigo

Protrak Logo

Layout Configurations

Configure web, tablet, and mobile-facing page layouts for operational users.

Explore the capability

Overview

Layout Configurations in Protrak Design Studio allow administrators and implementation teams to decide how information, forms, widgets, and actions are presented across user journeys.

The capability covers home pages, dashboards, create/edit/view pages, and report layouts, while honoring device-specific presentation needs for desktop, tablet, and mobile usage.

The capability is designed for configurable enterprise applications where different roles, teams, or process stages need different screens, without requiring a separate custom screen build for every tenant or use case.

Design Studio capability

Capability Scope

Home layout

Grid-based placement of widgets with drag-and-drop arrangement, resize handles, full-width options, tab or dropdown template display, and role-wise template selection.

Dashboard layout

Vertical ordering of dashboard, report, and custom widgets with page settings such as create button visibility, view modes, and configurable auto-refresh.

Create/Edit/View layout

Form-centric layouts with configurable details area, tabs for related widgets in view mode, page actions, auto-save visibility, and support for standard or custom widgets where applicable.

Report layout

Report widgets rendered through configured views such as tabular reports, charts, pivot views, and other supported report presentations.

Device layouts

Separate desktop, tablet, and mobile configuration behavior, with mobile app experiences optimized for vertical display.

What teams can configure

Core Capabilities

A configurable Design Studio capability that helps teams shape operational applications without rebuilding screens for every process variation.

  • Drag and arrange widgets on home layouts, including odd-numbered widget combinations and resized containers.
  • Configure page templates per layout type and control whether templates are shown as tabs or dropdowns.
  • Apply role-based and condition-based visibility to templates, widgets, and content blocks.
  • Use device-wise configuration to shape desktop, tablet, and mobile presentations from the same design model.
  • Configure details of forms, field containers, renderers, editors, and attribute visibility inside create, edit, view, and quick-edit modes.
  • Control page actions such as editing, creating, copying, exporting, printing QR code, annotating file, and auto-save visibility based on the page context.
  • Enable auto-refresh for monitoring dashboards that need periodic updates while the page remains open.

Operational application

Use Cases

  • Create a role-specific home page where supervisors see monitoring widgets, while field users see assigned work and quick-entry actions.
  • Configure a dashboard view for live operational tracking where the screen remains open and refreshes at selected intervals.
  • Design create/edit/view pages differently for office users and field users while keeping the same underlying business object.
  • Present report layouts as charts, grids, or pivots depending on whether the audience needs analysis, review, or execution support.
  • Optimize the same process for desktop planning and mobile execution by using device-specific layout behavior.
  • A production manager can monitor active jobs on a dashboard without manually refreshing the screen.
  • A quality team can see different form sections or actions based on inspection stage and user role.
  • A mobile user can complete a compact vertical form without navigating through unnecessary desktop-style sections.
  • A tenant administrator can adjust page composition when process ownership changes, without requesting a new custom screen.

Centralized and reusable

Configuration Model

Layout configuration works through page templates, forms, widgets, and page settings. A template defines the structure of a page for a role, use case, or type. Within that template, administrators place configured widgets, forms, attributes, and actions. The runtime then renders the relevant layout according to the selected page, device, role, and display conditions.

Which template is shown

Role-wise and context-wise page experience for different users.

Which widgets are placed

Operational content, reports, forms, related data, actions, or custom logic visible on the page.

How fields render

Attribute grouping, renderer/editor selection, masked display, and conditional display rules.

How often data refreshes

Dashboard refresh interval for monitoring-oriented screens.

How mobile behaves

Vertical-first presentation for mobile app usage, with responsive behavior for web/PWA access.

In practice

Use Scenarios

  • Role-specific home pages for operational users, supervisors, and administrators.
  • Monitoring dashboards that stay open and refresh at a configured interval.
  • Create and edit screens that expose only the fields and actions needed for a specific process stage.
  • View pages that combine form details with related records, reports, attachments, geolocation views, or custom actions.
  • Mobile-friendly forms where the same configured capability is presented in a compact vertical flow.

Design Studio

A configurable digital execution platform, not a fixed application

Layout Configurations help position Protrak as a configurable digital execution platform, not a fixed application. Customers can adapt screens to their operational model, user roles, and device needs while retaining governance through Design Studio.

Business teams can evolve page experiences as requirements change, while implementation teams keep the configuration centralized and reusable.