Hi Everyone
I have just updated to the Latest Promis-e SS8 REFRESH (08.11.13.96) and have had a few problems with the latest release. When I select a bunch of drawing in Project Manager and hit the "Plot Pages" Button in the toolbar. It functions like normal, opening up each drawing you want to print and then populating the print organiser from which you can enter your print settings and punch out pdfs or send to the printer no problems. Once I'm finished though, i look back in the project manager and all the drawings I printed are booked out to me but they arent locked, i have had a colleague verify that he can open a drawing that says is open by me and he can open it without getting the read-only msg. Is this a glitch?
Cheers
Chris
Hi Christopher,For the issue you are facing have you tried using Page Refresh / Update on the drawings that are booked in you name. kindly let us if that helps with your concern. If you are still able to see your name against all the Drawings that you selected to Print then let us know the same. You can refer the below steps for the same.select all the Drawings in Project Manager for which you are facing concern and then Right Click and select Refresh Page / update Page and then check if that helps yo can also refer the below Wiki Link for the issue for Update Page function.Wiki Link Update Page: https://communities.bentley.com/products/electrical___instrumentation/w/electrical_and_instrumentation__wiki/7533/update-page Regards,Satish Saptasagar
Hi Satish
Its not hard to fix the problem, simply opening and closing the drawings will fix the problem as well, refreshing the project manager doesn't fix it though as it generally shows more that are booked in my name. My question is how to stop this behaviour of the program in the first place as this has never really been a problem in the past. Printing drawing and letting the program run through your selection to populate your print organiser didn't leave them booked to you, they would always close down properly.
Hi Christopher. Right, this is a known issue that will be resolved by the Promis.e CONNECT Edition expected by early 2019. I don't know a way to prevent it in the meantime.