Showing results for 
Search instead for 
Do you mean 

Sage Summit, mobile, and JavaScript

by ‎08-23-2012 12:55 PM - edited ‎08-23-2012 01:04 PM

For those of you unable to attend Sage Summit, here's a quick run down of the sessions I covered on mobile and customization. Hope to see you at Sage Summit next year!


Sage Summit was a huge success for Sage and Sage SalesLogix. I presented a few sessions from version 8 stuff for partners to Mobile and web administrator information for Customers. The atmosphere was very positive with some really big adoptions of both 7.5.4 and Mobile. The most interest was in version 8 and Mobile version 2.0 and 3.0. We were even able to show off version 3.0 of mobile to customers using our iPads (mobile 3.0 is the tablet version).


I started the last of my customer sessions by mentioning JavaScript and debugging. It is a hot topic these days and I just left an internal Sage SalesLogix meeting where JavaScript and the debugging thereof was part of the discussion. John Perona pointed out debugging JavaScript is a lot like VB Script was back in the day. You have no real UI to speak of, no intellisense, and you can only see errors at runtime. With vbscript the UI was Visual Interdev, with JavaScript we have Notepad ++ (or any other editor). For debugging in VB Script we would response.write and in JavaScript we have alert or console.print.


That sad story is not the end of it though. At Sage Summit we were able to learn about using Chrome and its debugging tools, Firefox and Firebug, and how to leverage the output of these tools to find our errors faster. The focus of my demonstration was mobile, but with a successful mobile customization comes some debugging. Debugging of YOUR MISTAKES.


That is the hard part. As developers or customizers, we know we made the mistake, but we want to have the tools to find those mistakes and reduce their impact. Right now we are just starting to learn about those tools as a community. I assure you we have many customers (I had 50+ in my session, standing room only) that want mobile 1.2, 2.0 and 3.0 and with these customizations there is debugging to be done.


Another key point discussed with Partners and Customers alike was “should I use Mobile 2.0 or go with 1.2?” There isn’t an easy answer, but here are the key points. 1.2 will work with 7.5.4, 7.5.3, and 8.0+. 2.0 will work with 7.5.4 (when the patch is released to update a small piece of 7.5.4) and 8+. Now the catch might be that 1.2 is using EXT and 2.0 is using DOJO. Anything you write in 1.2 will need to be touched (rewritten is a bit strong of a word here) to move it to 2.0. Anything you write in 2.0 will port to 3.0 without much trouble (I have the developers assurance here).


Final point. Did you miss something at Sage Summit? Want to know more about 8.0, the Job Service, Mobile 2.0 & 3.0, add a field, or anything else Sage SalesLogix related? Well join us at Boot Camp. It is the premier location for partners (sorry not a customer event yet) to learn about what is new for Sage SalesLogix. Customers and partners alike can always email training for more information (or to try and convince us to share the boot camp details after the event):

by Gold Super Contributor
on ‎08-24-2012 06:52 AM

Good post Jason. 

As you pointed out, what really helps is to have a GOOD tool that "unerstands" javascript syntax. I've found WebStorm fits the bill perfectly.. and (AFAIK) the SLX Mobile developers use it too. SInce v1.x actually deploys the "source" to the website, developing using WebStorm is really easy. It solves the "intellisense" issue 100%.


Although V8.0 (w/2.0 mobile) does (current beta) NOT deploy the source, one can "hack" the source in. This is a "feature" that 1.x has always had & I hope/expect the v8.0 AA will be changed to deploy source (optionally?) so we can continue to use great tools like WebStorm. 

Register Read Guidelines Request Partner or Employee Access

What's New in 8.1