Calculated values code for WI attributes in RTC 3.0 M6a
Hi,
I am working with the new milestone RTC 3.0 M6a and I would like to add some custom code to a work item field attribute but all the new fields that appear in the new release for this new functionality when I add a WI custom attribute are not enabled (Default Value, Calculated Value, Value Set, Validators...). How can I enable this functionality and add some custom code to validate or calculate a WI attribute? Is there any documentation available I can take a look at to know how this new functionality works in last milestone?. Many thanks, ana |
5 answers
I am working with the new milestone RTC 3.0 M6a and I would like to add You have to go to the 'Attribute Customization' section in the Process Spec Editor. There you can define new default values, dependent attributes etc. -- Regards, Patrick Jazz Work Item Team |
Hi
Apologies this is probably a daft question... Where do you actually enter the script for a calculated value ? And even better is there an example somewhere ? It just advises me to update the process source... I'm using beta1 Steve I am working with the new milestone RTC 3.0 M6a and I would like to add You have to go to the 'Attribute Customization' section in the Process Spec Editor. There you can define new default values, dependent attributes etc. -- Regards, Patrick Jazz Work Item Team |
why is there no help ready for those new features???
It really takes many effort to study. |
With RC1 the way to set up dependent enums is:
1. Create source enum 2. create target enum 3. In Attribute Customisation node create a new "Dependent Enumarations" value set, setting values to be shown in the "Configuration Section 4. Add a new customAttribute for source 5. Add a new custom attribute for target, specifying the dependent value set created in step 3 as it's "Value Set" and specifying the attribute created in source in the Dependencies list. Sound right? On 30/06/2010 6:34 PM, Patrick Streule wrote:
|
With RC1 the way to set up dependent enums is:
Here is an example how to create dependent enumerations: Let say that you have attribute Pick2 which depends on choise of attribute Pick1. For example, if you choose Pick1 literal.l1, on Pick2 attribute only literals l2,l4,l5 are available for choose and if you choose Pick1 literal.l2, on Pick2 attribute only literals l3,l6 are available for choose. You must write next source code at configuration source of specific project area: <valueSetProvider> <filterMap> <value> <literal> <literal> <literal> </value> <value> <literal> <literal> </value> </filterMap> </valueSetProvider> Then, you must find the <attributeDfinitions> tab, and add next: <attributeDefinition> <dependsOn> <valueSetProvider> <filterAttribute> </valueSetProvider> </attributeDefinition> That should work. |
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.