AC 10 Evaluation - Request Screens & Emails

[Former Member]

Hi Everybody

as part of an evaluation on AC10 the following two questions came up. The two areas are currently a problem with 5.3. and the question is if AC10 can solve the issues?

So here we come:

1) System-specific request screens:

I am aware that AC10 provides more flexibility on request screens.

The scenario is, that users are provisioned to many systems, and some systems require more or less fields than other systems. Can request screens be created for specific systems, and depending on the selected system, the "system-specific" fields appear? E.g. for the BW System only firstname, lastname, username, email is required... but for the ECC System a lot more fields...

2) Email after auto-provisioning:

In general, after auto provisioning is done, the email is sent to the user. This is how it is configured in 5.3. and it works. However, for one specific system, there is an additional field maintained by the security team before the user can actually log on to the system. Therefore, the auto-provisioning email is not really helpful, since the user is informed too early.

Is there a way to configure AC 10 in the way, that the auto-provisioning email is only send for certain systems?

Thank you very much for any clarifications? I would really like to understand if AC10 can do this and how this is done?

Your input is much appreciated!

Mo

[Former Member]

HI,

Your both issues are resolved in GRC AC10.0.

You can maintain the EUP ID system/connector specific in GRC AC 10.0 by going to SPROIMG> GRC-->Access Control --> User Provisioning --> End user Personalization. Assign the same in MSMP workflow.

Second problem or email ca also be resolved using the BRF+ (Business Rule Framework). You have to create a BRF rule and decison tree with filter criteria as connector name.

Hope this will solve your problems.

Ragards

Rajan Arora