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

UX Login Session Variables

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

    UX Login Session Variables

    Hi,

    I've created a UX login component which is working correctly, I know session variables can be used to filter the data, but how?

    I only want to use the UserID to bind with the other components in my app, but where and how do I do this?

    Thanks

    #2
    Re: UX Login Session Variables

    Have you tried setting the session variable with an ajax callback when the user pushes the login button?

    Comment


      #3
      Re: UX Login Session Variables

      Hi,

      Thanks for the reply, Have you got an example of the code I can use for the callback?

      Comment


        #4
        Re: UX Login Session Variables

        An ajax callback isn't required. There's a server-side event, onLogin, where you can check if the login was successful and setup any session variables you need that way:

        Code:
        if (e.loginSucceeded <> .f.) then
            dim pUser as p
            a5ws_logged_in_user_values(pUser)
            session.userId = pUser.userId
        end if
        Does this answer what was being asked? Or was the question more along the lines of how to populate/filter data in the UX with the logged-in user values?
        Alpha Anywhere latest pre-release

        Comment


          #5
          Re: UX Login Session Variables

          Hi Sarah,

          Thats working perfectly for me, thanks for your help.

          Comment


            #6
            Re: UX Login Session Variables

            Yeah you know, it would be sweet to have some pre-built session variables in Alpha. We all eventually want to reference these values in web apps. It should just be a drop down selection in the default values properties at this point...literally that code would work in all of our applications, and of course the next logical step from that is to filter records by the variable - another drop down selection in the query.
            I can imagine there are many more useful variables that could be hard coded right into Alphas UX and Grids, on demand.

            I see this as a separate area of web security, called Session variables, where you just select the ones you want per grid or UX just like permissions.
            Then when you want to reference one as a default value, its already there as a dropdown selection in the Default values, etc.
            NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

            Comment


              #7
              Re: UX Login Session Variables

              In most web security configurations, there are very few values that are available from the security system itself after a user has logged in. Typically, the only value is the UserId / UserName which can be obtained anywhere with
              Code:
              a5ws_GetCurrentUser()
              . About the only other values that could be usable would be the security groups, and that could be obtained with
              Code:
              a5ws_Get_User_Assignments(a5ws_GetCurrentUser())

              Comment


                #8
                Re: UX Login Session Variables

                Charles,

                Just to mention, I have had something similar to that in my Framework for many years (see image). It ensures specific session vars exist mainly after login. However, at least in my applications, I never have more than a few session variables, five or six at the most. I use them to store a couple key values, and never for secondary values like "home address", etc.
                Attached Files
                Steve Wood
                See my profile on IADN

                Comment


                  #9
                  Re: UX Login Session Variables

                  Originally posted by CharlesParker View Post
                  Yeah you know, it would be sweet to have some pre-built session variables in Alpha.
                  That would be a great feature. I am currently trying to figure out how to bring a selected record's value over to another page and I am stumped. In the past I would find the action JavaScript equivalent of something, create it, then turn it into text and usually I would understand it from then on.
                  I will get it eventually, but it would fit the rest of Alpha's functionality to do this automatically.
                  Last edited by BCJack; 01-05-2015, 08:34 PM.

                  Comment


                    #10
                    Re: UX Login Session Variables

                    Originally posted by BCJack View Post
                    That would be a great feature. I am currently trying to figure out how to bring a selected record's value over to another page and I am stumped. In the past I would find the action JavaScript equivalent of something, create it, then turn it into text and usually I would understand it from then on.
                    I will get it eventually, but it would fit the rest of Alpha's functionality to do this automatically.
                    Open a new page? Pass it as a parameter to the page.
                    Alpha Anywhere latest pre-release

                    Comment


                      #11
                      Re: UX Login Session Variables

                      Originally posted by TheSmitchell View Post
                      Open a new page? Pass it as a parameter to the page.
                      That sounds like it is simple enough to be what I am missing, but I am not sure what you mean exactly. I dont want to pull this topic off track, however, as my problem really is not related to login sessions, so I started a new thread.

                      Page-To-Page Variables

                      Your input would be very much appreciated because I have already learned a lot from you so far, especially when you reply with answers and show how you found them. That alone is invaluable.

                      Comment

                      Working...
                      X