Hello,
after refining the groups/roles/permissions concept on our portal I found out that VC developers need end-user <b>and</b> admin read permissions on the required system objects (in order to see their aliases e.g. in 'find data' while vc modelling).
This fundamentally upsets my understanding of portal permissions! So far I thought the various admin(a.k.a. 'design-time')permissions were only needed for administering pcd objects (i.e. look at/alter object attributs) whereas end-user(a.k.a. 'run-time')permissions where only relevant for end-users who run applications in the portal.
In my case I would expect end-user permission to suffice for developing vc models. I mean as for the system objects used, a vc developer is an end-user - he doesn't administer system objects in any way.
Any ideas why this is so?
Regards,
Sebastian