Guys,
I have a requirement to open different components based on the operator logging in.
There are 3 sets of users and each need to be taken to 3 different components. The users do not want the home page to be displayed.
I would think this needs to be done through Peoplecode.
What will the peoplecode be? and where should the peoplecode be placed ?
| Title | Under | Posted on |
|---|---|---|
| MD5 - SHA checksum of a file. | PeopleSoft Technical | 02/07/2012 - 5:29am |
| nVision Tabular Report through PIA with prompts | PeopleSoft Technical | 02/02/2012 - 10:07pm |
| Can we create an AE to mass update Position - Jobcode data? | PeopleSoft Technical | 01/18/2012 - 3:11am |
| Pay Components on job data can be defaulted and setup based on the rules? | PeopleSoft Functional | 01/05/2012 - 4:58am |
Could you please be more specific? Do you mean to ask that a same content reference needs to hold 3 different components ? Each one for that specific user?
How are you differentiating between those 3 users? They have separate permission lists? In that case you can create three components and register with same content reference label and give the appropriate permission list to each component.
I apologize if i understood your question wrongly.
All the best
Shiva
Yes.
3 separate components ( say customer home, vendor home and guest home ) for those 3 types of users. ( when any of the category of user logs in, I can determine that based on permission list )
As soon as the user is logged in, I need to open up the relevant component.
Ok. I would think you have to do it in the following manner.
Create three components and register each of them with the appropriate permission list.
By this way , every user who has the appropriate permission list will view their corresponding component. People correct me , if there is any effective way to do.
Regards
Shiva
To navigate directly to a specific component you need to give the full URL in the with the Menu , Market and the Panel GroupName. A user will then login and will be automatically redirected to the component specified in the URL.
Post new comment