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



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

Basic Question About Applying Security

  • Filter
  • Time
  • Show
Clear All
new posts

  • Basic Question About Applying Security

    I have .. finally .. successfully converted my application from the old TabbedUI interface to an Expanding Menu interface. Now I'm going through the security permissions and have a very basic question, I may be overthinking this but I'd like some other opinions.

    At login, I am redirecting users to a specific home page depending on their security group. Each home page is the new Expanding Menu interface. So Administrators go to Administrators Home, Users go to the Users Home, and so on.
    Now, because each user is logged into their respective home page based on their security, is it necessary or good practice to still apply security permissions at the Expanding Menu level.

    That is, if a user is logged in as Administrators, do I or should I apply security for Administrators at every menu branch as well? Is this redundant? Is it better practice? Is it more secure?
    If multiple groups were using the same home page then I would definitely apply security at the menu level.

    Thoughts anyone?
    Alpha Anywhere v12. Build 8245-5650 IIS v10.0 on Windows Server 2019 Std in Hyper-V

  • #2
    Just my thoughts... depends i think.
    I have not choosen a homepage per usergroup. But have a menustructure based on functions. And each and every option is explicitly authorized for groups who should have access to that function.
    If a functions loads a page, you have to authorize that page accordingly.

    If you have a menu structure per usergroup, maybe have (now or in future) many usergroups, and usergroups share a decent amount of functions you end up with maintaining many more or less equal menu components..... I prefer one menu structure, but maybe that is just a matter of taste....
    Ger Kurvers
    Alpha Anywhere / V4.6.1.9- Build 6488
    Development: Mysql, windows 10 64 Applicationserver: standard on Windows server 2019


    • #3
      Thanks but I have some user groups who use the same home page and some user groups with unique home pages. Reason being, they will have different embedded objects displayed at login (ie dashboards).

      Regardless, management isn't my question. I'm more interested in what is best practice for security application in the above structure.
      Apply only at the top component level only or add to the individual menu items when only one group has access to the component?
      Alpha Anywhere v12. Build 8245-5650 IIS v10.0 on Windows Server 2019 Std in Hyper-V


      • #4
        I think that's redundant, if the page has usergroup security, anything in that page will only be accessible by the usergroup. If you have multiple usergroups using the same page then you'll be forced to assign permissions per menu item, not a big deal but you should go through each user experience and having inside knowledge of how it is setup try to get around your security setup. If you can't do it...
        NWCOPRO: Nuisance Wildlife Control Software My Application: "Without forgetting, we would have no memory at what was I saying?"


        • #5
          Charles, that's what I thought, but I wasn't sure if would be 'more' secure to add layers. Or as you say, it's redundant. And yes, testing is key! Thanks.
          Alpha Anywhere v12. Build 8245-5650 IIS v10.0 on Windows Server 2019 Std in Hyper-V