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



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

Has anyone created a Login page using a UX component?

  • Filter
  • Time
  • Show
Clear All
new posts

  • Has anyone created a Login page using a UX component?

    I am developing a mobile app and do not understand how you would use the standard Login or App Launcher component to create a login page that has the same look and feel as a mobile panel card. I have never used Alpha’s security or created a Login page before. It seems like you should be able to use the first panel card as the login page and then call a5ws_login_user() to authenticate. Is there more to it than this?

    I followed the Login component code as far as I could using Firebug from the point where the form is submitted. The last thing it does (as far as I can tell) is make an AJAX callback to an Xbasic system login function. I have not been able to test a5ws_login_user yet because I am having some problems with my SQL and/or Active-Link web security tables which I am trying to resolve. It would be nice to know if anyone has been able to do this or if there is a way to use App Launcher and maintain the same look and feel as a panel card.


  • #2
    Re: Has anyone created a Login page using a UX component?

    Hi Dave

    I have made several login panels, some with username and password and one that logs you in based on a choice of pictures and patterns. It is important to get the security working first as it can be very confusing to figure it out without that.



    • #3
      Re: Has anyone created a Login page using a UX component?

      I have placed a textbox for username and password on a UX Panelheader and used the security functions from there. However, I don't think I'll have to use it as there are some new Login features coming. From Selwyn...

      We are adding integrated login to the UX so that you will have the following options

      1. use a standard Login component that redirects to the ux on login
      2. use the AppLauncher component and turn on the login feature
      3. use the integrated login functionality that is being built into the ux.


      • #4
        Re: Has anyone created a Login page using a UX component?

        Thanks. I just got mine working too after troubleshooting a problem I was having with my SQL web security tables. I could not even log in with the old login component. I added a5ws_login_user to my login panel card and it's working great! When I originally created my mobile app, I made a login panel card with a user id and password, but never bothered implementing security until now.


        • #5
          Re: Has anyone created a Login page using a UX component?

          Yes... makes it really simple. I haven't added anything for changing password, invalid login etc. I'll wait for the new UX login stuff.


          • #6
            Re: Has anyone created a Login page using a UX component?

            Moving forward, is there a best practice in Alpha for having your code remain in a state where it will authenticate the user after login but also allow you to test in Working and Live Preview? The call to a5ws_login_user will fail in Working and Live Preview modes and also if you disable security. I realize you can always comment out the code when testing or maybe even add a5w_FlagWorkingPreviewOrPreview() to your logic before calling a5ws_login_user. My concern is forgetting to uncomment the code or relying on a5w_FlagWorkingPreviewOrPreview() never to fail in production. I don't want to accidentally create a backdoor (or an open door) to the system after moving my app back to production because I forgot to uncomment a line of code or because a bug in the system is causing a5w_FlagWorkingPreviewOrPreview() to return "true".

            I hope I am making sense. This is kind of hard to explain.



            • #7
              Re: Has anyone created a Login page using a UX component?

              Yes, makes sense... not hard to explain... it's a standard software development concern. I make notes on a white board about final delivery checks... stuff that needs to be done before moving code into production. I check that list and then I check my code. Even if I know I've already made those changes... I check it anyway. It's the last thing you should do. Use any kind of reminder system that will work for you and develop the habit of checking it.