What’s New in Digital StoreFront 8.4
Copyright © 2004 - 2015 by Electronics for Imaging, Inc. All Rights Reserved. EFI Digital StoreFront | What’s New in Digital StoreFront 8.4
July 2015Digital StoreFront version 8.4 Document version 1.00
This publication is protected by copyright, and all rights are reserved. No part of it may be reproduced or transmitted in any form or by any means for any purpose without express prior written consent from Electronics for Imaging, Inc. Information in this document is subject to change without notice and does not represent a commitment on the part of Electronics for Imaging, Inc.
This product may be covered by one or more of the following U.S. Patents: 4,716,978, 4,828,056, 4,917,488, 4,941,038, 5,109,241, 5,170,182, 5,212,546, 5,260,878, 5,276,490, 5,278,599, 5,335,040, 5,343,311, 5,398,107, 5,424,754, 5,442,429, 5,459,560, 5,467,446, 5,506,946, 5,517,334, 5,537,516, 5,543,940, 5,553,200, 5,563,689, 5,565,960, 5,583,623, 5,596,416, 5,615,314, 5,619,624, 5,625,712, 5,640,228, 5,666,436, 5,745,657, 5,760,913, 5,799,232, 5,818,645, 5,835,788, 5,859,711, 5,867,179, 5,940,186, 5,959,867, 5,970,174, 5,982,937, 5,995,724, 6,002,795, 6,025,922, 6,035,103, 6,041,200, 6,065,041, 6,112,665, 6,116,707, 6,122,407, 6,134,018, 6,141,120, 6,166,821, 6,173,286, 6,185,335, 6,201,614, 6,215,562, 6,219,155, 6,219,659, 6,222,641, 6,224,048, 6,225,974, 6,226,419, 6,238,105, 6,239,895, 6,256,108, 6,269,190, 6,271,937, 6,278,901, 6,279,009, 6,289,122, 6,292,270, 6,299,063, 6,310,697, 6,321,133, 6,327,047, 6,327,050, 6,327,052, 6,330,071, 6,330,363, 6,331,899, 6,340,975, 6,341,017, 6,341,018, 6,341,307, 6,347,256, 6,348,978, 6,356,359, 6,366,918, 6,369,895, 6,381,036, 6,400,443, 6,429,949, 6,449,393, 6,476,927, 6,490,696, 6,501,565, 6,519,053, 6,539,323, 6,543,871, 6,546,364, 6,549,294, 6,549,300, 6,550,991, 6,552,815, 6,559,958, 6,572,293, 6,590,676, 6,606,165, 6,633,396, 6,636,326, 6,643,317, 6,647,149, 6,657,741, 6,662,199, 6,678,068, 6,707,563, 6,741,262, 6,748,471, 6,753,845, 6,757,436, 6,757,440, 6,778,700, 6,781,596, 6,816,276, 6,825,943, 6,832,865, 6,836,342, RE33,973, RE36,947, D341,131, D406,117, D416,550, D417,864, D419,185, D426,206, D439,851, D444,793. Trademarks
The EPS logo, AutoCal, Auto-Count, Balance, Best, the Best logo, BESTColor, BioVu, BioWare, ColorPASS, Colorproof, ColorWise, Command WorkStation, CopyNet, Cretachrom, Cretaprint, the Cretaprint logo, Cretaprinter, Cretaroller, DockNet, Digital StoreFront, DirectSmile, DocBuilder, DocBuilder Pro, DocStream, DSFdesign Studio, Dynamic Wedge, EDOX, EFI, the EFI logo, Electronics For Imaging, Entrac, EPCount, EPPhoto, EPRegister, EPStatus, Estimate, ExpressPay, Fabrivu, Fast-4, Fiery, the Fiery logo, Fiery Driven, the Fiery Driven logo, Fiery JobFlow, Fiery JobMaster, Fiery Link, Fiery Prints, the Fiery Prints logo, Fiery Spark, FreeForm, Hagen, Inktensity, Inkware, Jetrion, the Jetrion logo, LapNet, Logic, MiniNet, Monarch, MicroPress, OneFlow, Pace, PhotoXposure, PressVu, Printcafe, PrinterSite, PrintFlow, PrintMe, the PrintMe logo, PrintSmith, PrintSmith Site, Printstream, Print to Win, Prograph, PSI, PSI Flexo, Radius, Rastek, the Rastek logo, Remoteproof, RIPChips, RIP-While-Print, Screenproof, SendMe, Sincrolor, Splash, Spot-On, TrackNet, UltraPress, UltraTex, UltraVu, UV Series 50, VisualCal, VUTEk, the VUTEk logo, and WebTools are trademarks of Electronics For Imaging, Inc. and/or its wholly owned subsidiaries in the U.S. and/or certain other countries. All other terms and product names may be trademarks or registered trademarks of their respective owners, and are hereby acknowledged.
What’s New in Digital StoreFront 8.4 ... 5
Dynamic Forms in Variable Data Products ... 5
Progressive Disclosure of Form Elements ... 5
Benefits of Using Dynamic Web Forms ... 5
Binding Edge Print Option ... 7
Orientation in Special Pages... 9
A Use Case of Binding Edge and Special Page Orientation ... 10
Intelligent Ticketing: Recommend Alternatives ... 10
Address Book Searches ... 11
User Registration and DSFdesign Studio Jobs ... 12
Additional Variables in E-Mail Templates... 13
Improved File Retention and Removal ... 14
Garbage Collection Management ... 14
Changes to Integration with Google Drive and Picasa ... 16
Support for Fiery XF 6.1 Color Modes ... 17
Fusion Pro: Support for Images in Common Data ... 18
MIS Access to AccuZIP USPS Files ... 18
What Was New in Pre-8.4 Versions of Digital StoreFront... 19
Digital StoreFront 8.2 ... 19
Shopping & Checkout ... 19
Fulfillment Shopping ... 19
Products Displayed in List or Grid View ... 20
Fast Shopping ... 22
Rapid Checkouts ... 22
Intelligent (Enforced and Recommended) Ticketing ... 24
Re-Orders of Products with Changed Content or Ticketing Options ... 27
Changes to Content Files for Static Products ... 27
Changes to Ticketing Options ... 30
Single-Page Previews ... 30
Combo Mode for DirectSmile and FusionPro Products ... 33
PrintMessenger Redirection... 34
Multiple First-Level Domains (Self-Hosted Installations) ... 35
User Authentication: SAML 2.0 Support ... 36
SEO (Search Engine Optimization) Enhancements ... 37
Select Merchant Accounts at the Company and Department Levels ... 37
Kits and Matrix Products ... 38
High-Resolution Preview for FusionPro Products ... 38
Digital StoreFront 8.0 ... 39
Entity Model ... 39
Enhancements to AccuZIP Direct Mail Support ... 45
MIS Enhancements ... 46
Merchant Account Support ... 46
Fiery Central Support for Banner Pages (Separator Sheets)... 47
Variable Data Printing (VDP) Support ... 47
Digital StoreFront 7.6 ... 47 Digital StoreFront 7.4 ... 49 Digital StoreFront 7.2 ... 50 Digital StoreFront 7.0 ... 51 Digital StoreFront 6.7 ... 51 Digital StoreFront 6.6 ... 51 Digital StoreFront 6.4 ... 52 Digital StoreFront 6.2 ... 52 Digital StoreFront 6.0 ... 53 Digital StoreFront 5.10 ... 53 Digital StoreFront 5.6 ... 54 Digital StoreFront 5.4 ... 54 Digital StoreFront 5.2 ... 54
What’s New in Digital StoreFront 8.4
Dynamic Forms in Variable Data Products
Digital StoreFront’s dynamic web form functionality enables administrators to build “smart” VDP web forms that “respond” to buyer input by adapting subsequent data input choices based on previous data input choices. For instance, administrators can build conditional rules-based (if-then) logic into VDP forms.
For example, say a business card web form has a Region field (common element) with three options:
“Northeast,” “Southeast,” and “Midwest.” If you have defined rules for what happens when buyers select each of these options, then you can make buyers’ lives much easier. When buyers select “Northeast” from the “Region” drop-down list, your rule, which says “If Region is Northeast, then auto-populate the Address, Slogan, and Web address fields with the values in Address-NE, Slogan-NE, and Web Address-NE,” will save buyers several steps because they will not have to manually enter the address, slogan, and web address fields corresponding to their region.
This type of rules-based logic not only saves buyers time, but ensures consistency in how forms are filled out.
Progressive Disclosure of Form Elements
A dynamic web form can also be configured with progressive disclosure, based on your web form and rule settings. Progressive disclosure means that the form will be displayed to buyers one field at a time. This is useful, for instance, to ensure that subsequent fields “unfold” with valid options based on buyer input in previous fields.
How progressive disclosure happens: A dynamic web form displays fields in a particular sequence (based on the Order on page specified for the elements on the Products - Progress 2 Web Form page) until it reaches a field that has a rule assigned to it and requires the buyer make an input selection, at which point the form stops disclosing fields until the buyer selects an option. When the buyer selects an option, any rules associated to that form field will be applied and the form resumes disclosing fields until it reaches the next data element field that has a rule and no value assigned to it.
Benefits of Using Dynamic Web Forms
• Improved accuracy of data input: Buyers are prevented from entering inaccurate or inappropriate data.
• Single-sourcing of templates and products: Administrators can use a single VDP template and Digital StoreFront product for multiple workflows.
• Time-saving: Saves time for both administrators and buyers.
• Enhanced usability: Progressive disclosure lets administrators predefine the sequencing or flow of data input, which limits the amount of data requested at any time while improving the quality and accuracy of data input.
Rules are defined on the Manage Dynamic Web Forms Rules page:
Rules can be assigned to fields that are a list type input (i.e., checkbox, dropdown, etc.) and are: • Common VDP type – for FusionPro and EFI VDP
• Adors or Dial – for XMPie
• On the add rule section, define the rule: Source Value: From the pull-down list, select the source value for the field that will govern the rule. This is the “if” part of the rule, i.e., “If buyers select this value....”
• Action: From the pull-down list, select the type of action for the rule. This is the “then” part of the rule, i.e., “If buyers select this value, then take this action (hide, disable, enforce, recommend)....”
• Hide Element: Select this option to hide the value for another field when buyers select the specified source value. Buyers will not be able to see any options that are hidden.
Example: You would choose the Hide Element option if you wanted to hide a certain category of weekly specials when buyers select a particular product category. The effect of this rule would be: For Data Element “Instrument” if buyer selects Source Value “Guitar,” then hide the Destination Element “Weekly Drum Specials.”
• Disable Element: Select this option to automatically set the value for another field when buyers select the specified source value. Buyers will be able to see but not select any disabled options.
Example: You would choose the Disable Element option if you wanted to disable (without hiding) a certain category of weekly specials when buyers select a particular product category. The effect of this rule would be: For Data Element “Instrument” if buyer selects Source Value “Guitar,” then disable the Destination Element “Weekly Drum Specials.”
• Enforce Value: Select this option to automatically set the value for another field when buyers select the specified source value. Buyers will not be able to choose any other option than the forced value.
Example: You would choose the Enforce Value option if you wanted to automatically supply (force) an address when buyers select a particular home office source value. The effect of this rule would be: For Data Element “Home Office” if buyer selects Source Value “Boston,” then automatically set Destination Element “Address” to Destination Value “89 12th Avenue, St. 198, Boston MA 02108.”
• Recommend Value: Select this option to recommend a value for another field when buyers select the specified source value. Buyers will be able to either accept the recommendation or decline it and select another option.
Example: You would choose the Recommended Value option if you wanted to recommend that buyers select a particular currency when buyers select a particular country source value. The effect of the rule would be: For Data Element “Country” if buyer selects Source Value “United States,” then recommend that the buyer selects the Destination Element “Currency” Destination Value “US Dollar.”
• Enforce List: Select this option to automatically set the list to be displayed in another field when buyers select the specified source value. Buyers will be forced to choose one of the values on the enforced list.
Example: You would choose the Enforce List option if you wanted to automatically supply (force) a certain list of selections when buyers select a particular home office source value. The effect of the rule would be: For Data Element “Home Office” if buyer selects Source Value “Boston,” then
automatically set Destination Element “First Name” to display the list of employee first names for Boston (FN-Boston). This lets you limit the number of values displayed to buyers For example, If you set a rule for Field 1 that says for Data Element “Country” if buyer selects Source Value “US” enforce a list of US states for Field 5. Without enforcing the list, the buyer would be presented with a list of all US states, all Canadian provinces, etc.—potentially a very long list of values.
• Hide Value: Select this option to hide a particular value for another field when buyers select the specified source value. Buyers will not be able to see the hidden value.
Example: You would choose the Hide Value option if you wanted to hide a certain value from the category of weekly specials when buyers select a particular product category. The effect of the rule would be: For Data Element “Show Me” if buyer selects Source Value “Guitar Accessories,” then hide the Destination Value “Drum Sticks.”
• Destination Element: From the pull-down list, select the destination element to apply the action of the rule to.
The Destination Element and Destination Value are the part of the if-then rule that specifies what the action is applied to, i.e., “If buyers select this value, then take this action (hide, disable, enforce, recommend) on this element and/or value.”
• Destination Value: From the pull-down list, select the destination element to which you want to apply the action of the rule.
Binding Edge Print Option
Designed to be used with binding print options, the new binding edge option can be added to a ticket template to allow jobs to be bound on the left edge (as before), on the top edge, and on the right edge (to support languages that are read right-to-left).
The Binding Edge print service category and options are also compatible with intelligent (or conditional) ticketing (can be used in both site-level and ticket template-level intelligent ticketing).
The preview reflects the buyer’s selection. For example, for top edge binding, the first page looks like this:
The binding edge option is available on SmartStores and in Visual Product Builder on classic storefronts.
Orientation in Special Pages
For greater flexibility in designing the content of documents, administrators can enable orientation for special pages in ticket templates:
Orientation in special pages is useful for documents that include foldout inserts, especially when they are on media of different sizes (for example, an 8.5x11 document with a 17x11 folded insert).
When orientation is enabled for special pages, buyers will see an Orientation selection on the shortcut menu when they right-click a page:
Orientation will also be a choice in the Special Pages window:
A Use Case of Binding Edge and Special Page Orientation
The Binding Edge print service category lets buyers choose on which side certain pages in their documents should be bound—left, right, or top. This is useful, for example, in setting up jobs in which buyers use the Orientation print service to specify that certain special pages (e.g., those that are of a different size) are to be produced in a different orientation from the other pages in the document. For example :
Buyer has a 24-page bound document that she wants to be printed as follows:
• Pages 1-2 are to be produced on letter-size media, portrait orientation, and coil-bound on the left edge
• Pages 3-4 are to be produced on tabloid-size media, landscape orientation, folded with a half-fold, and coil-bound on the left edge (these pages will be a fold-out)
• Pages 5-24 are to be produced on letter-size media, portrait orientation, and coil-bound on the left edge Using the Binding Edge print service in combination with the Orientation print service (with special pages) will eliminate issues with the dynamic preview of the job, which would be problematic if, for instance, all pages in the job were set to be bound on the long edge, etc.
Intelligent Ticketing: Recommend Alternatives
Digital StoreFront 8.2 introduced the ability to enforce print option selections as well as recommend additional selections based on print options that buyers selected. Digital StoreFront 8.4 expands this functionality by
allowing you to define a ticketing rule that recommends an alternative option based on what a buyer selected. For example, you could set up rule that recommends coil binding as an alternative whenever a buyer selects stapling. If the buyer accepts your recommendation, the alternative option replaces the buyer’s previous selection (staples in this example). Recommendations for alternatives offer an opportunity to “upsell” your services.
You manage intelligent ticketing by selecting a ticket template on the Manage Ticket Templates page and clicking Manage Intelligent Ticketing on the Manage Ticket Template page.
To recommend an alternative to a selection the buyer makes, you set the Action to Recommend Alternate, select a print service on the left (e.g., 2 Staples Left Side), and select the recommended alternative(s) on the left (e.g., Coil Bind, Gray and Coil Bind, Clear). You can enter a note in the Message text box to let buyers know why you are recommending the alternate option.
You can recommend more than alternative from a particular print service category (as shown in the figure below) and you can recommend alternatives from multiple print service categories.
When buyers order a product based on this ticket template and select 2 Staples Left Side, a popup window recommends two alternative options: Coil Bind > Clear and Coil Bind > Gray. The buyer can then select one of these recommendations, which will replace the one previously selected (the staples in this example).
Address Book Searches
The address book search options have been expanded. More information is now displayed about each address, and buyers can search the address book using many more criteria (e.g., first or last name, e-mail, company, address, phone, etc.) when managing their address book or selecting recipients from the address book during checkout.
User Registration and DSFdesign Studio Jobs
Anonymous buyers who work on personalizing a DSFdesign Studio job are now given the option of registering on the site after they click Save Job (if they are not already registered). As a result, no work is lost – buyers can come back to the job later.
Anonymous buyers will also be able to register on the site after clicking Save Job when using Visual Product Builder on classic storefronts to customize other types of products.
Note For products using Classic Product Builder, the registration option is unavailable after you try to save a job as an anonymous buyer. It is also unavailable when customizing products other than DSFdesign Studio products on SmartStores.
Additional Variables in E-Mail Templates
Numerous new variables are available for inclusion in notification e-mails. For example, the OrderLineItemDetail variable lets you include the details of the product ordered by the buyer.
System Variables for Use in Email Notifications
[AdminFirstName] [AdminLastName] [ApprovalDetails]
[ApproverCompany] [ApproverFirstName] [ApproverFullName]
[ApproverID] [ApproverLastName] [ApproverMiddleName]
[AuthorizedAmount] [CaptureAmount] [CatalogItemDisplayAsName]
[CatalogItemLongDescription] [CatalogItemShortDescription] [CatalogProductType]
[CompanyName] [ContentFileNames] [CurrentOrderStatus]
[CustomerAddress1] [CustomerAddress2] [CustomerAddress3]
[CustomerCity] [CustomerCostCenterNumber] [CustomerCountry] [CustomerCustomField1] [CustomerCustomField2] [CustomerCustomField3]
[CustomerCustomField4] [CustomerCustomField5] [CustomerDefaultPrintShopAddress] [CustomerDefaultPrintShopEmail] [CustomerDefaultPrintShopName] [CustomerDefaultPrintShopPhone] [CustomerDepartment] [CustomerEmailAddress] [CustomerFirstName]
[CustomerFullName] [CustomerLastName] [CustomerMiddleName]
[CustomerPhone] [CustomerState/Province/Region] [CustomerTitle] [CustomerZip/PostalCode] [DeliveryAddress] [DeliveryCompany]
[DeliveryEmailAddress] [DeliveryMethod] [DigitalDownloadDetailsVariable] [DigitalDownloadIncluded] (Yes/No) [Handling] [ImpressionColorMode] (Color/B&W) [ImpressionType] (Simplex/Duplex) [ItemStatus] [ItemTax]
[JobName] [JobQuantity] [JobTotal]
[Media] [MISCommunicationFailureDetails] [MISDataFailureDetails] [OrderApprovalAmount] [OrderApprovalCustomerQualification] [OrderApprovalDateTime] [OrderApprovalProduct] [OrderApprovalReason] [OrderApprovalReasonNeeded] [OrderApprovalStatus] [OrderApprovalType] [OrderApproverEMails]
[OrderApproverLevel] [OrderApproverName] [OrderDate]
[OrderDeclinedReason] [OrderDueDateTime] [OrderDueDateTimeOld] [OrderLineItem] [OrderPlacedPrintShopAddress] [OrderPlacedPrintShopEmail] [OrderPlacedPrintShopHoursOfOperation] [OrderPlacedPrintShopName] [OrderPlacedPrintShopPhone]
[OrderTotal] [OrderTotalOld] [OutputDevice]
[OutputDeviceId] [PaymentMethod] [PaymentMethodDetails]
[PaymentMethodNumber] [PreviousOrderStatus] [PrintShopAdministratorFirstName] [PrintShopAdministratorLastName] [PrintShopAdministratorMiddleName] [PrintShopEMail]
[PrintShopPhone] [ProductIcon] [ProductName]
[ProductType] [QuantityShipped] [ShipmentDetailsVariable]
[ShipmentInstructions] [ShipmentStatus] [ShipmentTrackingCode]
[ShipperURL] [ShippingCharges] [ShippingQuantity]
[ShipToAddress] [ShipToEMail] [ShipToName]
[ShipToPhone] [SpecialInstructions] [SubTotal]
[Taxes] [UnitPrice] [Upload date and time]
Improved File Retention and Removal
You now have greater control over how long files are stored in the system and when Digital StoreFront performs “garbage collection,” which is the process of removing files from the system. For example, you can control when buyer-uploaded content files, production PDFs (generated by Digital StoreFront), and credit card transactions logs are removed. You can also control file removal at the company level as well as the site level. The File Expiration section in Site Settings > Basic Settings now includes some new settings:
• Files: These are files buyers upload when creating products (ad hoc, DSFdesign Studio, VDP). These files include images, text documents, CSV data list files, images saved to galleries, etc. and both the original files and converted PDF files.
• Job Files: These are the files Digital StoreFront generates in the process of producing jobs.
Note that FusionPro and DSFdesign Studio job files are not automatically cleaned up using this file expiration setting.
• Saved Files: These are files buyers have saved for later use.
• Credit Card Transactions: These are files associated with credit card order transactions stored in the transactions table in the database.
Periodically purging these files will cause the Credit Card Transaction page to load faster.
In the Company settings, you can override the site-level File Expiration settings if necessary for Files, Saved Files, and Credit Card Transactions:
The default is Use Site Level File Expiration Settings.
Garbage Collection Management
Digital StoreFront 8.4 introduces a more robust set of tools to help administrators manage temporary files on their sites. The Manage Garbage Collection page enables them to delete specified file stores on demand. The accumulation of files can degrade system performance and consume massive amounts of disk space. The controls on this page let administrators prevent or remedy this by cleaning up temporary files, uploaded files,
support logs, etc., as needed.
You can add or edit temporary folders/file extensions to delete at specified intervals.
Reviewing the folder structures of uploaded and ticketed files on the Folder Structures tab will help you analyze how much disk space each node is consuming and therefore make better decisions about which folders/file extensions to delete.
The number in parentheses indicates how much disk space in gigabytes (GB) a particular node is consuming.
Clicking Show Ticketed Folders Structure lets you view the ticketed folders by date.
Changes to Integration with Google Drive and Picasa
Google Drive is a free cloud-based file-sharing service that enables users to access photos, documents, and videos from anywhere. Any file saved to the user’s Google Drive will automatically save to all their computers, phones, and even the Dropbox website. Digital StoreFront’s workflow integrates with Google Drive so customers can select their Google Drive files and upload them to Digital StoreFront as they would any other files stored on a local computer. Picasa is a free cloud-based application for organizing, managing, and sharing
image files. Digital StoreFront’s workflow integrates with Picasa so customers can select their Picasa files and upload them to Digital StoreFront as they would any other files stored on a local computer.
In May 2015, Google introduced a new API (OAuth 2.0 API) for integrations with its services such as Google Drive and Picasa. If you allow (or plan to allow) buyers to download documents from Google Drive and/or Picasa, you must obtain a Client ID and Client Secret by creating a project in the Google Developers Console (accessible from a link on the Site Settings > Basic Settings tab):
You will also have to register your site URL as well as any branded company short URLs or entity short URLs with Google.
Then you will enter the ID and secret Google provides in the Cloud Providers section on the Site Settings > Basic Settings tab.
Once the admin configures Google Drive and/or Picasa in the Site Settings, downloads from those services will work as before – buyers will experience no change.
Support for Fiery XF 6.1 Color Modes
To support Fiery® XF 6.1 (and therefore improve support for EFI VUTEk® and Jetrion® printers), the Color Mode print service category in Digital StoreFront includes the following new color modes:
• CMYKV • CMYKOV • CMYKcmO • CMYKcmV • CMYKcmOV • CMYKRB
Fusion Pro: Support for Images in Common Data
FusionPro combo products (ones with both common and versioned data) can now include common images. (This was not possible in Digital StoreFront 8.2.)
MIS Access to AccuZIP USPS Files
When an MIS is integrated with Digital StoreFront, the USPS files that are generated by AccuZIP can now be accessed from the MIS. You no longer need to get the files from within Digital StoreFront.
What Was New in Pre-8.4 Versions of Digital StoreFront
Digital StoreFront 8.2
Shopping & Checkout
Digital StoreFront 8.2 adds several new features and enhancements to improve your customers’ buying experience.
You can now create fulfillment categories that make it easier for buyers to shop for products that require no buyer input (e.g., non print products, static products that cannot be customized, or digital downloads). A fulfillment category lets buyers select multiple products and then click an Add All to Cart button to place all the selected products in the cart at once.
Fulfillment categories apply to SmartStores only.
On the admin side
On the Manage Categories page, you can open or create a category, go to the settings, select the Is Fulfillment Category check box, choose whether you want products in the category to be displayed in List View or Grid View, and save the category.
If you are upgrading to Digital StoreFront 8.2, note the warning about resolving any HTML or style sheet conflicts on a storefront before publishing the fulfillment category to it.
To turn on fulfillment shopping in the Featured Products section of a SmartStore, on the Edit Page Elements & Styles page in SmartStore Builder, you must select Enable Fulfillment Shopping.
Note that these storefront settings apply to the featured products and search results but have no effect on category settings. All other category behavior is governed by the category settings.
On the buyer side
When buyers display the contents of a fulfillment category, an Add All to Cart button is always displayed. This lets buyers know that they can select multiple products and add them all to the cart at one time. Buyers just need to enter or select a quantity for the products they want (selected products will be shaded) and then click Add All to Cart.
If a fulfillment category includes a product that requires customizing, the product cannot be added to the cart as part of a group. Buyers must customize the product as usual and add it to the cart individually.
If list view was enabled for the storefront (see “Products Displayed in List or Grid View“ below), buyers
may want to switch to list view to expedite product selection.
What happens after products get added to the cart depends on how the storefront was configured. See “Fast Shopping“ on page 22.
Products Displayed in List or Grid View
As of Digital StoreFront 8.2, you can give buyers the option of displaying products in a category in grid or list view. Grid view is the standard “block-style” display available up to now; list view is a table-style listing which makes it possible to display more products at a time. The ability to switch between grid and list view must be set at the storefront level, but you can then specify a default view for a category (which buyers can change if they want). For example, you may want a fulfillment category with many products to be displayed in list view by default. This makes it faster for buyers to select multiple products at a time.
The ability to switch between grid and list view applies to SmartStores only.
If you are upgrading to Digital StoreFront 8.2, storefronts are displayed in grid view by default. If you want the option of displaying products in list view, you must set this at the storefront level and reconcile any CSS/HTML discrepancies.
On the admin side
You can use a new category setting to control the default product listing style for a category.
If you publish a category to a storefront that does not support list view, selecting List View in the category settings will have no effect – products will be listed in grid view and buyers will not be given the option to change the view.
On the buyer side
If list view is supported on a storefront, new buttons are available at the top of each category to let buyers switch between views. The default view is based on the category settings (as shown above).
You can now configure a SmartStore to allow buyers to continue shopping after they add a product to the cart instead of being taken immediately to the shopping cart to begin checkout after adding each individual item. The ability to keep shopping is also known as “fast shopping” because buyers are not interrupted (by being taken to the cart) when they are purchasing multiple products.
Configurable Cart Behavior On the admin side
On the Edit Page Elements and Styles page in SmartStore Builder, you can control what happens after buyers click Add to Cart (or click Add All to Cart in a fulfillment category).
The default behavior is Add + Goto Cart. To allow buyers to keep shopping, select Add + Continue Shopping. This is a storefront-wide setting.
When you are upgrading to Digital StoreFront 8.2, the ADD TO CART BEHAVIOR options will be disabled if there are conflicts in the HTML and style sheet for the storefront. A message will tell you what to do (close the SmartStore Builder, go to the Storefront Management page, click the conflict icon, and resolve the conflict).
The default behavior after upgrading to Digital StoreFront 8.2 will be Add +_Goto Cart, which is consistent with the way the system behaved prior to upgrade.
On the buyer side
Depending on what was selected in SmartStore Builder, buyers will either continue shopping after they add products to the cart or be placed in the cart to begin checkout. If they automatically continue to shop, buyers can just go to the cart when they are ready to check out. Alternatively, if buyers are placed in the cart after they add products to it, they can go back to shopping if they want.
You now have a choice of two additional types of checkout that can be configured for a company: rapid checkout and very rapid checkout.
You select the type of checkout you want on Manage Company page under Checkout Settings. Click to switch from
The table below shows the standard, rapid, and very rapid checkout workflows: Standard Checkout Workflow
In the shopping cart, buyers:
Rapid Checkout Workflow In the shopping cart, buyers:
Very Rapid Checkout Workflow In the shopping cart, buyers: 1: Click Proceed to Checkout. 1: Click Proceed to Checkout. 1: Click Proceed to Checkout. 2: Specify shipping options on the
2: Specify shipping options on the Shipping page.
2: Specify shipping and payment options on Rapid Checkout pop-up window.
3: Click Proceed to Payment. 3: Click Proceed to Payment. 4: Specify payment options on the
4: Specify payment options on Rapid Checkout pop-up window.
5: Click Place My Order. 5: Click Place My Order. 3: Click Place My Order.
Buyers skip the Payment page in
Buyers skip the Shipping and Payment pages in the checkout process.
All Payment Types Supported Supported Payment Types: — Pay At Store
— Cost Center — Accounting Codes — PO Number
Supported Payment Types: — Pay At Store
— Cost Center — Accounting Codes — PO Number Rapid Checkout
If rapid checkout is configured for a company, buyers complete a Rapid Checkout payment window instead of the standard payment page:
Rapid checkout can be configured only if a company uses the following payment methods: Pay at Store, PO Number, Cost Center, and Accounting Codes. If a company uses other payment methods, rapid checkout will not work (and the standard checkout process is used instead).
If Pay at Store is the only payment method defined for a company, the Rapid Checkout window is bypassed altogether – buyers are taken directly to the Order Confirmation page.
Very Rapid Checkout
If very rapid checkout is configured for a company, buyers skip the standard shipping and payment checkout steps and select a shipping and payment method in a popup window:
If a buyer selects a shipping method that is not Customer Pickup, the order is automatically shipped to the address in the user’s profile. If you offer very rapid checkout, make sure buyers have current addresses in their user profiles.
If Pay at Store is the only payment method defined for a company and only one delivery method is available, the selection of a shipping and payment method is bypassed altogether – buyers are taken directly to the Order Confirmation page.
If you configure either rapid or very rapid checkout, EFI recommends that you let your buyers know what to expect during the checkout process.
Intelligent (Enforced and Recommended) Ticketing
Digital StoreFront has two levels of intelligent or conditional ticketing designed to constrain buyer options based on various choices they make in the product ordering process.
Pre v. 8.2: Print service and print service category intelligent conditional ticketing: This functionality (available on the Print Services and Media pages) enables administrators to establish incompatibility rules to prevent buyers from making illogical or ill-fated choices in the ordering process (i.e., by selecting two incompatible print services or a print service that is incompatible with a particular media).
Introduced in v. 8.2: Ticket Template level intelligent conditional ticketing: This functionality (available from the Ticket Templates page) provides administrators with additional options for tailoring the ticket (i.e., aside from simply making a print service incompatible with another print service or media) to determine what happens when a buyer selects a particular print service. The administrator can also recommend one or more additional options based on buyer choices or enforce a particular option (e.g., a banner for outdoor use must be printed on vinyl). This level of intelligent ticketing is covered in this section.
What is the purpose of intelligent ticketing at the ticket level?
Buyers are often unaware of best practices in the print production process. For instance, a buyer ordering a wide format product might specify that a banner intended for long-term outdoor use with a viewing distance of more than 10 feet be printed on an inappropriate media that will not weather well. Intelligent ticketing at the ticket level is intended to prevent buyers from making such unsatisfactory choices based on buyers’ stated intent (i.e., as expressed through the choices they make). When the buyer selects a print service that you specify on the Intelligent Ticketing dialog (as described below), the system will either enforce or recommend certain choices or alert them to an incompatibility.
You can create print services designed to reveal buyers’ intent. These print services will serve as an intent questionnaire that will help you make ticketing decisions on behalf of the buyer to best meet the buyers’ needs. For example, for wide format products, you could create the following print services aimed at getting at your buyers’ intent, how they intend to use the product:
• Display Environment print service with the following options: Indoor, Outdoor, Mixed-Indoor & Outdoor, etc.
• Viewing Distance print service with the following options: Less than 10 feet, More than 10 feet, etc.
• Length of Use print service with the following options: Short-term (less than one month); Long-term (more than one month), etc.
Based on the options buyers select for these print services, you can use intelligent ticketing to constrain their choices so they get the finished product they need.
For instance, if a buyer chooses the Outdoor, Less than 10 feet, and Long-term options, you might opt to enforce vinyl media, 600dpi resolution, and UV inks.
Enforced ticketing at the Ticket Template level applies to SmartStores only.
On the admin side
You manage intelligent ticketing by selecting the ticket template on the Manage Ticket Templates page and clicking Manage Intelligent Ticketing on the Manage Ticket Template page.
You can select one of three actions to take when the buyer selects a print service to define the intelligent ticketing relationship:
• Enforce: This option forces application of the specified print service based on the option the buyer chose for the selected print service.
For example, if a buyer chooses the Outdoor use print service option, the system will force the job to be printed on vinyl (or another weather-resistant substrate).
• Incompatible: This option excludes one or more options based on buyers’ selection of the selected print service.
For example, if a buyer chooses the Close viewing print service option, the system will not give the option of printing at a resolution less than 300dpi.
• Recommend Additional: This option makes one or more recommendations of additional print service options to the buyer based on the option the buyer chose for the selected print service.
For example, if a buyer chooses the Close viewing print service option, the system will also
recommend that the job be printed at either 600dpi or 1,200dpi. For any recommended action, you can add a custom message explaing the recommended action to buyers in the Message text box.
On the buyer side
As buyers select print options for a product they are ordering, they are informed about their selections as necessary:
• Incompatible print options: For example, if a buyer selected color printing, the media/paper selections may be limited to those that are compatible with color printing. The buyer would need to change the selections as necessary.
• Recommended options: A print option buyers select may result in a recommendation for one or more other print options. For example, if buyers select landscape orientation, a particular media may be recommended. (Buyers are not forced to accept the recommendation.)
In another example, if buyers select outdoor viewing distance, certain types of vinyl media may be recommended:
• Enforced options: An option buyers select may automatically result in another option being selected automatically. A message explains what is being enforced.
Sometimes no message is displayed when print options are enforced, but such required print options may affect the price of the job. Buyers can see the required print options in the job summary or pricing summary.
An enforced option may sometimes require further information from buyers, in which case a red icon at the top of the window alerts them:
If buyers move the pointer over the icon, they can see what is required. For example, if they selected a welded hem, grommets may be required, and buyers must select the required grommet option and then provide information about grommet spacing or position.
If buyers do not notice the alert or they ignore it, they are reminded again when they click Add to Cart, and are prevented from continuing until they provide the required information. For example, they may need to make further selections or provide dimensions.
Re-Orders of Products with Changed Content or Ticketing Options
When buyers re-order products, the system now better detects and handles any changes that may have occurred since the product was last ordered. For example, the content for a static product may be different or ticketing changes such as different media or binding selections may affect the product when it is re-ordered.
Changes to Content Files for Static Products
You can control how changed content files are handled during re-orders.
A new option in Site Settings > Basic Settings lets you define the default behavior for re-orders of a static product when content files change: Use Buyer File(s) (the original files) or Use Current Product File(s) (updated files).
On a product-by-product basis, however, you can override the site settings if necessary with a setting on the Product > Upload Files page:
If you select Inherit, the default site setting is used. Otherwise, you can select Use Buyer File(s) or Use Current Product File(s):
• If you select Use Buyer File(s) and make any changes to the content files for the product (delete a file, add a file, or change the order of files), the new/changed files are not used when buyers re-order the product; the original files are used. A new order, however, will use the latest content files.
• If you select Use Current Product File(s) and make any changes to the content files for the product, the new/changed files are used when buyers re-order the product and buyers are informed that the content is different.
This option is useful, for instance, if a static document product contains time-sensitive material that is updated on a periodic basis. Take, for example, a product catalog that is updated every quarter (Winter, Spring, Summer, Fall). A buyer orders the catalog in January and receives the Winter catalog. If she reorders the catalog in May she will receive the Spring catalog if the Use Current Product File(s) option is selected or the prior Winter catalog again if the Use Buyer File(s) option is selected.
Which option is right for you?
If most of the static document products on your site contain time-sensitive material subject to periodic change (e.g., quarterly product catalogs, course materials that change each semester, seasonal sales collateral), you might want to set the Use Current Product File(s) option at the site level and override those products that are not subject to change at the product level.
For backward compatibility, when you upgrade to Digital StoreFront 8.2, the site setting is set to Use Buyer File(s) and all static products are set to Inherit. You can change these settings as necessary.
When buyers re-order a product with changed content, and Use Current Product File(s) was selected by the administrator, a message in the cart informs the buyer. If the product allows buyer configuration (in the product settings), Click here to review (as shown below) is also displayed so the buyer can review what has changed. If the product does not allow buyer configuration, Click here to review is not displayed and the rest of the message is just informational.
Changes to Ticketing Options
As before, the way changes to ticketing options are handled during a re-order is controlled in the shopping cart settings on the Manage Company page:
“Behind the scenes,” however, the system can now better figure out which ticketing options are still valid during a re-order of a product and automatically update the new job accordingly (when Reorder in the company settings is set to Use latest/current ticket template). The system can also detect if special pages or tabs still apply. As with changed content files, changed ticketing options are identified in the cart (and in Visual Product Builder where applicable). Depending on the product, buyers may be able to click a link (as shown in the figure below) to review new/changed print options and change the selections if necessary.
Even if no message about changed ticketing options is displayed, it is always a good idea for buyers to review a product they are re-ordering (if they have permission to do so).
To make choices clearer to buyers when configuring products, you can configure ad hoc and static products to display one page at a time in spread view (instead of two facing pages). Select this option if you want multi-page documents to be shown to buyers one multi-page at a time (single-multi-page view) instead of two-up (i.e., two facing pages in spread view). Single-page view is especially useful for double-sided products in landscape mode such as a tri-fold brochure.
This feature applies to SmartStores only.
On the admin side
On the Product > Settings page, when Dynamic Preview is Enabled, select the Show Single Page View check box.
Single-page view will not be shown to buyers in Visual Product Builder when Binding, Staple, Drill, Tabs, or Covers print options are selected.
When Show Single Page View is not enabled, the back side of a sheet will be displayed as if the page had been turned along the binding edge, and the content will be oriented based on the duplex type – standard Double-Sided or Double-Double-Sided (Tumble). This is true whether binding is set for the job or not.
Back side of page if standard Double-Sided is selected:
Back side of page if Double-Sided (Tumble) is selected:
When Show Single Page View is enabled, the back side of a standard duplex sheet will be displayed “right-side up” with the top edge oriented at the top of the VPB. First page is shown right-side up (of course):
Back side of page is displayed right-side up when standard Double-Sided is selected:
Back side of page if Double-Sided (Tumble) is selected:
On the buyer side
When a product is configured for single-page preview, only one page is displayed in spread view (instead of two facing pages), unless the buyer selects a print option like binding, stapling, drilling, or covers for this type of product, in which case two facing pages are displayed.
Combo Mode for DirectSmile and FusionPro Products
As of Digital StoreFront 8.2, DirectSmile and FusionPro® products can be set up in combo mode. Multi-record VDPs can be set up as “combo” products. The term “combo” (combination) refers to a mix of common (same for all records) and versioned (unique for all records) data. For example, a batch of postcards that a realtor distributes can combine common elements (all the postcards have the realtor’s address; same for all records) and versioned elements (recipient customers’ names and addresses; unique for each record). Buyers enter the common information into form fields (i.e., the web form) and assign a data source for the versioned
For each field on your DirectSmile and FusionPro template, you can specify whether it is Versioned or Common.
Note that for FusionPro products, image field types should not be set as Common – Data Same on all Records because this functionality is not currently supported.
Digital StoreFront’s PrintMessenger is a print driver application that buyers can download from your site that enables them to submit jobs using File > Print option in the desktop applications they use to create documents (e.g., Word, PhotoShop, Illustrator). The core of the application is a print driver that converts native file formats to PDF for processing in your Digital StoreFront workflow. PrintMessenger Redirect enables you to associate a particular product with PrintMessenger so that when buyers submit a job through PrintMessenger they are taken immediately into the associated product’s workflow (the Visual Product Builder) in Digital StoreFront (without having to manually select a product that matches the submitted file).
If you have only one ad hoc product, PrintMessenger will automatically route all jobs submitted through it to that product.
Buyer Workflow Without PrintMessenger Redirect: If you have two or more ad hoc products on the
storefront and do not use PrintMessenger Redirect, PrintMessenger will not automatically route jobs to any of the products. Instead, it will take the buyer to the Upload Successful! landing page in Digital StoreFront that informs the buyer that the file was added to the Files list and directs him/her to click the Get Started button to begin. After clicking Get Started, the buyer must then select the product for the submitted file.
Buyer Workflow With PrintMessenger Redirect: If you have two or more ad hoc products on the storefront and use PrintMessenger Redirect, it will save buyers a step in the workflow because you select the default ad hoc product to associate with all jobs submitted through PrintMessenger. Thus, when the buyer submits a job through PrintMessenger, Digital StoreFront will open Visual Product Builder for the designated default product so the buyer can immediately begin configuring the product.
You select the default ad hoc product for PrintMessenger Redirect on the Companies page:
On the buyer side, buyers will not get a Get Started link after they upload files with PrintMessenger. Instead, they are taken directly to the product customization step; no product selection is necessary.
Multiple First-Level Domains (Self-Hosted Installations)
Digital StoreFront 8.2 supports multiple domains. This allows companies or entities to have exclusive branded URLs. Self-hosted customers can use multiple first-level domains within a single instance of Digital StoreFront. This extends the short URL functionality (i.e., that supports sub-domains such as books.iprintstuffgood.com or cheapposters.iprintstuffgood.com). Multiple first-level domain support is robust enough to support customers who want to have a Digital StoreFront site at their own domain such as www.BestPrintingCo.com rather than BestPrintingCo.iprintstuffgood.com.
Note that multiple domain support is currently supported only for self-hosted (standalone) sites (i.e., not cloud, or EFI-hosted, sites).
Primary Use Cases for Multiple Domain Support
• A service provider wants to “productize” an offering with unique URLs (www.cheapestprintsonearth.com and www.biggestbannersonearth.com).
• A managed services provider with multiple clients wants them to have their own vanity URL (www.yummyfoodsprinting.com) and not one with the service provider in the URL
Multiple domain support prevents managed services customers from needing separate instances of Digital StoreFront for each URL (because self-hosted customers were previously permitted to have only one top-level domain). By extending the framework that EFI introduced with short URLs, a single self-hosted Digital
StoreFront site can assign different top-level domains at the company level. This makes management across multiple clients easier and less complex.
You add supported domains on the Multiple URL Configuration page.
User Authentication: SAML 2.0 Support
Digital StoreFront 8.2 adds support for the SAML 2.0 federated identity services protocol. SAML stands for Security Assertion Markup Language. This option is for sites whose identity standard calls for SAML 2.0.
The SAML 2.0 protocol supports Shibboleth, a free and open source federated identity solution. For more
information, visit http://www.shibboleth.net.
You configure SAML 2.0 by selecting Administration > Site Settings > Authentication > Federated SSO and selecting SAML 2.0 as the Federation Protocol. For more information see administration online Help.
SEO (Search Engine Optimization) Enhancements
Digital StoreFront 8.2 enhances search engine optimization (SEO) for self-hosted sites with SmartStores so that they work well with: (1) a recent change in which Google no longer indexes keywords on pages and (2) Digital StoreFront’s single-page architecture.
URL Change to Improve Rankings
In Digital StoreFront 8.2, the site URL will be changed to use a hash bang URL.
For example, a URL that was previously in the format
http://mysite.com/DSF/SmartStore.aspx#/Storefront will be changed to
http://mysite.com/DSF/SmartStore.aspx#!/Storefront in 8.2. This will enable Google to recognize the variations in the URL after the # fragment and convert the URL to
Sitemap to Improve Rankings
A SmartStore specific sitemap was also added to improve the page ranking. Note that in v. 8.2, sitemaps will be generated only for the default storefront. All products and categories published on the storefront will be available in the sitemap with a distinct URL. This will allow buyers to search for any product or category/sub-category available on storefront page that is accessible to anonymous users. The relevance of the data available on pages and number of matches of the search term will help achieve better ranking in Google. Category and product detail page URLs were also changed to be more user friendly by adding the category/product name in the URL. This, too, will help in improving the ranking with search engines.
Complete instructions on how to register and submit a sitemap to Google is available in the administrator online help topic “Google Analytics Tracking.”
Limitations: Sitemaps will be generated only for the default storefront and search engine registration can be done only for self-hosted (standalone) sites.
Select Merchant Accounts at the Company and Department Levels
You can now select credit card merchant accounts to use at the company and department levels. Thus, you can select the appropriate credit card merchant account for each company and department (i.e., independent of the merchant account specified at the print shop level).
Kits and Matrix Products
As of Digital StoreFront 8.2, a kit can now be part of a matrix product and a matrix product can be part of a kit. (A matrix product is a composite product that combines two or more related products into a single product with various options so that buyers have a convenient way of choosing the options they want, e.g., a hat in the size and color they want.)
High-Resolution Preview for FusionPro Products
Digital StoreFront 8.2 now supports high-resolution previews for FusionPro products. Various resolution options were added at the product level so that an admin can choose optimal resolution for each product. For example, a small product such as a business card might benefit from a higher preview resolution, whereas a wide format poster may be perfectly acceptable at a lower resolution.
Digital StoreFront 8.0
Entities are new building blocks in Digital StoreFront for defining organizational structure. Entities offer a top-down, multi-level approach to sharing (or not sharing) products, media, storefronts, pricing, etc., in different parts of a single Digital StoreFront installation.
Entities can be used for:
• Enterprise organizations with subsidiaries
These may be separate business units or regional subdivisions with a combination of shared and unique Web-to-Print needs.
Example: A large corporation based in New York City has five subsidiary branches—US, Canada, Brazil, Europe, Asia—that have both shared and unique Web-to-print needs. The Digital StoreFront parent administrator (for the license-holding U.S. branch) would thus create five entities (one each for the international divisions). Administrators at each of the entities could in turn create sub-entities as needed for branches beneath them. The entity model lets the corporation administer Digital StoreFront from a single instance for consistency of pricing, product offerings, user database, reporting, etc. This is more efficient than using separate instances of Digital StoreFront while still providing the flexibility for each branch to administer non-shared (unique) assets.
• Managed service businesses
Service businesses typically include many parallel customers with unique Web-to-Print needs. These are B2B organizations that service client organizations (e.g., printing, shipping). Without the entity model, each client organization would typically be set up as a “company” in Digital StoreFront. The entity model offers a more flexible way to manage multiple parallel customers with unique Web-to-print needs vs. company-level management.
Example: ServiceProVida provides managed Web-to-print services to multiple discrete client companies, each with a unique set of needs. The entity model provides a way to silo the client companies from a single instance of Digital StoreFront much more effectively than company-level management. For
instance, it will create higher “walls” between client companies to ensure there is no intermingling of user data, product data, pricing data, etc. The branches can be built with as much or as little interconnectivity between them as needed. The Digital StoreFront parent administrator (for the license-holding
ServiceProVida) would thus create entities for the each of the organizations the company services. Administrators at each of the entities could in turn create sub-entities as needed for branches beneath them.
• “Marketplace” sales
Here affiliates or partners can sell their products online in a space they control (e.g., a photographer offers prints and cards for sale), but the primary Digital StoreFront owner produces or fulfills the products. The marketplace sales concept in the entity model provides printers with an effective way to partner with content creators (such as photographers, fine artists, book authors, publishers, etc.) they produce products for by giving them a branch or space on Digital StoreFront site through which they can sell their products through their own storefront (i.e., that you will print and fulfill). Each content creator can have a separate space on your site with limited administrator access and capabilities you define.
Example: MarketPlace Printing wants to provide each of its content creation partners with its own site to drive business both to the partners and the printer (who produces their products). The entity model enables the printer to give each content provider its own space on the printer’s Digital StoreFront instance with limited administrative access and control. The Digital StoreFront parent administrator (the license-holder) would thus create an entity for each content creation partner. Administrators at each of the entities could in turn create sub-entities as needed for branches beneath them. The chart below illustrates how the entities and sub-entities might be organized.
• You can have multiple levels of entities in the form of parent-child relationships. Permissions and sharing
• A parent entity gives permissions to its children (sub-entities) to control how much or how little the child entities can do in Digital StoreFront.
• Parent entities can only pass down permissions they have themselves.
• Products, print services, pricing, storefronts, etc., can be shared. They are always shared “downwards,” from a parent entity to its child entities. Print shops, however, are the exception – they can be shared any way you want among entities.
• Existing Digital StoreFront elements—groups, companies, users, etc.—still play a role in Digital StoreFront. Entities do not replace them, but rather expand the options.
Entities require separate licensing – you can purchase licenses for as many entities as you need (similar to purchasing print shop licenses).
Notes Any optional module (e.g., EFI VDP Powered by DirectSmile or DSFdesign Studio™) for which you have a license is automatically available to all your entities. These licenses apply to the entire Digital StoreFront installation; you cannot purchase licenses for optional modules for individual entities.
You can set up multiple levels of entities. The figure below shows a single level below the parent organization, but each of these entities could include sub-entities, which in turn could include sub-entities, and so on. The number of levels you have depends on the needs of your organization.
Rules control what each entity can do.
The rules control whether the entity can:
• Create print shops
When you allow an entity to create print shops, you specify the number of print shops it can create. (This must be within the limit of your license – the system shows you how many licenses remain.) An entity that can create print shops also controls how its print shops are shared, e.g., globally, by selected entities, etc. (Sharing permissions are part of the print shop settings.)
• Create sub-entities
When you allow an entity to create sub-entities (child entities), you specify the number of sub-entities it can create. (This must be within the limit of your license – the system shows you how many licenses remain.) Note that an entity with permission to create sub-entities can only give its sub-entities the permissions it has itself. For example, if the parent entity cannot create products, it cannot allow a sub-entity to do so, but if it can create products, it can either allow a sub-sub-entity to create products or prevent it.
• Create new products
Depending on your organization, you may want to control which entities can create products. In some situations, you may want all products to be created by the top parent entity and shared with all the
sub-entities in the organization. (For information about sharing, see page 43.) In other situations you may want to give entities the option to create their own products, which they can offer in addition to any products shared by the parent entity.
When a sub-entity cannot create its own products, its products come from the parent entity through sharing. The sub-entity, in turn, can share products with its sub-entities (if any). For information about sharing, see page 43.
• Change pricing
Pricing can be fixed (controlled completely by the parent entity), or you can allow the pricing defined by the parent entity to be marked up and/or down, or overridden by a sub-entity. For example, if the entity can mark the pricing up or down, a price sheet will give the option of marking an item up or down by a fixed amount or a percentage. The prices from the parent entity are always available so you know what you are adjusting.
When defining an entity, you also decide whether the design and branding of the storefront can be changed, and whether the entity can manage or add featured products and categories on the storefront. (Only SmartStores are supported.) For example, you may want “one look” throughout the organization with the same featured products, in which case you would not allow branding or featured products to be changed. What you allow depends on your organizational needs and structure.
Many items in Digital StoreFront (products, media, print services, ticket templates, merchant accounts) can be shared by a parent entity with its entities (children). By sharing, you make the items available to sub-entities.
With the exception of print shops, the sharing is always “downwards” from a parent to a child. In all places where sharing is possible, a new Sharing Permissions section is available. You always have a choice of sharing with all sub-entities or with selected sub-entities (by clicking Add Entities). For example, when defining a product, the Security product settings include Sharing Permissions.
Items that are shared by a parent entity cannot be changed by a sub-entity; the sub-entity can view the details of an item (e.g., product or ticket template), but only the parent entity that created the item can modify it. If you allow sub-entities to create their own products, you may want to share media, print services, and ticket templates with the sub-entities so they have the necessary building blocks for product creation. Sharing also standardizes what the entities are using. If you do not allow a sub-entity to create its own products, you must share products with it, or it will not have any products to sell.
Print shops, as mentioned earlier, can be shared with any entities, not just by a parent entity with its child entities. The entity that created a print shop can share the print shop with all entities in the system (globally) or share it with selected entities anywhere in the system.
To facilitate the setup and configuration of sub-entities, a Digital StoreFront administrator can impersonate a sub-entity. A new Impersonate Sub-Entity Admin link is available at the top of the Administration page.
After you click the link, you select the sub-entity you want. No separate login is required. After you finish working with the sub-entity, you just log out.
Queries and Reports
You can use dynamic queries to obtain entity-related information. In addition, the following standard reports account for the entity model:
• 72 Hour Outlook by Company
• 72 Hour Outlook by Print Shop
• Output Utilization by Print Shop
• Revenue By Company
• Revenue By Print Shop
• Taxes Collected for Period
Enhancements to AccuZIP Direct Mail Support
Digital StoreFront 8.0 adds the following enhancements to the AccuZIP direct mail integration:
On the admin side, additional support was added for the USPS PostalOne! Mail service. The mail.dat file is now available in a downloadable zip file (Maildata.zip) from the Postal File(s) section of the production job ticket.