Form Validation Failure

Hi,
When trying to use PPR on radio buttons to make a field mandatory.
when I am deselecting to change criteria I am facing Form Validation Failure error.
why this error will come.
Krishna

Hi Anil,
Thanks for the reply
after setting
Disable Client Side Validation and Disable Server Side Validation Property to "True"
the issue is resolved.
Krishna

Similar Messages

Retain all form field values after input text field validation failure

Hi,
I have a form with 1 input text field, one Command button and one h:selectManyListbox. when User enteres some values in input field and clicks on command button named Add, the value is validated. If input is invalid, then an error message appears next to the field. If input is valid, then the value is added into h:selectManyListbox. Adding to list box is done using Ajax4Jsf.
Probelm:
Let's assume user entered 3 valid values one after another and all are added into the list box. When he enters a wrong value, and error message appears. however, the entered values in list box goes away. Is there a way to retain the values even after validation failure.
Code is given below;
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h"%>
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f"%>
<%@ taglib uri="http://myfaces.apache.org/tomahawk" prefix="t"%>
<%@ taglib uri="http://richfaces.org/rich" prefix="rich"%>
<%@ taglib uri="http://richfaces.org/a4j" prefix="a4j"%>
<h:panelGroup>
     <h:outputLabel for="inputEmailId1" value="Email Id: " />
     <t:inputText value="#{bean.newEmailId}" id="inputEmailId1" maxlength="100" size="40" immediate="true">
          <t:validateEmail message="Enter a valid Email Id." />
     </t:inputText>
     <t:message for="inputEmailId1" styleClass="errorStyleClass" />
</h:panelGroup>
<t:panelGroup style="text-align: left;" >
     <a4j:commandButton value="Add" styleClass="buttonsSub" action="#{bean.addSharedEmails}"
          reRender="inputEmailId1, selectedSharedEmails" />
</t:panelGroup>
<t:panelGroup style="text-align: left;">
     <h:selectManyListbox id="selectedSharedEmails" size="8" style="width:100%;" immediate="true">
          <f:selectItems value="#{bean.sharedEmails}" />
     </h:selectManyListbox>
</t:panelGroup>
Thanks in advance,

Use the attribute "binding" instead of a "value". This will remember the value. You can also make sure that you dont have anything in your constructor or class level that initialises that value to "" or null. Because if JSF is remembering your value but your initialization that gets triggered before the page loading resets it to default values then you need to change that part of the code.

Need help regarding form validation

Hi all,
I have particular doubt regarding form validation. I have a form based on a table. ( One data block ) . I have a function in program unit which return boolean value based on some conditions. I will be calling this function in block validate trigger.
What i need is , if function return false i need to stop any insertion,updation action that's going to be done by forms.( point to control insertion and updation)
I don't want to use form triggure failure builtin. What should i do ? plz guide
regards

what are you going to do stop insert/update upon commit?
-- use on-insert trigger
if allowed_to_insert then
insert_record;
end if;
-- use on-update trigger
if allowed_to_update then
update_record;
end if;
if when entering data, you might want to check set_block_property

Call a Javascritp function after a validation failure

Hi all,
I have a javascript function that is executed on page load. (it works fine)
Now I need to call it after a validation failure
How I can implement this call ?
I am using Apex 4.0.2 and the inline notification, so the page load event is not fired
which "activation" event can i use ?
regards
saverio
Edited by: tirone on 17-giu-2011 9.00
Edited by: tirone on 17-giu-2011 9.04

Thank You Tyson for your quick replay,
and .. I apologize me for mine bad English.
My problem is that after a validation failure (with in line notification) the page load event IS NOT fired (in some case): so my script is not executed.
I would like to execute this script however and I don't know where and how to call it.
I give You more detail ......
I'm working on a page that contain a tabular form; in this form, using my script (called "disable_field"), Ii set to read-only some fields.
I call my script in "Execute when page load" section of page definition.
If the validation failure is produced by an update of some records in my tabular form all is OK : the inline notification is shown, the page is re-loaded and my script is executed.
If I add a new record and, after the submit, a validation fail, the page IS NOT reloaded (I don't know the why) and my script is not executed (so all fields are modifiable and this is not how much I want)
I will appreciate very any help
regards
saverio

Querystring is lost when form validation failes

I have a form that uses form validation and <i>@jpf:validation-error-forward name="validation-failure" return-to="currentPage"</i>.<br><br>
When the validation of the form failes it returns to the current page as it is supposed to but it looses the querystring that i use to show the correct content in the form. :-(<br><br>
I have tryed to find a way to also send the querystring but without success so far. Any ideas anyone?

Can the query string be stored in pageflow scoped variable? That way it will exist as long as the portlet instance exists.
--SJ

Tabular Form Validation not working in tabular form APEX 4.0

Hi,
I am using APEX 4.0. I have a tabular form with Tabular form validation done with it.
Item not null is the validation.. so if I dont type any value in the any of the fields in the tabular form and press the Submit button, the first time error is shown... but when I click the Submit button again, with still the empty rows the page is submitted.
How to resolve this issue?
Edited by: Suzi on Oct 5, 2010 11:13 AM

Look at this thread - Re: Validations of tabular forms in 4.0

Is there a way to bypass the form Validation

I'm getting really upset with the Coldfusion built-in form validation for any HTML formfield ending by _date , _required, _time and so on...
My application proposes to the users to create some Properties for an object and later on to modify the values for all these properties.
I've got a piece of code building dynamically some form fields named just like the properties (by a simple cfloop on a DB query getting the property list).
And a registering page to records the new value in the DB.
But it crashes onto the classical "
Form entries are incomplete or invalid.
I can't control what the users set as property name (one of them was Checklist_required).
Is there any way to prevent this error by disabling this auto validation ?
(I'd like to avoid having to rename any field dynamically created and rename any forms variables before registering them on the DB : it's just NO WAY for me to rename the properties created by the users)

Fober1, that's not how it works. It's pretty much the ultimate example of the disjoint between how HTML forms work and how the naive CFML Cfform / cfinput design wished they work.
When a request is being processed by the coldfusion server, it just looks at the list of FORM (POST) variable names (whether it came from cfform or not; URL/GET params are exempt), and for those with certain suffixes (_date, _required, etc.), and it assumes their existence is intended to request validation another field without that suffix. It doesn't actually know or care whether form submission, nor the HTML rendered in the user's browser, actually came from "cfform" or "cfinput". The composition of the request that comes in (when a user clicks on "submit", or a hacker uses any tool imaginable) is out of the server's hands. The cfform code is not used during form submission processing, because the receiving template (the form action="this_one.cfm") doesn't even have to be the same template that has the cfform in it. There could be multiple conflicting cfforms directing users to request the same template on a single site, with or without the validation, even without considering what a whole other person might decide to send to your server.
The fact that it can work as intended for a typical user is irrelevant, because the purpose of validation is to deal with the atypical situation. A malicious or merely mischievous user that wanted to circumvent the validation would simply modify a copy of the page to leave out the "validation request" fields. For the developer to truly validate the input, additional code must be written, making the feature not only inadequate, but a complete waste of time. There absolutely should be a way to disable it at worst; Ideally, it would be taken out of coldfusion completely. It's not only useless, it's a security risk, wooing programmers to write code that doesn't do what they think it does.
The error message it gives isn't so great, either, and it's a pity that it can't show more than one validation message at a time, either. If more than one input is invalid, you could end up going through one round after another of submit + back button.
edit: I forgot to add the other important reason that this feature should never have existed: It is a nuisance to everyone else who doesn't want to use it at all, too! Those suffixes simply couldn't have been a worse choice, colliding with probably thousands of peoples' variable names. Why not "*_cfval_date" "*_cfval_time" etc?

Form validation working on one page, but not the other....

Hope someone can help with this.
I have a page below with a load of contact forms which all work fine :
http://www.goodsafariguide.com/judges/judges.php
I've trued to recreate (admittedly mostly by saving as....) the same functionality here :
http://www.goodsafariguide.com/awardssite/judges/
They do work when fulled in correctly, but there's a glitch with the validation.
Basically when you fill in a form incorrectly, the page reloads, with the form's accordion closed. When you open it up, its showing the ugly looking error at the top of the form.
Any ideas what's causing it to act like this, as opposed to the way it works in the first link?
Thanks.

Iain71 wrote:
I've trued to recreate (admittedly mostly by saving as....) the same functionality here :
http://www.goodsafariguide.com/awardssite/judges/
They do work when fulled in correctly, but there's a glitch with the validation.
When looking at the source code I note that - unlike the first page - this one doesn´t contain any references to the ADDT form validation libraries ("../includes/tng/scripts/FormValidation.js" and "../includes/tng/scripts/FormValidation.js.php"), meaning that the validation can´t work.
Cheers,
Günter

What is your strategy for form validation when using MVC pattern?

This is more of a general discussion topic and will not necessarily have a correct answer. I'm using some of the Flex validator components in order to do form validation, but it seems I'm always coming back to the same issue, which is that in the world of Flex, validation needs to be put in the view components since in order to show error messages you need to set the source property of the validator to an instance of a view component. This again in my case seems to lead to me duplicating the code for setting up my Validators into several views. But, in terms of the MVC pattern, I always thought that data validation should happen in the model, since whether or not a piece of data is valid might be depending on business rules, which again should be stored in the model. Also, this way you'd only need to write the validation rules once for all fields that contain the same type of information in your application.
So my question is, what strategies do you use when validating data and using an MVC framework? Do you create all the validators in the views and just duplicate the validator if the exact same rules are needed in some other view, or do you store the validators in the model and somehow reference them from the views, changing the source properties as needed? Or do you use some completely different strategy for validating forms and showing error messages to the user?

Thanks for your answer, JoshBeall. Just to clarify, you would basically create a subclass of e.g. TextInput and add the validation rules to that? Then you'd use your subclass when you need a textinput with validation?
Anyway, I ended up building sort of my own validation framework. Because the other issue I had with the standard validation was that it relies on inheritance instead of composition. Say I needed a TextInput to both check that it doesn't contain an empty string or just space characters, is between 4 and 100 characters long, and follows a certain pattern (e.g. allows only alphanumerical characters). With the Flex built in validators I would have to create a subclass or my own validator in order to meet all the requirements and if at some point I need another configuration (say just a length and pattern restriction) I would have to create another subclass which duplicates most of the rules, or I would have to build a lot of flags and conditional statements into that one subclass. With the framework I created I can just string together different rules using composition, and the filter classes themselves can be kept very simple since they only need to handle a single condition (check the string length for instance). E.g. below is the rule for my username:
library["user_name"] = new EmptyStringFilter( new StringLengthFilter(4,255, new RegExpFilter(/^[a-z0-9\-@\._]+$/i) ) );
<code>library</code> is a Dictionary that contains all my validation rules, and which resides in the model in a ValidationManager class. The framework calls a method <code>validate</code> on the stored filter references which goes through all the filters, the first filter to fail returns an error message and the validation fails:
(library["user_name"] as IValidationFilter).validate("testuser");
I only need to setup the rule once for each property I want to validate, regardless where in the app the validation needs to happen. The biggest plus of course that I can be sure the same rules are applied every time I need to validate e.g. a username.
The second part of the framework basically relies on Chris Callendar's great ErrorTipManager class and a custom subclass of spark.components.Panel (in my case it seemed like the reasonable place to put the code needed, although perhaps extending Form would be even better). ErrorTipManager allows you to force open a error tooltip on a target component easily. The subclass I've created basically allows me to just extend the class whenever I need a form and pass in an array of inputs that I want to validate in the creationComplete handler:
validatableInputs = [{source:productName, validateAs:"product_name"},
                     {source:unitWeight, validateAs:"unit_weight", dataField:"value"},
               {source:unitsPerBox, validateAs:"units_per_box", dataField:"value"},
                    {source:producer, validateAs:"producer"}];
The final step is to add a focusOut handler on the inputs that I want to validate if I want the validation to happen right away. The handler just calls a validateForm method, which in turn iterates through each of the inputs in the validatableInputs array, passing a reference of the input to a suitable validation rule in the model (a reference to the model has been injected into the view for this).
Having written this down I could probably improve the View side of things a bit, remove the dependency on the Panel component and make the API easier (have the framework wire up more of the boilerplate like adding listeners etc). But for now the code does what it needs to.

During an update of the applications on the BlackBerry smartphone an error message may be displayed "BlackBerry Desktop Software failed to validate your BlackBerry device update - Aborting install due to validation failure. Some packages contained unsatis

I have reset both my torch and playbook back to original only thing that I kept was my contact. And still problems I am a few min away from leave my loved blackberry and going android !! Or heaven help us Phone
Issues 1) playbook wont connect to desktop manager anymore
2) Play book has 2 calendar icons with two different settings on them ??? I have one that is currently working with my yahoo email and calendar account.
3) my Phone when connected to desk top software shows the calendar as read only
4) Unable to update my phone says During an update of the applications on the BlackBerry® smartphone an error message may be displayed "BlackBerry Desktop Software failed to validate your BlackBerry device update - Aborting install due to validation failure. Some packages contained unsatisfactory dependencies."
I just want my email and Calendars to work I am tried of spending nights trying to get these deices working !!!
someone please help me. !!
I know you are going to ask I have updated everything last time and it is all as update as it can get.
As for now as I wait I am going to wipe my phone again and just set everything up again !! If I have to even my contacts AHHHH Help I am starting to think crazy thoughts

Did you try to eboot the your PC or laptop where your device is connected ?
I experienced this with my windows laptop, after a failed to do an update, I restart the laptop and my Torch, then retried, and it's worked

Script for Form validator in head causes error

When I use the Window/Behaveiors/ to create a form validator, Dreamweaver CS5 puts script in the Head of page, and seems to work ok. But when I validate page with W3c it says there are errors with code and as Dreamweaver created this I have no idea what to do to put right, so could someone please help. This is code generated by Dreamweaver, all other pages have past with flying colors!
<script type="text/javascript">
function MM_validateForm() { //v4.0
if (document.getElementById){
    var i,p,q,nm,test,num,min,max,errors='',args=MM_validateForm.arguments;
    for (i=0; i<(args.length-2); i+=3) { test=args[i+2]; val=document.getElementById(args[i]);
      if (val) { nm=val.name; if ((val=val.value)!="") {
        if (test.indexOf('isEmail')!=-1) { p=val.indexOf('@');
          if (p<1 || p==(val.length-1)) errors+='- '+nm+' must contain an e-mail address.\n';
        } else if (test!='R') { num = parseFloat(val);
          if (isNaN(val)) errors+='- '+nm+' must contain a number.\n';
          if (test.indexOf('inRange') != -1) { p=test.indexOf(':');
            min=test.substring(8,p); max=test.substring(p+1);
            if (num<min || max<num) errors+='- '+nm+' must contain a number between '+min+' and '+max+'.\n';
      } } } else if (test.charAt(0) == 'R') errors += '- '+nm+' is required.\n'; }
    } if (errors) alert('The following error(s) occurred:\n'+errors);
    document.MM_returnValue = (errors == '');
</script>

If the script is working fine in all browsers, you could put it in an external JS file and link to it, then the W3C validator won't find an error.
If you don't know already, learn about how to do this:
http://www.hypergurl.com/jsfiles.html

Submit by email not working as form validation failed.

Ive created a form with mulitple pages. Three pages require form validation.
Each page is a unique process so I'm trying to use the "Submit button" to only submit that
particular page. I've created dummy fields as defaults to cure the validation problem but
can't seem to get the e-mail button to work. I also created a email dummy button with the
scripting:
EmailSubmitButton.execEvent("click");
I did this to try to force the the form to be sumitted via PDF. I am a novice at this so please
help. I'd be happy to send the form as well for review

You may need to enable usage rights in your form. You must have version 8 to do this. Open the form in Acrobat Pro (not Livecycle), click on Advanced tab, then select "enable usage rights in Adobe Reader"

Trying to understand a WS-I validation failure

I'm trying to understand the following WS-I validation failure message. I'm sure I'm making a basic mistake but I can't find an example of the use case where an xsd is imported. Can someone point out my error?
Thanks,
Bret
Validation failure:
Result failed:
Failure Message: A QName reference that is referring to a schema component, uses a namespace not defined in the targetNamespace attribute on the xs:schema element, or in the namespace attribute on an xs:import element within the xs:schema element.Failure Detail Message:
{http://Messages.xsd}SigReplyMessage,
{http://schemas.xmlsoap.org/wsdl/}string,
{http://Messages.xsd}SigRequestMessage
Element Location: lineNumber=8
My wsdl looks like this:
<definitions targetNamespace="urn:S3SignatureGenerator"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="urn:S3SignatureGenerator"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:messages="http://Messages.xsd">
<types>
<xsd:schema>
<xsd:import id="Messages.xsd"
schemaLocation="../../XSDDocument/Messages.xsd"
namespace="http://Messages.xsd"/>
</xsd:schema>
</types>
<message name="ReturnSignature">
<part name="SigAndExp" type="messages:SigReplyMessage"/>
</message>
<message name="RequestSignature">
<part name="Keys" type="messages:SigRequestMessage"/>
</message>
<portType name="SigGenerator">
<operation name="GetSignature">
<input message="tns:RequestSignature"/>
<output message="tns:ReturnSignature"/>
<fault name="sigFault" message="tns:SigFault"/>
</operation>
</portType>
<message name="SigFault">
<part name="faultMessage" element="string"/>
</message>
<binding name="SigGenSoapHttp" type="tns:SigGenerator">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="GetSignature">
<soap:operation soapAction="urn:S3SignatureGenerator/GetSignature"/>
<input>
<soap:body use="literal" parts="SecretKey PublicKey"/>
</input>
<output>
<soap:body use="literal" parts="Signature"/>
</output>
<fault name="sigFault">
<soap:body use="literal" parts="SecretKey PublicKey"/>
</fault>
</operation>
</binding>
<service name="SignatureGenerationService">
<port name="SigGenSoapHttpPort" binding="tns:SigGenSoapHttp">
<soap:address location="tbd"/>
</port>
</service>
</definitions>
Messages.xsd looks like this:
<?xml version="1.0" encoding="windows-1252" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://www.bret.org/S3test/Messages"
targetNamespace="http://www.bret.org/S3test/Messages"
elementFormDefault="qualified">
<xsd:complexType name="sigRequestMessage">
<xsd:sequence>
<xsd:element name="publicKey" type="xsd:string"/>
<xsd:element name="privateKey" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="sigReplyMessage">
<xsd:sequence>
<xsd:element name="Signature" type="xsd:string"/>
<xsd:element name="expiration" type="xsd:dateTime"/>
</xsd:sequence>
</xsd:complexType>
</xsd:schema>

Hi Bret,
Sorry it's taken me a bit of time to respond, but please find below a run-down of the WS-I related problems I spotted in your WSDL document. The first few are related to the import error you saw, and there's a few others that I'll also discuss. Apologies in advance if you've already spotted and corrected those.
I'll use line numbering based on the formatting of the WSDL and XSD that you supplied.
BP2417 (the one you asked about)
The line number in the error is a red herring. There are two problems here:
- WSDL document, line 29: You're using the XSD type string unqualified - it should be xsd:string.
- WSDL document, lines 8 and 13; schema, lines 3 and 4: The namespaces you're using don't match. Either change the namespaces in the schema to be http://Messages.xsd, or change the namespaces in the WSDL to http://www.bret.org/S3test/Messages.
BP2202
You should declare UTF-8 or UTF-16 encoding when creating WSDL or schema documents. The easiest way to do this is to go to Tools|Preferences, and set JDeveloper's default encoding to either UTF-8 or UTF-16.
BP2032
WSDL document, line 26 and 43: The name attribute of the fault should read SigFault, not sigFault, as WSDL is case-sensitive.
WSDL document, line 44: You should use a soap:fault element, not a soap:body element, to bind a fault, thus:
<soap:fault name="SigFault" use="literal"/>
BP2012
WSDL document, lines 17 and 20: Message parts in a document-bound service like this one should reference XSD elements and not complexTypes. What you need to do is define two elements in your messages schema whose types are SigReplyMessage and SigRequestMessage respectively, and then reference those elements from the WSDL.
WSDL document, line 38: The value of the parts attribute should be Keys to match the name of the part child of the RequestSignature.
WSDL document, line 41: The value of the parts attribute should be SigAndExp to match the name of the part child of the ReturnSignature.
WSDL document, line 44: The value of the parts attribute should be faultMessage to match the name of the part child of the SigFault.
BP2115
WSDL document, lines 17 and 20: The names of the elements should be sigReplyMessage and sigRequestMessage and not SigReplyMessage and SigRequestMessage, again because WSDL is case-sensitive.
WSDL document, line 30: The element attribute of the part references xsd:string, which is not an element but a complexType. You'll need to add an element declaration to your schema, which is of type xsd:string.
I've included corrected versions of your WSDL and schema below, I hope this helps. I also note you've posted a few other messages related to WS-I and WSDL, I hope I've managed to cover those in this message too.
Regards,
Alan.
WSDL:
<?xml version="1.0" encoding="UTF-8" ?>
<definitions targetNamespace="urn:S3SignatureGenerator"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="urn:S3SignatureGenerator"
xmlns:mime="http://schemas.xmlsoap.org/wsdl/mime/"
xmlns:soap12="http://schemas.xmlsoap.org/wsdl/soap12/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/"
xmlns:messages="http://Messages.xsd">
<types>
<xsd:schema>
<xsd:import id="Messages.xsd"
schemaLocation="Messages.xsd"
namespace="http://Messages.xsd"/>
</xsd:schema>
</types>
<message name="ReturnSignature">
<part name="SigAndExp" element="messages:sigReplyMessage"/>
</message>
<message name="RequestSignature">
<part name="Keys" element="messages:sigRequestMessage"/>
</message>
<message name="SigFault">
<part name="faultMessage" element="messages:faultMessage"/>
</message>
<portType name="SigGenerator">
<operation name="GetSignature">
<input message="tns:RequestSignature"/>
<output message="tns:ReturnSignature"/>
<fault name="SigFault" message="tns:SigFault"/>
</operation>
</portType>
<binding name="SigGenSoapHttp" type="tns:SigGenerator">
<soap:binding style="document"
transport="http://schemas.xmlsoap.org/soap/http"/>
<operation name="GetSignature">
<soap:operation soapAction="urn:S3SignatureGenerator/GetSignature"/>
<input>
<soap:body use="literal" parts="Keys"/>
</input>
<output>
<soap:body use="literal" parts="SigAndExp"/>
</output>
<fault name="SigFault">
<soap:fault name="SigFault" use="literal"/>
</fault>
</operation>
</binding>
<service name="SignatureGenerationService">
<port name="SigGenSoapHttpPort" binding="tns:SigGenSoapHttp">
<soap:address location="tbd"/>
</port>
</service>
</definitions>
Schema:
<?xml version="1.0" encoding="UTF-8" ?>
<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns="http://Messages.xsd"
targetNamespace="http://Messages.xsd"
elementFormDefault="qualified">
<xsd:element name="sigRequestMessage">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="publicKey" type="xsd:string"/>
<xsd:element name="privateKey" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="sigReplyMessage">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="Signature" type="xsd:string"/>
<xsd:element name="expiration" type="xsd:dateTime"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element name="faultMessage" type="xsd:string"/>
</xsd:schema>

Form Validations

How to perform form validations in ADF. And also can i customize the behaviour of "Required" property of a UIComponent? I dont want alert boxes to be shown Can i change that?

you might want to think about using one of the popup LOV item types for your employee ID field. popup LOVs are great for cases where you don't want to weigh your page down w/large lists of values. about your validation, if you really want to do it client-side, then javascript's probably the way to go (search google for code). if you do that, though, let the record show that you'd have to fetch your valid values down to your page for your comparison logic, anyhow. i'd consider using a regular htmldb validation for your emp id field. you seemed concerned in your post with the page submission. i'm assuming that's because you didn't want processing to occur unless the validation passes. if that's the case, fear not, it's a simple matter to set your processing to occur only after your validations have passed. check out the available "Process Point"s and "Computation Point"s for htmldb Processes and Computations to see what i mean.
hope this helps,
raj

ORA-29024: Certificate validation failure when trying to redirect to https

Hi, I was trying to redirect the page to another https website using utl_http.request,
I configured Oracle wallet and import the certificate, and successfully to get the webpage content in sqlplus by
select utl_http.request('https://<website>,null,<wallet>,<wallet password>) from dual,
but when I trying to use the same way in a button process of Apex, the error ORA-29024: Certificate validation failure prompt.
Anyone know what wrong with it?
Thanks
Vincent Pek

Hi, Sorry, I found that after i reboot my laptop , it's working now.

Form Validation Failure

Similar Messages

Maybe you are looking for