Forgive me if I have missed this but I have a generate uniqueness problem
I have written a few powershell scripts that run using a Portal Powershell WF Activity.. one creates a "file and URL safe SHA token" bla bla all good
I have written a script that tries to generate a unique attribute in the Portal using first middle third preferred and lastname and i=+1 do until loop at the end bla bla
BUT my testingthat imports, sync's and exports to FIMMA 10 identical first middle third preferred and lastname identities (good test huh !) fails uniqueness generation.
Well the PS script fires and checks the derived name from the script login is "not in AD" OR "not in Porta"l BUT at the time the first 'n' WF fire in parallel a match was not found in AD or Portal. Consequently all 'n' WF try and DO populate the same value to the destination attr.
The unique but duplicate attribute occurs because the 10 identites cause an un-anticiapted duplicate becasue they all fire their WF in sequence but run in parallel at the same time. If these 10 were spilt over time or over sequence (meaning if they occured somewhere in a stream of 1500 identites that fire the same WF then I might never generate a duplicate)
I have enforced unique validation for create and edit user objects for this attribute in RCDC and then worked out this XPATH check only applies FROM the portal not a WF that hits the FIM :5725
I have some ideas to minmise the possible duplication but wondered how I can enforce uniqueness when the attribute neither exists in AD nor the Portal but another WF is queued to used the same value.
Hope thi smakes sense
Any ideas please ?
TIA
Nigel