Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "/Stardust/KnowledgeBase/Customization/Portal/Role Based Stardust UI Customization Using Spring Bean Post-processor"

m (New page: == Introduction == In this article, we will see how you can customize access permission to the Stardust Portal UI components using spring bean post processor approach. In the portal, per...)
 
 
(22 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
+
#REDIRECT [[Stardust/Knowledge Base/Customization/Portal/Role Based Stardust UI Customization Using Spring Bean Post-processor]]
== Introduction ==
+
In this article, we will see how you can customize access permission to the Stardust Portal UI components using spring bean post processor approach.
+
In the portal, perspectives, launch panels, and views are implemented and controlled by spring backing beans. The spring backing beans take care of UI component visibility (like launch panel links) and role based access permissions.
+
If you need to change the default UI access policy, you can use spring bean post processor and change access *permissions by changing UI component backing beans as per your need. For example, you can change the things like:
+
*Make the ‘my documents’ launch panel not to be accessible to X role;
+
Restrict the process details view to be visible for Role Y and so on
+
Now let us see all this in action with illustrative example;
+

Latest revision as of 20:23, 10 March 2014

Back to the top