FF Login notification shows FF User id instead of FF Owner id against FF Owner in Decentralized FF

[former_member272370]

FF Login notification shows FF User id instead of FF Owner id against FF Owner in Decentralized FF:

I believe the document id being used is" /GRCPI/GRIA_SPM_NOTIFICATION " in the target system (ECC). The standard content in the document id is as below in (1) but the mail notification sent to the controller results as in screenshot (2). Please update on issue note fix if any.

We are on GRC 10 SP16.

(1)

Dear %RECIPIENT%,

The login notification details for the Firefighter ID %FFOBJECT%  in system %CONNECTOR%  using Reason code  '%REASON_CODE%'  is as follows :

Firefighter:              %FF_USER%

Owner:                   %OWNER%

Date & Time: %LOG_TIME%

Reason code: %REASON_CODE_DESCN%

Activity:              %ACTIVITY%

Kind Regards,

Access Control Administrator

(2)

Dear XXXXXXX,

The login notification details for the Firefighter ID XXX_FF_ABAP in
system X20CLNTX00 using Reason code 'Critical XXXX issues' is as follows :

Firefighter: Shasxxxx
Owner: Shasxxxx
Date & Time: 11.09.2015 16:47:40
Reason code: test
Activity: test


Kind Regards,
Access Control Administrator

Regards,

Arun

[former_member197694 · Accepted solution]

Hello Arun,

Check and apply the below Note for correction

1908134 - Wrong FFowner shown in email notification

Regards

Baithi

[former_member272370 · Accepted solution]

Thanks Baithi !

Additionally to the above, apart from the configuration mentioned in various EAM blogs, the FF Owner has to exist in the Target system too along with the GRC system in the decentralized firefighting.

This is because, in decentralized firefighting, the FF login notification is triggered by the FF user email id in the target system and it has to obtain the FF Owner from a source which has to be present in the target system.

We have created to the FF Owner in the target system and now the FF Owner id shows in the login notification mail.

Regards,

Arun

[former_member197694 · Accepted solution]

Hello Arun,

Thanks for update to community

if issue solved then close the thread as answered.

Regards

Baithi