 | basenine 11/29/2012 5:11:04 AM Great idea
Do you recommend we clear our browser cache before we enable this feature?
I found clearing mine from after a heavy setup session seems to make things run smoother/quicker
|
 | Slava Shinderov 11/29/2012 5:22:11 AM @Brett browser cache is not involved here.
We're trying to eliminate a time required to ask back-end database and build page if we know that it's not needed since nothing changed.
|
| basenine 11/29/2012 4:19:35 PM Works very well. Just tested it on an app where their connection is pretty average and the new feature sped things up nicely
|
 | Rick Cogley 12/2/2012 12:46:27 AM Works very well, but it seems to be a little off when you change application Workspaces in setup. The newly added Workspace does not get picked up.
|
| Slava Shinderov 12/3/2012 4:59:55 AM @Rick we've addressed "workspaces" problem.
|
| Rick Cogley 12/4/2012 5:19:27 PM Hi Slava - indeed it is better, but sometimes when I switch workspaces, I have to hit ctrl-R to refresh, to get the newly selected one to appear. Previously, even that did not work, but now at least it does. Still, it is something that would have to be explained to users, if it could not be rectified.
I'm loving the snappiness, though. Thanks! :-)
|
| Slava Shinderov 12/5/2012 2:55:59 AM @Rick can you provide exact steps to reproduce the problem?
|
| Rick Cogley 12/5/2012 3:47:42 AM I'm trying to make it happen but it won't recur in Chrome :-(
|
| Rick Cogley 12/5/2012 3:48:51 AM What happened was, I was switching b/w all the workspaces to see how it works, and after a certain few switches, 5 or 6, it would stop recognizing the selection of the workspace. If I hit Ctrl-R then, it will...
|
| basenine 12/5/2012 3:49:13 AM works ok in Safari too...
Were you using IE by any chance?(!)...
|
| Rick Cogley 12/5/2012 3:50:30 AM ew
|
| Rick Cogley 12/5/2012 3:50:54 AM No, just Chrome. I use Safari too and can test it.
|
| Rick Cogley 12/8/2012 8:42:23 AM Hi Slava - we found a strange problem today. I had turned the cache on, and one of my staff noticed a problem when he was doing a little procedure he does to save time, when he is in a calendar view in our Times entry table.
He uses the New button from a given date in the calendar, by right-clicking on it and selecting "open in new tab", repeating this a few times, to get multiple tabs that he can then switch between, fill in, and save. With the cache ON, it was no longer leading to unique entries. The IDs of the new entries in the browser tabs were the same, and he was getting errors about the ID not being unique, on Save.
When I turned the cache OFF, he could do this again.
Is there any way to make this work?
|
| Rick Cogley 12/8/2012 8:48:46 AM |
 | gerardo garcia 12/8/2012 12:55:29 PM Hello!
There is another behaviour to report.
I have a dashboard with multiple views.
Even if update the whole webpage, the views are showing non-updated, previous information.
If I go into each particular view, the data shows updated and correct.
Regards.
|
| Rick Cogley 12/9/2012 1:01:45 PM By the way, the above was observed on Google Chrome, Ver 23.0.1271.95 if that makes a difference one way or the other.
|
| basenine 12/9/2012 3:41:32 PM I've seen issues with "browse for choices" option on related fields. Firstly, the item could not be found and then even searching again within the popup, it could not be found. Turning "browse for choices" option off fixed it.
|
| Slava Shinderov 12/10/2012 6:51:20 AM @Rick we've addressed the problem with "New" button.
@All in most cases it rarely a browser problem. We're trying to calculate all page dependencies and display information from cache if we're sure that related tables were not changed. So if you see outdated page - most likely dependencies were calculated incorrectly. Please drop us a link to particular page in that case.
|
| Rick Cogley 12/11/2012 6:09:07 AM Slava, thanks. We confirm that the New problem is now gone.
|
| Slava Shinderov 12/14/2012 4:13:39 AM Application cache is now enabled by default.
If you'll see any incompatibility with your app, please disable it in app labs and contact us with details.
|
