I've created a new boolean attribute and bound it to the user. I've also created two sets which both use the new attribute to determine membership, one for true and one for false. By default the attribute does not appear to be either true or false. Once I change the attribute, the user appears in the set memberships as required. Can anyone shed some light on what is occurring here? I was expecting a default value of false. Do I need to use an Function evaluator workflow to populate this value to a default of False? Thanks, Matthew

yes, you have to. any boolean attribute in FIM and in MIIS/ILM connector space can be either true or false and also may be non-existent. I mean your object will not have this attribute listed at all. in FIM RCDC form for user you can set default value and it will work for objects created from the Portal. but for objects came from MV and created under SyncEngine account you'll have to have a WF which will set default user properties. for default values in RCDC see what I have for object create: - <my:Control my:Name="BACCategory" my:TypeName="UocDropDownList" my:Caption="{Binding Source=schema, Path=BACCategory.DisplayName}" my:Description="{Binding Source=schema, Path=BACCategory.Description}" my:RightsLevel="{Binding Source=rights, Path=BACCategory}"> - <my:Options> <my:Option my:Value="2" my:Caption="Application" /> </my:Options> - <my:Properties> <my:Property my:Name="ReadOnly" my:Value="false" /> <my:Property my:Name="Required" my:Value="true" /> <my:Property my:Name="ValuePath" my:Value="Value" /> <my:Property my:Name="CaptionPath" my:Value="Caption" /> <my:Property my:Name="HintPath" my:Value="Hint" /> <my:Property my:Name="ItemSource" my:Value="Custom" /> <my:Property my:Name="SelectedValue" my:Value="{Binding Source=object,Path=BACCategory, Mode=TwoWay}" /> </my:Properties> </my:Control> - <my:Control my:Name="BACStatus" my:TypeName="UocCheckBox" my:Visible="false" my:Caption="{Binding Source=schema, Path=BACStatus.DisplayName}" my:Description="{Binding Source=schema, Path=BACStatus.Description}" my:RightsLevel="{Binding Source=rights, Path=BACStatus}"> - <my:Properties> <my:Property my:Name="ReadOnly" my:Value="false" /> <my:Property my:Name="Checked" my:Value="{Binding Source=object, Path=BACStatus, Mode=TwoWay}" /> <my:Property my:Name="DefaultValue" my:Value="false" /> <my:Property my:Name="Text" my:Value="Disabled" /> <my:Property my:Name="Hint" my:Value="{Binding Source=schema, Path=BACStatus.Hint}" /> </my:Properties> </my:Control>

Yes, by default attribute values have no value. You need to set them. This includes Boolean. If you expose the Boolean attribute in a control within the RCDC then by not checking it it will be false at the end, however if you do not implement a control then the only way to initialise the value is to set it in an action WF, e.g. using the FE as you state. Note you can capture the uninitialised state in a set (or just XPath) by looking for all objects that don't have that value set to true or false.

The other option that I was told to use when I was on connect was to simply create a not set. In the case of the groups, I have a set that looks for true and another set that looks for values that are "not true". This seems to give me what I require for the time being. Thanks. B

yep, it will work for Sets, but that attribute value will not flow to MV. in my scenario it has to be there, but "not true" approach is more simple, agree.

In cases where I have needed to have the data flow back to the metaverse, I have created a set of "not true" and "not false" so that I know the value isn't set. This then is used to kick off the MPR which will fire the workflow to set the value to false. :) Its a bit convoluted but it works. B