Width of Hightlighted Field on Validation Error

Hi
Is there anyway to control the width of the Red Highlight that the Mandatory fields get?
Regards
Meir

Similar Messages

Mandatory fields causing validation errors

The problem is that we have a process train and the user can't enter fields that are marked as mandatory on the Entity Object until they get further down the process train. However, you cannot get past the first step (refer to this image: http://xs344.xs.to/xs344/09412/screen444823.png).
The weird part is that there are 2 validation checks, the first checks if the fields on the page are validated (exactly what I need), THEN it checks all of the EO validations. I do not want the later.
What is the best work around for this?

Hi,
Did you try using immediate=true attribute for passing the validation phase?

Validation Errors with adf dialog

Hi!
We are using Oracle BC and ADF Faces.
I'm having some validation problems with a adf dialog.
The scenario is the following:
An editing page.
A field in this page has a LOV.
The LOV has some search criteria, and a search button.
When the button is clicked, the results appear on a table. The user selects one and the lov is closed.
When filling the editing page the Lov is opened.
When i don't put search criteria in the fields, no validation errors appear.
If i put one or more search criterias, validations errors of the editing page appear.
Why is this happening?
Thanks.

Please post a link to your site.
Gramps

Validation error appearing for the wrong field

Hi friends
i am facing aissue with my application
I have 3 Field
1.     Department (Field 1)
2.     Emp id(Field 2)
3.     Name(Field 3)
If i am not giving Field 1 value and trying to save i am getting proper error message.
If I am giving Field 1 value and not giving Field 2 value , then I am getting error message for Field 2 in Field 1 .
If am giving Field 1 and Field 2 value and not giving Field 3 value , I am getting the error for Field 3 in Field 1.
validation in Entity level.
i am using jdev11.1.1.6.0, adf faces and adf bc.
Edited by: 964331 on Oct 22, 2012 3:21 AM

Hi,
See followings
https://blogs.oracle.com/workingwithadf/entry/adf-bc_business_rulesvalidation_eovo
http://one-size-doesnt-fit-all.blogspot.com/2007/08/jdev-11g-new-features-adf-bc-entity_06.html

No message for validation error "format", type "date", field "date-expired"

Dear
Guys,
i am getting the following error : ((No message for validation error "format", type "date", field "date-expired"))
When trying to upload adobe connect 7 license to the adobe connect 7 configuration wizard. the problem occurs because my server was install on Arabic Saudi Arabia date format while installation, but if i change the windows date format to US then the problem still occurs, and formatting windows is not possible, could anybody help??
Regards

Thank you for replying,
No i am not on host mode, a have installed it deferent times ago successfully, but the only problem now is that during the installation windows server 2008 the default language, time and date. Was set Arabic Saudi Arabia. And even changing it does not solve the problem, as i mentioned above.

Validation Error in complaint search with changed on field.

Hi all,
I have added changed on field in complaint search screen of IC agent role, while searching for a complaint using changed on field, data as last month. We are getting an error message saying "Date M+-1 is invalid". Which I am suspecting as an validation error. Please also refer if any notes.
FYR, Error is attached. Fast responses are highly appreciated.
Thanks,
Vivek.

Hi Vivek,
Your intention is need to find the error validation?
If that could be the case,then we can check from where that error message is coming!!
1. Add a parameter in su3 BSPWD_USER_LEVEL and value is 8. If you go to web ui and place the cursor in error message, it will display the message class and message number.
2. Then go to SE91 and put the class and number, check where used list. So that u can easily find the code logic beyond that field validation.
Reply if u need more!!!
Regards,
Sugan.

Mandatory field validation error occurs when user cancels out of blank "cre

Hi - I'm building an application using Oracle 10g 9.0.5.2, with ADF/UIX/Struts.
I followed the technique described in the tutorial
http://otn.oracle.com/obe/obe9051jdev/uixtutorial/lesson_uix.htm
In that example they have a page called BrowseDeptEmp. On this page is a
create button, which is linked to a /createEmpAction before displaying the
FormEmp uix page, where the user is supposed to enter new employee data.
So I did the same thing, but I added a cancel button on the FormEmp.uix page.
If the user presses cancel on the FormEmp page, it goes through a 'rollback' DataAction (with a rollback operation dragged on it) and then back
to the main page.
here's my problem:
If the user
1. clicks the create button on the BrowseDeptEmp page
2. Sees the blank form in the FormEmp page
3. Changes his mind (does not want to add a new employee) and clicks cancel
The FormEmp page displays validation errors on the fields that are mandatory in the DB! So the user
can't cancel out of the create page unless he fills in the mandatory fields...!!
How do I cancel out of a create page 1) without entering any data on the page and 2) without getting
mandatory field validation messages?
It must be simple but i can't figure it out....
Please help :)
Thanks
Des

I don't understand how this can happen if the user has not entered any data.
Is there a commit action somewhere that is being triggered before the rollback?
is your cancel button a submit button?
one way to fix this is to convert the submit button into a
regular button and have the regular button go directly to your DataAction (the one with the rollback).
you can automatically create this button by drawing a pageLink from the page to the DataAction in the page flow diagram.

Form validation error with mandatory fields and signature field

Hello,
I have seen that many other users are facing this issue, and they partialy do solve it with some workarounds. However, none of them applies to my case.
I have a dynamic form (can be registration form for example) where user fills in bunch of fields. Some of them are mandatory.
When user signs the form, I get our favourite validation error popups that filed this and this did not validate. (I think that the signature is not valid too once I get these errors).
Workaround would be to set all fileds in the form as optional, however, the presign and postsign events work only in A9 and I need the form to be compatible with ver. 8 too.
I also need to make sure, that they are not set to optional, if the signing fails, user clicks on cancel etc...
Any ideas how to acomplish such a scenario?
Thanks
J.

solved by myself.
You have to install and configure the reader rights credentials mentioned in note 736902

Read-only radio group losing value on validation error

It took quite a while to track this down, but I think I've got it narrowed down properly. I have an APEX form for updating a record in a databse table with a radio group which is conditionally read-only. If that radio group has a value AND is read-only, when the form is submitted and hits a validation error, the value of the radio group is lost.
For example, the radio group SUBMITTED_FOR_APPROVAL is set to Y and is read-only for a given user. That user then changes something else on the form and submits it. However, the form now hits a validation error for some field. When the form reloads with the validation error displayed, all the fields are restored except the read-only radio group which is now blank. If a select list is used with the identical read-only condition, it works fine. Likewise, if a radio group is used, but the read-only condition is removed, it works fine. It is only when it is a radio group and it is read-only, that the value does not appear to be submitted to the session with all the form values whent he form is submitted.
Is this a bug or am I simply missing something?
Apex 3.1.2
Rgds/Mark M.

It's using a shared component LOV cleverly called LOV_YN which consists of a static LOV with
1 Display=Yes, Return=Y
2 Display=No, Return=N
The settings in the LOV section on the item iteself:
Named LOV: LOV_YN
Display Extra values: No Dynamic translation: Not translated
Number of columns: 2 Display null: No
Null display value is blank as is null return value
Item was setup as a radio group and was only converted over to a select list to work around this issue. Let me know what else you need and thanks again.
Rgds/Mark M.

Calendar Component and validation errors

Hi,
For the first time I am trying to use the Calendar component to insert a date field in my SQL Server db.
The problem: I can insert a date column only if its of type java.sql.Timestamp.
As Timestamp extends the date object..
I tried to bind the selectedDate field as <Timestamp> Object[refractored in my class file] and when i tried to update by DB it throwing a Validation error.
If I bind it as a Date Object directly I am getting an EvaluvationException
as date objects cannot be inserted directly
Am i missing something here or is there a proper way of implementing it.

Its a fairly direct question about object conversion problem in creator
Basically the selectedDate parameter of the JSC Calendar component
needs to be pointed to a Date Object
If we need to insert that date information to a SQL Server column the equivalent data type should be java.sql.Timestamp which extends Date.
So if we point the selectedDate parameter as a Timestamp object the creator throws an illegal argument exception.
Can some one clarify how to resolve this issue?

Validation error while trying to change a value in a request scope bean

- JBoss 4.2.3.GA
- JSF 1.2_09-b01-BETA1 (Mojarra)
- Java 5 Update 17
Hello, everybody!
I'm having the following problem in my JSF web application:
I have a request scope backing bean. The first time this bean is loaded (I check
this with the ResponseStateManager.isPostBack() method) I fill a list of SelectItem
instances that are to be displayed in the JSF page in a +<h:selectOneMenu>+ component.
The list goes, of course, to the +<h:selectOneMenu>+'s +<f:selectItems>+ facet child
component. In the constructor I also define the value that goes to the value property
of the +<h:selectOneMenu>+ component. This value is a property in the backing bean, as
is the list of SelectItem instances. Until now we have something like this:
The backing bean declaration in faces-config.xml:
<managed-bean>
    <managed-bean-name>solicitacaoGeral</managed-bean-name>
    <managed-bean-class>br.urca.solicitacoes.web.PaginaSolicitacaoGeral</managed-bean-class>
    <managed-bean-scope>request</managed-bean-scope>
</managed-bean>
The relevant parts of the JSF page:
<h:form id="form">
    <h:selectOneMenu value="#{solicitacaoGeral.setorOrigem}" id="foco">
        <f:selectItems value="#{solicitacaoGeral.setoresOrigem}" />
    </h:selectOneMenu>
</h:form>
The relevant parts of the backing bean class:
public class PaginaSolicitacaoGeral
    private final List<SelectItem> fSetoresOrigem = new ArrayList<SelectItem>();
    private Setor fSetorOrigem;
    public PaginaSolicitacaoGeral()
        if (primeiraExibicao()) // First load (!ResponseStateManager.isPostBack())
            // Fill fSetoresOrigem...
            fSetorOrigem = ...
        else // Page submitted
            // Read below...
    public List<SelectItem> getSetoresOrigem()
        return fSetoresOrigem;
    public Setor getSetorOrigem()
        return fSetorOrigem;
    public void setSetorOrigem(Setor setorOrigem)
        fSetorOrigem = setorOrigem;
    private boolean primeiraExibicao()
        String idFerramentaExibicao =
            FacesContext.getCurrentInstance().getViewRoot().getRenderKitId();
        ResponseStateManager gerenciadorEstadoResposta =
            RenderKitUtils.getResponseStateManager(
            FacesContext.getCurrentInstance(), idFerramentaExibicao);
        return !gerenciadorEstadoResposta.isPostback(
            FacesContext.getCurrentInstance());
}But when the user submits the form and the bean constructor is called again
(this time the method ResponseStateManager.isPostBack() returns true ),
in the else block in the constructor above, I need to fill fSetoresOrigem with
other values and also the fSetorOrigem field because, of course, the fSetorOrigem
field has to be a valid value that exists in the new fSetoresOrigem list.
JSF is not complaining about the change to the list items, but it is complaining
to the change to the fSetorOrigem field (the list value), even though it is a
valid value present in the list. So I'm getting this error message:
08:23:54,312 INFO [lifecycle] WARNING: FacesMessage(s) have been enqueued, but may not have been displayed.
sourceId=form:foco[severity=(ERROR 2), summary=(form:foco: Validation Error: Value is not valid), detail=(form:foco: Validation Error: Value is not valid)]I suppose that JSF is comparing the new value of the field fSetorOrigem with the value
it has in the view state. As the value is different it is raising the error. That's
what I suppose. But am I not able the change the value in the postback? I've already
checked and the value is valid. It corresponds to a value that exists in the list.
I really need a solution to this problem as I'm stuck with this and can't proceed until
I find a solution to this. What I am doing wrong and how can I solve this?
Thank you very much.
Marcos

BalusC wrote:
It is comparing the selected value against the List<SelectItem> returned by getSetoresOrigem() as it is during the apply request values phase of the form submit request.Ok. That's what I supposed JSF was doing.
BalusC wrote:
If the selected value isn't in there, then you will get this error.I can understand this, but is this right? As I said, the old value isn't really there because I changed the list values to new ones. But the new value (the value of fSetorOrigem ) corresponds to a value that exist in the new list items, so a valid value. So JSF is not considering that I also changed the list, not just the value. It is comparing the new value with the old list, not the new one. Acting like this JSF is making the page looks like a static HTML page, not a dynamic one. If I can't change the list and the value, what's the point of that? In my point of view I'm not doing anything wrong, I'm not violating any JSF rules.
Marcos

Validation error message display

I am creating a registration form with a bunch of required fields and validation messages which are associated with these fields. I have a state drop down, a province drop down and a region textfield, only one of them will be rendered depending on the selected value from a country drop down. My problem is that when the user selects a country I get validation errors for fields that haven't yet been filled out. Is there a way to ignore validation on a value_change from the country dropdown? I.E only have a validation occur when the submit button is pressed?
Thanks ,
Kevin

Kevin,
As you already created a registration fom with a bunch of required fields and validation messages which are associated with those foelds, could you please let me know how you handled all the custom messagess for all required fields. I have some knowledge using resource bundle- required key..but will handle one at a time. How we can handle all at a time and can display message on the top of the page when we click "submit" button when all field are empty .
Your early reply will be highly appreciated!
Thanks,
Hiten

Validation error for tag cfloop

Hi All,
Complete newbie to CF here. I've inherited (or bought) an online business which has its site written in CF. I haven't done this sort of stuff before but do work SQL for a living and object oriented stuff plus have done a bit of html and php so CF isn't mind blowing to me (in its simple form).
I've downloaded my site on to my computer to run a local copy that I can hack to pieces if needs be. For some reason, I have a few problems with the site running locally. The first error I'm getting is a Attribute validation error for tag cfloop.
Basically, index.cfm has this bit of code in it:
<cfinvoke component="#datasets#" method="storedProcedure" returnvariable="getFeaturedWineries_qry">
    <cfinvokeargument name="storedProcedure" value="usp_GetFeaturedWineries">
</cfinvoke>
Ok, easy enough. Anyway, there's a call down the page to:
<cfinclude template = "#REQUEST.CFMPath#includes/displayFeaturedWineries.cfm">
Within displayFeaturedWineries.cfm is the code that calls the stored proc invoked above:
<cfloop query="getFeaturedWineries_qry" startrow="1" endrow="2">
Bam, that's where the error occurs. "The value of the attribute query, which is currently getFeaturedWineries_qry, is invalid.
What??? The stored proc exists and it only returns two records (which begs me to wonder why you would have startrow and endrow but anyway, it doesn't work with or without it).
The other interesting thing is that this works on production, NO PROBLEM!!! WTF? How can it work on production but not locally.
The only thing I'm starting to think is:
a) I've missed a setting somewhere in CF or
b) I'm running Apache as compared to IIS or
c) I'm running SQL 2008 and CF 9 which will no doubt be different to the production host server.
Should B or C be causing THAT type of problem??
Thanks,
Matt

I'm not sure what code apart from the above is going to show you what you could possibly need to solve this, but here goes. The following is only snippets of the code, but they are the relavant snippets. Other stored procs work. The cfdump for getFeaturedWineries_qry shows 'usp_getFeaturedWineries'. I know its there because I've been unable to run "EXEC usp_getFeaturedWineries" after copying it straight out of the code. As previously stated, there are other stored procs which are running fine.
datasets.cfc
    <cffunction name="storedProcedure">
        <cfargument name="storedProcedure" required="Yes" type="string">
        <cfstoredproc procedure = "#ARGUMENTS.storedProcedure#"
                      datasource = "#REQUEST.DSN_NAME#"
                      username   = "#REQUEST.DSN_USER#"
                      password   = "#REQUEST.DSN_PASS#"
                      returncode = "Yes">
            <cfprocresult name="storedProcedure" resultset="1">
        </cfstoredproc>
        <cfreturn storedProcedure>
    </cffunction>
application.cfm
    
    <cfset DSN_NAME = "boutiqueWineriesTest">
    <cfset DSN_USER = "coldfusion">
    <cfset DSN_PASS = "coldfusion">
index.cfm
<cfobject component="#COMP_REF#.datasets" name="datasets">
<cfinvoke component="#datasets#" method="storedProcedure" returnvariable="getFeaturedWineries_qry">
    <cfinvokeargument name="storedProcedure" value="usp_getFeaturedWineries">
</cfinvoke>
<cfinclude template = "#REQUEST.CFMPath#includes/displayFeaturedWineries.cfm">
displayFeaturedWineries.cfm
         <cfloop query="getFeaturedWineries_qry" startrow="1" endrow="2">
Attribute validation error for tag cfloop.
The value of the attribute query, which is currently getFeaturedWineries_qry, is invalid.                                                                                  The error occurred in C:\apps\iishome\includes\displayFeaturedWineries.cfm: line 33
Called from C:\apps\iishome\index.cfm: line 399
Called from C:\apps\iishome\index.cfm: line 79
Called from C:\apps\iishome\index.cfm: line 1
31 :      <tr>
32 :           <td width="626" colspan="3" class="productCenter_bg2">
33 :          <cfloop query="getFeaturedWineries_qry" startrow="1" endrow="2">
34 :              <div class="productCennews">
35 :                  <table border="0" cellspacing="0" cellpadding="0">

Validation error corrupts component tree?

I've got a strange problem trying to use validation on input fields.
The basic setup is as follows:
I've got a page divided into two parts with separate h:form tags, the one holding a dataTable with some elements and the other showing the element details in inputFields once an item is selected in the dataTable via a commandLink. A commandButton on the detail side allows you to update the values of the selected item which is being reflected in the dataTable on reload. So far so good.
Here comes the strange part:
All the inputFields are marked required. Now once you leave a field empty and try to submit the form, you get a validation error as expected. BUT if you now select a different element from the dataTable, ONLY the field whose validation formerly failed is being updated, the other fields still show the same value as before. The backing bean method that belongs to the commandLink is being executed, and the underlying data object of the input fields is being set properly, only the values in the component tree aren't updated. This behaviour persists until you enter a valid value in the formerly invalid input field and submit. Debugging shows that as long as at least one field has had validation errors, only the getter of these backing beans properties are being invoked during render response phase, as opposed to the "normal" case where the getters of all the backing beans properties are being called.
For some reason, the render response phase seems to ignore the other components in the component tree when there was some validation error on one or more fields.
Another interesting observation:
This is the behaviour if I don't specify an action attribute in the commandLink selecting an element from the dataTable, as I want to return to the same page again. But if I define a navigation case that brings me to the same page and put that into the action attribute, the problem doesn't occur. Unfortunately this is no option for me, as I'm aiming to do all this with ajax.
I've created a simple example so you can try out yourself:
test.jsp:
<%@ taglib uri="http://java.sun.com/jsf/html" prefix="h"%>
<%@ taglib uri="http://java.sun.com/jsf/core" prefix="f"%>
<html>
<head>
<title>validator test</title>
</head>
<body>
<f:view>
     <h:form id="form1">
          <h:dataTable id="table" value="#{bean.datas}" var="data" binding="#{bean.table}" border="1">
               <h:column>
                    <h:commandLink actionListener="#{bean.selectData}" value="#{data.string1}" />
               </h:column>
               <h:column>
                    <h:outputText value="#{data.string2}" />
               </h:column>
          </h:dataTable>
          </h:form>
     <hr />
     <h:form id="form2">
          <h:inputText value="#{bean.data.string1}" id="field1" required="true" />
          <h:inputText value="#{bean.data.string2}" id="field2" required="true"/>
          <h:commandButton value="submit" />
     </h:form>
</f:view>
</body>
</html>Bean.java:
needs to be defined in faces-config.xml as bean "bean" with session scope
import java.util.ArrayList;
import java.util.List;
import javax.faces.component.html.HtmlDataTable;
import javax.faces.event.ActionEvent;
public class Bean {
     private Data data;
     private List<Data> datas;
     private HtmlDataTable table;
     public Bean() {
          datas = new ArrayList<Data>();
          datas.add(new Data("data1value1","data1value2"));
          datas.add(new Data("data2value1",""));
     public void selectData(ActionEvent event) {
          data = (Data)table.getRowData();
     public List<Data> getDatas() {
          return datas;
     public Data getData() {
          return data;
     public void setData(Data data) {
          this.data = data;
     public HtmlDataTable getTable() {
          return table;
     public void setTable(HtmlDataTable table) {
          this.table = table;
     public class Data {
          private String string1;
          private String string2;
          public Data(String string1, String string2) {
               this.string1 = string1;
               this.string2 = string2;
          public String getString1() {
               return string1;
          public void setString1(String value) {
               string1 = value;
          public String getString2() {
               return string2;
          public void setString2(String value) {
               string2 = value;
}My system setup:
WinXP Professional
JDK 1.6.0-b105
Tomcat 5.5.20 (also tried 6.0.7)
JSF RI 1.1.02_b08 (also tried 1.2_04-b10-p01, different but anyway not expected behaviour with MyFaces 1.1.5)
Thanks for any input,
Harry.

Is there noone here who can tell me if this is behavior like specified or if I miss some point?
A possible solution seems to be telling JSF programmatically to rebuild the view root. Does anyone if this is possible?

Validation error for non-null throws false error condition

I am trying to perform a DML (INSERT) with a form element (textbox) that has been disabled on the form.
The objective is to allow the user to:
1) disable a form element using javascript when a radio element is selected - works OK using an onclick event
2) user clicks a button to ENTER (perform a INSERT DML) - here the validation throws an error but I have enabled the previously disabled form element and I have used $x_Value() to input a value into the form element by onsubmit event on button.
If I remove the validation error trap the DML saves the appropriate value.
I can create two buttons and it works:
1 button to enable fields that were previously disabled
2 button to perform DML. (works if after button 1 I set focus on any form field with my mouse.)
Any help would be appreciated.
marshall

Knight,
Thanks for your interest in helping.
I am trying not to create a situation w/bugs and such. I think I can devise a work around but I would like a more "correct" solution. ;-)
To explain what I am doing I have a form that a person can use to enter a complaint. The person can give their last - middle - first name but they can also decide to be anonymous. If anonymous they click checkbox. Onclick of checkbox I fire javascript to disable name fields and place "Anonymous" in the last_name disabled field. The user can enter other data and when the user clicks ENTER I want to insert into the DB but the validation error trap of APEX sees a disabled field as a null. I want to place "Anonymous" in the last name field and then save the record with other data besides name.
To add to it - I can create two buttons 1-button enables and 2-button inserts and the same code works if I touch( give focus) to a field in between enabling and inserting into the DB
Does that help explain better.
Thanks again - hope you or someone can help - best regards.

Width of Hightlighted Field on Validation Error

Similar Messages

Maybe you are looking for