Resource Attributes not saving in Queriable User Extended Attributes

Howdy,

I added a few queriable user extended attributes to IDM. I originally added them in through the configure user attributes interface. I then edited the UserUIConfig to specify that they were queryable. I then edited the User Search Defaults form's getSearchableAttrs function to include these attributes. My added attributes now show up in the search user form, etc., just like I expected them to. Next I configured a new resource adapter for a database table that contained some values I wanted to use to populate these queriable attributes. I wrote a correlation rule, and ran reconciliation on the new resource. It matched up the account entries and automatically matched and linked the account information. So far so good. However, the user extended attributes I defined are not getting populated with the data from the new resource. The mapped resource attributes are treated as part of the user view, but only under the given resource, not as a queriable attribute. I really want to be able to use the find user interface with these datafields. Does anyone know why my data is ot making it into the queriable fields? Do I need to write another rule or workflow? Any advice would be most helpful.

Thanks!

Jim

[1245 byte] By [JimBeard] at [2007-11-26 9:39:57]
# 1

Queryable attributes refer to attributes stored in the IDM user object, and so need to be referenced as such.

If you want attribute 'foo' in resource 'bar' to be stored as a Queryable attribute, you need to define it like so in your User Form :

<Field name='accounts[Lighthouse].foo'>

<Expansion>

<ref>accounts[bar].foo</ref>

</Expansion>

</Field>

This should pull the value from the resource attribute and put it in the IDM attribute. If you refer to it as a global.foo everywhere, that might work (but I find globals to be problematic).

Let me know if it works...

Jason

jsallee at 2007-7-7 0:36:29 > top of Java-index,Web & Directory Servers,Directory Servers...
# 2
Which form do you mean when you say User Form? Default User Form? End User Form? I have a difficult time understanding which repository object map to what. I know there is no 'User Form' object in the repository.
JimBeard at 2007-7-7 0:36:29 > top of Java-index,Web & Directory Servers,Directory Servers...
# 3

So I can see how I can bring up the correct value in a field. And it would likely save in the field if I clicked the save action on an edit user form. However, I want this field (and a few others like it) to be saved during the reconciliation or active sync event. I need to be able to search on all accounts, and I don't want to have to hit save after each account is reconcilled. How do I go about this?

JimBeard at 2007-7-7 0:36:29 > top of Java-index,Web & Directory Servers,Directory Servers...
# 4

Add the fields to the Default User Form (probably Tabbed User Form) for administrators to be able to set these values.

The ActiveSync resource allows you to specify a form to use and/or a proxy administrator to run as. If you are setting these values, then the ActiveSync form and the form that the proxy administrator uses (which may be the Default) need these fields set.

The ActiveSync process will process the form settings when it checks out the user view. You won't have to save each user, it will be done by the ActiveSync poll.

Jason

jsallee at 2007-7-7 0:36:29 > top of Java-index,Web & Directory Servers,Directory Servers...