Workflow Attribute Namespace?

Question

How would I compare a waveset attribute with the attribute being modified from the Tabbed User Form?
ex)
<Transition to="Rename Activity">
<cond>
<neq>
<ref>waveset.EXT_ATTRIBUTE</ref>
<ref> EXT_ATTRIBUTE being updated in UpdateUser WORKFLOW</ref>
</neq>
</cond>
</Transition>
<Transition to="DoNotUnlock"/>
Thanks                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               

Answer 1

You can check for renames by comparing like this:
<neq>
    <ref>user.accounts[Lighthouse].netlinkID</ref>
    <ref>user.waveset.attributes.netlinkID</ref>
</neq>    A problem is that if the rename of a resource account fails for some reason, the workflow won't try it again the next time.
A more effective approach that I use to check for renames with LDAP and AD is this:
<and>
    <ref>user.accountInfo.accounts[LDAP].created</ref>
    <not>
        <invoke name='endsWith'>
            <new class='javax.naming.ldap.LdapName'>
                <ref>user.accountInfo.accounts[LDAP].accountId</ref>
            </new>
            <list>
                <new class='javax.naming.ldap.Rdn'>
                    <s>uid</s>
                    <ref>user.global.netlinkID</ref>
                </new>
            </list>
        </invoke>
    </not>
</and>It is clumsy in that I have to construct the RDN and compare it to the resource account. I have to do this for both LDAP and AD.
It does work reliably, though.