FIM2010-Using Custom Objects and Attributes in Out of Box FIM Approval Activities

I was working in the approvals arena today and was looking at how the activity calculates the list of attributes that are provided to the end user as part of “[//Target]. It would appear that the system parses out the attributes from the “User” and “Group” objects only for this list.

In my environment I have a custom object with a variety of attributes. If I go to validate the “[//Target/CustomAttribute]” in the out of box approval activity it won’t allow me to use it. This is due to where the activity is looking for the list of reference attributes to use as allowable from the target.

The workaround for this is to add the custom attributes to the “Group” or “User” object. Remember they have to be defined as reference attribute types as the need to be resolved back to a list of objects for the approval. Once added to the Group/User object, the custom attributes will be listed in the allowed attributes for “Target” when you do a lookup or do a validation on a manually typed string of ‘[//Target/CustomAttribute]’. Once configured, the target resource type is not constrained and any custom object (or out of the box one for that matter) can be used.

I did look around to see if I could find a configuration setting for what objects the approval would parse to get its list of attributes but I didn’t find anything. If someone has found a configuration setting for this, please let me know as I would love to have this completed more elegantly.

This entry was posted in Forefront Identity Manager 2010. Bookmark the permalink.

2 Responses to FIM2010-Using Custom Objects and Attributes in Out of Box FIM Approval Activities

  1. Jason Cowell says:


    Did you have any more thoughts on this? I ‘think’ i’m having a similar problem…
    I want to use the custom attributes that i’ve added to the user object to define criteria for group membership but when i click ‘select attribute’ to build the query the custom attributes are not in the list.
    I’d be grateful for any insights…


    • Hi There,

      I’ve generally seen this when I’ve not selected the proper object type, in this case user (changed it from the default all resources).

      Don’t forget to make sure that they attributes are also in the “Administrative Filter” as well so it can be used in the searches.



Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s