It's all about the answers!

Ask a question

3 extensions we could use


Steve Wittie (1175) | asked Jun 09 '10, 9:38 a.m.
Wondering if these 3 features/functions already exist, or are about to be added by community or product development:

1) allow fields to have numeric editing (in this case we need 1 integer and 1 decimal position (9.9). There is a field type for hours (called duration) that would work for our needs, and is used in the predefined process templates, but is unavailable for use in customization's.
2) drop down lists that are populated based on the choice in another drop down list.
Basically this is - populating enumeration fields dynamically (on the fly) based on another fields value. In this case, the choice in one enumeration will decide the enumeration list of another field.
3) make some fields "read-only" at certain states (matrix). We have the ability to make a field required by state/action. We need the same thing for "read-only" by state/action.

We are trying to avoid having to write these extension ourselves, if they already exist or are about to exist (some one is already working on it). :?: :?:

2 answers



permanent link
Christophe Elek (2.9k12921) | answered Jun 09 '10, 12:08 p.m.
JAZZ DEVELOPER
Wondering if these 3 features/functions already exist, or are about to be added by community or product development:

1) allow fields to have numeric editing (in this case we need 1 integer and 1 decimal position (9.9). There is a field type for hours (called duration) that would work for our needs, and is used in the predefined process templates, but is unavailable for use in customization's.
2) drop down lists that are populated based on the choice in another drop down list.
Basically this is - populating enumeration fields dynamically (on the fly) based on another fields value. In this case, the choice in one enumeration will decide the enumeration list of another field.
3) make some fields "read-only" at certain states (matrix). We have the ability to make a field required by state/action. We need the same thing for "read-only" by state/action.

We are trying to avoid having to write these extension ourselves, if they already exist or are about to exist (some one is already working on it). :?: :?:



Steve, check the following link for customization, I think we can do 2 and 3
I will let Patrick answer the rest :)
https://jazz.net/wiki/bin/view/Main/AttributeValueProviders

permanent link
Patrick Streule (4.9k21) | answered Jun 09 '10, 1:24 p.m.
JAZZ DEVELOPER
Wondering if these 3 features/functions already exist, or are about to be added by community or product development:

1) allow fields to have numeric editing (in this case we need 1 integer and 1 decimal position (9.9). There is a field type for hours (called duration) that would work for our needs, and is used in the predefined process templates, but is unavailable for use in customization's.
2) drop down lists that are populated based on the choice in another drop down list.
Basically this is - populating enumeration fields dynamically (on the fly) based on another fields value. In this case, the choice in one enumeration will decide the enumeration list of another field.
3) make some fields "read-only" at certain states (matrix). We have the ability to make a field required by state/action. We need the same thing for "read-only" by state/action.

We are trying to avoid having to write these extension ourselves, if they already exist or are about to exist (some one is already working on it). :?: :?:



Steve, check the following link for customization, I think we can do 2 and 3
I will let Patrick answer the rest :)
https://jazz.net/wiki/bin/view/Main/AttributeValueProviders


1) We have added support for custom "duration" attributes in 3.0 M6, so this is available.

2) This is also supported since early 3.0 and is partially available in 2.0.0.2 (https://jazz.net/wiki/bin/view/Main/AttributeValueProviders)

3) This is not possible yet. "Implement work item property readonlyIfInState (112816)" would be close, although it asks for this funtionality at a UI level (and not on the model layer). It would be possible to write a custom precondition that prevents changing values of certain attributes if a work item is in a specific state. This wouldn't require any product changes and could be implemented by a contractor.

Your answer


Register or to post your answer.