Timeline Overview Public

Timeline

Standalone ERPat Timeline module. Controller, model (Posts_model, table 'posts'), views, routes and menu are owned by this package and loaded through the HMVC compatibility layer. Slug 'timeline' matches the legacy module_timeline active-setting.

Guide version: r1 Module version: 1.0.0 Updated: 2026-07-22 Estimated time: 2 min 2 views
Overview

Timeline

Standalone ERPat Timeline module. Controller, model (Posts_model, table 'posts'), views, routes and menu are owned by this package and loaded through the HMVC compatibility layer. Slug 'timeline' matches the legacy module_timeline active-setting.

Slug: timelineVersion: 1.0.0Category: GeneralReviewed: 2026-07-11

What This Module Is For

Standalone ERPat Timeline module. Controller, model (Posts_model, table 'posts'), views, routes and menu are owned by this package and loaded through the HMVC compatibility layer. Slug 'timeline' matches the legacy module_timeline active-setting.

Use this guide as the operator manual for the module. It combines end-user steps with implementation evidence from the current module package so admins, support staff, and QA can agree on what the module actually ships.

Module at a Glance

1Controllers
9Screens
1Models
1Tables

Where users usually start

  • Timeline

Primary user groups

  • Module administrators
  • Staff users assigned to the workflow
  • Managers who review records and reports

Documentation Map

Getting Started

Use this first when enabling the module, assigning access, and preparing starter data.

Daily Operations

Use this for routine work, record handling, review cycles, reporting, and handoff steps.

Administration and Controls

Use this for permissions, settings, automations, public pages, widgets, and APIs.

Data and Screen Reference

Use this to identify module screens, data records, routes, and supporting files.

Module Research Notes

Use this to see what module files were inspected and what capability evidence was found.

FAQ and Troubleshooting

Use this when the menu, data, permissions, jobs, public pages, or reports do not behave as expected.

Operator Outcomes

  • Understand what the module owns and where it appears in the ERPat workspace.
  • Know the first setup tasks required before staff use live data.
  • Operate the main list, form, detail, report, and review screens consistently.
  • Identify which permissions, settings, public pages, APIs, jobs, or widgets need administrator review.
  • Recognize the core records managed by the module, including posts.
Was this guide helpful?

Report a content problem