In CaliberRM you can create User Defined Attributes (UDA) of various types. For example if you create a UDA of type List as follows, note that there are four possible values:
In order to map this UDA to SCTM you may create a custom requirement property of type List:
Under the Requirements Management Integration section of SCTM you can then setup the mapping between the UDA in CaliberRM (called "TestUDA2") and the custom requirement property in SCTM (called "Test_UDA_SCTM"):
If you then Synchronize your requirements you will notice that the mapping does not work as you would expect and no value is passed over.
The reason for this issue is that the value you have set for the UDA in a partcular requirement is not available in the list of values that can be used in the custom requirement property in SCTM. In this example the UDA in CaliberRM has possible values of one, two, three and four. However the custom requirement property in SCTM only has the available values of one, two and three. The mapping is not able to pass any differences in the list of available values from CaliberRM into SCTM.
Therefore if you must use a custom requirement property of type List in SCTM the list of available values must match exactly.
However the best way to set this up is to create a custom requirement property of type Text in SCTM instead.
Then if you map this to the UDA in CaliberRM the value will be passed over correctly.
The added benefit of using a custom requirement property of type Text instead of a List in SCTM is that you only have to maintain the available list values in CaliberRM and not in SCTM.