Skip to main content

Web Form Values

Aeon's patron-facing web forms (the New User Registration form, the request forms, and so on) each end with a submit button — the button a researcher clicks to send the form. The Web Form Values table lets you control the wording on those buttons per form, so a request form can read Submit Request while a registration form reads Register instead of a generic default.

Each row maps one form to one submit button: the Form Name identifies which web page the button lives on, the Submit Button Value is the internal value the form posts, and the Submit Button Text is the label the patron actually sees. Most sites set these up once when the web pages are first configured and rarely revisit them — you come back to this table when you rename a form, add a new form to your web interface, or want to reword a button (for example, changing Submit to Place Request).

When you'll use this
  • You've added a new web form and want its submit button to read something specific instead of the default.
  • You want to reword an existing button — for instance, changing a request form's button from Submit to Submit Request.
  • You're reviewing your web interface configuration and want to confirm which forms have custom button labels defined.
This controls button labels, not form fields

The Web Form Values table only governs submit-button text. It does not add input fields, dropdowns, or other content to a form — that's done in the web page markup itself, alongside settings like Custom Field Definitions and Custom Dropdowns. Think of this table as "what the button says," not "what the form asks for."

Opening the Web Form Values table​

  1. Open the Customization Manager.
  2. In the left navigation, expand the Web Interface group.
  3. Select Web Form Values.

The page opens to a table of the form values currently defined for your site, with three columns: Form Name, Submit Button Value, and Submit Button Text. If nothing has been configured yet, you'll see No web form values defined with a prompt to Add a form value to get started.

Adding a form value​

  1. On the Web Form Values page, click Add Form Value (top-right).
  2. In the Add Form Value dialog, fill in all three fields:
    • Form Name — the name of the web form the button belongs to (for example, DefaultRequest).
    • Submit Button Value — the value the button posts when the form is submitted (for example, Submit Request).
    • Submit Button Text — the text the patron sees on the button (for example, Submit Request).
  3. Click Add.

A Form value added confirmation appears and the new row shows in the table.

All three fields are required

The Add button stays disabled until Form Name, Submit Button Value, and Submit Button Text all have a value. Each field accepts up to 100 characters. Leading and trailing spaces are trimmed automatically.

Editing a form value​

  1. Find the row you want to change.
  2. Click the pencil icon at the end of that row.
  3. The Edit Form Value dialog opens pre-filled with the current values. Adjust Form Name, Submit Button Value, or Submit Button Text as needed.
  4. Click Update.

You'll see a Form value updated confirmation, and the table reflects the change.

Deleting a form value​

  1. Click the trash icon at the end of the row you want to remove.
  2. A Delete Form Value confirmation asks Are you sure you want to delete the form value for "[Form Name]"? This action cannot be undone.
  3. Click Delete to confirm, or Cancel to keep the row.

A Form value deleted confirmation appears once the row is removed.

Deletes are permanent

There's no undo. Removing a row deletes that form's custom submit-button configuration; the form will fall back to whatever default its web page markup provides. Re-create the row if you need it back.

Permissions
  • Viewing the Web Form Values table is available to any signed-in staff member.
  • Adding, editing, and deleting rows requires the Data & Fields configuration permission (the role setting covering custom fields, lookup tables, and field definitions). Without it, the save is rejected and you'll see a Failed to add form value (or update/delete) error. Configuration permissions are managed per role in the Customization Manager's permission settings.
Editor review — remove this callout (and the HTML comment below it) before publishing

A couple of things only an SME can settle on this page:

  • Confirm the framing and examples. The inventory paired this page with a V6 article that's actually about adding custom field HTML to web forms — a different feature. This page was written from the V7 code, which shows the table edits submit-button labels only (Form Name / Submit Button Value / Submit Button Text in the WebFormValues table). Confirm that scope is right and that the example values used (DefaultRequest, Submit Request) match real-world usage.
  • Screenshots needed: (1) the Web Form Values table with a few rows; (2) the Add Form Value dialog showing the three fields.

The full generation metadata — sources, files read, and verifications, i.e. the detail a tool like Claude would need to regenerate this page — is in the HTML comment directly below this callout. When this page has been reviewed and approved, delete both this callout and that comment; a page with no Editor-review callout is one that's done.