Community
Participate
Working Groups
OS: Windows XP with SP2 Language: English Build: epf-composer-1.0-M4-N20060719-1630-win32 TestCase ID: 8938 Steps to Reproduce: 1. Create a new Method Library 2. Create a new Method Configurations 3. Create a new Method Plug-in 4. Create a new Delivery Process, input DP name and select Configuration name, press OK 5. Create another DP quickly (in fact, previous DP is in creating) 6. The first DP name will be shown in the current create DP interface, input another one instead it, press OK 7. Check XMI files and it's parent directory -->Problem: the file content and directory name are difference with DP name DP name is the new one you inputted in step 6, but in file system, the directory and file content are still the old one Expected Result: DP name should be same as XMI files in file system Remarks: 1. If you don't see the first DP name in step 7, you cannot recreate this defect, the keyword is "quickly" 2. Restatr EPF, the DP name is same as the file system content, it's the OLD one
This is a low priority issue, but please comment whether we have some kind of techincal solutions on this or not?
Does below solution can resolve this issue? 1. Set ContextMenuNewElementEnable = True, user can use Context menu create a new element by default 2. Set ContextMenuNewElementEnable flag = False once click New->New Element, during element is creating, Context Menu is disabled 3. Reset flag to True after element is created (element editor initialized)
can't re-produce it. When step 4 is executed, a progress bar starts. then you can't get another context menu to invoke the creation of another DP. Please elaborate the steps.
(In reply to comment #3) > can't re-produce it. When step 4 is executed, a progress bar starts. then you > can't get another context menu to invoke the creation of another DP. > Please elaborate the steps. Just ignore the progress bar, and R-click on the DP node and select New->DP, you can see the context menu, when the new process component window popup, the first DP name is bring up by default, then problem should occurs. I agree with you this is a low priority issue.
