Collect inputs for an external calculation
POM Forms provides validated Number fields, including range sliders, prefixes, suffixes, and thousands separators. It does not provide a native calculated-result field in the visual form builder.
Use this recipe to collect inputs for a quote request or send them to a calculation service. Do not promise an instant result unless the receiving integration actually returns and displays one.
Define the numeric inputs
For each value, record:
- Unit and meaning
- Minimum and maximum
- Decimal step
- Whether only integers are valid
- Whether the value is required
Build the input form
- Open Forms → Add New.
- Add one Number field per input.
- Set Name, Min Value, Max Value, and Step.
- Enable Integer Only where decimals are invalid.
- Choose Number Input or Range Slider under Control Type.
- Add a visible Prefix or Suffix for currency or units when useful.
- Add contact fields when a person will provide the result.
- Add a Submit Button whose label describes the real action.
Display formatting does not replace validation or define a calculation formula.
Choose the processing path
Quote request
Use AJAX mode with an administrator notification. Include the number-field merge tags and explain in the success message that a person will respond.
External calculation service
Use either:
- Webhook for a JSON copy after the internal POM pipeline.
- Form Action URL (GET) or Form Action URL (POST) when the external endpoint owns the whole submission.
Action URL modes bypass storage, notifications, the Webhook tab, Google Drive uploads, and post creation. POST sends validated values as JSON; GET appends them as query parameters and cannot send uploads.
Verify boundaries
Test minimum, maximum, decimal step, invalid text, and empty values. Confirm the external receiver interprets units and numeric formats exactly as intended.
If a live on-page result is required, it needs a separately implemented and supported integration; do not simulate it with a Hidden field or client-controlled value.