zedSuite Receives PA-DSS Validation for zed eCommerce Product

St. John's, Newfoundland, Canada

The Payment Card Industry Data Security Standard (PCI-DSS) was created to help global payment card industry organizations that process card payments prevent credit card fraud through increased controls around data and its exposure to compromise. From the world's largest corporations to small Internet stores, merchants who store, process or transmit cardholder data are responsible for maintaining a secure network, protecting data, implementing strong access control measures and regularly monitoring and testing their application.

PA-DSS represents a specific set of requirements that a system must meet if it is used to process credit card transactions. An independent assessor, approved by the PCI SSC, must audit each system and assign a "pass" or "fail" to the application. Those that pass are put on the official list of PA-DSS-compliant applications - of which zed eCommerce is now included.

For zed eCommerce and WebCRM 7.5, being PCI-DSS compatible provides an extra measure of protection for users. After testing 70,000 vulnerabilities, the newest version has added several changes to user authentication such as user accounts, passwords, encryptions and other payment data related information. By complying with this set of rules, zedSuite has improved how personal information is collected, how internal users and customers access zed eCommerce and WebCRM 7.5, and how the overall application is created and tested.

zedSuite, a leader in eCommerce and other complementary web products integrated with SAP Business One, is proactively meeting this industry standard and sharing their ongoing commitment to the eCommerce industry as a whole. As an established eBusiness solution provider for SAP Business One, zed eCommerce and WebCRM 7.5 has taken drastic measures to ensure the protection of personal information and customer credit card data. zed eCommerce 7.5 is compatible with SAP Business One 9.9.1 PL9 and 8.8 PL22.

About zedSuite

zedSuite (www.zedsuite.com) is a certified SAP Software Solutions Partner with more than seven (7) years of experience providing custom development work for the SAP Business One solution. In 2009, zedSuite officially acquired the SAP eCommerce and WebCRM solutions from SAP Global, and rebranded them as zed eCommerce and zed WebCRM respectively. zedSuite provides a portfolio of eBusiness solutions for SAP Business One that empower small businesses and help them expand their market reach, while saving them considerable time, budget and resources. Through our formal network of Partners and Distributors worldwide, zedSuite includes zed eCommerce, zed WebCRM, zed B1WebAPI, zed Customer Portal, zed B1 Query Portal and zedCRM.

# # #

SAP and all SAP logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries.

All other product and service names mentioned are the trademarks of their respective companies.

For more information, press only:

Sarah Coish +1 (709) 722-7213, sarah.coish@zedsuite.com

The following plugin will accomplish this task by checking if the current page is secure and if not, redirect to the secure page. The advantage of using a plugin to do this is it can be theme specific so ThemeA can force a secure connection but ThemeB can remain non-secure.

To install, copy the plugin to the plugins folder and modify the theme to include the plugin in a new slot. The plugin does not display any HTML so the design should not be affected.

Before installing the plugin, test that the site will work under ssl. Access the site by manually typing https:// as the url and if the site loads properly then the site should be properly configured.

Potential Issues: If the ssl certificate isn't properly installed all secure requests to the page could fail and with this plugin running it won't be possible to get back to the theme to disable it. If this (or any problems) occur, navigate to the plugins folder and simply delete or rename the plugin. This will allow you to navigate the site insecurely again.

Download the zed eCommerce for SAP Business One security plug-in here.

First you'll need to login to the administration as manager or a user with super user privileges.

Then choose Definitions, Language Strings

Then click on the folder icon to proceed to the import/export strings page.

To do this, edit the "login webflow" and assign the web flow to the account type "internal"

To edit the login webflow, login to the admin as manager or a super user. Click Layout > Web Flow

On the web flow list screen select "Login" from the dropdown menu and then click the "New" icon

For the Source page field enter "common/accounts/login.aspx" Note there is no preceding slash yet the text is referring to a site root relative location.

For the Next page field enter "admin/focus/today.aspx" to forward users to the Today screen that lists activities for today.

Choose "Internal" for the account type. In this way, only those users that belong to the Internal Account will be forwarded and all other users will still be forwarded to the My Account screen or shipping screen if they are in the process of checking out.

Click Save

Logout as manager and log back in. Instead of seeing the My Account screen, you should be forwarded to the Today page of the admin.

As you can see, it's possible to change the value for the Next field to be any page you like. Perhaps you want to send internal users to the Sales View page, that would be "admin/focus/sales.aspx"

Ticking the Secure checkbox will attempt to forward to the https version of the page and does not encrypt the data for the actual login. If you want a secure login you will need to set the link to login.aspx to use https. After doing so, the entire session will be within https unless another link specifically points to http. You will also need an SSL certificate enabled on the web server to do any https.

In previous versions of zed eCommerce and WebCRM, as well as WebTools, a document (NP2SBO-DataMap.xls) was shipped in the SDK\Code Examples\SynchPlugin\ folder that contained a mapping of how the data synchs from one system to the other. However, not everyone knew this document was there and the information contained in it was considerably out of date. As part of the 7.1.2 release of zed eCommerce and WebCRM we wanted to include the updated information as well as present it in a user friendly format that will allow the users to search for the information they require without having to scroll through pages of information to try and find it. This data will also be updated with each release to reflect the current version of the application.

Anyone who has installed 7.1.2 can view this information in the Admin under Help -> Synch Data Map. This will open a new tab displaying the basic information. For a more detailed view of the data click on the Advanced View link at the bottom of the page. The table will be updated to include information such as the field sizes and API properties.

If you haven't yet downloaded 7.1.2 you can view this information at http://www.b1webcrm.com/admin/synchmap.aspx . However, this link will reflect the mapping as of the version installed on the b1webcrm site (currently 7.1.2).

I've included a couple of examples as part of this document of how a beginner or a more advanced user might use the data mapping to solve issues that they may encounter. If there are any specific situations which you have used this information for, or plan to use this information for please add a comment here so that others can learn from your experience. Also, as this information is every changing please feel free to comment on how we could improve the presentation to make it more beneficial.

Basic View:

 The Basic View contains the follow Columns:

Name:

          A friendly name used to identify the Synch Object.

zed Table:

          The table name in the zed eCommerce and WebCRM database.

zed Field:

          The name of the field in the zed eCommerce and WebCRM table.

B1 Table:

          The table name in the SAP Business One database.

B1 Field:

          The name of the field in the SAP Business One table.

To B1:

          Does this field Synch to Business One.

To zed:

          Does this field Synch to zed eCommerce and WebCRM.

Comments:

          Any additional information about the line.

Finding Information:

Page Control:

The page control is located at the bottom of the table. The user can click the First, Next, Previous, and Last buttons to scroll through the data. A picture of this control can be seen below.

Group By Area:

The Group By area allows users to group the data by dragging columns from the table and dropping them in this area. This will change the display to group by the specified columns. For example, if we drag the Name column to the Group By Area it will be updated to look like this:

Sections can then be expanded by clicking on the '+' at the beginning of the row. To ungroup the data the column can be dragged back to its place in the table.

Search Box:

The Search Box is displayed in the far right corner of the Group By Area. The user can type characters into this field and it will search all columns and rows for cells containing this information. The table is refreshed as each character is typed so it is not necessary to press the enter key after entering the word that you wish to search for. For example, if a user wanted to know where all of the fields in the PartsMaster table synch they could type PartsMaster into the search box and the following will be displayed:

Additional Features:

Sorting:

          The data in the table can be sorted by clicking on the column header.

Organizing:

The columns can be dragged and dropped in the table allowing the user to change the order of the columns.

Resizing:

The width of columns can be increased by dragging the column separator to the desired width.

Examples:

Q: I want to know if the remarks on an Item in eCommerce synchs to the Item Master in Business One?

A: Using the Search Box type in the information that you know. In this example, you know the field is called Remarks so type in Remarks. A few lines will be returned. Looking at the lines you will notice that one is for Items.

Reading the rest of the line you can see that it synchs to the UserText field in the OITM table of Business One. Also, that it synchs in both directions.

Q: I want to Synch quotes but I'm not sure if all of the information that I require will be synched. What exactly synchs for quotes and where does it Synch?

A: Since you know that you want information about Quotes type Quote in the Search Box. The table will be filled with the data associated with quotes. From this list you can identify which fields synch and where they synch to.

Advanced View:

For more advanced users another view of the data mapping is available that displays additional information. A user can see this view by click the Advanced View link at the bottom of the page. All features described above also apply to the Advanced View. This view can be seen below:

Additional Columns:

zed Field Size:

          The size of the field in the zed eCommerce and WebCRM table.

API Class:

          The class in the Netpoint.API library that references the zed table.

API Property:

          The property in the API class that references the zed field.

DI API Class:

          The class in the SAP Business One DI API that references the B1 Table.

DI API Property:

          The property in the DI API class that references the B1 Field.

B1 Field Size:

          The size of the field in the SAP Business One table.

Examples:

Q: After the Item Synch completes, I want to create a Synch Plugin that will update the dimensions with data from a custom table to handle a conversion we need in Business One. How do I know what to use in the Netpoint.API to update these fields.

A: Using the Search Box type in the information that you know. In this example, you know that it is part of the Item synch so type Item. This will return rows related to the synching of items. From this list locate the dimensions. Using the API Class and API Property columns you will see that it uses NPPart and the Properties are Depth, Width and Height.

Q: I've created a synch plugin to update the name of the Contract Template once it has been added to the WebTools database. I'm using the DI API to retrieve the Contract Templates in Business One. My plugin fails stating that the Template Name is too long. I don't have access to the database server. How can I find out the maximum size of this field?

A: Using the Search Box type in the DI API property (TemplateName) that you are using to access the field in Business One. This will return the row that you are looking for. From here you can see that the maximum field size is 100 characters.

Perform a new install on the new server and request a new license rather than trying to copy and recreate the eCommerce environment. There should be a test server license option available to choose from when requesting a new license.

Once you get the new install done, copy the website files from the current site (except web.config and bin folder) and overwrite the new ones and backup and restore the live database on the new server overwriting the one created in the new install. At this point you should have a running site that looks like your current site.

At this time you should also test the messaging service to make sure it works form the new server as well as a test synch from a copy of your SBO company to make sure there are no connectivity issues.

When you are ready to go live, request a new server license and then stop the synch in the current environment. Copy the web database to the new server again and re-configure the synch manager to point to the new server. You can request a new license by navigating to licenserequest.aspx from the root of the website

NOTE: when you do the new install make sure you use the same private key as your current one so you don't get errors decrypting passwords on the new site.

This is not an installation document for zed eCommerce. This document assumes you have done all the work necessary on the eCommerce website, including licensing, synchronization of data with B1, site design, B2B or B2C logins created, catalog and categories sorted, item availability defined, price list functional, internal testing completed. For information on how to complete these steps, see the guides available as part of the eCommerce download. It is recommended you work with a partner that has experience installing, customizing, and implementing eCommerce.

Network Settings

* Web server on premise

1. Firewall/Router configuration

- Using Network Address Translation or Port Forwarding

i.    Forward HTTP requests on TCP/IP Port 80 to internal IP address of web server

ii.    Forward HTTPS requests on TCP/IP Port 443 to internal IP address of web server

2. dMZ established for Web server IP Addresses

- TCP Port 1433(SQL) available between web server and B1 server, regardless of location of eCommerce database, that being on the web server(local) or on the B1 server(remote)

* Web server hosted with B1 server on premise

1. Firewall/Router configuration

- TCP Port 1433(SQL) available between IP Address of hosted web server and B1 server for synchronization

i.    Recommended to run in a secure tunnel(SSH) or encrypted connection using VPN

ii.   This most likely has already been done during setup of the solution to enable any synchronization between eCommerce and B1

Domain Name

1.    Register desired domain name with any provider

• Network Solutions
• DirectNic
• Verisign

Note : Do not configure DNS servers or records until completed with all go live steps. This is how you make the site available to the world.

2.   You must have a domain name to complete the SSL certificate process

SSL Certificate

1. Generate request within IIS

2. Register account with SSL provider

• Network Solutions
• Verisign
• Thawte

128-bit regular strength will suffice

Avoid using own Certificate Server if deploying website to non-internal customers as the browser will not be set to accept the certificate as it does not trust a non-standard certificate authority

3. Install on web server in IIS

• Choose port 443 for SSL
• Consider using tertiary domain name(store.example.com) for SSL transactions

4. Enable eCommerce for secure checkout

If the eCommerce website will be accepting credit cards it is necessary that the billing page, where the credit card numbers are entered, be encrypted with SSL between the client(browser) and server.  The following steps will enable the billing page to be SSL secured.

i.    Within the administration, choose Layout - Webflow

ii.    Click the new icon, while Checkout is displayed in the dropdown

iii.    In the field labeled "Source page" enter "commerce/cart.aspx"

iv.    In the field labeled "Next page" enter "commerce/shipping.aspx"

v.    Tick the box labeled "Secure"

vi.    Click the save icon

vii.    Click the new icon, while Checkout is displayed in the dropdown

viii.    In the field labeled "Source page" enter "commerce/shipping.aspx"

ix.    In the field labeled "Next page" enter "commerce/billing.aspx"

x.    Tick the box labeled "Secure"

xi.    Click the save icon

xii.    Click the new icon, while Checkout is displayed in the dropdown

xiii.    In the field labeled "Source page" enter "commerce/billing.aspx"

xiv.    In the field labeled "Next page" enter "commerce/verify.aspx"

xv.    Tick the box labeled "Secure"

xvi.    Click the save icon

xvii.    You may wish to include links on the theme that take the shopper out of SSL mode, as this can be taxing on the server. Consider adding a "Return to site" link that is not HTTPS.

Credit Card Gateway Testing

1. Registration with approved gateway

• Authorize.Net
• Payflow Pro
• Ogone(UK)
• SkipJack

2. Configure eCommerce with login information provided by gateway

Administration - Setup - Credit Card Gateways

Try test transactions using test credit card numbers

i.    Test numbers available from provider or use 4111111111111111 for Visa 1/2020 for expiration

Verify information in payment gateway admin

Note: eCommerce has internal number format checking on billing page of checkout

IIS Configuration

* Multi-Homed

Multiple IP addresses assigned to single network device or multiple network interface(s) on single server

i.    Select IP address in website properties in IIS

ii.    Define host header details(www.example.com, port 80)

1.    Can assign more than one domain to a single IP

2.    Can be used for tertiary domains(store.example.com)

Single IP address assigned to single network interface
Select IP address in website properties in IIS

Messaging

This will configure the messaging service so that order confirmation and shipment notifications will be sent.

1. Go to Administration - Config Settings - Messaging
If using remote SMTP server, such as internal Exchange server

-          Enter the FQDN(Fully Qualified Domain Name) or IP address in the SMTP Host field

-          Enter a valid email address or account for sending mails in the SMTPAuthUsername field and if there is a password enter it into the SMTPAuthpassword field

-          Set the sleep field to the desired interval(in minutes) you wish the service to send all messages queued in the eCommerce db

-          Tick the SendOrderDocuments and SendDeliveryNotices boxes

-          Make sure port 25 is available between web server and internal SMTP server

-          You will also most likely have to configure Exchange or your SMTP server to accept connections from the web server.

If using a local SMTP server

-          Some versions of Windows ship with a free SMTP server, the default Pickup directory for messages is C:\Inetpub\mailroot\Pickup. Enter this into the field MailPickupDirectory

-          There is a local system service, SMTP, that needs to be enabled for messages to be picked up and sent.

-          It is recommended that you configure the local SMTP server to use your ISP's mail server or your internal mail server as a smart host. Documentation on how to do this is included in Windows help.

-          Other settings for remote server then also apply

Also assign mail templates for invoice and shipment to the desired theme to apply the CSS found in this theme to the emails going to shoppers.

-          Administration - Layout - Mail Templates

 Themes Configuration

Associate domain with Theme

Administration - Layout - Theme Designer - Theme details

i.    Enter domain name in the Associated domain field

ii.    Check Default if this theme should load for first time visitors to this domain by default

iii.    This sets the %%VirtualPath%% themes variable to point to this domain

Final DNS configuration

When you are ready to start accepting traffic, go back to the site that you registered your domain name and edit the DNS records for the domain to point to a registered DNS server. This could be provided by your ISP, hosting provider or the domain name company itself. Do not try to use your own internal DNS server, unless you feel comfortable with the knowledge you have regarding this.

Then edit the A records for the domain and point them to the external IP address of either your hosting provider or your own public facing router. You do not need to do this separately for SSL, one A record should suffice.

You will now be accepting all traffic that comes to your registered domain. It may take up to 24-hours to propagate the information in the DNS records to the rest of the Internet. 

A backup archive of every file in the folder for the website(inetpub\wwwroot\zedsuite) is made and placed in the installer directory C:\Program Files\zedIT..\Installer, so you will always have a backup of the files as they were. There is also a backup of the db made and placed in this folder as well, so any changes made to the theme in a theme slot(stored in db) will be backed up.

Also, although the upgrade replaces all files in the website folder, a list of only those files that were changed in the patch is included in the release notes. Meaning, you then only need to merge your custom changes made to default system files for the files that were changed in the patch; all others you can simply overwrite the new file with your custom changed file.

Say for instance patch 7.1.1 had an update to /commerce/cart.aspx and you have modified /commerce/cart.aspx as well. The upgrade will archive your file and replace it with the new /commerce/cart.aspx. Since this file was modified in patch 7.1.1 you should merge your changes into it.

If however, you modified /commerce/shipping.aspx and patch 7.1.1 did not change this file, you can simply place your custom shipping.aspx back, and overwrite the distributed shipping.aspx that came with 7.1.1

Upgrading from SAP Web tools 6 Service Pack 2 to zed eCommerce 7.4 requires knowledge of the Web tools product and should be completed by a person that performed the implementation or is familiar with it.

Customizations made to the Web tools distributed source code files will need to be reapplied to the zed eCommerce files, therefore some programming knowledge will also be necessary if this was done.

This document only serves as a guide and may not address every issue that could be encountered.  Please proceed with caution. 

Overview of steps:

• 1. Download and upgrade to SAP Web tools Service Pack 2(if necessary)
• 2. Uninstall SAP Web tools Service Pack 2 Installer and Synch manager
• 3. Install zed eCommerce Installer
• 4. Copy instances.xml file to zed eCommerce Installer directory
• 5. Open zed eCommerce Installer and upgrade instance
• 6. Launch zed eCommerce website and complete license key request, install received key
• 7. Install zed eCommerce Synch manager
• 8. Copy NPSynchConfig.xml file to zed eCommerce Synch manager directory
• 9. Launch zed eCommerce Synch manager
• 10. Complete synchronization as normal

Prerequisites:

Must be on SAP Business One eCommerce and WebCRM Service Pack 2 or later

This information is available on the about.aspx page of a web tools website  (ie. http://localhost/about.aspx)

NetPoint   2009.2.655.0

NetPoint.API   2009.2.655.0

NetPoint.CreditCards   2009.2.655.0

NetPoint.WebControls   2009.2.655.0

Web Tools Database   655

Make sure to create a test environment that is an exact copy of the live site, with B1 database and Web  tools database, and with copies of the customized files(if any)

Download Service Pack 2 for Web tools:

• 1. Go to http://service.sap.com/support -S number login required
• 2. Choose "Downloads" , "SAP Support Packages" , "Support Packages and Patches - Entry by Application Group" , "SAP Business One" , "SAP Business One 2007" , "SAP BUSINESS ONE WEB TOOLS 6" , "SAP BUSINESS ONE WEB TOOLS 6" , "Win32"
• 3. Choose the link in the "Download Object" column with the title "SAP Business One Web tools 6 SP02"

After downloading the zip file, extract the contents to the desktop of the web server and run setup.exe

 Upgrading the Web tools Installer to Service Pack 2

A message will display asking if you wish to upgrade - click yes

The upgrade will continue, stopping and starting the messaging service

After the upgrade is complete, open the Installer and upgrade the desired instance, by selecting it and clicking the Upgrade button.

The installer will create a backup of the database and web files, upgrade the database and replace all files with the latest versions 

Click Upgrade to begin this process, when it is complete the home screen will display

Uninstall the Web tools Installer

Uninstall SAP Business One Web tools Installer, via Add/Remove Programs in the control panel or the Start Menu - All Programs - SAP Business One eCommerce and WebCRM - Uninstall

Some of the files will remain in the Program Files\SAP\...\Installer directory and the website will continue to function 

Upgrade to zed eCommerce 7.4

Go to /softwaredownload.aspx

Username and Password is available upon request from your zedIT partner

After downloading the zip file, extract the contents to the desktop of the web server and run setup.exe

Install the zed eCommerce and WebCRM Installer

If a message asking if you would like to upgrade appears, click no and ensure that neither the Installer or Synch Manager are installed

If no message appears continue with the installation of the Installer using the setup program. 

You can install the installer on the web server and the synch manager on the B1 server, just as you would a normal installation of SAP Web tools.

Continue the installation...

After the setup program is finished you should see the icons for the programs you chose to install on the desktop.

Next copy the instances.xml file from C:\Program Files\SAP\SAP Business One Web tools\Installer to C:\Program Files\zedIT Solutions\zed Ecommerce and WebCRM\Installer. This file contains all the configuration data for the instance, including web files location, database connection info, and private key. We do this so that the zed eCommerce Installer knows where the locations of these assets are, so it can upgrade them.

Upgrade the old Web tools Instance

Open the Installer and upgrade the desired instance, by selecting it and clicking the Upgrade button.

The installer will create a backup of the database and web files, upgrade the database and replace all files with the latest versions.

Note: If you have customized aspx or ascx files that are distributed with the product(default system files), they will be replaced with default system files that are included with the latest version.

Place copies of these files in /assets/common/themes/"themeid". The upgrade process will not overwrite any files in this directory.  When finished upgrading, either use a Friendly URL for the item and category(see SEO Functions in 7.4) or use the Page Redirect plug-in within a theme slot(included with the 7.4 installation in the plugins folder)

The default system files you customized will be within the archive created in the Installer program files directory(C:\Program Files\zedIT\...\Installer). Check the release notes for a list of the default system files that have changed, and if you have changed one of those files, merge your changes into the new file. Otherwise, simply place your customized default system files back in the correct directory and overwrite the new default system files.

Click Upgrade to begin this process, when it is complete the home screen of the zed eCommerce Installer will display.

License new zed eCommerce Website

It is possible to have SAP Web tools and zed eCommerce on the same physical server, provided the licenses for both are in the BIN directory for each website.

Launch the website(default is http://localhost/zedsuite) and the license request form page should display

Complete the license request and email the license request key to support@zedit.com

Support will validate the request key and return a response key - please configure any spam filtering or blocking software to allow emails from support@zedit.com or this email may never arrive or will be delayed.

Return to website and enter response key and the site should now display.

Note: Upon entering the license response key you may get a .Net error. If this happens follow the steps below

• 1) Perform a search on the system drive (c:\) for any file with a .lic extension, making sure you include hidden files in the search.
• 2) The old SAP Web tools license file will be in a folder deep within the user profile directory called "Isolated Storage". Move(do not copy) this file to the BIN directory of the web tools website. By default this is Inetpub\wwwroot\B1Webtools\BIN. The Web tools website should still work.
• 3) Try to enter the license for zed eCommerce again. If this fails, save the license file itself in the BIN directory of the zed eCommerce website. (Inetpub\wwwroot\zedsuite\BIN)

Customized Source Files

If distributed source files were customized within SAP Web tools, they should have been copied to the aforementioned /assets/common/themes/themeid folder

For example, if the /catalog/partlist.aspx file had been modified to show more or less than the default number of records(20) then partlist.aspx should be placed in this folder. The upgrade will not overwrite the file if it is in this directory, but it will overwrite the /catalog/partlist.aspx file.

Use the Page Redirect plug-in within any theme slot to load the customized version of this file when the user navigates to /catalog/partlist.aspx. If not using a Friendly URL(eCommerce 7.4 only) on the category, you'll see the new full path( www.sample.com/assets/common/themes/themeid/partlist.aspx). If you are using Friendly URL you'll see the customized file, but with the shortened Friendly URL.

Load the website and test to make sure all customizations were correctly merged and that the website is functional.

Theme Slot Update

You may encounter an error when attempting to login to the new theme.  This is due to the addition of a new content placeholder in the commonlogin master page used to show the Express Checkout login field.  If the instance upgraded included a theme created in Web tools Service Pack 2 and was set as the default theme, or if you directed the browser to this theme you would see an error indicating the commonlogin master page does not contain this content placeholder.

To correct this issue, follow the steps below.

1) Open the theme details and go to the masters tab, and click on the link for commonlogin.master page

2)  The next window is the contents of the file, click the edit icon to edit

3)  By default, the main slot content contains the new user and login user slots highlighted below

4)  This should be updated with the new layout, copy the:

<asp:Content ContentPlaceHolderID="mainslot" ID="mainslotcontent" runat="server">
    <table width="100%" cellpadding="3" cellspacing="0" border="0">
   <tr>
    <td width="100%" valign="top" colspan="2">
   <asp:ContentPlaceHolder ID="messageslot" runat="server"></asp:ContentPlaceHolder>
    </td>
    </tr>
    <tr>
    <td width="50%" valign="top">
    <asp:ContentPlaceHolder ID="newuserslot" runat="server"></asp:ContentPlaceHolder>
    </td>
    <td width="50%" valign="top">
    <asp:ContentPlaceHolder ID="loginslot" runat="server"></asp:ContentPlaceHolder>
    </td>
    </tr>
    <tr>
    <td width="100%" valign="top" colspan="2">
   <asp:ContentPlaceHolder ID="expressslot" runat="server"></asp:ContentPlaceHolder>
    </td>
    </tr>
    </table>

</asp:Content>

5)  When finished click save and click the Home icon in the Administration Toolbar to view the theme

6) Logout from the theme and return to /common/accounts/login.aspx the page should load successfully.

Item Remarks Content Placeholder

In version 7.1.0 of zed eCommerce new functionality was introduced that synchronizes item remarks in Business One with a new field in zed eCommerce called "part remarks"

This new functionality included an update to the catalogpartdetail.master template and the content placeholder must be included in this template for the item detail screen to display in the  webstore.

Any theme created in a previous version must have this content placeholder within the catalogpartdetail.master

• 1) To edit the catalogpartdetail.master page, open the theme details and click the highlighted item below

• 2) Edit the master page by clicking on the edit icon

• 3) Enter this code in the master page in the desired location. For example between the partcrossell and the partnotes content placeholders

<asp:ContentPlaceHolder ID="partremarks" runat="server"></asp:ContentPlaceHolder>

• 4) Save

Uninstall Web tools Synch Manager

Ensure the Synchronization Service is stopped before continuing. If a synch is in progress, let it complete and then stop the service.

Uninstall the Web tools Synch Manager, via Add/Remove Programs  in the control panel or the Start Menu - All Programs - SAP Business One eCommerce and WebCRM - Uninstall

Some files will remain in C:\Program Files\SAP\...\Synch Manager directory

Run setup.exe and install the zed eCommerce Synch Manager

If you are prompted to upgrade, click no and ensure that the Synch Manager is fully uninstalled

Launch zed eCommerce Synch Manager

Copy NPSynchConfig.xml from C:\Program Files\SAP\...\Synch Manager to C:\Program Files\zedIT\Synch Manager

Open the zed eCommerce Synch Manager and complete a normal synchronization, do not initialize synch. You might see some upgrade scripts executed and a "Finished Synchall" in the log once the upgrade is complete.

The upgrade is complete