I am not sure if this is a possible bug or if I should make it a feature request.

Has anyone been able to choose "Find user by:" using a custom attribute if the workflow was built BEFORE the custom attribute was added?

To explain in a little more detail, I have a number of workflows already built that have the find user activity and I find the user by email (connecting to Active Directory).  We found an issue with our AD where when a person changes their name, their email does not always change. For example Sally Sample has the email of sample.sally@workplace.com, then she changes her name to Sally Johnson.  Active Directory still shows the email attribute as sample.sally@workplace.com.

So when people fill out a form and put the email address of johnson.sally@workplace.com, it gets passed to workflow where my Find User activity fails because AD still has sample.sally@workplace.com.

We found a way around that by adding the proxyEmail attribute to the customer properties in workflow admin console.

Now I would like to work on going back to old workflows and changing all the find user activities to look by proxyEmail instead of email.  However, the old workflows won't let me use that attribute unless I delete the exiting find user activity and add a new one back in.  Which is more work than I would like to do.

Some workflows don't show the new custom attribute at all.  Some workflows show the attribute and initially let me pick it but as soon as I click off the activity it deletes the property.

In the shot below, #1 is one of my activities that was built prior to adding the customer attribute and it shows the ProxyEmail choice.  #2 shows the what the options box looks like after I choose it from the list.  But then I click off the activity and when I go back to it, I see #3 where it no longer shows that I chose the new custom attribute.

If I add in a new find user activity to the workflow and pick the ProxyEmail, it works just fine.

I am working in Workflow 10.2.0.216.