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

Logged in User Name Friendly Get

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

    Logged in User Name Friendly Get

    I want to use something similar to the loggedInUserNameFriendlyGet function to display the user ID of the person logged into my UX component. However, I am not using the integrated login, I am using persistent login. My understanding is that this function will only work with the integrated login. Does anyone have a method they can share to make this same functionality work with persistent login?

    #2
    Re: Logged in User Name Friendly Get

    Regarding the Integrated Login... how would you be setting the FriendlyName... where would that value come from?

    Comment


      #3
      Re: Logged in User Name Friendly Get

      This video is kind of long, but explains the process of using Integrated Login



      I want to do something similar to this, but with persistent login.

      Comment


        #4
        Re: Logged in User Name Friendly Get

        Here's how I am doing it (persistent login).... add a label control to your main panel and in the Client Side Properties / Calculated field expression" enter the name of the textbox variable your app has for the user to enter their login ID
        example.PNGmobilehomescreen.PNG

        Comment


          #5
          Re: Logged in User Name Friendly Get

          The end goal is I want someone to log into my app, and on the home screen it will say something like "logged in as X", where X is the user ID.

          Comment


            #6
            Re: Logged in User Name Friendly Get

            I don't really need a video of how Integrated Login works. I was asking about how you'd go about getting a FriendlyName in that circumstance. What would you do?

            Comment


              #7
              Re: Logged in User Name Friendly Get

              Hey Dave, Sorry, I didn't explain well. But that particular video shows how to get a friendlyName with the integrated login. I know you know how integrated login works. :-) The video was just my attempt at explaining what I am trying to do, except I want to do that with a persistent login. Thanks for the feedback.

              Comment


                #8
                Re: Logged in User Name Friendly Get

                ids-dave, thanks. That looks like a good way to do it. Only problem is I have a login UX, and then embedded application UX. So I'm not sure how I could make one UX reference a username field from another UX. If you have any ideas, I would love to here them. Thanks!

                Comment


                  #9
                  Re: Logged in User Name Friendly Get

                  It's exactly the same concept. The video doesn't really show getting a real friendly name... but does talk about adding code to do lookups to get the name etc. That's what I was attempting to get at... what process would you actually use to get a name.

                  Because Persistent Login calls an Xbasic function to log in... that's where you'd run the same additional code to grab your FriendlyName... while you're at the server.

                  Then you'd follow the same practice you're using to store the other data coming out of the Xbasic login function. I'm not crazy about localStorage... I prefer DeviceStorage... but whatever you use, you'd simply store the FriendlyName as well.

                  In onRenderComplete you go after the stored data, to validate your login, and you'd also get your FriendlyName.

                  Comment


                    #10
                    Re: Logged in User Name Friendly Get

                    Originally posted by carlbsmith View Post
                    ids-dave, thanks. That looks like a good way to do it. Only problem is I have a login UX, and then embedded application UX. So I'm not sure how I could make one UX reference a username field from another UX. If you have any ideas, I would love to here them. Thanks!
                    But the FriendlyName concept was created to keep from having to display a real user login name. I thought that's what you wanted. Do you actually just want to display the login name? I'm also not sure how that works for persistent login after you've close the app and then re-opened it. The username isn't entered again... unless David is doing something else not shown.

                    Comment


                      #11
                      Re: Logged in User Name Friendly Get

                      At this point I would be fine with friendly name or user name, whichever is easier to implement. Unfortunately my Xbasic skills are limited, so figuring exactly out how to get that implemented will be a challenge. I will try to research that out some more though. Thanks!

                      Comment


                        #12
                        Re: Logged in User Name Friendly Get

                        Originally posted by Davidk View Post
                        But the FriendlyName concept was created to keep from having to display a real user login name. I thought that's what you wanted. Do you actually just want to display the login name? I'm also not sure how that works for persistent login after you've close the app and then re-opened it. The username isn't entered again... unless David is doing something else not shown.
                        I'm not doing anything else with the control "UserName". In the past, I was saving the user login ID and other info in state variables, but after modifying this app to be completely offline capable, I determined I could trust the control used for the login ID to persist to the device storage and not expire

                        Comment


                          #13
                          Re: Logged in User Name Friendly Get

                          Originally posted by carlbsmith View Post
                          At this point I would be fine with friendly name or user name, whichever is easier to implement. Unfortunately my Xbasic skills are limited, so figuring exactly out how to get that implemented will be a challenge. I will try to research that out some more though. Thanks!
                          IMO, I think you're adding complexity to your project because of the multiple UX's. I started out my 1st mobile app doing the same thing and quickly realized it was better to have only 1 UX for the entire app. For example, if your app was a single UX, you could use my earlier example and be done with it.

                          Comment


                            #14
                            Re: Logged in User Name Friendly Get

                            Thanks for all the feedback. I will look at this more today.

                            Comment


                              #15
                              Re: Logged in User Name Friendly Get

                              Oh, and I forgot to mention that one of the reasons I was sort of talked into doing the embedded UX was because I have a control bar that I only wanted to appear in the main application, not on the login screen. One of the solutions suggested to me was to have a login UX, and then a main application UX with it's own control panel. That has worked well for me, except for issues like this. And you are right, it does seem to be a pain to figure out how to jump back and forth between components to do things.

                              Comment

                              Working...
                              X