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

Mobile Login Components

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

    Mobile Login Components

    Hey everyone,

    I'm playing around with integrated login for mobile applications (I.e. I select the choice for integrated login from properties on my mobile UX)

    My only question is, how does this work?

    Is this login function still based on my web security users from the alpha control panel?

    Thanks!

    #2
    Re: Mobile Login Components

    Yup, there are sample UX components. Create a new UX and search for security. You want "SecurityFramwork-LoginComponentMobileApp"

    You should end up with 2 UX components min
    * one is your actual app
    * one is the logincomponent which you embed the first UX into.
    Use session variables/setting the loggedInFriendlyName to pass around the users name.

    If you dont do two components then you cannot use working preview as this doesnt support security. So you can have one UX if you are prepared to live with this restriction.

    Comment


      #3
      Re: Mobile Login Components

      Hm interesting ok, thank you for this. I've gotten the login working, but it seems doing something seemingly simple like getting the logged in username is a task in and of itself.

      I've tried {dialog.object}.loggedInUserNameFriendlyGet Method, as well as various ajax callbacks, and keep getting undefined. Would anyone know why this is the case?

      Thanks!

      Comment


        #4
        Re: Mobile Login Components

        Okay this bits a touch hidden.

        you have to set the value in loggedInUserNameFriendlyGet value.

        You do this in Events > Server Side Section, these are xbasic events that happen on the server side at key times, e.g. at login.

        You can read some variables as show in the default comment but you probably want this code in the onLogin event.
        Code:
        if e.loginSucceeded
        	'set the friendly username you can access in the client side javanscript
        	e.userNameFriendly = e.username
        	'or you could set a session variable
        	Session.MYUSERNAME = e.username
        end if
        If you go down the Session route then
        you must publish the session variable from the Properties section on the left
        you must declare an argument of the same name
        set to a variable of the same name
        AND ALL MUST BE IN CAPS, dont ask me why, it just does.

        Key client side event is onRenderComplete, in here I would normally
        Move on from an initial panel card that just shows a loading message
        refresh my list data (set all the lists to delay until explicit refresh)

        Hope that helps, Im just an Alpha beginner myself

        Comment


          #5
          Re: Mobile Login Components

          okay I've got the code from an actual production application we run

          in the Server side > onLogin
          Code:
          e.javascript = ""
          if (e.loginSucceeded .OR. e.flagUserWasAlreadyLoggedIn) then
          	e.session.user_name = e.username
          	e.userNameFriendly = e.username
          	e.javascript = e.javascript + "{dialog.object}.panelSetActive('PANEL_APPLICATION');"	
          	e.javascript = e.javascript + "{dialog.object}.hideWaitMessage();"
          end if
          in the server side > onDialogInitialize
          Code:
          e.javascript = ""
          'If session is still there, but you are not logged in, clear the session, log out and reload
          if session.user_name != "" .AND. Context.Security.CurrentUser == "" then
          	a5ws_logoutuser(session,request,response)
          	session.reset()
          	e.javascript = e.javascript + crlf() + "window.open('DesktopApplicationMenu.a5w','_self');"
          'logged in, i.e. your user name is not blank then redirect to the menu panelcard.
          else if Context.Security.CurrentUser != "" then 
          	 e.javascript = e.javascript + "{dialog.object}.panelSetActive('PANEL_APPLICATION');"	
          	e.javascript = e.javascript + "{dialog.object}.hideWaitMessage();"
          end if
          UX component for handling login looks like this, and the list navigates to other a5w pages depending on your menu option.
          Untitled.png

          Comment

          Working...
          X