lock FF ID to not be requested by another

[former_member205095]

When we request on ARM a FF ID, we want that the FF ID that is already approved for another person do not appear to be requested

[madhusap]

Hi Arivind,

Since this is specific custom requirement, you can handle using following options:

Enhancement

- Enhance the access request submission method to do a check for selected FF ID against the GRC provisioning table if it has any active assignments to a user and then stop the request submission for that FF ID with relevant Error message

or

Enhance the access request submission method to auto default validity dates of FF ID to different dates not to conflict with existing ACTIVE assignment

Manual Checks

- Give EAM request submission to only authorized requestors who can manually verify if the FF ID has active assignments before requesting for assignment of a FF ID to a user

- EAM Owners to verify if the FF ID has active assignments before approving the request and also can change validity dates of FF ID assignment before approval

Regards,

Madhu

[former_member205095]

HI Madhu,

yes I know when the users call GRAC_EAM, it will appear that the user is already in use, but it can be a problem because, in this situation the FF USer, needs to wait, the another FF user to user the FF ID.

So we want that if the the user is already in user, the requester could request another one

Arivind

[RameshVithanala]

Hi Arivind,

You could also use the message to the Firefighter from the EAM cockpit.

Thanks

Ramesh

[madhusap]

Hi Arivind,

Generally FF ID already has standard functionality where concurrent use of FF ID is not allowed. So, even if the same FF ID is assigned to multiple users, only one user can login and concurrent usage is not allowed.

Do you have any specific requirement or business justification to have this restriction at ARM side?

Regards,

Madhu