I am not completely convinced because it works in the VMware lab environment with the HTML5 client. I believe one of the others in this thread was also using the HTML5 client and it worked for them.
It "works" in some situations and creates compatibility issues for things like XaaS. That feature is a 1.0 feature, which means it's going to be buggy and incomplete. It's best to continue using the legacy client until things stabilize. My advice is to not even touch the HTML5 client in 7.6.
The problem is we adopted the HTML5 client 2 months ago and have created several newer workflows since. In fact, the Java client has a warning on the current workflow stating "this workflow can be edited only in the web-client as it has newer format." Everything about the workflow is greyed out in the Java client and it will not let me copy it.
So yes, this is one of the side effects of adopting the HTML5 client, hence my advice of not using it.
The regular expression of “.su$” does work on another field, but does not work on the field I am working on, leading to my conclusion it is because the field is an Active Directory lookup.
I created a new Active Directory policy with the sub-OU of the SU accounts that points to our existing AD endpoint.
I think the next step may be to try adding the configuration to a Blueprint in VRA or in VRO try adjusting the workflow input parameter. Everything I am reading so far talks about placing a new machine in a specific OU with VRA done at the vSphere portion of the blueprint, and is not available in the portion I am working which appears to be a VRO section of the blueprint. So at this point, we might have to get rid of the AD drop down and let them type in manually and force the SU at the end that way.