principal propagation permissions for intermediate message event

[Former Member]

Hello,

My process contains an intermediate message event followed by an automatic activity. I want the logged in user who invokes the message event to be propagated to the automatic activity. Therefore I activiated principal propagation in the corresponding pool (process has only one pool and one lane) and assigned RoleX as potential owners to this pool. The logged in user (UserX) is assigned this role RoleX as well as BPEM End User, eu_role and eu_core_role. Security concept for service and client is logon ticket. I'm using NW AS 7.2.

When the logged in user UserX invokes the intermediate message event nothing happens: the process doesn't react and not a single error is logged anywhere. However if I assign the role Administrator to UserX and the message event is invoked by UserX with these permissions everything works fine as expected: the process message event is executed, following automatic activity is executed with the forwarded credentials from UserX.

Why does it only works when I assign Administrator rights? All documentations I found about principal propagation never mention role Administrator. It should not be necessary. And I don't want assign Administrator rights to standard users of this custom application. What do I have to do so a standard/restricted user can execute an intermediate message event and have its credentials propagated to the next process step?

[ch_loos · Accepted solution]

Hello Anja,

your RoleX will also need the TRIGGEREVENT action in order to call the intermediate event.

See http://help.sap.com/saphelp_nw73/helpdata/en/9c/23eaeb4c53486f8d9c4cb376b99994/frameset.htm   for more information.

[Former Member · Accepted solution]

Thanks Christian. Problem is that this action as well as the role SAP_BPM_TRIGGER_EVENT don't exist on our server. Got it introduced with some updates for NW AS 7.2 or should they be available since the very beginning of 7.2? It the latter is true, what might be the reason that they don't exist on our server?

[ch_loos · Accepted solution]

It was introduced in 7.2 SP04 and 7.30 SP03. Before you needed the SUPERADMIN role.