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

Looking for information regarding integrated login and setting fields based on logged in name

  • Filter
  • Time
  • Show
Clear All
new posts

    Re: Looking for information regarding integrated login and setting fields based on logged in name

    I would try an alert('test'); as the only code in both the afterLogin and afterFailedLogin events. Are you getting logged in? As well... in the server-side onLogin event... again as the only code in this event... put e.javascript = "alert('test');" Shove the e.javacsript code into the server-side beforeLogin event as well. Might as well cover all the bases.

    See what's firing and what's not.


      Re: Looking for information regarding integrated login and setting fields based on logged in name

      I'll see your video and raise you a:


        Re: Looking for information regarding integrated login and setting fields based on logged in name

        No, no, no, no... now I see what you're doing. You're testing login stuff inside your embedded object... is that right? Is that what I'm seeing? If so... no.

        Your login tests must be in the parent UX... in the UX in which the login is taking place.

        It's the parent UX that decides, based on login info, if and where you go next.

        BTW... thanks for posting the video.
        Last edited by Davidk; 12-04-2015, 04:14 PM.


          Re: Looking for information regarding integrated login and setting fields based on logged in name

          Wow. So this indeed was all due to something really, *really* silly. Can't believe it didn't occur to me. Seems like common sense now, but I hadn't touched the 'outer' login UX since it was implemented. Only reason I even showed that in the video was for reasons of completeness. Guess it's good that I did! I will play in the proper UX later then and report back. I apologize for wasting your time, but much thanks!


            Re: Looking for information regarding integrated login and setting fields based on logged in name

            No waste at all. This type of thing isn't really completely obvious. Just got to keep digging. The addition of AD to Alpha should be, and is, transparent, but because it's kinda new it provides other possible avenues for investigation. Soon as you saw you pop into that embedded component I knew the issue.


              Re: Looking for information regarding integrated login and setting fields based on logged in name

              Got around to it this morning, and of course that works as intended now. It helps to be in the right &#$@#ing UX component.

              If you are feeling especially generous at some point, I'm now trying to figure out the best way to convert the username in AD to a full name. "jdoe" to "John Doe".
              The notes say to
              "In the onLogin server-side event you can execute code to translate the user name logged in with into a 'friendly' user name which can be safely displayed on the client-side. For example, assume that you had a table that had two columns - 'userName' and 'friendlyUserName'. In your onLogin server-side event you would execute code to set e.userNameFriendly by looking up the friendly name for the user name."
              So now I know this is due to my lack of javascript knowledge, but I could use some direction as to how that can be done. I can make a new table and reference it, but I am guessing it can be done by some sort of a lookup to the same table I am in. for instance, I have the tech number, first name and last name, as well as an email that starts with the AD username. [email protected]. Maybe some kind of an rtrim on that field and then map & concatenate the first and last name to 'Record_Creator'.

              What would be a snippet to do the "code to lookup the friendly name" bit?