Here my requirement is to disable only EMP account not provider account for EPIC application. I am looking best possible solution for this use case.
Thanks.
Here my requirement is to disable only EMP account not provider account for EPIC application. I am looking best possible solution for this use case.
Thanks.
@Ankit_002 , We have followed up on changing the operation (Disable/Modify) depending on whether it is a provider (classified by NPI or another identifier) or a non-provider in the connector rule in provisioning operations.
Thanks,
Siva Lankapalli
Thanks Siva. We need to use a before-provisioning rule to check if the identity is a provider identity, and if so, change the operation from ‘disable’ to ‘modify’." Is this correct?
Is there another way to achieve this without using a rule?
I’m uncertain about the other approach at the moment. We will need to explore it further.
Are you talking about EMP or SER? For SER you never want to disable records.
Here I am working on EMP account and same we are trying to disable on user termination. Via before provisioning I am able to achieve this.
You use two different connectors. EMP is independent of SER in this case. Can you edit the Source and remove the DISABLE functionality there? Wonder if that would suffice?
The way we handled this was to include the Epic EMP in the inactive life cycle state to disable the account within the Identity Profile. While excluding the Epic SER from this configuration.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.