Orders, requests, bookings and purchases in an account

Personal history pages show information associated with the current account on this site. The visitor must sign in first. A matching email in another order or form does not transfer that history to the account.

Understand the sections

  • Orders show the visitor's orders, items, amounts and retained payment and delivery information.
  • Requests show account-linked submissions of the site's native forms. This is not a general list of Database records.
  • Service bookings show retained creation details separately from the booking's current state, when available.
  • Purchases show the relevant purchase history and the access state of each purchase. An order total is not the price of a single line.

Browse history

Open a section, refresh its data and select an entry for details. The next page is available when the server returns a continuation. Refresh starts a new view. An empty page means that this request has no accessible entries; it does not mean registration failed.

If a current title or linked object is unavailable, retained history may still be shown. Do not replace retained facts with a different object that has a similar name. A submission acknowledgement does not imply navigation to an arbitrary address or successful payment.

Build a separate data application

To let visitors create and edit their own requests in a collection, configure the collection, site binding and permissions, then add a separate application page. The native form history template does not create that screen automatically.

History pages are for reading. They do not themselves cancel bookings, make payments or grant course access. Signing out or changing accounts must clear the previous list and details.