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

setting a field to current username using WAS

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

    setting a field to current username using WAS

    Hi, I have a web based app and in my component's CanUpdateRecord event I'd like to set a field to the username of the currently logged in user. How do I do this? Is there a session variable that can be accessed from the CanUpdateRecord event?

    thanks

    #2
    Re: setting a field to current username using WAS

    There will be a session variable available with the user name only if you set it somewhere, else there isn't one. I have the following in my Header.A5W page, meaning it refreshes itself everytiime someone refreshes the browser. It keeps the 'fullname' in a session variable, which is then available throughout the system where needed. I assume you are using Security Framework with the 'ulink' set, else this exact code won't work. The ID in my example is the Ulink value shared betwen my web_users table and the Security Framework files.

    Code:
    IF eval_valid("session.__protected__ulink")
    	IF session.__protected__ulink <> "" THEN
    		session.fullname = alltrim(lookupc("F",alltrim(session.__protected__ulink),"Fname + " " Lname","[PathAlias.ADB_Path]\web_users","ID"))
    	END IF
    END IF
    Steve Wood
    See my profile on IADN

    Comment


      #3
      Re: setting a field to current username using WAS

      Thanks Steve.
      For those of you who don't know (and for my future reference), there are few assumptions here that I'll spell out so that this makes better sense to non experts:

      The ulink variable identifies the logged in user on a web app, but is only active if you:

      a) got WEB_SECUTIRY-->WEB_SECURITY_CONFIGURATION and put a checkmark in the "Enable external user identifier field" option under CUSTOMIZE_OPTIONS.
      b) also, in the "session variable for identifier field" field under CUSTOMIZE_OPTIONS, you must specify a variable name. You can use the name "ulink" or as Steve did above, you can use "__protected__ulink". To learn about the __protected__ prefix, check the helpfile.
      c) Turning this on will cause a new field to appear under WEB_SECURITY-->WEB_USERS_AND_GROUPS. Edit one of your existing users and you'll see a new field called "External User ID Value". Set this to something unique for each of your users. For simplicity sake (this isn't the best idea), let's say you set this to be the same as the User ID.
      d) If you do the above, anywhere in your component events or in alpha5 script on a5w pages, you can refer to the session variable session.__protected__ulink and this will produce the username of whomever is currently logged in.
      e) In Steve's example, it appears that his ulinks are unique numbers that he assigns to each user (most likely, this is done automatically). The code he sent then takes the session.__protected__ulink and uses it to search a user table from which he extracts the first and last name of the logged in user. Then he puts that into a more temporary session variable called session.fullname. Probably this would need to be called each time the page is loaded to work (he prefers using header files, search "Header.A5W" for some of his posts on this.)

      I personally use steps a-d because I only have half a dozen users and I enter their accounts manually myself. To understand when/why you'd need to use step e, you should read more about the A5 security framework and what kind of security systems you'd need for different types of web apps. Steve has written a short and very clear article on this on his webpage. To read it (I recommend to anyone doing web apps). Go to http://alphatogo.com/learning.htm and click on the "User Registration and Login Methods" article.

      Comment

      Working...
      X