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
l Awaiting Payment:If a payment is required on the order but the payment does not go through, for example
if the customer cancels or closes the payment window. If the customer returns to complete the payment or a Pro-
duction Manager manually approves the order, it will go into Ordered or Approved status.
l Awaiting Payment:Orders that are awaiting payment can be re-opened by the customer that made the order, a
manager or an administrator. An order that is awaiting payment can either go to the Ordered or Approved status
depending if the user or a Manager changed its status, respectively.
l On Hold:An order can either be put On Hold automatically if a new order requires a price quote, or manually by a Man-
ager as required. An On Hold order can be put into Ordered status manually or Approved status when a price quote has
been completed.
l Approved:An order goes into approved status once it's been quoted, paid for and approved by the appropriate man-
agers. Once an order is Approved, it cannot revert to any previous status and must move forward unless it is deleted.
An Approved order can be put into the In Plant state by a Production Manager.
l In Plant:An order goes into In Plant status by the Production Manager when it is ready to generate output. An Oper-
ator uses the In Planet status to see what jobs are ready and as a queue to know which job to output next. Once the job
has been output, the Operator can place the order in Shipping status.
l Shipping:This status is used to indicate that an order has been generated and is ready to be shipped (or has already
been shipped)to a customer.
l Completed:Once a customer confirms that his order has been received, an Operator or Production Manager will be
able to place the job into Completed status, where no further processing is necessary.
Ordering Workflow
©2010 Objectif Lune Inc - 63 -