updating user extended attribute
Hi All,
I need to update a user extended attribute. I have added the attribute (date) in config objects, UI config and in defalut tabbed user form.
I used checkout view and checkin view, but i am unable to update the value.
<Action id='1' application='com.waveset.session.WorkflowServices'>
<Argument name='op' value='checkoutView'/>
<Argument name='type' value='User'/>
<Argument name='id' value='$(accountId)'/>
</Action>
<Action id='2'>
<expression>
<block name='updatedate' trace='true'>
<set name='user.global.Date'>
<s>12/21/2007</s>
</set>
<ref>user.global.Date</ref>
</block>
</expression>
</Action>
<Action id='3' application='com.waveset.session.WorkflowServices'>
<Argument name='op' value='checkinView'/>
<Argument name='view' value='user'/>
</Action>
<Action id='4'>
<expression>
<block name='testdate' trace='true'>
<ref>user.accounts[Lighthouse].Date</ref>
</block>
</expression>
</Action>
i tried with global and accounts[Lighthouse], but no use.
To update user extended attr checkout view is the right way or i need to use checkout object.
if anybody knows, please do reply back.
thanks in advance
# 2
I agree with chits98. It seems that there is something that is preventing this from happenning. Holistically, the code seems to be right.
Check the user view in BPE. Since this is a user.global namespace attribute, you should be able to update in BPE. If you can update this in BPE, check for other attributes update process using the WF.
If it works for other process, it should work for date also, unless there is some internal conflict suggested by chits98.
# 3
Thanks for the reply.
actually it's not about date, i tried anothter attr managerId but that is also not working.
may be i am doing wrong while defining the user exteneded attr.
i did as follows
1. defined the attr in config user extended attrs
2. defiined under queryable attrs in UI Config
3. defined in default tabbed user form.
can anybody please tell me how can i define a user extended attr.
thanks in advance
# 4
User Extended Attributes is the important one. You should be able to add it and restart the instance to start using it. The User UI Config change is needed if you plan on searching on this attribute.
What version of IDM are you using? I think 6.0 does things a little differently.
Are you able to view the fields in the form if you edit the user? If so, this is a good sign that the problem lies with the workflow itself, not the attribute definition. Try both the global.* and accounts[Lighthouse].* references in the form.
# 5
I am using waveset 5.5.
I managed to update the exteneded attribute, but there is a peculiar behavior.
i defined an attribute startdate, but when i opened the user object, the attribute which i have defined is not appearing in the user object. why is it so.
then for my convienience i have added the attribute in user object and tried to update that attribute. i am able to update the startdate attr for that particular user. if it is the case, fo how many users i can hard code the attribute.
i don't know where i am going wrong.
my ques is why i am not able to see the extended attribute startdate(which i have defined in configuration objectsuser extended attributes ) in the user object.
please give some feedback
thanks
# 6
Adding an attribute to the User Extended Attribute list does not mean that users will have the attribute defined for them when you check them out. The field needs to be added to your user forms so that it can be set in the view.
To populate the attribute for every user you would need to either checkout every user and check them in (assuming the form can calculate the value and set it), write a bulk action CSV list that lists out the users and the startdate, or write a script/program to edit the raw XML of all the users to set the value and then import them back into IDM.
It's possible that reconciliation could be used to do this, too.
Jason
