I have created an custon attributre in RCDC and assigned a constant value it. I have a requirement that the attribute have to be made hidden and still the value should be synchronized to MV as i have a given a flow from FIM to MV. Can anyone help on this.?

If you make sure no users are granted access to this attribute through an MPR, it should not appear on the RCDC the user is viewing. So I would advise to avoid granting users full access to certain objects as this will make it hard to enforce the above.http://setspn.blogspot.com

Further to Thomas' comments above, a way which you may want to consider using to populate the FIM attribute value is the Function Evaluator ... which (if the FIM Sync Engine has the necessary rights) will allow you to set up a constant flow directly into the FIM User attribute (presuming this is the user object here) rather than trying to associate this with the RCDC (which should only ever serve to accept user-supplied values anyhow). In other words, define a step in the workflow which precedes the OUT-BOUND Sync Rule to write to [//Target/YourCustomAttribute] ... then include this in the outbound flow. I think you will find this works nicely ...Bob Bradley, www.unifysolutions.net (FIMBob?)

But if a constant value set in RCDC cannot be projected in MV? Because i tried projecting the constant value set in RCDC but it is unable to project it.

If I understand your scenario correct: An RCDC is just a way of showing the "attributes" for a given object. There are RCDC's to create, view and edit an object.If you have permissions to change an attribute and set a constant through a given RCDC. Then upon an import + sync towards the Metaverse (running profiles on the FIM MA) this should be projected into the MV. I might be misunderstanding what you mean with "setting a constant in a RCDC". Can you elaborare on how you achieve that?http://setspn.blogspot.com

You cannot default attribute values from an RCDC, other than via a UocDropDownList or a Boolean, i.e. UocCheckBox. This is a known limitation in the current OVC design. As Bob says the way to do this is in action WF. Don't mandate the attribute value in the binding, or even in the RCDC. Instead mandate it via AuthZ and use an Action WF to initialise it. As an example I initialise an Asset resource type when it's created via the Sync Engine. I run several WFs that fire on create Asset resources by FIMMA and then set initial values, e.g. Owner, Enabled, etc. Once the value is set it's good for synchronisation.

You cannot default attribute values from an RCDC, other than via a UocDropDownList or a Boolean, i.e. UocCheckBox. This is a known limitation in the current OVC design. As Bob says the way to do this is in action WF. Don't mandate the attribute value in the binding, or even in the RCDC. Instead mandate it via AuthZ and use an Action WF to initialise it. As an example I initialise an Asset resource type when it's created via the Sync Engine. I run several WFs that fire on create Asset resources by FIMMA and then set initial values, e.g. Owner, Enabled, etc. Once the value is set it's good for synchronisation.

Ah, now I get the question completely. Definately a common question. Would be nice to see someone blogging about this in detail. Perhaps I'll give it a try.http://setspn.blogspot.com

Thank You for all of you for all your suggestions.. I have created a UocDropDownList with defaulting a value to it and i have passed that value to the metaverse by keeing it as a hidden attribute in FIM Portal.