PM49290: RESOLVE CONFLICTS UI DOES NOT ACCURATELY DISPLAY ALL CONFLICTS -- SPECIFICALLY CONFLICTS BETWEEN TYPES IN THE SAME LIBRARY.
Closed as suggestion for future release.
You have defined a particular term in your personal library under more than one of your personal types. You attempt to define the term yet again, under yet another type in this same library. the "Resolve Conflicts" UI pops up asking you to decide which type to associate this term with. However, only one type is displayed rather than the three or more redundant definitions you've already created. Upon dismissing this UI, it appears that the term is forced into more than one type.
Un-check the box next to each type that contains your term. Then individually add the types back in, working through the "Resolve Conflicts" UI each time. Ideally, you will never have the same term associated with more than one type within the same library. At present, the "Resolve Conflicts" UI is geared toward resolving contention between terms uniquely defined in each of two (or more) unique types in separate libraries. This issue will be addressed in a future release .
This issue has been closed with status "No plans to fix" and has been accepted as a suggestion for a future release, should one be fielded.
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Applicable component levels
Translate this page: