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

After App Login It Just Sits On Working Screen

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

    After App Login It Just Sits On Working Screen

    I have an app that after I login it just sits on a screen that saids working. It the login ux component in the client side event I have an action script in the afterlogin that calls the panel that has the embedded main app. Also on the server side in the on login event I have some code that sets a session variable that filters base on userid. Not sure if the issue is with the filtering process or it not knowning which panel to call in the main app or something else?

    #2
    Re: After App Login It Just Sits On Working Screen

    Are you sure you're actually logged in?
    Have you published your UX?
    Is security for the UX set to Always Allowed?
    Is your Embedded UX published?
    Is the Embedded UX Security set to Always Allowed?
    Are you using the UX Integrated Security?
    What Alpha build/version are you using?

    If this is a mobile app I wouldn't use session vars. Use either state vars or write your userid to a textbox control and reference that for filters.

    Comment


      #3
      Re: After App Login It Just Sits On Working Screen

      Do I have to publish to IIS (which is what I am running) or can I just submit to phonegap?

      Comment


        #4
        Re: After App Login It Just Sits On Working Screen

        Because you're logging in I have to assume you're using the Alpha login process... although you've not said.

        This means that you're communicating with the Alpha Server.

        Client-side UX --> Server-side UX --> Alpha Server --> SQL Backend... and back again.

        This is how communication "normally" works if you're using Alpha Security and talking to a SQL Database.

        The UX you have rendered Client-side talks directly to the same UX published on your Server.

        So, to answer your question, all components used in your app must be published, with security set to Always Allowed, to your server.

        From there, you login using the UX Integrated Login (which you haven't confirmed you're using) and then you control security to various parts of your app.

        Comment


          #5
          Re: After App Login It Just Sits On Working Screen

          Thanks it is working now. However, it is not filtering the list correctly based on who logs in. Like I said I am using session variables for the mobile app. You were saying use state vars? Can you give an example of that or point where on alphaanywhere site I can read about it?

          Comment


            #6
            Re: After App Login It Just Sits On Working Screen

            The online doc has some good info about state vars... http://documentation.alphasoftware.c...nformation.xml

            Look at client-side .setStateInfo(), .getStateInfo(). Have a look at the Server-side events and the state var examples there. Session vars are fine... it's just that they're not always immediately available... in some circumstances.

            In your case, I'd save the Userid in a "currUserId" textbox control and set up your SQL filter based on an argument that gets its value from that textbox control. Nice and easy... always works.

            Comment


              #7
              Re: After App Login It Just Sits On Working Screen

              Working through my issues with creating a PG application and integrated login I stared at this list oh about 25 times.
              Are you sure you're actually logged in?
              Have you published your UX?
              Is security for the UX set to Always Allowed?
              Is your Embedded UX published?
              Is the Embedded UX Security set to Always Allowed?
              Are you using the UX Integrated Security?
              My issue was in there, I just couldn't figure it out. As it turns out my published component on my server was completely different than the one I was uploading to PG and I had the component security set to requires login - so guess what you cannot use the component unless your logged in - duh.

              looking back what an idiotic mess, I am only telling my stupidity to help others in the future.
              As it turns out, AS makes it easy to build a PG application - I, of course, made it hard, lol.
              Thanks!
              NWCOPRO: Nuisance Wildlife Control Software My Application: http://www.nwcopro.com "Without forgetting, we would have no memory at all...now what was I saying?"

              Comment

              Working...
              X