EventR Wiki - User contributions [en]

Alerts

2026-07-01T13:29:49Z

Samh: Created page with "== What are Alerts? == '''Alerts''' is your personal notification center within the EventR app. It provides a simple, easy-to-read list of any changes made to your event itinerary since you last checked — whether that's a newly booked flight, an updated hotel reservation, or a fresh activity added to your schedule. Think of Alerts as your "what's new" dashboard, keeping you informed without having to hunt for updates across multiple screens. == How to Access Alerts..."

== What are Alerts? ==

'''Alerts''' is your personal notification center within the EventR app. It provides a simple, easy-to-read list of any changes made to your event itinerary since you last checked — whether that's a newly booked flight, an updated hotel reservation, or a fresh activity added to your schedule.

Think of Alerts as your "what's new" dashboard, keeping you informed without having to hunt for updates across multiple screens.

== How to Access Alerts ==

# Open the EventR app
# Navigate to your event itinerary
# Tap the '''Alerts''' icon in the navigation menu

The Alerts page will display all recent updates, grouped by date.

== Understanding Your Alerts ==

When you open the Alerts page, you'll see:

* '''Date headings''' — Alerts are organized under date labels like "'''Today'''", "'''Yesterday'''", or specific dates, making it easy to see when changes happened.
* '''Individual alert cards''' — Each card shows a brief description of the change and the name of the affected item.
* '''Empty state''' — If there are no new updates, you'll see a friendly message letting you know there's nothing new.

== Types of Alerts ==

Alerts cover all the key items in your event itinerary:

{| class="wikitable"
|+ Supported Alert Types
! Alert Type !! What You'll See
|-
| '''Flight''' || New flight bookings or changes to existing flights, including your booking reference and departure/arrival airports
|-
| '''Hotel''' || New hotel reservations or updates to existing bookings, showing the hotel name
|-
| '''Car Hire''' || New car hire bookings or changes, showing the vehicle type and provider
|-
| '''Transport''' || New transport arrangements or updates, showing the transport details
|-
| '''Parking''' || New parking bookings or changes, showing the parking location
|-
| '''Activity / Stand''' || New activities or stands added to your itinerary, or updates to existing ones
|-
| '''To-Do''' || New to-do items or updates to existing tasks
|}

Each alert clearly indicates whether the item is '''newly added''' or an '''existing item that has been updated'''.

== Interacting with Alerts ==

=== View Details ===

'''Tap''' any alert card to navigate directly to the full details page for that itinerary item. This is the quickest way to review what changed.

=== Clear All Alerts ===

When you've caught up on all your updates, tap the '''Clear All''' button (represented by a read/all icon in the top-right corner of the Alerts page) to mark every alert as read. The list will then appear empty until new changes are made.

=== Refresh Alerts ===

Simply '''pull down''' on the Alerts page to refresh and ensure you're seeing the very latest updates.

== Tips ==

* '''Check Alerts regularly''' — Especially on the days leading up to your event, when changes are most common.
* '''Use Clear All''' — Once you've reviewed everything, clear your alerts so the list stays clean and focused on new updates.
* '''Alerts are smart''' — You'll only see changes that have happened since your last visit, so you won't be shown the same update twice.
* '''Tap to navigate''' — Every alert is a shortcut. Tap it to jump straight to the full details of that item.

== Frequently Asked Questions ==

'''Q: Why are some alerts showing as "updated" instead of "new"?'''
:A: An alert is marked as "updated" when an existing item in your itinerary has been modified — for example, if a flight time changes or a hotel room is upgraded. "New" alerts appear when an item is added to your itinerary for the first time.

'''Q: Will I miss alerts if I don't check for a while?'''
:A: No! All alerts are saved until you view them. When you open the Alerts page, you'll see every change that's happened since your last visit.

'''Q: Can I filter or sort the alerts?'''
:A: Alerts are automatically sorted by date, with the most recent updates appearing at the top. This ensures you always see the latest changes first.

'''Q: Who can make changes that trigger alerts?'''
:A: Any authorized user — including event organizers, administrators, or yourself — can make changes to the itinerary. When a change is made, it will appear in your Alerts feed.

[[Category:Features]]
[[Category:User Guide]]

Todos

2026-06-17T14:00:32Z

Samh: Samh moved page Todos to Custom Todos

#REDIRECT [[Custom Todos]]

Custom Todos

2026-06-17T14:00:32Z

Samh: Samh moved page Todos to Custom Todos

{{Infobox Feature
| name = Custom Todos
| version = [[Release 3.5.0|3.5.0]]
| tier = Standard, Premium and Enterprise
}}

[[File:Screenshot 2026-06-17 at 14.57.14.png|thumb|Example: Input - ECH custom Todo]]
[[File:App-custom-todo.png|thumb|Example: Output - App custom Todo]]

= Custom Todos =

Todo task labels support special prefixes and variables that control how tasks are rendered in the UI.

== Prefixes ==

Prefixes are detected by examining the '''first character''' of the label after trimming leading whitespace.

=== ''.'' (Dot) – Inline/Child Tasks ===

Prefix a task label with <code>.</code> to make it an '''inline child''' of the preceding non-dot task. Child tasks are displayed in a grid row alongside their parent, creating a compact horizontal layout.

'''Behaviour:'''

* The <code>.</code> prefix is stripped from the displayed label
* The task is grouped with the previous non-dot task as a child
* Displayed in a shared grid row (parent + children side by side)
* Checkbox is still shown (can be checked/unchecked)
* If a dot-prefixed task appears without a preceding parent, it is treated as a regular individual task

'''Example:'''

<syntaxhighlight>
Monday Breakfast
.Lunch
.Dinner
</syntaxhighlight>

=== <code>|</code> (Pipe) – Label-Only (No Checkbox) ===

Prefix a task label with <code>|</code> to render it as '''plain text without a checkbox'''. Useful for section headers, notes, or informational text within a todo list.

'''Behaviour:'''

* The <code>|</code> prefix is stripped from the displayed label
* No checkbox is rendered
* The item does not count toward the completed/total counter

'''Example:'''

<syntaxhighlight>
|Important Notes
Attend all morning sessions
|Evening Activities
</syntaxhighlight>

== Date Variables ==

Task labels support the <code><nowiki>{{EventDate}}</nowiki></code> variable, which is replaced with the event's start date displayed as day and month numbers (e.g., ''16/06'').

=== Basic Usage ===

{| class="wikitable"
! Variable
! Replaced With
|-
| <code><nowiki>{{EventDate}}</nowiki></code>
| Event start date (e.g., ''16/06'')
|}

=== Offsets ===

You can add or subtract days from the event date using <code>+</code> or <code>-</code>:

{| class="wikitable"
! Variable
! Replaced With
|-
| <code><nowiki>{{EventDate+1}}</nowiki></code>
| Event start date + 1 day
|-
| <code><nowiki>{{EventDate-1}}</nowiki></code>
| Event start date − 1 day
|-
| <code><nowiki>{{EventDate+3}}</nowiki></code>
| Event start date + 3 days
|-
| <code><nowiki>{{EventDate-2}}</nowiki></code>
| Event start date − 2 days
|}

Whitespace inside the braces is tolerated:

* <code><nowiki>{{ EventDate + 1 }}</nowiki></code> → same as <code><nowiki>{{EventDate+1}}</nowiki></code>
* <code><nowiki>{{EventDate- 2}}</nowiki></code> → same as <code><nowiki>{{EventDate-2}}</nowiki></code>

Unknown variables (anything other than ''EventDate'') are left as-is.

'''Example:'''

<syntaxhighlight>
{{EventDate}} Check-in at hotel
{{EventDate+1}} Follow-up meeting
</syntaxhighlight>

== Combining Prefixes and Variables ==

Prefixes and date variables can be used together:

<syntaxhighlight>
|Schedule for {{EventDate}}
Morning briefing
. Afternoon workshop
. Evening networking
</syntaxhighlight>

2026-06-16T14:47:06Z

Samh: Blanked the page

Custom Todos

2026-06-16T14:46:31Z

Samh:

== Shortcuts ==

# TODO Task Label Prefixes & Variables

TODO task labels support special prefixes and variables that control how tasks are rendered in the UI.

## Prefixes

Prefixes are detected by examining the **first character** of the label after trimming leading whitespace.

### `.` (Dot) – Inline/Child Tasks

Prefix a task label with `.` to make it an **inline child** of the preceding non-dot task. Child tasks are displayed in a grid row alongside their parent, creating a compact horizontal layout.

**Behaviour:**
- The `.` prefix is stripped from the displayed label
- The task is grouped with the previous non-dot task as a child
- Displayed in a shared grid row (parent + children side by side)
- Checkbox is still shown (can be checked/unchecked)
- If a dot-prefixed task appears without a preceding parent, it is treated as a regular individual task

**Example:**
```
Monday Breakfast
.Lunch
.Dinner
```
Renders as a single row: `[☐ Monday Breakfast] [☐ Lunch] [☐ Dinner]`

### `|` (Pipe) – Label-Only (No Checkbox)

Prefix a task label with `|` to render it as **plain text without a checkbox**. Useful for section headers, notes, or informational text within a todo list.

**Behaviour:**
- The `|` prefix is stripped from the displayed label
- No checkbox is rendered
- The item does not count toward the completed/total counter

**Example:**
```
|Important Notes
Attend all morning sessions
|Evening Activities
```
Renders as:
```
Important Notes (plain text, no checkbox)
[☐ Attend all morning sessions]

Evening Activities (plain text, no checkbox)
```

## Date Variables

Task labels support the `{{EventDate}}` variable, which is replaced with the event's start date displayed as day and month numbers (e.g., `16/06`).

### Basic Usage

| Variable | Replaced With |
|---|---|
| `{{EventDate}}` | Event start date (e.g., `16/06`) |

### Offsets

You can add or subtract days from the event date using `+` or `-`:

| Variable | Replaced With |
|---|---|
| `{{EventDate+1}}` | Event start date + 1 day |
| `{{EventDate-1}}` | Event start date − 1 day |
| `{{EventDate+3}}` | Event start date + 3 days |
| `{{EventDate-2}}` | Event start date − 2 days |

Whitespace inside the braces is tolerated:

- `{{ EventDate + 1 }}` → same as `{{EventDate+1}}`
- `{{EventDate- 2}}` → same as `{{EventDate-2}}`

Unknown variables (anything other than `EventDate`) are left as-is.

**Example:**
```
{{EventDate}} Check-in at hotel
{{EventDate+1}} Follow-up meeting
```
Renders as: `16/06 Check-in at hotel`, `17/06 Follow-up meeting` (assuming event starts June 16)

## Combining Prefixes and Variables

Prefixes and date variables can be used together:

```
|Schedule for {{EventDate}}
Morning briefing
. Afternoon workshop
. Evening networking
```

---

Samh:

Rooming Lists

2026-05-06T10:44:32Z

Samh:

Rooming Lists

2026-05-06T10:42:53Z

Samh: /* Accessing Rooming Lists */

File:Screenshot 2026-05-06 at 11.38.33.png

2026-05-06T10:41:31Z

Samh:

screenshot

File:Screenshot 2026-05-06 at 11.21.54.png

2026-05-06T10:40:29Z

Samh:

screenshot