Service Worker to the Rescue
There has been a lot of traffic opining about the new release that changed various aspects of the GUI. To be honest I didn't read most of the posts in detail nor do I have any problem overcoming any o...
Forum Discussion
So, ideally if i have service worker script for each table, we dont really need the old style IOL technique anymore. right ? All that could be done via IOL can be done from within the service worker scripts ?
A Service Worker has the concept of a scope which restricts what URLs will execute the Service Worker. A Service Worker will only execute against URL paths that are at the same level or lower. Because of QuickBase's URL architecture you can register a Service Worker against the scope https://SUBDOMAIN.quickase.com/db (basically the entire account) or against the scope of a single dbid https://SUBDOMAIN.quickase.com/db/DBID.
Once registered the Service Worker will execute against any page in the defined scope (not just add, view, edit, report or grid pages). Every page including charts and administrative pages. So within your Service worker you have to put the appropriate logic to decode what particular code should be executed based on the current URL or query parameters or some other condition..
Once registered the Service Worker will execute against any page in the defined scope (not just add, view, edit, report or grid pages). Every page including charts and administrative pages. So within your Service worker you have to put the appropriate logic to decode what particular code should be executed based on the current URL or query parameters or some other condition..