Problem: Currently, OutSystems Community forum users have to do a full browser page refresh to see new questions or answers. This leads to missed conversations, outdated thread views while writing replies, and duplicate answers being posted.

Proposed Improvements:

1. Auto-refresh post list The forum list should silently update in the background every 30–60 seconds. New posts should appear with a subtle highlight — no full page reload needed.

2. "Refresh List" button (partial refresh only) A dedicated refresh button that reloads only the posts list — not the entire page. Users keep their scroll position, active filters, and tabs intact.

3. Conflict warning before submitting an answer When a user is typing a reply and someone else posts an answer in the meantime, show a warning before submission: "New answers were added while you were writing. View them before submitting?" — preventing duplicate or redundant answers.

4. "New replies" toast inside open thread When reading a thread, if new replies arrive, show a non-intrusive toast: "3 new replies — click to load." User stays in reading context without losing scroll position.

5. "New questions" badge on forum nav Show a live badge count on the Forums section when new posts arrive, so users notice activity even while browsing other sections.

6. Live accepted answer update If an answer gets accepted while a user is viewing the thread, the "Accepted" badge should appear live — without requiring a reload.

Visual Reference (AI-generated mockups): To better illustrate the proposed changes, I have attached two AI-generated reference mockups below:

• Image 1 shows the forum list view with the new "Refresh" button and "2 new" badge visible in the toolbar alongside existing Sort and Translate controls.
• Image 2 shows an open thread view with the "New answers added while reading" toast bar, the conflict warning before reply submission, and how the overall thread experience would feel with live updates.

These are for visual reference only and not final designs — the actual implementation details are at the team's discretion.

Expected Impact: Fewer duplicate answers, faster community response times, and a significantly better forum experience overall.