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

Error Message handling with Mobile Panels

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

    Error Message handling with Mobile Panels

    All of the videos and examples I have seen using mobile panels are for display only. I am building a mobile screen for data-entry that has 8 different panels, and I'm having some interesting issues. I'm looking to share what I have encountered and find out if anyone else has had these issues.

    My current issue is with error messages. Some of the fields on the form are required. If you have the messages showing inline, you can't see them when you finishing filling out the form, because they are on a hidden panel. This particular form as 8 panels, and the submit button is only on the last panel. However, when I switch it to show the errors in one location, it gives me other problems because it completely screws up the screen rendering. I haven't found a good solution.

    If I set fields to validate immediately, I have found that the validation is sometimes triggered before you get to the panel. So, if the field is on panel 3, the error will already be triggered after you fill out the fields on the first two panels. This doesn't cause any usage issues, because it works - but the system is telling them to fill-in the field with an error message the moment to open that panel.

    Should I use only server side validation on a mobile app, because I don't know what the device will or will not handle? Or can I safely use client-side validation, but if so, what is the best way to do so?

    #2
    Re: Error Message handling with Mobile Panels

    Having posted this and done a bit more work I see there are about a million options for showing error messages and just as many different selections inside each option. When using panels, I am going to recommend that you use the server side dialoguevalidate event to house the bulk of your errors.

    You can also use errors at each control, but those will only be seen if the user goes back to that control. If you use them in tandem, it works pretty well. They get an error at the submit button, then they see the errors when they scroll back through the panels.

    In the error style properly under validation and error Reporting, I recommend you stay away from the global option. It did not work well for me with panels.

    If you use the option "show UX compentent validation errors in popup window", you will get two popup windows. One from the dialogevalidate event, and one from this checkbox. (This one I will submit as a bug, because I don't think it was intended to work this way.)

    That's my two cents for now. Maybe it will help someone down the line....

    Comment

    Working...
    X