- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-01-2014 08:01 AM
In my previous organization where I started with ServiceNow we were advised to use GlideAjax in async mode on client side scripts instead of GlideRecord. GlideRecords too can work in async mode. So was this advise incorrect?
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-02-2014 02:39 PM
Depends what you are trying to achieve really.
aysnc client side gliderecord is is identical as far as I can tell as an async glideajax call (performance wise aswell ) as they both send the request and await the response with a callback function.
HOwever be careful with your queries, client side glide records adhere to ACLs whereas server side ACLs do not. So if the information is secure away from the user via an ACL, you'll need to use a glideajax call.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-03-2014 01:40 AM
Hello Kalai,
Do you think it's a design flaw or was it intended when there is different behavior in security for server and client side?
Regards,
Ravish
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-03-2014 01:49 AM
not really sure on this ... have never check this with service now or with anybody ... may be you could create a HI ticket and they could provide some insight on this and yes , if you happen to create one , please provide us the details too
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-03-2014 02:04 AM
The difference in security between server side and client side gliderecords is intentional.
Any user can run a client side glide record without admin access and so could do all sorts of damage if ACLs weren't implemented.
Whereas server side glide records can only be implemented as part of development and therefore unde control of the servicenow admins.
However, there is (possibly was, I haven't tested in Eureka) a small client side glide record ACL bug which would prevent access to records even if you were meant to have access .
I wrote more explanation on it on my blog here
