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

Mobile Persistent Login

  • Filter
  • Time
  • Show
Clear All
new posts

  • Davidk
    Re: Mobile Persistent Login

    Using the Alpha sample, the token is created on the server and saved in the device localStorage. On the app 2nd and subsequent starts the token is retrieved. If it's there and not blank then it's assumed all is good and the app proceeds.

    It's up to you to follow the same practice with any other information you may want to save. You can't get a username if you haven't saved a username.

    Following the same pattern, get the username, and anything else you want, and save it in localStorage. When the app starts... get the token and everything else you've saved and push that data into controls in your app.

    I don't often use localStorage... I use the device File System... or SQLite... but the concept is all the same. If you need data, then save that data. You don't know when you'll be back to the server to get it there.

    Leave a comment:

  • scrimej
    started a topic Mobile Persistent Login

    Mobile Persistent Login

    I've struggled with this for too long so I'm hoping someone can point me in the right direction on what I'm sure is a simple solution.

    Within a Mobile Application, I used the Alpha Template to generated a Mobile Persistent Login UX.
    I also have a separated application UX which I then embed into the Login UX within the PANEL_APPLICATION

    My embedded Application UX needs to know who is logged in, in order to filter various lists, and set a default foreign key field when I submit a record that indicates the current logged in user submitted this particular record. Prior to persistent login, I used an argument from the login ux an passed that to the embedded UX

    I was able to get this working in the persistent login example somehow, but after I closed the application (not logged out) and it re-logged in using the initial token I lost who the logged in user was.

    Basically, I need to know at all times the Primary Key of the logged in user in the embedded UX. I tried state variables but again after the initial login those seemed to be gone.

    Hopefully it's clear what I am trying to accomplish. Can anyone point me in a direction to accomplish the above?