mozu q2 2015 release...volusion confidential page 3 of 24 access to this information is permitted...

MOZU Q2 2015 RELEASE

Release Notes

© Volusion, LLC. 2015

VOLUSION CONFIDENTIAL of 24 Access to this information is permitted only for authorized business purpose by authorized personnel subject to confidentiality and nondisclosure provisions.

Table of Contents

What’s New in Q2 2015 Release 3

Mozu Admin Updates 4

Admin General Settings 4

Restrict access to staged content 4

Update shopper passwords through the Mozu API 5

Catalog 6

Restrict product properties to Mozu Admin only 6

Input and display on-hand negative inventory quantities 7

Disable Locations 8

Orders 9

Capture and display interaction history for orders 9

Accept Japan Credit Bureau (JCB) credit cards 10

View line item order number and status 11

Add duty fees to orders 12

Extended Properties for cart and order 13

Marketing 14

Delete discounts 14

Site Builder 15

Improved widget controls 15

Dev Center Updates 17

Access web logs 17

Improved Dev Center users and roles grid 18

View applications or themes from the Installed Assets section 18

No Sandbox sites indexed 18

Configure search matching preferences with mm parameter 18

Product variant inventory status returned for category pages 18

Hypr date filter issues resolved 18

Integrations Updates 20

Application Updates 20

SDK Updates With the SDKs, you can now add, update, and delete credit card data with the credit card

resource. Here is an example using the .NET SDK: 20

Updating to Mozu Core 7 Theme 21

Duty fees displayed 21

JCB credit card option 21

Hiding Empty Categories 21

Store Affiliate Strings in Cart 21

Mozu Resolved Issues 22


What’s New in Q2 2015 Release

The following sections detail all the new features and updates included in the Mozu Q2 2015 Release. This release

includes new functionality and usability improvements.


Mozu Admin Updates

See what’s new in this release for Mozu Admin. Most updates you receive automatically. If there is manual work

required to upgrade a particular feature, there are instructions on how to do so.

ADMIN GENERAL SETTINGS

The following features are new for General Settings:

Restrict access to staged content

Update shopper passwords through the API

Restrict access to staged content

You may want to restrict who can view your staging site. For example, you may want to prevent unauthorized access

to upcoming sales or product information. To restrict access, you can require a user name and password to view the

staging site, and you can assign the Site Reviewer role to users with restricted access. You can also require user

authentication for your live site.

RESTRICT ACCESS

1. In Mozu Admin, select Settings>General Settings.

2. In the Site Authentication section, select Require Login to View Staging Site, Require Login to View Live

Site, or both.

3. Click Save.


ASSIGN SITE REVIEWER ROLE

You can also assign users you want to restrict to the new Site Reviewer role in Mozu. This role includes only two

behaviors:

Preview changes before they are published

View live site

To view this role, select Settings>General Settings>Roles. Go to Users to add this role.

Update shopper passwords through the Mozu API

You can update a single shopper password or do a bulk update of shopper passwords via the Mozu API. Now you can

sync passwords with external systems without having to know the shopper’s current password or use the reset

password workflow in the Customers Module. During the update, the account will be unlocked only if you set the

unlock flag. No password changed emails are sent when making this update via the API.

Tips for working with password updates through the API:

If a shopper updates his or her password at the same time the password update is taking place, a password

change confirmation email will be sent to the shopper. The confirmation code within the email is still valid

after the password has been updated through the API. These codes are valid as long as the email has not

expired; however, the shopper must use the password that was updated through the API as the old password

when creating a new one.

If an account has not hit the lock threshold (15 failed login attempts) and the password is changed through

the API, retry count resets when the password updates.

The new password cannot match any of the last four passwords. This is the same rule Mozu enforces when a

shopper updates his or her password.


UPDATE SHOPPER PASSWORD CODE SAMPLE

1. Add “Customer Password Update” behavior to application.

2. Issue a POST request (through the SDK you are using) to the following endpoints with associated payloads:

3. a. commerce/customer/accounts/Change-Passwords

{

"items": [

{

"accountId": <AccountId>,

"unlockAccount": <TrueOrFalse>,

"passwordInfo": {

"newPassword": <newPassordHere>

}

}

]

}

b. commerce/customer/accounts/{accountId}/Change-

Password?unlockAccount={unlockAccount}

{

"newPassword": <newPassord>

}

CATALOG

The following features are new for Catalog:

Restrict product properties to Mozu Admin only

Input and display on-hand negative inventory quantities

Disable Locations

Restrict product properties to Mozu Admin only

For product properties, you can restrict whether these appear on your storefront, in Mozu Admin, or both. For

properties that you designate as both, you can also choose whether to show or hide the property to your shopper in

the storefront. You might have a property you want your theme to access on the storefront, but you do not want it to

render and be viewable to your shoppers. In this case, you can choose to make it available to the storefront but hide it

from the shopper. Restricting this product information is not available for Options and Extras, as their intended use is

with shoppers. To restrict product properties:


1. In Mozu Admin, select Catalog>Product Types.

2. Select a Product Type.

3. In the Properties section, edit or add a property.

4. In the Display Group, select Admin&Storefront or Admin Only.

5. If you select Admin & Storefont, but you only want your theme to access the property on the storefront,

select Hidden from Shopper.

The screenshot shows an Oversized property that denotes extra-large items. In this example, we want our theme to

access this information, but we do not want to expose it to our shoppers, so the Display Group is set to Admin &

Storefront and Hidden from Shopper is selected.

Input and display on-hand negative inventory quantities

Mozu now allows negative on-hand inventory quantities, which allows you to manually enter negative quantities into

the inventory fields. You can also configure whether Mozu checks inventory levels prior to fulfillment.

NEW VALIDATE INVENTORY LEVEL ON FULFILLMENT SETTING

This new setting allows you to fulfill when inventory levels are zero or below. For existing clients, this setting is

checked by default. If you are a new Mozu customer, this setting is unchecked by default. If you are an existing client,

and you want to fulfill when inventory levels are at zero or below, uncheck this setting.

You can also use this setting to help you determine how many items you have fulfilled without available stock. For

example, if you uncheck Validate inventory level on fulfillment, you don’t have available stock, and you fulfill an item,

the inventory field will reflect a negative number for on-hand stock.

You can find this setting in Mozu Admin by selecting Locations.


NEW ADD ADJUSTMENT MODE

In previous versions, you used the Inventory Adjustment mode to set on-hand inventory. Now the Adjustment mode

has two modes: Add or Set. If you are in Add mode, you can tell Mozu how many items you have received and it will

automatically add this to the existing inventory count, even if you have negative inventory on hand. If you are in Set

mode, you can manually override the inventory count in the system.

1. Select Locations>Inventory.

2. Select Add for the Adjustment Mode.

3. Hover over a product you need to change the quantity and click to make it editable.

4. Use the arrow keys or type in your new quantity.

Disable Locations

If you have a Location you no longer need, you can disable it. However, you cannot disable locations that are defined

as the designated shipping locations for your site. Disabling a location prevents it from displaying in any drop-down

menu across Mozu Admin where active locations are displayed.

1. In Mozu Admin, select Locations. Select a location, click the gear icon, and select Disable.


You can easily review which locations are active or disabled with the Status column in the Locations Grid.

ORDERS

The following features are new for Orders:

Capture and display interaction history for orders

Accept Japan Credit Bureau (JCB) credit cards

View line item order number and status

Add duty fees to orders

Extended Properties for cart and order

Capture and display interaction history for orders

The Orders Page now includes an Audit Log section that displays when an order is created. This section helps you

track what tasks have been completed for an order, who completed the tasks, and when they were done. Knowing

what stage an order is in, who is working on the order, and when tasks are done can help you more easily serve your

customers. The Audit Log captures tasks done to an order from within Mozu and tasks done with an order from any

third-party integration that also works with your orders.


Click on an order and select Audit Log to view this information. Within the log, you can click on an entry to view

details of that audit information.

Accept Japan Credit Bureau (JCB) credit cards

You can now add Japan Credit Bureau (JCB) credit cards as an acceptable form of payment. You set up the JCB card per

payment gateway, and after you configure it, the card will appear as a form of payment at checkout. Shoppers with

both US and international addresses can checkout using the JCB card. To add the JCB card to your payment gateway:

1. In Mozu Admin, select Settings>Payment and Checkout.

2. In Payment Types, select a Payment Gateway.

3. Select JCB in the list of supported cards.


View line item order number and status

On the Order Details, Fulfillment, and Return sections of the Orders module, each line item in the order is now listed

with a unique number and status. Knowing the status of each line item within an order makes it easier to see where

the order is within the order lifecycle. If you cancel an action, the line item returns to its previous step. Line item

number and status do not appear on the Print Order Summary or Packing Slip. As the order moves through the

lifecycle, you will see the following for each line item status:

STATUS DEFINITION

Pending

Occurs once the line item is in a created state

Pending Fulfillment

Occurs once the line item is in a submitted state

Partially Packaged Occurs once part of a bundled or multiple item line item is partially packaged

Packaged Occurs if an line item was added to a fulfillment package

Partially Fulfilled

Occurs once part of a bundled or multiple item line item is partially fulfilled

Fulfilled

Occurs when the package was shipped, a digital gift card was fulfilled, or an in store pickup was picked up

Partially Returned

Occurs once part of a bundled or multiple item line item is partially returned

Returned Occurs once a line item on an order is part of an RMA


Add duty fees to orders

You can now add and track duty fees and tariffs at the line item and order level. You must use your own data source,

web service, and so on to determine the correct fee amount. Adding duty fees and tariffs ensures proper handling of

orders shipped to other countries. Like tax, the shopper cannot adjust the duty field, and when this fee is added, it is

combined with the tax field and displayed in the following areas:

Mozu Admin Order Editor Order details page and edit modal Order confirmation email Print order summary Storefront checkout Storefront order confirmation page

While duties and taxes display as one field, they are maintained as two separate fields on the order for reporting. Line item and order discounts do not impact duty fees on an order.

DUTY FEE SDK EXAMPLE

Here’s an example (using a mock client/SDK wrapper) of settings duty amounts on an order item as well as an order

for a particular order.

order.Items[0].DutyAmount = 25m; order.DutyAmount = 50.5m;

var createdOrder = await orderClient.CreateOrderAsync(order); // createdOrder.DutyTotal = 75.5m in this example where m means decimal in the programming language;


Extended Properties for cart and order

Cart and Order now have a property called “ExtendedProperties” that allow for the storage of an arbitrary number of

extended properties/tracking strings. These strings will persist from the cart to the order to allow Mozu admins to

support a variety of use cases: tracking references, marketing sources, affiliates, and so on.

When you create a cart from an order, all extended properties on the cart are retained and copied to the order when it

is created.

1. In Mozu Admin, select Site Builder.

2. Hover over your theme and select Settings.

3. In the Extended Properties section, select Enable Extended Properties (Tracking Strings).

4. Add the query strings you want to track as values in the Query Parameters text box. Enabling this theme

feature and specifying one or more querystring parameters will automatically track these querystring values

when items are added to a cart from product detail pages.

5. If you have content publishing turned on for your site, go to Mozu>Publishing. Publish your settings and

theme changes to enable the extended properties.


EXTENDED PROPERTIES EXAMPLE

1. You define affiliateId as a query string in Mozu.

2. The shopper visits “/p/t-shirt?affiliateId=A123” in their browser, where this page/URL is a product detail

page.

3. The shopper adds one or more t-shirts to the cart.

4. The cart for the user will now have an extended property with the key of “affiliateId” and the value of “A123.”

MARKETING

The following features are new for Discounts:

Tooltip help

Delete discounts

Tooltip help

Discounts now include tooltip help. Click the help icon to view more information:

Delete discounts

You might create a discount in error that you do not need. Now you can delete discounts in the Discounts Grid or in

the Discounts Editor.

Caution: You cannot delete discounts that have been used in a financial transaction.


Deleting discounts from the Grid:

1. In Mozu Admin, select Marketing>Discounts.

2. Hover over a discount, click the Gear icon, and select Delete.

Deleting discounts from the Editor:

1. In Mozu Admin, select Marketing>Discounts.

2. Click on a discount to display the Discount Editor.

3. Select More>Delete.

SITE BUILDER

The following features are new for Site Builder:

Improved widget controls

Automatically hide empty categories

Improved icons for Site Builder items

Improved widget controls

Now the widget move and delete icons are inside the widget area, which makes working with them easier. Hover over

a widget to see the icons. Here’s an example of the icons for the video widget:

Automatically hide empty categories

By default, Mozu now hides empty categories, For example, if you hide products that are out of stock and all products

within a category or sub-category are out of stock, Mozu will automatically hide the category or sub category. If all

sub-categories of a main category are empty, then Mozu will also hide the main category. Mozu hides the empty

category from navigation, search, faceting, the store footer, and anywhere a custom widget uses the category. There is

a caching delay of approximately twenty minutes before an empty category is hidden.


MANUALLY TURNING OFF AUTO-HIDE CATEGORIES

You can manually turn off the auto-hide empty categories feature by removing the .isEmpty property in your

site-nav.hypr file:

1. Open your site-nav.hypr file. The .isEmpty property is added to links, sub-links, and sub-sub-links.

2. Remove all instances of the .isEmpty property on the links. There are multiple instances of the .isEmpty

property, and you must remove them all to turn off this feature.

Here is an example of the syntax when the feature is ON:

{% if not sublink.isHidden and not sublink.isEmpty %}

Here is an example of the syntax when the feature is OFF: {% if not sublink.isHidden %}

Improved icons for Site Builder items

Site Builder includes new icons to help you distinguish between pages, templates, folders, and other items in the user

interface.


Dev Center Updates

Dev Center includes the following updates to theme and application development:

Access Web logs

Improved Dev Center users and roles grid

View applications or themes from the Installed Assets section

No sandbox sites indexed

Configure search matching preferences with mm parameter

Product variant inventory status returned for category pages

Hypr date filter issues resolved

Access web logs

If you have Amazon Simple Storage Service (S3) or an FTP service, you can use the Mozu Import/Export application to

export Mozu web logs to your data storage. The web logs contain details on storefront errors, such as broken links or

images not loading.

You must have an Amazon S3 account or an FTP service account and the Mozu Import/Export application to access

this feature. If you need the Mozu Import/Export application, request this from your Mozu Account Executive.

By default, web logs are disabled. Enable them with these steps:

1. Navigate to the Import/Export application (Select Mozu Admin>General

Settings>Applications>Import/Export).

2. Select Configuration.

3. In the Export tab, select Web Logs.

4. In the Export Data dialog, enter your information, select an Export Interval, and select Enable Web Log

Export.


Improved Dev Center users and roles grid

In Mozu Dev Center, we’ve improved the usability of the Users and Roles grid. These updates make the following

actions easier:

Add new users and send their invitation email

Assign roles

Duplicate roles, customize role behavior, and delete roles

Edit user details and expand roles for those who have multiple roles

View user status and the user’s time and date of last log in

View applications or themes from the Installed Assets section

You can navigate to installed applications and themes from the Sandbox Editor in Dev Center:

1. Select the sandbox you want to view the installed applications or themes.

2. Select the Installed Assets section, click the Gear icon and select View to see your application or theme in the

respective editor.

No Sandbox sites indexed

By default, when you provision a new sandbox or site from a sandbox, the site header contains X-Robots-

Tag:noindex, nofollow. This meta tag prevents development sites from being indexed or found by Web

crawlers. Any new production sites provisioned will not contain this meta tag so that they can be indexed.

Configure search matching preferences with mm parameter

Now Mozu allows you to configure your own search preferences by setting the Solr minimum match, mm, parameter.

The mm parameter indicates the percent of terms in a search query that must be contained in the search results. The parameter takes the number of words in a query*the number of words in your search, and rounds down. The default value is 75%, and if you do not set an explicit value, Mozu will use 75%. The max value is 100%, which means all of the search results must include all of the terms from the search query. The higher the percentage, the more narrow results you will return. Valid values for the Mozu implementation of this parameter are integers 0-100. You can also enter a negative percent value. For example, an mm parameter value of 50 means 50% of the query terms rounded down must be contained in the search results. 50% in a five word query will return results where any 2 of the query words are matched. -50% in a five word query will return results where any 3 of the query words are matched. For more information about the mm parameter, refer to the Solr documentation: https://wiki.apache.org/solr/ExtendedDisMax#mm_.28Minimum_.27Should.27_Match.29

Product variant inventory status returned for category pages

You can now see the inventory status of product variations without the need to do a post. Product variations are now

returned on the GET (get product, get products, and so on) on category pates and in search results.

Hypr date filter issues resolved

We have now updated the hypr date filter to be cross-compatible with the Django date filter. The Django date filter

uses the common PHP date format syntax. Previously, the date filter partially supported PHP date format strings and

partially supported .NET format strings. With this update, we now fully support PHP date format strings and as a

https://wiki.apache.org/solr/ExtendedDisMax%23mm_.28Minimum_.27Should.27_Match.29


consequence, any workaround using .NET date format strings will no longer work. If you have .NET date format

strings, update them to PHP date format strings.


Integrations Updates

Application Updates

Mozu integration applications receive the following updates:

Updates to Avalara application: Refer to the application version history for more details:

http://mozu.github.io/IntegrationDocuments/Avalara/versionhistory.html

Updates to BazaarVoice Conversations application: Refer to the application version history for more details:

http://mozu.github.io/IntegrationDocuments/BazaarVoice/versionhistory.html

New Power Review application: The Mozu PowerReviews Enterprise Application seamlessly integrates your

PowerReviews account with your storefront so that you can start displaying and generating reviews on your

product and category pages. With the Mozu PowerReviews Enterprise Application, you can import

PowerReviews content on demand or at scheduled intervals between 1 to 12 hours, ensuring that your

storefront is kept up to date with the latest available reviews. Refer to the configuration guide for more

details: http://mozu.github.io/IntegrationDocuments/PowerReviews/Mozu-PowerReviews-App.htm

Visit http://www.mozu.com/ecommerce-app-center to learn more about applications available for integration with

Mozu. Visit http://developer.mozu.com/tools to find links to the Mozu In-Store Sales Assistant and the Mystic Sports

storefront:

In-Store Sales Assistant App: An extension of the Mozu platform giving sales associates immediate access to

product, customer and order data. It was designed to help sales associates be more responsive to consumer

needs.

Mystic Sports: A Mozu storefront complete with products and customer data designed with current best

practices. Use these storefront example to learn more about the Mozu platform.

SDK Updates

With the SDKs, you can now add, update, and delete credit card data with the credit card resource. Here is an example

using the .NET SDK:

var paymentResource = new PublicCardResource(new ApiContext(TenantId));

var card= paymentResource.CreateAsync(new PublicCard {

CardHolderName = "test",

CardIssueMonth = 01,

CardIssueYear = 2014,

CardNumber = "4111111111111111",

CardType = "VISA",

ExpireMonth = 11,

ExpireYear = 2020,

Cvv = "123"

}).Result;

http://mozu.github.io/IntegrationDocuments/Avalara/versionhistory.html

http://mozu.github.io/IntegrationDocuments/BazaarVoice/versionhistory.html

http://www.mozu.com/

http://mozu.github.io/IntegrationDocuments/PowerReviews/Mozu-PowerReviews-App.htm

http://www.mozu.com/ecommerce-app-center

http://developer.mozu.com/tools


Updating to Mozu Core 7 Theme

You receive some Q2 2015 features automatically, but some features require you to manually update your theme

files to use the new features.

To view the changes we made from Core 6 to Core 7, view the comparison on GitHub:

https://github.com/Mozu/core-theme/compare/core6...master

On the Mozu GitHub repository, we explain what we’ve changed for these new features, and we have a diff of the

files to show you the code we updated. Here are the following features that are new in Core 7 that require theme

updates:

DUTY FEES DISPLAYED

Learn about the duty fee feature: https://github.com/Mozu/core-theme/pull/12

Review the file changes we made for the duty fee feature: https://github.com/Mozu/core-theme/pull/12/files

JCB CREDIT CARD OPTION

Learn about the JCB credit card option feature: https://github.com/Mozu/core-theme/pull/13

Review the file changes we made for the JCB credit card option feature: https://github.com/Mozu/core-

theme/pull/13/files

HIDING EMPTY CATEGORIES

Learn about the hiding empty categories feature: https://github.com/Mozu/core-theme/pull/11

Review the file changes we made for the hiding empty categories feature: https://github.com/Mozu/core-

theme/pull/11/files

STORE AFFILIATE STRINGS IN CART

Learn about the storing affiliate string feature: https://github.com/Mozu/core-theme/pull/10

Review the file changes we made for the storing affiliate strings in cart feature: https://github.com/Mozu/core-

theme/pull/10/files

https://github.com/Mozu/core-theme/compare/core6...master

https://github.com/Mozu/core-theme/pull/12

https://github.com/Mozu/core-theme/pull/12/files











Mozu Resolved Issues

The Q2 2015 release includes the following resolved issues:

SALESFORCE ID ISSUE ID RESOLUTION

00002957 59438 Corrected an issue where filtering by greater than returned greater than or equal to data.

00008622 47057 Corrected an issue where users did not receive the “back in stock” email.

00003114 47114

Corrected an issue where navigating in Mozu Admin from a product catalog page to an inventory page did not work.

00006163 00009684

59626 Corrected an issue where editing the phone number in MyAccount settings did not save.

00006827 58350

Corrected an issue where dragging and dropping categories within the catalog module were not saved.

00006953 51385 Corrected an issue where categories were duplicated in Mozu Admin discount conditions.

00007005 51476 Corrected an issue where cross-sell attributes did not function when manually re-added.

00007572 53217

Corrected an issue where product search results within the Mozu Admin catalog module were inaccurate.

00007629

52473 Corrected an issue where a catalog was not created correctly.

00007713 54199 Corrected an issue where products were not showing properly on category pages.

00008476 58267 Corrected an issue where filters were not ordered properly.

00008874 57611 Corrected an issue where the primary key error was displayed.


SALESFORCE ID ISSUE ID RESOLUTION

00009106 59149 Corrected an issue where pagination arrows in the storefront were not working properly.

00009285 58957 Corrected an issue where hidden categories were displayed on the storefront.

00009623 59538 Corrected an issue where facet range ordering did not work properly.

41874

Corrected an issue where the sort order of the store front did not match the sort order defined in Site Builder.

50557 Corrected an issue where Site Builder assets lacked a cache ID tag.

52202 Corrected an issue where transactional emails were not sending properly.

60766

Corrected an issue where orders could not be canceled if they included items and an authorized payment.