Reference Attribute in Work flow
How I can use the Reference attributes in portal work flow if the ref. attribute is pointing to a different object (not person).
I'm using FIM 2010
November 3rd, 2010 8:12am
Hello,
It's hard to answer this whithout more details, even if I figure what you means the correct answers will difere depending what you need to do
Could you be more precise on what kind of WF Activity you want to fire, and in wich case ?
It's possible that what you want to do is only answered by a Custom Workflow Activity
Fabrice
Free Windows Admin Tool Kit Click here and download it now
November 3rd, 2010 9:09am
I have one source data that supplies user name, another source data supply department, both sources are connected through ref. attribute, I want to populate the users with department names. is it possible?
November 4th, 2010 1:01am
You can do with plain function evaluator: use a custom expression, something like [//Target/DepartementRef/DisplayName].
Free Windows Admin Tool Kit Click here and download it now
November 4th, 2010 3:50am
Thank you, but there is nothing in the previous experssion that points to the second data source?
suppose I have a workflow that create user in AD, thus target is user, will this experssion work?
[department/[//target/departementRef]/displayname]
November 4th, 2010 4:28am
What I don't understand if is user objects in the FIM database already have a reference to their department. In such a case the function evaluator should be applied to users objects. In case you don't already have such a reference, then the problem is to
build such reference, which can be done in more ways.
Free Windows Admin Tool Kit Click here and download it now
November 4th, 2010 5:56am
I have two objects in Portal, object user, and object department, the user object has a reference to department object, I need a way to use this reference attribute to fill the user department field in AD.
November 4th, 2010 5:59am
the problem with this expression //Target/DepartementRef/DisplayName] is that FIM portal will understand the target of DperatmentRef as another user, that is why I suggest another expression.
if I create a work flow the acts on department object as source or requester, and the target is user creation, will this expression work?
[department/[//target/departementRef]/displayname]
Free Windows Admin Tool Kit Click here and download it now
November 5th, 2010 6:03am