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

Column Properties > Security level property?

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

  • Column Properties > Security level property?

    Controlling Access to Fields

    Each field on a grid or dialog component has a Column Properties > Security level property (V7). This property contains an integer number with a value of 0 or higher. There is no upper limit to its value.

    Note : A user with a security level of 0 has unrestricted access. Any user without an assigned security level has a security level of 0.

    The security access level property is compared to a protected session variable named session.__protected__SecurityLevel. Your application code should set this variable to reflect the access rights of the current user.

    If the user has a security level lower than the field's security level, the field will be hidden. If the user has a security level equal to or greater than the field's security level, the field will be displayed.

    This is fro the help file and I can not find where in the field properties the setting is? Any one can post a picture?

    Nicholas
    Nicholas Wieland
    LedgerSuite.com Corp
    [email protected]
    http://www.ledgersuite.com


  • #2
    Re: Column Properties > Security level property?

    I've been using the Group route for so long, I haven't noticed that Security Levels appear to be missing from V9. Nick - even it is/were present in V9 you would have to pick Level OR Groups, you couldn't have both. It may be in V9, but I cant find it either.
    Steve Wood
    Join the ALPHA DEVELOPERS NETWORK
    There is no Cloud. It's just someone else's computer.
    Web - Mobile - Hosting - Products - Frameworks - Developer Resources
    AlphaToGo | IADN (100% Alpha Anywhere Websites)

    Comment


    • #3
      Re: Column Properties > Security level property?

      The default security method is group based. However, if you go to Grid -> Properties -> Security, you can select "Level based" and then the Security level option is activated for all fields and objects.

      If you use level based, the built in security system must be turned off, or all pages with a level based security set as "Allowed" as the Web Security does not evaluate levels at the page level. If you use levels, you must write your own page validation process and use the methods from Alpha Five V7 for setting a level for component level security. The components will still honor the Alpha Five V7 methods to hide / show options.

      Comment


      • #4
        Re: Column Properties > Security level property?

        Originally posted by JerryBrightbill View Post
        If you use levels, you must write your own page validation process and use the methods from Alpha Five V7 for setting a level for component level security. The components will still honor the Alpha Five V7 methods to hide / show options.
        Jerry I have only worked with v9 can you post an example of how this is done?
        I found the switch you are talking about but have no idea how this is accomplished.


        Thanks
        Nicholas
        Nicholas Wieland
        LedgerSuite.com Corp
        [email protected]
        http://www.ledgersuite.com

        Comment


        • #5
          Re: Column Properties > Security level property?

          Nick,

          Believe it or not, just like I have a "web template" for versions 8 and above, I have a template for version 7 that uses the Security Levels concept. It comes with documentation on how to build an application using that security method (because that's all we had back then. I sold 30 copies back when V7 was current. It is unsophisticated compared to my current web template, but it works.
          Steve Wood
          Join the ALPHA DEVELOPERS NETWORK
          There is no Cloud. It's just someone else's computer.
          Web - Mobile - Hosting - Products - Frameworks - Developer Resources
          AlphaToGo | IADN (100% Alpha Anywhere Websites)

          Comment


          • #6
            Re: Column Properties > Security level property?

            Steve,

            Understand I just thought the based on what I was reading that it would give more control over fields in the table from not being seen based on a log on such as SQL.

            Nicholas
            Nicholas Wieland
            LedgerSuite.com Corp
            [email protected]
            http://www.ledgersuite.com

            Comment

            Working...
            X