I have a UDA that I am using to make LDAP calls to collect display names of users not in SharePoint profiles yet. After changing the password for the account used for the LDAP connection errors began being produced regarding the parsing of the Domain\Username in a regular expression.
This regular expression previously worked so I am puzzled. To eliminate this error I disabled all of the regular expression functionality and the LDAP calls which would create blanks in my e-mail notifications when users are not in SharePoint. However, all the workflows that used this UDA continue to produce the same error "Failed to run User Defined Action. parsing "\" - Illegal \ at end of pattern". I altered the notification at the end of the UDA that notifies me when it has been processed and published.
Now when this notification comes through it is not the altered one that I just published and the errors are still being produced even though the workflows that are calling the UDA are started after the publish (Which I would expect for it to be calling the new UDA).
Do I need to recreate the connection to the UDA on all the workflows that use it each time the UDA is altered in this manner?
If so, I would consider this a bug as I would expect the UDA to have the same GUID when an alteration is performed instead of a delete and new.
Any ideas?
Clarizion