7.1
Table Of Contents
- Table of Content
- Overview
- Understanding PrintShop Mail Web
- Getting Started
- The PrintShop Mail Web Interface
- Publishing Workflow
- Ordering Workflow
- New Document
- Order Manager
- Checkout
- Companies
- Users
- Publication Types
- Collections
- Settings
- About
- License
- Roles
- Languages
- Web Design
- Maintenance
- Settings
- Currencies
- Tax Rates
- Shipping Rates
- Calendar
- Production Settings
- User Input Field Defaults
- Output Folders
- Job options
- Printers
- E-mail Settings
- E-mail Addressees
- Managing E-mail Templates
- Modules Settings
- Enabling a MIS connector
- Installed modules
- Properties
- Enabling a Print Production connector
- Installed modules
- Properties
- Requirements
- Configuring the module
- The PayPal Sandbox
- Processing orders
- Requirements
- Configuring the Authorize.net module
- Test mode
- AVS and CCV checks
- Payment page
- Requirements
- Requesting a test account
- Configuring the iDEAL test dashboard
- Configuring the iDeal module
- Requirements
- Configuring the Moneris module
- Test mode
- Requesting a live account
- AVS and CVD checks
- Payment page
- Add a new Module
- Configure a module
- Delete a Module
- XML (eXtensible Markup Language)
- Options
- Sample POST receive script
- Interaction With PrintShop Mail Design
- Introduction to Regular Expressions
- Introduction
- Skinning Guide
- Getting started
- Creating your own skin
- The template file
- HMTL Outline
- Styling
- Key Concepts
- Style organization
- Header
- User information
- Menu bar
- Background
- Overview tables
- Edit forms
- Sub menus
- Special variables
- Variables for template files
- Variables for style files
- Creating page exceptions
- Creating a page specific template file
- Modifying a page specific template file
- DOM manipulation using jQuery
- Launching code on Document Ready
- Populating fields with computed values
- Removing elements from the DOM
- Adding information to the DOM
- Customizing the store front
- Storefront class
- Creating a hierarchical tree
- Adding a live search option
- Copyright Information
- Index
Ordering A Database-Upload Document
When you click on a document that requires a document upload in the New Document tab, you will need to go through the fol-
lowing steps for the document to be added to your cart:
l Upload your database through the "Database Upload Screen" (page 66).
l Verify the field mappings through the "Field Mapping" (page 66).
l Select your preview range in the "Preview Range" (page 67) window.
l Verify the result in the "Softproof" (page 68) window.
l Add the document to your cart and proceed to checkout.
Database Upload Screen
When a document requires a database in order to be processed, the Database Upload screen will be displayed.
The Fields table shows all of the fields that are expected to be in the uploaded database, and their order. If your database does
not correspond exactly to this list, you will be able to re-order them in the next step.
While it is recommended that the uploaded database be of the same type as the one used to create the document, this
is by no ways mandatory. As long as the database you upload is compatible with PrintShop Mail Suite your document
should output correctly. To verify this, make sure you double-check the softproof.
The Database file box lets you upload your database to PrintShop Mail Web to be merged with the document.
To upload the database:
1. Click the Browse button next to the Source File box.
2. Browse to your database file using your browser's File Upload dialog.
3. Click on the database in the File Upload Dialog
4. Click on OK.
5. When the filename and path appears in the Source File box, click Upload.
When you click Upload, you will be taken to the "Field Mapping" (page 66) window.
Field Mapping
The Field Mapping window is used to make sure the uploaded database file's fields correspond to the one that was used to
create the document. The window displays the Fields table with the following rows:
l Field Name:The list of all fields that the document expects to receive from the database. If there are more fields than
expected in the uploaded database, dashes (-) will be displayed as placeholders and the corresponding upload field will
not be used.
l Header:The list of fields in your database. If your database contains less fields than what is expected, a dash(-) will
be displayed as a placeholder, and nothing will be displayed in the output for this field.
l Value:Displays the first record in the uploaded database next to its field name.
PrintShop Mail Web will attempt to automatically match fields in your uploaded database that match the field names it knows to
use. If it cannot do this for one or more of the fields, you will have to reorder them manually.
New Document
©2010 Objectif Lune Inc - 66 -