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
Devcon 2020 Goes Virtual! LEARN MORE >

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

TabbedUI Based On Logged In User Groups

Collapse
X
Collapse
 
  • Page of 1
  • Filter
  • Time
  • Show
Clear All
new posts
Previous template Next
    #1

    TabbedUI Based On Logged In User Groups

    Just seeking some feedback or advice on the following change I am considering implementing:

    Background
    My application has been designed from day one, many years ago, around the TabbedUI.
    I have several groups of users, all of whom login and see the same main tab page inside the TabbedUI. The main tab acts as a status board for various conditions within the department.
    Recently another department has started using the application and now I want to change the behavior of the application so that users will actually see different things in the main tab based on their user group.

    Currently my application design works like this for all users:
    1. Standalone Login Component on an A5W page - redirect page after successful login is Login Processing A5W page (defined in Web Security Settings)
    2. Login Processing A5W page - assigns session variables (user firstname, lastname, department, etc) then redirects to the Home A5W page which holds the TabbedUI component.
    3. The TabbedUI properties define the main tab page.

    1.Login.jpg 2.TabbedUI Properties.jpg


    Changes To Modify Application
    It appears access to the main tab in the TabbedUI is through the TabbedUI property main page URL, so I am playing with this idea:
    1. Login Component on standalone A5W page remains unchanged - redirects to Login Processing page
    2. Login Processing Page gets user group then redirects to appropriate Home_Group page based on user group.
    3. Create multiple TabbedUI components and pages to hold them.
    4. Create new components (for each user group) which will display the appropriate component in the TabbedUI.

    I have played around with this at home and it works. I am just curious if any of the gurus in the community has used this type of approach?
    Is it bad practice to essentially have multiple TabbedUI components simply to have a different Main Tab displayed for a particular user group? Is there a better way to implement.

    Thanks for looking.
    Alpha Anywhere v12.4.6.5.2 Build 8867-5691 IIS v10.0 on Windows Server 2019 Std in Hyper-V
    Tags: None
    #2
    Re: TabbedUI Based On Logged In User Groups

    Hi Stephen

    Used both techniques! One long time application has used a single tabbed ui and has different menu options depending upon the user group assignments and has worked well. However as the application continues to grow are now testing a revision where after login all users are taken to a terms page where they have to check an acceptance box before proceeding. Exactly where they can go will depend on their user rights so for some they have only one option and for others they may have multiple options. Each option has its own tabbedui and each tabbedui has a navigation menu section which allows navigation between the different tabbedui menus dependent again on their user rights.

    Hope this helps.

    Glen

    Originally posted by iRadiate View Post
    Just seeking some feedback or advice on the following change I am considering implementing:

    Background
    My application has been designed from day one, many years ago, around the TabbedUI.
    I have several groups of users, all of whom login and see the same main tab page inside the TabbedUI. The main tab acts as a status board for various conditions within the department.
    Recently another department has started using the application and now I want to change the behavior of the application so that users will actually see different things in the main tab based on their user group.

    Currently my application design works like this for all users:
    1. Standalone Login Component on an A5W page - redirect page after successful login is Login Processing A5W page (defined in Web Security Settings)
    2. Login Processing A5W page - assigns session variables (user firstname, lastname, department, etc) then redirects to the Home A5W page which holds the TabbedUI component.
    3. The TabbedUI properties define the main tab page.

    [ATTACH=CONFIG]44192[/ATTACH] [ATTACH=CONFIG]44193[/ATTACH]


    Changes To Modify Application
    It appears access to the main tab in the TabbedUI is through the TabbedUI property main page URL, so I am playing with this idea:
    1. Login Component on standalone A5W page remains unchanged - redirects to Login Processing page
    2. Login Processing Page gets user group then redirects to appropriate Home_Group page based on user group.
    3. Create multiple TabbedUI components and pages to hold them.
    4. Create new components (for each user group) which will display the appropriate component in the TabbedUI.

    I have played around with this at home and it works. I am just curious if any of the gurus in the community has used this type of approach?
    Is it bad practice to essentially have multiple TabbedUI components simply to have a different Main Tab displayed for a particular user group? Is there a better way to implement.

    Thanks for looking.
    Glen Schild



    My Blog

    Comment

      #3
      Re: TabbedUI Based On Logged In User Groups

      Great, thank you for your comments Glen.
      Alpha Anywhere v12.4.6.5.2 Build 8867-5691 IIS v10.0 on Windows Server 2019 Std in Hyper-V

      Comment

        #4
        Re: TabbedUI Based On Logged In User Groups

        Here is an idea we use:
        Create a ux component with one control, a tab component. On each tab, you can put a page, a component or a tabbedUI. Also, each tab has a Show/hide property, so you can set which tabs show based on a session variable set in your processing page such as Session.GROUPID. This also can give you space above the tab component for stuff common to everyone, such as "Welcome ...." or help.
        The ux layout we use looks like:
        controls.png
        and the ux showing a tabbedUI on a tab looks like:
        component.png
        Pat Bremkamp
        MindKicks Consulting

        Comment

          #5
          Re: TabbedUI Based On Logged In User Groups

          I have a single tabbedUI - what I do is put certain buttons in a frame and set security by user group that way. Very simple, single UI - each "Group" see's ONLY the buttons that they need to AND I can set up show hide based on the company_ID and or the particular user if need be - so overall a single tabbed UI can be a rock star of a UI!!!
          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

            #6
            Re: TabbedUI Based On Logged In User Groups

            Excellent suggestions gentlemen! Thanks for your input.
            Alpha Anywhere v12.4.6.5.2 Build 8867-5691 IIS v10.0 on Windows Server 2019 Std in Hyper-V

            Comment

            Previous template Next
            Working...
            X