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

Dialog published session variables problem

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

    Dialog published session variables problem

    In the published variable properties of a ux componrnt, I entered the following
    SESSION.CUSTOMER = "HILLSB" as a published variable.
    I also had a javascript function as follows:

    function testing() {
    var showme = {dialog.object}._vars.SESSION.CUSTOMER;
    alert(showme);}


    When invoking the function in the on click event of a button in the same ux component .
    it returns "undefined" rather than the expected "HILLSB"

    This was done as a way of tracking some unexpected results when using the session variable.

    I amusing the latest a5v12 version 4.Has anyone else had problems with the published varianles property in
    the UX component? Or do you see a problem with my methodology ?
    John

    #2
    Re: Dialog published session variables problem

    John,

    I believe what you're wanting to use is the following code:
    Code:
    {dialog.object}.getSessionVariable('CUSTOMER');
    The document on this code is as followed:


    I hope this helps...

    Regards,
    Joshua

    Comment


      #3
      Re: Dialog published session variables problem

      Setting the value of a session variable requires a server call back. SESSION.CUSTOMER = "HILLSB" in the UX properties doesn't do that. I know the "IMPORTANT" example in the Session Variables to Publish window may lead you to believe that but I don't believe that's the case. Instead try placing your SESSION.CUSTOMER = "HILLSB" in the UX's onDialogInitialize server-side event. Should work then.

      Here is an example component...

      SV_Example.a5wcmp

      EDIT: Just to be clear ... in the Published Session Variables part of the UX's properties you do want SESSION.CUSTOMER. You'll then have to set it's value before you can use it (like how I described above and in my component example). Then use the code Joshua suggested and you'll achieve what you want.
      Last edited by mikeallenbrown; 04-26-2016, 07:22 PM.
      Mike Brown - Contact Me
      Programmatic Technologies, LLC
      Programmatic-Technologies.com
      Independent Developer & Consultant​​

      Comment


        #4
        Re: Dialog published session variables problem

        You don't say, but if you're working in mobile I'd have a look at using State variables instead. Server and Client side availability.

        Comment


          #5
          Re: Dialog published session variables problem

          Thanks for the responses folks. Here is what I did:
          1) I left SESSION.CUSTOMER = "HILLSB" in the published session variables property
          2)I put SESSION.CUSTOMER = "HILLSB" in the dialog's on initialize server side event
          3) I changed my javascript function to the following:
          function testing() {
          var showme = {dialog.object}.getSessionVariable('CUSTOMER');
          alert(showme)}
          it now returns false rather than undefined
          As to the suggestion to use state variables as an alternative. I need session variables to accomplish my goals.

          Comment


            #6
            Re: Dialog published session variables problem

            #1 is incorrect ... it should be only SESSION.CUSTOMER
            Mike Brown - Contact Me
            Programmatic Technologies, LLC
            Programmatic-Technologies.com
            Independent Developer & Consultant​​

            Comment


              #7
              Re: Dialog published session variables problem

              As to the suggestion to use state variables as an alternative. I need session variables to accomplish my goals.
              I'd have to ask why you can only use session variables to accomplish what you need to do.

              Comment


                #8
                Re: Dialog published session variables problem

                Mike,
                Thank you for pointing out the error of my ways. That fixed the problem.
                As a point of interest:
                var showme = {dialog.object}._vars.SESSION.CUSTOMER;
                and
                var showme ]= {dialog.object}.getsessionvariable('SESSION.CUSTOMER')
                produce the same results. the ._vars object contains all the variables published in the dialog properties
                making it no longer necessary to do an ajax callback to get values via javascript
                Thanks to all contributors

                Comment

                Working...
                X