Community
Participate
Working Groups
OS: Windows XP with SP2 Language: English Build: epf-composer-1.0-M4-N20060728-1650 Headline: Unique_Name_Rule may be broken when changing the type of concept, guideline or supporting material. Steps to Reproduce: 1. Create a concept and a guideline, both named 'ibm' 2. Click 'Chang Type' button in the editor, e.g. change concept to guideline. -->Problem: two guidelines have the same name 'ibm' without warining. Expected Result: Unique_Name_Rule performs a name-checking action. Remark: 1. Three type of workproducts can interchange, either has this problem.
Fixed. If there is a name conflict at time of type change, it will prompt a dialog "name conflict dialog" to rename it. If you cancel, type will not be changed. Else, it will create with new name.
In M5-N20060823-1845-win32 build, this problem was not fixed correctly, a new problem occurs which seems more unacceptable. --->New Problem: (The base convert function hurt) After create a new guideline (concept), it cannot be convert to concept (guideline). Only if there already be another type of element with the same name, the following actions runs well.
Fixed.
verified on epf-composer-1.0-M5-N20060824-1920-win32
Verified and fixed on 1.0-M5-N20060824-1920-win32.
Reproduce this bug on build RC2 0926, it's a regresison problem, pls reopen it.
Reopen it as a regression BUG.
will postpone the fix for this to the next release. This is not a critical issue as the underlying data's integrity is still intact (only GUID is used for that purpose). A simple workaround is just to rename those duplicate ones.