You could copy Content Reference using Application Designer, but you should me careful when doing this across different applications.
Applications have different parent folders, content reference has permissions that are application specific, which to not have to exist in the target environment.
And especially Portal works different from the other applications.
Portal, said very easily, "has no own application", but is used to link to content references to other applications.
You should really set up Content reference in Portal manually, that's why Unified Navigation was introduced.
Why you should set it up manually and not copy via application designer:
Content reference in for example HCM is usually configured on LOCAL_NODE.
When you copy this across to Portal, Portal will interpret this a link to the Portal application.
This has to be changed in Portal to the local node of HCM, for example PSFT_HR.
Content reference have permissions set, usually deviated from the permission lists on components using the Portal Security Sync process.
Permission to a component is/could be different than permission to the content reference that references the component.
One is, can I see the menu link, other is, do I have access to the page.
And is exactly what you should do with Portal in junction with other PeopleSoft applications.
Portal has only permissionlist to content references (menu links) to components on other Applications nodes.
On the other application permission list on the actual component has to set.
So userprofiles and assigned roles will have to synchronized across applications user the USER_SYNC service.
Roles in Portal and and other applications have to exists, but do not need to have any permissionlists in the Portal environment.
Suppose you have a user in HCM with roles and within the role permissionlist to components.
The same user will be synced to Portal, the user profile will be copied and assigned roles will be copied.
Now Portal needs to have roles/permissionlists to the content references in Portal that link to the HCM component.
These permissionlist in Portal can be other than the ones in HCM.
Applications have different parent folders, content reference has permissions that are application specific, which to not have to exist in the target environment.
And especially Portal works different from the other applications.
Portal, said very easily, "has no own application", but is used to link to content references to other applications.
You should really set up Content reference in Portal manually, that's why Unified Navigation was introduced.
Why you should set it up manually and not copy via application designer:
Content reference in for example HCM is usually configured on LOCAL_NODE.
When you copy this across to Portal, Portal will interpret this a link to the Portal application.
This has to be changed in Portal to the local node of HCM, for example PSFT_HR.
Content reference have permissions set, usually deviated from the permission lists on components using the Portal Security Sync process.
Permission to a component is/could be different than permission to the content reference that references the component.
One is, can I see the menu link, other is, do I have access to the page.
And is exactly what you should do with Portal in junction with other PeopleSoft applications.
Portal has only permissionlist to content references (menu links) to components on other Applications nodes.
On the other application permission list on the actual component has to set.
So userprofiles and assigned roles will have to synchronized across applications user the USER_SYNC service.
Roles in Portal and and other applications have to exists, but do not need to have any permissionlists in the Portal environment.
Suppose you have a user in HCM with roles and within the role permissionlist to components.
The same user will be synced to Portal, the user profile will be copied and assigned roles will be copied.
Now Portal needs to have roles/permissionlists to the content references in Portal that link to the HCM component.
These permissionlist in Portal can be other than the ones in HCM.
ReplyDeleteWhat an awesome post, I just read it from start to end. Learned something new after a long time.
Manual testing training in Chennai
Selenium testing training in Chennai
ReplyDeleteI do agree with all the ideas you have presented in your post. They’re really convincing and will certainly work. Still, the posts are very short for newbies. Could you please extend them a little from next time?..Keep this great work..
Web development company in Chennai
Very nice post here thanks for it I always like and search such topics and everything connected to them. Keep update more information..
ReplyDeleteSeo Services
ya this article was nice one but i expect more from this topic its useful for our pepoles.
ReplyDeleteBack to original
This site has lots of advantage.I found many interesting things from this site. It helps me in many ways.
ReplyDeleteOracle Fusion HCM Technical Training in Ameerpet