Defects/Deficiencies relating to Share Functionality
I have discovered defects/deficiencies relating to the Share Functionality within ZOHO Creator ... I did not want to hi-jack this topic ... http://help.zoho.com/portal/en/community/topic/an-issue-with-unshare ... so I started a new topic here.
A couple of months ago I was asked to evaluate an Application (running since January/2010) for a Customer ... their previous Developer had gone AWOL.
This Application had never been backed up ... and the first attempt to do so failed ... the ZOHO Support Team had to intervene in order to create the backup file ... then intervene again in order to restore it (as a test copy).
Once restored, I noticed that the Share information was NOT restored in the restored copy ... apparently, this is how ZOHO Creator works !!!
Upon further analysis, it was discovered that details of the Share configuration in the Production copy could not be viewed for any of the 43 Users !!! ... we were told that this was a known deficiency (some would call it a defect) ... apparently, when a ZOHO Application has more than 15 Users, the ZOHO Creator Team has turned off the ability to display the individual components shared to a specific user !!!
More than two months later, this issue remains unresolved ... kind of surprised that no one else has encountered this problem ... aren't there any Applications out there with more than 15 users ???
This issue caused me to do some more investigating ... and I found that the Share Information is NOT backed up with the data and scripts ... I wonder how many users here know that if there was ever a reason to Restore their Application from one of the Backup copies ... the Share Information would need to be re-entered.
There is no facility for the user to export the current Share configuration to an external source ... so if they had not noted such details on an external source (like a spreadsheet) manually, they would not have any means to recover their Application to the point of last backup ... for the afore mentioned Customer, the detailed knowledge of required Share components by User went AWOL with the Developer ... leaving the Customer in a precarious situation.
Gaev