Hello Wayne,
I believe we have met before; my name is Juan Rodriguez, and I am the CIO for Sage North America. I got forwarded to me a post that you made in a private LinkedIn group recently about portal browser support, software demos and houses of cards. I wanted to give you personally some color commentary on specifically the portal pieces, and I will leave the other ones alone, as they are more opinion than fact.
As you know our browser support for the portals has been limited since we released Atlas. The reasons vary, but primarily this is due to the fact that we are stuck with what our vendor's technology would support for the portal. There is nothing more than myself and the rest of the Sage team would like than supporting every single browser technology under the sun for our portals, but unfortunately we have certain limitations and constraints.
Recently our vendor released a version of their technology stack that supports newer browsers, like Chrome and newer versions of Firefox, which is great news. We have been working on upgrading our external portals to this technology stack version over the past few weeks. It's not a straight forward process, I can tell you that. In any case, we made ourselves a target to have increased browser support prior to the end of the year. To that goal two weekends ago we released a new portal version that supports Chrome on Windows, along with IE 8/9, as usual, in compatibility mode. Google Chrome support is something the team worked hard on to release prior to year end. We expect that we will have further browser support over the next 8-12 weeks as we complete the stack upgrade.
You mentioned an specific issue regarding certain KB items that are published in xml format in Chrome. This, indeed, appears to be an issue. Our research indicates a limitation in Chrome that is not present in other browsers like IE or Firefox. In fact, this item is documented in the following Chromium issue:
http://code.google.com/p/chromium/issues/detail?id=70088
It seems the chromium team doesn't plan to address this limitation, and as you can see in the discussion this has created certain angst by the community; their response... well, use another browser.
Here is the browser flow and the differences in IE and Chrome:
Search term for ""Aatrix ird"" is entered and executed for Sage 100 ERP:
[cid:
image009.jpg@01CDE43C.929680C0]
Search Results returned:
[cid:
image003.png@01CDE43A.81A60670]
Article for IRD:
[cid:
image004.png@01CDE43A.81A60670]
Within the KB article, the ""Aatrix Entitlement"" link points to an XML article that is associated with an XSLT (which transforms the content in a presentable HTML format).
https://partners.sagenorthamerica.com/irj/go/km/docs/sageKM/Sage%20MAS%2090%20and%20200/Gated%20Customers/Warr_Svc_Support%20Plan/110-1003783.xml
These types of articles in Atlas KM render fine in IE:
[cid:
image010.jpg@01CDE43C.929680C0]
however, not Google Chrome and all that appears is a blank screen:
[cid:
image011.jpg@01CDE43C.929680C0]
Roughly 12% of the articles in our KB system have been published in the xml format that is having this issue in Chrome, with the vast majority of them being internal only articles. Having said that, we are investigating how we can address this Chrome limitation in these KB articles, and I am certain we will solve this soon. In the mean time if you see that you are hitting this issue constantly you should use IE8/9 for portal access.
Apologies for the frustration the portal's limited browser support gives. I believe we are moving in the right direction and hopefully over the next few months this will be behind us. We also have a few other exciting things in the works with our CRM upgrade, which will bring other portal improvements, and a project to implement a new knowledge base system, which I believe will enhance the experience significantly.
Thank you for your time, and please let me know if I can be of assistance. If in the future you have a question or a comment, you are more than welcome to contact me directly if you would like to discuss; I welcome the dialog.
Thanks again!
Juan M. Rodriguez