The file share form has the "Share with" combo with 2 options: community and public. When you choose public the file is added to the community files. When you choose community the file is added to the user's private files. I would suggest to change the label from community to private.
Another problem is the operation feedback. If you upload a file that already exists, for example, which return a error from connections, the user is not notified. You don't even get an error on sugarcrm logs. It's important to provide clear feedback to the user otherwise the user might think that the file was correctly uploaded and it was not. Ex: if he/she uploads a public file, he/she sees the file on community list and thinks is the last one.
You can image the problems this kind of issue can cause (I sent the old version of the proposal to the customer ! ooops!)
For future: it would be nice to always create a new version of the file (or be asked if you want to create one) on upload.
The file share form has the "Share with" combo with 2 options: community and public. When you choose public the file is added to the community files. When you choose community the file is added to the user's private files. I would suggest to change the label from community to private.
Another problem is the operation feedback. If you upload a file that already exists, for example, which return a error from connections, the user is not notified. You don't even get an error on sugarcrm logs. It's important to provide clear feedback to the user otherwise the user might think that the file was correctly uploaded and it was not. Ex: if he/she uploads a public file, he/she sees the file on community list and thinks is the last one.
You can image the problems this kind of issue can cause (I sent the old version of the proposal to the customer ! ooops!)
For future: it would be nice to always create a new version of the file (or be asked if you want to create one) on upload.