Hi formspider team,

Please provide column-wise and row wise validation facility.

What is required is to keep the cursor in the same column or row until validation flag is set to TRUE.

Validation flag can be set to TRUE or FALSE by the developer.

Kindly facilitate to keep the cursor in the same column or row and do not exit it until developer decides to exit after validation.

Or else you may decide how to go about adding the validation feature. My development is stuck because I do not have validation facility.

George

**Why column validation is required in a business data entry scenario.**
Consider the user is entering a Sales Order. The important columns to be entered are: 1. ITEM code, 2.Unit of Measurement(UOM), 3.Quantity, 4.Cost and 5. Sales Price.
1. When item code is entered (manually or through an LOV) it will populate UOM, and cost and sales price.  
2. Unit of Measurement(UOM) (there could be multiple UOM for the same item) - this can be optionally populated through an LOV. Eg. Box, Bag, Kg etc.
3. Quantity ordered - Eg. 2, 3 or 2.3,1.2 etc.  Here if the unit is Box and 2 is entered that means 2 boxes; But if 1.2 is entered it means 1 box and 2 pieces. This is based on how UOM is defined in the Item Master table.
4. Unit Cost - Fixed rate from the Item master table.
5. Sales Price - either fixed amt from the Item master or can be manually entered.

Now kindly note that UOM is based on ITEM. Therefore, ITEM must first be avaiable if UOM has to be determined as one ITEM may have multiple UOMs. This in turn affects the way quantity is entered and calculated. Other calculations for discount, tax, profit etc are based on these base data. If these cannot first be entered and validated none of the subsequent data entry and calculations are possible.
In this scenario column wise validation is the ultimate solution. Even record wise validation is insufficient.

asked 10 May '15, 03:56

grajan777's gravatar image

grajan777
1011226
accept rate: 10%

edited 12 May '15, 06:09

Serdar's gravatar image

Serdar ♦♦
100k4


Hi George,

These requirements are easily enforced in Formspider and many customers do so.

We think forcing the user to stay in a field until she enters a value is an old style of creating UI. So Formspider is not focused on making users stuck in a field. But for a dependant field, you can easily validate that the fields it depends on are populated correctly.

The best way to do this the OK (save,next etc...) button on the screen. You can wait until the user attempts to save an order, and inform her about her errors such as missing an item code or UOM.

Alternatively, if you want to inform the user that field B's values depend on field A while she is attempting to select a value for B, you can do so by showing a warning on the valueChanged event of field B (or on the button press event for the button which shows the relevant LOV for field B.) But like I said I'd go with validating at the OK button.

All the necessary API's exist to make these validations.

For validating multiple columns in one row, look at api_datasource.getRow. For validating multiple rows at once, look at API's api_datasource.getRows, api_datasource.getQuery, api_datasource.getRequiredColumnViolations etc...

Screens like the one you have described have been built many times with Formspider.

Hope this helps.

Kind Regards, Yalim

link

answered 13 May '15, 09:32

Yalim%20Gerger's gravatar image

Yalim Gerger ♦♦
1.8k5
accept rate: 15%

Hi Yalim,

Thanks for the answer.

A. Validating while user saves. It is OK if the Quotation, for example, user entering is 10/20 lines. But our Oracle Forms user is entering a quotation of 200/300 printed pages (around 100,000/200,000 lines). And it is fast data entry not just leisurely entering data in an easy way. The company wants user mistakes to be caught and corrected immediately as soon as a mistake is committed.

Further, the user forgets to save the data until pages of data is entered. Validating pages of data is not at all practical. Ah! one solution is to force the user to save the data on every line and validate at that time. When the company asks why don't you correct errors column by column, we cannot simply say, formspider do not like this idea.

continued...

(14 May '15, 06:27) grajan777

B. As you suggested, I am using valueChanged event to warn and validate. There is a problem using this event for validation. If user enters wrong data he is warned and forced into the same column. Now he can easily escape validation if he simply presses the tab key without making any changes. The valueChanged event is not fired in this case and ultimately the validation fails.

Though the user is responsible for entering correct data, the development team is blamed and fired for not forcing the user to enter correct data. This was easily implemented in Oracle Forms to the satisfaction of all concerned. Oracle Form is data conscious and business conscious. No surprise, it became a top leader as a business development tool.

C. I am already using the row validation as you suggested.

Our problem is that the user cannot be forced by the system to enter correct data column by column. Column validation is the ultimate solution for our kind of development.

George

(14 May '15, 06:27) grajan777

I support column validation too! And I mean REAL column validation. Now, on a dateFiled, valueChanged trigger is fired up only if we change the value using that calendar button, and IS NOT fired if we manually change the value. Validation is a very important feature as is direct linked to data consistency. The more validation methods we have, the better.

Now, I notice that we cannot stuck the user in a record. CurrentRowChanged event is useful for data syncronization on screen, but for validation it would be very useful an event like BEFORE_CURRENT_ROW_CHANGE, that would allow us to forbid exiting the current row until certain conditions are satisfied.

Please understand that in real life applications, validation is very often enforced by the customer/end user and it is not up to developer, so please supply us with some solid validation methods.

link

answered 24 Jun '16, 03:16

brg's gravatar image

brg
1114
accept rate: 0%

edited 24 Jun '16, 03:44

Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Tags:

×4

Asked: 10 May '15, 03:56

Seen: 1,037 times

Last updated: 24 Jun '16, 03:44


© Copyright Gerger 2017