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-30 Estimated time: 2 min 1 views
You are viewing version r1 of this guide. View the current version
End-user documentation

Timeline

A social timeline for posts, replies, attachments, widgets, reactions, profile wall activity, and internal announcements.

Where users startTimeline
Primary goalHelp a beginner understand what the module does and how to operate it safely.
Last reviewed2026-07-10

Purpose and What Problem This Solves

The Timeline module gives staff a shared internal activity feed. It helps teams post updates, celebrate work, ask quick questions, and keep lightweight social communication inside ERPat.

Plain-language rule: If a user can explain what record they are creating, why it exists, who owns it, and what happens next, they are ready to use the module responsibly.

Who normally uses this module

Staff users Managers HR or culture teams Team leads Internal communication owners

What You Can Do Here

  • Post internal announcements, quick updates, reminders, or team wins.
  • Reply to posts and keep discussion near the original update.
  • Attach files or images when supported by the post form.
  • Show timeline activity through widgets or profile-related surfaces.
  • Use reactions as lightweight acknowledgement or sentiment.

Core Concepts and Terms

Learn these words first. Most user mistakes happen when a beginner opens a form without knowing what the record represents.

Post

A top-level timeline update.

Reply

A comment or response under a post.

Reaction

A lightweight response such as like or similar configured action.

Attachment

A file or image linked to a post.

Profile wall

A user-related timeline view when enabled.

Beginner Quick Start

Use this first-run path in a training database or with a supervised account before handling live records.

  1. Open Timeline and read existing posts to understand team tone.
  2. Create a short post with a clear first sentence.
  3. Add attachments only when they help the reader.
  4. Reply under the existing post when continuing a topic instead of creating duplicates.
  5. Use formal modules for work that needs assignment, approval, SLA, or audit.
Before using live data: confirm the module is enabled, your role has the right permissions, required master data exists, and you know the rollback or correction process for mistakes.

Standard Operating Procedures

These SOPs describe the routine operating pattern. Your company policy may add approvals, attachments, or segregation-of-duties controls.

Actor: Team lead or communications owner

Post an internal announcement

  1. Write the key message first: who is affected, what changes, and when.
  2. Add supporting details, links, or attachments.
  3. Post at the right time for the intended audience.
  4. Monitor replies and answer clarifying questions.
Actor: Staff user

Use timeline for team discussion

  1. Search or scan for an existing related post.
  2. Reply to the existing post when the topic is the same.
  3. Keep comments professional and relevant to the workplace.
  4. Move action items to Todo, Projects, or Helpdesk when follow-up is needed.
Actor: Manager or administrator

Clean up inappropriate content

  1. Review the post, replies, attachments, and context.
  2. Remove or hide unsafe content according to policy.
  3. Contact the author privately when correction or coaching is needed.
  4. Escalate privacy, harassment, or compliance issues through HR or management.

Industry Notes and Good Practice

  • Timeline is informal communication, not a replacement for controlled workflows.
  • Use plain language and short posts. People scan feeds quickly.
  • Avoid confidential payroll, medical, legal, or customer-sensitive details in a social feed.
  • Convert decisions or tasks into the correct module so they can be tracked.

Controls, Data Quality, and Review Checklist

Use this checklist during onboarding, monthly review, and process audits.

  • Announcements state audience, date, action needed, and owner.
  • Action items are moved into trackable modules.
  • Attachments are relevant and safe to share with the audience.
  • Posts follow workplace communication policy.

Related ERPat areas

Todo for actions Projects for work tracking Helpdesk for support Community for public/member discussions

FAQ and Troubleshooting

Should I post a support issue here?

Use Helpdesk for support that needs tracking, SLA, privacy, or assignment.

Can timeline posts be used as approvals?

No. Use the relevant approval workflow for controlled decisions.

Why can I not see the timeline?

The module may be disabled or your role may not have access.

What makes a useful post?

A clear first line, relevant context, named owner, and next action if one exists.

Report a content problem