Hello, In our instance of FIM portal there are object types of “FAccount” as well as “User”. Each “FAccount” object contains an attribute called “fAccountOwner”, the attribute is a reference to “User” type object. In outbound synchronization rule responsible for “FAccount” object synchronization i try to use 3 workflow parameters which would contain values of specific attributes of “fAccountOwner” set for given “FAccount”. Steps I’ve made in order to create those 3 WFW parameters: - In the Synchronization Rule triggered by the Worflow in “Workflow Parameters” tab parameters has been added: Example: Name: Data Type: FirstNameOwner String - In the Synchronization Rule triggered by the Workflow in OutBound Attribute Flow a flow has been added: Example: $FirstNameOwner=>extensionAttribute15 - In the WFW which triggers the synchronization rule values of Parameters has been set Example: FirstNameOwner(String): [//Target/fAccountOwner/FirstName] The problem is that those attributes are not set. In the Synchronization Engine I can not see parameters added into EREs SynchronizationRuleData attribute, no actions regarding “extensionAttribute15” takes place during the synchronization cycle. What makes it even more peculiar is a fact that there already is other WFW parameter included in the same WFW/SR, doing basically the same thing only with different attribute of the “fAccountOwner” object – this works (parameter is included in the ERE it is also correctly synchronized). The parameter was not included there by me so I am not aware of details of implementation. However, I would guess that this implies that the environment (MPR/SET/WFW/SR) is configured correctly. Could anyone please advice what I’ve missed, what could be the problem?

Your configuration looks sound. Assuming this is a lab, try the following: If your WF is fired by a set transition MPR: Open the WF definition and enable Run on Policy Update. Submit. Disable the MPR. Enable the MPR. If your WF is not fired by a set transition MPR, you need to re-fire the rule. Do this. Report back if all values are in the ERE as expected. Obviously, your test candidate requires the necessary reference to the FAccount and the referenced FAccount requires valid values.