Alpha Software Mobile Development Tools:   Alpha Anywhere    |   Alpha TransForm subscribe to our YouTube Channel  Follow Us on LinkedIn  Follow Us on Twitter  Follow Us on Facebook

Announcement

Collapse

The Alpha Software Forum Participation Guidelines

The Alpha Software Forum is a free forum created for Alpha Software Developer Community to ask for help, exchange ideas, and share solutions. Alpha Software strives to create an environment where all members of the community can feel safe to participate. In order to ensure the Alpha Software Forum is a place where all feel welcome, forum participants are expected to behave as follows:
  • Be professional in your conduct
  • Be kind to others
  • Be constructive when giving feedback
  • Be open to new ideas and suggestions
  • Stay on topic


Be sure all comments and threads you post are respectful. Posts that contain any of the following content will be considered a violation of your agreement as a member of the Alpha Software Forum Community and will be moderated:
  • Spam.
  • Vulgar language.
  • Quotes from private conversations without permission, including pricing and other sales related discussions.
  • Personal attacks, insults, or subtle put-downs.
  • Harassment, bullying, threatening, mocking, shaming, or deriding anyone.
  • Sexist, racist, homophobic, transphobic, ableist, or otherwise discriminatory jokes and language.
  • Sexually explicit or violent material, links, or language.
  • Pirated, hacked, or copyright-infringing material.
  • Encouraging of others to engage in the above behaviors.


If a thread or post is found to contain any of the content outlined above, a moderator may choose to take one of the following actions:
  • Remove the Post or Thread - the content is removed from the forum.
  • Place the User in Moderation - all posts and new threads must be approved by a moderator before they are posted.
  • Temporarily Ban the User - user is banned from forum for a period of time.
  • Permanently Ban the User - user is permanently banned from the forum.


Moderators may also rename posts and threads if they are too generic or do not property reflect the content.

Moderators may move threads if they have been posted in the incorrect forum.

Threads/Posts questioning specific moderator decisions or actions (such as "why was a user banned?") are not allowed and will be removed.

The owners of Alpha Software Corporation (Forum Owner) reserve the right to remove, edit, move, or close any thread for any reason; or ban any forum member without notice, reason, or explanation.

Community members are encouraged to click the "Report Post" icon in the lower left of a given post if they feel the post is in violation of the rules. This will alert the Moderators to take a look.

Alpha Software Corporation may amend the guidelines from time to time and may also vary the procedures it sets out where appropriate in a particular case. Your agreement to comply with the guidelines will be deemed agreement to any changes to it.



Bonus TIPS for Successful Posting

Try a Search First
It is highly recommended that a Search be done on your topic before posting, as many questions have been answered in prior posts. As with any search engine, the shorter the search term, the more "hits" will be returned, but the more specific the search term is, the greater the relevance of those "hits". Searching for "table" might well return every message on the board while "tablesum" would greatly restrict the number of messages returned.

When you do post
First, make sure you are posting your question in the correct forum. For example, if you post an issue regarding Desktop applications on the Mobile & Browser Applications board , not only will your question not be seen by the appropriate audience, it may also be removed or relocated.

The more detail you provide about your problem or question, the more likely someone is to understand your request and be able to help. A sample database with a minimum of records (and its support files, zipped together) will make it much easier to diagnose issues with your application. Screen shots of error messages are especially helpful.

When explaining how to reproduce your problem, please be as detailed as possible. Describe every step, click-by-click and keypress-by-keypress. Otherwise when others try to duplicate your problem, they may do something slightly different and end up with different results.

A note about attachments
You may only attach one file to each message. Attachment file size is limited to 2MB. If you need to include several files, you may do so by zipping them into a single archive.

If you forgot to attach your files to your post, please do NOT create a new thread. Instead, reply to your original message and attach the file there.

When attaching screen shots, it is best to attach an image file (.BMP, .JPG, .GIF, .PNG, etc.) or a zip file of several images, as opposed to a Word document containing the screen shots. Because Word documents are prone to viruses, many message board users will not open your Word file, therefore limiting their ability to help you.

Similarly, if you are uploading a zipped archive, you should simply create a .ZIP file and not a self-extracting .EXE as many users will not run your EXE file.
See more
See less

Simply want to apply show/hide or disable button if any error exists within UX component

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Simply want to apply show/hide or disable button if any error exists within UX component

    Hello all,

    I'm simply wanting to not allow a user to press a button I have in a UX component if any data validation errors exist on the UX component.

    I know that using the built in SUBMIT button has this functionality, however for many reasons I need to keep my UX unbound and are therefore not using the SUBMIT button on my UX.

    I have several fields that have data validation that are working beautifully, and gives the proper error messages, however once all the fields are populated my button appears due to my show/hide criteria, basically not null, however it allows the button to be clicked and therefore proceeds to allow the javascript to fire from the button. I simply want the button to be disabled, or continue to be hidden until all data validation errors are resolved.

    I'm sure I', probably missing something obvious.

    Please advise.

    Thank you, Casey

    #2
    Re: Simply want to apply show/hide or disable button if any error exists within UX component

    You'd have to advise how your data validation is set up. XBasic, Javascript, your own function?

    Comment


      #3
      Re: Simply want to apply show/hide or disable button if any error exists within UX component

      Hello David,

      Sorry, just basic field validation. One of the fields is set to "must contain value" and it turns read when the user blurs out of the field which is correct, however I would like to configure the button to not be enabled if this field is red...

      -Casey

      Comment


        #4
        Re: Simply want to apply show/hide or disable button if any error exists within UX component

        The problem with field validation is that the user isn't usually forced into a field. If they skip over a field... if that control never got focus, then validation isn't fired. If you hide or disable the Submit button they won't know what's going on.

        What about letting them click the Submit button... but stopping the submit code if there's an issue? To solve the problem of a control that did not get focus, we can fire control validations in the submit code.

        For each control you want validated, perform a .clientSideValidateField('controlName',1,1); (it's always 1,1 for non-repeating section controls).

        Now... validationResult will be set if there's a problem, but we don't want to have to check every one of them. So... instead... just check the UX's error handler. If the error handler has array length greater than 0 we know there's a validation error... and so just return.

        Code:
        debugger;
        
        var validationResult={dialog.object}.clientSideValidateField('text1',1,1);
        
        if({dialog.Object}._eh._e.length > 0){
        	//we have an error so return
        	return;
        }
        
        //all ok... save stuff

        Comment


          #5
          Re: Simply want to apply show/hide or disable button if any error exists within UX component

          David K to the rescue again! The code referenced above worked like a charm. Thank you so much, again, for the great explanation, both easy to understand and easy to implement my code given your comments...

          Much appreciated!

          -Casey

          Comment


            #6
            Re: Simply want to apply show/hide or disable button if any error exists within UX component

            David, just a quick clarification, can you possibly show how should the syntax read for multiple fields? This code is working perfectly for one field, however I applied the following code to my submit button and it only holds up processing for the first line of validation -

            debugger;

            var validationResult={dialog.object}.clientSideValidateField('hdInvNum',1,1);
            var validationResult={dialog.object}.clientSideValidateField('hdInvDate',1,1);
            var validationResult={dialog.object}.clientSideValidateField('hdVenName',1,1);




            if({dialog.Object}._eh._e.length > 0){
            //we have an error so return
            return;
            }

            {dialog.object}.runAction('ProcessExpenseInvoice');

            Comment


              #7
              Re: Simply want to apply show/hide or disable button if any error exists within UX component

              In the attached UX (current Alpha build, format:formatted JSON), both my textbox controls are set to Require Value and both are caught by validation... same as you've written.
              Attached Files

              Comment

              Working...
              X