Please include detailed documentation such as screenshots, images or video. 1. What version of the software are you running? Release: 12.1.2.1 2. What is the problem? Windchill system currently allows Users to publish CAD Representations manually multiple time. It could be great if system could stop the single user from Publishing more than once (stating your publishing is in progress). Similarly also letting the other users situated globally, that a publishing is in Progress, who is trying to publish the same cad too. The situation gets too complex, when we have many CAD Queues, then it allows still many more duplicate publishing. Example:- When user A hits at "Create Representation" for "CAD Object " "star.asm", it goes under "Execution" But when the user hits again without noticing the same create representation status goes as second job and shows as " Ready". Then User B can try to "Create Representation" for "CAD Object " "star.asm" it goes under "Execution" and this could continue with n number of users. Can these be avoided. Since the system should say, a representation creation is already "In Progress". #This could save time #Avoid unnecessary resource consumption to server 3. Are you using a workaround? If yes, please describe it. There is no workaround currently. This is a huge issue. Since bigger representations could consume more memory and these could indirectly have impact on performances. 4. What is the use case for your organization? Describe how your idea would work in context or how it would apply to a practical situation. If the product enhancement team, could take multiple queue into account. This could improve things a lot. Save time and Also avoid performances impacts. we have set this property : publish.service.duplicatepublishjobvalidation.enabled=true But in our case of multiple queues, this is not helpful. Currently we have 20 queues created for PROE to loadbalance the publishing request from users. So in theory users could hit 40* duplicate publishing request for same CAD file. 5. What impact does this problem currently have on your organization? (Number of users affected, hours of lost productivity, etc.) Currently we have 20 queues created for PROE to loadbalance the publishing request from users. So in theory users could hit 40* duplicate publishing request for same CAD file. #This could save time #Avoid unnecessary resource consumption to server
... View more