Standard widgets
Predefined widgets that can be placed into supported layouts and configured for visibility, title, border, content, and page behavior where applicable.
Standard and Custom Widgets
Reusable page components for configurable dashboards, forms, reports, and operational actions.
Explore the capabilityOverview
Widgets are the building blocks used by Design Studio layouts to present information, capture input, trigger actions, and extend the product experience.
Protrak supports standard widgets, type widgets, report widgets, and custom widgets so customers can combine out-of-the-box capabilities with tenant-specific or process-specific extensions.
This capability gives product and implementation teams a structured way to configure what users see, where they see it, and how they interact with operational data.
Design Studio capability
Widget Types
Type widgets
Configured widgets tied to instance types, dashboards, reports, relations, calendar, tree, geolocation, sprint planner, DF analytics, and other supported views.
Report widgets
Report-oriented widgets that can render tabular, bar chart, pie chart, pivot, and other configured report views.
Custom widgets
Schema-defined widgets that allow custom UI, logic, renderers, editors, or actions using supported product APIs and components.
Field widgets
Attribute containers that group selected fields and control how values are shown or edited on forms.
What teams can configure
Core Capabilities
A configurable Design Studio capability that helps teams shape operational applications without rebuilding screens for every process variation.
- Add reusable standard widgets such as task, messages, recently updated, rich text, text/title widgets, dynamic forms, QR code, and other supported components.
- Select configured type widgets directly from layout settings and navigate to their detailed configuration when needed.
- Use report widgets to surface analytics, tabular information, charts, or pivot-style summaries inside layouts.
- Define custom widgets in schema configuration and expose them in selected layout targets such as home page, dashboard, form, renderer, editor, or custom action.
- Apply display conditions and role-based visibility so widgets appear only when the user, role, or record context is relevant.
- Use custom renderers and editors to display attribute values in specialized ways, including masked or tailored presentation.
- Configure custom actions for process-specific operations such as bulk actions, printing labels/stickers, or tenant-specific integrations.
Operational application
Use Cases
- Use a task or message widget on a home page so users see pending work and communication without opening multiple screens.
- Use report widgets to show pie charts, bar charts, or tabular lists for leadership, operations, and quality review.
- Use custom widgets to embed a specialized customer workflow, visual component, or integration action inside a configured page.
- Use field widgets to group related attributes such as status, ownership, quality information, or tracking details.
- Add a rich text widget to provide operational notes, process guidance, or customer-specific instructions on a dashboard.
- Configure display conditions so a widget appears only when a record reaches a specific lifecycle state.
- Use a custom renderer to show an attribute value in a more meaningful visual format instead of plain text.
- Configure a custom action for a process step that requires external communication, special validation, or batch execution.
Centralized and reusable
Configuration and Extension Model
Standard widgets are used as configured product components. Custom widgets extend the product experience when an implementation needs specialized behavior that is not covered by standard configuration. Custom widgets can reuse exposed APIs, containers, spinners, and product-side components to maintain consistency with the platform.
Use an existing operational component
Place a standard widget and configure visibility, display, or content settings.
Show a configured dashboard or report
Use a type widget or report widget linked to the required type/widget configuration.
Render a value differently
Use a custom renderer or editor for the attribute or form context.
Trigger a special operation
Use a custom action where process-specific logic is needed.
Build a specialized experience
Create a schema-based custom widget with the required target layout and logic.
In practice
Use Scenarios
- Role-specific dashboards that combine operational lists, reports, tasks, and rich-text guidance.
- Executive or supervisor views that show report widgets with charts and selected KPIs.
- Field or production screens where users need quick access to related records, QR code printing, attachments, or actions.
- Custom page experiences where tenant-specific logic, APIs, or process actions must be embedded into the product UI.
- Attribute-level customization where values need special rendering, masking, or editing behavior.
Design Studio
Reusable product capability with extensibility
Standard and Custom Widgets show how Protrak balances reusable product capability with extensibility. Customers can move quickly with predefined widgets while still supporting differentiated process needs through custom widgets and actions.
Pages are assembled from governed components, making solutions faster to configure, easier to evolve, and more consistent across use cases.