You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Divesh Dutta (JIRA)" <ji...@apache.org> on 2016/06/21 14:02:58 UTC

[jira] [Comment Edited] (OFBIZ-7511) Add proper form validation across the application

    [ https://issues.apache.org/jira/browse/OFBIZ-7511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15341810#comment-15341810 ] 

Divesh Dutta edited comment on OFBIZ-7511 at 6/21/16 2:02 PM:
--------------------------------------------------------------

auto-fields-service handles required option i.e if IN attribute is not optional then required is set to "true" in form widget. so where ever auto-fields-service is used fields will be automatically work as required field, but in forms where you want to make field mandatory but that field in not mandatory in service definition, there is no option available. 

Also forms which are directly not based on service, for those forms, there is no option available. So such cases, this is the only option available i.e you will have to define required explicitly in form.

I don't see any thing to to be fixed at framework level here as auto-fields-service handles this already . Approach taken in ticket can be done when, you cannot use auto-fields-service or  auto-fields-service is used but fields are overridden in form. So my +1 for the approach taken in this ticket. I agree that we can manage this effort at component level instead of each form. 

[~deepak.dixit] what do you have in mind when you say we can fix this required-field at the time of form rendering ? There is no bug in required-field. 




was (Author: diveshdut):
auto-fields-service handles required option i.e if IN attribute is not optional then required is set to "true" in form widget. so where ever auto-fields-service is used fields will be automatically work as required field, but in forms where you want to make field mandatory but that field in not mandatory in service definition, there is no option available. 

Also forms which are directly not based on service, for those forms, there is no option available. So such cases, this is the only option available i.e you will have to define required explicitly in form.

I don't see any thing to to be fixed at framework level here. Deepak what do you have in mind when you say we can fix this required-field at the time of form rendering. There is no bug in required-field. 

> Add proper form validation  across the application
> --------------------------------------------------
>
>                 Key: OFBIZ-7511
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-7511
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: ALL APPLICATIONS
>    Affects Versions: Trunk
>            Reporter: Deepak Dixit
>
> This is the place holder task for adding proper form validation across the application.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)