Often users move by mistake base folders of their mailbox all around and so is not uncommon to end up with things moved where they should not be. Given time they forgot that "move" and so they call for help about "restoring" missing" elements.
by: Ferdinando G. | over a year ago | Windows Client
Comments
or the mobility client is destroy!
Good point, when you move mailbox folders, Mobility will stop working.
Really, I did not know that? Wow, have I been lucky because no one has complained about that - at least not that I'm aware of.
I also have users that move a column heading off (delete) by mistake by a mouse micro click movement when they are not aware they did it. Our Help Desk is constantly helping end users get back deleted column headings. When such a column heading is put in a delete mode, Prompt the end user to confirm the delete. This Prompt will stop all these help desk calls.
yes base folders should be fixed and not allowed for moving.
but it should also be configurable if folders are allowed to move under this base folders.
for example i dont want that a cabinet mail-folder from being moved by mistake under adressbook or calender...
also i want to freeze a folder-structure an beware from mistake-moving.
so may a "fix-mark" in folder properties would be a solution...
I agree, it would be helpful to be able to have a lock/unlock icon appear (similar to the categories bubble that does the same) when you move the mouse over the left of the folder icon... even better a lock/unlock/hide option, with the home(house) icon enabling an unhide.. .that would tidy up things
Taht happen often. Good point. Base folder fixed and even other too if we choose so.
I (and one of my customers) too want the system folders not able to move around. Today we ran into a poa crashing due to root folders being moved by a user in the GW client, which the Mobility Server seem not to like triggering a core on the server. Well, we can educate customers to not hit the Red-button, but in most cases users move folders by accident is my expirience. So, basically we should protect users from doing such by accident and as a bonus we prevent poa's crashing that way. This is now a long known issue which just should be fixed.
Since the location and existence of system folders for a good syncing with GMS is needed, they should prevented from moving and deletion.
This shouldn´t be rocket science to implement it, or ?
Could we have an official statement on this topic from MF / Mike Bills?
Thanks
This is currently planned on the roadmap the 18.1 release of GroupWise. 18.1 is currently schedule for release late secon half of 2018. Please remember that roadmap items are subject to change as we get closer to release.
GREAT
Thanks! Hopping this will solve many sync-issues.
Thanks looking forward to this feature ! very much!
I have had two users move their calendar in to their mailbox. This causes any client that views them in a multi-user calendar to crash before it is fully loaded. It takes quite a while to find the offender and drag the calendar out of their mailbox to fix it.
This has been an issue since GW was first release and is frankly a bug that should have been fixed decades ago. This causes us considerable issues.
When will 18.1 ship ? I am really excited for this feature.
My understanding is that 18.1 will ship soon.
This is available in 18.1 which is shipping today 10/31/2018. For customers on maintenance this should be available for download in your customer portal over the next couple of days.