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

a5ws_GetCurrentUser() to show on report/letter

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

  • a5ws_GetCurrentUser() to show on report/letter

    How can I get the function a5ws_GetCurrentUser() to show up on a report / letter when being printed? I tried simply adding this code in a rich text field on the layout but that didnt work, I tried created a calc field with this definition, that didnt work either. What am I missing? Any Ideas?

  • #2
    Re: a5ws_GetCurrentUser() to show on report/letter

    It really depends on what you are using to print the report.

    In my system I have a login page. Once successfully logged in, a login-processing page assigns a session variable called session.username = a5ws_GetCurrentUser(), amongst other things. The login-processing page then redirects normally to a tabbed_UI, this can be different for a mobile device.

    Because our usernames (login names) are not our full names the tabbed_ui has an SQL lookup in its ontabbeduiinitialize server side event to return the users full name as session.username. Then on any report/letter I want the persons name on I create a calculated field user=session.username. You get an error in the calculated field builder because session.username does not exist because you are not logged in, but you can ignore this. put that calculated field on the report and all should be well.

    Comment


    • #3
      Re: a5ws_GetCurrentUser() to show on report/letter

      After login create a session variable called 'userid' ... session.userid = a5ws_GetCurrentUser()

      In the report's datasource define an argument that defaults to session.userid.

      ScreenShot_2015.05.07_009_.png

      Then in the report create a calculated field using this expression: a5_GetArgumentValue("userid")
      Mike Brown - Contact Me
      Programmatic Technologies, LLC
      Programmatic-Technologies.com
      Independent Developer & Consultant

      Comment


      • #4
        Re: a5ws_GetCurrentUser() to show on report/letter

        Great! Thank you for the replies, now I just need to learn how to set session variables. I'm still getting the hang of this web stuff. Ive used the a5_GetArgumentValue() in reports before, but not session variables, Im sure its not difficult but learning where and when to use them is the trick.

        Comment


        • #5
          Re: a5ws_GetCurrentUser() to show on report/letter

          How are you logging in users? ..via Alpha's UX login template? ...There are a number of ways to do this.
          Mike Brown - Contact Me
          Programmatic Technologies, LLC
          Programmatic-Technologies.com
          Independent Developer & Consultant

          Comment


          • #6
            Re: a5ws_GetCurrentUser() to show on report/letter

            Yes, im using the login component.

            Comment


            • #7
              Re: a5ws_GetCurrentUser() to show on report/letter

              As soon as the login component authenticates the user, it redirects to a different page with a tabbed ui component.

              Comment


              • #8
                Re: a5ws_GetCurrentUser() to show on report/letter

                Try this and then follow my steps in post #3.


                ScreenShot_2015.05.07_001_.png
                Mike Brown - Contact Me
                Programmatic Technologies, LLC
                Programmatic-Technologies.com
                Independent Developer & Consultant

                Comment


                • #9
                  Re: a5ws_GetCurrentUser() to show on report/letter

                  Thank you very much Mike, Ill give this a shot.

                  Comment


                  • #10
                    Re: a5ws_GetCurrentUser() to show on report/letter

                    Hi there, I followed your steps Mike but I'm still not getting the logged in user on the report. I have a question, do I put the on-Login event on the component I open to print the report, or do I put it on the actual Tabbed_UI component?

                    EDIT: Btw, Ive tried it on both components but not at the same time.

                    Comment


                    • #11
                      Re: a5ws_GetCurrentUser() to show on report/letter

                      You place the onLogin code in the login component. Here is some sample code to try...

                      ScreenShot_2015.07.02_001_.png

                      Also, create an A5W page called Session_Info (or something like that, the title doesn't matter). In this new page have this xbasic code (see below). Place a link on your tabbed ui somewhere to access this new A5W page (set security so only you can see that link). After you log in check that page...it'll give you a lot of info in addition to session variable info. You should see the session.userid if everything is correct.

                      Code:
                      <%a5
                      a5w_info()
                      %>
                      Mike Brown - Contact Me
                      Programmatic Technologies, LLC
                      Programmatic-Technologies.com
                      Independent Developer & Consultant

                      Comment


                      • #12
                        Re: a5ws_GetCurrentUser() to show on report/letter

                        It looks as though its done correctly, right? Sorry for taking so long in my replies.
                        screenGrab.jpg

                        Comment


                        • #13
                          Re: a5ws_GetCurrentUser() to show on report/letter

                          That looks right to me!
                          Mike Brown - Contact Me
                          Programmatic Technologies, LLC
                          Programmatic-Technologies.com
                          Independent Developer & Consultant

                          Comment


                          • #14
                            Re: a5ws_GetCurrentUser() to show on report/letter

                            SUCCESS! I finally got the user name to come out on the report. Thank you Mike! Also, thank you for your patience.

                            Comment


                            • #15
                              Re: a5ws_GetCurrentUser() to show on report/letter

                              Originally posted by Gustavo1478 View Post
                              SUCCESS! I finally got the user name to come out on the report. Thank you Mike! Also, thank you for your patience.
                              You're welcome!
                              Mike Brown - Contact Me
                              Programmatic Technologies, LLC
                              Programmatic-Technologies.com
                              Independent Developer & Consultant

                              Comment

                              Working...
                              X