Release all when closing Teamwork File

[Patrick M]

Am I completely missing something, or is this a big nothing setting in the work environment? I have it checked, everyone I know has it checked. Everyone still deals with latent users (not in the file, but with inactive connections) retaining reservations after they have closed.
Is this a feature that only works for full BIMcloud, not BIMcloud basic? Or is it just a dummy box that was never fully developed?

 

[Barry Kelly]

I don't use teamwork, but is the clue in the wording?

It is not release all when you close a teamwork file.

It is release all when you send changes and close the file.

So is there a 'send and close' command that you use to close the file?

Rather than possibly sending the changes and then just closing the file.

There may be a difference.

Barry.

[scottjm]

We experience the same thing. We have that setting on all our workspaces but someone people every so often manage to close without releasing all

I’ve worked out if you hit Ctrl+S and then close Archicad it does not give you the ‘do you want to Send/receive and Release All’ dialogue and Archicad just closes cause it thinks there are no unsaved changes. 
That setting only changes the default option to Send/Receive and Release All dialouge, not actually automatically do the release all, so the user still has the option to just S/R and not release all. 

My wish is: with that setting on, always make the Release All dialogue come up. 

We make a big deal in our office about people remembering not to forget to Release All and the impact it has on everyone else to they do forget. 

[Patrick M]

that would mean we are closing/quitting without sending changes, and only hitting send changes when prompted with the "you will lose your work if you don't" warning.
maybe thats what it is, but I'm never going to tell users to close before sending changes. That'd be like telling someon on a pln to close without sending and only send when prompted at closing. I have personally lost work because I absentmindedly hit 'close without saving'. Always save/send THEN close.
If the release only works when you close the incorrect way, then it doesnt work.

[Patrick M]

I see; so it's a nonsense setting that benefits almost no one... bummer

How about a wishlist item to make this thing work as it should?

[scottjm]

I think it still comes up if you send/recieve and then close (I’d have to check). 

the number of users in our office who forgot to release all definitely did decrease significantly since we introduced that setting, but I agree it needs adjustment to work every time as the setting name suggests it should. 

[Barry Kelly]

If the Work Environment is set to 'Release all' and it is not working, there seems to be another way of doing it.

Don't set the Work Environment to 'release all'.

Then next to the 'send & save' button will be a small arrow that will give you the option to 'send & save and release all'.

Then I assume you would have to close the file close.

Of course the 'release all when closing teamwork with send changes' should do as it says.

But it seems to me there should then be a command to 'send changes and close', which there doesn't seem to be?

Barry.