Workflow - Action - Function Evaluator: List of attributes

All replies

• 

  

  0

  Sign in to vote

  Sachin,

   

  The list of attributes for destination is based on what the destination is. If this is inbound sync rule, then the destination is the Metaverse. If this is outbound sync rule, the destination is what attributes are in the schema of the connected directory. i.e. AD, SQL, text file, etc......

  • Marked as answer by Markus VilcinskasMicrosoft employee Saturday, September 4, 2010 9:28 PM

  Tuesday, August 17, 2010 2:11 AM
• 

  

  0

  Sign in to vote

  Thanks Glenn for the reply. Here is the scenario...

  On "Create Workflow" page,

  1. "Workflow Type" as "Action"

  2. "Activity Picker" as "Function Evaluator"

  3. Click "Select"

  4. Click "Lookup"

  5. Workflow Parameter as "Target"

  6. Parameter Attribute: <drop down>  -> How is this list populated? I have not specified any sync rule type or object type

  7. Under "Value"/"Name" <Please select an item> -> How is this list populated? I have not specified any sync rule type or object type

  TIA

  Sachin

  Tuesday, August 17, 2010 8:24 AM
• 

  

  0

  Sign in to vote

  Sachin,

   

  I looked at my environment, this list is determined by the schema of the FIM portal. I made a new attribute, called Delegate, and created binding for this attribute to person object. When I go to workflow and select function evaluator and choose 'Target' for Workflow Parameter, I now have 'Delegate' available for Workflow Attribute. I also notice that the list includes attributes for multiple object types, including group.

  Wednesday, August 18, 2010 2:02 AM
• 

  

  0

  Sign in to vote

  Thanks Glenn for the reply.

  I noticed that only those attributes which are bound to the existing resource types are available for the workflow attribute.

  However, if you create a new attribute and bind it to the new custom resource type then it is not availabe.

  - Sachin

  Wednesday, August 18, 2010 8:38 AM
• 

  

  2

  Sign in to vote

  After some more research, this looks like it could be a known problem. I was able to work around this by adding the custom attribute that I want to view to existing resource type. I chose person. After doing this, I ran IISRESET on portal, now the attribute is available in dropdown list.

   

  • Marked as answer by Markus VilcinskasMicrosoft employee Saturday, September 4, 2010 9:28 PM

  Thursday, August 19, 2010 4:09 AM
• 

  

  0

  Sign in to vote

  I have a custom attribute attached to a New Resource, and I wish to send email to that distribuition group in the attribute, I am trying to do this in a approval activity

  Can I set the target as \\target\custom_attribute and where I can allow it happen? It must be create a MPR or some kind of filter like for \\target\owner?

   

  ---

  Lucas Marques Identity and Access Management http://lucasmarquesit.blogspot.com/

  Friday, November 19, 2010 5:26 PM
• 

  

  0

  Sign in to vote

  Have you found a solution to this problem Lucas? This is exactly what I am attempting to do!

  Friday, March 25, 2011 8:39 PM
• 

  

  1

  Sign in to vote

  Jerry,

  I was able to find one more way around this issue (other than binding the custom attribute to another resource).  If you select the CustomExpression option, you can simply type in the attribute you wish to access.  For example: [//Target/MyCustomExpression].  You can check out my blog post at http://www.apollojack.com/2011/05/custom-attributes-in-function-evaluator.html for more information.

  Thursday, May 26, 2011 12:22 AM