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.
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.
Comment