Hi Everyone,
I have a requirement where I have to create accounts in NERM using workflow.When a form is submitted it triggers a workflow .Then I have used a HTTP api operations to create a account in NERM,here we need to have unique identifier in a sequential order like HAID1,HAID2 .For example if the latest account created in NERM is HAID23 then when workflow is trigger then the unique identifier has to be HAID24.Is it possible to do in workflow or is there any other ways to implement it so that NERM identities has a unique UID in a sequential order.
Thanks!!
I would use the ISC for creating the unique user name for the user instead of NERM.
From NERM, i would just create an attribute which should be unique (using standard attribute validation ) and then once this account is aggregated into ISC, then you can use attribute generator rule to generate the unique user id field and write back to NERM using attribute sync.
I hope the information helps.
Regards
Vikas.
1 Like
We have to get the latest created account from source and the new identity id has to be latest id +1 eg:AHUID2 and AHUID3 using identity attribute generator rule.
Yes that would be the idea. So it will follow the same approach as we do for other authoritative sources where user id is not generated at the source level but once the identity is received by ISC, then ISC generates a unique value while trying to create an account in AD or some other system.
Here you can have the attribute generation rule in place and make this user name field as searchable from all the sources which could have a duplicated value (other auth sources etc) for this attribute and then in the rule you can generate the new value in a way that it is always unique.
NOTE: - for the initial load of the users in NERM, then you will have to make sure that already existing users have this attribute value uniquely updated for all the identities so that ISC can control the newer user id generation and write back to NERM for this identity.
Once you have written it back to NERM then it will be available in ISC’s aggregated objects too and thus next time which can help in generating the unique attribute value.
I hope this helps. 
Good luck with the implementation. If any questions, please let us know.
Regards
Vikas.
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.