Validation and mandatory fields

Hello

I use Jdev 11.1.1.4.0.

I have ClientEO which has attributes name, address, city, State and Zip and obligatory. On client.jsff, I have them displayed in a table. This table is editable table where the user can add new customer or modify existing customer information. My problem is with validation happening in the middle of entering the information.

I click on the 'New' button which performs the operation of "CreateInsert". This creates a low vacuum in the table with the fields of text for all, LOV select only one option for the status field. The thing is, if I click on the State list, I get a validation error popup saying all fields are required. I KNOW, but I did not even have the chance to enter them again!.

If I want the field validation required to treat only the submit, what should I do? I've tried to set skipValidation to true on pagedef, but did not work.

Any suggestions will be greatly appreciated!

Thank you

Bones Jones

See if this helps:
http://andrejusb.blogspot.com/2012/09/what-to-do-when-ADF-editable-table.html

Tags: Java

Similar Questions

  • Tabbed Panel (validation and on the issue of validation)

    Hi experts,

    I HAV a form in which it is two sides separated by a group separator. In the first part I drag and droped VO control in the form of panel data (attributes). In the second second fecet, I used a Panel tab with detail element see the 2... few remaining VO attributes are placed first tab and rest all are placed on the 2nd tab.

    My question is, after you enter the values in the form of Panel and first tab, then when I try to move to the 2nd tab it triggers validation filed (mandatory fields shown in the form of Panel)... How can I fix this problem?

    PMS

    Published by: pms on January 18, 2012 11:25

    in the property inspector set the immediate attribute for the show detail true items

  • Field of own ViewObject and its validation mutual transient fields

    Hello

    I have a question about the validation between the own field of ViewObject and transitional fields.

    My VO has an attribute named AmountReceived & it is inherited from the EO.

    My VO has also 2 transitional named Expense1 and Fees2attributes. These 2 transient fields are directly added to the level of the VO.

    Now in the Page UI, I have a table for my VO.

    For each row in the table, all 3 fields above appears.

    I have to validate this Expense1 + Fees2 cannot be greater than AmountReceived field.

    I know I can do this at the bean support using valueChangeListener but the problem with this implementation is the user can COMMIT the transaction without correction of the data.

    Where and how should I apply my validation logic SO that the user must need to correct the data before embarking, I mean when the user loses the focus of the current row in my table - it should trigger my logic and the user must need to correct the data?

    Help please?

    Thanks - Hitesh

    As you have two fields for each row place in the OT instead of the original version. Then, you can implement a business for your validation rule.

    Timo

  • MANDATORY FIELD VALIDATION PRIOR TO SUBMITTING

    Hi Experts,

    I have an obligation to check if all the required fields in a form has been filled before submitting the form. The form has 1 page that is cast and spans of 8 pages. There are about 40-50 fields. I tried to put the following script in the event click of the SUBMIT button.

    var lv_txtfld;
    for (var nPageCount = 0; nPageCount < xfa.host.numPages; nPageCount ++) {}
    var oFields = xfa.layout.pageContent (nPageCount, "field");
    var nNodesLength = oFields.length;
    for (var nNodeCount = 0; nNodeCount < nNodesLength; nNodeCount ++) {}
    If (. ui.oneOfChild.className oFields.item (nNodeCount) == 'textEdit') {}
    lv_txtfld. = ui.oneOfChild.rawValue oFields.item (nNodeCount);
    If ((! lv_txtfld.optional) & & (lv_txtfld == null) |) (lv_txtfld == "")) {
    XFA. Host.message (oFields.item (nNodeCount) ".ui + ' '+' ' is mandatory field - please enter the same");

    continue;
    }
    }
    }
    }

    The script above doesn't work - I don't want to make mandatory field checking each field by field, because it would be too tedious for 40-50 fields. Please let me know of any alternative.

    Hello rohitacmilan!

    Just to make sure I'm covering all bases, note that the existence of ANY empty required field (defined as user entered - required) will prevent the form of presentation by default.

    Which, according to me, you want to come but you want to programmatically control all fields before submitting so that you can make a custom action.  If this is the case, you indeed a script similar to the one you posted.  After reviewing your script, I found a few issues that I will discuss this subject after the display of the solution:

    var lv_txtfld;

    for (var nPageCount = 0; nPageCount < xfa.host.numPages; nPageCount++)

    {

         var oFields = xfa.layout.pageContent(nPageCount, "field");

         var nNodesLength = oFields.length;

         for (var nNodeCount = 0; nNodeCount < nNodesLength; nNodeCount++)

          {  

               if (oFields.item(nNodeCount).ui.oneOfChild.className == "textEdit")   

               {  

                    lv_txtfld = oFields.item(nNodeCount);  

                   if ( (lv_txtfld.mandatory == "error") &&

                        (lv_txtfld.rawValue == null || lv_txtfld.rawValue == ""))   

                   {    

                         xfa.host.messageBox(lv_txtfld.name + " is a required field - please enter the same");  

                   }             

               }

         }

    }

    The questions were the following:

    (1) the line "lv_txtfld =. ui.oneOfChild.rawValue oFields.item (nNodeCount)" was bombing.  I think it was the intention here is to get a reference to the specific node we are in our loop for use in the following if statement.  Note, however, that we already have an array of references to all applicable nodes in the table "oFields.

    (2) the line that starts with "if ((!)). lv_txtfld.optional)... "was bombing for several reasons.  First of all, not a property of a shape node is "optional".  I think the intention here was to check if the current node was necessary or not.  In this case, you would normally check the "required" property  A required field will have a 'compulsory' property equivalent to the literal string "error".  Second, the segment of the 'if' clause after the "&" seems to be written in order to check the contents of the current node to a value.  If this is the case, we must check the "rawValue" property  In addition to this point, we would like the second clause of our ' | ' statement not having spaces in the string literal as "" is not to "". ""

    (3) it appears that the intent of the line within the deeper ' if' statement must display a message to the user to let them know that a field empty, required was found.  If this is the case, then we can just use the "name" property of the current node instead of '.ui oFields.item (nNodeCount).  In addition, the method to display a message box is «xfa.host.messageBox (...)»

    4) well not really a 'mistake' in itself, I thought that I would point out that you don't have no need to use the key word 'continue' after displaying the message box to the user on a required field blank.  You are in a loop at this point and will continue to function normally until finally his test clause fails.

    I hope I've been helpful!  Please let me know if you have any questions.

    Take care!

    Josh Boyle

    [email protected]

    Cardinal Solutions Group

  • I create a form based on two tables that have sequences also. When I create insert only row is inserted in the fields in table first and second fields of the table are empty. Why?

    Mr President.

    I create a form based on two tables that have sequences also. When I create insert only row is inserted in the fields in table first and second fields of the table are empty. Why?

    formdoubletables.png

    the page source is

    <?xml version='1.0' encoding='UTF-8'?>
    <ui:composition xmlns:ui="http://java.sun.com/jsf/facelets" xmlns:af="http://xmlns.oracle.com/adf/faces/rich"
                    xmlns:f="http://java.sun.com/jsf/core">
      <af:panelFormLayout id="pfl1">
        <af:group id="Group">
          <af:inputText value="#{bindings.VoucherId.inputValue}" label="#{bindings.VoucherId.hints.label}"
                        required="#{bindings.VoucherId.hints.mandatory}" columns="#{bindings.VoucherId.hints.displayWidth}"
                        maximumLength="#{bindings.VoucherId.hints.precision}"
                        shortDesc="#{bindings.VoucherId.hints.tooltip}" id="it1">
            <f:validator binding="#{bindings.VoucherId.validator}"/>
            <af:convertNumber groupingUsed="false" pattern="#{bindings.VoucherId.format}"/>
          </af:inputText>
          <af:inputDate value="#{bindings.VoucherDate.inputValue}" label="#{bindings.VoucherDate.hints.label}"
                        required="#{bindings.VoucherDate.hints.mandatory}"
                        columns="#{bindings.VoucherDate.hints.displayWidth}"
                        shortDesc="#{bindings.VoucherDate.hints.tooltip}" id="id1">
            <f:validator binding="#{bindings.VoucherDate.validator}"/>
            <af:convertDateTime pattern="#{bindings.VoucherDate.format}"/>
          </af:inputDate>
          <af:inputText value="#{bindings.Credit.inputValue}" label="#{bindings.Credit.hints.label}"
                        required="#{bindings.Credit.hints.mandatory}" columns="#{bindings.Credit.hints.displayWidth}"
                        maximumLength="#{bindings.Credit.hints.precision}" shortDesc="#{bindings.Credit.hints.tooltip}"
                        id="it2">
            <f:validator binding="#{bindings.Credit.validator}"/>
          </af:inputText>
        </af:group>
        <af:group id="g1">
          <af:inputText value="#{bindings.Lineitem.inputValue}" label="#{bindings.Lineitem.hints.label}"
                        required="#{bindings.Lineitem.hints.mandatory}" columns="#{bindings.Lineitem.hints.displayWidth}"
                        maximumLength="#{bindings.Lineitem.hints.precision}" shortDesc="#{bindings.Lineitem.hints.tooltip}"
                        id="it3">
            <f:validator binding="#{bindings.Lineitem.validator}"/>
            <af:convertNumber groupingUsed="false" pattern="#{bindings.Lineitem.format}"/>
          </af:inputText>
          <af:inputText value="#{bindings.VoucherId1.inputValue}" label="#{bindings.VoucherId1.hints.label}"
                        required="#{bindings.VoucherId1.hints.mandatory}"
                        columns="#{bindings.VoucherId1.hints.displayWidth}"
                        maximumLength="#{bindings.VoucherId1.hints.precision}"
                        shortDesc="#{bindings.VoucherId1.hints.tooltip}" id="it4">
            <f:validator binding="#{bindings.VoucherId1.validator}"/>
            <af:convertNumber groupingUsed="false" pattern="#{bindings.VoucherId1.format}"/>
          </af:inputText>
          <af:inputText value="#{bindings.Debit.inputValue}" label="#{bindings.Debit.hints.label}"
                        required="#{bindings.Debit.hints.mandatory}" columns="#{bindings.Debit.hints.displayWidth}"
                        maximumLength="#{bindings.Debit.hints.precision}" shortDesc="#{bindings.Debit.hints.tooltip}"
                        id="it5">
            <f:validator binding="#{bindings.Debit.validator}"/>
          </af:inputText>
          <af:inputText value="#{bindings.Credit1.inputValue}" label="#{bindings.Credit1.hints.label}"
                        required="#{bindings.Credit1.hints.mandatory}" columns="#{bindings.Credit1.hints.displayWidth}"
                        maximumLength="#{bindings.Credit1.hints.precision}" shortDesc="#{bindings.Credit1.hints.tooltip}"
                        id="it6">
            <f:validator binding="#{bindings.Credit1.validator}"/>
          </af:inputText>
          <af:inputText value="#{bindings.Particulars.inputValue}" label="#{bindings.Particulars.hints.label}"
                        required="#{bindings.Particulars.hints.mandatory}"
                        columns="#{bindings.Particulars.hints.displayWidth}"
                        maximumLength="#{bindings.Particulars.hints.precision}"
                        shortDesc="#{bindings.Particulars.hints.tooltip}" id="it7">
            <f:validator binding="#{bindings.Particulars.validator}"/>
          </af:inputText>
          <af:inputText value="#{bindings.Amount.inputValue}" label="#{bindings.Amount.hints.label}"
                        required="#{bindings.Amount.hints.mandatory}" columns="#{bindings.Amount.hints.displayWidth}"
                        maximumLength="#{bindings.Amount.hints.precision}" shortDesc="#{bindings.Amount.hints.tooltip}"
                        id="it8">
            <f:validator binding="#{bindings.Amount.validator}"/>
            <af:convertNumber groupingUsed="false" pattern="#{bindings.Amount.format}"/>
          </af:inputText>
        </af:group>
        <f:facet name="footer">
          <af:button text="Submit" id="b1"/>
          <af:button actionListener="#{bindings.CreateInsert.execute}" text="CreateInsert"
                     disabled="#{!bindings.CreateInsert.enabled}" id="b2"/>     
          <af:button actionListener="#{bindings.Commit.execute}" text="Commit" disabled="#{!bindings.Commit.enabled}"
                     id="b3"/>
          <af:button actionListener="#{bindings.Rollback.execute}" text="Rollback" disabled="#{!bindings.Rollback.enabled}"
                     immediate="true" id="b4">
            <af:resetActionListener/>
          </af:button>
        </f:facet>
      </af:panelFormLayout>
    </ui:composition>
    
    
    
    

    Concerning

    Go to your VO Wizard, select the tab of the entity and to check if both the EO is editable or not.

    See you soon

    AJ

  • ADF mandatory fields: validate/report of all client-side regardless of the type of

    JDeveloper 10.1.3.4
    10.1.3.42.70 ADF business components

    Is there a way to validate and report on all of the mandatory fields empty/null in the validation on the client (in the default dialog box "Message from Web page") side?

    Some existing fields (some af:inputText, other af:selectOneChoice) is no longer an option, so let's validation of required fields on the page (instead of a mixture of validation on the client and database). Jspx form where the record is created, these have been marked as:

    showRequired = "true" required = "true".

    (These attributes are also marked as mandatory in the object of the entity).

    When creating a new record and play "Commit", a dialog box titled "Message from Web page" returns with "Form validation failures" and required still empty inputText field names. All fields required but empty selectOneChoice do not appear in this initial validation dialog box. When all required them inputText areas are registered and running "Commit", all the fields empty selectOneChoice are presented with Houston-27014 message returned to the jspx error.

    QA wants that all of the required fields are empty/null should be written both in the "Message from Web page" dialog box

    Thank you

    David K

    In of each link Explorer selectOneChoice of we should also change the "selection" Item _N_o: of - include white point - to - selection Required.

    Published by: dak on May 30, 2013 10:30

  • Seem to have lost my mandatory field option in Business Catalyst

    Hello

    I set up a form of catalyst business and formatted, but in the process have lost the functionality of mandatory field

    http://aom002.BusinessCatalyst.com/registration_copy.htm

    The form should be not able to be present if the terms, conditions and other REQUIRED fields are not completed.

    For the moment, required fields is not necessary be filled and the form can be sent.

    Any thoughts would be great.

    Ciao

    Cathy

    Your form validation works on my end. It seems you've already solved this problem. If it does not always work on your end, please join our support team via of Administration Console/partner portal > & support.

  • Validation of input field in the OPA for the optional input fields

    Hi all

    OPM, I have a text input field. To do this, I wrote an entry of Validation Using Regular Expressions to allow the alphabets and numbers.

    Also, I did the same field as "optional-always.

    Then in debugging, it is always check for the Input Validation and displaying the error message when I do not enter any value.

    How can I request an entry for an optional input field Validation.

    Thank you

    Siri

    I'm not an expert on regular expressions, but my guess here is that your regular expression must change. If an empty string is an acceptable entry, then you should allow for her in the regular expression. I don't know the regex code for this on the top of my head, but I hope that you will find quite easily with a few searches on Google.

  • Validation error: the field types incompatibilities.

    Hi all

    I coded an integration to export data from the API in bulk Eloqua REST and it worked well before.

    But recently, when I try again to launch an export, I could only successfully to POST an export. I met a WebException when you try to VIEW a synchronization for export.

    The exception message is: "the remote server returned an error: bad request (400)"

    And the JSON response is:

    {

    {"failures": [{"field": "'status' ',' forced':" "Validation error: incompatibilities of field types."}]}

    I haven't changed anything recently, but it wouldn't work any longer.

    Is there something different for the API in bulk?

    Any suggestions for this exception?

    Thank you

    Biao

    This was announced in the recent release (Archives) what's new in Oracle Eloqua?.

    Validation of strict type for JSON serializer is now enabled (see API in bulk in the notes above), so it provides you with an explanation of what is wrong, by design.

    Make sure that your JSON is valid and everything should work fine.

  • problem with validation in the field with the radio button type in create profile jsp page

    Hello

    Kindly help me with the validation of a field with the type option button in the createProfile jsp page. Its actually not to validate the sex with radio button field.

    The code is as follows...

    < % @ page language = "java" contentType = text/html"; charset = ISO-8859-1"

    pageEncoding = "ISO-8859-1" % >

    <! – this taglib used to access dsp tags - >

    < %@taglib uri = "" / dspTaglib "prefix ="dsp"% >"

    < dsp:page >

    < dsp:importbean bean = "/ atg/userprofiling/ProfileFormHandler" / >

    < dsp:importbean bean = "/ atg/dynamo/drop/ErrorMessageForEach" / >

      <! DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional / / IN" "http://www.w3.org/TR/html4/loose.dtd" > ""

    < html >

    < head >

    < meta http-equiv = "Content-Type" content = text/html"; charset = utf-8 "/ >"

    < title > < /title > user registration Page

    < / head >

    < body >

    < dsp:form id = "registerForm" method = "post" action = "registration.jsp" >

    < div >

    < div > if please fill in all fields below and click Save

    button. < / div >

    < br / >

    < table >

    < tbody >

    < b >

    < td width = "150" > name < table >

    < td > < dsp:input bean = "ProfileFormHandler.value.firstName"

    MaxLength = "30" size = "25" type = "text" required = "true" / > < table >

    < /tr >

    < b >

    Last name < td > < table >

    < td > < dsp:input bean = "ProfileFormHandler.value.lastName"

    MaxLength = "30" size = "25" type = "text" required = "true" / > < table >

    < /tr >

    < b >

    < td > username < table >

    < td > < dsp:input bean = "ProfileFormHandler.value.login"

    MaxLength = "30" size = "25" type = "text" required = "true" / > < table >

    < /tr >

    < b >

    password < td > < table >

    < td > < dsp:input bean = "ProfileFormHandler.value.password"

    MaxLength = "30" size = "25" type = "password" required = "true" / > < table >

    < /tr >

    < b >

    < td > confirm password < table >

    < td > < dsp:input bean = "ProfileFormHandler.value.password"

    MaxLength = "30" size = "25" type = "password" required = "true" / > < table >

    < /tr >

    < b >

    Identification of Email < td > < table >

    < td > < dsp:input bean = "ProfileFormHandler.value.email"

    MaxLength = "30" size = "25" type = "text" required = "true" / > < table >

    < /tr >

    < b >

    Sex < td > < table >

    < td > < dsp:input bean = "ProfileFormHandler.value.gender"

    Type = "radio" required = "true" > male < / dsp:input > < dsp:input

    Bean = "ProfileFormHandler.Value.Gender" type = "radio" "

    required = "true" > female < / dsp:input > < table >

    < /tr >

    < b >

    < td colspan = "2" > < dsp:input bean = "ProfileFormHandler.create"

    Type = "submit" value = "Save" / > < dsp:input

    Bean = "ProfileFormHandler.createSuccessURL" type = "hidden"

    value = "index.jsp" / > < table > "

    < /tr >

    < b >

    < td colspan = "2" >

    < ul >

    < dsp:droplet name = "ErrorMessageForEach" >

    < dsp:param bean = "ProfileFormHandler.formExceptions"

    name = 'exceptions' / >

    < name dsp:oparam = "output" >

    < li > < dsp:valueof param = "message" / > < /li >

    < / dsp:oparam >

    < / dsp:droplet >

    < /ul >

    < table >

    < /tr >

    < / tbody >

    < /table >

    < / div >

    < / dsp:form >

    < / dsp:page >

    < / body >

    < / html >

    Use code next, may be you do not value attribute set and causing a problem (data inconsistency problem) or case mismatch while storing data in the repository.

    <%Boolean checked = true;%>

    Sex:

    Male

    Female

    I do not know what will radio back button if the value is specified: a boolean value or the value aim to display (in your male cases),.

    If the problem is fixed, undo the change and please let me know what value he sent in your case.

    Please

    Thank you

    Nitin.

  • With immediate SOC = true is always run validation of other fields

    11.1.2.2 JDev

    I have a popup and the dialog box that contains a set of SOC and InputText fields. I put the attribute 'required' to all the fields of the form to "false" so I can run validation in the dialogListener method.

    On the one hand the components of the SOC, I need to show or hide a panelGroupLayout according to the value selected in the SOC.  For this SOC, I 'autosubmit = true' to trigger the valueChangeListener method in bean and ' immediate = true' to bypass validation for the other fields in the form.

    The problem is that, even if none of the fields are marked as 'required' in the form and even if I ' immediate = true' to the SOC, when I change the value of the SOC, I get a facesMessage saying a couple of fields are required in the t.  So it seems to be bypassing the validation on the client and go directly to the validation of the model side during the valueChangeEvent of the SOC, and I don't want ANY type of validation to perform during the action autosubmit to one of the fields on the form.  I use an addPartialTarget in the valueChangeEvent to refresh the panelGroupLayout after you have determined whether or not it should be displayed.

    Here is the Declaration of .jsff to the SOC and panelGroupLayout:

    <af:selectOneChoice value="#{bindings.ItemTypId.inputValue}"
                                                        label="#{bindings.ItemTypId.label}"
                                                        shortDesc="#{bindings.ItemTypId.hints.tooltip}" id="soc4"
                                                        autoSubmit="true"
                                                        valueChangeListener="#{pageFlowScope.MyBean.selectedItemTypeValueChangeListener}"
                                                        immediate="true">
                                        <f:selectItems value="#{bindings.ItemTypId.items}" id="si4"/>
    </af:selectOneChoice>
                                    <af:panelGroupLayout id="pgl1"
                                                         rendered="#{pageFlowScope.MyBean.passingScoreReq}"
                                                         binding="#{pageFlowScope.MyBean.pglPassingScore}"
                                                         clientComponent="true">
                                        <af:inputText value="#{bindings.PassingScorePct.inputValue}"
                                                      label="Passing Score"
                                                      columns="#{bindings.PassingScorePct.hints.displayWidth}"
                                                      maximumLength="#{bindings.PassingScorePct.hints.precision}"
                                                      shortDesc="#{bindings.PassingScorePct.hints.tooltip}" id="it1">                     
                                            <f:validator binding="#{bindings.PassingScorePct.validator}"/>
                                            <af:convertNumber groupingUsed="false"
                                                              pattern="#{bindings.PassingScorePct.format}"/>
                                        </af:inputText>
                                    </af:panelGroupLayout>
    

    Here is the code of the bean that performs the valueChangeEvent for the SOC in question:

    /**
         * Handle value change event for Item Type SOC on Edit Item popup
         * @param valueChangeEvent
         */
        public void selectedItemTypeValueChangeListener(ValueChangeEvent valueChangeEvent) {
            Long newItemTypId = (Long) valueChangeEvent.getNewValue();
            passingScoreReq = false;
            
            RichSelectOneChoice soc = (RichSelectOneChoice) valueChangeEvent.getComponent();
            List<UIComponent> socItems = soc.getChildren();
            UISelectItems uiSelectItems = (UISelectItems) socItems.get(0);
            List<SelectItem> listSelectItems = (List<SelectItem>) uiSelectItems.getValue();
            for(SelectItem item : listSelectItems){
                if(item.getValue().equals(newItemTypId) && item.getLabel().equals("Test")){
                    //The selected item is a 'Test' type, so we need set set passingScoreReq to true and refresh the pglPassingScore PanelGroupLayout
                    passingScoreReq = true;
                    break;
                }
            } 
            
            AdfFacesContext.getCurrentInstance().addPartialTarget(pglPassingScore);
        }
    

    You can try setting skipValidation = true in your pagedef.

    Thank you

  • How to restrict user access to must enter a value in the mandatory fields

    Greetings!

    I had a personal information form. I want to restrict the user to enter values in all areas of mandatory for example fields (username, date of birth, etc.)
    How to limit the search user must enter a value in the mandatory fields

    Create dynamic actions for each of the fields, or you can create javascript.
    for example create dynamic action 1 with event as tune-up losing select the item and the condition as NULL and action as alert and type the message you want to display in the text section.

    Thank you
    Mehabub

  • When we change the non-mandatory field in the form, it is not updated

    Hello... I have a question here...

    If I required fields in a custom form, and when I ask the form and change the value in the non-mandatory field and click on save, then it does not save. It is said ' no changes to save "." But it is not the same for the non-compulsory fields.

    Can you please suggest me?

    -vrdida

    If you have an element with an assigned LoV it much difference if you change the value of points (assuming that you have either the property 'Validate list', the value yes or you have a WHEN-VALIDATE-POINT-trigger who performs the search ID fk of the given text) or if you visit the 'empty' field, or NULL. In this case, you must create a WHEN-VALIDATE-trigger POINT on the element, which "cleans" the Fk - id as

    IF :BLOCK.LOKUP_ITEM IS NULL THEN
      :BLOCK.FK_ID:=NULL;
    eNd IF;
    
  • How to make a request for Validation on the field of comments in BPM Worklist task details Page

    Hello
    I am newbie to SOA 11 g.

    I use SOA 11 g and Jdev 11.1.1.3 for development. I created a human with two results (APPROVE, REJECT) and task able to display the page the task details in the BPM list. I have the comments of default section that comes by 'Auto generation of ADF Taskflow' in the Task Details page. This comments section will display the comments of several users who have access to the task. I want to add validation for the field of comments as below-

    (1) to DISMISS the action, we must check whether or not the APPROVER had provided the reason for REJECTION in the comments field. If this isn't the case, we need to display a popup asking him to provide observations of REJECTION.
    (2) on the action to APPROVE, no need to check for comments, so no validation is necessary.

    Can someone give me some ideas how it is possible.

    Thank you
    Udaya Neeliahgari

    Hello
    Try the following...
    In the composite open y'r process bpel... and then to expand the human task... you will notice a task entitled just before the initiateTask run the following two copy operation in the task of AssignTaskAttributes within the scope of the human task.

    IMP Note: The variable is the variable initiateTaskInput of the human task field. Don't assign not on on the global variable

    1 assign a string value "REJECT" in the expression (assuming that you do so that the result of REJECTION) and assign it to the variable

    /TaskService:initiateTask / task: task / mission: systemAttributes / task: preActionUserSteps / task: preActionUserStep / task: results

    2 assign the string value "PROVIDE_COMMENTS" in the expression and assign it to the variable

    /TaskService:initiateTask / task: task / mission: systemAttributes / task: preActionUserSteps / task: preActionUserStep / task: userStep

    view the .bpel file source y'r and make sure that you see something like the following:




    Query = "" / taskservice:initiateTask / task: task / task: systemAttributes / task: preActionUserSteps / task: preActionUserStep / task: result "/ >"




    Query = "" / taskservice:initiateTask / task: task / task: systemAttributes / task: preActionUserSteps / task: preActionUserStep / task: userStep "/ >"

    Just deploy the app... and when you try to dismiss... it should appear the message.

    concerning
    Raja

  • Validation of DateTime field (without custom management functions)

    Hello

    I need to know how I can validate if a date is correct or not and fail to do something.

    I have a DateTime Field field, with a pattern ' DD / MM / YYYY ', the value appears correctly using the selected template, the problem is validation.


    Now I just that if the date is wrong, teaches an alert to the user, and the focus returns to the DateTime control until you enter a valid value.

    I need something like:

    -Form1.SUBVENCION_O_AYUDA.dateTimeField1: Validate - (JavaScript, client).

    If (this.rawValue! = null & &! test (this.rawValue, ' DD/MM/YYYY')) {}

    xfa.host.setFocus ("this");
    }

    How will I know if the validation is successful or not (without having to implement long-standing management functions)?

    By default, if I put 'validation model messaga' field, a warning message is displayed, but here the emphasis is more and the user can continue to fill the rest of the form, whereas the datetime field is filled with an incorrect value.

    I want to warn the user to continue to fill out the form, if the value in the dateTime field is not valid.

    Any idea?

    Thank you!

    Hello

    If your date may not be formatted correctly against your view model then the formattedValue is equal to the rawValue.

    Thus, in the event output put;

    If (this.rawValue is this.formattedValue)

    {

    App.Alert ("enter a date in the dd/mm/yyyy" format "");

    xfa.host.setFocus (this.somExpression);

    }

    Bruce

Maybe you are looking for