Unified ERP eCommerce Shipping POS

Software Upgrade Considerations

This document was designed to help users upgrading from Interprise Suite 6.0.9 to Connected Business 13. It includes several “tips and tricks” for the upgrade as well as any changes that will affect the product usage after the upgrade. While we have tested the software thoroughly over several months with several of our customers, and have been running the solution in-house since late 2012, the fact remains that upgrading a custom solution from one version to another can be tricky. Accordingly we highly encourage companies that do not need to upgrade to wait until we have released out our first service pack before upgrading.

Before upgrading to Connected Business, the system requires a minimum version of Interprise Suite which needs to be version 6.0.9.22. Any versions lower than 6.0.9.22 will not allow you to upgrade to Connected Business.
Log in for Web Admin and Email Admin is no longer allowed in Connected Business as this is being solely used by Email Service and eCommerce Website.
Upon upgrade from Interprise Suite 6 to Connected Business 13, the Allow manual journal entry to default control accounts is disabled in the Accounting preferences. This option restricts users from creating manual entry to GL accounts being used by the system to generate journal.

When this option is enabled – allows you from creating manual journals using the Default Accounts. However, the system will only compute the totals created from the transactions forms. In effect, it will not allow you to compare your financial statements to your reports as the totals may no longer match.
When this option is disabled – it will not allow you from creating manual journals using the Default Accounts. By default this is disabled in the system and can be configured by navigating to the Accounting module > Setup > Preference and then tick on the checkbox for Allow Manual Journal Entry for Default Control Accounts.

Connected Business uses a brand new report writer. Custom reports created in Interprise Suite will not automatically be upgraded to Connected Business 13. In order to move them to Connected Business 13 you would need to run the Report Migration tool found on Report Center to convert your old Interprise Suite reports to Connected Business 13 the new report engine.
If your database has custom triggers, please disable your custom triggers first before upgrading.
The following Lerryn plugins will be deleted upon upgrade to Connected Business 13:

To continue using these plugins on Connected Business 13, you may contact Lerryn through their website: http://www.pluginsforinterprise.com/

Lerryn Payroll (both US and UK version)
Lerryn eShopConnect. Please note that we expect eShopConnect to be in the first service release.

SDK Plugins need to be recompiled using the latest SDK build. We currently have a project converter that updates the 3rd party component and which requires using DevEx 12.2.6 version.

The location of the Project converter can be found on this path(depending upon the build version):
C:\Users\....\AppData\Local\Microsoft\VisualStudio\10.0\Extensions\Interprise Solutions\Connected Business SDK 13\13.0.0.x

Any modifications on the User Role are on a Per Module and Per Form basis. This means that any changes made on a form, section, grid or field that is tied in a number of modules in Connected Business should be updated on the other modules where it is currently available. If this is not updated on the other module, the customization applied on the currently updated module will not be implemented, thus you need to manually update the changes on the other module.

An example would be on the item form where it can be seen on two modules namely – Inventory and eCommerce module. Suppose a custom tab is applied on the item form in the eCommerce module. Unless you apply the same changes in the Inventory module, the changes will not be implemented in the eCommerce module.

The rest of these software upgrade considerations are related to the eCommerce module and its folders. Make sure to back up all data before implementing these changes.

The following scripts need to be changed in the Web.CONFIG file. You can access the Web Config through this link: C:\Program Files (x86)\Connected Business 13\ISE\Web.

Add this line inside <configSections> node:

Click Image to Enlarge

Update your Devexpress from version=11.2.11.0 to version=12.2.6.0.

Click Image to Enlarge

There are several areas on web.config where Devexpress are instantiated. Make sure to find and change them all.

Add updated Paypal Express API url’s below </configSections>.

<paypal>
<endpoints>
<wsdl>
<environment name="live">
<port name="PayPalAPI">https://api.paypal.com/2.0/</port>
<port name="PayPalAPIAA">https://api-aa.paypal.com/2.0/</port>
<port name="PayPalAPI" threetoken="true">https://api-3t.paypal.com/2.0/</port>
<port name="PayPalAPIAA" threetoken="true">https://api-aa-3t.paypal.com/2.0/</port>
</environment>
<environment name="sandbox">
<port name="PayPalAPI">https://api.sandbox.paypal.com/2.0/</port>
<port name="PayPalAPIAA">https://api-aa.sandbox.paypal.com/2.0/</port>
<port name="PayPalAPI" threetoken="true">https://api-3t.sandbox.paypal.com/2.0/</port>
<port name="PayPalAPIAA" threetoken="true">https://api-3t.sandbox.paypal.com/2.0/</port>
</environment>
<environment name="beta-sandbox">
<port name="PayPalAPI">https://api.beta-sandbox.paypal.com/2.0/</port>
<port name="PayPalAPIAA">https://api-aa.beta-sandbox.paypal.com/2.0/</port>
<port name="PayPalAPI" threetoken="true">https://api-3t.beta-sandbox.paypal.com/2.0/</port>
<port name="PayPalAPIAA" threetoken="true">https://api-3t.beta-sandbox.paypal.com/2.0/</port>
</environment>
</wsdl>
</endpoints>
</paypal>

Click Image to Enlarge

Add this line under <controls> section:

<add tagPrefix="dxwc" namespace="DevExpress.XtraReports.Web" assembly="DevExpress.XtraReports.v12.2.Web, Version=12.2.6.0, Culture=neutral, PublicKeyToken=B88D1754D700E49A"/>

Click Image to Enlarge

Add the following lines under <assemblies> section:

<add assembly="DevExpress.Printing.v12.2.Core, Version=12.2.6.0, Culture=neutral, PublicKeyToken=B88D1754D700E49A"/>
<add assembly="DevExpress.Utils.v12.2, Version=12.2.6.0, Culture=neutral, PublicKeyToken=B88D1754D700E49A"/>
<add assembly="DevExpress.Web.v12.2, Version=12.2.6.0, Culture=neutral, PublicKeyToken=B88D1754D700E49A"/>
<add assembly="DevExpress.XtraBars.v12.2, Version=12.2.6.0, Culture=neutral, PublicKeyToken=B88D1754D700E49A"/>
<add assembly="DevExpress.XtraEditors.v12.2, Version=12.2.6.0, Culture=neutral, PublicKeyToken=B88D1754D700E49A"/>
<add assembly="DevExpress.XtraGrid.v12.2, Version=12.2.6.0, Culture=neutral, PublicKeyToken=B88D1754D700E49A"/>
<add assembly="DevExpress.XtraLayout.v12.2, Version=12.2.6.0, Culture=neutral, PublicKeyToken=B88D1754D700E49A"/>
<add assembly="DevExpress.XtraPrinting.v12.2, Version=12.2.6.0, Culture=neutral, PublicKeyToken=B88D1754D700E49A"/>
<add assembly="DevExpress.XtraReports.v12.2, Version=12.2.6.0, Culture=neutral, PublicKeyToken=B88D1754D700E49A"/>
<add assembly="DevExpress.XtraReports.v12.2.Web, Version=12.2.6.0, Culture=neutral, PublicKeyToken=B88D1754D700E49A"/>
<add assembly="DevExpress.XtraVerticalGrid.v12.2, Version=12.2.6.0, Culture=neutral, PublicKeyToken=B88D1754D700E49A"/>
<add assembly="DevExpress.RichEdit.v12.2.Core, Version=12.2.6.0, Culture=neutral, PublicKeyToken=B88D1754D700E49A"/>
<add assembly="DevExpress.Data.v12.2, Version=12.2.6.0, Culture=neutral, PublicKeyToken=B88D1754D700E49A"/>]

Click Image to Enlarge

Modify the line:
<httpRuntime maxRequestLength="409600" executionTimeout="300"/>

Change to:
<httpRuntime maxRequestLength="409600" executionTimeout="300" requestValidationMode="2.0"/>

The following scripts need to be changed in the SKIN TEMPLATE.ASCX file.

Modify the line:
<script type="text/javascript" src="/jscripts/jquery/jquery.min.v1.6.4.js"></script>

Change to:
<script type="text/javascript" src="/jscripts/jquery/jquery.min.v1.7.2.js"></script>

Delete the line:

Add the following lines on <head> section:

Click Image to Enlarge

Add Google Analytics script on <head> section below other javascripts entries:

<script type="text/javascript">
            var _gaq = _gaq || [];
            $(window).load(function () {
                        var pageTracking = ise.Configuration.getConfigValue("GoogleAnalytics.PageTracking");
                        var ecTracking = ise.Configuration.getConfigValue("GoogleAnalytics.ConversionTracking");
                        var gaAccount = ise.Configuration.getConfigValue("GoogleAnalytics.TrackingCode");

var orderNumber = getQueryString()["ordernumber"]; // get ordernumber query string

var imAtConfirmOrderPage = false;

if (typeof orderNumber != "undefined" && ecTracking == 'true') { // verify if ordernumber query string is defined and ecTracking app config is true
imAtConfirmOrderPage = true;
}

if ((pageTracking == 'true' || imAtConfirmOrderPage) && gaAccount != "") { // verify if pageTracking app config is true OR current page is orderconfirmation.aspx

// uncomment to test your Google Analytics on localhost:
// _gaq.push(['_setDomainName', 'none']);
_gaq.push(['_setAccount', gaAccount]); // set google analytics account (see app config GoogleAnalytics.TrackingCode
_gaq.push(['_trackPageview']); // request page tracking
}
});
</script>

Click Image to Enlarge

Add this script above the closing </body> tag:

<script type="text/javascript">
        $(window).load(function () {
            var pageTracking = $.trim(ise.Configuration.getConfigValue("GoogleAnalytics.PageTracking"));
            var ecTracking = $.trim(ise.Configuration.getConfigValue("GoogleAnalytics.ConversionTracking"));
            var gaAccount = $.trim(ise.Configuration.getConfigValue("GoogleAnalytics.TrackingCode"));
            var orderNumber = getQueryString()["ordernumber"]; // get ordernumber query string
            var imAtConfirmOrderPage = false;

if (typeof orderNumber != "undefined" && ecTracking == 'true') imAtConfirmOrderPage = true;

if ((pageTracking == 'true' || imAtConfirmOrderPage) && gaAccount != "GoogleAnalytics.TrackingCode") {
var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
ga.src = ('https:' == document.location.protocol ? 'https://ssl' : 'http://www') + '.google-analytics.com/ga.js';
var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
}
});
</script>

Click Image to Enlarge

Add global loader script after Google Analytics script used for showing loading animation.

<script type="text/javascript">
$(document).ready(function () {
$("body").globalLoader({
autoHide: false,
image: 'images/ajax-loader.gif',
opacity: 0.3,
text: 'loading...'
});
//sample implementation to display the loader
//$("body").data("globalLoader").show();
});
</script>

Add top menu place holder section. Check Skin_99 from installer for the location on template.ascx.

Add Social Media token (facebook feeds).

(!SOCIALMEDIA_FEEDBOX!)

Modify the token from (!ADDRESS_VERIFICATION_DIALOG!)

to (!ADDRESS_VERIFICATION_DIALOG_LISTING!) .

Add Bubble Tip container. This is the yellow bubble on createaccount.aspx

<div id="ise-message-tips"><span id="ise-message" class="custom-font-style"></span><span id="message-pointer"></span></div>

Add Mobile switcher token. You can put this on the footer of your website. This will only show when browsing on mobile device.

<div class="footer-mobile-link">
(!MOBILE_FULLMODE_SWITCHER!)
</div>

Add Social Media link token by inserting the script below.

<div id="socialmedia-subscribebox">
(!Topic Name="SocialMediaSubscribeBox"!)
</div>

Add Customer Support code. It is recommended to place the customer support code on the footer area.

<div id="request-container">
            <div class="request-caption-wrapper">
                        <span class="request-caption">(!stringresource name="main.content.1"!) </span>
                        <div class="request-code-wrapper">
                                    <div class="request-generator-content">
                                                <span class="request-code">---------------</span>
                                    </div>
                        </div>
                        <div id="imgLoader" style="display: none">
                                    <img src="/skins/Skin_(!SKINID!)https://www.connectedbusiness.com/images/blogs/loading.gif" alt="" title="" />
                        </div>
            </div>
            <%--*width:155px; width:155px\0; ie8 and ie6/7 css hack--%>
            <div style="margin-left: 10px; float: left; width: 155px;">
                        <a href="javascript:void(0);" class="generate-link">
                                    <img src="/skins/Skin_(!SKINID!)https://www.connectedbusiness.com/images/blogs/refresh-captcha.png" alt="" title="" />
                        </a><a href="javascript:void(0);" class="copy-link">(!stringresource name="main.content.3"!)
                        </a>
            </div>
</div>

For STYLE.CSS:
Changes on style.css for Connected Business 13 is attached to file style.css included on this instruction. Copy the content there to your style.css file. Click here to download the file.
For SKIN XMLPACKAGE:

Copy rev.multicolumn.topmenu.xml.config and rev.singlecolumn.topmenu.xml.config from Skin_99/XmlPackages to your skin_#/XmlPackages folder.

rev.multicolumn.topmenu.xml.config is for showing multiple column top menu
rev.singlecolumn.topmenu.xml.configis for single column top menu.

Change the name to rev.topmenu.xml.config if you want to use it for your top menu.

Copy rev.topmenu.xml.config from Skin_99/XmlPackages to your skin_#/XmlPackages folder

For SKIN images:

Copy giftregistry and storelocator folder from Skin_99/images to your skin_#/images folder.
Copy calendar-icon.png, cbleads_logo.png, minicarttop.gif, minicartbottom.gif, pencil.png, nopictureminicart.gif, nopictureicon_entity.gif from Skin_99/images to your skin_#/images folder.

For Skin New folders:

Copy plugin from Skin_99 folder to your skin_# folder.
Copy ui-lightness from Skin_99 folder to your skin_# folder.

For Product Images:
Copy all your product images to the same location of your upgraded Connected Business 13 eCommerce site.
For Website XML Packages:

Copy your modified XMLPackage to the XMLPackage folder of your upgraded CB 13 eCommerce website.
For XMLPackage Extension Functions (e.g. ise: …) that do not work any longer on CBE (Connected Business eCommerce) check the XMLPackage from the installer for the new format.

For JSCRIPTS Folder:
Any changes made in your current version must be merged to Connected Business 13 through copy and pasting your changes to Connected Business. Copy ONLY the scripts you modified or code block any modifications to your upgraded Connected Business eCommerce jscripts folder. There are many changes to these files inside this folder and they should remain intact.

Failing to comply on these software upgrade considerations, may result to unexpected errors or most likely encounter similar issues stated above. For concerns on upgrading to Connected Business, you may contact Interprise Solutions support department to further assist you.

Schedule A Consultation Today

Schedule Product Tour