Jazz Forum Welcome to the Jazz Community Forum Connect and collaborate with IBM Engineering experts and users

This document specifies the need to configure dynamic field linkage rules for the "Change Application" work item in the EWM module: the "Requirement Type" field is hidden by default and only displayed when "Requirement Change" is selected for the "Change

Questions
Tags
Users
Badges
BoCheng Bi
(11●1●1●1) Jan 28, 9:08 p.m.

In the EWM module, we need to implement a set of dynamic field linkage display logic for the "Change Application" work item.

The specific requirement is as follows: configure the dependency and visibility rules between fields so that the "Requirement Type" field is hidden by default; the system will automatically trigger and display the "Requirement Type" field only when the user selects the specific option "Requirement Change" in the "Change Type" field, and the field will not appear on the interface when any other change type is selected. How to configure this function? A detailed explanation is required.

0 votes

Comments
Ralph Schoon
Jan 29, 4:30 a.m.
Pasting your complete question into the question title/summary is frowned upon. Please create a decent title and provide the details in the question body.

1 answer
917 views
0 votes

One answer

Permanent link
Davyd Norris
(3.8k●2●20) Jan 28, 9:41 p.m.
You can't hide work item attribute fields based on generic conditions - You can only make them read only. 

You can set fields to be hidden: 
 - during creation
 - when they are empty and the form isn't in edit mode
 - in specific workflow states of your choosing
 - if there are no links of specific types of your choosing
 - if there are no associations to other project areas of your choosing

In addition, if a work item doesn't have the field in its definition, then the UI will not display the field. So your choices are make the field readonly based on the value of the "Change Type" field, or use different work item types for each change type and then only define the required fields.

0 votes

Comments
BoCheng Bi
Jan 28, 9:54 p.m.
If I want to achieve the aforementioned effect, take the change request process as an example—it includes design change, requirement change, supplier change and other types. Each type of process has its exclusive fields, yet the state transition of all change processes is basically consistent. For this reason, I do not want the exclusive fields of supplier change to appear when processing a design change, which may lead to misunderstandings among users. Could you advise on a solution to this problem?

Davyd Norris
Jan 28, 10:35 p.m.
OK this definitely sounds like the best approach would be to create separate workitem types for each change.  - create a type for each change, then create new attributes where needed, and reuse the attributes where they are common  - workflows are created separately to workitem types and can be assigned to multiple types, so create a single workflow and assign it to all the types  - presentations are also created separately and can be reused, so create a form that has ALL the attributes across all the change types, and assign it to each type. Depending on the type, only the attributes that are defined on it will be displayed

Your answer

Register or log in to post 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.

Ask a question
Guidelines
FAQ
Search context
Follow this question

By Email: 

Once you sign in you will be able to subscribe for any updates here.

By RSS:

Answers
Answers and Comments
Question details
× 12,146
× 7,624
× 1,454

Question asked: Jan 28, 9:08 p.m.

Question was seen: 917 times

Last updated: Jan 29, 4:30 a.m.

Confirmation Cancel Confirm