and more in a single search tool across platforms. Read the announcement here. |
07/11/2022 10:37 AM
Hi Team ,
I wanted to know if we can check for duplicity check with non mandatory attribute in AD like employeeID ?
I tried Check for unique parameter from AD connector guide but it didn’t help .
I added something like EmployeeID: ${user.username)
please help if any suggestion on same .
thanks
Ankit Jain
07/12/2022 12:21 AM
Hi @Ankyt19 ,
The AD connector has a CHECKFORUNIQUE field to achieve this. Please go through the AD Connector guide to know more of its features :
https://saviynt.freshdesk.com/support/solutions/articles/43000615764-active-directory-ad-connector-g...
07/13/2022 10:16 AM
Hi @sahajranajee ,
IT is not working . Expectation was to have task in pending task if there is any duplicity on employeeID .
I added below syntax : EmployeeID: ${user.username)
but with duplicate employee ID or any other attribute in AD it created the account .
note : DN, sAMAccountName, UPN works fine OOTB . And we get error in pending task saying entry already exists .
07/13/2022 10:21 AM
Hi @Ankyt19 ,
I am still unclear on your requirement. What do you mean by "Expectation was to have task in pending task if there is any duplicity on employeeID" ?
Do you want the task to not provision if a duplicate is found?
07/13/2022 10:31 PM
Yes @sahajranajee , it should not provision the account rather it should be there in pending task ( as duplicity found ) .
08/25/2022 11:33 AM
Hi @sahajranajee @any update here. ?
08/25/2022 01:40 PM
"employeeid":"${user.emplopyeeid}"
08/28/2022 11:16 PM
@Ankyt19 ,
CHECKFORUNIQUE will help you send a different value if a duplicate is found from the data present in Saviynt , similar to an account name rule.
But if a task is created, it will get provisioned, unless a restriction is available for the attribute on your target.
08/29/2022 04:57 AM
Yes @sahajranajee and @rushikeshvartak . I agree CHEQUEFORUNIQUE is used to check for duplicity and change it to make it unique . Do we have any option to check for uniqueness on employeeID , So that even if duplicity found ,take no action rather just put that in pending task saying entry exists ?
Thanks
Ankit
08/29/2022 05:01 AM
Hi @Ankyt19 ,
Do we have any option to check for uniqueness on employeeID --> Yes, CHECKFORUNIQUE conditions can be set for any attribute and can be later referenced in the provisioning JSONs.
So that even if duplicity found ,take no action rather just put that in pending task saying entry exists ?
--> No, if duplicity is found in checkforunique, it moves to the next rule setup there and uses the value. it cannot act as a negation for the task to not provision. This has to be a restriction at the target.
09/15/2022 12:16 PM
Yes @sahajranajee . We could have handled in Saviynt . CHECKFORUNIQUE acts as function 🙂
Anyway I got my answer .Thank you so much