Certain requirements during a phase of a project cycle demands the following:
- Add Custom perspective within the Stardust portal
- Add Custom Views within the custom perspective
- Role Based access to the aboved defined views
The key here is that these aspects can be set programmatically and do not require the portal context files to be changed.
b) Setting Perspective and Views customization project (Example Attached)
- The above example project Stardust_RoleBasedPlugin has a structure that includes all the markups(xhtml,images..etc), and source. Nothing else needs to be stored at the dynamic web application level.
- Compile the attached project plugin and add the same in the WEB-INF\lib folder of your dynamic web project
- Add 2 new roles/participants to the process model that will be deployed eventually, "Internal" and "External".
- Deploy the process model.
A new perspective with id "aoBccPerspective" will be added.
- If you login to the portal with the user having "Internal" role following BCC perspective with all the views will be displayed.
- If you login to the portal with the user having "External" role New Ao Ao perspective with 2 new views "Process Manager" and "Process Search" will be displayed
- With this spring and programmatic way you can control and define the different views within the portal, which can be role based as well. That would avoid modifying the Portal level context files, shipped with default Stardust.
Lets look at the key spring context files of the above configured plugin
- Portal UI Initialization Bean is the one which sets the initial UI context
- The below context file defines the management views.