(imported comment written by SystemAdmin)
Due to the fact you’re trying to parse something that could have a wide variety of permutations, this might be a bit awkward to try to do directly as a single, dynamic relevance, but generally it is achieveable.
First thing is, when dealing with clients, forget about your Properties. Retrieved and Analysis properties exist as part of the console and not something your clients know about. Therefore, you must take the relevance that you use in your custom property and use it as part of your dynamic relevance.
Secondly, you might need to construct the relevance to create the entire output string, rather than try to combine a relevance command and the additional elements. (This might not be a problem, but I certainly find it a bit more straightforward/cleaner to just create the output in the relevance.)
Lastly, although it might be a bit ‘ugly’, your relays and client couldn’t care less what the seek list keywords are going to be, so if you can avoid having to do a conversion (if x then a else if y then a else if z then b else c), I would do so. Thus the keywords would end up being the data pulled from the AD string (x, y and z) rather than your preferred keywords (a, b or c).
You can set up your relays to allow multiple types of AD OU elements, as they will still match even if they are far down the list. So a relay that might handle a chunk of OU types, might have an affiliation list of "x;y;z;static;
" and another one might be "q;r;s;t;u;v;w;x;static;
", assuming that clients with ‘x’ can land on either one.
So, to get the output, you would have something like the following relevance and use {} to wrap around it when you place it in the seek list (Note: be aware there is a legacy length limit which may still exist):
{ (it &";static value;catch all;*") of (relevance to pull the AD OU data) }
Worst case, if your AD relevance is too complex, you can have a task that will create a setting on the client (based on AD OU and adding in the static and catchall values) and then use a simple relevance to pull out the setting in the dynamic relevance for the field.
-Jim