Contents
Custom fields - Plugixa Car Rental
Custom fields are your own questions on the booking form: a flight number so the desk knows when an arriving customer will land, a driving licence number, “How did you hear about us?”. The customer answers them on the Details step, and the answers are kept on the booking.
Open Plugixa Car Rental, then Custom fields in the Configuration group of the app’s sidebar.
Custom fields is an app. It is on by default and can be switched off in the App manager. While it is off the booking form asks none of the questions, and answers already given stay on their bookings.
The list
| Column | What it shows |
|---|---|
| Label | The question. |
| Type | Short text, Paragraph, Number, Date, Choice or Tick box. |
| Required | Yes or No. |
| Order | The position on the form. |
| Status | On is Published, off is Unpublished. Only Published fields are asked. |
The search box is labelled “Search fields…”.
Adding a field
Click Create.
| Field | Notes |
|---|---|
| Label | Required. “The question as the customer reads it.” |
| Type | What kind of answer the field takes. See below. |
| Options | For Choice only. “One option per line.” Empty lines and repeated options are dropped. A choice needs at least two: “A choice field needs at least two options, one per line.” |
| Help text | “Optional. Shown under the field.” |
| Required | Off by default. On: the booking cannot be completed without an answer. |
| Order | A whole number. Fields are asked from the lowest number up. |
| Status | Published or Unpublished. |
The types
| Type | The customer sees | What is accepted |
|---|---|---|
| Short text | A one-line box | Up to 255 characters. |
| Paragraph | A box of several lines | Up to 2000 characters. |
| Number | A number box | A number: “Please enter a number.” |
| Date | A date picker | A real date: “Please enter a valid date.” |
| Choice | A list to pick from | One of the options, exactly: “Please choose one of the options.” |
| Tick box | A box to tick | Ticked or not. A ticked box is stored as “Yes”; an unticked one is not stored. |
Required fields
A required field left empty stops the booking with a message beside it:
| Type | Message |
|---|---|
| Tick box | “Please tick this box to continue.” |
| Every other type | “Please answer this question.” |
A required Tick box is how you ask the customer to agree to something particular, such as “I will bring a credit card in the driver’s name”.
The answers are checked on the server when the customer completes the booking, so leaving out a required answer, or sending an option that is not on the list, is refused even if somebody gets round the form.
Where the answers go
The answers are stored with the booking when the customer completes it, under the label the question had at that moment. An answer left empty on an optional field is not stored.
| Place | What is shown |
|---|---|
| The booking’s page in the admin | Each answer under its label, with the booking’s other details. See Bookings. |
| The desk email for a confirmed booking | Each answer as a row of the booking summary. See Booking emails. |
The customer’s own confirmation email does not repeat the answers.
Bookings made at the desk
Custom fields are questions for customers booking online. The New booking form in the admin does not ask them; use the booking’s Notes for anything the desk needs to record.
Changing or removing a field
Renaming a question does not change answers already given: each booking keeps the label it was answered under. Unpublishing or deleting a field stops it being asked on new bookings and leaves existing answers in place.
Deleting a field moves it to the trash. Switch the list to Trash to restore it.