Community Tip - You can subscribe to a forum, label or individual post and receive email notifications when someone posts a new topic or reply. Learn more! X
Two users have confirmed this and I have seen this before years ago I believe with change objects. The user was creating a new part request object. Two were created as a result at exactly the same time and two workflows were spawned. As I have seen this before with other wizards, was there a fix or should this be filed as ticket to PTC? I cannot say if the user clicked something twice or rapidly. I will try to repeat but system should not allow multiple objects to be created if the user gets click happy waiting for response.
Solved! Go to Solution.
PTC replied back that there is an SPR on this (SPR 1979291) but that duplicate part requests can result if Apply is clicked multiple times before Finish. Each time you click apply, a new part request is created but window remains open. When you close with Finish, it creates the final one. At least we know what triggers it and can avoid it until SPR is closed.
its worth to check the Apache access log, if two requests were generated by the client machine
issue tracked with TS IN C17323941
PTC replied back that there is an SPR on this (SPR 1979291) but that duplicate part requests can result if Apply is clicked multiple times before Finish. Each time you click apply, a new part request is created but window remains open. When you close with Finish, it creates the final one. At least we know what triggers it and can avoid it until SPR is closed.
Ok, here is a head scratcher. What say you? The SPR was closed with a note "as working to specification". Seems the user should know not to hit apply multiple times before finish. I replied in disagreement that this cannot be as intended. Awaiting response.
I would say that Apply should create the new object, leave the wizard open, but erase the original entered data so an additional new object(s) can be created. Finish should create the object and close the wizard.