<?xml version="1.0"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
	<id>https://eventrwiki.softpauer.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Samh</id>
	<title>EventR Wiki - User contributions [en]</title>
	<link rel="self" type="application/atom+xml" href="https://eventrwiki.softpauer.com/api.php?action=feedcontributions&amp;feedformat=atom&amp;user=Samh"/>
	<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php/Special:Contributions/Samh"/>
	<updated>2026-08-28T21:44:42Z</updated>
	<subtitle>User contributions</subtitle>
	<generator>MediaWiki 1.45.3</generator>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=Orders&amp;diff=1394</id>
		<title>Orders</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=Orders&amp;diff=1394"/>
		<updated>2026-08-04T10:20:12Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Infobox Feature&lt;br /&gt;
 | name = Orders&lt;br /&gt;
 | version = [[Release 3.4.1|3.4.1]] (BETA)&lt;br /&gt;
 | tier = Standard, Premium and Enterprise&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
= Overview =&lt;br /&gt;
The &#039;&#039;&#039;Orders&#039;&#039;&#039; feature allows users to create, manage, save, and generate request documents for both &#039;&#039;&#039;Accommodation&#039;&#039;&#039; and &#039;&#039;&#039;Flight&#039;&#039;&#039; bookings. It acts as a central workspace for collecting booking requirements, guest preferences, and order details related to an itinerary. Users can generate PDFs for sharing with suppliers, export order data to spreadsheets, and import existing booking data from exported files.&lt;br /&gt;
&lt;br /&gt;
= Accessing Orders =&lt;br /&gt;
{| style=&amp;quot;width:100%; margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width:60%; vertical-align:top;&amp;quot; |&lt;br /&gt;
To find the Orders functionality, select &#039;&#039;&#039;Create Order&#039;&#039;&#039; from the itinerary section in the ECH. This opens the Orders workspace in a full-screen modal.&lt;br /&gt;
&lt;br /&gt;
On opening, users can select the type of order to create using the &#039;&#039;&#039;Order Type&#039;&#039;&#039; dropdown in the top bar:&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Accommodation&#039;&#039;&#039; - For hotel and accommodation requests&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Flight&#039;&#039;&#039; - For flight booking requests&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:40%; vertical-align:top;&amp;quot; |[[File:Screenshot 2026-08-04 at 11.07.33.png|thumb|When you have no existing orders, button is located bottom centre.]][[File:Screenshot 2026-08-04 at 11.08.41.png|thumb|Button moves into the header when you have existing orders.]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
= Managing Orders =&lt;br /&gt;
{| style=&amp;quot;width:100%; margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width:60%; vertical-align:top;&amp;quot; |New orders begin as unsaved drafts until they are saved.&lt;br /&gt;
When creating a new order, the form is automatically pre-filled using information from the selected itinerary, including dates, location, and lead booker details where available. The agent notes field is pre-populated with a template relevant to the selected order type.&lt;br /&gt;
&lt;br /&gt;
=== Layout Overview ===&lt;br /&gt;
The Orders workspace is divided into four main sections:&lt;br /&gt;
&lt;br /&gt;
- Top Bar&lt;br /&gt;
&lt;br /&gt;
- Sidebar&lt;br /&gt;
&lt;br /&gt;
- Main Form&lt;br /&gt;
&lt;br /&gt;
- Bottom Bar&lt;br /&gt;
&lt;br /&gt;
== Top Bar ==&lt;br /&gt;
&lt;br /&gt;
=== Order Type Selector ===&lt;br /&gt;
Dropdown to select the type of order to create when clicking &amp;quot;Create New&amp;quot;:&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Accommodation&#039;&#039;&#039; - Hotel and accommodation booking requests&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Flight&#039;&#039;&#039; - Flight booking requests&lt;br /&gt;
&lt;br /&gt;
Changing the selector does not affect the currently open order. The selected type applies to the next new order created.&lt;br /&gt;
&lt;br /&gt;
=== Reset ===&lt;br /&gt;
Restores the currently selected order back to its last saved state.&lt;br /&gt;
&lt;br /&gt;
If editing a new unsaved draft, the form will revert to its original pre-filled itinerary values.&lt;br /&gt;
&lt;br /&gt;
=== Create New ===&lt;br /&gt;
Creates a new unsaved order draft of the type selected in the Order Type dropdown, while keeping the current modal open.&lt;br /&gt;
&lt;br /&gt;
If unsaved changes exist, the user will be prompted to save or discard them before continuing.&lt;br /&gt;
&lt;br /&gt;
The new order is automatically given a unique title based on the itinerary name.&lt;br /&gt;
&lt;br /&gt;
=== Close ===&lt;br /&gt;
Closes the Orders modal.&lt;br /&gt;
&lt;br /&gt;
If there are unsaved changes, the user will be prompted to save or discard the draft before closing.&lt;br /&gt;
&lt;br /&gt;
== Sidebar ==&lt;br /&gt;
The sidebar contains all saved orders (both Accommodation and Flight) for the currently selected itinerary.&lt;br /&gt;
&lt;br /&gt;
=== Search ===&lt;br /&gt;
Filters saved orders by title.&lt;br /&gt;
&lt;br /&gt;
=== Refresh ===&lt;br /&gt;
Reloads the latest orders from the server without closing the modal.&lt;br /&gt;
&lt;br /&gt;
=== Order Entries ===&lt;br /&gt;
Displays all saved orders ordered by most recently updated first.&lt;br /&gt;
&lt;br /&gt;
Each entry displays:&lt;br /&gt;
&lt;br /&gt;
- Order title&lt;br /&gt;
&lt;br /&gt;
- Order type tag (&#039;&#039;&#039;Accommodation&#039;&#039;&#039; or &#039;&#039;&#039;Flight&#039;&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
- Last modified date and time&lt;br /&gt;
&lt;br /&gt;
Selecting a different order will load its saved data into the form and automatically switch the form to the correct type.&lt;br /&gt;
&lt;br /&gt;
If unsaved changes exist, the user will be prompted to save or discard them before switching.&lt;br /&gt;
&lt;br /&gt;
When no order is selected, the sidebar shows a &#039;&#039;&#039;Draft&#039;&#039;&#039; entry indicating an unsaved draft is being edited.&lt;br /&gt;
&lt;br /&gt;
== Bottom Bar ==&lt;br /&gt;
&lt;br /&gt;
=== Save ===&lt;br /&gt;
Saves the current order.&lt;br /&gt;
&lt;br /&gt;
Once saved:&lt;br /&gt;
&lt;br /&gt;
- The order becomes persistent&lt;br /&gt;
&lt;br /&gt;
- It appears in the sidebar with the appropriate type tag&lt;br /&gt;
&lt;br /&gt;
- Future edits can be restored using Reset&lt;br /&gt;
&lt;br /&gt;
=== Delete / Discard Draft ===&lt;br /&gt;
Deletes the currently selected saved order. This action cannot be undone and requires confirmation.&lt;br /&gt;
&lt;br /&gt;
If working on an unsaved draft, this button instead discards the draft and requires confirmation.&lt;br /&gt;
&lt;br /&gt;
=== Generate PDF ===&lt;br /&gt;
Generates a PDF version of the current order using all entered form data. The PDF format adapts to the order type:&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Accommodation PDF&#039;&#039;&#039; - Includes hotel details, guest rooming assignments, check-in/check-out times, and contact information. Designed for sharing with hotels, accommodation providers, or booking agents.&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Flight PDF&#039;&#039;&#039; - Includes flight details, passenger list, airline information, departure and arrival details, and special requests. Designed for sharing with airlines, flight providers, or booking agents.&lt;br /&gt;
&lt;br /&gt;
=== Export Format ===&lt;br /&gt;
Optional dropdown to select the export file format:&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;XLSX&#039;&#039;&#039; (default)&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;CSV&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=== Export ===&lt;br /&gt;
Generates a downloadable spreadsheet of the current order&#039;s details. The exported file format adapts to the order type:&lt;br /&gt;
&lt;br /&gt;
==== Accommodation Export ====&lt;br /&gt;
Includes:&lt;br /&gt;
&lt;br /&gt;
- Team Name, Itinerary Name, Order Name&lt;br /&gt;
&lt;br /&gt;
- Selected Hotel details (Name, Address, Check-In/Out Times, Telephone)&lt;br /&gt;
&lt;br /&gt;
- Guest table with: Guest Names, Check-In Date/Time, Check-Out Date/Time, Room Type, Booking Reference&lt;br /&gt;
&lt;br /&gt;
==== Flight Export ====&lt;br /&gt;
Includes:&lt;br /&gt;
&lt;br /&gt;
- Team Name, Itinerary Name, Order Name&lt;br /&gt;
&lt;br /&gt;
- Flight details (Airline, Cabin Class, Flight Number, Departure Date/Time &amp;amp; Airport, Arrival Date/Time &amp;amp; Airport)&lt;br /&gt;
&lt;br /&gt;
- Passenger table with: Passenger Names, Booking Reference&lt;br /&gt;
&lt;br /&gt;
=== Import ===&lt;br /&gt;
Imports order data from a previously exported XLSX or CSV file. The system automatically detects whether the file contains Accommodation or Flight data and populates the corresponding form.&lt;br /&gt;
&lt;br /&gt;
==== Accommodation Import ====&lt;br /&gt;
Imports hotel details, guest room assignments, check-in/check-out dates, room types, and booking references. Creates a new hotel in the itinerary and associates it with the imported order. Validates guest names against known users, date formats, and room date logic.&lt;br /&gt;
&lt;br /&gt;
==== Flight Import ====&lt;br /&gt;
Imports flight details including airline, cabin class, flight number, departure/arrival airports and dates, and passenger list. Creates a new flight in the itinerary and associates it with the imported order. Validates passenger names against known users, airport codes, date formats, and cabin class values.&lt;br /&gt;
&lt;br /&gt;
If validation errors are found during import, they are displayed in a dialog showing a spreadsheet preview of the imported data with errors highlighted, allowing the user to identify and fix issues before re-importing.&lt;br /&gt;
&lt;br /&gt;
== General Form Fields ==&lt;br /&gt;
These fields are shared across both Accommodation and Flight order types.&lt;br /&gt;
&lt;br /&gt;
=== Order Name * ===&lt;br /&gt;
The title of the order.&lt;br /&gt;
&lt;br /&gt;
This is used:&lt;br /&gt;
&lt;br /&gt;
- In the sidebar list&lt;br /&gt;
&lt;br /&gt;
- As the PDF title&lt;br /&gt;
&lt;br /&gt;
- To help identify booking requests&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
- &amp;quot;Trip to Milan&amp;quot;&lt;br /&gt;
&lt;br /&gt;
- &amp;quot;Barcelona Conference Accommodation&amp;quot;&lt;br /&gt;
&lt;br /&gt;
- &amp;quot;London Team Flight Bookings&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Contact Name ===&lt;br /&gt;
The primary contact person responsible for the booking request. Typically pre-filled using the current user profile.&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Phone Number ===&lt;br /&gt;
The primary contact phone number for suppliers to use when responding to the request.&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Contact Email ===&lt;br /&gt;
The main email address suppliers should use for communication. Usually pre-filled from the logged-in user profile.&lt;br /&gt;
&lt;br /&gt;
=== Additional Emails ===&lt;br /&gt;
Optional comma-separated email addresses that should also receive communications or copies of the generated PDF.&lt;br /&gt;
&lt;br /&gt;
Example: &amp;lt;code&amp;gt;ops@company.com, travel@company.com&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Event Location ===&lt;br /&gt;
The destination, venue, or event location related to the booking request. Uses an interactive map address selector.&lt;br /&gt;
&lt;br /&gt;
=== Stay Dates * ===&lt;br /&gt;
The date range for the booking. Typically pre-filled from the itinerary dates.&lt;br /&gt;
&lt;br /&gt;
=== Response Due Date ===&lt;br /&gt;
The deadline by which suppliers or agents should respond to the request.&lt;br /&gt;
&lt;br /&gt;
=== Additional Information for Agent ===&lt;br /&gt;
Free-text notes intended for suppliers or booking agents. Character limit of 1024 with a remaining character counter.&lt;br /&gt;
&lt;br /&gt;
This content is included in the generated PDF. The field is pre-populated with a template based on the order type:&lt;br /&gt;
&lt;br /&gt;
==== Accommodation template ====&lt;br /&gt;
&lt;br /&gt;
- Desired room type&lt;br /&gt;
&lt;br /&gt;
- Required services (wifi, parking, breakfast etc)&lt;br /&gt;
&lt;br /&gt;
- Additional requests&lt;br /&gt;
&lt;br /&gt;
==== Flight template ====&lt;br /&gt;
&lt;br /&gt;
- Special meal requirements&lt;br /&gt;
&lt;br /&gt;
- Seat preferences&lt;br /&gt;
&lt;br /&gt;
- Additional requests&lt;br /&gt;
&lt;br /&gt;
=== Team Internal Comments ===&lt;br /&gt;
Internal-only notes visible to EventR users. Intended for operational or planning purposes and not shared with suppliers.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
- Internal approval notes&lt;br /&gt;
&lt;br /&gt;
- Supplier preferences&lt;br /&gt;
&lt;br /&gt;
- Budget discussions&lt;br /&gt;
&lt;br /&gt;
- Booking reminders&lt;br /&gt;
&lt;br /&gt;
== Accommodation-Specific Fields ==&lt;br /&gt;
&lt;br /&gt;
=== Select Pending Hotel ===&lt;br /&gt;
Selects an existing pending hotel/accommodation item from the itinerary.&lt;br /&gt;
&lt;br /&gt;
When selected:&lt;br /&gt;
&lt;br /&gt;
- Related guest information can be used&lt;br /&gt;
&lt;br /&gt;
- Room counts may auto-populate based on assigned guests&lt;br /&gt;
&lt;br /&gt;
- Guest data can be included in the generated PDF&lt;br /&gt;
&lt;br /&gt;
# Only hotels currently marked as &#039;&#039;&#039;Pending&#039;&#039;&#039; are available.&lt;br /&gt;
&lt;br /&gt;
=== Number of Rooms Required ===&lt;br /&gt;
The total number of rooms required for the stay. May automatically populate based on the selected hotel&#039;s guest assignments, but can also be edited manually.&lt;br /&gt;
&lt;br /&gt;
=== Maximum Number of Hotels to Split \* ===&lt;br /&gt;
Defines how many separate hotels the booking can be split across. Options: 1, 2, 3, or 4.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
- &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; = all guests must stay in the same hotel&lt;br /&gt;
- &amp;lt;code&amp;gt;2&amp;lt;/code&amp;gt; = guests may be split between two hotels&lt;br /&gt;
&lt;br /&gt;
=== Maximum Distance from Event ===&lt;br /&gt;
Optional distance limit between the accommodation and the event location.&lt;br /&gt;
&lt;br /&gt;
# Examples: &amp;quot;5km&amp;quot;, &amp;quot;15 minute walk&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== Minimum Cost per Night per Room ===&lt;br /&gt;
Optional minimum nightly room budget. Useful when requesting accommodation within a preferred pricing range.&lt;br /&gt;
&lt;br /&gt;
=== Maximum Cost per Night per Room ===&lt;br /&gt;
Optional maximum nightly room budget. Helps suppliers avoid quoting accommodation outside budget requirements.&lt;br /&gt;
&lt;br /&gt;
== Flight-Specific Fields ==&lt;br /&gt;
&lt;br /&gt;
=== Select Pending Flight ===&lt;br /&gt;
Selects an existing pending flight from the itinerary.&lt;br /&gt;
&lt;br /&gt;
When selected, the form is automatically pre-populated with:&lt;br /&gt;
&lt;br /&gt;
- Flight number/booking reference&lt;br /&gt;
&lt;br /&gt;
- Airline name &lt;br /&gt;
&lt;br /&gt;
- Departure airport&lt;br /&gt;
&lt;br /&gt;
- Arrival airport&lt;br /&gt;
&lt;br /&gt;
- Departure date and time&lt;br /&gt;
&lt;br /&gt;
- Arrival date and time&lt;br /&gt;
&lt;br /&gt;
- Number of passengers&lt;br /&gt;
&lt;br /&gt;
Only flights currently marked as &#039;&#039;&#039;Pending&#039;&#039;&#039; are available.&lt;br /&gt;
&lt;br /&gt;
=== Flight Number ===&lt;br /&gt;
The flight booking reference number. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Airline ===&lt;br /&gt;
The airline operating the flight. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Number of Passengers ===&lt;br /&gt;
The total number of passengers for the flight. May automatically populate based on the selected flight&#039;s passenger list, but can also be edited manually.&lt;br /&gt;
&lt;br /&gt;
=== Cabin Class ===&lt;br /&gt;
The requested cabin class for the flight. Options:&lt;br /&gt;
&lt;br /&gt;
- Economy&lt;br /&gt;
&lt;br /&gt;
- Premium Economy&lt;br /&gt;
&lt;br /&gt;
- Business&lt;br /&gt;
&lt;br /&gt;
- First&lt;br /&gt;
&lt;br /&gt;
=== Departure Airport ===&lt;br /&gt;
The departure airport for the flight. Uses an interactive airport selector with search functionality. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Arrival Airport ===&lt;br /&gt;
The arrival airport for the flight. Uses an interactive airport selector with search functionality. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Departure Date ===&lt;br /&gt;
The departure date and time for the flight. Uses a date/time picker with warning indicators for dates outside the event range. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Arrival Date ===&lt;br /&gt;
The arrival date and time for the flight. Uses a date/time picker with warning indicators for dates outside the event range. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
== Draft Handling ==&lt;br /&gt;
Orders support unsaved drafts.&lt;br /&gt;
&lt;br /&gt;
If the user attempts to:&lt;br /&gt;
&lt;br /&gt;
- Close the modal&lt;br /&gt;
&lt;br /&gt;
- Switch orders&lt;br /&gt;
&lt;br /&gt;
- Refresh data&lt;br /&gt;
&lt;br /&gt;
- Create a new draft&lt;br /&gt;
&lt;br /&gt;
- Change the order type (while in unsaved draft mode)&lt;br /&gt;
&lt;br /&gt;
while unsaved changes exist, EventR will prompt the user to:&lt;br /&gt;
&lt;br /&gt;
- Save changes&lt;br /&gt;
&lt;br /&gt;
- Discard changes&lt;br /&gt;
&lt;br /&gt;
This helps prevent accidental data loss.&lt;br /&gt;
| style=&amp;quot;width:40%; vertical-align:top;&amp;quot; |[[File:Screenshot 2026-08-04 at 11.11.05.png|thumb|Example: Draft order]][[File:Screenshot 2026-08-04 at 11.19.48.png|thumb|Multiple orders view with type tags]]&lt;br /&gt;
|}&lt;br /&gt;
[[Category:3.4.1]]&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=File:Screenshot_2026-08-04_at_11.19.48.png&amp;diff=1393</id>
		<title>File:Screenshot 2026-08-04 at 11.19.48.png</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=File:Screenshot_2026-08-04_at_11.19.48.png&amp;diff=1393"/>
		<updated>2026-08-04T10:20:05Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Flight order&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=File:Screenshot_2026-08-04_at_11.11.05.png&amp;diff=1392</id>
		<title>File:Screenshot 2026-08-04 at 11.11.05.png</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=File:Screenshot_2026-08-04_at_11.11.05.png&amp;diff=1392"/>
		<updated>2026-08-04T10:11:45Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Example accommodation order draft&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=Orders&amp;diff=1391</id>
		<title>Orders</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=Orders&amp;diff=1391"/>
		<updated>2026-08-04T10:09:21Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Infobox Feature&lt;br /&gt;
 | name = Orders&lt;br /&gt;
 | version = [[Release 3.4.1|3.4.1]] (BETA)&lt;br /&gt;
 | tier = Standard, Premium and Enterprise&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
= Overview =&lt;br /&gt;
The &#039;&#039;&#039;Orders&#039;&#039;&#039; feature allows users to create, manage, save, and generate request documents for both &#039;&#039;&#039;Accommodation&#039;&#039;&#039; and &#039;&#039;&#039;Flight&#039;&#039;&#039; bookings. It acts as a central workspace for collecting booking requirements, guest preferences, and order details related to an itinerary. Users can generate PDFs for sharing with suppliers, export order data to spreadsheets, and import existing booking data from exported files.&lt;br /&gt;
&lt;br /&gt;
= Accessing Orders =&lt;br /&gt;
{| style=&amp;quot;width:100%; margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width:60%; vertical-align:top;&amp;quot; |&lt;br /&gt;
To find the Orders functionality, select &#039;&#039;&#039;Create Order&#039;&#039;&#039; from the itinerary section in the ECH. This opens the Orders workspace in a full-screen modal.&lt;br /&gt;
&lt;br /&gt;
On opening, users can select the type of order to create using the &#039;&#039;&#039;Order Type&#039;&#039;&#039; dropdown in the top bar:&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Accommodation&#039;&#039;&#039; - For hotel and accommodation requests&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Flight&#039;&#039;&#039; - For flight booking requests&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:40%; vertical-align:top;&amp;quot; |[[File:Screenshot 2026-08-04 at 11.07.33.png|thumb|When you have no existing orders, button is located bottom centre.]][[File:Screenshot 2026-08-04 at 11.08.41.png|thumb|Button moves into the header when you have existing orders.]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
= Managing Orders =&lt;br /&gt;
{| style=&amp;quot;width:100%; margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width:60%; vertical-align:top;&amp;quot; |New orders begin as unsaved drafts until they are saved.&lt;br /&gt;
When creating a new order, the form is automatically pre-filled using information from the selected itinerary, including dates, location, and lead booker details where available. The agent notes field is pre-populated with a template relevant to the selected order type.&lt;br /&gt;
&lt;br /&gt;
=== Layout Overview ===&lt;br /&gt;
The Orders workspace is divided into four main sections:&lt;br /&gt;
&lt;br /&gt;
- Top Bar&lt;br /&gt;
&lt;br /&gt;
- Sidebar&lt;br /&gt;
&lt;br /&gt;
- Main Form&lt;br /&gt;
&lt;br /&gt;
- Bottom Bar&lt;br /&gt;
&lt;br /&gt;
== Top Bar ==&lt;br /&gt;
&lt;br /&gt;
=== Order Type Selector ===&lt;br /&gt;
Dropdown to select the type of order to create when clicking &amp;quot;Create New&amp;quot;:&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Accommodation&#039;&#039;&#039; - Hotel and accommodation booking requests&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Flight&#039;&#039;&#039; - Flight booking requests&lt;br /&gt;
&lt;br /&gt;
Changing the selector does not affect the currently open order. The selected type applies to the next new order created.&lt;br /&gt;
&lt;br /&gt;
=== Reset ===&lt;br /&gt;
Restores the currently selected order back to its last saved state.&lt;br /&gt;
&lt;br /&gt;
If editing a new unsaved draft, the form will revert to its original pre-filled itinerary values.&lt;br /&gt;
&lt;br /&gt;
=== Create New ===&lt;br /&gt;
Creates a new unsaved order draft of the type selected in the Order Type dropdown, while keeping the current modal open.&lt;br /&gt;
&lt;br /&gt;
If unsaved changes exist, the user will be prompted to save or discard them before continuing.&lt;br /&gt;
&lt;br /&gt;
The new order is automatically given a unique title based on the itinerary name.&lt;br /&gt;
&lt;br /&gt;
=== Close ===&lt;br /&gt;
Closes the Orders modal.&lt;br /&gt;
&lt;br /&gt;
If there are unsaved changes, the user will be prompted to save or discard the draft before closing.&lt;br /&gt;
&lt;br /&gt;
== Sidebar ==&lt;br /&gt;
The sidebar contains all saved orders (both Accommodation and Flight) for the currently selected itinerary.&lt;br /&gt;
&lt;br /&gt;
=== Search ===&lt;br /&gt;
Filters saved orders by title.&lt;br /&gt;
&lt;br /&gt;
=== Refresh ===&lt;br /&gt;
Reloads the latest orders from the server without closing the modal.&lt;br /&gt;
&lt;br /&gt;
=== Order Entries ===&lt;br /&gt;
Displays all saved orders ordered by most recently updated first.&lt;br /&gt;
&lt;br /&gt;
Each entry displays:&lt;br /&gt;
&lt;br /&gt;
- Order title&lt;br /&gt;
&lt;br /&gt;
- Order type tag (&#039;&#039;&#039;Accommodation&#039;&#039;&#039; or &#039;&#039;&#039;Flight&#039;&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
- Last modified date and time&lt;br /&gt;
&lt;br /&gt;
Selecting a different order will load its saved data into the form and automatically switch the form to the correct type.&lt;br /&gt;
&lt;br /&gt;
If unsaved changes exist, the user will be prompted to save or discard them before switching.&lt;br /&gt;
&lt;br /&gt;
When no order is selected, the sidebar shows a &#039;&#039;&#039;Draft&#039;&#039;&#039; entry indicating an unsaved draft is being edited.&lt;br /&gt;
&lt;br /&gt;
== Bottom Bar ==&lt;br /&gt;
&lt;br /&gt;
=== Save ===&lt;br /&gt;
Saves the current order.&lt;br /&gt;
&lt;br /&gt;
Once saved:&lt;br /&gt;
&lt;br /&gt;
- The order becomes persistent&lt;br /&gt;
&lt;br /&gt;
- It appears in the sidebar with the appropriate type tag&lt;br /&gt;
&lt;br /&gt;
- Future edits can be restored using Reset&lt;br /&gt;
&lt;br /&gt;
=== Delete / Discard Draft ===&lt;br /&gt;
Deletes the currently selected saved order. This action cannot be undone and requires confirmation.&lt;br /&gt;
&lt;br /&gt;
If working on an unsaved draft, this button instead discards the draft and requires confirmation.&lt;br /&gt;
&lt;br /&gt;
=== Generate PDF ===&lt;br /&gt;
Generates a PDF version of the current order using all entered form data. The PDF format adapts to the order type:&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Accommodation PDF&#039;&#039;&#039; - Includes hotel details, guest rooming assignments, check-in/check-out times, and contact information. Designed for sharing with hotels, accommodation providers, or booking agents.&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Flight PDF&#039;&#039;&#039; - Includes flight details, passenger list, airline information, departure and arrival details, and special requests. Designed for sharing with airlines, flight providers, or booking agents.&lt;br /&gt;
&lt;br /&gt;
=== Export Format ===&lt;br /&gt;
Optional dropdown to select the export file format:&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;XLSX&#039;&#039;&#039; (default)&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;CSV&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=== Export ===&lt;br /&gt;
Generates a downloadable spreadsheet of the current order&#039;s details. The exported file format adapts to the order type:&lt;br /&gt;
&lt;br /&gt;
==== Accommodation Export ====&lt;br /&gt;
Includes:&lt;br /&gt;
&lt;br /&gt;
- Team Name, Itinerary Name, Order Name&lt;br /&gt;
&lt;br /&gt;
- Selected Hotel details (Name, Address, Check-In/Out Times, Telephone)&lt;br /&gt;
&lt;br /&gt;
- Guest table with: Guest Names, Check-In Date/Time, Check-Out Date/Time, Room Type, Booking Reference&lt;br /&gt;
&lt;br /&gt;
==== Flight Export ====&lt;br /&gt;
Includes:&lt;br /&gt;
&lt;br /&gt;
- Team Name, Itinerary Name, Order Name&lt;br /&gt;
&lt;br /&gt;
- Flight details (Airline, Cabin Class, Flight Number, Departure Date/Time &amp;amp; Airport, Arrival Date/Time &amp;amp; Airport)&lt;br /&gt;
&lt;br /&gt;
- Passenger table with: Passenger Names, Booking Reference&lt;br /&gt;
&lt;br /&gt;
=== Import ===&lt;br /&gt;
Imports order data from a previously exported XLSX or CSV file. The system automatically detects whether the file contains Accommodation or Flight data and populates the corresponding form.&lt;br /&gt;
&lt;br /&gt;
==== Accommodation Import ====&lt;br /&gt;
Imports hotel details, guest room assignments, check-in/check-out dates, room types, and booking references. Creates a new hotel in the itinerary and associates it with the imported order. Validates guest names against known users, date formats, and room date logic.&lt;br /&gt;
&lt;br /&gt;
==== Flight Import ====&lt;br /&gt;
Imports flight details including airline, cabin class, flight number, departure/arrival airports and dates, and passenger list. Creates a new flight in the itinerary and associates it with the imported order. Validates passenger names against known users, airport codes, date formats, and cabin class values.&lt;br /&gt;
&lt;br /&gt;
If validation errors are found during import, they are displayed in a dialog showing a spreadsheet preview of the imported data with errors highlighted, allowing the user to identify and fix issues before re-importing.&lt;br /&gt;
&lt;br /&gt;
== General Form Fields ==&lt;br /&gt;
These fields are shared across both Accommodation and Flight order types.&lt;br /&gt;
&lt;br /&gt;
=== Order Name * ===&lt;br /&gt;
The title of the order.&lt;br /&gt;
&lt;br /&gt;
This is used:&lt;br /&gt;
&lt;br /&gt;
- In the sidebar list&lt;br /&gt;
&lt;br /&gt;
- As the PDF title&lt;br /&gt;
&lt;br /&gt;
- To help identify booking requests&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
- &amp;quot;Trip to Milan&amp;quot;&lt;br /&gt;
&lt;br /&gt;
- &amp;quot;Barcelona Conference Accommodation&amp;quot;&lt;br /&gt;
&lt;br /&gt;
- &amp;quot;London Team Flight Bookings&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Contact Name ===&lt;br /&gt;
The primary contact person responsible for the booking request. Typically pre-filled using the current user profile.&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Phone Number ===&lt;br /&gt;
The primary contact phone number for suppliers to use when responding to the request.&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Contact Email ===&lt;br /&gt;
The main email address suppliers should use for communication. Usually pre-filled from the logged-in user profile.&lt;br /&gt;
&lt;br /&gt;
=== Additional Emails ===&lt;br /&gt;
Optional comma-separated email addresses that should also receive communications or copies of the generated PDF.&lt;br /&gt;
&lt;br /&gt;
Example: &amp;lt;code&amp;gt;ops@company.com, travel@company.com&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Event Location ===&lt;br /&gt;
The destination, venue, or event location related to the booking request. Uses an interactive map address selector.&lt;br /&gt;
&lt;br /&gt;
=== Stay Dates * ===&lt;br /&gt;
The date range for the booking. Typically pre-filled from the itinerary dates.&lt;br /&gt;
&lt;br /&gt;
=== Response Due Date ===&lt;br /&gt;
The deadline by which suppliers or agents should respond to the request.&lt;br /&gt;
&lt;br /&gt;
=== Additional Information for Agent ===&lt;br /&gt;
Free-text notes intended for suppliers or booking agents. Character limit of 1024 with a remaining character counter.&lt;br /&gt;
&lt;br /&gt;
This content is included in the generated PDF. The field is pre-populated with a template based on the order type:&lt;br /&gt;
&lt;br /&gt;
==== Accommodation template ====&lt;br /&gt;
&lt;br /&gt;
- Desired room type&lt;br /&gt;
&lt;br /&gt;
- Required services (wifi, parking, breakfast etc)&lt;br /&gt;
&lt;br /&gt;
- Additional requests&lt;br /&gt;
&lt;br /&gt;
==== Flight template ====&lt;br /&gt;
&lt;br /&gt;
- Special meal requirements&lt;br /&gt;
&lt;br /&gt;
- Seat preferences&lt;br /&gt;
&lt;br /&gt;
- Additional requests&lt;br /&gt;
&lt;br /&gt;
=== Team Internal Comments ===&lt;br /&gt;
Internal-only notes visible to EventR users. Intended for operational or planning purposes and not shared with suppliers.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
- Internal approval notes&lt;br /&gt;
&lt;br /&gt;
- Supplier preferences&lt;br /&gt;
&lt;br /&gt;
- Budget discussions&lt;br /&gt;
&lt;br /&gt;
- Booking reminders&lt;br /&gt;
&lt;br /&gt;
== Accommodation-Specific Fields ==&lt;br /&gt;
&lt;br /&gt;
=== Select Pending Hotel ===&lt;br /&gt;
Selects an existing pending hotel/accommodation item from the itinerary.&lt;br /&gt;
&lt;br /&gt;
When selected:&lt;br /&gt;
&lt;br /&gt;
- Related guest information can be used&lt;br /&gt;
&lt;br /&gt;
- Room counts may auto-populate based on assigned guests&lt;br /&gt;
&lt;br /&gt;
- Guest data can be included in the generated PDF&lt;br /&gt;
&lt;br /&gt;
# Only hotels currently marked as &#039;&#039;&#039;Pending&#039;&#039;&#039; are available.&lt;br /&gt;
&lt;br /&gt;
=== Number of Rooms Required ===&lt;br /&gt;
The total number of rooms required for the stay. May automatically populate based on the selected hotel&#039;s guest assignments, but can also be edited manually.&lt;br /&gt;
&lt;br /&gt;
=== Maximum Number of Hotels to Split \* ===&lt;br /&gt;
Defines how many separate hotels the booking can be split across. Options: 1, 2, 3, or 4.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
- &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; = all guests must stay in the same hotel&lt;br /&gt;
- &amp;lt;code&amp;gt;2&amp;lt;/code&amp;gt; = guests may be split between two hotels&lt;br /&gt;
&lt;br /&gt;
=== Maximum Distance from Event ===&lt;br /&gt;
Optional distance limit between the accommodation and the event location.&lt;br /&gt;
&lt;br /&gt;
# Examples: &amp;quot;5km&amp;quot;, &amp;quot;15 minute walk&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== Minimum Cost per Night per Room ===&lt;br /&gt;
Optional minimum nightly room budget. Useful when requesting accommodation within a preferred pricing range.&lt;br /&gt;
&lt;br /&gt;
=== Maximum Cost per Night per Room ===&lt;br /&gt;
Optional maximum nightly room budget. Helps suppliers avoid quoting accommodation outside budget requirements.&lt;br /&gt;
&lt;br /&gt;
== Flight-Specific Fields ==&lt;br /&gt;
&lt;br /&gt;
=== Select Pending Flight ===&lt;br /&gt;
Selects an existing pending flight from the itinerary.&lt;br /&gt;
&lt;br /&gt;
When selected, the form is automatically pre-populated with:&lt;br /&gt;
&lt;br /&gt;
- Flight number/booking reference&lt;br /&gt;
&lt;br /&gt;
- Airline name &lt;br /&gt;
&lt;br /&gt;
- Departure airport&lt;br /&gt;
&lt;br /&gt;
- Arrival airport&lt;br /&gt;
&lt;br /&gt;
- Departure date and time&lt;br /&gt;
&lt;br /&gt;
- Arrival date and time&lt;br /&gt;
&lt;br /&gt;
- Number of passengers&lt;br /&gt;
&lt;br /&gt;
Only flights currently marked as &#039;&#039;&#039;Pending&#039;&#039;&#039; are available.&lt;br /&gt;
&lt;br /&gt;
=== Flight Number ===&lt;br /&gt;
The flight booking reference number. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Airline ===&lt;br /&gt;
The airline operating the flight. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Number of Passengers ===&lt;br /&gt;
The total number of passengers for the flight. May automatically populate based on the selected flight&#039;s passenger list, but can also be edited manually.&lt;br /&gt;
&lt;br /&gt;
=== Cabin Class ===&lt;br /&gt;
The requested cabin class for the flight. Options:&lt;br /&gt;
&lt;br /&gt;
- Economy&lt;br /&gt;
&lt;br /&gt;
- Premium Economy&lt;br /&gt;
&lt;br /&gt;
- Business&lt;br /&gt;
&lt;br /&gt;
- First&lt;br /&gt;
&lt;br /&gt;
=== Departure Airport ===&lt;br /&gt;
The departure airport for the flight. Uses an interactive airport selector with search functionality. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Arrival Airport ===&lt;br /&gt;
The arrival airport for the flight. Uses an interactive airport selector with search functionality. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Departure Date ===&lt;br /&gt;
The departure date and time for the flight. Uses a date/time picker with warning indicators for dates outside the event range. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Arrival Date ===&lt;br /&gt;
The arrival date and time for the flight. Uses a date/time picker with warning indicators for dates outside the event range. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
== Draft Handling ==&lt;br /&gt;
Orders support unsaved drafts.&lt;br /&gt;
&lt;br /&gt;
If the user attempts to:&lt;br /&gt;
&lt;br /&gt;
- Close the modal&lt;br /&gt;
&lt;br /&gt;
- Switch orders&lt;br /&gt;
&lt;br /&gt;
- Refresh data&lt;br /&gt;
&lt;br /&gt;
- Create a new draft&lt;br /&gt;
&lt;br /&gt;
- Change the order type (while in unsaved draft mode)&lt;br /&gt;
&lt;br /&gt;
while unsaved changes exist, EventR will prompt the user to:&lt;br /&gt;
&lt;br /&gt;
- Save changes&lt;br /&gt;
&lt;br /&gt;
- Discard changes&lt;br /&gt;
&lt;br /&gt;
This helps prevent accidental data loss.&lt;br /&gt;
| style=&amp;quot;width:40%; vertical-align:top;&amp;quot; |&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.49.46.png|thumb|Example: Draft order]]&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.58.44.png|thumb|Multiple orders view with type tags]]&lt;br /&gt;
|}&lt;br /&gt;
[[Category:3.4.1]]&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=File:Screenshot_2026-08-04_at_11.08.41.png&amp;diff=1390</id>
		<title>File:Screenshot 2026-08-04 at 11.08.41.png</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=File:Screenshot_2026-08-04_at_11.08.41.png&amp;diff=1390"/>
		<updated>2026-08-04T10:09:15Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Top section&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=Orders&amp;diff=1389</id>
		<title>Orders</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=Orders&amp;diff=1389"/>
		<updated>2026-08-04T10:08:17Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Infobox Feature&lt;br /&gt;
 | name = Orders&lt;br /&gt;
 | version = [[Release 3.4.1|3.4.1]] (BETA)&lt;br /&gt;
 | tier = Standard, Premium and Enterprise&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
= Overview =&lt;br /&gt;
The &#039;&#039;&#039;Orders&#039;&#039;&#039; feature allows users to create, manage, save, and generate request documents for both &#039;&#039;&#039;Accommodation&#039;&#039;&#039; and &#039;&#039;&#039;Flight&#039;&#039;&#039; bookings. It acts as a central workspace for collecting booking requirements, guest preferences, and order details related to an itinerary. Users can generate PDFs for sharing with suppliers, export order data to spreadsheets, and import existing booking data from exported files.&lt;br /&gt;
&lt;br /&gt;
= Accessing Orders =&lt;br /&gt;
{| style=&amp;quot;width:100%; margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width:60%; vertical-align:top;&amp;quot; |&lt;br /&gt;
To find the Orders functionality, select &#039;&#039;&#039;Create Order&#039;&#039;&#039; from the itinerary section in the ECH. This opens the Orders workspace in a full-screen modal.&lt;br /&gt;
&lt;br /&gt;
On opening, users can select the type of order to create using the &#039;&#039;&#039;Order Type&#039;&#039;&#039; dropdown in the top bar:&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Accommodation&#039;&#039;&#039; - For hotel and accommodation requests&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Flight&#039;&#039;&#039; - For flight booking requests&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:40%; vertical-align:top;&amp;quot; |[[File:Screenshot 2026-08-04 at 11.07.33.png|thumb|When you have no existing orders, button is located bottom centre.]][[File:Screenshot 2026-05-06 at 11.38.33.png|thumb|Button moves into the header when you have existing orders.]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
= Managing Orders =&lt;br /&gt;
{| style=&amp;quot;width:100%; margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width:60%; vertical-align:top;&amp;quot; |New orders begin as unsaved drafts until they are saved.&lt;br /&gt;
When creating a new order, the form is automatically pre-filled using information from the selected itinerary, including dates, location, and lead booker details where available. The agent notes field is pre-populated with a template relevant to the selected order type.&lt;br /&gt;
&lt;br /&gt;
=== Layout Overview ===&lt;br /&gt;
The Orders workspace is divided into four main sections:&lt;br /&gt;
&lt;br /&gt;
- Top Bar&lt;br /&gt;
&lt;br /&gt;
- Sidebar&lt;br /&gt;
&lt;br /&gt;
- Main Form&lt;br /&gt;
&lt;br /&gt;
- Bottom Bar&lt;br /&gt;
&lt;br /&gt;
== Top Bar ==&lt;br /&gt;
&lt;br /&gt;
=== Order Type Selector ===&lt;br /&gt;
Dropdown to select the type of order to create when clicking &amp;quot;Create New&amp;quot;:&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Accommodation&#039;&#039;&#039; - Hotel and accommodation booking requests&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Flight&#039;&#039;&#039; - Flight booking requests&lt;br /&gt;
&lt;br /&gt;
Changing the selector does not affect the currently open order. The selected type applies to the next new order created.&lt;br /&gt;
&lt;br /&gt;
=== Reset ===&lt;br /&gt;
Restores the currently selected order back to its last saved state.&lt;br /&gt;
&lt;br /&gt;
If editing a new unsaved draft, the form will revert to its original pre-filled itinerary values.&lt;br /&gt;
&lt;br /&gt;
=== Create New ===&lt;br /&gt;
Creates a new unsaved order draft of the type selected in the Order Type dropdown, while keeping the current modal open.&lt;br /&gt;
&lt;br /&gt;
If unsaved changes exist, the user will be prompted to save or discard them before continuing.&lt;br /&gt;
&lt;br /&gt;
The new order is automatically given a unique title based on the itinerary name.&lt;br /&gt;
&lt;br /&gt;
=== Close ===&lt;br /&gt;
Closes the Orders modal.&lt;br /&gt;
&lt;br /&gt;
If there are unsaved changes, the user will be prompted to save or discard the draft before closing.&lt;br /&gt;
&lt;br /&gt;
== Sidebar ==&lt;br /&gt;
The sidebar contains all saved orders (both Accommodation and Flight) for the currently selected itinerary.&lt;br /&gt;
&lt;br /&gt;
=== Search ===&lt;br /&gt;
Filters saved orders by title.&lt;br /&gt;
&lt;br /&gt;
=== Refresh ===&lt;br /&gt;
Reloads the latest orders from the server without closing the modal.&lt;br /&gt;
&lt;br /&gt;
=== Order Entries ===&lt;br /&gt;
Displays all saved orders ordered by most recently updated first.&lt;br /&gt;
&lt;br /&gt;
Each entry displays:&lt;br /&gt;
&lt;br /&gt;
- Order title&lt;br /&gt;
&lt;br /&gt;
- Order type tag (&#039;&#039;&#039;Accommodation&#039;&#039;&#039; or &#039;&#039;&#039;Flight&#039;&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
- Last modified date and time&lt;br /&gt;
&lt;br /&gt;
Selecting a different order will load its saved data into the form and automatically switch the form to the correct type.&lt;br /&gt;
&lt;br /&gt;
If unsaved changes exist, the user will be prompted to save or discard them before switching.&lt;br /&gt;
&lt;br /&gt;
When no order is selected, the sidebar shows a &#039;&#039;&#039;Draft&#039;&#039;&#039; entry indicating an unsaved draft is being edited.&lt;br /&gt;
&lt;br /&gt;
== Bottom Bar ==&lt;br /&gt;
&lt;br /&gt;
=== Save ===&lt;br /&gt;
Saves the current order.&lt;br /&gt;
&lt;br /&gt;
Once saved:&lt;br /&gt;
&lt;br /&gt;
- The order becomes persistent&lt;br /&gt;
&lt;br /&gt;
- It appears in the sidebar with the appropriate type tag&lt;br /&gt;
&lt;br /&gt;
- Future edits can be restored using Reset&lt;br /&gt;
&lt;br /&gt;
=== Delete / Discard Draft ===&lt;br /&gt;
Deletes the currently selected saved order. This action cannot be undone and requires confirmation.&lt;br /&gt;
&lt;br /&gt;
If working on an unsaved draft, this button instead discards the draft and requires confirmation.&lt;br /&gt;
&lt;br /&gt;
=== Generate PDF ===&lt;br /&gt;
Generates a PDF version of the current order using all entered form data. The PDF format adapts to the order type:&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Accommodation PDF&#039;&#039;&#039; - Includes hotel details, guest rooming assignments, check-in/check-out times, and contact information. Designed for sharing with hotels, accommodation providers, or booking agents.&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Flight PDF&#039;&#039;&#039; - Includes flight details, passenger list, airline information, departure and arrival details, and special requests. Designed for sharing with airlines, flight providers, or booking agents.&lt;br /&gt;
&lt;br /&gt;
=== Export Format ===&lt;br /&gt;
Optional dropdown to select the export file format:&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;XLSX&#039;&#039;&#039; (default)&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;CSV&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=== Export ===&lt;br /&gt;
Generates a downloadable spreadsheet of the current order&#039;s details. The exported file format adapts to the order type:&lt;br /&gt;
&lt;br /&gt;
==== Accommodation Export ====&lt;br /&gt;
Includes:&lt;br /&gt;
&lt;br /&gt;
- Team Name, Itinerary Name, Order Name&lt;br /&gt;
&lt;br /&gt;
- Selected Hotel details (Name, Address, Check-In/Out Times, Telephone)&lt;br /&gt;
&lt;br /&gt;
- Guest table with: Guest Names, Check-In Date/Time, Check-Out Date/Time, Room Type, Booking Reference&lt;br /&gt;
&lt;br /&gt;
==== Flight Export ====&lt;br /&gt;
Includes:&lt;br /&gt;
&lt;br /&gt;
- Team Name, Itinerary Name, Order Name&lt;br /&gt;
&lt;br /&gt;
- Flight details (Airline, Cabin Class, Flight Number, Departure Date/Time &amp;amp; Airport, Arrival Date/Time &amp;amp; Airport)&lt;br /&gt;
&lt;br /&gt;
- Passenger table with: Passenger Names, Booking Reference&lt;br /&gt;
&lt;br /&gt;
=== Import ===&lt;br /&gt;
Imports order data from a previously exported XLSX or CSV file. The system automatically detects whether the file contains Accommodation or Flight data and populates the corresponding form.&lt;br /&gt;
&lt;br /&gt;
==== Accommodation Import ====&lt;br /&gt;
Imports hotel details, guest room assignments, check-in/check-out dates, room types, and booking references. Creates a new hotel in the itinerary and associates it with the imported order. Validates guest names against known users, date formats, and room date logic.&lt;br /&gt;
&lt;br /&gt;
==== Flight Import ====&lt;br /&gt;
Imports flight details including airline, cabin class, flight number, departure/arrival airports and dates, and passenger list. Creates a new flight in the itinerary and associates it with the imported order. Validates passenger names against known users, airport codes, date formats, and cabin class values.&lt;br /&gt;
&lt;br /&gt;
If validation errors are found during import, they are displayed in a dialog showing a spreadsheet preview of the imported data with errors highlighted, allowing the user to identify and fix issues before re-importing.&lt;br /&gt;
&lt;br /&gt;
== General Form Fields ==&lt;br /&gt;
These fields are shared across both Accommodation and Flight order types.&lt;br /&gt;
&lt;br /&gt;
=== Order Name * ===&lt;br /&gt;
The title of the order.&lt;br /&gt;
&lt;br /&gt;
This is used:&lt;br /&gt;
&lt;br /&gt;
- In the sidebar list&lt;br /&gt;
&lt;br /&gt;
- As the PDF title&lt;br /&gt;
&lt;br /&gt;
- To help identify booking requests&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
- &amp;quot;Trip to Milan&amp;quot;&lt;br /&gt;
&lt;br /&gt;
- &amp;quot;Barcelona Conference Accommodation&amp;quot;&lt;br /&gt;
&lt;br /&gt;
- &amp;quot;London Team Flight Bookings&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Contact Name ===&lt;br /&gt;
The primary contact person responsible for the booking request. Typically pre-filled using the current user profile.&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Phone Number ===&lt;br /&gt;
The primary contact phone number for suppliers to use when responding to the request.&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Contact Email ===&lt;br /&gt;
The main email address suppliers should use for communication. Usually pre-filled from the logged-in user profile.&lt;br /&gt;
&lt;br /&gt;
=== Additional Emails ===&lt;br /&gt;
Optional comma-separated email addresses that should also receive communications or copies of the generated PDF.&lt;br /&gt;
&lt;br /&gt;
Example: &amp;lt;code&amp;gt;ops@company.com, travel@company.com&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Event Location ===&lt;br /&gt;
The destination, venue, or event location related to the booking request. Uses an interactive map address selector.&lt;br /&gt;
&lt;br /&gt;
=== Stay Dates * ===&lt;br /&gt;
The date range for the booking. Typically pre-filled from the itinerary dates.&lt;br /&gt;
&lt;br /&gt;
=== Response Due Date ===&lt;br /&gt;
The deadline by which suppliers or agents should respond to the request.&lt;br /&gt;
&lt;br /&gt;
=== Additional Information for Agent ===&lt;br /&gt;
Free-text notes intended for suppliers or booking agents. Character limit of 1024 with a remaining character counter.&lt;br /&gt;
&lt;br /&gt;
This content is included in the generated PDF. The field is pre-populated with a template based on the order type:&lt;br /&gt;
&lt;br /&gt;
==== Accommodation template ====&lt;br /&gt;
&lt;br /&gt;
- Desired room type&lt;br /&gt;
&lt;br /&gt;
- Required services (wifi, parking, breakfast etc)&lt;br /&gt;
&lt;br /&gt;
- Additional requests&lt;br /&gt;
&lt;br /&gt;
==== Flight template ====&lt;br /&gt;
&lt;br /&gt;
- Special meal requirements&lt;br /&gt;
&lt;br /&gt;
- Seat preferences&lt;br /&gt;
&lt;br /&gt;
- Additional requests&lt;br /&gt;
&lt;br /&gt;
=== Team Internal Comments ===&lt;br /&gt;
Internal-only notes visible to EventR users. Intended for operational or planning purposes and not shared with suppliers.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
- Internal approval notes&lt;br /&gt;
&lt;br /&gt;
- Supplier preferences&lt;br /&gt;
&lt;br /&gt;
- Budget discussions&lt;br /&gt;
&lt;br /&gt;
- Booking reminders&lt;br /&gt;
&lt;br /&gt;
== Accommodation-Specific Fields ==&lt;br /&gt;
&lt;br /&gt;
=== Select Pending Hotel ===&lt;br /&gt;
Selects an existing pending hotel/accommodation item from the itinerary.&lt;br /&gt;
&lt;br /&gt;
When selected:&lt;br /&gt;
&lt;br /&gt;
- Related guest information can be used&lt;br /&gt;
&lt;br /&gt;
- Room counts may auto-populate based on assigned guests&lt;br /&gt;
&lt;br /&gt;
- Guest data can be included in the generated PDF&lt;br /&gt;
&lt;br /&gt;
# Only hotels currently marked as &#039;&#039;&#039;Pending&#039;&#039;&#039; are available.&lt;br /&gt;
&lt;br /&gt;
=== Number of Rooms Required ===&lt;br /&gt;
The total number of rooms required for the stay. May automatically populate based on the selected hotel&#039;s guest assignments, but can also be edited manually.&lt;br /&gt;
&lt;br /&gt;
=== Maximum Number of Hotels to Split \* ===&lt;br /&gt;
Defines how many separate hotels the booking can be split across. Options: 1, 2, 3, or 4.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
- &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; = all guests must stay in the same hotel&lt;br /&gt;
- &amp;lt;code&amp;gt;2&amp;lt;/code&amp;gt; = guests may be split between two hotels&lt;br /&gt;
&lt;br /&gt;
=== Maximum Distance from Event ===&lt;br /&gt;
Optional distance limit between the accommodation and the event location.&lt;br /&gt;
&lt;br /&gt;
# Examples: &amp;quot;5km&amp;quot;, &amp;quot;15 minute walk&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== Minimum Cost per Night per Room ===&lt;br /&gt;
Optional minimum nightly room budget. Useful when requesting accommodation within a preferred pricing range.&lt;br /&gt;
&lt;br /&gt;
=== Maximum Cost per Night per Room ===&lt;br /&gt;
Optional maximum nightly room budget. Helps suppliers avoid quoting accommodation outside budget requirements.&lt;br /&gt;
&lt;br /&gt;
== Flight-Specific Fields ==&lt;br /&gt;
&lt;br /&gt;
=== Select Pending Flight ===&lt;br /&gt;
Selects an existing pending flight from the itinerary.&lt;br /&gt;
&lt;br /&gt;
When selected, the form is automatically pre-populated with:&lt;br /&gt;
&lt;br /&gt;
- Flight number/booking reference&lt;br /&gt;
&lt;br /&gt;
- Airline name &lt;br /&gt;
&lt;br /&gt;
- Departure airport&lt;br /&gt;
&lt;br /&gt;
- Arrival airport&lt;br /&gt;
&lt;br /&gt;
- Departure date and time&lt;br /&gt;
&lt;br /&gt;
- Arrival date and time&lt;br /&gt;
&lt;br /&gt;
- Number of passengers&lt;br /&gt;
&lt;br /&gt;
Only flights currently marked as &#039;&#039;&#039;Pending&#039;&#039;&#039; are available.&lt;br /&gt;
&lt;br /&gt;
=== Flight Number ===&lt;br /&gt;
The flight booking reference number. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Airline ===&lt;br /&gt;
The airline operating the flight. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Number of Passengers ===&lt;br /&gt;
The total number of passengers for the flight. May automatically populate based on the selected flight&#039;s passenger list, but can also be edited manually.&lt;br /&gt;
&lt;br /&gt;
=== Cabin Class ===&lt;br /&gt;
The requested cabin class for the flight. Options:&lt;br /&gt;
&lt;br /&gt;
- Economy&lt;br /&gt;
&lt;br /&gt;
- Premium Economy&lt;br /&gt;
&lt;br /&gt;
- Business&lt;br /&gt;
&lt;br /&gt;
- First&lt;br /&gt;
&lt;br /&gt;
=== Departure Airport ===&lt;br /&gt;
The departure airport for the flight. Uses an interactive airport selector with search functionality. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Arrival Airport ===&lt;br /&gt;
The arrival airport for the flight. Uses an interactive airport selector with search functionality. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Departure Date ===&lt;br /&gt;
The departure date and time for the flight. Uses a date/time picker with warning indicators for dates outside the event range. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Arrival Date ===&lt;br /&gt;
The arrival date and time for the flight. Uses a date/time picker with warning indicators for dates outside the event range. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
== Draft Handling ==&lt;br /&gt;
Orders support unsaved drafts.&lt;br /&gt;
&lt;br /&gt;
If the user attempts to:&lt;br /&gt;
&lt;br /&gt;
- Close the modal&lt;br /&gt;
&lt;br /&gt;
- Switch orders&lt;br /&gt;
&lt;br /&gt;
- Refresh data&lt;br /&gt;
&lt;br /&gt;
- Create a new draft&lt;br /&gt;
&lt;br /&gt;
- Change the order type (while in unsaved draft mode)&lt;br /&gt;
&lt;br /&gt;
while unsaved changes exist, EventR will prompt the user to:&lt;br /&gt;
&lt;br /&gt;
- Save changes&lt;br /&gt;
&lt;br /&gt;
- Discard changes&lt;br /&gt;
&lt;br /&gt;
This helps prevent accidental data loss.&lt;br /&gt;
| style=&amp;quot;width:40%; vertical-align:top;&amp;quot; |&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.49.46.png|thumb|Example: Draft order]]&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.58.44.png|thumb|Multiple orders view with type tags]]&lt;br /&gt;
|}&lt;br /&gt;
[[Category:3.4.1]]&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=File:Screenshot_2026-08-04_at_11.07.33.png&amp;diff=1388</id>
		<title>File:Screenshot 2026-08-04 at 11.07.33.png</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=File:Screenshot_2026-08-04_at_11.07.33.png&amp;diff=1388"/>
		<updated>2026-08-04T10:08:05Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Orders&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=Rooming_Lists&amp;diff=1387</id>
		<title>Rooming Lists</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=Rooming_Lists&amp;diff=1387"/>
		<updated>2026-08-04T10:05:51Z</updated>

		<summary type="html">&lt;p&gt;Samh: Samh moved page Rooming Lists to Orders: Renamed&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Orders]]&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=Orders&amp;diff=1386</id>
		<title>Orders</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=Orders&amp;diff=1386"/>
		<updated>2026-08-04T10:05:51Z</updated>

		<summary type="html">&lt;p&gt;Samh: Samh moved page Rooming Lists to Orders: Renamed&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Infobox Feature&lt;br /&gt;
 | name = Orders&lt;br /&gt;
 | version = [[Release 3.4.1|3.4.1]] (BETA)&lt;br /&gt;
 | tier = Standard, Premium and Enterprise&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
= Overview =&lt;br /&gt;
The &#039;&#039;&#039;Orders&#039;&#039;&#039; feature allows users to create, manage, save, and generate request documents for both &#039;&#039;&#039;Accommodation&#039;&#039;&#039; and &#039;&#039;&#039;Flight&#039;&#039;&#039; bookings. It acts as a central workspace for collecting booking requirements, guest preferences, and order details related to an itinerary. Users can generate PDFs for sharing with suppliers, export order data to spreadsheets, and import existing booking data from exported files.&lt;br /&gt;
&lt;br /&gt;
= Accessing Orders =&lt;br /&gt;
{| style=&amp;quot;width:100%; margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width:60%; vertical-align:top;&amp;quot; |&lt;br /&gt;
To find the Orders functionality, select &#039;&#039;&#039;Create Order&#039;&#039;&#039; from the itinerary section in the ECH. This opens the Orders workspace in a full-screen modal.&lt;br /&gt;
&lt;br /&gt;
On opening, users can select the type of order to create using the &#039;&#039;&#039;Order Type&#039;&#039;&#039; dropdown in the top bar:&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Accommodation&#039;&#039;&#039; - For hotel and accommodation requests&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Flight&#039;&#039;&#039; - For flight booking requests&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:40%; vertical-align:top;&amp;quot; |&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.21.54.png|thumb| When you have no existing orders, button is located bottom centre.]]&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.38.33.png|thumb|Button moves into the header when you have existing orders.]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
= Managing Orders =&lt;br /&gt;
{| style=&amp;quot;width:100%; margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width:60%; vertical-align:top;&amp;quot; |New orders begin as unsaved drafts until they are saved.&lt;br /&gt;
When creating a new order, the form is automatically pre-filled using information from the selected itinerary, including dates, location, and lead booker details where available. The agent notes field is pre-populated with a template relevant to the selected order type.&lt;br /&gt;
&lt;br /&gt;
=== Layout Overview ===&lt;br /&gt;
The Orders workspace is divided into four main sections:&lt;br /&gt;
&lt;br /&gt;
- Top Bar&lt;br /&gt;
&lt;br /&gt;
- Sidebar&lt;br /&gt;
&lt;br /&gt;
- Main Form&lt;br /&gt;
&lt;br /&gt;
- Bottom Bar&lt;br /&gt;
&lt;br /&gt;
== Top Bar ==&lt;br /&gt;
&lt;br /&gt;
=== Order Type Selector ===&lt;br /&gt;
Dropdown to select the type of order to create when clicking &amp;quot;Create New&amp;quot;:&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Accommodation&#039;&#039;&#039; - Hotel and accommodation booking requests&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Flight&#039;&#039;&#039; - Flight booking requests&lt;br /&gt;
&lt;br /&gt;
Changing the selector does not affect the currently open order. The selected type applies to the next new order created.&lt;br /&gt;
&lt;br /&gt;
=== Reset ===&lt;br /&gt;
Restores the currently selected order back to its last saved state.&lt;br /&gt;
&lt;br /&gt;
If editing a new unsaved draft, the form will revert to its original pre-filled itinerary values.&lt;br /&gt;
&lt;br /&gt;
=== Create New ===&lt;br /&gt;
Creates a new unsaved order draft of the type selected in the Order Type dropdown, while keeping the current modal open.&lt;br /&gt;
&lt;br /&gt;
If unsaved changes exist, the user will be prompted to save or discard them before continuing.&lt;br /&gt;
&lt;br /&gt;
The new order is automatically given a unique title based on the itinerary name.&lt;br /&gt;
&lt;br /&gt;
=== Close ===&lt;br /&gt;
Closes the Orders modal.&lt;br /&gt;
&lt;br /&gt;
If there are unsaved changes, the user will be prompted to save or discard the draft before closing.&lt;br /&gt;
&lt;br /&gt;
== Sidebar ==&lt;br /&gt;
The sidebar contains all saved orders (both Accommodation and Flight) for the currently selected itinerary.&lt;br /&gt;
&lt;br /&gt;
=== Search ===&lt;br /&gt;
Filters saved orders by title.&lt;br /&gt;
&lt;br /&gt;
=== Refresh ===&lt;br /&gt;
Reloads the latest orders from the server without closing the modal.&lt;br /&gt;
&lt;br /&gt;
=== Order Entries ===&lt;br /&gt;
Displays all saved orders ordered by most recently updated first.&lt;br /&gt;
&lt;br /&gt;
Each entry displays:&lt;br /&gt;
&lt;br /&gt;
- Order title&lt;br /&gt;
&lt;br /&gt;
- Order type tag (&#039;&#039;&#039;Accommodation&#039;&#039;&#039; or &#039;&#039;&#039;Flight&#039;&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
- Last modified date and time&lt;br /&gt;
&lt;br /&gt;
Selecting a different order will load its saved data into the form and automatically switch the form to the correct type.&lt;br /&gt;
&lt;br /&gt;
If unsaved changes exist, the user will be prompted to save or discard them before switching.&lt;br /&gt;
&lt;br /&gt;
When no order is selected, the sidebar shows a &#039;&#039;&#039;Draft&#039;&#039;&#039; entry indicating an unsaved draft is being edited.&lt;br /&gt;
&lt;br /&gt;
== Bottom Bar ==&lt;br /&gt;
&lt;br /&gt;
=== Save ===&lt;br /&gt;
Saves the current order.&lt;br /&gt;
&lt;br /&gt;
Once saved:&lt;br /&gt;
&lt;br /&gt;
- The order becomes persistent&lt;br /&gt;
&lt;br /&gt;
- It appears in the sidebar with the appropriate type tag&lt;br /&gt;
&lt;br /&gt;
- Future edits can be restored using Reset&lt;br /&gt;
&lt;br /&gt;
=== Delete / Discard Draft ===&lt;br /&gt;
Deletes the currently selected saved order. This action cannot be undone and requires confirmation.&lt;br /&gt;
&lt;br /&gt;
If working on an unsaved draft, this button instead discards the draft and requires confirmation.&lt;br /&gt;
&lt;br /&gt;
=== Generate PDF ===&lt;br /&gt;
Generates a PDF version of the current order using all entered form data. The PDF format adapts to the order type:&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Accommodation PDF&#039;&#039;&#039; - Includes hotel details, guest rooming assignments, check-in/check-out times, and contact information. Designed for sharing with hotels, accommodation providers, or booking agents.&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Flight PDF&#039;&#039;&#039; - Includes flight details, passenger list, airline information, departure and arrival details, and special requests. Designed for sharing with airlines, flight providers, or booking agents.&lt;br /&gt;
&lt;br /&gt;
=== Export Format ===&lt;br /&gt;
Optional dropdown to select the export file format:&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;XLSX&#039;&#039;&#039; (default)&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;CSV&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=== Export ===&lt;br /&gt;
Generates a downloadable spreadsheet of the current order&#039;s details. The exported file format adapts to the order type:&lt;br /&gt;
&lt;br /&gt;
==== Accommodation Export ====&lt;br /&gt;
Includes:&lt;br /&gt;
&lt;br /&gt;
- Team Name, Itinerary Name, Order Name&lt;br /&gt;
&lt;br /&gt;
- Selected Hotel details (Name, Address, Check-In/Out Times, Telephone)&lt;br /&gt;
&lt;br /&gt;
- Guest table with: Guest Names, Check-In Date/Time, Check-Out Date/Time, Room Type, Booking Reference&lt;br /&gt;
&lt;br /&gt;
==== Flight Export ====&lt;br /&gt;
Includes:&lt;br /&gt;
&lt;br /&gt;
- Team Name, Itinerary Name, Order Name&lt;br /&gt;
&lt;br /&gt;
- Flight details (Airline, Cabin Class, Flight Number, Departure Date/Time &amp;amp; Airport, Arrival Date/Time &amp;amp; Airport)&lt;br /&gt;
&lt;br /&gt;
- Passenger table with: Passenger Names, Booking Reference&lt;br /&gt;
&lt;br /&gt;
=== Import ===&lt;br /&gt;
Imports order data from a previously exported XLSX or CSV file. The system automatically detects whether the file contains Accommodation or Flight data and populates the corresponding form.&lt;br /&gt;
&lt;br /&gt;
==== Accommodation Import ====&lt;br /&gt;
Imports hotel details, guest room assignments, check-in/check-out dates, room types, and booking references. Creates a new hotel in the itinerary and associates it with the imported order. Validates guest names against known users, date formats, and room date logic.&lt;br /&gt;
&lt;br /&gt;
==== Flight Import ====&lt;br /&gt;
Imports flight details including airline, cabin class, flight number, departure/arrival airports and dates, and passenger list. Creates a new flight in the itinerary and associates it with the imported order. Validates passenger names against known users, airport codes, date formats, and cabin class values.&lt;br /&gt;
&lt;br /&gt;
If validation errors are found during import, they are displayed in a dialog showing a spreadsheet preview of the imported data with errors highlighted, allowing the user to identify and fix issues before re-importing.&lt;br /&gt;
&lt;br /&gt;
== General Form Fields ==&lt;br /&gt;
These fields are shared across both Accommodation and Flight order types.&lt;br /&gt;
&lt;br /&gt;
=== Order Name * ===&lt;br /&gt;
The title of the order.&lt;br /&gt;
&lt;br /&gt;
This is used:&lt;br /&gt;
&lt;br /&gt;
- In the sidebar list&lt;br /&gt;
&lt;br /&gt;
- As the PDF title&lt;br /&gt;
&lt;br /&gt;
- To help identify booking requests&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
- &amp;quot;Trip to Milan&amp;quot;&lt;br /&gt;
&lt;br /&gt;
- &amp;quot;Barcelona Conference Accommodation&amp;quot;&lt;br /&gt;
&lt;br /&gt;
- &amp;quot;London Team Flight Bookings&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Contact Name ===&lt;br /&gt;
The primary contact person responsible for the booking request. Typically pre-filled using the current user profile.&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Phone Number ===&lt;br /&gt;
The primary contact phone number for suppliers to use when responding to the request.&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Contact Email ===&lt;br /&gt;
The main email address suppliers should use for communication. Usually pre-filled from the logged-in user profile.&lt;br /&gt;
&lt;br /&gt;
=== Additional Emails ===&lt;br /&gt;
Optional comma-separated email addresses that should also receive communications or copies of the generated PDF.&lt;br /&gt;
&lt;br /&gt;
Example: &amp;lt;code&amp;gt;ops@company.com, travel@company.com&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Event Location ===&lt;br /&gt;
The destination, venue, or event location related to the booking request. Uses an interactive map address selector.&lt;br /&gt;
&lt;br /&gt;
=== Stay Dates * ===&lt;br /&gt;
The date range for the booking. Typically pre-filled from the itinerary dates.&lt;br /&gt;
&lt;br /&gt;
=== Response Due Date ===&lt;br /&gt;
The deadline by which suppliers or agents should respond to the request.&lt;br /&gt;
&lt;br /&gt;
=== Additional Information for Agent ===&lt;br /&gt;
Free-text notes intended for suppliers or booking agents. Character limit of 1024 with a remaining character counter.&lt;br /&gt;
&lt;br /&gt;
This content is included in the generated PDF. The field is pre-populated with a template based on the order type:&lt;br /&gt;
&lt;br /&gt;
==== Accommodation template ====&lt;br /&gt;
&lt;br /&gt;
- Desired room type&lt;br /&gt;
&lt;br /&gt;
- Required services (wifi, parking, breakfast etc)&lt;br /&gt;
&lt;br /&gt;
- Additional requests&lt;br /&gt;
&lt;br /&gt;
==== Flight template ====&lt;br /&gt;
&lt;br /&gt;
- Special meal requirements&lt;br /&gt;
&lt;br /&gt;
- Seat preferences&lt;br /&gt;
&lt;br /&gt;
- Additional requests&lt;br /&gt;
&lt;br /&gt;
=== Team Internal Comments ===&lt;br /&gt;
Internal-only notes visible to EventR users. Intended for operational or planning purposes and not shared with suppliers.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
- Internal approval notes&lt;br /&gt;
&lt;br /&gt;
- Supplier preferences&lt;br /&gt;
&lt;br /&gt;
- Budget discussions&lt;br /&gt;
&lt;br /&gt;
- Booking reminders&lt;br /&gt;
&lt;br /&gt;
== Accommodation-Specific Fields ==&lt;br /&gt;
&lt;br /&gt;
=== Select Pending Hotel ===&lt;br /&gt;
Selects an existing pending hotel/accommodation item from the itinerary.&lt;br /&gt;
&lt;br /&gt;
When selected:&lt;br /&gt;
&lt;br /&gt;
- Related guest information can be used&lt;br /&gt;
&lt;br /&gt;
- Room counts may auto-populate based on assigned guests&lt;br /&gt;
&lt;br /&gt;
- Guest data can be included in the generated PDF&lt;br /&gt;
&lt;br /&gt;
# Only hotels currently marked as &#039;&#039;&#039;Pending&#039;&#039;&#039; are available.&lt;br /&gt;
&lt;br /&gt;
=== Number of Rooms Required ===&lt;br /&gt;
The total number of rooms required for the stay. May automatically populate based on the selected hotel&#039;s guest assignments, but can also be edited manually.&lt;br /&gt;
&lt;br /&gt;
=== Maximum Number of Hotels to Split \* ===&lt;br /&gt;
Defines how many separate hotels the booking can be split across. Options: 1, 2, 3, or 4.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
- &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; = all guests must stay in the same hotel&lt;br /&gt;
- &amp;lt;code&amp;gt;2&amp;lt;/code&amp;gt; = guests may be split between two hotels&lt;br /&gt;
&lt;br /&gt;
=== Maximum Distance from Event ===&lt;br /&gt;
Optional distance limit between the accommodation and the event location.&lt;br /&gt;
&lt;br /&gt;
# Examples: &amp;quot;5km&amp;quot;, &amp;quot;15 minute walk&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== Minimum Cost per Night per Room ===&lt;br /&gt;
Optional minimum nightly room budget. Useful when requesting accommodation within a preferred pricing range.&lt;br /&gt;
&lt;br /&gt;
=== Maximum Cost per Night per Room ===&lt;br /&gt;
Optional maximum nightly room budget. Helps suppliers avoid quoting accommodation outside budget requirements.&lt;br /&gt;
&lt;br /&gt;
== Flight-Specific Fields ==&lt;br /&gt;
&lt;br /&gt;
=== Select Pending Flight ===&lt;br /&gt;
Selects an existing pending flight from the itinerary.&lt;br /&gt;
&lt;br /&gt;
When selected, the form is automatically pre-populated with:&lt;br /&gt;
&lt;br /&gt;
- Flight number/booking reference&lt;br /&gt;
&lt;br /&gt;
- Airline name &lt;br /&gt;
&lt;br /&gt;
- Departure airport&lt;br /&gt;
&lt;br /&gt;
- Arrival airport&lt;br /&gt;
&lt;br /&gt;
- Departure date and time&lt;br /&gt;
&lt;br /&gt;
- Arrival date and time&lt;br /&gt;
&lt;br /&gt;
- Number of passengers&lt;br /&gt;
&lt;br /&gt;
Only flights currently marked as &#039;&#039;&#039;Pending&#039;&#039;&#039; are available.&lt;br /&gt;
&lt;br /&gt;
=== Flight Number ===&lt;br /&gt;
The flight booking reference number. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Airline ===&lt;br /&gt;
The airline operating the flight. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Number of Passengers ===&lt;br /&gt;
The total number of passengers for the flight. May automatically populate based on the selected flight&#039;s passenger list, but can also be edited manually.&lt;br /&gt;
&lt;br /&gt;
=== Cabin Class ===&lt;br /&gt;
The requested cabin class for the flight. Options:&lt;br /&gt;
&lt;br /&gt;
- Economy&lt;br /&gt;
&lt;br /&gt;
- Premium Economy&lt;br /&gt;
&lt;br /&gt;
- Business&lt;br /&gt;
&lt;br /&gt;
- First&lt;br /&gt;
&lt;br /&gt;
=== Departure Airport ===&lt;br /&gt;
The departure airport for the flight. Uses an interactive airport selector with search functionality. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Arrival Airport ===&lt;br /&gt;
The arrival airport for the flight. Uses an interactive airport selector with search functionality. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Departure Date ===&lt;br /&gt;
The departure date and time for the flight. Uses a date/time picker with warning indicators for dates outside the event range. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Arrival Date ===&lt;br /&gt;
The arrival date and time for the flight. Uses a date/time picker with warning indicators for dates outside the event range. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
== Draft Handling ==&lt;br /&gt;
Orders support unsaved drafts.&lt;br /&gt;
&lt;br /&gt;
If the user attempts to:&lt;br /&gt;
&lt;br /&gt;
- Close the modal&lt;br /&gt;
&lt;br /&gt;
- Switch orders&lt;br /&gt;
&lt;br /&gt;
- Refresh data&lt;br /&gt;
&lt;br /&gt;
- Create a new draft&lt;br /&gt;
&lt;br /&gt;
- Change the order type (while in unsaved draft mode)&lt;br /&gt;
&lt;br /&gt;
while unsaved changes exist, EventR will prompt the user to:&lt;br /&gt;
&lt;br /&gt;
- Save changes&lt;br /&gt;
&lt;br /&gt;
- Discard changes&lt;br /&gt;
&lt;br /&gt;
This helps prevent accidental data loss.&lt;br /&gt;
| style=&amp;quot;width:40%; vertical-align:top;&amp;quot; |&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.49.46.png|thumb|Example: Draft order]]&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.58.44.png|thumb|Multiple orders view with type tags]]&lt;br /&gt;
|}&lt;br /&gt;
[[Category:3.4.1]]&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=Orders&amp;diff=1385</id>
		<title>Orders</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=Orders&amp;diff=1385"/>
		<updated>2026-08-04T10:05:30Z</updated>

		<summary type="html">&lt;p&gt;Samh: /* Order Name \* */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Infobox Feature&lt;br /&gt;
 | name = Orders&lt;br /&gt;
 | version = [[Release 3.4.1|3.4.1]] (BETA)&lt;br /&gt;
 | tier = Standard, Premium and Enterprise&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
= Overview =&lt;br /&gt;
The &#039;&#039;&#039;Orders&#039;&#039;&#039; feature allows users to create, manage, save, and generate request documents for both &#039;&#039;&#039;Accommodation&#039;&#039;&#039; and &#039;&#039;&#039;Flight&#039;&#039;&#039; bookings. It acts as a central workspace for collecting booking requirements, guest preferences, and order details related to an itinerary. Users can generate PDFs for sharing with suppliers, export order data to spreadsheets, and import existing booking data from exported files.&lt;br /&gt;
&lt;br /&gt;
= Accessing Orders =&lt;br /&gt;
{| style=&amp;quot;width:100%; margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width:60%; vertical-align:top;&amp;quot; |&lt;br /&gt;
To find the Orders functionality, select &#039;&#039;&#039;Create Order&#039;&#039;&#039; from the itinerary section in the ECH. This opens the Orders workspace in a full-screen modal.&lt;br /&gt;
&lt;br /&gt;
On opening, users can select the type of order to create using the &#039;&#039;&#039;Order Type&#039;&#039;&#039; dropdown in the top bar:&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Accommodation&#039;&#039;&#039; - For hotel and accommodation requests&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Flight&#039;&#039;&#039; - For flight booking requests&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:40%; vertical-align:top;&amp;quot; |&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.21.54.png|thumb| When you have no existing orders, button is located bottom centre.]]&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.38.33.png|thumb|Button moves into the header when you have existing orders.]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
= Managing Orders =&lt;br /&gt;
{| style=&amp;quot;width:100%; margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width:60%; vertical-align:top;&amp;quot; |New orders begin as unsaved drafts until they are saved.&lt;br /&gt;
When creating a new order, the form is automatically pre-filled using information from the selected itinerary, including dates, location, and lead booker details where available. The agent notes field is pre-populated with a template relevant to the selected order type.&lt;br /&gt;
&lt;br /&gt;
=== Layout Overview ===&lt;br /&gt;
The Orders workspace is divided into four main sections:&lt;br /&gt;
&lt;br /&gt;
- Top Bar&lt;br /&gt;
&lt;br /&gt;
- Sidebar&lt;br /&gt;
&lt;br /&gt;
- Main Form&lt;br /&gt;
&lt;br /&gt;
- Bottom Bar&lt;br /&gt;
&lt;br /&gt;
== Top Bar ==&lt;br /&gt;
&lt;br /&gt;
=== Order Type Selector ===&lt;br /&gt;
Dropdown to select the type of order to create when clicking &amp;quot;Create New&amp;quot;:&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Accommodation&#039;&#039;&#039; - Hotel and accommodation booking requests&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Flight&#039;&#039;&#039; - Flight booking requests&lt;br /&gt;
&lt;br /&gt;
Changing the selector does not affect the currently open order. The selected type applies to the next new order created.&lt;br /&gt;
&lt;br /&gt;
=== Reset ===&lt;br /&gt;
Restores the currently selected order back to its last saved state.&lt;br /&gt;
&lt;br /&gt;
If editing a new unsaved draft, the form will revert to its original pre-filled itinerary values.&lt;br /&gt;
&lt;br /&gt;
=== Create New ===&lt;br /&gt;
Creates a new unsaved order draft of the type selected in the Order Type dropdown, while keeping the current modal open.&lt;br /&gt;
&lt;br /&gt;
If unsaved changes exist, the user will be prompted to save or discard them before continuing.&lt;br /&gt;
&lt;br /&gt;
The new order is automatically given a unique title based on the itinerary name.&lt;br /&gt;
&lt;br /&gt;
=== Close ===&lt;br /&gt;
Closes the Orders modal.&lt;br /&gt;
&lt;br /&gt;
If there are unsaved changes, the user will be prompted to save or discard the draft before closing.&lt;br /&gt;
&lt;br /&gt;
== Sidebar ==&lt;br /&gt;
The sidebar contains all saved orders (both Accommodation and Flight) for the currently selected itinerary.&lt;br /&gt;
&lt;br /&gt;
=== Search ===&lt;br /&gt;
Filters saved orders by title.&lt;br /&gt;
&lt;br /&gt;
=== Refresh ===&lt;br /&gt;
Reloads the latest orders from the server without closing the modal.&lt;br /&gt;
&lt;br /&gt;
=== Order Entries ===&lt;br /&gt;
Displays all saved orders ordered by most recently updated first.&lt;br /&gt;
&lt;br /&gt;
Each entry displays:&lt;br /&gt;
&lt;br /&gt;
- Order title&lt;br /&gt;
&lt;br /&gt;
- Order type tag (&#039;&#039;&#039;Accommodation&#039;&#039;&#039; or &#039;&#039;&#039;Flight&#039;&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
- Last modified date and time&lt;br /&gt;
&lt;br /&gt;
Selecting a different order will load its saved data into the form and automatically switch the form to the correct type.&lt;br /&gt;
&lt;br /&gt;
If unsaved changes exist, the user will be prompted to save or discard them before switching.&lt;br /&gt;
&lt;br /&gt;
When no order is selected, the sidebar shows a &#039;&#039;&#039;Draft&#039;&#039;&#039; entry indicating an unsaved draft is being edited.&lt;br /&gt;
&lt;br /&gt;
== Bottom Bar ==&lt;br /&gt;
&lt;br /&gt;
=== Save ===&lt;br /&gt;
Saves the current order.&lt;br /&gt;
&lt;br /&gt;
Once saved:&lt;br /&gt;
&lt;br /&gt;
- The order becomes persistent&lt;br /&gt;
&lt;br /&gt;
- It appears in the sidebar with the appropriate type tag&lt;br /&gt;
&lt;br /&gt;
- Future edits can be restored using Reset&lt;br /&gt;
&lt;br /&gt;
=== Delete / Discard Draft ===&lt;br /&gt;
Deletes the currently selected saved order. This action cannot be undone and requires confirmation.&lt;br /&gt;
&lt;br /&gt;
If working on an unsaved draft, this button instead discards the draft and requires confirmation.&lt;br /&gt;
&lt;br /&gt;
=== Generate PDF ===&lt;br /&gt;
Generates a PDF version of the current order using all entered form data. The PDF format adapts to the order type:&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Accommodation PDF&#039;&#039;&#039; - Includes hotel details, guest rooming assignments, check-in/check-out times, and contact information. Designed for sharing with hotels, accommodation providers, or booking agents.&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Flight PDF&#039;&#039;&#039; - Includes flight details, passenger list, airline information, departure and arrival details, and special requests. Designed for sharing with airlines, flight providers, or booking agents.&lt;br /&gt;
&lt;br /&gt;
=== Export Format ===&lt;br /&gt;
Optional dropdown to select the export file format:&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;XLSX&#039;&#039;&#039; (default)&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;CSV&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=== Export ===&lt;br /&gt;
Generates a downloadable spreadsheet of the current order&#039;s details. The exported file format adapts to the order type:&lt;br /&gt;
&lt;br /&gt;
==== Accommodation Export ====&lt;br /&gt;
Includes:&lt;br /&gt;
&lt;br /&gt;
- Team Name, Itinerary Name, Order Name&lt;br /&gt;
&lt;br /&gt;
- Selected Hotel details (Name, Address, Check-In/Out Times, Telephone)&lt;br /&gt;
&lt;br /&gt;
- Guest table with: Guest Names, Check-In Date/Time, Check-Out Date/Time, Room Type, Booking Reference&lt;br /&gt;
&lt;br /&gt;
==== Flight Export ====&lt;br /&gt;
Includes:&lt;br /&gt;
&lt;br /&gt;
- Team Name, Itinerary Name, Order Name&lt;br /&gt;
&lt;br /&gt;
- Flight details (Airline, Cabin Class, Flight Number, Departure Date/Time &amp;amp; Airport, Arrival Date/Time &amp;amp; Airport)&lt;br /&gt;
&lt;br /&gt;
- Passenger table with: Passenger Names, Booking Reference&lt;br /&gt;
&lt;br /&gt;
=== Import ===&lt;br /&gt;
Imports order data from a previously exported XLSX or CSV file. The system automatically detects whether the file contains Accommodation or Flight data and populates the corresponding form.&lt;br /&gt;
&lt;br /&gt;
==== Accommodation Import ====&lt;br /&gt;
Imports hotel details, guest room assignments, check-in/check-out dates, room types, and booking references. Creates a new hotel in the itinerary and associates it with the imported order. Validates guest names against known users, date formats, and room date logic.&lt;br /&gt;
&lt;br /&gt;
==== Flight Import ====&lt;br /&gt;
Imports flight details including airline, cabin class, flight number, departure/arrival airports and dates, and passenger list. Creates a new flight in the itinerary and associates it with the imported order. Validates passenger names against known users, airport codes, date formats, and cabin class values.&lt;br /&gt;
&lt;br /&gt;
If validation errors are found during import, they are displayed in a dialog showing a spreadsheet preview of the imported data with errors highlighted, allowing the user to identify and fix issues before re-importing.&lt;br /&gt;
&lt;br /&gt;
== General Form Fields ==&lt;br /&gt;
These fields are shared across both Accommodation and Flight order types.&lt;br /&gt;
&lt;br /&gt;
=== Order Name * ===&lt;br /&gt;
The title of the order.&lt;br /&gt;
&lt;br /&gt;
This is used:&lt;br /&gt;
&lt;br /&gt;
- In the sidebar list&lt;br /&gt;
&lt;br /&gt;
- As the PDF title&lt;br /&gt;
&lt;br /&gt;
- To help identify booking requests&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
- &amp;quot;Trip to Milan&amp;quot;&lt;br /&gt;
&lt;br /&gt;
- &amp;quot;Barcelona Conference Accommodation&amp;quot;&lt;br /&gt;
&lt;br /&gt;
- &amp;quot;London Team Flight Bookings&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Contact Name ===&lt;br /&gt;
The primary contact person responsible for the booking request. Typically pre-filled using the current user profile.&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Phone Number ===&lt;br /&gt;
The primary contact phone number for suppliers to use when responding to the request.&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Contact Email ===&lt;br /&gt;
The main email address suppliers should use for communication. Usually pre-filled from the logged-in user profile.&lt;br /&gt;
&lt;br /&gt;
=== Additional Emails ===&lt;br /&gt;
Optional comma-separated email addresses that should also receive communications or copies of the generated PDF.&lt;br /&gt;
&lt;br /&gt;
Example: &amp;lt;code&amp;gt;ops@company.com, travel@company.com&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Event Location ===&lt;br /&gt;
The destination, venue, or event location related to the booking request. Uses an interactive map address selector.&lt;br /&gt;
&lt;br /&gt;
=== Stay Dates * ===&lt;br /&gt;
The date range for the booking. Typically pre-filled from the itinerary dates.&lt;br /&gt;
&lt;br /&gt;
=== Response Due Date ===&lt;br /&gt;
The deadline by which suppliers or agents should respond to the request.&lt;br /&gt;
&lt;br /&gt;
=== Additional Information for Agent ===&lt;br /&gt;
Free-text notes intended for suppliers or booking agents. Character limit of 1024 with a remaining character counter.&lt;br /&gt;
&lt;br /&gt;
This content is included in the generated PDF. The field is pre-populated with a template based on the order type:&lt;br /&gt;
&lt;br /&gt;
==== Accommodation template ====&lt;br /&gt;
&lt;br /&gt;
- Desired room type&lt;br /&gt;
&lt;br /&gt;
- Required services (wifi, parking, breakfast etc)&lt;br /&gt;
&lt;br /&gt;
- Additional requests&lt;br /&gt;
&lt;br /&gt;
==== Flight template ====&lt;br /&gt;
&lt;br /&gt;
- Special meal requirements&lt;br /&gt;
&lt;br /&gt;
- Seat preferences&lt;br /&gt;
&lt;br /&gt;
- Additional requests&lt;br /&gt;
&lt;br /&gt;
=== Team Internal Comments ===&lt;br /&gt;
Internal-only notes visible to EventR users. Intended for operational or planning purposes and not shared with suppliers.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
- Internal approval notes&lt;br /&gt;
&lt;br /&gt;
- Supplier preferences&lt;br /&gt;
&lt;br /&gt;
- Budget discussions&lt;br /&gt;
&lt;br /&gt;
- Booking reminders&lt;br /&gt;
&lt;br /&gt;
== Accommodation-Specific Fields ==&lt;br /&gt;
&lt;br /&gt;
=== Select Pending Hotel ===&lt;br /&gt;
Selects an existing pending hotel/accommodation item from the itinerary.&lt;br /&gt;
&lt;br /&gt;
When selected:&lt;br /&gt;
&lt;br /&gt;
- Related guest information can be used&lt;br /&gt;
&lt;br /&gt;
- Room counts may auto-populate based on assigned guests&lt;br /&gt;
&lt;br /&gt;
- Guest data can be included in the generated PDF&lt;br /&gt;
&lt;br /&gt;
# Only hotels currently marked as &#039;&#039;&#039;Pending&#039;&#039;&#039; are available.&lt;br /&gt;
&lt;br /&gt;
=== Number of Rooms Required ===&lt;br /&gt;
The total number of rooms required for the stay. May automatically populate based on the selected hotel&#039;s guest assignments, but can also be edited manually.&lt;br /&gt;
&lt;br /&gt;
=== Maximum Number of Hotels to Split \* ===&lt;br /&gt;
Defines how many separate hotels the booking can be split across. Options: 1, 2, 3, or 4.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
- &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; = all guests must stay in the same hotel&lt;br /&gt;
- &amp;lt;code&amp;gt;2&amp;lt;/code&amp;gt; = guests may be split between two hotels&lt;br /&gt;
&lt;br /&gt;
=== Maximum Distance from Event ===&lt;br /&gt;
Optional distance limit between the accommodation and the event location.&lt;br /&gt;
&lt;br /&gt;
# Examples: &amp;quot;5km&amp;quot;, &amp;quot;15 minute walk&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== Minimum Cost per Night per Room ===&lt;br /&gt;
Optional minimum nightly room budget. Useful when requesting accommodation within a preferred pricing range.&lt;br /&gt;
&lt;br /&gt;
=== Maximum Cost per Night per Room ===&lt;br /&gt;
Optional maximum nightly room budget. Helps suppliers avoid quoting accommodation outside budget requirements.&lt;br /&gt;
&lt;br /&gt;
== Flight-Specific Fields ==&lt;br /&gt;
&lt;br /&gt;
=== Select Pending Flight ===&lt;br /&gt;
Selects an existing pending flight from the itinerary.&lt;br /&gt;
&lt;br /&gt;
When selected, the form is automatically pre-populated with:&lt;br /&gt;
&lt;br /&gt;
- Flight number/booking reference&lt;br /&gt;
&lt;br /&gt;
- Airline name &lt;br /&gt;
&lt;br /&gt;
- Departure airport&lt;br /&gt;
&lt;br /&gt;
- Arrival airport&lt;br /&gt;
&lt;br /&gt;
- Departure date and time&lt;br /&gt;
&lt;br /&gt;
- Arrival date and time&lt;br /&gt;
&lt;br /&gt;
- Number of passengers&lt;br /&gt;
&lt;br /&gt;
Only flights currently marked as &#039;&#039;&#039;Pending&#039;&#039;&#039; are available.&lt;br /&gt;
&lt;br /&gt;
=== Flight Number ===&lt;br /&gt;
The flight booking reference number. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Airline ===&lt;br /&gt;
The airline operating the flight. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Number of Passengers ===&lt;br /&gt;
The total number of passengers for the flight. May automatically populate based on the selected flight&#039;s passenger list, but can also be edited manually.&lt;br /&gt;
&lt;br /&gt;
=== Cabin Class ===&lt;br /&gt;
The requested cabin class for the flight. Options:&lt;br /&gt;
&lt;br /&gt;
- Economy&lt;br /&gt;
&lt;br /&gt;
- Premium Economy&lt;br /&gt;
&lt;br /&gt;
- Business&lt;br /&gt;
&lt;br /&gt;
- First&lt;br /&gt;
&lt;br /&gt;
=== Departure Airport ===&lt;br /&gt;
The departure airport for the flight. Uses an interactive airport selector with search functionality. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Arrival Airport ===&lt;br /&gt;
The arrival airport for the flight. Uses an interactive airport selector with search functionality. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Departure Date ===&lt;br /&gt;
The departure date and time for the flight. Uses a date/time picker with warning indicators for dates outside the event range. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Arrival Date ===&lt;br /&gt;
The arrival date and time for the flight. Uses a date/time picker with warning indicators for dates outside the event range. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
== Draft Handling ==&lt;br /&gt;
Orders support unsaved drafts.&lt;br /&gt;
&lt;br /&gt;
If the user attempts to:&lt;br /&gt;
&lt;br /&gt;
- Close the modal&lt;br /&gt;
&lt;br /&gt;
- Switch orders&lt;br /&gt;
&lt;br /&gt;
- Refresh data&lt;br /&gt;
&lt;br /&gt;
- Create a new draft&lt;br /&gt;
&lt;br /&gt;
- Change the order type (while in unsaved draft mode)&lt;br /&gt;
&lt;br /&gt;
while unsaved changes exist, EventR will prompt the user to:&lt;br /&gt;
&lt;br /&gt;
- Save changes&lt;br /&gt;
&lt;br /&gt;
- Discard changes&lt;br /&gt;
&lt;br /&gt;
This helps prevent accidental data loss.&lt;br /&gt;
| style=&amp;quot;width:40%; vertical-align:top;&amp;quot; |&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.49.46.png|thumb|Example: Draft order]]&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.58.44.png|thumb|Multiple orders view with type tags]]&lt;br /&gt;
|}&lt;br /&gt;
[[Category:3.4.1]]&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=Orders&amp;diff=1384</id>
		<title>Orders</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=Orders&amp;diff=1384"/>
		<updated>2026-08-04T10:04:55Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Infobox Feature&lt;br /&gt;
 | name = Orders&lt;br /&gt;
 | version = [[Release 3.4.1|3.4.1]] (BETA)&lt;br /&gt;
 | tier = Standard, Premium and Enterprise&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
= Overview =&lt;br /&gt;
The &#039;&#039;&#039;Orders&#039;&#039;&#039; feature allows users to create, manage, save, and generate request documents for both &#039;&#039;&#039;Accommodation&#039;&#039;&#039; and &#039;&#039;&#039;Flight&#039;&#039;&#039; bookings. It acts as a central workspace for collecting booking requirements, guest preferences, and order details related to an itinerary. Users can generate PDFs for sharing with suppliers, export order data to spreadsheets, and import existing booking data from exported files.&lt;br /&gt;
&lt;br /&gt;
= Accessing Orders =&lt;br /&gt;
{| style=&amp;quot;width:100%; margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width:60%; vertical-align:top;&amp;quot; |&lt;br /&gt;
To find the Orders functionality, select &#039;&#039;&#039;Create Order&#039;&#039;&#039; from the itinerary section in the ECH. This opens the Orders workspace in a full-screen modal.&lt;br /&gt;
&lt;br /&gt;
On opening, users can select the type of order to create using the &#039;&#039;&#039;Order Type&#039;&#039;&#039; dropdown in the top bar:&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Accommodation&#039;&#039;&#039; - For hotel and accommodation requests&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Flight&#039;&#039;&#039; - For flight booking requests&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:40%; vertical-align:top;&amp;quot; |&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.21.54.png|thumb| When you have no existing orders, button is located bottom centre.]]&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.38.33.png|thumb|Button moves into the header when you have existing orders.]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
= Managing Orders =&lt;br /&gt;
{| style=&amp;quot;width:100%; margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width:60%; vertical-align:top;&amp;quot; |New orders begin as unsaved drafts until they are saved.&lt;br /&gt;
When creating a new order, the form is automatically pre-filled using information from the selected itinerary, including dates, location, and lead booker details where available. The agent notes field is pre-populated with a template relevant to the selected order type.&lt;br /&gt;
&lt;br /&gt;
=== Layout Overview ===&lt;br /&gt;
The Orders workspace is divided into four main sections:&lt;br /&gt;
&lt;br /&gt;
- Top Bar&lt;br /&gt;
&lt;br /&gt;
- Sidebar&lt;br /&gt;
&lt;br /&gt;
- Main Form&lt;br /&gt;
&lt;br /&gt;
- Bottom Bar&lt;br /&gt;
&lt;br /&gt;
== Top Bar ==&lt;br /&gt;
&lt;br /&gt;
=== Order Type Selector ===&lt;br /&gt;
Dropdown to select the type of order to create when clicking &amp;quot;Create New&amp;quot;:&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Accommodation&#039;&#039;&#039; - Hotel and accommodation booking requests&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Flight&#039;&#039;&#039; - Flight booking requests&lt;br /&gt;
&lt;br /&gt;
Changing the selector does not affect the currently open order. The selected type applies to the next new order created.&lt;br /&gt;
&lt;br /&gt;
=== Reset ===&lt;br /&gt;
Restores the currently selected order back to its last saved state.&lt;br /&gt;
&lt;br /&gt;
If editing a new unsaved draft, the form will revert to its original pre-filled itinerary values.&lt;br /&gt;
&lt;br /&gt;
=== Create New ===&lt;br /&gt;
Creates a new unsaved order draft of the type selected in the Order Type dropdown, while keeping the current modal open.&lt;br /&gt;
&lt;br /&gt;
If unsaved changes exist, the user will be prompted to save or discard them before continuing.&lt;br /&gt;
&lt;br /&gt;
The new order is automatically given a unique title based on the itinerary name.&lt;br /&gt;
&lt;br /&gt;
=== Close ===&lt;br /&gt;
Closes the Orders modal.&lt;br /&gt;
&lt;br /&gt;
If there are unsaved changes, the user will be prompted to save or discard the draft before closing.&lt;br /&gt;
&lt;br /&gt;
== Sidebar ==&lt;br /&gt;
The sidebar contains all saved orders (both Accommodation and Flight) for the currently selected itinerary.&lt;br /&gt;
&lt;br /&gt;
=== Search ===&lt;br /&gt;
Filters saved orders by title.&lt;br /&gt;
&lt;br /&gt;
=== Refresh ===&lt;br /&gt;
Reloads the latest orders from the server without closing the modal.&lt;br /&gt;
&lt;br /&gt;
=== Order Entries ===&lt;br /&gt;
Displays all saved orders ordered by most recently updated first.&lt;br /&gt;
&lt;br /&gt;
Each entry displays:&lt;br /&gt;
&lt;br /&gt;
- Order title&lt;br /&gt;
&lt;br /&gt;
- Order type tag (&#039;&#039;&#039;Accommodation&#039;&#039;&#039; or &#039;&#039;&#039;Flight&#039;&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
- Last modified date and time&lt;br /&gt;
&lt;br /&gt;
Selecting a different order will load its saved data into the form and automatically switch the form to the correct type.&lt;br /&gt;
&lt;br /&gt;
If unsaved changes exist, the user will be prompted to save or discard them before switching.&lt;br /&gt;
&lt;br /&gt;
When no order is selected, the sidebar shows a &#039;&#039;&#039;Draft&#039;&#039;&#039; entry indicating an unsaved draft is being edited.&lt;br /&gt;
&lt;br /&gt;
== Bottom Bar ==&lt;br /&gt;
&lt;br /&gt;
=== Save ===&lt;br /&gt;
Saves the current order.&lt;br /&gt;
&lt;br /&gt;
Once saved:&lt;br /&gt;
&lt;br /&gt;
- The order becomes persistent&lt;br /&gt;
&lt;br /&gt;
- It appears in the sidebar with the appropriate type tag&lt;br /&gt;
&lt;br /&gt;
- Future edits can be restored using Reset&lt;br /&gt;
&lt;br /&gt;
=== Delete / Discard Draft ===&lt;br /&gt;
Deletes the currently selected saved order. This action cannot be undone and requires confirmation.&lt;br /&gt;
&lt;br /&gt;
If working on an unsaved draft, this button instead discards the draft and requires confirmation.&lt;br /&gt;
&lt;br /&gt;
=== Generate PDF ===&lt;br /&gt;
Generates a PDF version of the current order using all entered form data. The PDF format adapts to the order type:&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Accommodation PDF&#039;&#039;&#039; - Includes hotel details, guest rooming assignments, check-in/check-out times, and contact information. Designed for sharing with hotels, accommodation providers, or booking agents.&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Flight PDF&#039;&#039;&#039; - Includes flight details, passenger list, airline information, departure and arrival details, and special requests. Designed for sharing with airlines, flight providers, or booking agents.&lt;br /&gt;
&lt;br /&gt;
=== Export Format ===&lt;br /&gt;
Optional dropdown to select the export file format:&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;XLSX&#039;&#039;&#039; (default)&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;CSV&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=== Export ===&lt;br /&gt;
Generates a downloadable spreadsheet of the current order&#039;s details. The exported file format adapts to the order type:&lt;br /&gt;
&lt;br /&gt;
==== Accommodation Export ====&lt;br /&gt;
Includes:&lt;br /&gt;
&lt;br /&gt;
- Team Name, Itinerary Name, Order Name&lt;br /&gt;
&lt;br /&gt;
- Selected Hotel details (Name, Address, Check-In/Out Times, Telephone)&lt;br /&gt;
&lt;br /&gt;
- Guest table with: Guest Names, Check-In Date/Time, Check-Out Date/Time, Room Type, Booking Reference&lt;br /&gt;
&lt;br /&gt;
==== Flight Export ====&lt;br /&gt;
Includes:&lt;br /&gt;
&lt;br /&gt;
- Team Name, Itinerary Name, Order Name&lt;br /&gt;
&lt;br /&gt;
- Flight details (Airline, Cabin Class, Flight Number, Departure Date/Time &amp;amp; Airport, Arrival Date/Time &amp;amp; Airport)&lt;br /&gt;
&lt;br /&gt;
- Passenger table with: Passenger Names, Booking Reference&lt;br /&gt;
&lt;br /&gt;
=== Import ===&lt;br /&gt;
Imports order data from a previously exported XLSX or CSV file. The system automatically detects whether the file contains Accommodation or Flight data and populates the corresponding form.&lt;br /&gt;
&lt;br /&gt;
==== Accommodation Import ====&lt;br /&gt;
Imports hotel details, guest room assignments, check-in/check-out dates, room types, and booking references. Creates a new hotel in the itinerary and associates it with the imported order. Validates guest names against known users, date formats, and room date logic.&lt;br /&gt;
&lt;br /&gt;
==== Flight Import ====&lt;br /&gt;
Imports flight details including airline, cabin class, flight number, departure/arrival airports and dates, and passenger list. Creates a new flight in the itinerary and associates it with the imported order. Validates passenger names against known users, airport codes, date formats, and cabin class values.&lt;br /&gt;
&lt;br /&gt;
If validation errors are found during import, they are displayed in a dialog showing a spreadsheet preview of the imported data with errors highlighted, allowing the user to identify and fix issues before re-importing.&lt;br /&gt;
&lt;br /&gt;
== General Form Fields ==&lt;br /&gt;
These fields are shared across both Accommodation and Flight order types.&lt;br /&gt;
&lt;br /&gt;
=== Order Name \* ===&lt;br /&gt;
The title of the order.&lt;br /&gt;
&lt;br /&gt;
This is used:&lt;br /&gt;
&lt;br /&gt;
- In the sidebar list&lt;br /&gt;
&lt;br /&gt;
- As the PDF title&lt;br /&gt;
&lt;br /&gt;
- To help identify booking requests&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
- &amp;quot;Trip to Milan&amp;quot;&lt;br /&gt;
&lt;br /&gt;
- &amp;quot;Barcelona Conference Accommodation&amp;quot;&lt;br /&gt;
&lt;br /&gt;
- &amp;quot;London Team Flight Bookings&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Contact Name ===&lt;br /&gt;
The primary contact person responsible for the booking request. Typically pre-filled using the current user profile.&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Phone Number ===&lt;br /&gt;
The primary contact phone number for suppliers to use when responding to the request.&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Contact Email ===&lt;br /&gt;
The main email address suppliers should use for communication. Usually pre-filled from the logged-in user profile.&lt;br /&gt;
&lt;br /&gt;
=== Additional Emails ===&lt;br /&gt;
Optional comma-separated email addresses that should also receive communications or copies of the generated PDF.&lt;br /&gt;
&lt;br /&gt;
Example: &amp;lt;code&amp;gt;ops@company.com, travel@company.com&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Event Location ===&lt;br /&gt;
The destination, venue, or event location related to the booking request. Uses an interactive map address selector.&lt;br /&gt;
&lt;br /&gt;
=== Stay Dates \* ===&lt;br /&gt;
The date range for the booking. Typically pre-filled from the itinerary dates.&lt;br /&gt;
&lt;br /&gt;
=== Response Due Date ===&lt;br /&gt;
The deadline by which suppliers or agents should respond to the request.&lt;br /&gt;
&lt;br /&gt;
=== Additional Information for Agent ===&lt;br /&gt;
Free-text notes intended for suppliers or booking agents. Character limit of 1024 with a remaining character counter.&lt;br /&gt;
&lt;br /&gt;
This content is included in the generated PDF. The field is pre-populated with a template based on the order type:&lt;br /&gt;
&lt;br /&gt;
==== Accommodation template ====&lt;br /&gt;
&lt;br /&gt;
- Desired room type&lt;br /&gt;
&lt;br /&gt;
- Required services (wifi, parking, breakfast etc)&lt;br /&gt;
&lt;br /&gt;
- Additional requests&lt;br /&gt;
&lt;br /&gt;
==== Flight template ====&lt;br /&gt;
&lt;br /&gt;
- Special meal requirements&lt;br /&gt;
&lt;br /&gt;
- Seat preferences&lt;br /&gt;
&lt;br /&gt;
- Additional requests&lt;br /&gt;
&lt;br /&gt;
=== Team Internal Comments ===&lt;br /&gt;
Internal-only notes visible to EventR users. Intended for operational or planning purposes and not shared with suppliers.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
- Internal approval notes&lt;br /&gt;
&lt;br /&gt;
- Supplier preferences&lt;br /&gt;
&lt;br /&gt;
- Budget discussions&lt;br /&gt;
&lt;br /&gt;
- Booking reminders&lt;br /&gt;
&lt;br /&gt;
== Accommodation-Specific Fields ==&lt;br /&gt;
&lt;br /&gt;
=== Select Pending Hotel ===&lt;br /&gt;
Selects an existing pending hotel/accommodation item from the itinerary.&lt;br /&gt;
&lt;br /&gt;
When selected:&lt;br /&gt;
&lt;br /&gt;
- Related guest information can be used&lt;br /&gt;
&lt;br /&gt;
- Room counts may auto-populate based on assigned guests&lt;br /&gt;
&lt;br /&gt;
- Guest data can be included in the generated PDF&lt;br /&gt;
&lt;br /&gt;
# Only hotels currently marked as &#039;&#039;&#039;Pending&#039;&#039;&#039; are available.&lt;br /&gt;
&lt;br /&gt;
=== Number of Rooms Required ===&lt;br /&gt;
The total number of rooms required for the stay. May automatically populate based on the selected hotel&#039;s guest assignments, but can also be edited manually.&lt;br /&gt;
&lt;br /&gt;
=== Maximum Number of Hotels to Split \* ===&lt;br /&gt;
Defines how many separate hotels the booking can be split across. Options: 1, 2, 3, or 4.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
- &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; = all guests must stay in the same hotel&lt;br /&gt;
- &amp;lt;code&amp;gt;2&amp;lt;/code&amp;gt; = guests may be split between two hotels&lt;br /&gt;
&lt;br /&gt;
=== Maximum Distance from Event ===&lt;br /&gt;
Optional distance limit between the accommodation and the event location.&lt;br /&gt;
&lt;br /&gt;
# Examples: &amp;quot;5km&amp;quot;, &amp;quot;15 minute walk&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== Minimum Cost per Night per Room ===&lt;br /&gt;
Optional minimum nightly room budget. Useful when requesting accommodation within a preferred pricing range.&lt;br /&gt;
&lt;br /&gt;
=== Maximum Cost per Night per Room ===&lt;br /&gt;
Optional maximum nightly room budget. Helps suppliers avoid quoting accommodation outside budget requirements.&lt;br /&gt;
&lt;br /&gt;
== Flight-Specific Fields ==&lt;br /&gt;
&lt;br /&gt;
=== Select Pending Flight ===&lt;br /&gt;
Selects an existing pending flight from the itinerary.&lt;br /&gt;
&lt;br /&gt;
When selected, the form is automatically pre-populated with:&lt;br /&gt;
&lt;br /&gt;
- Flight number/booking reference&lt;br /&gt;
&lt;br /&gt;
- Airline name &lt;br /&gt;
&lt;br /&gt;
- Departure airport&lt;br /&gt;
&lt;br /&gt;
- Arrival airport&lt;br /&gt;
&lt;br /&gt;
- Departure date and time&lt;br /&gt;
&lt;br /&gt;
- Arrival date and time&lt;br /&gt;
&lt;br /&gt;
- Number of passengers&lt;br /&gt;
&lt;br /&gt;
Only flights currently marked as &#039;&#039;&#039;Pending&#039;&#039;&#039; are available.&lt;br /&gt;
&lt;br /&gt;
=== Flight Number ===&lt;br /&gt;
The flight booking reference number. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Airline ===&lt;br /&gt;
The airline operating the flight. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Number of Passengers ===&lt;br /&gt;
The total number of passengers for the flight. May automatically populate based on the selected flight&#039;s passenger list, but can also be edited manually.&lt;br /&gt;
&lt;br /&gt;
=== Cabin Class ===&lt;br /&gt;
The requested cabin class for the flight. Options:&lt;br /&gt;
&lt;br /&gt;
- Economy&lt;br /&gt;
&lt;br /&gt;
- Premium Economy&lt;br /&gt;
&lt;br /&gt;
- Business&lt;br /&gt;
&lt;br /&gt;
- First&lt;br /&gt;
&lt;br /&gt;
=== Departure Airport ===&lt;br /&gt;
The departure airport for the flight. Uses an interactive airport selector with search functionality. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Arrival Airport ===&lt;br /&gt;
The arrival airport for the flight. Uses an interactive airport selector with search functionality. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Departure Date ===&lt;br /&gt;
The departure date and time for the flight. Uses a date/time picker with warning indicators for dates outside the event range. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Arrival Date ===&lt;br /&gt;
The arrival date and time for the flight. Uses a date/time picker with warning indicators for dates outside the event range. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
== Draft Handling ==&lt;br /&gt;
Orders support unsaved drafts.&lt;br /&gt;
&lt;br /&gt;
If the user attempts to:&lt;br /&gt;
&lt;br /&gt;
- Close the modal&lt;br /&gt;
&lt;br /&gt;
- Switch orders&lt;br /&gt;
&lt;br /&gt;
- Refresh data&lt;br /&gt;
&lt;br /&gt;
- Create a new draft&lt;br /&gt;
&lt;br /&gt;
- Change the order type (while in unsaved draft mode)&lt;br /&gt;
&lt;br /&gt;
while unsaved changes exist, EventR will prompt the user to:&lt;br /&gt;
&lt;br /&gt;
- Save changes&lt;br /&gt;
&lt;br /&gt;
- Discard changes&lt;br /&gt;
&lt;br /&gt;
This helps prevent accidental data loss.&lt;br /&gt;
| style=&amp;quot;width:40%; vertical-align:top;&amp;quot; |&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.49.46.png|thumb|Example: Draft order]]&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.58.44.png|thumb|Multiple orders view with type tags]]&lt;br /&gt;
|}&lt;br /&gt;
[[Category:3.4.1]]&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=Orders&amp;diff=1383</id>
		<title>Orders</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=Orders&amp;diff=1383"/>
		<updated>2026-08-04T10:02:42Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Infobox Feature&lt;br /&gt;
 | name = Orders&lt;br /&gt;
 | version = [[Release 3.4.1|3.4.1]] (BETA)&lt;br /&gt;
 | tier = Standard, Premium and Enterprise&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
= Overview =&lt;br /&gt;
The &#039;&#039;&#039;Orders&#039;&#039;&#039; feature allows users to create, manage, save, and generate request documents for both &#039;&#039;&#039;Accommodation&#039;&#039;&#039; and &#039;&#039;&#039;Flight&#039;&#039;&#039; bookings. It acts as a central workspace for collecting booking requirements, guest preferences, and order details related to an itinerary. Users can generate PDFs for sharing with suppliers, export order data to spreadsheets, and import existing booking data from exported files.&lt;br /&gt;
&lt;br /&gt;
= Accessing Orders =&lt;br /&gt;
{| style=&amp;quot;width:100%; margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width:60%; vertical-align:top;&amp;quot; |&lt;br /&gt;
To find the Orders functionality, select &#039;&#039;&#039;Create Order&#039;&#039;&#039; from the itinerary section in the ECH. This opens the Orders workspace in a full-screen modal.&lt;br /&gt;
&lt;br /&gt;
On opening, users can select the type of order to create using the &#039;&#039;&#039;Order Type&#039;&#039;&#039; dropdown in the top bar:&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Accommodation&#039;&#039;&#039; - For hotel and accommodation requests&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Flight&#039;&#039;&#039; - For flight booking requests&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:40%; vertical-align:top;&amp;quot; |&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.21.54.png|thumb| When you have no existing orders, button is located bottom centre.]]&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.38.33.png|thumb|Button moves into the header when you have existing orders.]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
= Managing Orders =&lt;br /&gt;
{| style=&amp;quot;width:100%; margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width:60%; vertical-align:top;&amp;quot; |New orders begin as unsaved drafts until they are saved.&lt;br /&gt;
&lt;br /&gt;
# When creating a new order, the form is automatically pre-filled using information from the selected itinerary, including dates, location, and lead booker details where available. The agent notes field is pre-populated with a template relevant to the selected order type.&lt;br /&gt;
&lt;br /&gt;
=== Layout Overview ===&lt;br /&gt;
The Orders workspace is divided into four main sections:&lt;br /&gt;
&lt;br /&gt;
- Top Bar&lt;br /&gt;
&lt;br /&gt;
- Sidebar&lt;br /&gt;
&lt;br /&gt;
- Main Form&lt;br /&gt;
&lt;br /&gt;
- Bottom Bar&lt;br /&gt;
&lt;br /&gt;
== Top Bar ==&lt;br /&gt;
&lt;br /&gt;
=== Order Type Selector ===&lt;br /&gt;
Dropdown to select the type of order to create when clicking &amp;quot;Create New&amp;quot;:&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Accommodation&#039;&#039;&#039; - Hotel and accommodation booking requests&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Flight&#039;&#039;&#039; - Flight booking requests&lt;br /&gt;
&lt;br /&gt;
Changing the selector does not affect the currently open order. The selected type applies to the next new order created.&lt;br /&gt;
&lt;br /&gt;
=== Reset ===&lt;br /&gt;
Restores the currently selected order back to its last saved state.&lt;br /&gt;
&lt;br /&gt;
If editing a new unsaved draft, the form will revert to its original pre-filled itinerary values.&lt;br /&gt;
&lt;br /&gt;
=== Create New ===&lt;br /&gt;
Creates a new unsaved order draft of the type selected in the Order Type dropdown, while keeping the current modal open.&lt;br /&gt;
&lt;br /&gt;
If unsaved changes exist, the user will be prompted to save or discard them before continuing.&lt;br /&gt;
&lt;br /&gt;
The new order is automatically given a unique title based on the itinerary name.&lt;br /&gt;
&lt;br /&gt;
=== Close ===&lt;br /&gt;
Closes the Orders modal.&lt;br /&gt;
&lt;br /&gt;
# If there are unsaved changes, the user will be prompted to save or discard the draft before closing.&lt;br /&gt;
&lt;br /&gt;
== Sidebar ==&lt;br /&gt;
The sidebar contains all saved orders (both Accommodation and Flight) for the currently selected itinerary.&lt;br /&gt;
&lt;br /&gt;
=== Search ===&lt;br /&gt;
Filters saved orders by title.&lt;br /&gt;
&lt;br /&gt;
=== Refresh ===&lt;br /&gt;
Reloads the latest orders from the server without closing the modal.&lt;br /&gt;
&lt;br /&gt;
=== Order Entries ===&lt;br /&gt;
Displays all saved orders ordered by most recently updated first.&lt;br /&gt;
&lt;br /&gt;
Each entry displays:&lt;br /&gt;
&lt;br /&gt;
- Order title&lt;br /&gt;
&lt;br /&gt;
- Order type tag (&#039;&#039;&#039;Accommodation&#039;&#039;&#039; or &#039;&#039;&#039;Flight&#039;&#039;&#039;)&lt;br /&gt;
&lt;br /&gt;
- Last modified date and time&lt;br /&gt;
&lt;br /&gt;
Selecting a different order will load its saved data into the form and automatically switch the form to the correct type.&lt;br /&gt;
&lt;br /&gt;
If unsaved changes exist, the user will be prompted to save or discard them before switching.&lt;br /&gt;
&lt;br /&gt;
# When no order is selected, the sidebar shows a &#039;&#039;&#039;Draft&#039;&#039;&#039; entry indicating an unsaved draft is being edited.&lt;br /&gt;
&lt;br /&gt;
== Bottom Bar ==&lt;br /&gt;
&lt;br /&gt;
=== Save ===&lt;br /&gt;
Saves the current order.&lt;br /&gt;
&lt;br /&gt;
Once saved:&lt;br /&gt;
&lt;br /&gt;
- The order becomes persistent&lt;br /&gt;
&lt;br /&gt;
- It appears in the sidebar with the appropriate type tag&lt;br /&gt;
&lt;br /&gt;
- Future edits can be restored using Reset&lt;br /&gt;
&lt;br /&gt;
=== Delete / Discard Draft ===&lt;br /&gt;
Deletes the currently selected saved order. This action cannot be undone and requires confirmation.&lt;br /&gt;
&lt;br /&gt;
If working on an unsaved draft, this button instead discards the draft and requires confirmation.&lt;br /&gt;
&lt;br /&gt;
=== Generate PDF ===&lt;br /&gt;
Generates a PDF version of the current order using all entered form data. The PDF format adapts to the order type:&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Accommodation PDF&#039;&#039;&#039; - Includes hotel details, guest rooming assignments, check-in/check-out times, and contact information. Designed for sharing with hotels, accommodation providers, or booking agents.&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Flight PDF&#039;&#039;&#039; - Includes flight details, passenger list, airline information, departure and arrival details, and special requests. Designed for sharing with airlines, flight providers, or booking agents.&lt;br /&gt;
&lt;br /&gt;
=== Export Format ===&lt;br /&gt;
Optional dropdown to select the export file format:&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;XLSX&#039;&#039;&#039; (default)&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;CSV&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=== Export ===&lt;br /&gt;
Generates a downloadable spreadsheet of the current order&#039;s details. The exported file format adapts to the order type:&lt;br /&gt;
&lt;br /&gt;
==== Accommodation Export ====&lt;br /&gt;
Includes:&lt;br /&gt;
&lt;br /&gt;
- Team Name, Itinerary Name, Order Name&lt;br /&gt;
&lt;br /&gt;
- Selected Hotel details (Name, Address, Check-In/Out Times, Telephone)&lt;br /&gt;
&lt;br /&gt;
- Guest table with: Guest Names, Check-In Date/Time, Check-Out Date/Time, Room Type, Booking Reference&lt;br /&gt;
&lt;br /&gt;
==== Flight Export ====&lt;br /&gt;
Includes:&lt;br /&gt;
&lt;br /&gt;
- Team Name, Itinerary Name, Order Name&lt;br /&gt;
&lt;br /&gt;
- Flight details (Airline, Cabin Class, Flight Number, Departure Date/Time &amp;amp; Airport, Arrival Date/Time &amp;amp; Airport)&lt;br /&gt;
&lt;br /&gt;
- Passenger table with: Passenger Names, Booking Reference&lt;br /&gt;
&lt;br /&gt;
=== Import ===&lt;br /&gt;
Imports order data from a previously exported XLSX or CSV file. The system automatically detects whether the file contains Accommodation or Flight data and populates the corresponding form.&lt;br /&gt;
&lt;br /&gt;
==== Accommodation Import ====&lt;br /&gt;
Imports hotel details, guest room assignments, check-in/check-out dates, room types, and booking references. Creates a new hotel in the itinerary and associates it with the imported order. Validates guest names against known users, date formats, and room date logic.&lt;br /&gt;
&lt;br /&gt;
==== Flight Import ====&lt;br /&gt;
Imports flight details including airline, cabin class, flight number, departure/arrival airports and dates, and passenger list. Creates a new flight in the itinerary and associates it with the imported order. Validates passenger names against known users, airport codes, date formats, and cabin class values.&lt;br /&gt;
&lt;br /&gt;
# If validation errors are found during import, they are displayed in a dialog showing a spreadsheet preview of the imported data with errors highlighted, allowing the user to identify and fix issues before re-importing.&lt;br /&gt;
&lt;br /&gt;
== General Form Fields ==&lt;br /&gt;
These fields are shared across both Accommodation and Flight order types.&lt;br /&gt;
&lt;br /&gt;
=== Order Name \* ===&lt;br /&gt;
The title of the order.&lt;br /&gt;
&lt;br /&gt;
This is used:&lt;br /&gt;
&lt;br /&gt;
- In the sidebar list&lt;br /&gt;
&lt;br /&gt;
- As the PDF title&lt;br /&gt;
&lt;br /&gt;
- To help identify booking requests&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
- &amp;quot;Trip to Milan&amp;quot;&lt;br /&gt;
&lt;br /&gt;
- &amp;quot;Barcelona Conference Accommodation&amp;quot;&lt;br /&gt;
&lt;br /&gt;
- &amp;quot;London Team Flight Bookings&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Contact Name ===&lt;br /&gt;
The primary contact person responsible for the booking request. Typically pre-filled using the current user profile.&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Phone Number ===&lt;br /&gt;
The primary contact phone number for suppliers to use when responding to the request.&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Contact Email ===&lt;br /&gt;
The main email address suppliers should use for communication. Usually pre-filled from the logged-in user profile.&lt;br /&gt;
&lt;br /&gt;
=== Additional Emails ===&lt;br /&gt;
Optional comma-separated email addresses that should also receive communications or copies of the generated PDF.&lt;br /&gt;
&lt;br /&gt;
# Example: &amp;lt;code&amp;gt;ops@company.com, travel@company.com&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Event Location ===&lt;br /&gt;
The destination, venue, or event location related to the booking request. Uses an interactive map address selector.&lt;br /&gt;
&lt;br /&gt;
=== Stay Dates \* ===&lt;br /&gt;
The date range for the booking. Typically pre-filled from the itinerary dates.&lt;br /&gt;
&lt;br /&gt;
=== Response Due Date ===&lt;br /&gt;
The deadline by which suppliers or agents should respond to the request.&lt;br /&gt;
&lt;br /&gt;
=== Additional Information for Agent ===&lt;br /&gt;
Free-text notes intended for suppliers or booking agents. Character limit of 1024 with a remaining character counter.&lt;br /&gt;
&lt;br /&gt;
This content is included in the generated PDF. The field is pre-populated with a template based on the order type:&lt;br /&gt;
&lt;br /&gt;
==== Accommodation template ====&lt;br /&gt;
&lt;br /&gt;
- Desired room type&lt;br /&gt;
&lt;br /&gt;
- Required services (wifi, parking, breakfast etc)&lt;br /&gt;
&lt;br /&gt;
- Additional requests&lt;br /&gt;
&lt;br /&gt;
==== Flight template ====&lt;br /&gt;
&lt;br /&gt;
- Special meal requirements&lt;br /&gt;
&lt;br /&gt;
- Seat preferences&lt;br /&gt;
&lt;br /&gt;
- Additional requests&lt;br /&gt;
&lt;br /&gt;
=== Team Internal Comments ===&lt;br /&gt;
Internal-only notes visible to EventR users. Intended for operational or planning purposes and not shared with suppliers.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
- Internal approval notes&lt;br /&gt;
&lt;br /&gt;
- Supplier preferences&lt;br /&gt;
&lt;br /&gt;
- Budget discussions&lt;br /&gt;
&lt;br /&gt;
- Booking reminders&lt;br /&gt;
&lt;br /&gt;
== Accommodation-Specific Fields ==&lt;br /&gt;
&lt;br /&gt;
=== Select Pending Hotel ===&lt;br /&gt;
Selects an existing pending hotel/accommodation item from the itinerary.&lt;br /&gt;
&lt;br /&gt;
When selected:&lt;br /&gt;
&lt;br /&gt;
- Related guest information can be used&lt;br /&gt;
&lt;br /&gt;
- Room counts may auto-populate based on assigned guests&lt;br /&gt;
&lt;br /&gt;
- Guest data can be included in the generated PDF&lt;br /&gt;
&lt;br /&gt;
# Only hotels currently marked as &#039;&#039;&#039;Pending&#039;&#039;&#039; are available.&lt;br /&gt;
&lt;br /&gt;
=== Number of Rooms Required ===&lt;br /&gt;
The total number of rooms required for the stay. May automatically populate based on the selected hotel&#039;s guest assignments, but can also be edited manually.&lt;br /&gt;
&lt;br /&gt;
=== Maximum Number of Hotels to Split \* ===&lt;br /&gt;
Defines how many separate hotels the booking can be split across. Options: 1, 2, 3, or 4.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
- &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; = all guests must stay in the same hotel&lt;br /&gt;
- &amp;lt;code&amp;gt;2&amp;lt;/code&amp;gt; = guests may be split between two hotels&lt;br /&gt;
&lt;br /&gt;
=== Maximum Distance from Event ===&lt;br /&gt;
Optional distance limit between the accommodation and the event location.&lt;br /&gt;
&lt;br /&gt;
# Examples: &amp;quot;5km&amp;quot;, &amp;quot;15 minute walk&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== Minimum Cost per Night per Room ===&lt;br /&gt;
Optional minimum nightly room budget. Useful when requesting accommodation within a preferred pricing range.&lt;br /&gt;
&lt;br /&gt;
=== Maximum Cost per Night per Room ===&lt;br /&gt;
Optional maximum nightly room budget. Helps suppliers avoid quoting accommodation outside budget requirements.&lt;br /&gt;
&lt;br /&gt;
== Flight-Specific Fields ==&lt;br /&gt;
&lt;br /&gt;
=== Select Pending Flight ===&lt;br /&gt;
Selects an existing pending flight from the itinerary.&lt;br /&gt;
&lt;br /&gt;
When selected, the form is automatically pre-populated with:&lt;br /&gt;
&lt;br /&gt;
- Flight number/booking reference&lt;br /&gt;
&lt;br /&gt;
- Airline name &lt;br /&gt;
&lt;br /&gt;
- Departure airport&lt;br /&gt;
&lt;br /&gt;
- Arrival airport&lt;br /&gt;
&lt;br /&gt;
- Departure date and time&lt;br /&gt;
&lt;br /&gt;
- Arrival date and time&lt;br /&gt;
&lt;br /&gt;
- Number of passengers&lt;br /&gt;
&lt;br /&gt;
# Only flights currently marked as &#039;&#039;&#039;Pending&#039;&#039;&#039; are available.&lt;br /&gt;
&lt;br /&gt;
=== Flight Number ===&lt;br /&gt;
The flight booking reference number. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Airline ===&lt;br /&gt;
The airline operating the flight. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Number of Passengers ===&lt;br /&gt;
The total number of passengers for the flight. May automatically populate based on the selected flight&#039;s passenger list, but can also be edited manually.&lt;br /&gt;
&lt;br /&gt;
=== Cabin Class ===&lt;br /&gt;
The requested cabin class for the flight. Options:&lt;br /&gt;
&lt;br /&gt;
- Economy&lt;br /&gt;
&lt;br /&gt;
- Premium Economy&lt;br /&gt;
&lt;br /&gt;
- Business&lt;br /&gt;
&lt;br /&gt;
- First&lt;br /&gt;
&lt;br /&gt;
=== Departure Airport ===&lt;br /&gt;
The departure airport for the flight. Uses an interactive airport selector with search functionality. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Arrival Airport ===&lt;br /&gt;
The arrival airport for the flight. Uses an interactive airport selector with search functionality. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Departure Date ===&lt;br /&gt;
The departure date and time for the flight. Uses a date/time picker with warning indicators for dates outside the event range. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
=== Arrival Date ===&lt;br /&gt;
The arrival date and time for the flight. Uses a date/time picker with warning indicators for dates outside the event range. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
== Draft Handling ==&lt;br /&gt;
Orders support unsaved drafts.&lt;br /&gt;
&lt;br /&gt;
If the user attempts to:&lt;br /&gt;
&lt;br /&gt;
- Close the modal&lt;br /&gt;
&lt;br /&gt;
- Switch orders&lt;br /&gt;
&lt;br /&gt;
- Refresh data&lt;br /&gt;
&lt;br /&gt;
- Create a new draft&lt;br /&gt;
&lt;br /&gt;
- Change the order type (while in unsaved draft mode)&lt;br /&gt;
&lt;br /&gt;
while unsaved changes exist, EventR will prompt the user to:&lt;br /&gt;
&lt;br /&gt;
- Save changes&lt;br /&gt;
&lt;br /&gt;
- Discard changes&lt;br /&gt;
&lt;br /&gt;
This helps prevent accidental data loss.&lt;br /&gt;
| style=&amp;quot;width:40%; vertical-align:top;&amp;quot; |&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.49.46.png|thumb|Example: Draft order]]&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.58.44.png|thumb|Multiple orders view with type tags]]&lt;br /&gt;
|}&lt;br /&gt;
[[Category:3.4.1]]&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=Orders&amp;diff=1382</id>
		<title>Orders</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=Orders&amp;diff=1382"/>
		<updated>2026-08-04T09:57:28Z</updated>

		<summary type="html">&lt;p&gt;Samh: Include Flights&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Infobox Feature&lt;br /&gt;
 | name = Orders&lt;br /&gt;
 | version = [[Release 3.4.1|3.4.1]] (BETA)&lt;br /&gt;
 | tier = Standard, Premium and Enterprise&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
= Overview =&lt;br /&gt;
The &#039;&#039;&#039;Orders&#039;&#039;&#039; feature allows users to create, manage, save, and generate request documents for both &#039;&#039;&#039;Accommodation&#039;&#039;&#039; and &#039;&#039;&#039;Flight&#039;&#039;&#039; bookings. It acts as a central workspace for collecting booking requirements, guest preferences, and order details related to an itinerary. Users can generate PDFs for sharing with suppliers, export order data to spreadsheets, and import existing booking data from exported files.&lt;br /&gt;
&lt;br /&gt;
= Accessing Orders =&lt;br /&gt;
{| style=&amp;quot;width:100%; margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width:60%; vertical-align:top;&amp;quot; |&lt;br /&gt;
To find the Orders functionality, select &#039;&#039;&#039;Create Order&#039;&#039;&#039; from the itinerary section in the ECH. This opens the Orders workspace in a full-screen modal.&lt;br /&gt;
&lt;br /&gt;
On opening, users can select the type of order to create using the &#039;&#039;&#039;Order Type&#039;&#039;&#039; dropdown in the top bar:&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Accommodation&#039;&#039;&#039; - For hotel and accommodation requests&lt;br /&gt;
- &#039;&#039;&#039;Flight&#039;&#039;&#039; - For flight booking requests&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:40%; vertical-align:top;&amp;quot; |&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.21.54.png|thumb| When you have no existing orders, button is located bottom centre.]]&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.38.33.png|thumb|Button moves into the header when you have existing orders.]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
= Managing Orders =&lt;br /&gt;
{| style=&amp;quot;width:100%; margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width:60%; vertical-align:top;&amp;quot; |New orders begin as unsaved drafts until they are saved.&lt;br /&gt;
&lt;br /&gt;
## When creating a new order, the form is automatically pre-filled using information from the selected itinerary, including dates, location, and lead booker details where available. The agent notes field is pre-populated with a template relevant to the selected order type.&lt;br /&gt;
&lt;br /&gt;
=== Layout Overview ===&lt;br /&gt;
The Orders workspace is divided into four main sections:&lt;br /&gt;
&lt;br /&gt;
- Top Bar&lt;br /&gt;
- Sidebar&lt;br /&gt;
- Main Form&lt;br /&gt;
- Bottom Bar&lt;br /&gt;
&lt;br /&gt;
---&lt;br /&gt;
&lt;br /&gt;
== Top Bar ==&lt;br /&gt;
&lt;br /&gt;
=== Order Type Selector ===&lt;br /&gt;
Dropdown to select the type of order to create when clicking &amp;quot;Create New&amp;quot;:&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Accommodation&#039;&#039;&#039; - Hotel and accommodation booking requests&lt;br /&gt;
- &#039;&#039;&#039;Flight&#039;&#039;&#039; - Flight booking requests&lt;br /&gt;
&lt;br /&gt;
Changing the selector does not affect the currently open order. The selected type applies to the next new order created.&lt;br /&gt;
&lt;br /&gt;
=== Reset ===&lt;br /&gt;
Restores the currently selected order back to its last saved state.&lt;br /&gt;
&lt;br /&gt;
If editing a new unsaved draft, the form will revert to its original pre-filled itinerary values.&lt;br /&gt;
&lt;br /&gt;
=== Create New ===&lt;br /&gt;
Creates a new unsaved order draft of the type selected in the Order Type dropdown, while keeping the current modal open.&lt;br /&gt;
&lt;br /&gt;
If unsaved changes exist, the user will be prompted to save or discard them before continuing.&lt;br /&gt;
&lt;br /&gt;
The new order is automatically given a unique title based on the itinerary name.&lt;br /&gt;
&lt;br /&gt;
=== Close ===&lt;br /&gt;
Closes the Orders modal.&lt;br /&gt;
&lt;br /&gt;
## If there are unsaved changes, the user will be prompted to save or discard the draft before closing.&lt;br /&gt;
&lt;br /&gt;
== Sidebar ==&lt;br /&gt;
The sidebar contains all saved orders (both Accommodation and Flight) for the currently selected itinerary.&lt;br /&gt;
&lt;br /&gt;
=== Search ===&lt;br /&gt;
Filters saved orders by title.&lt;br /&gt;
&lt;br /&gt;
=== Refresh ===&lt;br /&gt;
Reloads the latest orders from the server without closing the modal.&lt;br /&gt;
&lt;br /&gt;
=== Order Entries ===&lt;br /&gt;
Displays all saved orders ordered by most recently updated first.&lt;br /&gt;
&lt;br /&gt;
Each entry displays:&lt;br /&gt;
&lt;br /&gt;
- Order title&lt;br /&gt;
- Order type tag (&#039;&#039;&#039;Accommodation&#039;&#039;&#039; or &#039;&#039;&#039;Flight&#039;&#039;&#039;)&lt;br /&gt;
- Last modified date and time&lt;br /&gt;
&lt;br /&gt;
Selecting a different order will load its saved data into the form and automatically switch the form to the correct type.&lt;br /&gt;
&lt;br /&gt;
If unsaved changes exist, the user will be prompted to save or discard them before switching.&lt;br /&gt;
&lt;br /&gt;
## When no order is selected, the sidebar shows a &#039;&#039;&#039;Draft&#039;&#039;&#039; entry indicating an unsaved draft is being edited.&lt;br /&gt;
&lt;br /&gt;
== Bottom Bar ==&lt;br /&gt;
&lt;br /&gt;
=== Save ===&lt;br /&gt;
Saves the current order.&lt;br /&gt;
&lt;br /&gt;
Once saved:&lt;br /&gt;
&lt;br /&gt;
- The order becomes persistent&lt;br /&gt;
- It appears in the sidebar with the appropriate type tag&lt;br /&gt;
- Future edits can be restored using Reset&lt;br /&gt;
&lt;br /&gt;
=== Delete / Discard Draft ===&lt;br /&gt;
Deletes the currently selected saved order. This action cannot be undone and requires confirmation.&lt;br /&gt;
&lt;br /&gt;
If working on an unsaved draft, this button instead discards the draft and requires confirmation.&lt;br /&gt;
&lt;br /&gt;
=== Generate PDF ===&lt;br /&gt;
Generates a PDF version of the current order using all entered form data. The PDF format adapts to the order type:&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;Accommodation PDF&#039;&#039;&#039; - Includes hotel details, guest rooming assignments, check-in/check-out times, and contact information. Designed for sharing with hotels, accommodation providers, or booking agents.&lt;br /&gt;
- &#039;&#039;&#039;Flight PDF&#039;&#039;&#039; - Includes flight details, passenger list, airline information, departure and arrival details, and special requests. Designed for sharing with airlines, flight providers, or booking agents.&lt;br /&gt;
&lt;br /&gt;
=== Export Format ===&lt;br /&gt;
Optional dropdown to select the export file format:&lt;br /&gt;
&lt;br /&gt;
- &#039;&#039;&#039;XLSX&#039;&#039;&#039; (default)&lt;br /&gt;
- &#039;&#039;&#039;CSV&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
=== Export ===&lt;br /&gt;
Generates a downloadable spreadsheet of the current order&#039;s details. The exported file format adapts to the order type:&lt;br /&gt;
&lt;br /&gt;
==== Accommodation Export ====&lt;br /&gt;
Includes:&lt;br /&gt;
&lt;br /&gt;
- Team Name, Itinerary Name, Order Name&lt;br /&gt;
- Selected Hotel details (Name, Address, Check-In/Out Times, Telephone)&lt;br /&gt;
- Guest table with: Guest Names, Check-In Date/Time, Check-Out Date/Time, Room Type, Booking Reference&lt;br /&gt;
&lt;br /&gt;
==== Flight Export ====&lt;br /&gt;
Includes:&lt;br /&gt;
&lt;br /&gt;
- Team Name, Itinerary Name, Order Name&lt;br /&gt;
- Flight details (Airline, Cabin Class, Flight Number, Departure Date/Time &amp;amp; Airport, Arrival Date/Time &amp;amp; Airport)&lt;br /&gt;
- Passenger table with: Passenger Names, Booking Reference&lt;br /&gt;
&lt;br /&gt;
=== Import ===&lt;br /&gt;
Imports order data from a previously exported XLSX or CSV file. The system automatically detects whether the file contains Accommodation or Flight data and populates the corresponding form.&lt;br /&gt;
&lt;br /&gt;
==== Accommodation Import ====&lt;br /&gt;
Imports hotel details, guest room assignments, check-in/check-out dates, room types, and booking references. Creates a new hotel in the itinerary and associates it with the imported order. Validates guest names against known users, date formats, and room date logic.&lt;br /&gt;
&lt;br /&gt;
==== Flight Import ====&lt;br /&gt;
Imports flight details including airline, cabin class, flight number, departure/arrival airports and dates, and passenger list. Creates a new flight in the itinerary and associates it with the imported order. Validates passenger names against known users, airport codes, date formats, and cabin class values.&lt;br /&gt;
&lt;br /&gt;
## If validation errors are found during import, they are displayed in a dialog showing a spreadsheet preview of the imported data with errors highlighted, allowing the user to identify and fix issues before re-importing.&lt;br /&gt;
&lt;br /&gt;
== General Form Fields ==&lt;br /&gt;
These fields are shared across both Accommodation and Flight order types.&lt;br /&gt;
&lt;br /&gt;
=== Order Name \* ===&lt;br /&gt;
The title of the order.&lt;br /&gt;
&lt;br /&gt;
This is used:&lt;br /&gt;
&lt;br /&gt;
- In the sidebar list&lt;br /&gt;
- As the PDF title&lt;br /&gt;
- To help identify booking requests&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
- &amp;quot;Trip to Milan&amp;quot;&lt;br /&gt;
- &amp;quot;Barcelona Conference Accommodation&amp;quot;&lt;br /&gt;
- &amp;quot;London Team Flight Bookings&amp;quot;&lt;br /&gt;
&lt;br /&gt;
---&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Contact Name ===&lt;br /&gt;
The primary contact person responsible for the booking request. Typically pre-filled using the current user profile.&lt;br /&gt;
&lt;br /&gt;
---&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Phone Number ===&lt;br /&gt;
The primary contact phone number for suppliers to use when responding to the request.&lt;br /&gt;
&lt;br /&gt;
---&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Contact Email ===&lt;br /&gt;
The main email address suppliers should use for communication. Usually pre-filled from the logged-in user profile.&lt;br /&gt;
&lt;br /&gt;
---&lt;br /&gt;
&lt;br /&gt;
=== Additional Emails ===&lt;br /&gt;
Optional comma-separated email addresses that should also receive communications or copies of the generated PDF.&lt;br /&gt;
&lt;br /&gt;
## Example: &amp;lt;code&amp;gt;ops@company.com, travel@company.com&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== Event Location ===&lt;br /&gt;
The destination, venue, or event location related to the booking request. Uses an interactive map address selector.&lt;br /&gt;
&lt;br /&gt;
---&lt;br /&gt;
&lt;br /&gt;
=== Stay Dates \* ===&lt;br /&gt;
The date range for the booking. Typically pre-filled from the itinerary dates.&lt;br /&gt;
&lt;br /&gt;
---&lt;br /&gt;
&lt;br /&gt;
=== Response Due Date ===&lt;br /&gt;
The deadline by which suppliers or agents should respond to the request.&lt;br /&gt;
&lt;br /&gt;
---&lt;br /&gt;
&lt;br /&gt;
=== Additional Information for Agent ===&lt;br /&gt;
Free-text notes intended for suppliers or booking agents. Character limit of 1024 with a remaining character counter.&lt;br /&gt;
&lt;br /&gt;
This content is included in the generated PDF. The field is pre-populated with a template based on the order type:&lt;br /&gt;
&lt;br /&gt;
==== Accommodation template ====&lt;br /&gt;
&lt;br /&gt;
- Desired room type&lt;br /&gt;
- Required services (wifi, parking, breakfast etc)&lt;br /&gt;
- Additional requests&lt;br /&gt;
&lt;br /&gt;
==== Flight template ====&lt;br /&gt;
&lt;br /&gt;
- Special meal requirements&lt;br /&gt;
- Seat preferences&lt;br /&gt;
- Additional requests&lt;br /&gt;
&lt;br /&gt;
---&lt;br /&gt;
&lt;br /&gt;
=== Team Internal Comments ===&lt;br /&gt;
Internal-only notes visible to EventR users. Intended for operational or planning purposes and not shared with suppliers.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
- Internal approval notes&lt;br /&gt;
- Supplier preferences&lt;br /&gt;
- Budget discussions&lt;br /&gt;
- Booking reminders&lt;br /&gt;
&lt;br /&gt;
---&lt;br /&gt;
&lt;br /&gt;
== Accommodation-Specific Fields ==&lt;br /&gt;
&lt;br /&gt;
=== Select Pending Hotel ===&lt;br /&gt;
Selects an existing pending hotel/accommodation item from the itinerary.&lt;br /&gt;
&lt;br /&gt;
When selected:&lt;br /&gt;
&lt;br /&gt;
- Related guest information can be used&lt;br /&gt;
- Room counts may auto-populate based on assigned guests&lt;br /&gt;
- Guest data can be included in the generated PDF&lt;br /&gt;
&lt;br /&gt;
## Only hotels currently marked as &#039;&#039;&#039;Pending&#039;&#039;&#039; are available.&lt;br /&gt;
&lt;br /&gt;
=== Number of Rooms Required ===&lt;br /&gt;
The total number of rooms required for the stay. May automatically populate based on the selected hotel&#039;s guest assignments, but can also be edited manually.&lt;br /&gt;
&lt;br /&gt;
---&lt;br /&gt;
&lt;br /&gt;
=== Maximum Number of Hotels to Split \* ===&lt;br /&gt;
Defines how many separate hotels the booking can be split across. Options: 1, 2, 3, or 4.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
- &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; = all guests must stay in the same hotel&lt;br /&gt;
- &amp;lt;code&amp;gt;2&amp;lt;/code&amp;gt; = guests may be split between two hotels&lt;br /&gt;
&lt;br /&gt;
---&lt;br /&gt;
&lt;br /&gt;
=== Maximum Distance from Event ===&lt;br /&gt;
Optional distance limit between the accommodation and the event location.&lt;br /&gt;
&lt;br /&gt;
## Examples: &amp;quot;5km&amp;quot;, &amp;quot;15 minute walk&amp;quot;&lt;br /&gt;
&lt;br /&gt;
=== Minimum Cost per Night per Room ===&lt;br /&gt;
Optional minimum nightly room budget. Useful when requesting accommodation within a preferred pricing range.&lt;br /&gt;
&lt;br /&gt;
---&lt;br /&gt;
&lt;br /&gt;
=== Maximum Cost per Night per Room ===&lt;br /&gt;
Optional maximum nightly room budget. Helps suppliers avoid quoting accommodation outside budget requirements.&lt;br /&gt;
&lt;br /&gt;
---&lt;br /&gt;
&lt;br /&gt;
== Flight-Specific Fields ==&lt;br /&gt;
&lt;br /&gt;
=== Select Pending Flight ===&lt;br /&gt;
Selects an existing pending flight from the itinerary.&lt;br /&gt;
&lt;br /&gt;
When selected, the form is automatically pre-populated with:&lt;br /&gt;
&lt;br /&gt;
- Flight number/booking reference&lt;br /&gt;
- Airline name&lt;br /&gt;
- Departure airport&lt;br /&gt;
- Arrival airport&lt;br /&gt;
- Departure date and time&lt;br /&gt;
- Arrival date and time&lt;br /&gt;
- Number of passengers&lt;br /&gt;
&lt;br /&gt;
## Only flights currently marked as &#039;&#039;&#039;Pending&#039;&#039;&#039; are available.&lt;br /&gt;
&lt;br /&gt;
=== Flight Number ===&lt;br /&gt;
The flight booking reference number. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
---&lt;br /&gt;
&lt;br /&gt;
=== Airline ===&lt;br /&gt;
The airline operating the flight. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
---&lt;br /&gt;
&lt;br /&gt;
=== Number of Passengers ===&lt;br /&gt;
The total number of passengers for the flight. May automatically populate based on the selected flight&#039;s passenger list, but can also be edited manually.&lt;br /&gt;
&lt;br /&gt;
---&lt;br /&gt;
&lt;br /&gt;
=== Cabin Class ===&lt;br /&gt;
The requested cabin class for the flight. Options:&lt;br /&gt;
&lt;br /&gt;
- Economy&lt;br /&gt;
- Premium Economy&lt;br /&gt;
- Business&lt;br /&gt;
- First&lt;br /&gt;
&lt;br /&gt;
---&lt;br /&gt;
&lt;br /&gt;
=== Departure Airport ===&lt;br /&gt;
The departure airport for the flight. Uses an interactive airport selector with search functionality. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
---&lt;br /&gt;
&lt;br /&gt;
=== Arrival Airport ===&lt;br /&gt;
The arrival airport for the flight. Uses an interactive airport selector with search functionality. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
---&lt;br /&gt;
&lt;br /&gt;
=== Departure Date ===&lt;br /&gt;
The departure date and time for the flight. Uses a date/time picker with warning indicators for dates outside the event range. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
---&lt;br /&gt;
&lt;br /&gt;
=== Arrival Date ===&lt;br /&gt;
The arrival date and time for the flight. Uses a date/time picker with warning indicators for dates outside the event range. May be pre-filled from the selected flight.&lt;br /&gt;
&lt;br /&gt;
---&lt;br /&gt;
&lt;br /&gt;
== Draft Handling ==&lt;br /&gt;
Orders support unsaved drafts.&lt;br /&gt;
&lt;br /&gt;
If the user attempts to:&lt;br /&gt;
&lt;br /&gt;
- Close the modal&lt;br /&gt;
- Switch orders&lt;br /&gt;
- Refresh data&lt;br /&gt;
- Create a new draft&lt;br /&gt;
- Change the order type (while in unsaved draft mode)&lt;br /&gt;
&lt;br /&gt;
while unsaved changes exist, EventR will prompt the user to:&lt;br /&gt;
&lt;br /&gt;
- Save changes&lt;br /&gt;
- Discard changes&lt;br /&gt;
&lt;br /&gt;
This helps prevent accidental data loss.&lt;br /&gt;
| style=&amp;quot;width:40%; vertical-align:top;&amp;quot; |&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.49.46.png|thumb|Example: Draft order]]&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.58.44.png|thumb|Multiple orders view with type tags]]&lt;br /&gt;
|}&lt;br /&gt;
[[Category:3.4.1]]&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=Orders&amp;diff=1328</id>
		<title>Orders</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=Orders&amp;diff=1328"/>
		<updated>2026-07-21T15:04:03Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Infobox Feature&lt;br /&gt;
 | name = Rooming Lists&lt;br /&gt;
 | version = [[Release 3.4.1|3.4.1]] (BETA)&lt;br /&gt;
 | tier = Standard, Premium and Enterprise&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
= Overview =&lt;br /&gt;
The &#039;&#039;&#039;Rooming List&#039;&#039;&#039; feature allows users to create, manage, save, and generate accommodation request PDFs for hotels or accommodation suppliers. It acts as a central workspace for collecting stay requirements, guest accommodation preferences, and booking details related to an itinerary. &lt;br /&gt;
&lt;br /&gt;
= Accessing Rooming Lists =&lt;br /&gt;
{| style=&amp;quot;width:100%; margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width:60%; vertical-align:top;&amp;quot; |&lt;br /&gt;
To find the rooming list functionality, select &#039;&#039;&#039;Create Rooming List&#039;&#039;&#039; from the itinerary accommodation section in the ECH. This opens the Rooming List workspace in a full-screen modal.&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:40%; vertical-align:top;&amp;quot; |&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.21.54.png|thumb| When you have no existing accommodations, button is located bottom centre. ]]&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.38.33.png|thumb|Button moves into the header when you have existing accommodations.]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
= Managing Rooming Lists =&lt;br /&gt;
{| style=&amp;quot;width:100%; margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width:60%; vertical-align:top;&amp;quot; |New rooming lists begin as unsaved drafts until they are saved.&lt;br /&gt;
&lt;br /&gt;
When creating a new rooming list, the form is automatically pre-filled using information from the selected itinerary, including dates, location, and lead booker details (You) where available.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Layout Overview ===&lt;br /&gt;
The Rooming List workspace is divided into four main sections:&lt;br /&gt;
&lt;br /&gt;
* Top Bar&lt;br /&gt;
* Sidebar&lt;br /&gt;
* Main Form&lt;br /&gt;
* Bottom Bar&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Top Bar ==&lt;br /&gt;
&lt;br /&gt;
=== Reset ===&lt;br /&gt;
Restores the currently selected rooming list back to its last saved state.&lt;br /&gt;
&lt;br /&gt;
If editing a new unsaved draft, the form will revert to its original pre-filled itinerary values.&lt;br /&gt;
&lt;br /&gt;
=== Create New ===&lt;br /&gt;
Creates a new unsaved rooming list draft while keeping the current modal open.&lt;br /&gt;
&lt;br /&gt;
If unsaved changes exist, the user will be prompted to save or discard them before continuing.&lt;br /&gt;
&lt;br /&gt;
=== Close ===&lt;br /&gt;
Closes the Rooming List modal.&lt;br /&gt;
&lt;br /&gt;
If there are unsaved changes, the user will be prompted to save or discard the draft before closing.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Sidebar ==&lt;br /&gt;
The sidebar contains all saved rooming lists for the currently selected itinerary.&lt;br /&gt;
&lt;br /&gt;
=== Search ===&lt;br /&gt;
Filters saved rooming lists by title.&lt;br /&gt;
&lt;br /&gt;
=== Refresh ===&lt;br /&gt;
Reloads the latest rooming lists from the server without closing the modal.&lt;br /&gt;
&lt;br /&gt;
=== Rooming List Entries ===&lt;br /&gt;
Displays all saved rooming lists ordered by most recently updated first.&lt;br /&gt;
&lt;br /&gt;
Each entry displays:&lt;br /&gt;
&lt;br /&gt;
* Rooming list title&lt;br /&gt;
* Last modified date and time&lt;br /&gt;
&lt;br /&gt;
Selecting a different rooming list will load its saved data into the form.&lt;br /&gt;
&lt;br /&gt;
If unsaved changes exist, the user will be prompted to save or discard them before switching.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Bottom Bar ==&lt;br /&gt;
&lt;br /&gt;
=== Save ===&lt;br /&gt;
Saves the current rooming list.&lt;br /&gt;
&lt;br /&gt;
Once saved:&lt;br /&gt;
&lt;br /&gt;
* The rooming list becomes persistent&lt;br /&gt;
* It appears in the sidebar&lt;br /&gt;
* Future edits can be restored using Reset&lt;br /&gt;
&lt;br /&gt;
=== Delete ===&lt;br /&gt;
Deletes the currently selected saved rooming list.&lt;br /&gt;
&lt;br /&gt;
This action cannot be undone.&lt;br /&gt;
&lt;br /&gt;
If working on an unsaved draft, this button instead discards the draft.&lt;br /&gt;
&lt;br /&gt;
=== Generate PDF ===&lt;br /&gt;
Generates a PDF version of the current rooming list using all entered form data.&lt;br /&gt;
&lt;br /&gt;
The PDF is designed for sharing with hotels, accommodation providers, or booking agents.&lt;br /&gt;
&lt;br /&gt;
=== Export Format ===&lt;br /&gt;
Optional dropdown to select the export file format:&lt;br /&gt;
- XLSX (default)&lt;br /&gt;
- CSV&lt;br /&gt;
&lt;br /&gt;
=== Export ===&lt;br /&gt;
Generates a downloadable spreadsheet of the current rooming list&#039;s guest rooming details.&lt;br /&gt;
The exported file includes:&lt;br /&gt;
- Team Name, Itinerary Name, Order Name&lt;br /&gt;
- Selected Hotel details (Name, Address, Check-In/Out Times, Telephone)&lt;br /&gt;
- Guest table with: Guest Names, Check-In Date/Time, Check-Out Date/Time, Room Type, Booking Reference&lt;br /&gt;
&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Form Fields ==&lt;br /&gt;
&lt;br /&gt;
== General Information ==&lt;br /&gt;
&lt;br /&gt;
=== Order Name * ===&lt;br /&gt;
The title of the rooming list.&lt;br /&gt;
&lt;br /&gt;
This is used:&lt;br /&gt;
&lt;br /&gt;
* In the sidebar list&lt;br /&gt;
* As the PDF title&lt;br /&gt;
* To help identify accommodation requests&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
* “Trip to Milan”&lt;br /&gt;
* “Barcelona Conference Accommodation”&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Contact Name ===&lt;br /&gt;
The primary contact person responsible for the booking or accommodation request.&lt;br /&gt;
&lt;br /&gt;
This is typically pre-filled using the current user profile.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Phone Number ===&lt;br /&gt;
The primary contact phone number for accommodation providers to use when responding to the request.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Contact Email ===&lt;br /&gt;
The main email address accommodation providers should use for communication.&lt;br /&gt;
&lt;br /&gt;
This field is usually pre-filled from the logged-in user profile.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Additional Emails ===&lt;br /&gt;
Optional comma-separated email addresses that should also receive accommodation communications or copies of the generated PDF.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;ops@company.com, travel@company.com&amp;lt;/code&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Event Location ===&lt;br /&gt;
The destination, venue, or event location related to the accommodation request.&lt;br /&gt;
&lt;br /&gt;
This location helps suppliers understand where accommodation proximity is required.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Stay Dates * ===&lt;br /&gt;
The requested accommodation check-in and check-out date range.&lt;br /&gt;
&lt;br /&gt;
These dates are typically pre-filled from the itinerary.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Accommodation Requirements ==&lt;br /&gt;
&lt;br /&gt;
=== Select Pending Accommodations ===&lt;br /&gt;
Selects an existing pending hotel/accommodation item from the itinerary.&lt;br /&gt;
&lt;br /&gt;
When selected:&lt;br /&gt;
&lt;br /&gt;
* Related guest information can be used&lt;br /&gt;
* Room counts may auto-populate&lt;br /&gt;
* Guest data can be included in the generated PDF&lt;br /&gt;
&lt;br /&gt;
Only accommodations currently marked as &#039;&#039;&#039;Pending&#039;&#039;&#039; are available.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Number of Rooms Required ===&lt;br /&gt;
The total number of rooms required for the stay.&lt;br /&gt;
&lt;br /&gt;
This may automatically populate based on the selected accommodation’s guest assignments, but can also be edited manually.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Maximum Number of Accommodations to Split * ===&lt;br /&gt;
Defines how many separate hotels or accommodation providers the booking can be split across.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; = all guests must stay in the same hotel&lt;br /&gt;
* &amp;lt;code&amp;gt;2&amp;lt;/code&amp;gt; = guests may be split between two hotels&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Maximum Distance from Event ===&lt;br /&gt;
Optional distance limit between the accommodation and the event location.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
* “5km”&lt;br /&gt;
* “15 minute walk”&lt;br /&gt;
&lt;br /&gt;
This helps suppliers return more suitable accommodation options.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Minimum Cost per Night per Room ===&lt;br /&gt;
Optional minimum nightly room budget.&lt;br /&gt;
&lt;br /&gt;
Useful when requesting accommodation within a preferred pricing range.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Maximum Cost per Night per Room ===&lt;br /&gt;
Optional maximum nightly room budget.&lt;br /&gt;
&lt;br /&gt;
Helps suppliers avoid quoting accommodation outside budget requirements.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Response Due Date ===&lt;br /&gt;
The deadline by which accommodation providers or agents should respond to the request.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Notes &amp;amp; Comments ==&lt;br /&gt;
&lt;br /&gt;
=== Additional Information for Agent ===&lt;br /&gt;
Free-text notes intended for accommodation providers or booking agents.&lt;br /&gt;
&lt;br /&gt;
Typical information may include:&lt;br /&gt;
&lt;br /&gt;
* Preferred room types&lt;br /&gt;
* Required amenities&lt;br /&gt;
* Breakfast or parking requirements&lt;br /&gt;
* Accessibility requests&lt;br /&gt;
* Special guest requirements&lt;br /&gt;
&lt;br /&gt;
This content is included in the generated PDF.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Team Internal Comments ===&lt;br /&gt;
Internal-only notes visible to EventR users.&lt;br /&gt;
&lt;br /&gt;
These comments are intended for operational or planning purposes and are not intended for accommodation suppliers.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
* Internal approval notes&lt;br /&gt;
* Supplier preferences&lt;br /&gt;
* Budget discussions&lt;br /&gt;
* Booking reminders&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Draft Handling ==&lt;br /&gt;
Rooming lists support unsaved drafts.&lt;br /&gt;
&lt;br /&gt;
If the user attempts to:&lt;br /&gt;
&lt;br /&gt;
* Close the modal&lt;br /&gt;
* Switch rooming lists&lt;br /&gt;
* Refresh data&lt;br /&gt;
* Create a new draft&lt;br /&gt;
&lt;br /&gt;
while unsaved changes exist, EventR will prompt the user to:&lt;br /&gt;
&lt;br /&gt;
* Save changes&lt;br /&gt;
* Discard changes&lt;br /&gt;
&lt;br /&gt;
This helps prevent accidental data loss.&lt;br /&gt;
| style=&amp;quot;width:40%; vertical-align:top;&amp;quot; |&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.49.46.png|thumb|Example: Draft rooming list]]&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.58.44.png|thumb|Multiple rooming list view]]&lt;br /&gt;
|}&lt;br /&gt;
[[Category:3.4.1]]&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=Alerts&amp;diff=1028</id>
		<title>Alerts</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=Alerts&amp;diff=1028"/>
		<updated>2026-07-01T13:29:49Z</updated>

		<summary type="html">&lt;p&gt;Samh: Created page with &amp;quot;== What are Alerts? ==  &amp;#039;&amp;#039;&amp;#039;Alerts&amp;#039;&amp;#039;&amp;#039; 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&amp;#039;s a newly booked flight, an updated hotel reservation, or a fresh activity added to your schedule.  Think of Alerts as your &amp;quot;what&amp;#039;s new&amp;quot; dashboard, keeping you informed without having to hunt for updates across multiple screens.  == How to Access Alerts...&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== What are Alerts? ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Alerts&#039;&#039;&#039; 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&#039;s a newly booked flight, an updated hotel reservation, or a fresh activity added to your schedule.&lt;br /&gt;
&lt;br /&gt;
Think of Alerts as your &amp;quot;what&#039;s new&amp;quot; dashboard, keeping you informed without having to hunt for updates across multiple screens.&lt;br /&gt;
&lt;br /&gt;
== How to Access Alerts ==&lt;br /&gt;
&lt;br /&gt;
# Open the EventR app&lt;br /&gt;
# Navigate to your event itinerary&lt;br /&gt;
# Tap the &#039;&#039;&#039;Alerts&#039;&#039;&#039; icon in the navigation menu&lt;br /&gt;
&lt;br /&gt;
The Alerts page will display all recent updates, grouped by date.&lt;br /&gt;
&lt;br /&gt;
== Understanding Your Alerts ==&lt;br /&gt;
&lt;br /&gt;
When you open the Alerts page, you&#039;ll see:&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Date headings&#039;&#039;&#039; — Alerts are organized under date labels like &amp;quot;&#039;&#039;&#039;Today&#039;&#039;&#039;&amp;quot;, &amp;quot;&#039;&#039;&#039;Yesterday&#039;&#039;&#039;&amp;quot;, or specific dates, making it easy to see when changes happened.&lt;br /&gt;
* &#039;&#039;&#039;Individual alert cards&#039;&#039;&#039; — Each card shows a brief description of the change and the name of the affected item.&lt;br /&gt;
* &#039;&#039;&#039;Empty state&#039;&#039;&#039; — If there are no new updates, you&#039;ll see a friendly message letting you know there&#039;s nothing new.&lt;br /&gt;
&lt;br /&gt;
== Types of Alerts ==&lt;br /&gt;
&lt;br /&gt;
Alerts cover all the key items in your event itinerary:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
|+ Supported Alert Types&lt;br /&gt;
! Alert Type !! What You&#039;ll See&lt;br /&gt;
|-&lt;br /&gt;
| &#039;&#039;&#039;Flight&#039;&#039;&#039; || New flight bookings or changes to existing flights, including your booking reference and departure/arrival airports&lt;br /&gt;
|-&lt;br /&gt;
| &#039;&#039;&#039;Hotel&#039;&#039;&#039; || New hotel reservations or updates to existing bookings, showing the hotel name&lt;br /&gt;
|-&lt;br /&gt;
| &#039;&#039;&#039;Car Hire&#039;&#039;&#039; || New car hire bookings or changes, showing the vehicle type and provider&lt;br /&gt;
|-&lt;br /&gt;
| &#039;&#039;&#039;Transport&#039;&#039;&#039; || New transport arrangements or updates, showing the transport details&lt;br /&gt;
|-&lt;br /&gt;
| &#039;&#039;&#039;Parking&#039;&#039;&#039; || New parking bookings or changes, showing the parking location&lt;br /&gt;
|-&lt;br /&gt;
| &#039;&#039;&#039;Activity / Stand&#039;&#039;&#039; || New activities or stands added to your itinerary, or updates to existing ones&lt;br /&gt;
|-&lt;br /&gt;
| &#039;&#039;&#039;To-Do&#039;&#039;&#039; || New to-do items or updates to existing tasks&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Each alert clearly indicates whether the item is &#039;&#039;&#039;newly added&#039;&#039;&#039; or an &#039;&#039;&#039;existing item that has been updated&#039;&#039;&#039;.&lt;br /&gt;
&lt;br /&gt;
== Interacting with Alerts ==&lt;br /&gt;
&lt;br /&gt;
=== View Details ===&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Tap&#039;&#039;&#039; any alert card to navigate directly to the full details page for that itinerary item. This is the quickest way to review what changed.&lt;br /&gt;
&lt;br /&gt;
=== Clear All Alerts ===&lt;br /&gt;
&lt;br /&gt;
When you&#039;ve caught up on all your updates, tap the &#039;&#039;&#039;Clear All&#039;&#039;&#039; 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.&lt;br /&gt;
&lt;br /&gt;
=== Refresh Alerts ===&lt;br /&gt;
&lt;br /&gt;
Simply &#039;&#039;&#039;pull down&#039;&#039;&#039; on the Alerts page to refresh and ensure you&#039;re seeing the very latest updates.&lt;br /&gt;
&lt;br /&gt;
== Tips ==&lt;br /&gt;
&lt;br /&gt;
* &#039;&#039;&#039;Check Alerts regularly&#039;&#039;&#039; — Especially on the days leading up to your event, when changes are most common.&lt;br /&gt;
* &#039;&#039;&#039;Use Clear All&#039;&#039;&#039; — Once you&#039;ve reviewed everything, clear your alerts so the list stays clean and focused on new updates.&lt;br /&gt;
* &#039;&#039;&#039;Alerts are smart&#039;&#039;&#039; — You&#039;ll only see changes that have happened since your last visit, so you won&#039;t be shown the same update twice.&lt;br /&gt;
* &#039;&#039;&#039;Tap to navigate&#039;&#039;&#039; — Every alert is a shortcut. Tap it to jump straight to the full details of that item.&lt;br /&gt;
&lt;br /&gt;
== Frequently Asked Questions ==&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Q: Why are some alerts showing as &amp;quot;updated&amp;quot; instead of &amp;quot;new&amp;quot;?&#039;&#039;&#039;&lt;br /&gt;
:A: An alert is marked as &amp;quot;updated&amp;quot; when an existing item in your itinerary has been modified — for example, if a flight time changes or a hotel room is upgraded. &amp;quot;New&amp;quot; alerts appear when an item is added to your itinerary for the first time.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Q: Will I miss alerts if I don&#039;t check for a while?&#039;&#039;&#039;&lt;br /&gt;
:A: No! All alerts are saved until you view them. When you open the Alerts page, you&#039;ll see every change that&#039;s happened since your last visit.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Q: Can I filter or sort the alerts?&#039;&#039;&#039;&lt;br /&gt;
: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.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Q: Who can make changes that trigger alerts?&#039;&#039;&#039;&lt;br /&gt;
: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.&lt;br /&gt;
&lt;br /&gt;
[[Category:Features]]&lt;br /&gt;
[[Category:User Guide]]&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=Todos&amp;diff=971</id>
		<title>Todos</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=Todos&amp;diff=971"/>
		<updated>2026-06-17T14:00:32Z</updated>

		<summary type="html">&lt;p&gt;Samh: Samh moved page Todos to Custom Todos&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;#REDIRECT [[Custom Todos]]&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=Custom_Todos&amp;diff=970</id>
		<title>Custom Todos</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=Custom_Todos&amp;diff=970"/>
		<updated>2026-06-17T14:00:32Z</updated>

		<summary type="html">&lt;p&gt;Samh: Samh moved page Todos to Custom Todos&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Infobox Feature&lt;br /&gt;
 | name = Custom Todos&lt;br /&gt;
 | version = [[Release 3.5.0|3.5.0]]&lt;br /&gt;
 | tier = Standard, Premium and Enterprise&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot 2026-06-17 at 14.57.14.png|thumb|Example: Input - ECH custom Todo]]&lt;br /&gt;
[[File:App-custom-todo.png|thumb|Example: Output - App custom Todo]]&lt;br /&gt;
&lt;br /&gt;
= Custom Todos =&lt;br /&gt;
&lt;br /&gt;
Todo task labels support special prefixes and variables that control how tasks are rendered in the UI.&lt;br /&gt;
&lt;br /&gt;
== Prefixes ==&lt;br /&gt;
&lt;br /&gt;
Prefixes are detected by examining the &#039;&#039;&#039;first character&#039;&#039;&#039; of the label after trimming leading whitespace.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;.&#039;&#039; (Dot) – Inline/Child Tasks ===&lt;br /&gt;
&lt;br /&gt;
Prefix a task label with &amp;lt;code&amp;gt;.&amp;lt;/code&amp;gt; to make it an &#039;&#039;&#039;inline child&#039;&#039;&#039; of the preceding non-dot task. Child tasks are displayed in a grid row alongside their parent, creating a compact horizontal layout.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Behaviour:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* The &amp;lt;code&amp;gt;.&amp;lt;/code&amp;gt; prefix is stripped from the displayed label&lt;br /&gt;
* The task is grouped with the previous non-dot task as a child&lt;br /&gt;
* Displayed in a shared grid row (parent + children side by side)&lt;br /&gt;
* Checkbox is still shown (can be checked/unchecked)&lt;br /&gt;
* If a dot-prefixed task appears without a preceding parent, it is treated as a regular individual task&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
Monday Breakfast&lt;br /&gt;
.Lunch&lt;br /&gt;
.Dinner&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== &amp;lt;code&amp;gt;|&amp;lt;/code&amp;gt; (Pipe) – Label-Only (No Checkbox) ===&lt;br /&gt;
&lt;br /&gt;
Prefix a task label with &amp;lt;code&amp;gt;|&amp;lt;/code&amp;gt; to render it as &#039;&#039;&#039;plain text without a checkbox&#039;&#039;&#039;. Useful for section headers, notes, or informational text within a todo list.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Behaviour:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* The &amp;lt;code&amp;gt;|&amp;lt;/code&amp;gt; prefix is stripped from the displayed label&lt;br /&gt;
* No checkbox is rendered&lt;br /&gt;
* The item does not count toward the completed/total counter&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
|Important Notes&lt;br /&gt;
Attend all morning sessions&lt;br /&gt;
|Evening Activities&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Date Variables ==&lt;br /&gt;
&lt;br /&gt;
Task labels support the &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; variable, which is replaced with the event&#039;s start date displayed as day and month numbers (e.g., &#039;&#039;16/06&#039;&#039;).&lt;br /&gt;
&lt;br /&gt;
=== Basic Usage ===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Variable&lt;br /&gt;
! Replaced With&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date (e.g., &#039;&#039;16/06&#039;&#039;)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Offsets ===&lt;br /&gt;
&lt;br /&gt;
You can add or subtract days from the event date using &amp;lt;code&amp;gt;+&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;-&amp;lt;/code&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Variable&lt;br /&gt;
! Replaced With&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate+1}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date + 1 day&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate-1}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date − 1 day&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate+3}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date + 3 days&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate-2}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date − 2 days&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Whitespace inside the braces is tolerated:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{ EventDate + 1 }}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; → same as &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate+1}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate- 2}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; → same as &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate-2}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Unknown variables (anything other than &#039;&#039;EventDate&#039;&#039;) are left as-is.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
{{EventDate}} Check-in at hotel&lt;br /&gt;
{{EventDate+1}} Follow-up meeting&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Combining Prefixes and Variables ==&lt;br /&gt;
&lt;br /&gt;
Prefixes and date variables can be used together:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
|Schedule for {{EventDate}}&lt;br /&gt;
Morning briefing&lt;br /&gt;
. Afternoon workshop&lt;br /&gt;
. Evening networking&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=Custom_Todos&amp;diff=969</id>
		<title>Custom Todos</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=Custom_Todos&amp;diff=969"/>
		<updated>2026-06-17T14:00:05Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Infobox Feature&lt;br /&gt;
 | name = Custom Todos&lt;br /&gt;
 | version = [[Release 3.5.0|3.5.0]]&lt;br /&gt;
 | tier = Standard, Premium and Enterprise&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot 2026-06-17 at 14.57.14.png|thumb|Example: Input - ECH custom Todo]]&lt;br /&gt;
[[File:App-custom-todo.png|thumb|Example: Output - App custom Todo]]&lt;br /&gt;
&lt;br /&gt;
= Custom Todos =&lt;br /&gt;
&lt;br /&gt;
Todo task labels support special prefixes and variables that control how tasks are rendered in the UI.&lt;br /&gt;
&lt;br /&gt;
== Prefixes ==&lt;br /&gt;
&lt;br /&gt;
Prefixes are detected by examining the &#039;&#039;&#039;first character&#039;&#039;&#039; of the label after trimming leading whitespace.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;.&#039;&#039; (Dot) – Inline/Child Tasks ===&lt;br /&gt;
&lt;br /&gt;
Prefix a task label with &amp;lt;code&amp;gt;.&amp;lt;/code&amp;gt; to make it an &#039;&#039;&#039;inline child&#039;&#039;&#039; of the preceding non-dot task. Child tasks are displayed in a grid row alongside their parent, creating a compact horizontal layout.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Behaviour:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* The &amp;lt;code&amp;gt;.&amp;lt;/code&amp;gt; prefix is stripped from the displayed label&lt;br /&gt;
* The task is grouped with the previous non-dot task as a child&lt;br /&gt;
* Displayed in a shared grid row (parent + children side by side)&lt;br /&gt;
* Checkbox is still shown (can be checked/unchecked)&lt;br /&gt;
* If a dot-prefixed task appears without a preceding parent, it is treated as a regular individual task&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
Monday Breakfast&lt;br /&gt;
.Lunch&lt;br /&gt;
.Dinner&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== &amp;lt;code&amp;gt;|&amp;lt;/code&amp;gt; (Pipe) – Label-Only (No Checkbox) ===&lt;br /&gt;
&lt;br /&gt;
Prefix a task label with &amp;lt;code&amp;gt;|&amp;lt;/code&amp;gt; to render it as &#039;&#039;&#039;plain text without a checkbox&#039;&#039;&#039;. Useful for section headers, notes, or informational text within a todo list.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Behaviour:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* The &amp;lt;code&amp;gt;|&amp;lt;/code&amp;gt; prefix is stripped from the displayed label&lt;br /&gt;
* No checkbox is rendered&lt;br /&gt;
* The item does not count toward the completed/total counter&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
|Important Notes&lt;br /&gt;
Attend all morning sessions&lt;br /&gt;
|Evening Activities&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Date Variables ==&lt;br /&gt;
&lt;br /&gt;
Task labels support the &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; variable, which is replaced with the event&#039;s start date displayed as day and month numbers (e.g., &#039;&#039;16/06&#039;&#039;).&lt;br /&gt;
&lt;br /&gt;
=== Basic Usage ===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Variable&lt;br /&gt;
! Replaced With&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date (e.g., &#039;&#039;16/06&#039;&#039;)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Offsets ===&lt;br /&gt;
&lt;br /&gt;
You can add or subtract days from the event date using &amp;lt;code&amp;gt;+&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;-&amp;lt;/code&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Variable&lt;br /&gt;
! Replaced With&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate+1}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date + 1 day&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate-1}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date − 1 day&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate+3}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date + 3 days&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate-2}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date − 2 days&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Whitespace inside the braces is tolerated:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{ EventDate + 1 }}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; → same as &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate+1}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate- 2}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; → same as &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate-2}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Unknown variables (anything other than &#039;&#039;EventDate&#039;&#039;) are left as-is.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
{{EventDate}} Check-in at hotel&lt;br /&gt;
{{EventDate+1}} Follow-up meeting&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Combining Prefixes and Variables ==&lt;br /&gt;
&lt;br /&gt;
Prefixes and date variables can be used together:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
|Schedule for {{EventDate}}&lt;br /&gt;
Morning briefing&lt;br /&gt;
. Afternoon workshop&lt;br /&gt;
. Evening networking&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=Custom_Todos&amp;diff=968</id>
		<title>Custom Todos</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=Custom_Todos&amp;diff=968"/>
		<updated>2026-06-17T13:58:52Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Infobox Feature&lt;br /&gt;
 | name = Custom Todos&lt;br /&gt;
 | version = [[Release 3.5.0|3.5.0]]&lt;br /&gt;
 | tier = Standard, Premium and Enterprise&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot 2026-06-17 at 14.57.14.png|thumb|Example: Input - ECH custom Todo]]&lt;br /&gt;
[[File:App-custom-todo.png|thumb|Example: Output - App custom Todo]]&lt;br /&gt;
&lt;br /&gt;
= TODO Task Label Prefixes &amp;amp; Variables =&lt;br /&gt;
&lt;br /&gt;
TODO task labels support special prefixes and variables that control how tasks are rendered in the UI.&lt;br /&gt;
&lt;br /&gt;
== Prefixes ==&lt;br /&gt;
&lt;br /&gt;
Prefixes are detected by examining the &#039;&#039;&#039;first character&#039;&#039;&#039; of the label after trimming leading whitespace.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;.&#039;&#039; (Dot) – Inline/Child Tasks ===&lt;br /&gt;
&lt;br /&gt;
Prefix a task label with &amp;lt;code&amp;gt;.&amp;lt;/code&amp;gt; to make it an &#039;&#039;&#039;inline child&#039;&#039;&#039; of the preceding non-dot task. Child tasks are displayed in a grid row alongside their parent, creating a compact horizontal layout.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Behaviour:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* The &amp;lt;code&amp;gt;.&amp;lt;/code&amp;gt; prefix is stripped from the displayed label&lt;br /&gt;
* The task is grouped with the previous non-dot task as a child&lt;br /&gt;
* Displayed in a shared grid row (parent + children side by side)&lt;br /&gt;
* Checkbox is still shown (can be checked/unchecked)&lt;br /&gt;
* If a dot-prefixed task appears without a preceding parent, it is treated as a regular individual task&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
Monday Breakfast&lt;br /&gt;
.Lunch&lt;br /&gt;
.Dinner&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== &amp;lt;code&amp;gt;|&amp;lt;/code&amp;gt; (Pipe) – Label-Only (No Checkbox) ===&lt;br /&gt;
&lt;br /&gt;
Prefix a task label with &amp;lt;code&amp;gt;|&amp;lt;/code&amp;gt; to render it as &#039;&#039;&#039;plain text without a checkbox&#039;&#039;&#039;. Useful for section headers, notes, or informational text within a todo list.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Behaviour:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* The &amp;lt;code&amp;gt;|&amp;lt;/code&amp;gt; prefix is stripped from the displayed label&lt;br /&gt;
* No checkbox is rendered&lt;br /&gt;
* The item does not count toward the completed/total counter&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
|Important Notes&lt;br /&gt;
Attend all morning sessions&lt;br /&gt;
|Evening Activities&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Date Variables ==&lt;br /&gt;
&lt;br /&gt;
Task labels support the &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; variable, which is replaced with the event&#039;s start date displayed as day and month numbers (e.g., &#039;&#039;16/06&#039;&#039;).&lt;br /&gt;
&lt;br /&gt;
=== Basic Usage ===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Variable&lt;br /&gt;
! Replaced With&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date (e.g., &#039;&#039;16/06&#039;&#039;)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Offsets ===&lt;br /&gt;
&lt;br /&gt;
You can add or subtract days from the event date using &amp;lt;code&amp;gt;+&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;-&amp;lt;/code&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Variable&lt;br /&gt;
! Replaced With&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate+1}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date + 1 day&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate-1}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date − 1 day&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate+3}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date + 3 days&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate-2}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date − 2 days&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Whitespace inside the braces is tolerated:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{ EventDate + 1 }}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; → same as &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate+1}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate- 2}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; → same as &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate-2}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Unknown variables (anything other than &#039;&#039;EventDate&#039;&#039;) are left as-is.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
{{EventDate}} Check-in at hotel&lt;br /&gt;
{{EventDate+1}} Follow-up meeting&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Combining Prefixes and Variables ==&lt;br /&gt;
&lt;br /&gt;
Prefixes and date variables can be used together:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
|Schedule for {{EventDate}}&lt;br /&gt;
Morning briefing&lt;br /&gt;
. Afternoon workshop&lt;br /&gt;
. Evening networking&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=Custom_Todos&amp;diff=967</id>
		<title>Custom Todos</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=Custom_Todos&amp;diff=967"/>
		<updated>2026-06-17T13:57:47Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Screenshot 2026-06-17 at 14.57.14.png|thumb|Example: Input - ECH custom Todo]]&lt;br /&gt;
[[File:App-custom-todo.png|thumb|Example: Output - App custom Todo]]&lt;br /&gt;
&lt;br /&gt;
= TODO Task Label Prefixes &amp;amp; Variables =&lt;br /&gt;
&lt;br /&gt;
TODO task labels support special prefixes and variables that control how tasks are rendered in the UI.&lt;br /&gt;
&lt;br /&gt;
== Prefixes ==&lt;br /&gt;
&lt;br /&gt;
Prefixes are detected by examining the &#039;&#039;&#039;first character&#039;&#039;&#039; of the label after trimming leading whitespace.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;.&#039;&#039; (Dot) – Inline/Child Tasks ===&lt;br /&gt;
&lt;br /&gt;
Prefix a task label with &amp;lt;code&amp;gt;.&amp;lt;/code&amp;gt; to make it an &#039;&#039;&#039;inline child&#039;&#039;&#039; of the preceding non-dot task. Child tasks are displayed in a grid row alongside their parent, creating a compact horizontal layout.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Behaviour:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* The &amp;lt;code&amp;gt;.&amp;lt;/code&amp;gt; prefix is stripped from the displayed label&lt;br /&gt;
* The task is grouped with the previous non-dot task as a child&lt;br /&gt;
* Displayed in a shared grid row (parent + children side by side)&lt;br /&gt;
* Checkbox is still shown (can be checked/unchecked)&lt;br /&gt;
* If a dot-prefixed task appears without a preceding parent, it is treated as a regular individual task&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
Monday Breakfast&lt;br /&gt;
.Lunch&lt;br /&gt;
.Dinner&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== &amp;lt;code&amp;gt;|&amp;lt;/code&amp;gt; (Pipe) – Label-Only (No Checkbox) ===&lt;br /&gt;
&lt;br /&gt;
Prefix a task label with &amp;lt;code&amp;gt;|&amp;lt;/code&amp;gt; to render it as &#039;&#039;&#039;plain text without a checkbox&#039;&#039;&#039;. Useful for section headers, notes, or informational text within a todo list.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Behaviour:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* The &amp;lt;code&amp;gt;|&amp;lt;/code&amp;gt; prefix is stripped from the displayed label&lt;br /&gt;
* No checkbox is rendered&lt;br /&gt;
* The item does not count toward the completed/total counter&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
|Important Notes&lt;br /&gt;
Attend all morning sessions&lt;br /&gt;
|Evening Activities&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Date Variables ==&lt;br /&gt;
&lt;br /&gt;
Task labels support the &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; variable, which is replaced with the event&#039;s start date displayed as day and month numbers (e.g., &#039;&#039;16/06&#039;&#039;).&lt;br /&gt;
&lt;br /&gt;
=== Basic Usage ===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Variable&lt;br /&gt;
! Replaced With&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date (e.g., &#039;&#039;16/06&#039;&#039;)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Offsets ===&lt;br /&gt;
&lt;br /&gt;
You can add or subtract days from the event date using &amp;lt;code&amp;gt;+&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;-&amp;lt;/code&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Variable&lt;br /&gt;
! Replaced With&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate+1}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date + 1 day&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate-1}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date − 1 day&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate+3}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date + 3 days&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate-2}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date − 2 days&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Whitespace inside the braces is tolerated:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{ EventDate + 1 }}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; → same as &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate+1}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate- 2}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; → same as &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate-2}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Unknown variables (anything other than &#039;&#039;EventDate&#039;&#039;) are left as-is.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
{{EventDate}} Check-in at hotel&lt;br /&gt;
{{EventDate+1}} Follow-up meeting&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Combining Prefixes and Variables ==&lt;br /&gt;
&lt;br /&gt;
Prefixes and date variables can be used together:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
|Schedule for {{EventDate}}&lt;br /&gt;
Morning briefing&lt;br /&gt;
. Afternoon workshop&lt;br /&gt;
. Evening networking&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=File:Screenshot_2026-06-17_at_14.57.14.png&amp;diff=966</id>
		<title>File:Screenshot 2026-06-17 at 14.57.14.png</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=File:Screenshot_2026-06-17_at_14.57.14.png&amp;diff=966"/>
		<updated>2026-06-17T13:57:43Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Example custom todo ECH input&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=File:App-custom-todo.png&amp;diff=965</id>
		<title>File:App-custom-todo.png</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=File:App-custom-todo.png&amp;diff=965"/>
		<updated>2026-06-17T13:55:43Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;App custom todo example output&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=Custom_Todos&amp;diff=964</id>
		<title>Custom Todos</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=Custom_Todos&amp;diff=964"/>
		<updated>2026-06-17T13:53:43Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Ech custom todo.png|thumb|Example: Input - ECH custom Todo]]&lt;br /&gt;
&lt;br /&gt;
[[File:App custom todo.png|thumb|Example: Output - App custom Todo]]&lt;br /&gt;
&lt;br /&gt;
= TODO Task Label Prefixes &amp;amp; Variables =&lt;br /&gt;
&lt;br /&gt;
TODO task labels support special prefixes and variables that control how tasks are rendered in the UI.&lt;br /&gt;
&lt;br /&gt;
== Prefixes ==&lt;br /&gt;
&lt;br /&gt;
Prefixes are detected by examining the &#039;&#039;&#039;first character&#039;&#039;&#039; of the label after trimming leading whitespace.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;.&#039;&#039; (Dot) – Inline/Child Tasks ===&lt;br /&gt;
&lt;br /&gt;
Prefix a task label with &amp;lt;code&amp;gt;.&amp;lt;/code&amp;gt; to make it an &#039;&#039;&#039;inline child&#039;&#039;&#039; of the preceding non-dot task. Child tasks are displayed in a grid row alongside their parent, creating a compact horizontal layout.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Behaviour:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* The &amp;lt;code&amp;gt;.&amp;lt;/code&amp;gt; prefix is stripped from the displayed label&lt;br /&gt;
* The task is grouped with the previous non-dot task as a child&lt;br /&gt;
* Displayed in a shared grid row (parent + children side by side)&lt;br /&gt;
* Checkbox is still shown (can be checked/unchecked)&lt;br /&gt;
* If a dot-prefixed task appears without a preceding parent, it is treated as a regular individual task&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
Monday Breakfast&lt;br /&gt;
.Lunch&lt;br /&gt;
.Dinner&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== &amp;lt;code&amp;gt;|&amp;lt;/code&amp;gt; (Pipe) – Label-Only (No Checkbox) ===&lt;br /&gt;
&lt;br /&gt;
Prefix a task label with &amp;lt;code&amp;gt;|&amp;lt;/code&amp;gt; to render it as &#039;&#039;&#039;plain text without a checkbox&#039;&#039;&#039;. Useful for section headers, notes, or informational text within a todo list.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Behaviour:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* The &amp;lt;code&amp;gt;|&amp;lt;/code&amp;gt; prefix is stripped from the displayed label&lt;br /&gt;
* No checkbox is rendered&lt;br /&gt;
* The item does not count toward the completed/total counter&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
|Important Notes&lt;br /&gt;
Attend all morning sessions&lt;br /&gt;
|Evening Activities&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Date Variables ==&lt;br /&gt;
&lt;br /&gt;
Task labels support the &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; variable, which is replaced with the event&#039;s start date displayed as day and month numbers (e.g., &#039;&#039;16/06&#039;&#039;).&lt;br /&gt;
&lt;br /&gt;
=== Basic Usage ===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Variable&lt;br /&gt;
! Replaced With&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date (e.g., &#039;&#039;16/06&#039;&#039;)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Offsets ===&lt;br /&gt;
&lt;br /&gt;
You can add or subtract days from the event date using &amp;lt;code&amp;gt;+&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;-&amp;lt;/code&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Variable&lt;br /&gt;
! Replaced With&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate+1}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date + 1 day&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate-1}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date − 1 day&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate+3}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date + 3 days&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate-2}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date − 2 days&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Whitespace inside the braces is tolerated:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{ EventDate + 1 }}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; → same as &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate+1}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate- 2}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; → same as &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate-2}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Unknown variables (anything other than &#039;&#039;EventDate&#039;&#039;) are left as-is.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
{{EventDate}} Check-in at hotel&lt;br /&gt;
{{EventDate+1}} Follow-up meeting&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Combining Prefixes and Variables ==&lt;br /&gt;
&lt;br /&gt;
Prefixes and date variables can be used together:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
|Schedule for {{EventDate}}&lt;br /&gt;
Morning briefing&lt;br /&gt;
. Afternoon workshop&lt;br /&gt;
. Evening networking&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=File:App_custom_todo.png&amp;diff=963</id>
		<title>File:App custom todo.png</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=File:App_custom_todo.png&amp;diff=963"/>
		<updated>2026-06-17T13:53:18Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;App custom todo output&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=Custom_Todos&amp;diff=962</id>
		<title>Custom Todos</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=Custom_Todos&amp;diff=962"/>
		<updated>2026-06-17T13:52:59Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:Ech custom todo.png|thumb|Example: Input - ECH custom Todo]]&lt;br /&gt;
&lt;br /&gt;
= TODO Task Label Prefixes &amp;amp; Variables =&lt;br /&gt;
&lt;br /&gt;
TODO task labels support special prefixes and variables that control how tasks are rendered in the UI.&lt;br /&gt;
&lt;br /&gt;
== Prefixes ==&lt;br /&gt;
&lt;br /&gt;
Prefixes are detected by examining the &#039;&#039;&#039;first character&#039;&#039;&#039; of the label after trimming leading whitespace.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;.&#039;&#039; (Dot) – Inline/Child Tasks ===&lt;br /&gt;
&lt;br /&gt;
Prefix a task label with &amp;lt;code&amp;gt;.&amp;lt;/code&amp;gt; to make it an &#039;&#039;&#039;inline child&#039;&#039;&#039; of the preceding non-dot task. Child tasks are displayed in a grid row alongside their parent, creating a compact horizontal layout.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Behaviour:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* The &amp;lt;code&amp;gt;.&amp;lt;/code&amp;gt; prefix is stripped from the displayed label&lt;br /&gt;
* The task is grouped with the previous non-dot task as a child&lt;br /&gt;
* Displayed in a shared grid row (parent + children side by side)&lt;br /&gt;
* Checkbox is still shown (can be checked/unchecked)&lt;br /&gt;
* If a dot-prefixed task appears without a preceding parent, it is treated as a regular individual task&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
Monday Breakfast&lt;br /&gt;
.Lunch&lt;br /&gt;
.Dinner&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== &amp;lt;code&amp;gt;|&amp;lt;/code&amp;gt; (Pipe) – Label-Only (No Checkbox) ===&lt;br /&gt;
&lt;br /&gt;
Prefix a task label with &amp;lt;code&amp;gt;|&amp;lt;/code&amp;gt; to render it as &#039;&#039;&#039;plain text without a checkbox&#039;&#039;&#039;. Useful for section headers, notes, or informational text within a todo list.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Behaviour:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* The &amp;lt;code&amp;gt;|&amp;lt;/code&amp;gt; prefix is stripped from the displayed label&lt;br /&gt;
* No checkbox is rendered&lt;br /&gt;
* The item does not count toward the completed/total counter&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
|Important Notes&lt;br /&gt;
Attend all morning sessions&lt;br /&gt;
|Evening Activities&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Date Variables ==&lt;br /&gt;
&lt;br /&gt;
Task labels support the &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; variable, which is replaced with the event&#039;s start date displayed as day and month numbers (e.g., &#039;&#039;16/06&#039;&#039;).&lt;br /&gt;
&lt;br /&gt;
=== Basic Usage ===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Variable&lt;br /&gt;
! Replaced With&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date (e.g., &#039;&#039;16/06&#039;&#039;)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Offsets ===&lt;br /&gt;
&lt;br /&gt;
You can add or subtract days from the event date using &amp;lt;code&amp;gt;+&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;-&amp;lt;/code&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Variable&lt;br /&gt;
! Replaced With&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate+1}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date + 1 day&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate-1}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date − 1 day&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate+3}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date + 3 days&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate-2}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date − 2 days&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Whitespace inside the braces is tolerated:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{ EventDate + 1 }}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; → same as &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate+1}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate- 2}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; → same as &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate-2}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Unknown variables (anything other than &#039;&#039;EventDate&#039;&#039;) are left as-is.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
{{EventDate}} Check-in at hotel&lt;br /&gt;
{{EventDate+1}} Follow-up meeting&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Combining Prefixes and Variables ==&lt;br /&gt;
&lt;br /&gt;
Prefixes and date variables can be used together:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
|Schedule for {{EventDate}}&lt;br /&gt;
Morning briefing&lt;br /&gt;
. Afternoon workshop&lt;br /&gt;
. Evening networking&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=File:Ech_custom_todo.png&amp;diff=961</id>
		<title>File:Ech custom todo.png</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=File:Ech_custom_todo.png&amp;diff=961"/>
		<updated>2026-06-17T13:52:29Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Example: ECH custom todos&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=Custom_Todos&amp;diff=960</id>
		<title>Custom Todos</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=Custom_Todos&amp;diff=960"/>
		<updated>2026-06-17T13:22:44Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= TODO Task Label Prefixes &amp;amp; Variables =&lt;br /&gt;
&lt;br /&gt;
TODO task labels support special prefixes and variables that control how tasks are rendered in the UI.&lt;br /&gt;
&lt;br /&gt;
== Prefixes ==&lt;br /&gt;
&lt;br /&gt;
Prefixes are detected by examining the &#039;&#039;&#039;first character&#039;&#039;&#039; of the label after trimming leading whitespace.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;.&#039;&#039; (Dot) – Inline/Child Tasks ===&lt;br /&gt;
&lt;br /&gt;
Prefix a task label with &amp;lt;code&amp;gt;.&amp;lt;/code&amp;gt; to make it an &#039;&#039;&#039;inline child&#039;&#039;&#039; of the preceding non-dot task. Child tasks are displayed in a grid row alongside their parent, creating a compact horizontal layout.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Behaviour:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* The &amp;lt;code&amp;gt;.&amp;lt;/code&amp;gt; prefix is stripped from the displayed label&lt;br /&gt;
* The task is grouped with the previous non-dot task as a child&lt;br /&gt;
* Displayed in a shared grid row (parent + children side by side)&lt;br /&gt;
* Checkbox is still shown (can be checked/unchecked)&lt;br /&gt;
* If a dot-prefixed task appears without a preceding parent, it is treated as a regular individual task&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
Monday Breakfast&lt;br /&gt;
.Lunch&lt;br /&gt;
.Dinner&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== &amp;lt;code&amp;gt;|&amp;lt;/code&amp;gt; (Pipe) – Label-Only (No Checkbox) ===&lt;br /&gt;
&lt;br /&gt;
Prefix a task label with &amp;lt;code&amp;gt;|&amp;lt;/code&amp;gt; to render it as &#039;&#039;&#039;plain text without a checkbox&#039;&#039;&#039;. Useful for section headers, notes, or informational text within a todo list.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Behaviour:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* The &amp;lt;code&amp;gt;|&amp;lt;/code&amp;gt; prefix is stripped from the displayed label&lt;br /&gt;
* No checkbox is rendered&lt;br /&gt;
* The item does not count toward the completed/total counter&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
|Important Notes&lt;br /&gt;
Attend all morning sessions&lt;br /&gt;
|Evening Activities&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Date Variables ==&lt;br /&gt;
&lt;br /&gt;
Task labels support the &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; variable, which is replaced with the event&#039;s start date displayed as day and month numbers (e.g., &#039;&#039;16/06&#039;&#039;).&lt;br /&gt;
&lt;br /&gt;
=== Basic Usage ===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Variable&lt;br /&gt;
! Replaced With&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date (e.g., &#039;&#039;16/06&#039;&#039;)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Offsets ===&lt;br /&gt;
&lt;br /&gt;
You can add or subtract days from the event date using &amp;lt;code&amp;gt;+&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;-&amp;lt;/code&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Variable&lt;br /&gt;
! Replaced With&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate+1}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date + 1 day&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate-1}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date − 1 day&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate+3}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date + 3 days&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate-2}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date − 2 days&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Whitespace inside the braces is tolerated:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{ EventDate + 1 }}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; → same as &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate+1}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
* &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate- 2}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt; → same as &amp;lt;code&amp;gt;&amp;lt;nowiki&amp;gt;{{EventDate-2}}&amp;lt;/nowiki&amp;gt;&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Unknown variables (anything other than &#039;&#039;EventDate&#039;&#039;) are left as-is.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
{{EventDate}} Check-in at hotel&lt;br /&gt;
{{EventDate+1}} Follow-up meeting&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Combining Prefixes and Variables ==&lt;br /&gt;
&lt;br /&gt;
Prefixes and date variables can be used together:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
|Schedule for {{EventDate}}&lt;br /&gt;
Morning briefing&lt;br /&gt;
. Afternoon workshop&lt;br /&gt;
. Evening networking&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=Custom_Todos&amp;diff=959</id>
		<title>Custom Todos</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=Custom_Todos&amp;diff=959"/>
		<updated>2026-06-17T13:19:43Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= TODO Task Label Prefixes &amp;amp; Variables =&lt;br /&gt;
&lt;br /&gt;
TODO task labels support special prefixes and variables that control how tasks are rendered in the UI.&lt;br /&gt;
&lt;br /&gt;
== Prefixes ==&lt;br /&gt;
&lt;br /&gt;
Prefixes are detected by examining the &#039;&#039;&#039;first character&#039;&#039;&#039; of the label after trimming leading whitespace.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;.&#039;&#039; (Dot) – Inline/Child Tasks ===&lt;br /&gt;
&lt;br /&gt;
Prefix a task label with &amp;lt;code&amp;gt;.&amp;lt;/code&amp;gt; to make it an &#039;&#039;&#039;inline child&#039;&#039;&#039; of the preceding non-dot task. Child tasks are displayed in a grid row alongside their parent, creating a compact horizontal layout.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Behaviour:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* The &amp;lt;code&amp;gt;.&amp;lt;/code&amp;gt; prefix is stripped from the displayed label&lt;br /&gt;
* The task is grouped with the previous non-dot task as a child&lt;br /&gt;
* Displayed in a shared grid row (parent + children side by side)&lt;br /&gt;
* Checkbox is still shown (can be checked/unchecked)&lt;br /&gt;
* If a dot-prefixed task appears without a preceding parent, it is treated as a regular individual task&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
Monday Breakfast&lt;br /&gt;
.Lunch&lt;br /&gt;
.Dinner&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== &amp;lt;code&amp;gt;|&amp;lt;/code&amp;gt; (Pipe) – Label-Only (No Checkbox) ===&lt;br /&gt;
&lt;br /&gt;
Prefix a task label with &amp;lt;code&amp;gt;|&amp;lt;/code&amp;gt; to render it as &#039;&#039;&#039;plain text without a checkbox&#039;&#039;&#039;. Useful for section headers, notes, or informational text within a todo list.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Behaviour:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* The &amp;lt;code&amp;gt;|&amp;lt;/code&amp;gt; prefix is stripped from the displayed label&lt;br /&gt;
* No checkbox is rendered&lt;br /&gt;
* The item does not count toward the completed/total counter&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
|Important Notes&lt;br /&gt;
Attend all morning sessions&lt;br /&gt;
|Evening Activities&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Date Variables ==&lt;br /&gt;
&lt;br /&gt;
Task labels support the &amp;lt;code&amp;gt;{{EventDate}}&amp;lt;/code&amp;gt; variable, which is replaced with the event&#039;s start date displayed as day and month numbers (e.g., &#039;&#039;16/06&#039;&#039;).&lt;br /&gt;
&lt;br /&gt;
=== Basic Usage ===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Variable&lt;br /&gt;
! Replaced With&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;{{EventDate}}&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date (e.g., &#039;&#039;16/06&#039;&#039;)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Offsets ===&lt;br /&gt;
&lt;br /&gt;
You can add or subtract days from the event date using &amp;lt;code&amp;gt;+&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;-&amp;lt;/code&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Variable&lt;br /&gt;
! Replaced With&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;{{EventDate+1}}&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date + 1 day&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;{{EventDate-1}}&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date − 1 day&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;{{EventDate+3}}&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date + 3 days&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;{{EventDate-2}}&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date − 2 days&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Whitespace inside the braces is tolerated:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;{{ EventDate + 1 }}&amp;lt;/code&amp;gt; → same as &amp;lt;code&amp;gt;{{EventDate+1}}&amp;lt;/code&amp;gt;&lt;br /&gt;
* &amp;lt;code&amp;gt;{{EventDate- 2}}&amp;lt;/code&amp;gt; → same as &amp;lt;code&amp;gt;{{EventDate-2}}&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Unknown variables (anything other than &#039;&#039;EventDate&#039;&#039;) are left as-is.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
{{EventDate}} Check-in at hotel&lt;br /&gt;
{{EventDate+1}} Follow-up meeting&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Combining Prefixes and Variables ==&lt;br /&gt;
&lt;br /&gt;
Prefixes and date variables can be used together:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
|Schedule for {{EventDate}}&lt;br /&gt;
Morning briefing&lt;br /&gt;
. Afternoon workshop&lt;br /&gt;
. Evening networking&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=Custom_Todos&amp;diff=958</id>
		<title>Custom Todos</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=Custom_Todos&amp;diff=958"/>
		<updated>2026-06-16T14:53:47Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;= TODO Task Label Prefixes &amp;amp; Variables =&lt;br /&gt;
&lt;br /&gt;
TODO task labels support special prefixes and variables that control how tasks are rendered in the UI.&lt;br /&gt;
&lt;br /&gt;
== Prefixes ==&lt;br /&gt;
&lt;br /&gt;
Prefixes are detected by examining the &#039;&#039;&#039;first character&#039;&#039;&#039; of the label after trimming leading whitespace.&lt;br /&gt;
&lt;br /&gt;
=== &#039;&#039;.&#039;&#039; (Dot) – Inline/Child Tasks ===&lt;br /&gt;
&lt;br /&gt;
Prefix a task label with &amp;lt;code&amp;gt;.&amp;lt;/code&amp;gt; to make it an &#039;&#039;&#039;inline child&#039;&#039;&#039; of the preceding non-dot task. Child tasks are displayed in a grid row alongside their parent, creating a compact horizontal layout.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Behaviour:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* The &amp;lt;code&amp;gt;.&amp;lt;/code&amp;gt; prefix is stripped from the displayed label&lt;br /&gt;
* The task is grouped with the previous non-dot task as a child&lt;br /&gt;
* Displayed in a shared grid row (parent + children side by side)&lt;br /&gt;
* Checkbox is still shown (can be checked/unchecked)&lt;br /&gt;
* If a dot-prefixed task appears without a preceding parent, it is treated as a regular individual task&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
Monday Breakfast&lt;br /&gt;
.Lunch&lt;br /&gt;
.Dinner&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
=== &amp;lt;code&amp;gt;|&amp;lt;/code&amp;gt; (Pipe) – Label-Only (No Checkbox) ===&lt;br /&gt;
&lt;br /&gt;
Prefix a task label with &amp;lt;code&amp;gt;|&amp;lt;/code&amp;gt; to render it as &#039;&#039;&#039;plain text without a checkbox&#039;&#039;&#039;. Useful for section headers, notes, or informational text within a todo list.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Behaviour:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
* The &amp;lt;code&amp;gt;|&amp;lt;/code&amp;gt; prefix is stripped from the displayed label&lt;br /&gt;
* No checkbox is rendered&lt;br /&gt;
* The item does not count toward the completed/total counter&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
|Important Notes&lt;br /&gt;
Attend all morning sessions&lt;br /&gt;
|Evening Activities&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Date Variables ==&lt;br /&gt;
&lt;br /&gt;
Task labels support the &amp;lt;code&amp;gt;{{{EventDate}}}&amp;lt;/code&amp;gt; variable, which is replaced with the event&#039;s start date displayed as day and month numbers (e.g., &#039;&#039;16/06&#039;&#039;).&lt;br /&gt;
&lt;br /&gt;
=== Basic Usage ===&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Variable&lt;br /&gt;
! Replaced With&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;{{{EventDate}}}&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date (e.g., &#039;&#039;16/06&#039;&#039;)&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
=== Offsets ===&lt;br /&gt;
&lt;br /&gt;
You can add or subtract days from the event date using &amp;lt;code&amp;gt;+&amp;lt;/code&amp;gt; or &amp;lt;code&amp;gt;-&amp;lt;/code&amp;gt;:&lt;br /&gt;
&lt;br /&gt;
{| class=&amp;quot;wikitable&amp;quot;&lt;br /&gt;
! Variable&lt;br /&gt;
! Replaced With&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;{{{EventDate+1}}}&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date + 1 day&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;{{{EventDate-1}}}&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date − 1 day&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;{{{EventDate+3}}}&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date + 3 days&lt;br /&gt;
|-&lt;br /&gt;
| &amp;lt;code&amp;gt;{{{EventDate-2}}}&amp;lt;/code&amp;gt;&lt;br /&gt;
| Event start date − 2 days&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
Whitespace inside the braces is tolerated:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;{{{ EventDate + 1 }}}&amp;lt;/code&amp;gt; → same as &amp;lt;code&amp;gt;{{{EventDate+1}}}&amp;lt;/code&amp;gt;&lt;br /&gt;
* &amp;lt;code&amp;gt;{{{EventDate- 2}}}&amp;lt;/code&amp;gt; → same as &amp;lt;code&amp;gt;{{{EventDate-2}}}&amp;lt;/code&amp;gt;&lt;br /&gt;
&lt;br /&gt;
Unknown variables (anything other than &#039;&#039;EventDate&#039;&#039;) are left as-is.&lt;br /&gt;
&lt;br /&gt;
&#039;&#039;&#039;Example:&#039;&#039;&#039;&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
{{EventDate}} Check-in at hotel&lt;br /&gt;
{{EventDate+1}} Follow-up meeting&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;br /&gt;
&lt;br /&gt;
== Combining Prefixes and Variables ==&lt;br /&gt;
&lt;br /&gt;
Prefixes and date variables can be used together:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;syntaxhighlight&amp;gt;&lt;br /&gt;
|Schedule for {{EventDate}}&lt;br /&gt;
Morning briefing&lt;br /&gt;
. Afternoon workshop&lt;br /&gt;
. Evening networking&lt;br /&gt;
&amp;lt;/syntaxhighlight&amp;gt;&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=Custom_Todos&amp;diff=957</id>
		<title>Custom Todos</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=Custom_Todos&amp;diff=957"/>
		<updated>2026-06-16T14:47:06Z</updated>

		<summary type="html">&lt;p&gt;Samh: Blanked the page&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=Custom_Todos&amp;diff=956</id>
		<title>Custom Todos</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=Custom_Todos&amp;diff=956"/>
		<updated>2026-06-16T14:46:31Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Shortcuts ==&lt;br /&gt;
&lt;br /&gt;
# TODO Task Label Prefixes &amp;amp; Variables&lt;br /&gt;
&lt;br /&gt;
TODO task labels support special prefixes and variables that control how tasks are rendered in the UI.&lt;br /&gt;
&lt;br /&gt;
## Prefixes&lt;br /&gt;
&lt;br /&gt;
Prefixes are detected by examining the **first character** of the label after trimming leading whitespace.&lt;br /&gt;
&lt;br /&gt;
### `.` (Dot) – Inline/Child Tasks&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
**Behaviour:**&lt;br /&gt;
- The `.` prefix is stripped from the displayed label&lt;br /&gt;
- The task is grouped with the previous non-dot task as a child&lt;br /&gt;
- Displayed in a shared grid row (parent + children side by side)&lt;br /&gt;
- Checkbox is still shown (can be checked/unchecked)&lt;br /&gt;
- If a dot-prefixed task appears without a preceding parent, it is treated as a regular individual task&lt;br /&gt;
&lt;br /&gt;
**Example:**&lt;br /&gt;
```&lt;br /&gt;
Monday Breakfast&lt;br /&gt;
.Lunch&lt;br /&gt;
.Dinner&lt;br /&gt;
```&lt;br /&gt;
Renders as a single row: `[☐ Monday Breakfast] [☐ Lunch] [☐ Dinner]`&lt;br /&gt;
&lt;br /&gt;
### `|` (Pipe) – Label-Only (No Checkbox)&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
**Behaviour:**&lt;br /&gt;
- The `|` prefix is stripped from the displayed label&lt;br /&gt;
- No checkbox is rendered&lt;br /&gt;
- The item does not count toward the completed/total counter&lt;br /&gt;
&lt;br /&gt;
**Example:**&lt;br /&gt;
```&lt;br /&gt;
|Important Notes&lt;br /&gt;
Attend all morning sessions&lt;br /&gt;
|Evening Activities&lt;br /&gt;
```&lt;br /&gt;
Renders as:&lt;br /&gt;
```&lt;br /&gt;
Important Notes          (plain text, no checkbox)&lt;br /&gt;
[☐ Attend all morning sessions]&lt;br /&gt;
&lt;br /&gt;
Evening Activities       (plain text, no checkbox)&lt;br /&gt;
```&lt;br /&gt;
&lt;br /&gt;
## Date Variables&lt;br /&gt;
&lt;br /&gt;
Task labels support the `{{EventDate}}` variable, which is replaced with the event&#039;s start date displayed as day and month numbers (e.g., `16/06`).&lt;br /&gt;
&lt;br /&gt;
### Basic Usage&lt;br /&gt;
&lt;br /&gt;
| Variable | Replaced With |&lt;br /&gt;
|---|---|&lt;br /&gt;
| `{{EventDate}}` | Event start date (e.g., `16/06`) |&lt;br /&gt;
&lt;br /&gt;
### Offsets&lt;br /&gt;
&lt;br /&gt;
You can add or subtract days from the event date using `+` or `-`:&lt;br /&gt;
&lt;br /&gt;
| Variable | Replaced With |&lt;br /&gt;
|---|---|&lt;br /&gt;
| `{{EventDate+1}}` | Event start date + 1 day |&lt;br /&gt;
| `{{EventDate-1}}` | Event start date − 1 day |&lt;br /&gt;
| `{{EventDate+3}}` | Event start date + 3 days |&lt;br /&gt;
| `{{EventDate-2}}` | Event start date − 2 days |&lt;br /&gt;
&lt;br /&gt;
Whitespace inside the braces is tolerated:&lt;br /&gt;
&lt;br /&gt;
- `{{ EventDate + 1 }}` → same as `{{EventDate+1}}`&lt;br /&gt;
- `{{EventDate- 2}}` → same as `{{EventDate-2}}`&lt;br /&gt;
&lt;br /&gt;
Unknown variables (anything other than `EventDate`) are left as-is.&lt;br /&gt;
&lt;br /&gt;
**Example:**&lt;br /&gt;
```&lt;br /&gt;
{{EventDate}} Check-in at hotel&lt;br /&gt;
{{EventDate+1}} Follow-up meeting&lt;br /&gt;
```&lt;br /&gt;
Renders as: `16/06 Check-in at hotel`, `17/06 Follow-up meeting` (assuming event starts June 16)&lt;br /&gt;
&lt;br /&gt;
## Combining Prefixes and Variables&lt;br /&gt;
&lt;br /&gt;
Prefixes and date variables can be used together:&lt;br /&gt;
&lt;br /&gt;
```&lt;br /&gt;
|Schedule for {{EventDate}}&lt;br /&gt;
Morning briefing&lt;br /&gt;
. Afternoon workshop&lt;br /&gt;
. Evening networking&lt;br /&gt;
```&lt;br /&gt;
&lt;br /&gt;
---&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=Custom_Todos&amp;diff=955</id>
		<title>Custom Todos</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=Custom_Todos&amp;diff=955"/>
		<updated>2026-06-16T14:45:37Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Shortcuts ==&lt;br /&gt;
&lt;br /&gt;
# TODO Task Label Prefixes &amp;amp; Variables&lt;br /&gt;
&lt;br /&gt;
TODO task labels support special prefixes and variables that control how tasks are rendered in the UI.&lt;br /&gt;
&lt;br /&gt;
## Prefixes&lt;br /&gt;
&lt;br /&gt;
Prefixes are detected by examining the **first character** of the label after trimming leading whitespace.&lt;br /&gt;
&lt;br /&gt;
### `.` (Dot) – Inline/Child Tasks&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
**Behaviour:**&lt;br /&gt;
- The `.` prefix is stripped from the displayed label&lt;br /&gt;
- The task is grouped with the previous non-dot task as a child&lt;br /&gt;
- Displayed in a shared grid row (parent + children side by side)&lt;br /&gt;
- Checkbox is still shown (can be checked/unchecked)&lt;br /&gt;
- If a dot-prefixed task appears without a preceding parent, it is treated as a regular individual task&lt;br /&gt;
&lt;br /&gt;
**Example:**&lt;br /&gt;
```&lt;br /&gt;
Monday Breakfast&lt;br /&gt;
.Lunch&lt;br /&gt;
.Dinner&lt;br /&gt;
```&lt;br /&gt;
Renders as a single row: `[☐ Monday Breakfast] [☐ Lunch] [☐ Dinner]`&lt;br /&gt;
&lt;br /&gt;
### `|` (Pipe) – Label-Only (No Checkbox)&lt;br /&gt;
&lt;br /&gt;
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.&lt;br /&gt;
&lt;br /&gt;
**Behaviour:**&lt;br /&gt;
- The `|` prefix is stripped from the displayed label&lt;br /&gt;
- No checkbox is rendered&lt;br /&gt;
- The item does not count toward the completed/total counter&lt;br /&gt;
&lt;br /&gt;
**Example:**&lt;br /&gt;
```&lt;br /&gt;
|Important Notes&lt;br /&gt;
Attend all morning sessions&lt;br /&gt;
|Evening Activities&lt;br /&gt;
```&lt;br /&gt;
Renders as:&lt;br /&gt;
```&lt;br /&gt;
Important Notes          (plain text, no checkbox)&lt;br /&gt;
[☐ Attend all morning sessions]&lt;br /&gt;
&lt;br /&gt;
Evening Activities       (plain text, no checkbox)&lt;br /&gt;
```&lt;br /&gt;
&lt;br /&gt;
## Date Variables&lt;br /&gt;
&lt;br /&gt;
Task labels support the `{{EventDate}}` variable, which is replaced with the event&#039;s start date displayed as day and month numbers (e.g., `16/06`).&lt;br /&gt;
&lt;br /&gt;
### Basic Usage&lt;br /&gt;
&lt;br /&gt;
| Variable | Replaced With |&lt;br /&gt;
|---|---|&lt;br /&gt;
| `{{EventDate}}` | Event start date (e.g., `16/06`) |&lt;br /&gt;
&lt;br /&gt;
### Offsets&lt;br /&gt;
&lt;br /&gt;
You can add or subtract days from the event date using `+` or `-`:&lt;br /&gt;
&lt;br /&gt;
| Variable | Replaced With |&lt;br /&gt;
|---|---|&lt;br /&gt;
| `{{EventDate+1}}` | Event start date + 1 day |&lt;br /&gt;
| `{{EventDate-1}}` | Event start date − 1 day |&lt;br /&gt;
| `{{EventDate+3}}` | Event start date + 3 days |&lt;br /&gt;
| `{{EventDate-2}}` | Event start date − 2 days |&lt;br /&gt;
&lt;br /&gt;
Whitespace inside the braces is tolerated:&lt;br /&gt;
&lt;br /&gt;
- `{{ EventDate + 1 }}` → same as `{{EventDate+1}}`&lt;br /&gt;
- `{{EventDate- 2}}` → same as `{{EventDate-2}}`&lt;br /&gt;
&lt;br /&gt;
Unknown variables (anything other than `EventDate`) are left as-is.&lt;br /&gt;
&lt;br /&gt;
**Example:**&lt;br /&gt;
```&lt;br /&gt;
{{EventDate}} Check-in at hotel&lt;br /&gt;
{{EventDate+1}} Follow-up meeting&lt;br /&gt;
```&lt;br /&gt;
Renders as: `16/06 Check-in at hotel`, `17/06 Follow-up meeting` (assuming event starts June 16)&lt;br /&gt;
&lt;br /&gt;
## Combining Prefixes and Variables&lt;br /&gt;
&lt;br /&gt;
Prefixes and date variables can be used together:&lt;br /&gt;
&lt;br /&gt;
```&lt;br /&gt;
|Schedule for {{EventDate}}&lt;br /&gt;
Morning briefing&lt;br /&gt;
. Afternoon workshop&lt;br /&gt;
. Evening networking&lt;br /&gt;
```&lt;br /&gt;
&lt;br /&gt;
---&lt;br /&gt;
&lt;br /&gt;
Once you&#039;re satisfied with this documentation, please **toggle to Act mode** so I can write it to a file for you.&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=Custom_Todos&amp;diff=954</id>
		<title>Custom Todos</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=Custom_Todos&amp;diff=954"/>
		<updated>2026-06-16T14:39:08Z</updated>

		<summary type="html">&lt;p&gt;Samh: Created page with &amp;quot;== Shortcuts ==&amp;quot;&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;== Shortcuts ==&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=Orders&amp;diff=688</id>
		<title>Orders</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=Orders&amp;diff=688"/>
		<updated>2026-05-14T15:52:53Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Infobox Feature&lt;br /&gt;
 | name = Rooming Lists&lt;br /&gt;
 | version = 3.4.1 (BETA)&lt;br /&gt;
 | tier = Standard, Premium and Enterprise&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
= Overview =&lt;br /&gt;
The &#039;&#039;&#039;Rooming List&#039;&#039;&#039; feature allows users to create, manage, save, and generate accommodation request PDFs for hotels or accommodation suppliers. It acts as a central workspace for collecting stay requirements, guest accommodation preferences, and booking details related to an itinerary. &lt;br /&gt;
&lt;br /&gt;
= Accessing Rooming Lists =&lt;br /&gt;
{| style=&amp;quot;width:100%; margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width:60%; vertical-align:top;&amp;quot; |&lt;br /&gt;
To find the rooming list functionality, select &#039;&#039;&#039;Create Rooming List&#039;&#039;&#039; from the itinerary accommodation section in the ECH. This opens the Rooming List workspace in a full-screen modal.&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:40%; vertical-align:top;&amp;quot; |&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.21.54.png|thumb| When you have no existing accommodations, button is located bottom centre. ]]&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.38.33.png|thumb|Button moves into the header when you have existing accommodations.]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
= Managing Rooming Lists =&lt;br /&gt;
{| style=&amp;quot;width:100%; margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width:60%; vertical-align:top;&amp;quot; |New rooming lists begin as unsaved drafts until they are saved.&lt;br /&gt;
&lt;br /&gt;
When creating a new rooming list, the form is automatically pre-filled using information from the selected itinerary, including dates, location, and lead booker details (You) where available.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Layout Overview ===&lt;br /&gt;
The Rooming List workspace is divided into four main sections:&lt;br /&gt;
&lt;br /&gt;
* Top Bar&lt;br /&gt;
* Sidebar&lt;br /&gt;
* Main Form&lt;br /&gt;
* Bottom Bar&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Top Bar ==&lt;br /&gt;
&lt;br /&gt;
=== Reset ===&lt;br /&gt;
Restores the currently selected rooming list back to its last saved state.&lt;br /&gt;
&lt;br /&gt;
If editing a new unsaved draft, the form will revert to its original pre-filled itinerary values.&lt;br /&gt;
&lt;br /&gt;
=== Create New ===&lt;br /&gt;
Creates a new unsaved rooming list draft while keeping the current modal open.&lt;br /&gt;
&lt;br /&gt;
If unsaved changes exist, the user will be prompted to save or discard them before continuing.&lt;br /&gt;
&lt;br /&gt;
=== Close ===&lt;br /&gt;
Closes the Rooming List modal.&lt;br /&gt;
&lt;br /&gt;
If there are unsaved changes, the user will be prompted to save or discard the draft before closing.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Sidebar ==&lt;br /&gt;
The sidebar contains all saved rooming lists for the currently selected itinerary.&lt;br /&gt;
&lt;br /&gt;
=== Search ===&lt;br /&gt;
Filters saved rooming lists by title.&lt;br /&gt;
&lt;br /&gt;
=== Refresh ===&lt;br /&gt;
Reloads the latest rooming lists from the server without closing the modal.&lt;br /&gt;
&lt;br /&gt;
=== Rooming List Entries ===&lt;br /&gt;
Displays all saved rooming lists ordered by most recently updated first.&lt;br /&gt;
&lt;br /&gt;
Each entry displays:&lt;br /&gt;
&lt;br /&gt;
* Rooming list title&lt;br /&gt;
* Last modified date and time&lt;br /&gt;
&lt;br /&gt;
Selecting a different rooming list will load its saved data into the form.&lt;br /&gt;
&lt;br /&gt;
If unsaved changes exist, the user will be prompted to save or discard them before switching.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Bottom Bar ==&lt;br /&gt;
&lt;br /&gt;
=== Save ===&lt;br /&gt;
Saves the current rooming list.&lt;br /&gt;
&lt;br /&gt;
Once saved:&lt;br /&gt;
&lt;br /&gt;
* The rooming list becomes persistent&lt;br /&gt;
* It appears in the sidebar&lt;br /&gt;
* Future edits can be restored using Reset&lt;br /&gt;
&lt;br /&gt;
=== Delete ===&lt;br /&gt;
Deletes the currently selected saved rooming list.&lt;br /&gt;
&lt;br /&gt;
This action cannot be undone.&lt;br /&gt;
&lt;br /&gt;
If working on an unsaved draft, this button instead discards the draft.&lt;br /&gt;
&lt;br /&gt;
=== Generate PDF ===&lt;br /&gt;
Generates a PDF version of the current rooming list using all entered form data.&lt;br /&gt;
&lt;br /&gt;
The PDF is designed for sharing with hotels, accommodation providers, or booking agents.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Form Fields ==&lt;br /&gt;
&lt;br /&gt;
== General Information ==&lt;br /&gt;
&lt;br /&gt;
=== Order Name * ===&lt;br /&gt;
The title of the rooming list.&lt;br /&gt;
&lt;br /&gt;
This is used:&lt;br /&gt;
&lt;br /&gt;
* In the sidebar list&lt;br /&gt;
* As the PDF title&lt;br /&gt;
* To help identify accommodation requests&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
* “Trip to Milan”&lt;br /&gt;
* “Barcelona Conference Accommodation”&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Contact Name ===&lt;br /&gt;
The primary contact person responsible for the booking or accommodation request.&lt;br /&gt;
&lt;br /&gt;
This is typically pre-filled using the current user profile.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Phone Number ===&lt;br /&gt;
The primary contact phone number for accommodation providers to use when responding to the request.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Contact Email ===&lt;br /&gt;
The main email address accommodation providers should use for communication.&lt;br /&gt;
&lt;br /&gt;
This field is usually pre-filled from the logged-in user profile.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Additional Emails ===&lt;br /&gt;
Optional comma-separated email addresses that should also receive accommodation communications or copies of the generated PDF.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;ops@company.com, travel@company.com&amp;lt;/code&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Event Location ===&lt;br /&gt;
The destination, venue, or event location related to the accommodation request.&lt;br /&gt;
&lt;br /&gt;
This location helps suppliers understand where accommodation proximity is required.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Stay Dates * ===&lt;br /&gt;
The requested accommodation check-in and check-out date range.&lt;br /&gt;
&lt;br /&gt;
These dates are typically pre-filled from the itinerary.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Accommodation Requirements ==&lt;br /&gt;
&lt;br /&gt;
=== Select Pending Accommodations ===&lt;br /&gt;
Selects an existing pending hotel/accommodation item from the itinerary.&lt;br /&gt;
&lt;br /&gt;
When selected:&lt;br /&gt;
&lt;br /&gt;
* Related guest information can be used&lt;br /&gt;
* Room counts may auto-populate&lt;br /&gt;
* Guest data can be included in the generated PDF&lt;br /&gt;
&lt;br /&gt;
Only accommodations currently marked as &#039;&#039;&#039;Pending&#039;&#039;&#039; are available.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Number of Rooms Required ===&lt;br /&gt;
The total number of rooms required for the stay.&lt;br /&gt;
&lt;br /&gt;
This may automatically populate based on the selected accommodation’s guest assignments, but can also be edited manually.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Maximum Number of Accommodations to Split * ===&lt;br /&gt;
Defines how many separate hotels or accommodation providers the booking can be split across.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; = all guests must stay in the same hotel&lt;br /&gt;
* &amp;lt;code&amp;gt;2&amp;lt;/code&amp;gt; = guests may be split between two hotels&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Maximum Distance from Event ===&lt;br /&gt;
Optional distance limit between the accommodation and the event location.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
* “5km”&lt;br /&gt;
* “15 minute walk”&lt;br /&gt;
&lt;br /&gt;
This helps suppliers return more suitable accommodation options.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Minimum Cost per Night per Room ===&lt;br /&gt;
Optional minimum nightly room budget.&lt;br /&gt;
&lt;br /&gt;
Useful when requesting accommodation within a preferred pricing range.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Maximum Cost per Night per Room ===&lt;br /&gt;
Optional maximum nightly room budget.&lt;br /&gt;
&lt;br /&gt;
Helps suppliers avoid quoting accommodation outside budget requirements.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Response Due Date ===&lt;br /&gt;
The deadline by which accommodation providers or agents should respond to the request.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Notes &amp;amp; Comments ==&lt;br /&gt;
&lt;br /&gt;
=== Additional Information for Agent ===&lt;br /&gt;
Free-text notes intended for accommodation providers or booking agents.&lt;br /&gt;
&lt;br /&gt;
Typical information may include:&lt;br /&gt;
&lt;br /&gt;
* Preferred room types&lt;br /&gt;
* Required amenities&lt;br /&gt;
* Breakfast or parking requirements&lt;br /&gt;
* Accessibility requests&lt;br /&gt;
* Special guest requirements&lt;br /&gt;
&lt;br /&gt;
This content is included in the generated PDF.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Team Internal Comments ===&lt;br /&gt;
Internal-only notes visible to EventR users.&lt;br /&gt;
&lt;br /&gt;
These comments are intended for operational or planning purposes and are not intended for accommodation suppliers.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
* Internal approval notes&lt;br /&gt;
* Supplier preferences&lt;br /&gt;
* Budget discussions&lt;br /&gt;
* Booking reminders&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Draft Handling ==&lt;br /&gt;
Rooming lists support unsaved drafts.&lt;br /&gt;
&lt;br /&gt;
If the user attempts to:&lt;br /&gt;
&lt;br /&gt;
* Close the modal&lt;br /&gt;
* Switch rooming lists&lt;br /&gt;
* Refresh data&lt;br /&gt;
* Create a new draft&lt;br /&gt;
&lt;br /&gt;
while unsaved changes exist, EventR will prompt the user to:&lt;br /&gt;
&lt;br /&gt;
* Save changes&lt;br /&gt;
* Discard changes&lt;br /&gt;
&lt;br /&gt;
This helps prevent accidental data loss.&lt;br /&gt;
| style=&amp;quot;width:40%; vertical-align:top;&amp;quot; |&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.49.46.png|thumb|Example: Draft rooming list]]&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.58.44.png|thumb|Multiple rooming list view]]&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=How_to_add_users_to_EventR_via_a_spreadsheet&amp;diff=687</id>
		<title>How to add users to EventR via a spreadsheet</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=How_to_add_users_to_EventR_via_a_spreadsheet&amp;diff=687"/>
		<updated>2026-05-14T15:46:54Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:New user dialog.png|thumb|Add new user dialog]]&lt;br /&gt;
[[File:Additonal user info setting.png|thumb|Additional user info setting on admin page]]&lt;br /&gt;
[[File:Users export.png|thumb|Example of a users CSV export opened in Numbers]]&lt;br /&gt;
The user spreadsheet import export feature supports both CSV (comma separated variables) and XLS format. To get started we recommend downloading the existing user data, then editing the spreadsheet.&lt;br /&gt;
[[File:Upload tags.png|thumb|Example: Uploading department and groups]]&lt;br /&gt;
Groups can be added with a &#039;,&#039; between them, along with Departments, and Permissions.&lt;br /&gt;
&lt;br /&gt;
If the system has [[user personal data]] turned on in Admin -&amp;gt; Settings, this information will appear too in the export.&lt;br /&gt;
&lt;br /&gt;
If the user being added is new to EventR (e.g. a company email) you may edit the user personal data as an Administrator. However if they are a member of multiple teams or have a personal EventR app with the same email, this data cannot be modified in this way.&lt;br /&gt;
[[File:Upload user dialog.png|thumb|Upload users dialog]]&lt;br /&gt;
When you upload, it is important to have a First Name, Last name, and email address for every users - the Email address is required since that is where the invite will be sent to.&lt;br /&gt;
&lt;br /&gt;
During the upload you may have a conflict, or a partial change. The system will present a dialog allowing to to confirm what you want to do before the upload actually happens.&lt;br /&gt;
&lt;br /&gt;
If [[Departments and Groups]] are not already created, they can be created on the first screen. If you choose not to create them, the users will be added without them.&lt;br /&gt;
&lt;br /&gt;
Once a spreadsheet has been uploaded, users will not receive the invite email until you check the box next to them and select &amp;quot;Invite&amp;quot;.&lt;br /&gt;
[[Category:3.4.1]]&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=File:Users_export.png&amp;diff=686</id>
		<title>File:Users export.png</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=File:Users_export.png&amp;diff=686"/>
		<updated>2026-05-14T15:46:49Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Example of a users CSV export opened in Numbers&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=How_to_add_users_to_EventR_via_a_spreadsheet&amp;diff=685</id>
		<title>How to add users to EventR via a spreadsheet</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=How_to_add_users_to_EventR_via_a_spreadsheet&amp;diff=685"/>
		<updated>2026-05-14T15:43:41Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:New user dialog.png|thumb|Add new user dialog]]&lt;br /&gt;
[[File:Additonal user info setting.png|thumb|Additional user info setting on admin page]]&lt;br /&gt;
[[File:Example users download csv.png|thumb|Example of a users CSV export opened in Numbers]]&lt;br /&gt;
The user spreadsheet import export feature supports both CSV (comma separated variables) and XLS format. To get started we recommend downloading the existing user data, then editing the spreadsheet.&lt;br /&gt;
[[File:Upload tags.png|thumb|Example: Uploading department and groups]]&lt;br /&gt;
Groups can be added with a &#039;,&#039; between them, along with Departments, and Permissions.&lt;br /&gt;
&lt;br /&gt;
If the system has [[user personal data]] turned on in Admin -&amp;gt; Settings, this information will appear too in the export.&lt;br /&gt;
&lt;br /&gt;
If the user being added is new to EventR (e.g. a company email) you may edit the user personal data as an Administrator. However if they are a member of multiple teams or have a personal EventR app with the same email, this data cannot be modified in this way.&lt;br /&gt;
[[File:Upload user dialog.png|thumb|Upload users dialog]]&lt;br /&gt;
When you upload, it is important to have a First Name, Last name, and email address for every users - the Email address is required since that is where the invite will be sent to.&lt;br /&gt;
&lt;br /&gt;
During the upload you may have a conflict, or a partial change. The system will present a dialog allowing to to confirm what you want to do before the upload actually happens.&lt;br /&gt;
&lt;br /&gt;
If [[Departments and Groups]] are not already created, they can be created on the first screen. If you choose not to create them, the users will be added without them.&lt;br /&gt;
&lt;br /&gt;
Once a spreadsheet has been uploaded, users will not receive the invite email until you check the box next to them and select &amp;quot;Invite&amp;quot;.&lt;br /&gt;
[[Category:3.4.1]]&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=File:Example_users_download_csv.png&amp;diff=682</id>
		<title>File:Example users download csv.png</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=File:Example_users_download_csv.png&amp;diff=682"/>
		<updated>2026-05-14T15:42:13Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;numbers screenshot of user export&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=How_to_add_users_to_EventR_via_a_spreadsheet&amp;diff=680</id>
		<title>How to add users to EventR via a spreadsheet</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=How_to_add_users_to_EventR_via_a_spreadsheet&amp;diff=680"/>
		<updated>2026-05-14T15:40:48Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:New user dialog.png|thumb|Add new user dialog]]&lt;br /&gt;
[[File:Additonal user info setting.png|thumb|Additional user info setting on admin page]]&lt;br /&gt;
The user spreadsheet import export feature supports both CSV (comma separated variables) and XLS format. To get started we recommend downloading the existing user data, then editing the spreadsheet.&lt;br /&gt;
[[File:Upload tags.png|thumb|Example: Uploading department and groups]]&lt;br /&gt;
Groups can be added with a &#039;,&#039; between them, along with Departments, and Permissions.&lt;br /&gt;
&lt;br /&gt;
If the system has [[user personal data]] turned on in Admin -&amp;gt; Settings, this information will appear too in the export.&lt;br /&gt;
&lt;br /&gt;
If the user being added is new to EventR (e.g. a company email) you may edit the user personal data as an Administrator. However if they are a member of multiple teams or have a personal EventR app with the same email, this data cannot be modified in this way.&lt;br /&gt;
[[File:Upload user dialog.png|thumb|Upload users dialog]]&lt;br /&gt;
When you upload, it is important to have a First Name, Last name, and email address for every users - the Email address is required since that is where the invite will be sent to.&lt;br /&gt;
&lt;br /&gt;
During the upload you may have a conflict, or a partial change. The system will present a dialog allowing to to confirm what you want to do before the upload actually happens.&lt;br /&gt;
&lt;br /&gt;
If [[Departments and Groups]] are not already created, they can be created on the first screen. If you choose not to create them, the users will be added without them.&lt;br /&gt;
&lt;br /&gt;
Once a spreadsheet has been uploaded, users will not receive the invite email until you check the box next to them and select &amp;quot;Invite&amp;quot;.&lt;br /&gt;
[[Category:3.4.1]]&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=File:Additonal_user_info_setting.png&amp;diff=678</id>
		<title>File:Additonal user info setting.png</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=File:Additonal_user_info_setting.png&amp;diff=678"/>
		<updated>2026-05-14T15:40:33Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Additional user info setting on admin page&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=How_to_add_users_to_EventR_via_a_spreadsheet&amp;diff=677</id>
		<title>How to add users to EventR via a spreadsheet</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=How_to_add_users_to_EventR_via_a_spreadsheet&amp;diff=677"/>
		<updated>2026-05-14T15:39:54Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;[[File:New user dialog.png|thumb|Add new user dialog]]&lt;br /&gt;
The user spreadsheet import export feature supports both CSV (comma separated variables) and XLS format. To get started we recommend downloading the existing user data, then editing the spreadsheet.&lt;br /&gt;
[[File:Upload tags.png|thumb|Example: Uploading department and groups]]&lt;br /&gt;
Groups can be added with a &#039;,&#039; between them, along with Departments, and Permissions.&lt;br /&gt;
&lt;br /&gt;
If the system has [[user personal data]] turned on in Admin -&amp;gt; Settings, this information will appear too in the export.&lt;br /&gt;
&lt;br /&gt;
If the user being added is new to EventR (e.g. a company email) you may edit the user personal data as an Administrator. However if they are a member of multiple teams or have a personal EventR app with the same email, this data cannot be modified in this way.&lt;br /&gt;
[[File:Upload user dialog.png|thumb|Upload users dialog]]&lt;br /&gt;
When you upload, it is important to have a First Name, Last name, and email address for every users - the Email address is required since that is where the invite will be sent to.&lt;br /&gt;
&lt;br /&gt;
During the upload you may have a conflict, or a partial change. The system will present a dialog allowing to to confirm what you want to do before the upload actually happens.&lt;br /&gt;
&lt;br /&gt;
If [[Departments and Groups]] are not already created, they can be created on the first screen. If you choose not to create them, the users will be added without them.&lt;br /&gt;
&lt;br /&gt;
Once a spreadsheet has been uploaded, users will not receive the invite email until you check the box next to them and select &amp;quot;Invite&amp;quot;.&lt;br /&gt;
[[Category:3.4.1]]&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=File:New_user_dialog.png&amp;diff=676</id>
		<title>File:New user dialog.png</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=File:New_user_dialog.png&amp;diff=676"/>
		<updated>2026-05-14T15:39:32Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;Add new user dialog&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=How_to_add_users_to_EventR_via_a_spreadsheet&amp;diff=675</id>
		<title>How to add users to EventR via a spreadsheet</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=How_to_add_users_to_EventR_via_a_spreadsheet&amp;diff=675"/>
		<updated>2026-05-14T15:39:09Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;The user spreadsheet import export feature supports both CSV (comma separated variables) and XLS format. To get started we recommend downloading the existing user data, then editing the spreadsheet.&lt;br /&gt;
[[File:Upload tags.png|thumb|Example: Uploading department and groups]]&lt;br /&gt;
Groups can be added with a &#039;,&#039; between them, along with Departments, and Permissions.&lt;br /&gt;
&lt;br /&gt;
If the system has [[user personal data]] turned on in Admin -&amp;gt; Settings, this information will appear too in the export.&lt;br /&gt;
&lt;br /&gt;
If the user being added is new to EventR (e.g. a company email) you may edit the user personal data as an Administrator. However if they are a member of multiple teams or have a personal EventR app with the same email, this data cannot be modified in this way.&lt;br /&gt;
[[File:Upload user dialog.png|thumb|Upload users dialog]]&lt;br /&gt;
When you upload, it is important to have a First Name, Last name, and email address for every users - the Email address is required since that is where the invite will be sent to.&lt;br /&gt;
&lt;br /&gt;
During the upload you may have a conflict, or a partial change. The system will present a dialog allowing to to confirm what you want to do before the upload actually happens.&lt;br /&gt;
&lt;br /&gt;
If [[Departments and Groups]] are not already created, they can be created on the first screen. If you choose not to create them, the users will be added without them.&lt;br /&gt;
&lt;br /&gt;
Once a spreadsheet has been uploaded, users will not receive the invite email until you check the box next to them and select &amp;quot;Invite&amp;quot;.&lt;br /&gt;
[[Category:3.4.1]]&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=File:Upload_user_dialog.png&amp;diff=674</id>
		<title>File:Upload user dialog.png</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=File:Upload_user_dialog.png&amp;diff=674"/>
		<updated>2026-05-14T15:38:27Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;User upload dialog&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=File:Upload_tags.png&amp;diff=673</id>
		<title>File:Upload tags.png</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=File:Upload_tags.png&amp;diff=673"/>
		<updated>2026-05-14T15:37:40Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;upload tags&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=Orders&amp;diff=370</id>
		<title>Orders</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=Orders&amp;diff=370"/>
		<updated>2026-05-07T10:08:19Z</updated>

		<summary type="html">&lt;p&gt;Samh: /* Managing Rooming Lists */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Infobox Feature&lt;br /&gt;
 | name = Rooming Lists&lt;br /&gt;
 | version = Beta in 3.4.1 (Unreleased)&lt;br /&gt;
 | tier = Standard, Premium and Enterprise&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
= Overview =&lt;br /&gt;
The &#039;&#039;&#039;Rooming List&#039;&#039;&#039; feature allows users to create, manage, save, and generate accommodation request PDFs for hotels or accommodation suppliers. It acts as a central workspace for collecting stay requirements, guest accommodation preferences, and booking details related to an itinerary. &lt;br /&gt;
&lt;br /&gt;
= Accessing Rooming Lists =&lt;br /&gt;
{| style=&amp;quot;width:100%; margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width:60%; vertical-align:top;&amp;quot; |&lt;br /&gt;
To find the rooming list functionality, select &#039;&#039;&#039;Create Rooming List&#039;&#039;&#039; from the itinerary accommodation section in the ECH. This opens the Rooming List workspace in a full-screen modal.&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:40%; vertical-align:top;&amp;quot; |&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.21.54.png|thumb| When you have no existing accommodations, button is located bottom centre. ]]&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.38.33.png|thumb|Button moves into the header when you have existing accommodations.]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
= Managing Rooming Lists =&lt;br /&gt;
{| style=&amp;quot;width:100%; margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width:60%; vertical-align:top;&amp;quot; |New rooming lists begin as unsaved drafts until they are saved.&lt;br /&gt;
&lt;br /&gt;
When creating a new rooming list, the form is automatically pre-filled using information from the selected itinerary, including dates, location, and lead booker details (You) where available.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Layout Overview ===&lt;br /&gt;
The Rooming List workspace is divided into four main sections:&lt;br /&gt;
&lt;br /&gt;
* Top Bar&lt;br /&gt;
* Sidebar&lt;br /&gt;
* Main Form&lt;br /&gt;
* Bottom Bar&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Top Bar ==&lt;br /&gt;
&lt;br /&gt;
=== Reset ===&lt;br /&gt;
Restores the currently selected rooming list back to its last saved state.&lt;br /&gt;
&lt;br /&gt;
If editing a new unsaved draft, the form will revert to its original pre-filled itinerary values.&lt;br /&gt;
&lt;br /&gt;
=== Create New ===&lt;br /&gt;
Creates a new unsaved rooming list draft while keeping the current modal open.&lt;br /&gt;
&lt;br /&gt;
If unsaved changes exist, the user will be prompted to save or discard them before continuing.&lt;br /&gt;
&lt;br /&gt;
=== Close ===&lt;br /&gt;
Closes the Rooming List modal.&lt;br /&gt;
&lt;br /&gt;
If there are unsaved changes, the user will be prompted to save or discard the draft before closing.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Sidebar ==&lt;br /&gt;
The sidebar contains all saved rooming lists for the currently selected itinerary.&lt;br /&gt;
&lt;br /&gt;
=== Search ===&lt;br /&gt;
Filters saved rooming lists by title.&lt;br /&gt;
&lt;br /&gt;
=== Refresh ===&lt;br /&gt;
Reloads the latest rooming lists from the server without closing the modal.&lt;br /&gt;
&lt;br /&gt;
=== Rooming List Entries ===&lt;br /&gt;
Displays all saved rooming lists ordered by most recently updated first.&lt;br /&gt;
&lt;br /&gt;
Each entry displays:&lt;br /&gt;
&lt;br /&gt;
* Rooming list title&lt;br /&gt;
* Last modified date and time&lt;br /&gt;
&lt;br /&gt;
Selecting a different rooming list will load its saved data into the form.&lt;br /&gt;
&lt;br /&gt;
If unsaved changes exist, the user will be prompted to save or discard them before switching.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Bottom Bar ==&lt;br /&gt;
&lt;br /&gt;
=== Save ===&lt;br /&gt;
Saves the current rooming list.&lt;br /&gt;
&lt;br /&gt;
Once saved:&lt;br /&gt;
&lt;br /&gt;
* The rooming list becomes persistent&lt;br /&gt;
* It appears in the sidebar&lt;br /&gt;
* Future edits can be restored using Reset&lt;br /&gt;
&lt;br /&gt;
=== Delete ===&lt;br /&gt;
Deletes the currently selected saved rooming list.&lt;br /&gt;
&lt;br /&gt;
This action cannot be undone.&lt;br /&gt;
&lt;br /&gt;
If working on an unsaved draft, this button instead discards the draft.&lt;br /&gt;
&lt;br /&gt;
=== Generate PDF ===&lt;br /&gt;
Generates a PDF version of the current rooming list using all entered form data.&lt;br /&gt;
&lt;br /&gt;
The PDF is designed for sharing with hotels, accommodation providers, or booking agents.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Form Fields ==&lt;br /&gt;
&lt;br /&gt;
== General Information ==&lt;br /&gt;
&lt;br /&gt;
=== Order Name * ===&lt;br /&gt;
The title of the rooming list.&lt;br /&gt;
&lt;br /&gt;
This is used:&lt;br /&gt;
&lt;br /&gt;
* In the sidebar list&lt;br /&gt;
* As the PDF title&lt;br /&gt;
* To help identify accommodation requests&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
* “Trip to Milan”&lt;br /&gt;
* “Barcelona Conference Accommodation”&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Contact Name ===&lt;br /&gt;
The primary contact person responsible for the booking or accommodation request.&lt;br /&gt;
&lt;br /&gt;
This is typically pre-filled using the current user profile.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Phone Number ===&lt;br /&gt;
The primary contact phone number for accommodation providers to use when responding to the request.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Contact Email ===&lt;br /&gt;
The main email address accommodation providers should use for communication.&lt;br /&gt;
&lt;br /&gt;
This field is usually pre-filled from the logged-in user profile.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Additional Emails ===&lt;br /&gt;
Optional comma-separated email addresses that should also receive accommodation communications or copies of the generated PDF.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;ops@company.com, travel@company.com&amp;lt;/code&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Event Location ===&lt;br /&gt;
The destination, venue, or event location related to the accommodation request.&lt;br /&gt;
&lt;br /&gt;
This location helps suppliers understand where accommodation proximity is required.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Stay Dates * ===&lt;br /&gt;
The requested accommodation check-in and check-out date range.&lt;br /&gt;
&lt;br /&gt;
These dates are typically pre-filled from the itinerary.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Accommodation Requirements ==&lt;br /&gt;
&lt;br /&gt;
=== Select Pending Accommodations ===&lt;br /&gt;
Selects an existing pending hotel/accommodation item from the itinerary.&lt;br /&gt;
&lt;br /&gt;
When selected:&lt;br /&gt;
&lt;br /&gt;
* Related guest information can be used&lt;br /&gt;
* Room counts may auto-populate&lt;br /&gt;
* Guest data can be included in the generated PDF&lt;br /&gt;
&lt;br /&gt;
Only accommodations currently marked as &#039;&#039;&#039;Pending&#039;&#039;&#039; are available.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Number of Rooms Required ===&lt;br /&gt;
The total number of rooms required for the stay.&lt;br /&gt;
&lt;br /&gt;
This may automatically populate based on the selected accommodation’s guest assignments, but can also be edited manually.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Maximum Number of Accommodations to Split * ===&lt;br /&gt;
Defines how many separate hotels or accommodation providers the booking can be split across.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; = all guests must stay in the same hotel&lt;br /&gt;
* &amp;lt;code&amp;gt;2&amp;lt;/code&amp;gt; = guests may be split between two hotels&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Maximum Distance from Event ===&lt;br /&gt;
Optional distance limit between the accommodation and the event location.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
* “5km”&lt;br /&gt;
* “15 minute walk”&lt;br /&gt;
&lt;br /&gt;
This helps suppliers return more suitable accommodation options.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Minimum Cost per Night per Room ===&lt;br /&gt;
Optional minimum nightly room budget.&lt;br /&gt;
&lt;br /&gt;
Useful when requesting accommodation within a preferred pricing range.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Maximum Cost per Night per Room ===&lt;br /&gt;
Optional maximum nightly room budget.&lt;br /&gt;
&lt;br /&gt;
Helps suppliers avoid quoting accommodation outside budget requirements.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Response Due Date ===&lt;br /&gt;
The deadline by which accommodation providers or agents should respond to the request.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Notes &amp;amp; Comments ==&lt;br /&gt;
&lt;br /&gt;
=== Additional Information for Agent ===&lt;br /&gt;
Free-text notes intended for accommodation providers or booking agents.&lt;br /&gt;
&lt;br /&gt;
Typical information may include:&lt;br /&gt;
&lt;br /&gt;
* Preferred room types&lt;br /&gt;
* Required amenities&lt;br /&gt;
* Breakfast or parking requirements&lt;br /&gt;
* Accessibility requests&lt;br /&gt;
* Special guest requirements&lt;br /&gt;
&lt;br /&gt;
This content is included in the generated PDF.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Team Internal Comments ===&lt;br /&gt;
Internal-only notes visible to EventR users.&lt;br /&gt;
&lt;br /&gt;
These comments are intended for operational or planning purposes and are not intended for accommodation suppliers.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
* Internal approval notes&lt;br /&gt;
* Supplier preferences&lt;br /&gt;
* Budget discussions&lt;br /&gt;
* Booking reminders&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Draft Handling ==&lt;br /&gt;
Rooming lists support unsaved drafts.&lt;br /&gt;
&lt;br /&gt;
If the user attempts to:&lt;br /&gt;
&lt;br /&gt;
* Close the modal&lt;br /&gt;
* Switch rooming lists&lt;br /&gt;
* Refresh data&lt;br /&gt;
* Create a new draft&lt;br /&gt;
&lt;br /&gt;
while unsaved changes exist, EventR will prompt the user to:&lt;br /&gt;
&lt;br /&gt;
* Save changes&lt;br /&gt;
* Discard changes&lt;br /&gt;
&lt;br /&gt;
This helps prevent accidental data loss.&lt;br /&gt;
| style=&amp;quot;width:40%; vertical-align:top;&amp;quot; |&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.49.46.png|thumb|Example: Draft rooming list]]&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.58.44.png|thumb|Multiple rooming list view]]&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=Orders&amp;diff=369</id>
		<title>Orders</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=Orders&amp;diff=369"/>
		<updated>2026-05-07T10:06:23Z</updated>

		<summary type="html">&lt;p&gt;Samh: &lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Infobox Feature&lt;br /&gt;
 | name = Rooming Lists&lt;br /&gt;
 | version = Beta in 3.4.1 (Unreleased)&lt;br /&gt;
 | tier = Standard, Premium and Enterprise&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
= Overview =&lt;br /&gt;
The &#039;&#039;&#039;Rooming List&#039;&#039;&#039; feature allows users to create, manage, save, and generate accommodation request PDFs for hotels or accommodation suppliers. It acts as a central workspace for collecting stay requirements, guest accommodation preferences, and booking details related to an itinerary. &lt;br /&gt;
&lt;br /&gt;
= Accessing Rooming Lists =&lt;br /&gt;
{| style=&amp;quot;width:100%; margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width:60%; vertical-align:top;&amp;quot; |&lt;br /&gt;
To find the rooming list functionality, select &#039;&#039;&#039;Create Rooming List&#039;&#039;&#039; from the itinerary accommodation section in the ECH. This opens the Rooming List workspace in a full-screen modal.&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:40%; vertical-align:top;&amp;quot; |&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.21.54.png|thumb| When you have no existing accommodations, button is located bottom centre. ]]&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.38.33.png|thumb|Button moves into the header when you have existing accommodations.]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
= Managing Rooming Lists =&lt;br /&gt;
{| style=&amp;quot;width:100%; margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width:60%; vertical-align:top;&amp;quot; |To create a rooming list, select &#039;&#039;&#039;Create Rooming List&#039;&#039;&#039; from the itinerary accommodation section. This opens the Rooming List workspace in a full-screen modal.&lt;br /&gt;
&lt;br /&gt;
New rooming lists begin as unsaved drafts until they are saved.&lt;br /&gt;
&lt;br /&gt;
When creating a new rooming list, the form is automatically pre-filled using information from the selected itinerary, including dates, location, and lead booker details (You) where available.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Layout Overview ===&lt;br /&gt;
The Rooming List workspace is divided into four main sections:&lt;br /&gt;
&lt;br /&gt;
* Top Bar&lt;br /&gt;
* Sidebar&lt;br /&gt;
* Main Form&lt;br /&gt;
* Bottom Bar&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Top Bar ==&lt;br /&gt;
&lt;br /&gt;
=== Reset ===&lt;br /&gt;
Restores the currently selected rooming list back to its last saved state.&lt;br /&gt;
&lt;br /&gt;
If editing a new unsaved draft, the form will revert to its original pre-filled itinerary values.&lt;br /&gt;
&lt;br /&gt;
=== Create New ===&lt;br /&gt;
Creates a new unsaved rooming list draft while keeping the current modal open.&lt;br /&gt;
&lt;br /&gt;
If unsaved changes exist, the user will be prompted to save or discard them before continuing.&lt;br /&gt;
&lt;br /&gt;
=== Close ===&lt;br /&gt;
Closes the Rooming List modal.&lt;br /&gt;
&lt;br /&gt;
If there are unsaved changes, the user will be prompted to save or discard the draft before closing.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Sidebar ==&lt;br /&gt;
The sidebar contains all saved rooming lists for the currently selected itinerary.&lt;br /&gt;
&lt;br /&gt;
=== Search ===&lt;br /&gt;
Filters saved rooming lists by title.&lt;br /&gt;
&lt;br /&gt;
=== Refresh ===&lt;br /&gt;
Reloads the latest rooming lists from the server without closing the modal.&lt;br /&gt;
&lt;br /&gt;
=== Rooming List Entries ===&lt;br /&gt;
Displays all saved rooming lists ordered by most recently updated first.&lt;br /&gt;
&lt;br /&gt;
Each entry displays:&lt;br /&gt;
&lt;br /&gt;
* Rooming list title&lt;br /&gt;
* Last modified date and time&lt;br /&gt;
&lt;br /&gt;
Selecting a different rooming list will load its saved data into the form.&lt;br /&gt;
&lt;br /&gt;
If unsaved changes exist, the user will be prompted to save or discard them before switching.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Bottom Bar ==&lt;br /&gt;
&lt;br /&gt;
=== Save ===&lt;br /&gt;
Saves the current rooming list.&lt;br /&gt;
&lt;br /&gt;
Once saved:&lt;br /&gt;
&lt;br /&gt;
* The rooming list becomes persistent&lt;br /&gt;
* It appears in the sidebar&lt;br /&gt;
* Future edits can be restored using Reset&lt;br /&gt;
&lt;br /&gt;
=== Delete ===&lt;br /&gt;
Deletes the currently selected saved rooming list.&lt;br /&gt;
&lt;br /&gt;
This action cannot be undone.&lt;br /&gt;
&lt;br /&gt;
If working on an unsaved draft, this button instead discards the draft.&lt;br /&gt;
&lt;br /&gt;
=== Generate PDF ===&lt;br /&gt;
Generates a PDF version of the current rooming list using all entered form data.&lt;br /&gt;
&lt;br /&gt;
The PDF is designed for sharing with hotels, accommodation providers, or booking agents.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Form Fields ==&lt;br /&gt;
&lt;br /&gt;
== General Information ==&lt;br /&gt;
&lt;br /&gt;
=== Order Name * ===&lt;br /&gt;
The title of the rooming list.&lt;br /&gt;
&lt;br /&gt;
This is used:&lt;br /&gt;
&lt;br /&gt;
* In the sidebar list&lt;br /&gt;
* As the PDF title&lt;br /&gt;
* To help identify accommodation requests&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
* “Trip to Milan”&lt;br /&gt;
* “Barcelona Conference Accommodation”&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Contact Name ===&lt;br /&gt;
The primary contact person responsible for the booking or accommodation request.&lt;br /&gt;
&lt;br /&gt;
This is typically pre-filled using the current user profile.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Phone Number ===&lt;br /&gt;
The primary contact phone number for accommodation providers to use when responding to the request.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Contact Email ===&lt;br /&gt;
The main email address accommodation providers should use for communication.&lt;br /&gt;
&lt;br /&gt;
This field is usually pre-filled from the logged-in user profile.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Additional Emails ===&lt;br /&gt;
Optional comma-separated email addresses that should also receive accommodation communications or copies of the generated PDF.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;ops@company.com, travel@company.com&amp;lt;/code&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Event Location ===&lt;br /&gt;
The destination, venue, or event location related to the accommodation request.&lt;br /&gt;
&lt;br /&gt;
This location helps suppliers understand where accommodation proximity is required.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Stay Dates * ===&lt;br /&gt;
The requested accommodation check-in and check-out date range.&lt;br /&gt;
&lt;br /&gt;
These dates are typically pre-filled from the itinerary.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Accommodation Requirements ==&lt;br /&gt;
&lt;br /&gt;
=== Select Pending Accommodations ===&lt;br /&gt;
Selects an existing pending hotel/accommodation item from the itinerary.&lt;br /&gt;
&lt;br /&gt;
When selected:&lt;br /&gt;
&lt;br /&gt;
* Related guest information can be used&lt;br /&gt;
* Room counts may auto-populate&lt;br /&gt;
* Guest data can be included in the generated PDF&lt;br /&gt;
&lt;br /&gt;
Only accommodations currently marked as &#039;&#039;&#039;Pending&#039;&#039;&#039; are available.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Number of Rooms Required ===&lt;br /&gt;
The total number of rooms required for the stay.&lt;br /&gt;
&lt;br /&gt;
This may automatically populate based on the selected accommodation’s guest assignments, but can also be edited manually.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Maximum Number of Accommodations to Split * ===&lt;br /&gt;
Defines how many separate hotels or accommodation providers the booking can be split across.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; = all guests must stay in the same hotel&lt;br /&gt;
* &amp;lt;code&amp;gt;2&amp;lt;/code&amp;gt; = guests may be split between two hotels&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Maximum Distance from Event ===&lt;br /&gt;
Optional distance limit between the accommodation and the event location.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
* “5km”&lt;br /&gt;
* “15 minute walk”&lt;br /&gt;
&lt;br /&gt;
This helps suppliers return more suitable accommodation options.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Minimum Cost per Night per Room ===&lt;br /&gt;
Optional minimum nightly room budget.&lt;br /&gt;
&lt;br /&gt;
Useful when requesting accommodation within a preferred pricing range.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Maximum Cost per Night per Room ===&lt;br /&gt;
Optional maximum nightly room budget.&lt;br /&gt;
&lt;br /&gt;
Helps suppliers avoid quoting accommodation outside budget requirements.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Response Due Date ===&lt;br /&gt;
The deadline by which accommodation providers or agents should respond to the request.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Notes &amp;amp; Comments ==&lt;br /&gt;
&lt;br /&gt;
=== Additional Information for Agent ===&lt;br /&gt;
Free-text notes intended for accommodation providers or booking agents.&lt;br /&gt;
&lt;br /&gt;
Typical information may include:&lt;br /&gt;
&lt;br /&gt;
* Preferred room types&lt;br /&gt;
* Required amenities&lt;br /&gt;
* Breakfast or parking requirements&lt;br /&gt;
* Accessibility requests&lt;br /&gt;
* Special guest requirements&lt;br /&gt;
&lt;br /&gt;
This content is included in the generated PDF.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Team Internal Comments ===&lt;br /&gt;
Internal-only notes visible to EventR users.&lt;br /&gt;
&lt;br /&gt;
These comments are intended for operational or planning purposes and are not intended for accommodation suppliers.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
* Internal approval notes&lt;br /&gt;
* Supplier preferences&lt;br /&gt;
* Budget discussions&lt;br /&gt;
* Booking reminders&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Draft Handling ==&lt;br /&gt;
Rooming lists support unsaved drafts.&lt;br /&gt;
&lt;br /&gt;
If the user attempts to:&lt;br /&gt;
&lt;br /&gt;
* Close the modal&lt;br /&gt;
* Switch rooming lists&lt;br /&gt;
* Refresh data&lt;br /&gt;
* Create a new draft&lt;br /&gt;
&lt;br /&gt;
while unsaved changes exist, EventR will prompt the user to:&lt;br /&gt;
&lt;br /&gt;
* Save changes&lt;br /&gt;
* Discard changes&lt;br /&gt;
&lt;br /&gt;
This helps prevent accidental data loss.&lt;br /&gt;
| style=&amp;quot;width:40%; vertical-align:top;&amp;quot; |&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.49.46.png|thumb|Example: Draft rooming list]]&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.58.44.png|thumb|Multiple rooming list view]]&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=Orders&amp;diff=368</id>
		<title>Orders</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=Orders&amp;diff=368"/>
		<updated>2026-05-07T10:04:31Z</updated>

		<summary type="html">&lt;p&gt;Samh: /* Overview */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Infobox Feature&lt;br /&gt;
 | name = Rooming Lists&lt;br /&gt;
 | version = Unreleased&lt;br /&gt;
 | tier = Standard, Premium and Enterprise&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
= Overview =&lt;br /&gt;
The &#039;&#039;&#039;Rooming List&#039;&#039;&#039; feature allows users to create, manage, save, and generate accommodation request PDFs for hotels or accommodation suppliers. It acts as a central workspace for collecting stay requirements, guest accommodation preferences, and booking details related to an itinerary. &lt;br /&gt;
&lt;br /&gt;
= Accessing Rooming Lists =&lt;br /&gt;
{| style=&amp;quot;width:100%; margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width:60%; vertical-align:top;&amp;quot; |&lt;br /&gt;
To find the rooming list functionality, select &#039;&#039;&#039;Create Rooming List&#039;&#039;&#039; from the itinerary accommodation section in the ECH. This opens the Rooming List workspace in a full-screen modal.&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:40%; vertical-align:top;&amp;quot; |&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.21.54.png|thumb| When you have no existing accommodations, button is located bottom centre. ]]&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.38.33.png|thumb|Button moves into the header when you have existing accommodations.]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
= Managing Rooming Lists =&lt;br /&gt;
{| style=&amp;quot;width:100%; margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width:60%; vertical-align:top;&amp;quot; |To create a rooming list, select &#039;&#039;&#039;Create Rooming List&#039;&#039;&#039; from the itinerary accommodation section. This opens the Rooming List workspace in a full-screen modal.&lt;br /&gt;
&lt;br /&gt;
New rooming lists begin as unsaved drafts until they are saved.&lt;br /&gt;
&lt;br /&gt;
When creating a new rooming list, the form is automatically pre-filled using information from the selected itinerary, including dates, location, and lead booker details (You) where available.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Layout Overview ===&lt;br /&gt;
The Rooming List workspace is divided into four main sections:&lt;br /&gt;
&lt;br /&gt;
* Top Bar&lt;br /&gt;
* Sidebar&lt;br /&gt;
* Main Form&lt;br /&gt;
* Bottom Bar&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Top Bar ==&lt;br /&gt;
&lt;br /&gt;
=== Reset ===&lt;br /&gt;
Restores the currently selected rooming list back to its last saved state.&lt;br /&gt;
&lt;br /&gt;
If editing a new unsaved draft, the form will revert to its original pre-filled itinerary values.&lt;br /&gt;
&lt;br /&gt;
=== Create New ===&lt;br /&gt;
Creates a new unsaved rooming list draft while keeping the current modal open.&lt;br /&gt;
&lt;br /&gt;
If unsaved changes exist, the user will be prompted to save or discard them before continuing.&lt;br /&gt;
&lt;br /&gt;
=== Close ===&lt;br /&gt;
Closes the Rooming List modal.&lt;br /&gt;
&lt;br /&gt;
If there are unsaved changes, the user will be prompted to save or discard the draft before closing.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Sidebar ==&lt;br /&gt;
The sidebar contains all saved rooming lists for the currently selected itinerary.&lt;br /&gt;
&lt;br /&gt;
=== Search ===&lt;br /&gt;
Filters saved rooming lists by title.&lt;br /&gt;
&lt;br /&gt;
=== Refresh ===&lt;br /&gt;
Reloads the latest rooming lists from the server without closing the modal.&lt;br /&gt;
&lt;br /&gt;
=== Rooming List Entries ===&lt;br /&gt;
Displays all saved rooming lists ordered by most recently updated first.&lt;br /&gt;
&lt;br /&gt;
Each entry displays:&lt;br /&gt;
&lt;br /&gt;
* Rooming list title&lt;br /&gt;
* Last modified date and time&lt;br /&gt;
&lt;br /&gt;
Selecting a different rooming list will load its saved data into the form.&lt;br /&gt;
&lt;br /&gt;
If unsaved changes exist, the user will be prompted to save or discard them before switching.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Bottom Bar ==&lt;br /&gt;
&lt;br /&gt;
=== Save ===&lt;br /&gt;
Saves the current rooming list.&lt;br /&gt;
&lt;br /&gt;
Once saved:&lt;br /&gt;
&lt;br /&gt;
* The rooming list becomes persistent&lt;br /&gt;
* It appears in the sidebar&lt;br /&gt;
* Future edits can be restored using Reset&lt;br /&gt;
&lt;br /&gt;
=== Delete ===&lt;br /&gt;
Deletes the currently selected saved rooming list.&lt;br /&gt;
&lt;br /&gt;
This action cannot be undone.&lt;br /&gt;
&lt;br /&gt;
If working on an unsaved draft, this button instead discards the draft.&lt;br /&gt;
&lt;br /&gt;
=== Generate PDF ===&lt;br /&gt;
Generates a PDF version of the current rooming list using all entered form data.&lt;br /&gt;
&lt;br /&gt;
The PDF is designed for sharing with hotels, accommodation providers, or booking agents.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Form Fields ==&lt;br /&gt;
&lt;br /&gt;
== General Information ==&lt;br /&gt;
&lt;br /&gt;
=== Order Name * ===&lt;br /&gt;
The title of the rooming list.&lt;br /&gt;
&lt;br /&gt;
This is used:&lt;br /&gt;
&lt;br /&gt;
* In the sidebar list&lt;br /&gt;
* As the PDF title&lt;br /&gt;
* To help identify accommodation requests&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
* “Trip to Milan”&lt;br /&gt;
* “Barcelona Conference Accommodation”&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Contact Name ===&lt;br /&gt;
The primary contact person responsible for the booking or accommodation request.&lt;br /&gt;
&lt;br /&gt;
This is typically pre-filled using the current user profile.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Phone Number ===&lt;br /&gt;
The primary contact phone number for accommodation providers to use when responding to the request.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Contact Email ===&lt;br /&gt;
The main email address accommodation providers should use for communication.&lt;br /&gt;
&lt;br /&gt;
This field is usually pre-filled from the logged-in user profile.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Additional Emails ===&lt;br /&gt;
Optional comma-separated email addresses that should also receive accommodation communications or copies of the generated PDF.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;ops@company.com, travel@company.com&amp;lt;/code&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Event Location ===&lt;br /&gt;
The destination, venue, or event location related to the accommodation request.&lt;br /&gt;
&lt;br /&gt;
This location helps suppliers understand where accommodation proximity is required.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Stay Dates * ===&lt;br /&gt;
The requested accommodation check-in and check-out date range.&lt;br /&gt;
&lt;br /&gt;
These dates are typically pre-filled from the itinerary.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Accommodation Requirements ==&lt;br /&gt;
&lt;br /&gt;
=== Select Pending Accommodations ===&lt;br /&gt;
Selects an existing pending hotel/accommodation item from the itinerary.&lt;br /&gt;
&lt;br /&gt;
When selected:&lt;br /&gt;
&lt;br /&gt;
* Related guest information can be used&lt;br /&gt;
* Room counts may auto-populate&lt;br /&gt;
* Guest data can be included in the generated PDF&lt;br /&gt;
&lt;br /&gt;
Only accommodations currently marked as &#039;&#039;&#039;Pending&#039;&#039;&#039; are available.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Number of Rooms Required ===&lt;br /&gt;
The total number of rooms required for the stay.&lt;br /&gt;
&lt;br /&gt;
This may automatically populate based on the selected accommodation’s guest assignments, but can also be edited manually.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Maximum Number of Accommodations to Split * ===&lt;br /&gt;
Defines how many separate hotels or accommodation providers the booking can be split across.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; = all guests must stay in the same hotel&lt;br /&gt;
* &amp;lt;code&amp;gt;2&amp;lt;/code&amp;gt; = guests may be split between two hotels&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Maximum Distance from Event ===&lt;br /&gt;
Optional distance limit between the accommodation and the event location.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
* “5km”&lt;br /&gt;
* “15 minute walk”&lt;br /&gt;
&lt;br /&gt;
This helps suppliers return more suitable accommodation options.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Minimum Cost per Night per Room ===&lt;br /&gt;
Optional minimum nightly room budget.&lt;br /&gt;
&lt;br /&gt;
Useful when requesting accommodation within a preferred pricing range.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Maximum Cost per Night per Room ===&lt;br /&gt;
Optional maximum nightly room budget.&lt;br /&gt;
&lt;br /&gt;
Helps suppliers avoid quoting accommodation outside budget requirements.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Response Due Date ===&lt;br /&gt;
The deadline by which accommodation providers or agents should respond to the request.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Notes &amp;amp; Comments ==&lt;br /&gt;
&lt;br /&gt;
=== Additional Information for Agent ===&lt;br /&gt;
Free-text notes intended for accommodation providers or booking agents.&lt;br /&gt;
&lt;br /&gt;
Typical information may include:&lt;br /&gt;
&lt;br /&gt;
* Preferred room types&lt;br /&gt;
* Required amenities&lt;br /&gt;
* Breakfast or parking requirements&lt;br /&gt;
* Accessibility requests&lt;br /&gt;
* Special guest requirements&lt;br /&gt;
&lt;br /&gt;
This content is included in the generated PDF.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Team Internal Comments ===&lt;br /&gt;
Internal-only notes visible to EventR users.&lt;br /&gt;
&lt;br /&gt;
These comments are intended for operational or planning purposes and are not intended for accommodation suppliers.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
* Internal approval notes&lt;br /&gt;
* Supplier preferences&lt;br /&gt;
* Budget discussions&lt;br /&gt;
* Booking reminders&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Draft Handling ==&lt;br /&gt;
Rooming lists support unsaved drafts.&lt;br /&gt;
&lt;br /&gt;
If the user attempts to:&lt;br /&gt;
&lt;br /&gt;
* Close the modal&lt;br /&gt;
* Switch rooming lists&lt;br /&gt;
* Refresh data&lt;br /&gt;
* Create a new draft&lt;br /&gt;
&lt;br /&gt;
while unsaved changes exist, EventR will prompt the user to:&lt;br /&gt;
&lt;br /&gt;
* Save changes&lt;br /&gt;
* Discard changes&lt;br /&gt;
&lt;br /&gt;
This helps prevent accidental data loss.&lt;br /&gt;
| style=&amp;quot;width:40%; vertical-align:top;&amp;quot; |&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.49.46.png|thumb|Example: Draft rooming list]]&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.58.44.png|thumb|Multiple rooming list view]]&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=Orders&amp;diff=367</id>
		<title>Orders</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=Orders&amp;diff=367"/>
		<updated>2026-05-07T10:03:48Z</updated>

		<summary type="html">&lt;p&gt;Samh: /* Accessing Rooming Lists */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Infobox Feature&lt;br /&gt;
 | name = Rooming Lists&lt;br /&gt;
 | version = Unreleased&lt;br /&gt;
 | tier = Standard, Premium and Enterprise&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
= Overview =&lt;br /&gt;
The &#039;&#039;&#039;Rooming List&#039;&#039;&#039; feature allows users to create, manage, save, and generate accommodation request PDFs for hotels or accommodation suppliers. It acts as a central workspace for collecting stay requirements, guest accommodation preferences, and booking details related to an itinerary. &lt;br /&gt;
&lt;br /&gt;
= Accessing Rooming Lists =&lt;br /&gt;
{| style=&amp;quot;width:100%; margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width:60%; vertical-align:top;&amp;quot; |&lt;br /&gt;
To find the rooming list functionality, select &#039;&#039;&#039;Create Rooming List&#039;&#039;&#039; from the itinerary accommodation section in the ECH. This opens the Rooming List workspace in a full-screen modal.&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:40%; vertical-align:top;&amp;quot; |&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.21.54.png|thumb| When you have no existing accommodations, button is located bottom centre. ]]&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.38.33.png|thumb|Button moves into the header when you have existing accommodations.]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
= Managing Rooming Lists =&lt;br /&gt;
{| style=&amp;quot;width:100%; margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width:60%; vertical-align:top;&amp;quot; |To create a rooming list, select &#039;&#039;&#039;Create Rooming List&#039;&#039;&#039; from the itinerary accommodation section. This opens the Rooming List workspace in a full-screen modal.&lt;br /&gt;
&lt;br /&gt;
New rooming lists begin as unsaved drafts until they are saved.&lt;br /&gt;
&lt;br /&gt;
When creating a new rooming list, the form is automatically pre-filled using information from the selected itinerary, including dates, location, and lead booker details (You) where available.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Layout Overview ===&lt;br /&gt;
The Rooming List workspace is divided into four main sections:&lt;br /&gt;
&lt;br /&gt;
* Top Bar&lt;br /&gt;
* Sidebar&lt;br /&gt;
* Main Form&lt;br /&gt;
* Bottom Bar&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Top Bar ==&lt;br /&gt;
&lt;br /&gt;
=== Reset ===&lt;br /&gt;
Restores the currently selected rooming list back to its last saved state.&lt;br /&gt;
&lt;br /&gt;
If editing a new unsaved draft, the form will revert to its original pre-filled itinerary values.&lt;br /&gt;
&lt;br /&gt;
=== Create New ===&lt;br /&gt;
Creates a new unsaved rooming list draft while keeping the current modal open.&lt;br /&gt;
&lt;br /&gt;
If unsaved changes exist, the user will be prompted to save or discard them before continuing.&lt;br /&gt;
&lt;br /&gt;
=== Close ===&lt;br /&gt;
Closes the Rooming List modal.&lt;br /&gt;
&lt;br /&gt;
If there are unsaved changes, the user will be prompted to save or discard the draft before closing.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Sidebar ==&lt;br /&gt;
The sidebar contains all saved rooming lists for the currently selected itinerary.&lt;br /&gt;
&lt;br /&gt;
=== Search ===&lt;br /&gt;
Filters saved rooming lists by title.&lt;br /&gt;
&lt;br /&gt;
=== Refresh ===&lt;br /&gt;
Reloads the latest rooming lists from the server without closing the modal.&lt;br /&gt;
&lt;br /&gt;
=== Rooming List Entries ===&lt;br /&gt;
Displays all saved rooming lists ordered by most recently updated first.&lt;br /&gt;
&lt;br /&gt;
Each entry displays:&lt;br /&gt;
&lt;br /&gt;
* Rooming list title&lt;br /&gt;
* Last modified date and time&lt;br /&gt;
&lt;br /&gt;
Selecting a different rooming list will load its saved data into the form.&lt;br /&gt;
&lt;br /&gt;
If unsaved changes exist, the user will be prompted to save or discard them before switching.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Bottom Bar ==&lt;br /&gt;
&lt;br /&gt;
=== Save ===&lt;br /&gt;
Saves the current rooming list.&lt;br /&gt;
&lt;br /&gt;
Once saved:&lt;br /&gt;
&lt;br /&gt;
* The rooming list becomes persistent&lt;br /&gt;
* It appears in the sidebar&lt;br /&gt;
* Future edits can be restored using Reset&lt;br /&gt;
&lt;br /&gt;
=== Delete ===&lt;br /&gt;
Deletes the currently selected saved rooming list.&lt;br /&gt;
&lt;br /&gt;
This action cannot be undone.&lt;br /&gt;
&lt;br /&gt;
If working on an unsaved draft, this button instead discards the draft.&lt;br /&gt;
&lt;br /&gt;
=== Generate PDF ===&lt;br /&gt;
Generates a PDF version of the current rooming list using all entered form data.&lt;br /&gt;
&lt;br /&gt;
The PDF is designed for sharing with hotels, accommodation providers, or booking agents.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Form Fields ==&lt;br /&gt;
&lt;br /&gt;
== General Information ==&lt;br /&gt;
&lt;br /&gt;
=== Order Name * ===&lt;br /&gt;
The title of the rooming list.&lt;br /&gt;
&lt;br /&gt;
This is used:&lt;br /&gt;
&lt;br /&gt;
* In the sidebar list&lt;br /&gt;
* As the PDF title&lt;br /&gt;
* To help identify accommodation requests&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
* “Trip to Milan”&lt;br /&gt;
* “Barcelona Conference Accommodation”&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Contact Name ===&lt;br /&gt;
The primary contact person responsible for the booking or accommodation request.&lt;br /&gt;
&lt;br /&gt;
This is typically pre-filled using the current user profile.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Phone Number ===&lt;br /&gt;
The primary contact phone number for accommodation providers to use when responding to the request.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Contact Email ===&lt;br /&gt;
The main email address accommodation providers should use for communication.&lt;br /&gt;
&lt;br /&gt;
This field is usually pre-filled from the logged-in user profile.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Additional Emails ===&lt;br /&gt;
Optional comma-separated email addresses that should also receive accommodation communications or copies of the generated PDF.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;ops@company.com, travel@company.com&amp;lt;/code&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Event Location ===&lt;br /&gt;
The destination, venue, or event location related to the accommodation request.&lt;br /&gt;
&lt;br /&gt;
This location helps suppliers understand where accommodation proximity is required.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Stay Dates * ===&lt;br /&gt;
The requested accommodation check-in and check-out date range.&lt;br /&gt;
&lt;br /&gt;
These dates are typically pre-filled from the itinerary.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= Accommodation Requirements =&lt;br /&gt;
&lt;br /&gt;
=== Select Pending Accommodations ===&lt;br /&gt;
Selects an existing pending hotel/accommodation item from the itinerary.&lt;br /&gt;
&lt;br /&gt;
When selected:&lt;br /&gt;
&lt;br /&gt;
* Related guest information can be used&lt;br /&gt;
* Room counts may auto-populate&lt;br /&gt;
* Guest data can be included in the generated PDF&lt;br /&gt;
&lt;br /&gt;
Only accommodations currently marked as &#039;&#039;&#039;Pending&#039;&#039;&#039; are available.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Number of Rooms Required ===&lt;br /&gt;
The total number of rooms required for the stay.&lt;br /&gt;
&lt;br /&gt;
This may automatically populate based on the selected accommodation’s guest assignments, but can also be edited manually.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Maximum Number of Accommodations to Split * ===&lt;br /&gt;
Defines how many separate hotels or accommodation providers the booking can be split across.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; = all guests must stay in the same hotel&lt;br /&gt;
* &amp;lt;code&amp;gt;2&amp;lt;/code&amp;gt; = guests may be split between two hotels&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Maximum Distance from Event ===&lt;br /&gt;
Optional distance limit between the accommodation and the event location.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
* “5km”&lt;br /&gt;
* “15 minute walk”&lt;br /&gt;
&lt;br /&gt;
This helps suppliers return more suitable accommodation options.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Minimum Cost per Night per Room ===&lt;br /&gt;
Optional minimum nightly room budget.&lt;br /&gt;
&lt;br /&gt;
Useful when requesting accommodation within a preferred pricing range.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Maximum Cost per Night per Room ===&lt;br /&gt;
Optional maximum nightly room budget.&lt;br /&gt;
&lt;br /&gt;
Helps suppliers avoid quoting accommodation outside budget requirements.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Response Due Date ===&lt;br /&gt;
The deadline by which accommodation providers or agents should respond to the request.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= Notes &amp;amp; Comments =&lt;br /&gt;
&lt;br /&gt;
=== Additional Information for Agent ===&lt;br /&gt;
Free-text notes intended for accommodation providers or booking agents.&lt;br /&gt;
&lt;br /&gt;
Typical information may include:&lt;br /&gt;
&lt;br /&gt;
* Preferred room types&lt;br /&gt;
* Required amenities&lt;br /&gt;
* Breakfast or parking requirements&lt;br /&gt;
* Accessibility requests&lt;br /&gt;
* Special guest requirements&lt;br /&gt;
&lt;br /&gt;
This content is included in the generated PDF.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Team Internal Comments ===&lt;br /&gt;
Internal-only notes visible to EventR users.&lt;br /&gt;
&lt;br /&gt;
These comments are intended for operational or planning purposes and are not intended for accommodation suppliers.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
* Internal approval notes&lt;br /&gt;
* Supplier preferences&lt;br /&gt;
* Budget discussions&lt;br /&gt;
* Booking reminders&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
== Draft Handling ==&lt;br /&gt;
Rooming lists support unsaved drafts.&lt;br /&gt;
&lt;br /&gt;
If the user attempts to:&lt;br /&gt;
&lt;br /&gt;
* Close the modal&lt;br /&gt;
* Switch rooming lists&lt;br /&gt;
* Refresh data&lt;br /&gt;
* Create a new draft&lt;br /&gt;
&lt;br /&gt;
while unsaved changes exist, EventR will prompt the user to:&lt;br /&gt;
&lt;br /&gt;
* Save changes&lt;br /&gt;
* Discard changes&lt;br /&gt;
&lt;br /&gt;
This helps prevent accidental data loss.&lt;br /&gt;
| style=&amp;quot;width:40%; vertical-align:top;&amp;quot; |&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.49.46.png|thumb|Example: Draft rooming list]]&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.58.44.png|thumb|Multiple rooming list view]]&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
	<entry>
		<id>https://eventrwiki.softpauer.com/index.php?title=Orders&amp;diff=365</id>
		<title>Orders</title>
		<link rel="alternate" type="text/html" href="https://eventrwiki.softpauer.com/index.php?title=Orders&amp;diff=365"/>
		<updated>2026-05-07T10:02:11Z</updated>

		<summary type="html">&lt;p&gt;Samh: /* Managing Rooming Lists */&lt;/p&gt;
&lt;hr /&gt;
&lt;div&gt;{{Infobox Feature&lt;br /&gt;
 | name = Rooming Lists&lt;br /&gt;
 | version = Unreleased&lt;br /&gt;
 | tier = Standard, Premium and Enterprise&lt;br /&gt;
}}&lt;br /&gt;
&lt;br /&gt;
== Overview ==&lt;br /&gt;
The &#039;&#039;&#039;Rooming List&#039;&#039;&#039; feature allows users to create, manage, save, and generate accommodation request PDFs for hotels or accommodation suppliers. It acts as a central workspace for collecting stay requirements, guest accommodation preferences, and booking details related to an itinerary. &lt;br /&gt;
&lt;br /&gt;
== Accessing Rooming Lists ==&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;width:100%; margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width:60%; vertical-align:top;&amp;quot; |&lt;br /&gt;
To find the rooming list functionality, select &#039;&#039;&#039;Create Rooming List&#039;&#039;&#039; from the itinerary accommodation section in the ECH. This opens the Rooming List workspace in a full-screen modal.&lt;br /&gt;
&lt;br /&gt;
| style=&amp;quot;width:40%; vertical-align:top;&amp;quot; |&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.21.54.png|thumb| When you have no existing accommodations, button is located bottom centre. ]]&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.38.33.png|thumb|Button moves into the header when you have existing accommodations.]]&lt;br /&gt;
|}&lt;br /&gt;
&lt;br /&gt;
== Managing Rooming Lists ==&lt;br /&gt;
&lt;br /&gt;
{| style=&amp;quot;width:100%; margin:auto;&amp;quot;&lt;br /&gt;
|-&lt;br /&gt;
| style=&amp;quot;width:60%; vertical-align:top;&amp;quot; | &lt;br /&gt;
&lt;br /&gt;
When creating a new rooming list, the form is automatically pre-filled using information from the selected itinerary, including dates, location, and lead booker details (You) where available.&lt;br /&gt;
&lt;br /&gt;
== Creating a Rooming List ==&lt;br /&gt;
To create a rooming list, select &#039;&#039;&#039;Create Rooming List&#039;&#039;&#039; from the itinerary accommodation section. This opens the Rooming List workspace in a full-screen modal.&lt;br /&gt;
&lt;br /&gt;
New rooming lists begin as unsaved drafts until they are saved.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= Layout Overview =&lt;br /&gt;
The Rooming List workspace is divided into four main sections:&lt;br /&gt;
&lt;br /&gt;
* Top Bar&lt;br /&gt;
* Sidebar&lt;br /&gt;
* Main Form&lt;br /&gt;
* Bottom Bar&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= Top Bar =&lt;br /&gt;
&lt;br /&gt;
=== Reset ===&lt;br /&gt;
Restores the currently selected rooming list back to its last saved state.&lt;br /&gt;
&lt;br /&gt;
If editing a new unsaved draft, the form will revert to its original pre-filled itinerary values.&lt;br /&gt;
&lt;br /&gt;
=== Create New ===&lt;br /&gt;
Creates a new unsaved rooming list draft while keeping the current modal open.&lt;br /&gt;
&lt;br /&gt;
If unsaved changes exist, the user will be prompted to save or discard them before continuing.&lt;br /&gt;
&lt;br /&gt;
=== Close ===&lt;br /&gt;
Closes the Rooming List modal.&lt;br /&gt;
&lt;br /&gt;
If there are unsaved changes, the user will be prompted to save or discard the draft before closing.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= Sidebar =&lt;br /&gt;
The sidebar contains all saved rooming lists for the currently selected itinerary.&lt;br /&gt;
&lt;br /&gt;
=== Search ===&lt;br /&gt;
Filters saved rooming lists by title.&lt;br /&gt;
&lt;br /&gt;
=== Refresh ===&lt;br /&gt;
Reloads the latest rooming lists from the server without closing the modal.&lt;br /&gt;
&lt;br /&gt;
=== Rooming List Entries ===&lt;br /&gt;
Displays all saved rooming lists ordered by most recently updated first.&lt;br /&gt;
&lt;br /&gt;
Each entry displays:&lt;br /&gt;
&lt;br /&gt;
* Rooming list title&lt;br /&gt;
* Last modified date and time&lt;br /&gt;
&lt;br /&gt;
Selecting a different rooming list will load its saved data into the form.&lt;br /&gt;
&lt;br /&gt;
If unsaved changes exist, the user will be prompted to save or discard them before switching.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= Bottom Bar =&lt;br /&gt;
&lt;br /&gt;
=== Save ===&lt;br /&gt;
Saves the current rooming list.&lt;br /&gt;
&lt;br /&gt;
Once saved:&lt;br /&gt;
&lt;br /&gt;
* The rooming list becomes persistent&lt;br /&gt;
* It appears in the sidebar&lt;br /&gt;
* Future edits can be restored using Reset&lt;br /&gt;
&lt;br /&gt;
=== Delete ===&lt;br /&gt;
Deletes the currently selected saved rooming list.&lt;br /&gt;
&lt;br /&gt;
This action cannot be undone.&lt;br /&gt;
&lt;br /&gt;
If working on an unsaved draft, this button instead discards the draft.&lt;br /&gt;
&lt;br /&gt;
=== Generate PDF ===&lt;br /&gt;
Generates a PDF version of the current rooming list using all entered form data.&lt;br /&gt;
&lt;br /&gt;
The PDF is designed for sharing with hotels, accommodation providers, or booking agents.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= Form Fields =&lt;br /&gt;
&lt;br /&gt;
== General Information ==&lt;br /&gt;
&lt;br /&gt;
=== Order Name * ===&lt;br /&gt;
The title of the rooming list.&lt;br /&gt;
&lt;br /&gt;
This is used:&lt;br /&gt;
&lt;br /&gt;
* In the sidebar list&lt;br /&gt;
* As the PDF title&lt;br /&gt;
* To help identify accommodation requests&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
* “Trip to Milan”&lt;br /&gt;
* “Barcelona Conference Accommodation”&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Contact Name ===&lt;br /&gt;
The primary contact person responsible for the booking or accommodation request.&lt;br /&gt;
&lt;br /&gt;
This is typically pre-filled using the current user profile.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Phone Number ===&lt;br /&gt;
The primary contact phone number for accommodation providers to use when responding to the request.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Lead Booker Contact Email ===&lt;br /&gt;
The main email address accommodation providers should use for communication.&lt;br /&gt;
&lt;br /&gt;
This field is usually pre-filled from the logged-in user profile.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Additional Emails ===&lt;br /&gt;
Optional comma-separated email addresses that should also receive accommodation communications or copies of the generated PDF.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
&amp;lt;code&amp;gt;ops@company.com, travel@company.com&amp;lt;/code&amp;gt;&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Event Location ===&lt;br /&gt;
The destination, venue, or event location related to the accommodation request.&lt;br /&gt;
&lt;br /&gt;
This location helps suppliers understand where accommodation proximity is required.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Stay Dates * ===&lt;br /&gt;
The requested accommodation check-in and check-out date range.&lt;br /&gt;
&lt;br /&gt;
These dates are typically pre-filled from the itinerary.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= Accommodation Requirements =&lt;br /&gt;
&lt;br /&gt;
=== Select Pending Accommodations ===&lt;br /&gt;
Selects an existing pending hotel/accommodation item from the itinerary.&lt;br /&gt;
&lt;br /&gt;
When selected:&lt;br /&gt;
&lt;br /&gt;
* Related guest information can be used&lt;br /&gt;
* Room counts may auto-populate&lt;br /&gt;
* Guest data can be included in the generated PDF&lt;br /&gt;
&lt;br /&gt;
Only accommodations currently marked as &#039;&#039;&#039;Pending&#039;&#039;&#039; are available.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Number of Rooms Required ===&lt;br /&gt;
The total number of rooms required for the stay.&lt;br /&gt;
&lt;br /&gt;
This may automatically populate based on the selected accommodation’s guest assignments, but can also be edited manually.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Maximum Number of Accommodations to Split * ===&lt;br /&gt;
Defines how many separate hotels or accommodation providers the booking can be split across.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
* &amp;lt;code&amp;gt;1&amp;lt;/code&amp;gt; = all guests must stay in the same hotel&lt;br /&gt;
* &amp;lt;code&amp;gt;2&amp;lt;/code&amp;gt; = guests may be split between two hotels&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Maximum Distance from Event ===&lt;br /&gt;
Optional distance limit between the accommodation and the event location.&lt;br /&gt;
&lt;br /&gt;
Example:&lt;br /&gt;
&lt;br /&gt;
* “5km”&lt;br /&gt;
* “15 minute walk”&lt;br /&gt;
&lt;br /&gt;
This helps suppliers return more suitable accommodation options.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Minimum Cost per Night per Room ===&lt;br /&gt;
Optional minimum nightly room budget.&lt;br /&gt;
&lt;br /&gt;
Useful when requesting accommodation within a preferred pricing range.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Maximum Cost per Night per Room ===&lt;br /&gt;
Optional maximum nightly room budget.&lt;br /&gt;
&lt;br /&gt;
Helps suppliers avoid quoting accommodation outside budget requirements.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Response Due Date ===&lt;br /&gt;
The deadline by which accommodation providers or agents should respond to the request.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= Notes &amp;amp; Comments =&lt;br /&gt;
&lt;br /&gt;
=== Additional Information for Agent ===&lt;br /&gt;
Free-text notes intended for accommodation providers or booking agents.&lt;br /&gt;
&lt;br /&gt;
Typical information may include:&lt;br /&gt;
&lt;br /&gt;
* Preferred room types&lt;br /&gt;
* Required amenities&lt;br /&gt;
* Breakfast or parking requirements&lt;br /&gt;
* Accessibility requests&lt;br /&gt;
* Special guest requirements&lt;br /&gt;
&lt;br /&gt;
This content is included in the generated PDF.&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
=== Team Internal Comments ===&lt;br /&gt;
Internal-only notes visible to EventR users.&lt;br /&gt;
&lt;br /&gt;
These comments are intended for operational or planning purposes and are not intended for accommodation suppliers.&lt;br /&gt;
&lt;br /&gt;
Examples:&lt;br /&gt;
&lt;br /&gt;
* Internal approval notes&lt;br /&gt;
* Supplier preferences&lt;br /&gt;
* Budget discussions&lt;br /&gt;
* Booking reminders&lt;br /&gt;
&lt;br /&gt;
----&lt;br /&gt;
&lt;br /&gt;
= Draft Handling =&lt;br /&gt;
Rooming lists support unsaved drafts.&lt;br /&gt;
&lt;br /&gt;
If the user attempts to:&lt;br /&gt;
&lt;br /&gt;
* Close the modal&lt;br /&gt;
* Switch rooming lists&lt;br /&gt;
* Refresh data&lt;br /&gt;
* Create a new draft&lt;br /&gt;
&lt;br /&gt;
while unsaved changes exist, EventR will prompt the user to:&lt;br /&gt;
&lt;br /&gt;
* Save changes&lt;br /&gt;
* Discard changes&lt;br /&gt;
&lt;br /&gt;
This helps prevent accidental data loss.&lt;br /&gt;
| style=&amp;quot;width:40%; vertical-align:top;&amp;quot; |&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.49.46.png|thumb|Example: Draft rooming list]]&lt;br /&gt;
&lt;br /&gt;
[[File:Screenshot 2026-05-06 at 11.58.44.png|thumb|Multiple rooming list view]]&lt;br /&gt;
|}&lt;/div&gt;</summary>
		<author><name>Samh</name></author>
	</entry>
</feed>