Skip to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Data Validation

Featured Replies

I have a layout with several fields that have validation without user override capability.

A 'Proceed' button takes the user to the next operation.

When a user enters a value into one of the validated fields, but does not tab out, validation does not take place until the 'Proceed' button is hit. So the first step in the 'Proceed' script is a 'go to next field' step which generally causes validation. I set error capture to 'on'. If the field value is invalid an error is detected and I exit the script with an appropriate message. That works in almost all cases. BUT --

For those fields, I use a pop-up list with valid values for the user to select from, but some users think they can put anything into the field. The problem comes when they select one of the values from the drop down list and edit that value without tabbing out. The 'go to next field' in the 'Proceed' script does nothing and the error is not detected until some later step (a 'Perform script' step) and then there is no way to capture the error gracefully.

If they have blanked the field and entered a non-valid value, that error can be captured. It's only when they edit one of the valid values, creating an invalid value, then don't tab out before 'Proceed'ing that the problem occurs.

I have found no script step that I can use to capture this error. Can anyone help??

TIA

Don't allow the user to override the data from the valuelist. The error will be trapped immediately. Choose "Always Validate." In your script, the first line should be "Commit Records."

I agree with Trans. On the one hand, your layout employs strict value checking, but the value lists are at variance because apparently they allow editting.

My addition to this is that I've found it drop-down (as opposed to pop-up) menus discourage users from attempting to enter unwanted data.

Create an account or sign in to comment

Important Information

By using this site, you agree to our Terms of Use.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.