Professional Documents
Culture Documents
5.7
Administration Guide
© 2015
Equitrac Professional 5.7 Administration Guide
Document History
Revision Date Revision List
April 2010 Added information about Transaction import from a ODBC data source.
All rights to this document, domestic and international, are reserved by Nuance Communications, Inc. No part of this publication may be
reproduced, stored in a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or
otherwise) without prior written permission of Nuance.
Trademarks
Equitrac®, Equitrac Professional®, PageCounter®, PageCounter Professional®, SmartPrompt®, Follow-You Printing®, and TouchPoint Console® are
trademarks of Nuance Communications, Inc.
All other brands and their products are trademarks or registered trademarks of their respective holders, and should be noted as such.
Caution The accompanying text provides key information about a step or action that might produce
unexpected results if not followed precisely.
Note The accompanying text provides cross-reference links, tips, or general information that can add
to your understanding of the topic.
Warning Read the accompanying text carefully. This text can help you avoid making errors that might
adversely affect program behavior.
1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
About this Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Benefits of Cost Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Core Server Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Core Accounting Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Document Routing Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Device Control Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Scan Processing Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Device Monitoring Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Call Processing Service (CPS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Making Changes to Server Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Control Mechanisms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
TouchPoint Console . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
PageCounter Control Terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Embedded Device Interface Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Release Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Optional Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Rate Table Extensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Data Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Server Clustering . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
Embedded Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Release Station . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Web Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Print Client . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Rules & Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
3rd Party Transaction Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Time & Billing Integration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Data Flows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Validation Data Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Transaction Data Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Administering Equitrac Professional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Removing a Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Getting Around System Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Filtering and Managing List Views in System Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Scheduling Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Configuring Administrative Access Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Windows-level Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Application-level Permissions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Software Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Changing the License View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Deregistering Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Initial Configuration Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
2 Managing Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
About Equitrac Professional Users . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
User Accounts Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
Creating User Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Assigning Scan Aliases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Creating Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Adding User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Active Directory vs. Import from Time & Billing System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Importing from a Time & Billing System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Importing Users through Active Directory Services Synchronization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
Auto-creating User Accounts On First Print . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Adding User Accounts Manually . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
Testing the Popup Preview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
Viewing User Accounts in System Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Modifying User Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Accounts System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Configuring User Authentication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Selecting Notification Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
Configuring the Mail Server for Email Notices and Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Qualifying Accounts by Domain . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
Maintaining Classes, Locations, and Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Modifying a User Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Removing a User Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Modifying a Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Removing a Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Removing User Accounts from Equitrac Professional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
Managing Proxies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Defining Users as Proxies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
Configuring Proxies in System Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
Revoking Proxy Rights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
A Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 455
Regular Expressions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
Branch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
Piece . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
Bound . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456
Bracket Expression . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
Collating Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 457
Printer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
Printer Job Language (PJL) Page Counter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
Data Stream Interpreters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 458
Comparing Page Counting Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 460
Command Line Utilities and Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
The Tools Folder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462
The EQCDRTest.exe Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463
The EQModifyDeletedContainerSecurity.exe Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 464
The EQPrintConversion Wizards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 465
The EQTerminalUpdate.exe Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 466
The EQTransactionPurge.exe Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 469
Field String Syntax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 471
Entry Length . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472
Character Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 473
Specifically Positioned Character . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
Embedded Special Characters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 474
Combining Syntaxes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475
SMDR Translator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
The WinSMDR.exe Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 476
Using SMDRDesigner to Create and Modify CDR Parsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477
Parser Definition Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 479
Using FDL constructs in PRS files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 486
Field Formatting Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 489
Incoming Call Parsing and Identification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 491
Color Values in Transaction Import Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492
Format Variables for Custom Date Format Field . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 493
B Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 497
Topics:
About this Guide
Benefits of Cost Recovery
Core Server Components
Control Mechanisms
Optional Components
Data Flows
Administering Equitrac Professional
Configuring Administrative Access Permissions
Software Licensing
Initial Configuration Workflow
Equitrac Professional is a cost recovery system that works with control terminals, TouchPoint Consoles, client
software, and embedded interface software to record transactions performed on office devices (printers, photocopiers,
fax machines, multi-function devices, and so on) throughout your enterprise. Equitrac Professional is server-based
software consisting of several components—print servers, a core accounting server, and administrative applications—
that track and monitor device usage and export transaction data to your time and billing system, which charges
transaction costs to clients.
You can configure Equitrac Professional to monitor usage patterns on your output devices so you can analyze your
environment to ensure optimum usage of those devices. For example, you can create price lists to determine detailed
pricing for each transaction. You can then use this pricing information to bill clients, or to audit your own policies and
rules to ensure you derive maximum benefit from the various devices throughout your enterprise.
Equitrac Professional also provides a web-based reporting tool called the Web Client to allow disbursement entry,
transaction editing, and reporting. For information on performing transactions and using the Web Client, see the
Equitrac Professional Usage Guide.
This chapter describes essential Equitrac Professional concepts, data flows within Equitrac Professional, and the
primary software and hardware components.
Cluster Deployment Guide If you are deploying Equitrac Professional in an existing Windows cluster
environment, use this guide to plan and execute the installation.
Scan Solutions Guide Instructions to configure Equitrac Professional for use with:
Equitrac Embedded for eCopy
ScanPost for eCopy or Xerox
Equitrac server scanning with eCopy or Xerox
Usage Guide Instructions to use the Equitrac Web Client for exception editing, generating
reports, and disbursement entry.
PageCounter Quick Reference If you need help understanding the options available from the main PageCounter
interface, use this reference to quickly look up information.
Release Station Help Instructions and reference information about using Release Station to release jobs
from the secure print queue in a secure document release environment (SDR).
TouchPoint Console Online Help If you are deploying TouchPoint Consoles, refer users to the online help system
available for download on the Equitrac partner portal.
Equitrac Professional’s primary function is transaction cost recovery. Equitrac Professional monitors all transaction
activity and calculates the cost, based on pricing policies you provide. You can export tracked transaction data to your
time and billing system for billing those costs back to your clients.
Total cost of ownership for each device monitored by Equitrac Professional is based on direct and indirect costs
incurred over the life cycle of a device. Equitrac Professional enables you to set secondary pricing for transactions to
enable you to track the total cost of ownership of each device.
The main Core components include the CAS, DRE, DCE, SPE and the Windows Server
Equitrac port monitor. The DME and CPS are optional licensed
considered core components. Core components reside on one or more
Windows servers.
Administration takes place in System Manager, a centralized interface that provides an intuitive view of the accounts
database, and allows configuration of the server and peripheral components. The print tracking client tracks print
transactions, and the Web Client enables you to manually enter disbursements, and schedule and generate reports.
Every Equitrac Professional installation requires a pre-installed database. CAS uses the database instance to create an
accounts database that contains all printer, user, billing code, transaction, and balance information. The database can
reside on the same machine as CAS, or on a separate server if needed. See System Requirements in the Installation
Guide for information about supported databases.
CAS functionality is configured in System Manager.
1 Print Request
Port
Monitor
3 Job is Printed DB
1 A user generates a print request. The port monitor intercepts the request before it gets to the printer and “holds”
the print job while it waits for a user validation response from the CAS.
2 The CAS checks its database and either validates the user, or denies the request. If denied, the user receives a
notification message on their desktop (if configured).
3 The response is sent back to the DRE, and the print job is forwarded to the printer.
4 After the job is printed, the page count and job attributes are forwarded to the CAS database for tracking.
For installations that require secure document printing, you can configure the DRE to hold documents in a print
queue until the user releases them from either a terminal keypad or a Release Station. See Configure Basic Secure
Printing on page 239 for details.
Although the DRE is a core component, it is not required in all deployments. The DRE manages communications with
physical printing devices. If you are only tracking photocopy transaction on devices with embedded controller
interfaces (rather than tracking printing), you do not need to install the DRE component.
DRE functionality is configured in System Manager.
CAUTION: If the Print Client is installed on a Terminal Services server, the DRE/Print server must be installed on a
separate server.
1 Login Requested DB
3 Update Job Attributes
CAS
DCE
1 A user requests access to a multi-function device via a PageCounter terminal or a terminal keypad.
2 The request is handled by the DCE, which then forwards a user validation request to the CAS. The CAS checks its
database and either validates the request, or denies it.
3 After the user completes their photocopy, fax, or scan, the job attributes are forwarded to the CAS for tracking.
Although the DCE is a core component, it is not required in all deployments. If you intend to track printing from
workstations only, and do not need to track photocopy, scan, or fax jobs, you do not need to install the DCE
component. Instead, only the DRE component is required.
CAS
The DME keeps a record of all SNMP status changes on connected and enabled devices.
Control Mechanisms
Equitrac’s control mechanisms consist of hardware and software components that control access to office equipment
such as photocopiers, scan devices, and fax machines.
TouchPoint Console
TouchPoint Consoles (TPC) control access to multifunction devices through an intuitive touch-screen application.
Installed near the MFP and connected via a manufacturer-specific copy control cable, TPCs allow the user to quickly
enter their validation data (e.g. user name and password), then choose the client/matter codes to bill their transactions
against. When TPC verifies their entries, the MFP is unlocked and ready for use and the user can access all allowed
capabilities such as copying, scanning, or faxing.
In the case of printing, the user must enter their usercode only to proceed to the Document Release options on TPC.
The appropriate client/matter allocation data is retrieved from the print popup at the time of the print request.
Each TouchPoint Console requires one Device Connector license in System Manager.
See Configuring TouchPoint Consoles on page 301 to configure TouchPoint Consoles in System Manager.
Release Station
Release Station is an optional component used for secure printing. Release Station uses a network workstation as a
point for controlled document release. Using Release Station, network users can view, select, print, or delete
documents held in the proprietary secure print queue. Release Station is not installable default, and can be selected
during initial installation or at a later date.
Each Release Station requires a Release Station license in System Manager.
See Using Release Station on page 253 configure Release Stations.
Optional Components
Equitrac Professional is a highly configurable solution that offers optional components to customize the installation to
specifically suit your requirements. Many optional components are included in the Equitrac Professional Standard
license, however some require a separate license.
The following sections provide a description of each optional component, an indication of license requirements, and a
link to obtain further information if you want to configure the feature.
Data Source
The Data Source component enables a third party print tracking system to upload transaction data to the Equitrac
Professional accounting server. See Importing Transaction Data on page 102.
Server Clustering
You can install one more Equitrac Professional core server components within an existing Windows cluster
environment. For more information, refer to the Equitrac Professional Cluster Deployment Guide.
Embedded Interface
If your deployment includes Equitrac Embedded solutions, you must purchase a manufacturer-specific Embedded
device license to enable this communication. See Embedded and Controller Interfaces on page 215.
Release Station
For a description of Release Station, see Release Station on page 25.
Web Client
The Web Client is a server function that enables users to add disbursements, correct and edit exception transactions,
and schedule and generate reports. Users access the Web Client from a standard web browser.
Print Client
The Print Client application, is deployed to track print transactions from workstations throughout your organization.
NOTE: Along with the Print Client there is an option for a Document Routing Client (DRC), that acts as a locally
installed version of the Equitrac Professional Document Routing Engine. This client is only used when no print server
is available. There are no DRC installation options for Macintosh OS X.
When you deploy the Print Client (through installation on individual workstations or through a centralized, silent
installation on targeted workstations), you can install these components:
1 The user settings tool.
2 The Document Routing Client (DRC). This is only necessary if the installation does not employ a print server.
The user settings tool enables users to temporarily disable the client popup in cases where they are performing several
transactions for the same client/matter combination. The print tracking client popup tracks all transactions against the
specified client/matter, but remains hidden so users do not have to repeatedly enter validation data. The user settings
tool also enables users to disable field-level validation. Equitrac Professional still validates user entries as necessary,
but does so only once for all fields, rather than for each field individually.
NOTE: Equitrac Professional also provides the ability to temporarily "suppress and re-use" values for the popup, even
without the tool tray application. For detailed information, see Configuring Print Client User Settings on page 379.
The print tracking client popup prompts users for validation data and checks with the server to ensure that users have
supplied valid data. When the print tracking client popup receives valid data, it sends the print job to the appropriate
printer, collects details on the transaction, and sends transaction information to the CAS.
See Client Popup Management on page 343 for Administrative tasks. For information on using the Print Popup see
the Equitrac Professional Usage Guide.
CAUTION: If the Print Client is installed on a Terminal Services server, the DRE/Print server must be installed on a
separate server.
Web Client
When you install CAS, Equitrac Professional automatically installs the Web Client with it. Users can log in to the Web
Client to manually enter disbursements, view transactions, and schedule or generate reports.
The Web Client’s reporting functionality provides several system-defined reports. While administrative users with
appropriate access rights can customize these reports, non-administrative users can only modify reports names.
Web Client functionality is restricted to users with specific access permissions, as configured through System
Manager. Therefore, not all options on the Web Client are available to all users.
For information on using the Web Client see the Equitrac Professional Usage Guide. For information on administering
the Web Client, see Administering the Web Client on page 383.
Data Flows
Understanding the general data flows involved with your Equitrac Professional solution will help you plan import and
export schedules, load balancing on your print servers, and the deployment of remote management tools and client
components throughout your organization.
Time and Billing system or Validation Data (users, CAS Through Validation Import wizard.
external database clients, matters, custom
validation types)
User Response to validation Validation Data CAS From control terminal, TouchPoint
prompts Console, Print Client, or
embedded interface software
through DCE or SPE for scan jobs.
Controlled device (MFP, Transaction Data CAS From control terminal, TouchPoint
copier, scanner, fax machine, Console, Print Client or embedded
printer) interface software through DCE.
CAS Transaction Data Time and billing system Through Export wizard.
or external database
The time and billing system or external database contains validation data including your users, clients, matters, and
custom validation types. Use the Validation Import wizard to import this data into CAS.
Time and
Billing
System
Validation
Import Wizard CAS
Users can begin performing transactions when the following conditions are met:
• Validation data resides in the CAS
• Physical devices are added and configured in System Manager
• Control terminals and/or TouchPoint Consoles are configured (if in use)
• Print Client Popup styles are applied
• Embedded device interfaces are configured (if in use)
• Print Clients: When a user prints via the Client Popup, depending on the settings for the user, the validation
request is either sent directly to the CAS or checked against a local cache of recently validated data. If the user data
is validated, the print transaction will proceed.
CAS
Terminal or
TPC
Time and
Validation
Billing DCE
Import Wizard
System
Client
Popup
1 The validation data is imported from the time and billing system, then stored in the CAS and forwarded via the
DCE.
2 When the DCE receives a validation request from a control mechanism, it sends back a validation response. If the
response is positive, the device is unlocked for use. If negative, the device remains locked and the user is not
validated.
3 In the case of the Client Popup and network print requests, when needed, validation requests are made directly to
the CAS, rather than to the DCE. For searches in the Client Popup, requests are made to the DCE.
NOTE: If the DRC is installed, it will collect additional data from the transaction before sending it to CAS. This process
is automatic.
Control
Mechanisms
Transaction Data
Embedded
Controller
CAS
Terminal or
Export TPC
Time and Wizard
Billing DCE
System
Client
Popup
NOTE: Equitrac Professional stores connections between System Manager and the accounting server separately for
each logged-on user with administrative access. Each System Manager user must connect to the accounting server
to manage the Equitrac Professional applications.
Before System Manager launches, select the CAS you want to work with.
NOTE: The first time you open System Manager after installation, Equitrac Professional assumes the accounting
server resides on the local machine.
Since there is only one CAS, you can disable the dialog. If you later need to connect to a different CAS server, select
Tools > Options from within System Manager, then check the Display server selection dialog on startup option. The
next time you launch System Manager, the Select accounting server dialog box will appear again.
Removing a Server
You can remove a server from the tree structure in the Select server dialog box at connection time. By removing the
server from System Manager, you are disconnecting the accounting server and the accounts database. You are not
deleting information in the accounts database.
In the Select accounting server dialog box, select a server from the tree structure and click Delete Server.
Scheduling Tasks
Using System Manager > System > Scheduled tasks, you can create different tasks that will run automatically at a
preset date, time, and interval. There are two types of scheduled tasks: Import/Export tasks, and Arbitrary
Commands.
Import/export tasks allow you to create independent schedules for importing and exporting data between Equitrac
Professional and a third party time and billing system. See Scheduling Transaction Imports/Exports on page 138 for
instructions.
By default, when you configure Call Accounting, a Rate Table update task is automatically created to retrieve rate
tables from the Equitrac FTP Rate Table Update Server. This task keeps rate tables up-to-date automatically. See
Retrieving Rate Tables from the Equitrac FTP Rate Table Update Server on page 419.
Arbitrary commands provide the flexibility to run command-line tasks at a preset date, time, and interval.
Windows-level Permissions
At the Windows level, define at least one user with administrative privileges on the core accounting server (CAS) and
the document routing engine (DRE). The user must have administrative permissions on the server to start and stop
services and the print spooler. If you are configuring remote DREs, the user with administrative privileges on the
remote server must also have administrative privileges on the server hosting CAS. Refer to your Windows
documentation for information on assigning Windows-level administrative privileges.
Application-level Permissions
Application-level permissions determine which users have access to Equitrac Professional components. You can assign
access to registered domain security user groups to one or more of the following permissions:
• Administrative: Grants access to run System Manager.
• Reports: Grants access to run and schedule reports in the Web Client.
• Device Administrative: Grants access to the Device Monitoring Console.
• Web Disbursements: Grants access to the Disbursements tab in the Web Client.
• Web Transactions: Grants access to the Transactions tab in the Web Client.
• Web Exceptions: Grants access to the Exceptions tab in the Web Client.
You cannot assign application-level administrative permissions on an individual user basis; you must create Windows-
level user groups that include those users to whom you want to assign administrative privileges within Equitrac
Professional.
NOTE: If you start Equitrac Professional using the account that is also running the CAS or DRE services, you have full
administrative access to all Equitrac Professional components.
3 In the Permissions dialog box, click the permission group link you want to configure.
4 Use the Select Group dialog box to choose groups that have access to the selected Equitrac Professional function.
Software Licensing
While you can run Equitrac Professional in an unlicensed mode, you cannot configure software and printers,
including print queues on the Document Routing Engine (DRE), without first registering the relevant component
licenses in System Manager.
CAUTION: License Equitrac Professional before managing devices in Windows and configuring devices in System
Manager. If you add licenses after adding physical devices, the print queues do not appear in System Manager until
fifteen minutes expires after licensing Equitrac Professional, a user sends a print transaction to the printer, or you
restart the Equitrac DRE service. For instructions on applying licenses in System Manager, refer to the Installation
Guide.
Deregistering Licenses
System Manager enables you to select and deregister one or more desktop print licenses simultaneously.
In an environment with large print implementations, you may find it necessary to change out multiple printers each
month (particularly desktop printers), and manually deregistering each of those desktop print licenses could become
an administrative hassle. In the System Manager > System > Licensing link, use the License view for a full list of
available licenses. Select those licenses you wish to deregister, and right-click to select the relevant option from the
menu.
Establish flat rate or basic price lists for transaction cost tracking and billing requirements. You can create different
types of price lists and apply a price list per device if necessary. See Configuring Price Lists on page 143 for
instructions.
9 Set up Call Accounting
If implementing cost management for telephone systems, import rate tables and create call sites and extensions.
See Managing Call Accounting on page 415 for instructions.
Topics:
About Equitrac Professional Users
User Accounts Workflow
Creating User Classes
Creating Locations
Adding User Accounts
Viewing User Accounts in System Manager
Modifying User Accounts
Accounts System Configuration
Maintaining Classes, Locations, and Accounts
Managing Proxies
Creating and maintaining user accounts is fundamental to keeping an accurate record of the transactions your
business performs. To make user maintenance as easy as possible, Equitrac Professional provides several automated
ways to add user accounts to the system.
This chapter provides information about:
• the role users play in Equitrac Professional
• ways of categorizing users
• how to add user accounts
• how to maintain user accounts
• administering the accounts database
4 In the User class definition dialog box, enter a unique Name and Description for the new class.
5 If you are using Equitrac Professional’s print tracking functionality, use the drop list to select a popup Style for the
current class. The selected style determines the features and functionality that users within this class have access to
from the various control mechanisms. For information on configuring popup styles, see Popup Styles
Modification Workflow on page 358.
6 Select a method of print tracking behavior for this class:
• Display popup: show popup, track for cost recovery and total cost of ownership.
• Hide popup: hide popup, track for cost recovery and total cost of ownership.
• Silent tracking for device management only: hide popup, track for total cost of ownership only.
• Do not track: hide popup, do not track for cost recovery or total cost of ownership.
• Determined elsewhere: behavior determined by other class settings (device or application).
NOTE: For more information on the hierarchy of tracking options, see Print Tracking Hierarchy on page 346.
7 Select the Default class option if you want to make this new class definition the default class definition.
8 Click OK to save these settings and return to the Manage classes dialog box.
NOTE: You must have user classes configured. For information on configuring user classes, see Creating User
Classes on page 44.
You will need to have configured a scan aliases for this to be applicable. For information on configuring scan aliases,
see the Equitrac Document Capture chapter in the Equitrac Professional Scan Solutions Guide.
To assign scan aliases to select user classes, do the following:
1 In System Manager, navigate to Client config > Classes > Users.
2 In the right pane, right-click on a user class and select Assign scan aliases. A Scan alias assignment for class dialog
box opens.
3 Under Alias Name, find the scan alias you wish to associate with this user class and mark the checkbox next to it.
4 Click OK.
Creating Locations
Locations are used for the geographical grouping of users, devices, validation codes or other Equitrac Professional
elements. A location can be a room, a building, a geographic area, or other physical place that helps classify and group
your data. You might use locations for different departments in your enterprise, different operations in a service
business, different areas in a project.
Follow these steps to create a new location:
1 In System Manager, navigate to System > Configuration > Location settings > Locations to manually add a
location to Equitrac Professional.
2 In the Locations dialog box, click Add and in the new row, enter a Name, Abbreviation and Description
(optional) for the new location.
Abbreviations can be no more than three characters in length. Use the same abbreviation that your time and billing
system uses to keep the data consistent both for transaction disbursements and for transaction exports from
Equitrac Professional to the time and billing system.
3 Click OK.
NOTE: For information regarding importing transaction data, as opposed to validation data, see Determining
Validation Code Visibility on page 100. For information on using the Import Wizard in conjunction with the
Validation by Location feature, see Determining Validation Code Visibility on page 100.
Method Purpose
Validation Import Wizard (import • Most common method for adding user accounts to Equitrac Professional
from Time & Billing System) • After the initial import run subsequent manual imports, or schedule imports to run
automatically.
• See Importing from a Time & Billing System on page 48 for instructions.
Importing users through Active • Use Active Directory Services to batch import user data, then synchronize updates as
Directory Services they occur.
• Minimizes administration because updates occur automatically via communication
with the ADS.
• See Importing Users through Active Directory Services Synchronization on
page 60.
Create accounts manually • Add an account one at a time within System Manager
• effective when you need to add a small amount of users relatively quickly
• See Adding User Accounts Manually on page 62
Allow Equitrac Professional to • auto-create a user account the first time a user prints to an Equitrac Professional-
create users automatically controlled printer, or logs on to the Equitrac Professional Web Client
• The CAS determines if a user account based on the user’s network name exists or not.
If no such account exists, by default Equitrac Professional creates an account using the
user’s network name as the unique identifier
• enables users to perform print transactions even if they don’t yet have accounts in
CAS
• See Auto-creating User Accounts On First Print on page 62
User name Uniquely identifies user accounts within Equitrac Professional. This field is mandatory and, once populated,
cannot change. Typically, the User name field contains a network user name. If you import user accounts
from a time and billing system that does not include a field for network user name, the import process
creates a name based on the full name (if available) or the user code.
Full name This optional field contains the first and last name of the user. If you are importing from a time and billing
system that does not include the network user name, the import process creates a network name based on
the full name, if included in the import.
User code This optional field contains an alphanumeric code attached to each user account. Users enter user codes at
control terminals, embedded devices, and the Web client. User codes (when available) can be exported
with transaction records to the time and billing system.
Because the User name is the key field, it uniquely identifies user accounts and can neither be changed nor duplicated.
At the same time, control terminals, embedded devices, and (typically) your time and billing system identify users by
User code. As a result, both fields are equally important in Equitrac Professional. When importing users, therefore,
the ideal import source contains both network user names and user codes.
If your Active Directory contains a custom field you use to store user codes, use an Active Directory synchronization.
If your time and billing system contains a field for network user name, use the validation import wizard. If neither
source provides the required fields, you can either add the required field to your time and billing system or Active
Directory, or you can import users without the required fields.
If you import users from your Active Directory without importing user codes, you will have to manually add them to
each user account within Equitrac Professional.
If you import from your time and billing system without importing user names, the import process creates them.
Therefore, when you import from time and billing, you do not have to manually add user names. However, when your
users first generate print transactions, their network names may not exist in CAS (because the import generated
arbitrary user names that may not match actual network names). In such cases, Equitrac Professional automatically
creates a new user account based on the current user’s network name. As a result, such users end up with two user
accounts - one based on their actual network names and the other imported from the time and billing system and
based on user codes.
When importing users from your time and billing system, be aware that some users may end up with two user
accounts.
• maintaining records of transactions performed for specific clients to enable you to bill the appropriate clients for
the appropriate transactions.
Your time and billing system or external database can contain a list of active accounts for your organization. When
your users perform transactions, Equitrac Professional prompts them to specify the account for which they are
performing the transaction. To ensure that users only enter accounts that are active in your time and billing system,
Equitrac Professional enables you to import your account roster and validate user responses against it. If a user
provides a valid account ID, Equitrac Professional allows the transaction to continue and tracks it against the account.
If a user provides an invalid account ID, Equitrac Professional returns an error message and prompts the user to enter
a different ID.
Most organizations track transactions to 2 levels of detail: account and sub-account. Equitrac Professional (and this
documentation) refers to accounts as clients and sub-accounts as matters.
In addition to client and matter data, Equitrac Professional enables you to define user codes, definitions, and several
additional types of validation data, known as custom validation types. The term validation code refers to any
combination of user code, client, matter, or custom validation type code.
The first step in importing validation data is to map your validation types (user codes, clients, matters, and custom
types) to the appropriate fields in the Equitrac Professional database. This enables Equitrac Professional to prompt
users for validation data and to track transactions against the correct clients and matters.
The second step is to import validation codes and other transaction tracking data, such as telephone extensions,
through the Equitrac Professional Validation Import Wizard. Typically, you will import user, client, and matter codes
only, and add codes for custom validation types manually. However, if your time and billing system or external
database contains validation codes for your custom types, you can import them in addition to your user, client and
matter codes.
Equitrac Professional reserves the Field1, Field2, and Field3 fields for matter, client, and user codes respectively,
designates all three fields as validation fields, and designates the Client field as the parent of the Matter field. The
Field mappings dialog box represents this default structure as follows:
Equitrac Professional uniquely identifies users by network user name. If your time and billing system contains a field
for network user names, import this field and map it to Equitrac Professional’s User name field.
If your time and billing system contains a field for users’ full names, import this field and map it to Equitrac
Professional’s Full name field. Your time and billing system contains a field for user codes. Import this field and map it
to Equitrac Professional’s User code field.
If you do not import data from the time and billing’s full name field (or if no such field exists), Equitrac Professional
leaves the field empty.
If you do not import data from the time and billing’s network name field (or if no such field exists), Equitrac
Professional creates a user name based on the full name (if available) or the user code. Because Equitrac Professional
uniquely identifies users by the User name field, you cannot edit the user name after you import it. Therefore, use
caution when importing users from your time and billing system.
If your time and billing system uses a different validation structure, you can modify field mappings as necessary to
replicate that structure. If, for example, your time and billing system does not use a client/matter validation code
structure, but rather a single-tiered validation code, disable the parent/ child relationship between clients and matters
in Equitrac Professional. Disabling this relationship also disables the Client field. Equitrac Professional then uses the
Matter field to track validation data.
When mapping your validation data in Equitrac Professional, you can disable the parent/child relationship between
clients and matters, customize fields for validation types and, if desired, mark custom fields as validation data fields.
NOTE: Typically, you will add user, client, and matter codes through an import procedure, as described in Managing
Validation Data on page 79. You can also import validation codes for custom validation types, but typically you add
them manually.
To manually add new validation codes for custom validation types, do the following:
1 In System Manager, navigate to Client config > Validation Codes > <Custom Type>, where <Custom Type>
represents the custom validation type for which you want to add a new code.
2 Select Add under Current tasks in the left pane, or click <Add...> in the right pane.
3 In the <Custom Type> definition dialog box, enter a Name for the code you are adding.
4 Enter a Description, if desired.
5 From the drop list, select a SmartPrompt, if desired. For information on creating SmartPrompts, see Creating
SmartPrompts on page 377.
6 Select or clear the Active, Billable, and Postable options as desired. The Postable option allows you to mark this
validation data for export back to the time & billing system.
7 Click OK to add the code to CAS and close the <Custom Type> definition dialog box.
8 Repeat steps as necessary to add subsequent custom codes.
You can run a validation data import as a manual process using the Validation Import Wizard, or you can automate
Equitrac Professional to run data imports as a scheduled task. To use the wizard, you can either create a new import
template, or for subsequent imports, you can modify an existing import template. The Validation Import Wizard does
not include any default templates.
Before you run the Validation Import Wizard, use your time and billing system to create the import source file. This is
a flat file (.txt format, for example) of the delimited data exported from your time and billing system. This source file
must reside in a shared folder accessible to System Manager on the CAS server before you run the import wizard.
NOTE: If you are performing the import from a remote workstation, you must create or save the import source file to
a shared folder on the CAS server. The wizard does not check the local server, but assumes the source file resides on
CAS.
The following procedure assumes this import is for a first-time installation of Equitrac Professional, including a first-
time data import of validation data with no pre-existing import templates.
To use the Validation Import Wizard, do the following:
1 Select Start > All Programs > Equitrac Professional > Validation Import Wizard. A Validation Import Wizard
opens.
2 Select Create new import. (In the future, you can specify either Edit existing import or Load import from file.)
3 Give the new template a brief Import Name and Description. (In the future, you can select an existing template
and modify the description.)
4 Click Browse to open the location to Load import file from.
5 In the Import source section, select either From ODBC source, or From file.
a Click Configure.
b Specify the DSN, User name, and Password to access the database.
c Click on Test to test the specified connection ID if required.
d Specify the SQL script to run on successful connection with the database.
e If necessary, click on ODBC admin to open the ODBC Data Source Administrator to further configure your
connection to the SQL database.
f Click OK when you have finished configuring the connection.
—Or—
If you select a File source, do the following:
a Click Browse to open the location of the Import source file.
b Select the required file and click on Open.
6 Specify the import Type, selecting either Validation data, Telephone extensions, or Proxy users.
7 Specify the import Mode, selecting either a Full synchronization or Incremental update.
8 Click Next. You will be taken to the step 2: source format page of the wizard.
9 In the # of lines to preview field, enter the number of lines you want to preview.
10 In the Number of heading rows field, enter the number of heading rows the import source file has.
11 In the Ignore lines that start with field, specify any special characters that indicate a row in the source file that the
import wizard should ignore (default is a semi-colon).
12 Select the file input format.
• Specify the Delimited field delimiter if the input is delimited.
—Or—
• Specify that the input fields are fixed length.
13 Enter the quote character(s) used in the import source file that delimits text fields.
14 If necessary, select a new end of line designation in the EOL symbol field. By default, lines are delimited by ASCII
carriage return and line feed characters as the standard in Windows.
15 For each field in your import layout, click Add Field. An Add field dialog box opens.
NOTE: You cannot preview the contents of the import source file until after you configure the fields.
18 Click Next.
20 In the Field processing commands section, click Add. An Add/Edit command dialog box opens.
a Select a field transform Command from the drop-down list. Each command requires specific input and has a
specific purpose. For example, the SPLIT command requires you to specify a split delimiter or position. This
enables you to separate a single field from the source file into two or more CAS fields. Alternatively, the
SUBSTITUTE command requires a search value and a replacement value.
NOTE: For information on the PERL SCRIPT transform, see Sample Perl Scripts for Perl Script Field
Transformations on page 494.
24 In the Select destination field dialog box, select the Available database field to which you want to map the input
field you just selected. The input-to-database field mapping appears in the Selected input fields (mapped to
database fields) list. Note the contents of the Available database field drop-down list will differ, depending on the
type of import source (validation data or telephone extensions) you selected in Step 1 of 5 of the wizard.
25 If this import source file data is for a single location in your organization, select the appropriate location in the
Validation Codes Location field.
4 Click OK.
5 Open the Equitrac Professional menu and left-click the wizard you’ve just edited. Equitrac Professional launches
the wizard on the specified server.
If you are unable to modify the target field from the properties of the wizard as stated above, you can create a shortcut
that populates the command line parameter when clicked:
1 Right-click anywhere on the Windows Desktop. From the menu, select New > Shortcut.
2 In the Shortcut field, type the UNC path for the Import Wizard, or browse to C:\Program
Files\Equitrac\Professional\Tools\EQEPImport.exe. Click Next.
3 Provide a Name for the shortcut, and click Finish. The shortcut displays on the desktop.
4 Right-click the shortcut you just created, and select Properties from the menu.
5 In the Target field, navigate to the end of the string, then add a space, followed by the accounting server name. For
example, OKA2:
6 Click OK.
NOTE: Using the Re-export wizard remotely is ineffective for file exports because it writes export files on remote
machine. It does work well for integrated exports, however.
CAUTION: If you plan to use Active Directory Services to generate user accounts, you must decide before performing
the first synchronization whether or not to use Domain Qualification. See Qualifying Accounts by Domain on page
70 for instructions.
If your Active Directory does not contain a custom field to store user codes, users’ User code fields will remain blank
when you add them through ADS import. To enable these users to access devices controlled by PageCounter and
PageCounter Professional terminals, assign each of them a user code. For information on this procedure, see
Modifying User Accounts on page 65.
WARNING: The EQ services must be started by a Domain account with access to the contact Active Directory. If
services are started under the local administrative account, the Active Directory synchronization will fail.
It’s important to select options in the correct order in the Active Directory Synchronization dialog box, so follow the
steps provided below carefully. Performing these steps causes a task to run in the background. After you configure
your synchronization parameters and the first synchronization has run, you can verify your configuration by
reviewing the Users list in System Manager.
1 Enable Domain Qualification if you plan to synchronize accounts against multiple domains. Ensure that you read
the information in Qualifying Accounts by Domain on page 70 before continuing. Failure to enable domain
qualification before initial import will result in duplicate account creation.
2 In System Manager, navigate to Configuration > Network environment > Active directory synchronization.
3 Under Domain Controllers, click Add. An Add Domain Controller dialog box opens. Type the domain name in
the field and click OK to add the domain to the list.
A Domain controller refers to a name shared by a group of computers that use a common accounts database.
4 Click on the Filter button if you wish to filter users in the listed domains by specific attributes. A standard
Windows LDAP filter dialog box opens. Use this to specify basic or advanced conditions. Only user accounts that
meet these conditions will be included in the synchronization.
NOTE: If filters are applied after your initial user import, updates to users who do not match the filter specifications
will be ignored.
5 Under Containers, click Add. A container is a subset of a Domain controller. Select one or more containers that
belong to the selected Domain Controller.
CAUTION: Ensure that the OU containers you choose are comprised of user account data only. If the OUs contain
other data (such as system or contact info), you will see unexpected results. You may need to create specific OU
containers to be used only for importing and synchronization purposes.
6 Click on the Test button to confirm that your domain controller values are properly configured. An Active
directory lookup dialog box opens. Enter a user account name. If the domain controller can be contacted, the
dialog box will show the ADS properties associated for that account. You can use this information to refine your
container and filter configuration.
7 Adjust the Synchronization interval to change how often Equitrac Professional synchronizes its accounts
database with the specified Active Directories. The synchronization interval value must be at least 15 minutes.
8 Select or clear the Active Directory update options—Adds, Changes or Deletes—to specify which Active
Directory actions that are applied to Equitrac Professional during subsequent synchronizations.
9 In the Assign Values from Active Directory section, you can link Equitrac Professional user fields to ADS
attributes. Note that you should enter the Active Directory attribute name, not the field label from Windows ADS
tools.
• The Equitrac Professional Usercode field can be mapped to a custom ADS attribute. This attribute allows users
to authenticate by user code when allowed.
• In addition to Usercode, you should also consider mapping the following Equitrac Professional fields: Home
Print Server, Alternate Usercode (for card identification), Home folder (for Equitrac Document Capture
scanning), Primary extension, Secondary extension, Call site (name as configured for Call Accounting) and
Location.
10 Click Import to import user data for the first time. The Import task runs in the background on the CAS, and may
take a few minutes depending on the size of the Active Directory you are importing.
11 You can click OK to exit the dialog box. The task will continue to run even though the dialog box is closed.
12 After a few minutes, refresh System Manager, then check the list of Users to ensure successful import of the
accounts. Also open the properties for a user account and ensure that the expected values were assigned.
NOTE: Equitrac Professional auto-creates the user account the moment the user is presented with the Print Client
popup. Therefore, the user account is created in System Manager regardless of whether or not the user completes or
cancels the print transaction request.
When Equitrac Professional automatically generates a user account, it does not provide a user code. Therefore, users
with automatically-generated accounts do not have immediate access to Equitrac Professional control terminals. To
provide them access, assign them a user code. For information on this procedure, see Modifying User Accounts on
page 65.
2 In the User definition dialog box, enter a User name. Equitrac Professional uses this name as a unique identifier
for the user.
3 Enter the user’s Full name.
4 Assign the appropriate Location, or leave the field Undefined.
5 Enter the user’s Email address, if you are using email notification within your Equitrac Professional environment.
6 If you have defined user classes, you can assign a Class name from the drop list, or use the General users
default.
7 In the User Code field, enter a unique user code for Equitrac Professional control terminals (this code takes the
place of a primary PIN for users logging onto the terminals or the Web Client). When creating user codes, ensure
you adhere to the configured syntax for your terminals. See Field String Syntax on page 471 for information on
setting syntax for terminal fields.
8 In the Alternate user Code field, enter the unique access code from the user’s magnetic or proximity card readers.
When entering the alternate user code value, ensure you adhere to the configured syntax for the card readers. For
information on determining user card reader codes, see About Card Reader Support on page 327.
9 Specify a Phone auth. code for this user. This is the identifier assigned to this user in the Time & Billing system for
phone transactions; you can edit this code in System Manager.
10 Specify an Alternative reference for this user. This code is the identifier assigned to this user in the Time & Billing
system for users in voice-over-IP (VoiP) environments.
11 Define Client and Matter codes for this user. These codes relate to the Auto-charge feature in System Manager >
Configuration> Equitrac Professional settings > Auto-charge exception settings. Specify a client/matter
account to which Equitrac Professional will charge this user’s exceptions automatically, if the exception remains an
exception for longer than the time configured in System Manager. The client/matter account you assign here must
be a valid account before the assignment can work.
12 Enter a home print server for this user.
13 Enter a home folder for this user. This folder can be used for Equitrac Document Capture scan operations.
14 The Creation Source identifier indicates the source of this user data:
• Auto-created: indicates users that Equitrac Professional auto-registers on their first print or first login through
the web interface.
• System Manager: indicates users you have added manually in System Manager.
• Active Directory: indicates users imported through an active directory synchronization.
• Import: indicates users created through validation import.
15 Select the Active checkbox if this user’s validation code is active or inactive.
16 Select the Postable checkbox to specify whether or not this user account data is available for posting as export data
to the Time & Billing system.
17 Select the Notify by e-mail checkbox to have an e-mail sent to the user when there is an exception transaction they
need to edit. For more information about managing exceptions, see Managing Exception Editing on page 405.
18 Select Can approve transactions to indicate if this user has the authority to approve transactions via the Web
Client.
19 Click Set user as proxy to identify this user as someone with proxy rights to edit another user’s transaction data.
This opens the Proxy definition dialog box; for more information on managing proxies in Equitrac Professional,
see Managing Proxies on page 74.
20 Click Phone extensions to assign phone extensions to each specific user. You can assign multiple extensions to
any single user. Equitrac Professional imports phone extensions from the time and billing system as part of the
validation import.
21 Click OK to save your settings.
Once you create a user entry in the Equitrac Professional database, that record identifier is permanent. Even if you
delete the user account later, you cannot recreate that identifier, even by adding a new account with the same user
code.
NOTE: If you have renamed Field1 in Field mapping, your field name shows in the dialog box rather than UserCode.
1 Open Start > Programs > Equitrac Professional > System Manager and connect to the local server.
2 In System Manager, navigate to System > Configuration > Access > User authentication. The Authentication
methods dialog box opens.
3 In the Authentication mechanisms section, select the methods by which users will login to Equitrac Professional
interfaces.
a Check By UserCode to allow users to login only with their unique identification codes. Typically, these are the
time and billing user validation codes assigned to users on import.
b Check External user ID and password to allow users to login with network credentials according to the
external authority information settings you configure in step 8.
c Check By UserCode with external password to allow users to login by entering their UserCodes in the User
ID field and their network password in the Password field. Use this option to enforce device access security.
Users can swipe their cards at Equitrac interfaces and then type in their network password.
4 Under UserCode modification, select Zero fill if the user codes at your site start with zeros and your users only
want to enter significant digits to login.
In the Code length field, enter the number of digits expected in the UserCode. The server automatically pads
UserCode values with preceding zeros to the full UserCode length.
5 If you require different login methods depending on the Equitrac interface used, click on the Overrides button. A
Manage overrides dialog box opens.
a Under Client type, click <Add...>. A client type row is added to the list.
b Click on the drop down arrow for the new row and select an Equitrac interface client type.
c Click OK.
d Select the Authentication mechanisms that will be used to verify the user logins through this type of Equitrac
interface.
For instance, you may want all users to login to the Equitrac Professional Web Client with network credentials
rather than UserCodes or you may enforce network logins on embedded scan workstation clients for single sign-
on. Equitrac interfaces that are not included in overrides you configure will follow the default configuration.
6 Under External authorities, select which network authentication methods are in use at your site.
a Select the Windows authentication option to configure Equitrac Professional to validate logins against
Windows. By default, user credentials will be checked against the domain to which the CAS belongs. If your
users belong to a different domain than the CAS, specify a different Default domain.
b Select the LDAP authentication option to validate accounts against a default LDAP server name and type.
Specify a Server name, select a Type from the drop-down list, and select or clear the Force SSL option to
enable or disable LDAP Secure Socket Layer encryption.
7 Click OK to save the changes.
8 Set the Authentication options. This section determines the information the user must enter to gain access to the
device.
a From the Input type drop down list, select whether the user must authenticate via Card swipe or keypad entry,
Card swipe only, or Keypad only. If Keypad only is selected, the Authentication mechanism options disable.
b From the Prompt for password drop-down list, select if the user is asked for a password Always, or Only with
keyboard login.
c If you choose a card swipe option, you must configure the card setup by specifying the first and last position of
stripe data for the User Code. In the Card setup area, enter the data start position and the data stop position in
the Use data from position fields. The first value must be less than the second, and neither can exceed 39.
Values of 1 and 39 are recommended for proximity cards and track 2 magnetic stripe cards to guarantee
capture of the full information string.
d Determine the type of HID decoding. See Determining HID Decoding Values on page 330 for more
information.
9 Configure the Card Reader Data Positions. When a security card is swiped at the TPC, the Equitrac Professional
server needs to know which data positions in the card data should match a unique user identification code value in
its authentication database.
To configure security cards to function with the TPC, use System Manager to define the positions in the card data
where the user identification code is located.
a In the Use data from position and to fields, enter the values of the first and last digits where the user code data
starts and stops within the complete card data. See Determining Card Data Positions on page 328.
b If your company uses HID cards and you must identify specific authentication data within the HID card data,
click the <none> link beside HID decoding and set the HID decoding values. To learn about setting values for
HID decoding, see Determining HID Decoding Values on page 330.
c When you have entered the data position values and, if necessary, the HID decoding values, click OK to save
your changes. We recommend testing your TPC card reader data settings by swiping a security card at a TPC
with a card reader and verifying that the User field on the TPC screen is filled in correctly.
CAUTION: Be accurate in defining the data positions that will uniquely identify and validate each user in your firm. If
the card data positions do not isolate the data string that is unique for each user, your firm may experience incorrect
TPC user logins.
NOTE: The Equitrac messaging service is installed automatically with the Equitrac client. No additional configuration
is required. This service is not supported for UNIX print servers.
• Sending a popup message: Users receive an error message on the workstation from which the print request
originates. If you choose this option, the Windows Messenger service must be running on the client’s workstation.
• Sending the user email: Users receive an email notification of the transaction error. Equitrac Professional uses the
email address configured in Accounts Manager.
NOTE: You must configure System Manager > Configuration > Network environment > SMTP mail server
settings to enable email notifications.
• Printing a notification page: Equitrac Professional prints a separate error notification on a printed page.
By default, the printed notification page includes job status, the error message, and the user ID. You can customize
the printed notification page to provide users with more detailed information. You can format up to five lines
separately with text as well as escape codes. If you leave the field blank, Equitrac Professional assumes the
following escape code entries, in order: job status, error message, user ID, account.
The following table describes available escape codes, print notification details, and possible error conditions.
Escape
Print Notification Details Possible Error Condition
Code
\P Printer name —
2 Enter the SMTP Email Server (DNS name or IP address) of your network email server.
NOTE: Your mail server must support SMTP mail in order to use email features in Equitrac Professional. Older
systems, such as Microsoft Mail, may not support SMTP. Refer to your mail server documentation for details.
3 In the field provided, enter the Mail From address from which system-generated messages originate.
4 Check Basic Authentication if your SMTP mail server requires a user name and password each time it generates a
message, and provide a default user name and password against which Equitrac Professional authenticates these
messages.
5 Click OK to save the changes.
Therefore, to prevent slowing down system resources by doubling the number of user accounts unnecessarily, decide
whether or not to enable Domain Qualification before you perform a synchronization.
If you enable domain qualification and want to subsequently create users manually, ensure that you include the
domain qualification in the user ID you create, using the following format: user’s_domain\userID.
To set the domain qualification option, do the following:
1 In System Manager, navigate to System > Configuration > Network environment > Domain qualification.
2 Select or clear the Qualify all user IDs with NT domain information option as necessary, depending on whether
or not you want to use domain-qualified user IDs.
3 If necessary, provide a default domain name for unqualified users attempting to print.
4 Click OK to save the changes, or Cancel to close the window without saving changes.
NOTE: Use caution when removing entries in the Manage user classes dialog box. Equitrac Professional does not
ask you to confirm your selection before deleting the class from the list.
Modifying a Location
After adding a location to System Manager, you can edit any of its properties.
To modify a location, do the following:
1 Navigate to System > Configuration > Locations settings > Locations.
2 Select the Location, and modify the desired Name, Abbreviation or Description.
3 Click OK.
Removing a Location
You can remove a location in System Manager at any time. However, you will receive an error if you try to delete a
location assigned to one or more devices.
To remove a location, do the following:
1 Navigate to System > Configuration > Locations settings > Locations.
2 Right-click anywhere on the desired Location’s row.
3 Select Remove from the menu, and click OK.
NOTE: To select multiple user accounts, hold [CTRL] and select the desired codes, or hold [SHIFT] and select the first
and last codes in the desired, consecutive range.
3 Click Yes. Equitrac Professional removes the selected user accounts from the database.
If you removed user accounts from your time and billing system or Active Directory, you can also use a re-import
procedure to reflect the removal of those accounts in System Manager. For information on importing, see the Equitrac
Professional Installation Guide.
Managing Proxies
A proxy is a person who is performing cost recovery tasks, or accessing cost recovery data, on behalf of another user.
This includes exception editing for another user, or generating reports on another user’s transactions. Proxy rights
apply to all types of user transaction: copy, fax, phone calls, and so on.
Within Equitrac Professional, you can assign proxies at a global or regular level, the latter covering both users and
locations. You can apply a proxy to one or more users or locations at the same time; you can also associate any user or
location with multiple proxies.
A proxy may also be both regularly and globally applicable, and you can define multiple global proxies.
When you create either global or regular proxies, you can configure the proxy to notify the transaction’s original user
by email when the proxy edits exceptions on the user’s transactions. Likewise, you can configure users to require
notifications via email when another user edits transactions by proxy. Equitrac Professional uses the following logic
process to determine email notifications for proxy activity:
1 Check the User configuration to determine if user requires email notifications; if yes, Equitrac Professional sends
the email notification.
2 Check for user-level proxies; if the proxy requires exception notification, Equitrac Professional sends the email
notification.
3 If Equitrac Professional finds no user-level proxy, it checks for a location-level proxy; if the location proxy requires
exception notification, Equitrac Professional sends the email.
4 If Equitrac Professional finds no location-level proxy, it checks for a global proxy; if the global proxy requires
exception notification, Equitrac Professional sends the email.
5 If there is no user information associated with the transaction data, Equitrac Professional checks for a global proxy
to notify (if the global proxy requires notification).
2 In the Release by Proxy column, select the checkbox of the proxy you want to be able to release secured
documents. The box has three settings:
• No selection indicates that SDR is disabled for this proxy, but can be enabled by selecting this box if required.
• A gray x indicates that SDR is disabled and cannot be enabled for this user. The proxy has been disabled by an
administrator.
• A black x indicates these proxies can release documents on behalf of the user.
—Or—
• To enable all regular proxies in the list, click the Enable RBP for all regular proxies toggle button.
• To enable all global proxies in the list, select the Enable RBP for all global proxies toggle button.
3 In the Notify for RBP column, select the checkboxes of the proxies for whom the user receives a notification when
they release a secured document. When a selected proxy prints the user’s secured document, the proxy is notified
by email that a job is available for release. Note that only regular (individual) proxies receive these email messages;
global proxies do not. The default setting for this option is enabled (checked).
NOTE: Proxies whose SDR settings are disabled (gray check) cannot send notification email messages.
4 Select the Proxies have access to web scans checkbox if you want this user to be able to work with the scan jobs of
anyone or any location for whom they are a proxy.
5 Select the Enable proxy reporting checkbox to limit the proxy from seeing information about any potential
proxies the proxy has. This is useful for situations where you want to enable the proxy to see data based only upon
location.
6 Click <Add...> to open the Proxy definition dialog box.
CAUTION: This selection disables the proxy definition currently being configured. For more information on disabling
proxy definitions, see Revoking Proxy Rights on page 77.
NOTE: If you select Global proxy, you do not have to configure proxies for location or user and may skip to step 13. If
you select Regular proxy, continue to the next step.
11 For regular proxies, if you have locations defined in System Manager and want to assign proxy rights at the
location level, do the following:
a Under Proxy for location, click <Add...>.
b In the Add location to proxy list dialog box, select a Location from the drop down list and click OK.
For information on configuring locations, see Creating Locations on page 46.
12 Assigning proxy rights at the user level allows the proxy user the ability to edit transactions for the users
configured here. To assign proxy rights at the user level, do the following:
a Under Proxy for user, click <Add...>
b In Add user to proxy list dialog box, enter a User login ID and click OK.
13 Select Notify by e-mail if you want the proxy user to receive email notifications of any transaction exceptions.
14 Click OK to save the configuration.
Topics:
About Validation Codes
Validation Code Workflow
Configuring Equitrac Professional Fields
Enabling or Disabling the Parent/Child
Relationship between Clients and Matters
Adding Validation Codes
Maintaining Validation Codes
Managing Telcodes
Equitrac Professional primarily deals with two types of data: validation data (consisting of user, client, and matter
data) and transaction data. Equitrac Professional requires validation data to ensure that access to the terminals and the
system itself is only provided to authorized users, and to bill transactions processed at these terminals to the
appropriate user or client/matter combinations. When the core accounting server (CAS) receives the proper validation
data, a transaction can occur within the Equitrac Professional environment, thereby generating transaction data.
While validation data includes user, client, and matter data, the term validation code refers to any client-matter code
combination. Equitrac Professional enables you to combine client and matter codes to create single-tiered validation
codes, which you can export to your time and billing system or other external application. You can also create custom
validation types that you can use in conjunction with the standard client and matter types.
During initial configuration, most administrators use the import wizard to import validation codes from a time and
billing system. When you have imported your codes, you can use System Manager to manage them. For information
on using the import wizard, see Importing from a Time & Billing System on page 48.
This chapter covers client and matter codes only; for information about assigning user codes, see Managing Users on
page 41.
NOTE: See Adding Validation Codes on page 86 to add validation codes manually, or see Importing from a Time &
Billing System on page 48 for information on importing them from a time and billing system.
In addition to clients, matters and descriptions, Equitrac Professional enables you to define several custom validation
types. Use custom types to collect validation data other than client/matter or description data. For example, you may
want to track the geographic region of the client/matter for which a transaction is performed. Defining custom types
requires that you customize default Equitrac Professional data fields and designate them as validation data fields.
When you create terminal prompts or print popup styles, you can select these validation data fields for your prompt or
style; the terminal or Print Client popup subsequently prompts users to provide data for the selected fields.
When creating the terminal prompt or popup style, you can specify whether you want the server to validate users’
entries against the data residing in the core accounting server (CAS). If a user provides blank or invalid data, the
terminal, TouchPoint Console, or controller interfaces (for example, MEAP embedded), or client popup prevents the
user from completing the transaction (assuming you have designated the field as requiring server validation). For
more information on configuring terminal prompts, see Creating a General Configuration Set on page 272. For
information on creating a popup style, see Popup Styles Modification Workflow on page 358.
Client/Matter codes
Each client is assigned a unique code. Each matter for each client is assigned a matter code. The matter code must be
unique to the client code to which it is assigned. In such a configuration, two different clients can have identical matter
codes associated. However, matter codes must associate with unique client codes.
NOTE: In such a configuration, it is possible to enable users to identify account information by entering matter codes
or client codes. A popup style can include both client and matter input fields, allowing users to select which code to
enter. For information about setting up such a scenario, see Configuration for Validation by Best Practice on page
371.
Renaming a Field
If you need to rename a field, the field must be editable. Any fields that are used as validation data are not editable and
will appear in the Web Interface as non-editable. Clear the Validation checkbox for the field you want to rename.
Double-click on the field to rename it, then enter the new name. When the name is entered correctly, check the field
again if this field should continue to be used as validation data.
2 In the field mapping dialog box, modify the Name and Description for the field you want to add. You can replace
the Field4 through Field8 names because they are simply default placeholders. In the example above, Field4 is
renamed ‘Location’.
3 Enable the Validation data field option for the new field.
4 Modify settings for other fields if needed, and click OK to close the Field mapping dialog box.
The new validation field appears in the Client configuration area of System Manager, shown in the image to the right.
For information on manually adding codes to the new validation field, see Adding Custom Validation Codes on page
88.
NOTE: Only modify this relationship to synchronize Equitrac Professional’s validation structure with your time and
billing system’s validation structure.
To modify the parent/child relationship between clients and matters, do the following:
1 In System Manager, navigate to System > Configuration > Equitrac Professional settings > Field mapping.
3 From the drop list, select either None (to disable the parent/child relationship) or Client (to enable the parent/
child relationship).
NOTE: These instructions assume you are using the default Client and Matter names for your fields. If you have
renamed your Client and Matter fields, select the name of the field assigned to the Field2 row.
4 Click OK.
NOTE: The billable setting at the matter level overrides the billable setting at the client level; this setting is inherited,
but the user can change the flag if necessary.
2 Select Add under Current tasks in the left pane, or click <Add...> in the right pane.
3 In the Client definition dialog box, enter the appropriate Client code. Ensure that you assign the client the same
code assigned to it in your time and billing system.
2 In the Matter column of the client to which you want to add a matter, click the ellipsis (...) button.
3 In the Matter frame, click on the <Add...>to open the Matter definition dialog box.
4 In the Matter definition dialog box, enter the appropriate Matter code. Ensure that you assign the matter the same
code assigned to it in your time and billing system.
5 Enter a Description for the matter, if desired.
6 From the drop list, assign the matter a SmartPrompt for print, if desired. For information on creating
SmartPrompts, see Creating SmartPrompts on page 377.
7 Select or clear the Active and Billable options as desired.
NOTE: The Billable option you set at the matter level overrides the Billable option you set at the client level. For
example, if you mark a client as billable but a matter as nonbillable, transactions performed for that client/matter
combination are nonbillable.
8 Click OK to add the matter to the client and close the Matter definition dialog box.
9 Repeat steps as necessary to add subsequent matters to the same client, or to add matters to different clients.
3 Click the desired code to display the <Validation type> definition dialog box, where <Validation type>
represents the type of code you are modifying.
4 Modify the code’s attributes as necessary and click OK.
5 Repeat steps as necessary to modify attributes for additional codes.
3 Select the codes you want to remove by clicking any of their attributes other than their actual codes.
NOTE: To select multiple codes, hold [CTRL] and select the desired codes, or hold [SHIFT] and select the first and last
codes in the desired, consecutive range.
4 Right-click anywhere in the right pane and select Remove from the menu. A dialog box prompts you to confirm
that you want to remove the selected codes.
5 Click Yes.
6 Repeat steps as necessary to delete additional codes.
Managing Telcodes
Telcodes are a form of mapping client and matter data to information collected through your phone system. They are
numeric codes corresponding to client/matter combinations already existing in Equitrac Professional.
NOTE: Do not confuse telcodes, which map client/matter data to numeric values, with telephone extensions as a
form of validation data you can import from a time and billing system.
Equitrac Professional uses telcodes because users can only enter numeric codes through a telephone handset or fax
machine. If all codes are numeric to begin with, there is no need to use telcodes. However, alpha-numeric account
codes (including delimiters) need telcode substitutions for use via the telephone or fax machine.
Unless you configure the application to do otherwise, Equitrac Professional generates telcodes automatically during
validation import or manual entry. To prevent auto-generation, you can either configure Equitrac Professional to not
auto-generate telcodes, or explicitly assign telcodes to client/matter definitions.
NOTE: Telcodes are very rarely auto-generated for User Codes. Numeric codes corresponding to the User represent a
telephone AuthCode and an Extension.
2 In the Telcode configuration dialog box, specify the telcode generation method:
• Do not auto-generate: prevents Equitrac Professional from automatically creating and assigning telcodes
when you import or manually create client/matter records.
• Convert non-numeric characters: for auto-generated telcodes, substitutes an asterisk (*) for any alphabet or
symbol character.
• Letter to Digit: substitutes a numeric value in the place of any letter of the alphabet, according to the following
table of options:
A 2 A 21 A 2 A 21
B 2 B 22 B 2 B 22
C 2 C 23 C 2 C 23
D 3 D 32 D 3 D 31
E 3 E 33 E 3 E 32
F 3 F 34 F 3 F 33
G 4 G 43 G 4 G 41
H 4 H 44 H 4 H 42
I 4 I 45 I 4 I 43
J 5 J 54 J 5 J 51
K 5 K 55 K 5 K 52
L 5 L 56 L 5 L 53
M 6 M 65 M 6 M 61
N 6 N 66 N 6 N 62
O 6 O 67 O 6 O 63
P 7 P 76 P 7 P 71
Q 0 Q 01 Q 9 Q 74
R 7 R 77 R 7 R 72
S 7 S 78 S 7 S 73
T 8 T 87 T 8 T 81
U 8 U 88 U 8 U 82
V 8 V 89 V 8 V 83
W 9 W 98 W 9 W 91
X 9 X 99 X 9 X 92
Y 9 Y 93 Y 9 Y 93
Z 0 Z 02 Z 9 Z 94
NOTE: If you have a large number of client/matter records, the odds of telcode duplication increase with simpler
substitutions, such as DTMF 1 or 3; the more records you have, the more it would be advisable to select DTMF 2 or 4.
3 Select Pad client if you wish to set the client portion of the telcode to a certain number of digits; specify the Pad
character (often a numeric value such as 0), and a maximum width (number of characters used to represent the
client portion of the telcode).
For example, if you have a client code “RKO”, and select a regeneration method using DTMF 2, with a maximum
width of ten characters and padding with zeros as necessary, the client portion of the new telcode would be
0000755567: R=77, K=55, O=67, with an additional four zeros to pad the code to ten characters.
4 Select Insert delimiter, specifying the character to use as a delimiter, if you require something to mark the break
between the client and matter portions of the telcode. For example, you might use a hyphen as a delimiter between
the sections.
5 Select Pad matter if you wish to set the matter portion of the telcode to a certain number of characters; specify the
Pad character (often a numeric value such as 0), and a maximum width (number of characters used to represent
the client portion of the telcode).
For example, if you have a matter code “BGE”, and select a regeneration method using DTMF 2, with a maximum
width of five characters and padding with zeros as necessary, the client portion of the new telcode would be 22433.
NOTE: If you specify a padding width that is smaller than the number of digits that result from code generation, as
shown in the example above, then the regeneration process will automatically truncate the code at the specified
number of digits. In the example shown above, “BGE” results in six digits (B=22, G=43, E=33), but the configuration
only allows for five digits in the final code.
Using the examples in the preceding steps, a client/matter combination of RKO-BGE will result in a generated
telcode of 0000755567-22433.
6 Specify a replacement character for any non-convertible characters found in the client/matter combination (for
example, accented letters). If you leave this option blank, the generation process will remove non-convertible
characters. Test this setting as required.
7 Select Auto-increment telcode in case of a duplicate in order to avoid having Equitrac Professional attempt to
assign the same code to more than one client/matter combination. If you configure Equitrac Professional with
numeric telcodes only, these codes will increment sequentially.
NOTE: If your telcodes contain any kind of non-numeric characters, however (asterisks or hyphens, for example),
Equitrac Professional cannot increment the codes sequentially, but will still assign a unique code in the format you
determine in this dialog box.
NOTE: The Active, Postable, and Billable flags for every matter remain unchanged, unless you change the state of
the corresponding checkbox.
Topics:
Configuring Locations
Importing Transaction Data
Maintaining Transactions
Exporting Transactions
Scheduling Transaction Imports/Exports
Re-exporting Transactions
Equitrac Professional is designed to accept transactional data from devices registered in System Manager, apply cost
definitions to that data, and store the data along with its associated cost in the core accounting server (CAS) database.
When scheduled, Equitrac Professional exports this data to a time and billing system.
Transactions with missing or invalid data are flagged as exceptions. Because of the missing data, such transactions
cannot be accurately billed. Equitrac Professional provides you with the ability to edit these exceptions so you can
correct or supply the invalid or missing information.
Transaction types are allotted based upon their subtype in order to organize the transactions by type. Every
transaction has a type and subtype. These are the available transaction types:
• Document (doc)
• Telephone (pho)
• Disbursements (dsb)
The Document type has the following subtypes:
• cpy = Copy (cpy)
• scn = Scan (scn)
• fsn = Fax sent (fsn)
• frc = Fax received (frc)
• prn = Print (prn)
Configuring Locations
Equitrac Professional 5 transactions can be assigned to specific locations as they are collected. This is useful for firms
that need to segregate validation codes, devices, users and exported transactions. Equitrac Professional reports are also
grouped by location by default.
3 Define your location by adding a Name, three-character Abbreviation, and Description in their respective fields,
then click OK. The Web Client and reports show the abbreviation and name.
4 Apply location codes to your validation codes. You can manually assign locations in System Manager, or specify
locations when importing validation data through the validation import or active directory synchronization for
your users. When manually assigning locations, use multiple select to apply the same location code to many
validation codes at once.
CAUTION: The location assigned to a matter code (child) must match the location assigned to its client code
(parent).
2 Click on the Priority 1 and/or Priority 2 checkbox(es) and select a validation code type to specify which
validation data item takes precedence for determining an overall source validation location for transactions.
3 Select either Apply device location or Apply validation location.
4 Click OK.
Export Wizard
Likewise, when using the Export Wizard, as part of Step 4 - Mapping, you can select to export Transaction Locations
and Validation Locations as necessary.
NOTE: In the Exception Editing columns of the Maintenance > Default Settings view or the My Preference view,
“Location ID”, "Location Abbreviation" and "Location description" refer specifically to transaction location.
Reports
By default, most reports automatically group data on the basis of the transaction location. To limit the report to
localized data only, you can:
• Create a filter based on location
• Generate a report based on the filter
• Save the report as a custom personal report
• Schedule a report based on this custom, locally-filtered report
NOTE: For information on using the Import Wizard in conjunction with the Validation by Location feature, see
Determining Validation Code Visibility on page 100.
You can run a transaction data import as a manual process, or you can automate Equitrac Professional to run data
imports as a scheduled task. To use the wizard, you can either create a new import template, or you can modify an
existing import template.
NOTE: The following procedures assume this is a first-time import with no pre-existing import templates.
CAUTION: If you plan to import disbursement transactions, see Importing Disbursement Transactions on page
114 prior to using the Transaction Import Wizard.
7 Specify any special characters that indicate a row in the source file that the import wizard can ignore (default is a
semi-colon).
8 Select the file input format.
• Specify the field delimiter if the input file is delimited.
—Or—
• Specify that the input fields are fixed length.
9 Enter the quote character used in the import source file that delimits text fields.
10 If necessary, select a new end of line designation in the EOL symbol field. By default, lines are delimited by ASCIII
carriage return and line feed characters as the standard Windows.
11 For each field in your import layout, click on Add Field. An Add field dialog box opens.
• Give the import input field a unique field name.
• Keep the Input field checkbox selected if the field data originates from the input file. Clear the Input field
checkbox f the field data is not included in the input file. Non-input fields are typically data required for import
into CAS but are not known by the external system that generates the input file. Any field you specify as a non-
input field activates the Value field. Either type in a hard-coded value for all input records or use the Select
button to choose a predefined value. For instance, you may use non-input fields to map to required Equitrac
Professional database fields.
• Select the data type from the drop-down list.
• If you select a date and time or time span data type, use the Set Format button to specify the format of the
expected field entries. For date and time, you may specify a format that includes year, month, day, hours,
minutes, seconds, A.M/P.M. indicator, as well as the delimiters (if any) between those fields. Time span fields
are used for transaction durations. You may specify a form that includes hours, minutes, seconds, as well as any
delimiters between those components.
• If you are using a fixed-length import file format, specify the position and length of this field in the import
source file.
• Click OK to close the Add field dialog box.
12 Continue to add Edit, Delete, or Clear All field entries in this window until you have the input format you require.
13 Click Refresh Preview to see the layout of the import data, according to your defined fields. You can specify the #
of lines to preview (default is 20 lines), and refresh to update the preview.
NOTE: You cannot preview the contents of the import source file until after you configure the fields.
14 Click Next.
15 In the Field processing window, you can preview your fields.
16 Under Field processing commands, click Add. An Add/Edit command dialog box opens.
a Select a field transform command. Each command requires specific input and has a specific purpose. For
example, the SPLIT command requires you to specify a split delimiter or position. This enables you to separate
a single field from the source file into two or more CAS fields. Alternatively, the SUBSTITUTE command
requires a search value and a replacement value.
NOTE: For information on the PERL SCRIPT transform, see Sample Perl Scripts for Perl Script Field
Transformations on page 494.
In order to import the data, you must use the Transaction Import Wizard to create an import configuration containing
information about the specific database table to use, the values to map, filtering to be performed on the data (if any),
the purge interval and other information. Once the configuration is created, it can be saved as a template to be re-used
at any time, or scheduled to run automatically. The Transaction Import Wizard does not include any default templates.
Data is imported incrementally, augmenting existing data with data that has been added to the ODBC source since the
last import.
CAUTION: If you are already importing AccuRoute transactions using flat files generated from the AccuRoute server,
we recommend deleting the already imported records from the Omtool table prior to creating a new import
configuration. If you import data from the database after already using a flat file created from the same database, it
can result in duplicate transactions being stored in Equitrac Professional.
When creating a Transaction Import Configuration, you can control whether the transactions in the original ODBC
table are purged. Transaction databases can grow quickly, and purges of older data that have already been imported
into Equitrac Professional is necessary to control the maximum amount of transactions in the system at any given
time, and recommended to reduce storage requirements and streamline the import process. Data purge parameters
can be set based upon the needs of your enterprise.
NOTE: Setting aggressive parameters in the purge configuration can be counterproductive in cases where you are
trying to diagnose data flow issues between systems. Equitrac recommends choosing a maximum age around 8 to
12 weeks.
In order to properly map the contents of the source data to Equitrac Professional, you may need to use a tool to browse
the data in the source database to determine the exact names of the fields to map.
NOTE: This process does not import validation codes. For information on importing validation codes, see Using the
Validation Import Wizard on page 52.
To use the Transaction Import Wizard, complete the following procedure. The procedure assumes this import is for a
first-time installation of Equitrac Professional, including a first-time data import of transaction data with no pre-
existing import templates. Once you have configured an import, it can be saved as a template that can be loaded or
edited using the Edit existing import or Load import from file options instead of creating a new import, as
mentioned in step 2:
1 Navigate to Start > All Programs > Equitrac Professional > Transaction Import Wizard. A Transaction Import
Wizard opens, indicating the first step of a five step import process:
The field on the left of the dialog indicates which step is being performed by presenting it in bold.
2 Select the Create new import radio button.
3 In the Import name field, provide a brief import name for this configuration.
4 In the Import source box, select From ODBC source, and click Configure. An ODBC import source
configuration dialog box opens:
b In the User name and Password fields, enter the authentication information to access the ODBC link. These
should be identical to the login password and ID set up when the ODBC link was created.
6 Define the cost recovery table information. These fields identify the valid pre-conditions for acceptable
transaction data import over ODBC. Equitrac Professional can assign values to these fields in order to determine
when and whether the information has been imported. Equitrac Professional writes information to these fields
during the import process to ensure no duplication or loss occurs.
CAUTION: If these particular fields cannot be found, or cannot be written to, Equitrac Professional will not attempt
to import data from an external source.
a In the Input ID field, enter the name of the field that contains the ID of the import run. Every time an import
is run, a unique ID is assigned to it.
b In the GUID field, enter the name of the field that contains information provided by Equitrac Professional to
ensure no duplicate records are input going forward.
c In the Time Inserted field, enter the name of the field that contains the time value the record was inserted in
the AccuRoute CostRecoveryData table. This is used to determine the behavior of the purge feature.
d Specify the Cost recovery table name used to collect the imported information. Typically, the table is named
CostRecoveryData in the AccuRoute database.
7 Specify the SQL script to run on successful connection with the database. This is typically a select statement
that defines which fields and records are imported from the source database. See Defining an SQL script for ODBC
import on page 113 for more information.
CAUTION: The Transaction Import Wizard uses information from step 1 of the Wizard in the Field Mapping step
(step 4). Specifically, it maps ODBC table fields to Equitrac Professional 5 fields. It is important to use actual field
names in the SQL SELECT statement, rather than an asterisk (*). The field names defined here are carried forward to
step 4 of the Wizard.
8 Click Test to test the ODBC link to the database. Once the test passes, click OK to return to Step 1 of the Wizard.
9 To automatically purge transactions, select the Purge transactions from cost recovery table after checkbox, and
provide a time interval in weeks that is appropriate for your enterprise in the field provided. Equitrac recommends
a value of no less than 12 weeks, to balance disk space used with the need to preserve context for re-imports or
troubleshooting.
10 Click Next. The Transaction Import Wizard - Step 2 of 5 page of the wizard displays.
11 In the # of lines to preview field, enter the number of rows of imported information you want to preview.
12 For each field you want to map from your database import, click Add Field. An Add field dialog box opens.
• The Field name pre-populates with the values used in the SQL script statement provided in step 7. The fields
map in the correct order, and should not be modified.
• Select the Input field checkbox to specify that this field data comes from your import file. Deselect it if the
field is a virtual, non-input field created for import processing. In some cases, you will specify a virtual field
that does not appear in your import file. Provide a field name in the Field name field.
• In other cases, you may need to add a non-input field with static text that appears on all import records.
• Select the data type (integer or text) from the drop list.
• Click OK to close the Add field dialog box.
13 Continue to Add, Edit, Delete, or Clear All field entries in this window until you have the input format you
require.
CAUTION: The fields you import must be mapped in the same order as they appear in the original database.
Equitrac Professional associates the fields in this list in the same order they appear in the SELECT statement from
Step 7.
14 Click on the Refresh preview button to see the layout of the import data, according to your defined fields. You can
specify the # of lines to preview (default is 20 lines), and refresh to update the preview.
NOTE: You cannot preview the contents of the import source until after you configure the fields.
16 In the Preview area, you can preview the fields set up in the previous step.
17 In the Field processing commands area, click Add. An Add/Edit command dialog box opens:
a Select a field transform Command from the drop-down list. Each command requires specific input and has a
specific purpose. For example, the SPLIT command requires you to specify a split delimiter or position. This
enables you to separate a single field from the source file into two or more CAS fields. Alternatively, the
SUBSTITUTE command requires a search value and a replacement value.
NOTE: For information on the PERL SCRIPT transform, see Sample Perl Scripts for Perl Script Field
Transformations on page 494.
19 Click Next. The Transaction Import Wizard - Step 4 of 5 dialog box displays:
20 In the Field mapping area, select one of the available input fields from the list, and click the > button. A Select
destination fields dialog box displays.
21 From the Available database fields drop-down list, select the database field you want to map to the input field you
selected. The input-to-database field mapping appears in the Selected input fields (mapped to database fields)
list.
22 Click Refresh preview to see the layout of your fields.
23 Click Next. The Transaction Import Wizard Step 5 of 5 dialog box displays. This dialog box displays a preview of
the validation data as it will appear in the CAS database format.
24 Click Save to file if you want to save this import template to a file. Whether you elect to save the template to a file
or not, the import config is saved to the CAS server when you click the Finish button. Use the Save to File button
to save a distinct definition of the import config in an XML file. This XML file can be used in Load import from
File section in step 1 of this wizard.
25 Click Finish to close the wizard.
You now have an import template that you can use to manually run or schedule a validation data import from the time
and billing system.
The above example contains the a prDateDelivered flag. In some cases, the AccuRoute server stores process
records in the CostRecoveryData table (as opposed to scan destination records). These processes can be prevented
from being costed by checking the prDateDelivered time.
The above example also contains a prConceptuallyInbound flag. This is an AccuRoute flag that can be used to
differentiate inbound faxes from outbound faxes for costing purposes.
In cases where a SQL table field's name contains a period, the SQL engine can misinterpret the command. We
recommend using square brackets as indicated in the above example to clarify that the value is a field name, not a SQL
ownership designation.
A typical configuration screen for faxes, along with the appropriate script looks like this:
You may need to consult your AccuRoute system administrator for help in interpreting or adding to the fields in the
AccuRoute CostRecoveryData table.
5 In the Target field, navigate to the end of the string, then add a space, followed by the accounting server name. For
example, OKA2:
6 Click OK.
Maintaining Transactions
To help you manage the transaction data it collects, Equitrac Professional supports two ways of viewing transactions
that have not yet been exported to your time and billing system: the Equitrac Web Status page, and Transaction Editor.
You may also need to edit a transaction to correct billing or other transaction attributes. Transaction Editor allows you
to modify certain transaction values for transactions that have not yet been exported.
The top half of the status screen displays a summary of transactions (grouped by type), processed today and over the
last three days.
The bottom half of the status screen displays a summary list of the current CDR/Netbuffer, PageCounter/Pro, and
TouchPoint Console devices registered in System Manager. Click any of the column name links to sort the list by that
column.
Click the ellipsis (...) under the Transactions column for a given device to open the Device Transactions web dialog
box.
Here you can review a detailed summary of transactions processed by the device, including transaction type, total
number of transactions tracked on the device, number of transactions processed today, and the number of
transactions processed over the last three, seven, fourteen, or thirty days.
NOTE: The transaction list is a live snapshot and refreshes to include new transactions (as they are processed) when
you switch between the transaction type tabs.
The rest of the window is divided into two areas: The Filter section and the Edit Transactions section. The Filter
section enables you to limit the view of transactions according to filters you define. See Filtering Transactions on
page 121 for further details. The Edit Transactions section contains a grid displaying the current transactions for the
transaction type selected. See Editing Transactions on page 121 for further details.
Common Fields
The Edit Transactions section displays transaction data fields that can differ depending on which transaction type
you select. However, the table below lists fields common to all transaction types:
NOTE: The following table order matches the order in which the fields appear (from left to right) in the Edit
Transactions section. Transaction specific fields only display for some transaction types and appear at the far right
hand side of the table. Therefore they listed separately.
Field Description
DeviceName_ Name of the device that the transaction was sent to.
TransactionDate The date and time at which the transaction was performed.
CreationDate_ The date and time the transaction was created in the database.
LastModifiedDate_ The date and time the transaction was last edited using Transaction Editor.
Field Description
ApprovedbyUser_ The name of the user who released the transaction at the terminal.
Field1 User mapped validation field. By default this field is mapped to Matter ID code in System Manager.
Field2 User mapped validation field. By default this field is mapped to Client ID code in System Manager.
Field3 User mapped validation field. By default this field is mapped to User ID code in System Manager.
Fax-specific Fields
In addition to the fields common to all transaction types, the fax transaction type form contains the following
transaction fields:
Field Description
Scan-specific Fields
In addition to fields common to all transaction types, the scan transaction type form contains the following
transaction fields:
Field Description
Disbursement-specific Fields
In addition to fields common to all transaction types, the disbursement transaction type form contains the following
transaction fields:
Field Description
DisbursementType_ The type of disbursement: Courier, Regular Mail, shipment, or similar type. These are user-defined
values. See Define Disbursement Types on page 391 for details.
Filtering Transactions
Filters enable you to narrow the scope of the data that is presented by displaying only those records that meet specific
criteria. Consider that you might be searching a database with thousands of records, but you may only be interested in
seeing or working with a small subset of the table data such as print transactions, or transactions for a specific client.
By identifying patterns in the data you can reduce the amount of work required to locate a given piece of information.
This not only helps with accounting, but also reduces the load on the server because it doesn't need to return all the
records every time.
Filter transactions by specifying one or more criteria for one or more fields. The more criteria you specify for the filter,
the better chance of obtaining the range of transaction records that you are looking to work with. For example, you
may want to view all transactions on a particular date or made by specific users, or billed to a specific client.
Follow these steps to filter transactions:
1 In the field column list box, select a transaction attribute to filter by.
2 Choose an operator from the Select drop list. Choosing the Between operator replaces the Value field with From
and To fields.
3 Enter a parameter in the Value field, or a parameter range in the From and To fields.
4 Click the Add Filter button to add the filter to the list box.
5 Repeat the above steps to add more criteria to the filter if required.
6 Click the Filter button to apply the filter to the transactions table.
If the resulting number of transactions displayed is too large, add further filter criteria and click the Filter button
again to further narrow your search.
If the resulting list of transactions is too short, you can remove and re-add modified filters as needed. To remove a
filter, select it and click the Remove Filter button.
NOTE: Removing a filter does not clear the filters from the transaction list. Click the Clear Filter button to show all
transactions. Currently defined Filters remain in the Filter List so you can filter the list again if needed.
Editing Transactions
The overall process for editing transactions is the same across all transaction types. However, some fields are specific
to certain transaction types. For information on specific data fields, see Working with Transactions in Transaction
Editor on page 117.
NOTE: Any transactions you can access for editing in the Transaction Editor, such as exceptions or transactions
requiring approval, are also accessible through the Web Status Page.
NOTE: Certain transaction fields are read-only and cannot be modified. These fields are identified by an underscore
at the end of their name. For example, both DeviceName_ and UserName_ are read-only fields.
Exporting Transactions
The final step in processing transactions is exporting them to the Time and Billing system. Typically, you will schedule
exports to run on a regular basis. In some cases, you may need to re-export transactions. Simply re-running an export,
however, does not re-export transactions that were included in a previous export. Equitrac Professional provides a
wizard called ReExport for this procedure. See Re-exporting Transactions on page 141 for instructions.
NOTE: You can install and run the Export Wizard either on the CAS server or a remote workstation.
Equitrac Professional allows the export of transactional data in three file formats:
• Delimited: data in the flat file is separated by a specific character, usually a comma. This format is accepted by
most financial and accounting packages as it is a more common import export method allowing the import
application to recognize when a field ends and a new one begins regardless of field length.
• Fixed Length: data in the flat file is strung together without a separator. However, each field is of a fixed length
allowing the import application to recognize where each field begins and ends based on its length. This method
requires that some data be appended to meet the fixed length requirements on export. See Transforming Field
Data on page 130 for details.
• Integrated system: data is exported directly into a third-party database, rather than to a flat file. This option
enables you to configure the data mapping between Equitrac’s accounting server and the third-party database.
Transaction Exporting can only be performed using the export wizard and task scheduling features in System
Manager.
• From the Start Menu on the CAS server, click All Programs > Equitrac Professional > Export Wizard.
The export wizard launches and guides you through the following five stages:
Step 1: Introduction
1 At the welcome screen choose your creation method as follows:
a Select Create new export.
b Select Use existing export as template if you have already created an export file. If this is a first export, you can
select the default <Not Selected>.
c Choose the transaction types you wish to export from the View list box.
d Click the Fields button next to Summarized by, to select the fields by which you want the export data
summarized. Note that the text listed in the Fields Summary dialog box corresponds to the names of the
defined mapped fields for the system. For instance, if you have defined a single validation level called Project,
the checkbox label will read “Summary by Project”.
—Or—
a Select Edit existing export.
b Choose an existing export from the saved exports list.
2 Enter a unique Export name and an Export description.
3 Click Next.
Step 2: Configure
This section guides you through configuring the file export type.
1 Select your file export type:
• Delimited flat file: data within the file uses specific characters (delimiters) to separate its values. Most
database and spreadsheet programs are able to read or save data in a delimited format. Any character may be
used to separate the values, but the most common characters used are the comma, tab, vertical bar (also
referred to as pipe) and space. Delimited data is often divided into columns and rows. Column headers are
defined in the first line of data, and each subsequent line is a row of data. The lines are separated by newline
and/or carriage return characters. Due to their widespread use, certain spreadsheet programs can open
comma- and tab-delimited text files without the user designating which delimiter is in use.
• Fixed length flat file: data uses specific field lengths to separate its values. Some variable length database fields
must be appended in order to fit the data design. Column headers are defined in the first line of data, and each
subsequent line is a row of data.
• Integrated system: Exports the data to a specified database table.
a In the Export options section, specify the File name to be created when the export is run. You can specify a
location for the exported data by including the entire path to the file. If you choose not to specify a location for
the export, the generated export file is saved in the Export Wizard’s working directory: C:\Program
Files\Equitrac\Professional\tools.
You can name the exported file with, or include in the file name, the following variable date parameters. Note that
the parameters must be surrounded with a percent symbol (%) in the file name, for example CPCH%ddMMyy%.trn:
• dd — day of month with leading 0
• MM — month with leading 0
• yyyy — year
• yy — year without century
• HH or hh — 0-23 hour with leading 0
• mm — minute with leading 0
• ss — seconds with leading 0
b Select whether you wish to Append data to an existing file, or Overwrite an exisiting file with your custom
configuration. If you just created a new file name in the above step, select Overwrite an existing file.
3 If you are creating an integrated system export:
a Specify the DSN. Click ODBC admin to access the ODBC Data Source Administrator if necessary.
b Provide a username and password for an account with valid administrative access to the database.
c Specify the table name in the billing system database that you are exporting the data to.
d Click Test to ensure you can connect the export feature to the relevant table in the database using the account
credentials and DSN provided.
4 If you are creating a delimited flat file:
a Specify a Field delimiting character. The most common choices are a comma, a vertical bar (also known as a
pipe), or a space. If you need a special character to delimit your fields, select the relevant hex codes from the
Use hex code(s) drop list. The character you select will be added between data values when the export task is
run and the flat file is generated.
b Specify a Text identifying character. Many import applications require that text fields be wrapped between a
specific character to mark the beginning and end of the text string. Since commas and spaces are common in
text fields, this alleviates the problem where text strings may include the field delimiting character. The usual
values for wrapping text fields are the single or double quotes.
5 If you are creating a delimited or a fixed flat file, specify whether or not to include a linefeed at the end of each line
to indicate when new data rows begin.
NOTE: New rows in a delimited flat file are identified by carriage returns.
6 Specify whether or not to split the Total Count into two records.Use this option if the Time and Billing system
requires separate charging for black and white versus copy transaction. If you enable this option, specify the flag
field values for black and white or color that you expect to show as the ColorFlag field in your export.
Step 3: Mapping
This section guides you through mapping how fields will be formatted, transformed, and displayed in the final
exported output.
1 Select the fields you wish to include in the exported flat file from the Available fields list box. Select multiple fields
by holding down the Ctrl key.
This step of the export wizard provides a choice of “summarized totals” available for export. The fields available for
export depend on your initial choice of transaction type. For example, if you are exporting telephone transaction
data, then you can choose to export the total call duration, the total cost, and the total number of phone calls, etc.
For copy transactions, you can choose from the total number of pages, the total number of color pages, the total
cost, and other fields.
2 Add or remove the selected fields from the Fields to include in the export export mapping grid using the add (>)
or remove (<) buttons.
3 Edit the field mapping grid values as required. The following table outlines which values are editable and in which
file type they can be modified:
Header This value is displayed in the exported file if the Include column Yes Both
headers in the export option is selected.
Is text field? Selecting yes from the drop list identifies the field as a text string. Yes Delimited
When the transaction data is exported, these values are wrapped
with the Text identifying character you defined earlier during stage
2, the configuration stage. See Step 2: Configure on page 124.
Length This value identifies the fixed length of the field. Yes Fixed length
Align This option identifies if the field value is represented by the characters Yes Fixed length
at the right of the field or at the left. The rest of the field must be zero
filled for this option to function correctly.
Add new line? Selecting yes adds a linefeed after this field in the export. Yes Fixed length
4 After adding two or more fields to the field mapping grid, you can change the order in which they appear in the
export by moving them up or down in the grid. Select a field in the grid and use either the Up or Down buttons.
5 Click the Transform button to transform the value of a field to one that meets the import needs of your time and
billing application. See Transforming Field Data on page 130 for instructions.
6 Select Include column headers in the export if required.
The group header field will appear once at the top of each grouped set of transactions that match the value of the
group header field.
For example: If you choose clientname as the group header, all transactions will be grouped by client name, and the
clientname field will appear once, on a separate line, before each group as shown in below:
Client 1
transaction1details
transaction2details
transaction3details
Client 2
transaction1details
transaction2details
transaction3details
7 Click the Filter button to open the filter dialog box. Using a filter will narrow the transaction export output.
a Select one or more Available fields from the list, and click >.
b For each field selected, specify an operator, and the value. For example, you may want to filter on matter codes
less than 1000, so you would select an operator of < and a value of 1000.
c Enable the Include exceptions option if you wish to have transactions that are marked as exceptions included
in the export. By default, only valid transactions are exported.
d Enter your criteria for each selected field and click OK to return to the filter dialog box.
When you apply two logical operators within a rule, the AND operators are evaluated first. Equitrac Professional
permits two or more criteria settings in one rule, assigning AND a higher priority than OR, assuming a usual order
of application. For example:
A or B and C = A or (B and C)
A and B and C or D = ((A and B) and C) or D
A or B and C or D = (A or (B and C)) or D
CAUTION: Use caution when using the operand AND. Selecting the same criterion twice, such as two devices, and
changing the operand to OR allows the rule to apply transactions matching either criteria. However, leaving the
operand at AND could negate the entire re-costing criteria since a single transaction cannot be processed by more
than one device, or processed on multiple dates, or sent by more than one individual.
8 Click Next.
The following example shows a file header text block and the Header definition grid used to define it immediately
following it:
*** Equitrac Professional 5.7 ***
Copy Transactions
NOTE: Spaces required before and after a constant string must be included as part of the constant string. The above
table represents spaces by the use of [ ]. It is also recommended, but not required to use a final linefeed element to
separate the header from the rest of the file.
Function Parameter
Linefeed none
Linefeed none
Linefeed none
2 If you selected the option to include a header, create the header by selecting each header option you wish to use to
in building the header text and add it to the Header definition grid using the add (>>) button. Some header
functions have parameters or transformations that you can define when prompted, such as the Current date/time
option.
You can remove options from the Header definition grid by clicking it and using the remove (<<) button.
You can edit the parameter values after adding the option by double-clicking on the value and re-entering it.
Step 5: Summary
This section summarizes the custom configuration you are about to create and gives you the opportunity to preview
an actual export of the flat file would look like.
NOTE: Previewing the flat file does not actually export any transactions. Once the preview is opened in Notepad, you
can save it to a file location or you can email it as an attachment if desired.
1 Click the Preview Export button to launch Microsoft Notepad with an example of the flat file as it would appear if
this custom export configuration file were used now.
If this is a summary export, the preview displays the summary totals available for export. Please note that export
filters are not taken into consideration when generating a preview, so the content of the actual export may be
different from the content of the preview. The output file will have the transaction totals for every client and matter
combination that had a transaction recorded against it.
For example, the sample output file below shows the print transaction summary for a system with 2 clients (clients
1 and 2), each of which had matters 1 through 5 under it. The output fields appear in dictionary order by default.
Client,EndTransactionDate,Matter,StartTransactionDate,TotalBWPageCount,TotalColorPageCount,TotalCost,Tot
alPageCount,TransactionCount
1,2014-0-10 16:56:25.000,1,2014-10-10 16:31:37.000,63,0,37.80,63,7
1,2014-10-10 16:56:25.000,2,2014-10-10 16:31:37.000,63,0,39.80,63,14
1,2014-10-10 17:29:33.000,3,2014-10-10 16:31:37.000,63,0,32.80,63,5
1,2014-10-10 16:56:25.000,4,2014-10-10 16:31:37.000,72,0,43.20,72,8
1,2014-10-10 17:29:33.000,5,2014-10-10 16:31:37.000,90,0,54.00,90,10
2,2014-10-10 16:56:25.000,1,2014-10-10 16:31:37.000,36,0,21.60,36,4
2,2014-10-10 17:29:33.000,2,2014-10-10 16:31:37.000,117,0,70.20,117,13
2,2014-10-10 17:29:33.000,3,2014-10-10 16:31:37.000,126,0,75.60,126,14
2,2014-10-10 17:29:33.000,4,2014-10-10 16:31:37.000,63,0,30.80,63,7
2,2014-10-10 17:29:33.000,5,2014-10-10 16:31:37.000,135,0,81.00,135,15.
There is one line summarizing the totals for every client/matter combination. For example, the first line indicates
that there were a total of 7 print transactions for Client=1 and Matter=1, with the first of these transactions taking
place at 2014-10-10 16:31:37.000. The last transaction for this client matter was at 2014-10-10 16:56:25.000, and
the total cost of these transactions was 37.80 dollars.
2 If you are happy with the flat file contents and formatting, close Notepad and click the Finish button.
Your saved custom configuration now appears as an existing export configuration file the next time you launch the
Export Wizard.
1 From Step 3: Mapping page in the Export wizard, select a field to include in the export, and click the Field
transforms button. This opens the Transformation List dialog box for the selected field.
2 For each field, you can create multiple transformations to apply to export data. Click Add in the Transformation
List dialog box to open the Transform field dialog box; this provides you with a drop-down list where you select
the transformation you want to apply to the selected field.
The options you select here will then appear in the transformation list dialog box.
Transformation Description
LOWER Use LOWER to transform the format of a text string to lowercase characters.
UPPER Use UPPER to transform the format of a text string to uppercase characters.
RIGHT Use RIGHT to truncate the contents of a string value, starting from the right, to the number of
characters you specify in Number of characters.
LEFT Use LEFT to truncate the contents of a string value, starting from the left, to the number of
characters you specify in Number of characters.
SUBSTRING Use SUBSTRING to select a specific section from within the contents of a string value. To transform
a string into a substring, enter a number corresponding to the Start position within the string,
and enter the Number of characters, including the start position character, you want to capture
from the string.
Transformation Description
DATEFORMAT Use DATEFORMAT to change the format from the one in the database to the one you want to
appear in your flat file.
The following list outlines your date format options:
• yyyymmdd—The four digit year followed by the two digit month and two digit day
• mm/dd/yyyy—The two digit month, the two digit day, and the four digit year separated by
forward slashes
• mmddyyy—The two digit month followed by the two digit day and the four digit year.
• mmddyy—The two digit month followed by the two digit day followed by the last two digits of
the four digit year
• yymmdd—The last two digits of the four digit year, followed by the two digit month, followed
by the two digit day, excluding the time.
• #dd-MON-yy—The two digit date followed by the first three alpha characters of the month and
a two digit year.
• hh—The hour portion of the date/time stamp only.
• mm—The minute portion of the date/time stamp only.
• ss—The seconds portion of the date/time stamp only.
• CUSTOM—The export utility can now export dates in customizable output formats. You must
specify one or more date variables and optional text. All variables are defined by the percent
symbol and a letter. Text that does not follow the variable naming convention will be included
verbatim in the output string. All variables are formatted using the Microsoft Windows strftime()
function. See Format Variables for Custom Date Format Field on page 493 for more
information on supported variables.
Listed below are sample conversions showing the format string used, as well as the output for
“Wed, January 17 2007, 21:25”:
• Date<%b-%d> — Date<Jan-17>
• %Y%%%m%%%d — 2007%01%17
• %I:%M %p — 09:25 PM
• (%B %d ‘%y) — (January 17 ’07)
• %%today — %today
•
GROUPHEADER Use GROUPHEADER to transform a field into a group header. The GROUPHEADER transformation
option is only available to the first field in the Fields to include in the export grid.
If you chose a date/time field as the group header, you can select the Apply date format option
and a date format from the drop list to transform the field value to the date format you require. See
DATEFORMAT on page 133 for a listing of possible formats.
STRING Use STRING to completely replace the contents of a field with your own String text value.
Transformation Description
PAD WITH 0 Use PAD WITH 0 to pad the beginning of a field with zeros (0) to the Pad length you specify.
The pad length value controls the total length of the field that results after padding the field with
zeros.
The following list shows two examples of how pad with 0 transforms field values:
Field 1
• Field length = 10
• Pad length = 3
• Field Value = 123
123
Field 2
• Field length = 10
• Pad length=10
• Field Value=123
0000000123
CONCATENATE Use CONCATENATE to return a sequence that contains all the individual elements (fields and
strings) entered in the linear order in which they are added. The produced result of the
CONCATENATE transformation results in a string value.
• Note The first field in a the resulting string of a concatenate transformation is the field being
transformed, therefore do not add the field in the grid unless you require the field to
be duplicated in the transformation.
To create a single field, do the following:
• Select CONCATENATE as the transform option.
• Click Add to add a new row to the grid.
• Click <Option> in the Option column and select either a String or a Field from the drop list.
• Enter the Value using one of the following methods:
• For a String: Double click in the value field and enter the string value.
• For a Field: Click <Field> in the Value column and select a field from the drop list.
• Repeat the above steps to add further values as required.
• Click OK to close the Transform field dialog box.
CASES Use CASES to transform any standard date format into a custom date format not covered by the
DATEFORMAT transformation.
CUSTOM This transformation is intended for Equitrac support and field service engineers to deploy custom
transformations designed as custom releases for specific customer sites. General system
administrative users will not use this option.
Transformation Description
EXPORTTIME Use this option to timestamp the transactions with the current export with the time of export.
Some time and billing systems require time stamping be associated with transaction in the
exported file, rather than in the header of the export file itself.
You can specify a time offset in minutes to enable the export time to read a different time than the
actual scheduled export. For example, scheduling options may only accept “first day of the month”,
not “last day of the month”, but your time and billing system may require end-of-month reporting.
Therefore, you can schedule your export for after midnight on the first day of a new month, and
offset the EXPORTTIME option for each field to show 11:30pm on the previous day.
CRLF This option overwrites the actual export field and replaces it with a carriage return line feed.
SUBSTITUTE Use this option to specify values to overwrite in the string of the selected field, for example: From =
jan, To = Jan.
PERL SCRIPT The built-in transforms above represent the most common operations you will need for exported
fields. Given the variety of Time and Billing configurations and specific corporate needs, it is not
possible to predict every possible transformation a firm might need. To meet diverse field
manipulation needs, Equitrac Professional supports arbitrary field transformations using the Perl
scripting language. Perl is extremely versatile and provides exceptionally strong text manipulation
commands.
When you define an export format and select PERL SCRIPT as a field transform, you have the ability
to manipulate each field by using a customized Perl subroutine that you create. The export utility
invokes the Perl module with 2 parameters: the unfiltered exported field, and the text delimiter
used by the export configuration. Your subroutine is expected to output a single string that
represents the filtered field and the delimiter. The export utility is designed so that it does not add
a field delimiter after a field that has been transformed by a PERL SCRIPT. This enables you to
transform multiple fields in a row and effectively concatenate them if you do not include the
delimiter in your field output.
When you first select the PERL SCRIPT transform option, you are presented with a default script
that parses the input parameters, and re-assembles them for output. This script effectively does
nothing, but represents a default template that can be used to construct a filter. At any point
during the testing and editing of the Perl transform, you can use the “Default” button to discard all
changes you’ve made and reset the script to the baseline, null transform.
At any point during your development of a Perl transform, you can use the “Test” section at the
bottom of the dialog box to test it. You must provide a sample input field in the Parameter edit
box. The Delimiter edit box is read-only because the delimiter is fixed for the current configuration.
Specific use of Perl for text manipulation is beyond the scope of this manual. Consult the appendix
for a few sample transforms or use any of the many Perl resources available on the Internet for
further information.
PERL Record Transform
In some cases, it may be difficult to use a Field Transform for your specific needs. This usually
occurs when the resulting transformation of a specific field depends on the contents of other fields
in the record. In those cases, you can use a Record Transform. This special transform operates
similarly to the Field transform, with the obvious difference that it receives the whole record as an
input parameter. The “Default” transform in this case parses all the fields, and re-assembles them
into an identical output record.
It is possible to run the import and export wizards remotely, if you define CAS in the Equitrac Common registry on
the remote workstation, or you create a shortcut to the Wizard and include the server name as a command line
parameter (wizards can also simply be launched from the command line with the same parameter). All export/import
wizards, including the re-export wizard, have the optional command line parameter CASName, which you can specify
when running the command.
To launch any wizard from the Start menu using this parameter, do the following:
1 Click Start > Programs > Equitrac Professional.
2 Right-click the wizard you want to use and select Properties from the menu.
3 In the Target field, add a space and specify the accounting server name; for example:
“C:\Program Files\Equitrac\Professional\Tools\EQReExportUI.exe” OKA2
4 Click OK.
5 Click Start > Programs > Equitrac Professional and click the wizard you’ve just edited. Equitrac Professional
launches the wizard on the specified server.
If you are unable to modify the target field from the properties of the wizard as stated above, you can create a shortcut
that populates the command line parameter when clicked:
1 Right-click anywhere on the Windows Desktop. From the menu, select New > Shortcut.
2 In the Shortcut field, type the UNC path for the Import Wizard, or browse to C:\Program
Files\Equitrac\Professional\Tools\EQExportWizard.exe. Click Next.
3 Provide a Name for the shortcut, and click Finish. The shortcut displays on the desktop.
4 Right-click the shortcut you just created, and select Properties from the menu.
5 In the Target field, navigate to the end of the string, then add a space, followed by the accounting server name. For
example, OKA2:
6 Click OK.
Suspending a Task
When you suspend a task, the task remains in the task scheduler, but does not run.
To suspend a task, do the following:
1 Click the System > Scheduled Tasks link.
2 In the right pane, click the desired task to open the Modify task dialog box.
3 Select Yes from the Suspended drop list.
4 Click OK. The task is suspended and does not run at its scheduled time.
Resuming a Task
When you resume a task by removing its suspended status, the task runs at its regularly scheduled intervals.
NOTE: If the task’s end date has passed, you must modify the end date for the task to resume.
Removing a Task
To remove a task, do the following:
1 Click the System > Scheduled Tasks link.
2 In the right pane, right-click the task you want to remove and select Remove scheduled task from the menu.
3 Click Yes to confirm the deletion. The task is removed.
Re-exporting Transactions
You cannot simply re-run an export to re-export transactions since exported transaction records are flagged in the
database once they are exported. Therefore, Equitrac Professional provides you with a separate method for
accomplishing this procedure.
To re-export an export, do the following:
1 From the programs list in the Start Menu on the CAS server, click Equitrac Professional > ReExport to open the
Export history dialog box.
2 Select an export from the history list and click the Re-export button.
Your transactions will be exported to the same location as the first time the transactions were exported.
3 Click OK.
NOTE: Using the Re-export wizard remotely is ineffective for file exports because the wizard writes export files on the
remote machine. It does work well for integrated exports, however.
Topics:
Price List Workflow
Identifying Pricing Requirements
Creating Large-format Price Lists
Creating Fax Price Lists
Creating Scan Price Lists
Creating Disbursement Price Lists
Creating Phone Surcharges Price Lists
Assigning Price Lists
Price List Selection Rules
Transaction Re-costing
Maintaining Price Lists and Price List Selection
Rules
Example: Calculating Costs for an Advanced
Print Transaction
A price list is a collection of pricing rules you can apply to devices. These rules define how Equitrac Professional
assigns costs to clients for transactions based on attributes such as page count, page attributes, and finishing options. A
price list can also accommodate time-of-day charging. Once you have created price lists and assigned them to your
devices, you can customize how they are applied by creating price list selection rules. Price list selection rules override
the price list assigned to the device based on transaction attributes such as date, user code, client, matter, or validation
code.
This chapter provides information about:
• planning a pricing strategy
• creating price lists
• creating price list selection rules
• transaction re-costing
Basic Print/Copy Price per page for black & white or Basic printers that do not offer Print, Copy
color output extended capabilities.
Advanced Print/ Assign costs for extended job and Printers with finishing options and Print, Copy
Copy page attributes. page detail capabilities.
Large-Format Assign costs for extended job and Plotter printers. Print
page attributes for large-format jobs.
Fax Assign costs for fax jobs by page or by Printers with fax capabilities. Fax
minute, and optionally, by prefix.
Scan Assign costs for scan jobs per type Printers with scan capabilities. Scan
and page attributes.
Phone surcharges Assign surcharges for local, long Not applied to a device, use Phone
distance, and international phone pricing rules to assign surcharges
calls. to certain calls.
Page Sets
Equitrac Professional evaluates each transaction for all of its attributes and groups each page into a page sets according
to common attributes. Equitrac Professional applies only one page detail pricing rule to each page set in a transaction.
Page sets apply to both copy and print transactions.
A document that contains both color and black and white pages, generates two page sets, one grouping all color pages
together, and the other grouping all black and white pages. More page set groupings are created when more attribute
combinations exist.
NOTE: Equitrac Professional treats each side of a duplexed page as a separate impression. Depending on the
transaction attributes, the impressions might be grouped in separate page sets. For example, a document with only
one color page generates two page sets: one color set and one black and white set.
2 Left to right: If two rules have the same number of exact matches, column order determines the applied rule. An
exact match in the Type attribute supersedes an exact match in the Size attribute. An exact match in the Size
attribute supersedes an exact match in the Color attribute, and so forth.
3 Top to bottom: If two or more identical rules appear in the grid, the order in which they appear determines the
applied rule, regardless of its pricing.
NOTE: Transaction costs are calculated using the values in the Pricing column. As such, Pricing values are not
considered transaction attributes and therefore have no affect on rule hierarchy.
4 Default price: If the accounting server cannot find a match in the grid, it applies the default price if one is
configured.
Applying the grid hierarchy to the above table, the following rules are applied to the three page sets:
• Page set A: Although rules 2, 3 and 4 could apply, rule 3 has the most exact attribute matches.
• Page set B: Rules 1 and 6 are identical and both apply. However, since rule 1 appears in the grid first, it is applied
over rule 6.
• Page set C: Rules 2 and 4 have more exact matches than rule 5. However, both rule 2 and 4 have the same number
of exact attribute matches (two). Therefore, column order determines which rule is applied. Since rule 2 has exact
matches in columns one and three, it is applied over rule 4 with exact matches in columns two and three.
When defining advanced price lists, define a comprehensive set of page detail pricing rules that assign fixed prices for
several combinations of page attributes. The various page detail pricing rules should cover a range of anticipated page
attribute combinations. See Example: Calculating Costs for an Advanced Print Transaction on page 170 for example
scenarios, the rules required to support them, and how Equitrac Professional calculates the costs.
NOTE: Be aware that inconsistencies between printer drivers may require you to establish multiple price lists to
accommodate these differences.
Device Capabilities
When planning your price lists, make sure you evaluate the capabilities of each printer within the deployment. The
Equitrac Port Monitor examines incoming print job data only, as opposed to print output. If you create a price list for
a black and white printer, but mistakenly assign color pricing to that printer, a user who sends color output to the
printer will be charged for color output, even though the device cannot print in color.
As an example, you can configure primary pricing to charge the user for a print transaction, but use the secondary
price list to track the cost your company pays to the printer leasing company for the job (many lease contracts stipulate
a base cost per page). You could create secondary price lists for each device that reflect the actual costs to operate, then
assign both primary and secondary price list to each device as needed.
You can assign a secondary price list at the physical device, port, and queue level.
3 Configuring finishing costs for large-format price lists is similar to advanced price lists. See Creating an
Advanced Print/Copy Price List on page 150 for details.
4 The Default page price option includes size and roll width options. When configuring Default page price costing:
• Select a size from the drop list.
• When you select a linear size, enter a Roll width value in the field.
Page detail pricing for large format price list configuration is otherwise identical to the advanced price list
configuration. See Creating an Advanced Print/Copy Price List on page 150 for details.
NOTE: Fax transaction transmission duration values are saved in seconds, not minutes. Therefore a price list
configured with a per minute charge of 40 cents would result in a 20 cent charge for a 30 second transmission.
Prefixes
The prefix of a number consists of any combination of digits required to dial and send a fax. The prefix can include
area codes, country codes, or a single digit for local long distance dialing. Depending on the combination of numbers,
you can create rules to charge for long distance or international calling. You can also include parts of the actual
number itself to charge specific costs for numbers that start with certain digits.
Equitrac Professional applies rules according to the order they appear in the list from top to bottom, therefore, place
simpler prefixes near the end of the list if you have prefixes that start with the same digits.
For example, calling Europe from Canada or the US requires a country exit code (011) plus the European country
code. If you want to apply specific charges if the fax is going to either France or Germany, plus a generic charge for any
faxes going to any other European country, you would order the prefix rules as follows:
• 01133
• 01149
• 011
• 1
It does not matter which country code is first; but rather that the generic exit code (011) is placed after the two more
specific codes. If the generic exit code were first, then any faxes sent internationally would be charged the same cost.
The following table shows a simple configuration to account for local, long distance, and international dialing from
within North America:
Default 0.10 0.00 The default is applied to all faxes sent locally.
NOTE: Some countries use a direct-dial systems and therefore vary in how they are accessed internationally by
phone. For example, If you are making an international call to Denmark, the Czech Republic, Italy, Norway, Portugal,
or Spain, simply dial the international access code, country code, and phone number.
However, to call Belgium, France, or Switzerland, drop the initial zero. For example, to call a Paris hotel from London,
dial 00, 33 (France's country code), then 1 and the rest of the phone number without the initial zero.
b In the New phone prefix pricing dialog box, enter a Prefix (name) for this price list. See Prefixes on page 153
for details.
c Choose the Pricing method: Fixed page rate or Variable page rate. Fixed rate applies the same rate to all pages
in the fax. Variable page rate allows you to define page ranges that you want to assign the rate to. For example,
you can charge $1.00 for the first page, and $0.50 for each additional page.
d Adjust the page 1 cost if needed. You can adjust the Price per page price and/or the per minute charge.
NOTE: If a page pricing rule has both a price per page and price per minute cost, then the sum of both amounts is
charged for each transaction that meets the rule.
e Click <Add...> to add additional page pricing rules for page ranges or for single pages. A new line item appears
in the Pricing tiers list. In the example above, page 1 will cost $1.00, pages 2 through 10 will cost $.50, and
pages 11 and beyond will cost $.25.
f Repeat the above steps to add additional prefix rules.
g Click OK to close the dialog box.
7 Click OK to close the New fax price list dialog box.
NOTE: If you require separate price lists for incoming and outgoing fax transmissions, create separate fax price lists
for each. Since you are not charged for the call with incoming fax transmissions, you only need to use the Default
rule for incoming fax price lists to define a per page or per minute cost for all incoming transmissions.
NOTE: Equitrac Professional does not automatically assign a default price list to scan transactions at the device level.
When you create a scanning price list, you must manually flag it as the default price list for Equitrac Professional to
apply it to scan transactions.
NOTE: To create Disbursement Price Lists, you must have at least one disbursement type defined.
See Define Disbursement Price List Selection Rules on page 400 for instructions on creating disbursements, and
disbursement price lists.
NOTE: Enter a negative number into the Per call and Per minute surcharges fields to reduce the cost of a call.
Incoming Transaction
Job Request Type Print Queue Yes
Price List?
o
No
Databa
N
CAS
Port Yes
TPC/
Price List? Embedded?
No
No
Default Yes
Price List?
No
Apply $0.00
pricing
The primary and secondary drop lists for each transaction type only display price lists for the specific transaction
type. If you have not created a price list for a transaction type the list appears empty.
NOTE: There are two fax transmission types: Fax receive for incoming transmissions and Fax send for outgoing
transmissions. Assign the same price list to both if you do not intend to treat incoming and outgoing fax
transmissions differently. Otherwise, select separate price lists for each. See Creating Fax Price Lists on page 153
for instructions on creating fax price lists.
There is no option to select a primary or secondary price list for the disbursement mode as disbursement price lists
are associated with a single specific disbursement type. See Define Disbursement Price List Selection Rules on
page 400 for details.
4 If desired, select a defined secondary price list from the drop list.
Equitrac Professional uses the primary price list to calculate the actual transaction cost. Secondary price lists
enable the software to calculate another cost that is stored with the transaction for reporting purposes. Secondary
price lists do not factor into any balance calculations.
For example, you can use primary pricing to charge the user for a print transaction, and use the secondary price
list to track what you pay to the printer leasing company for the transaction, since many lease contracts stipulate a
base cost per page.
5 Click OK.
Print / Copy In the right pane, highlight the desired Print/Copy price lists row by clicking any of the price list’s
values other than its name.
• Select Current tasks > Set as default price list for print jobs to make this price list the default for
all print transactions.
– Or –
• Select Current tasks > Set as default price list for copy transactions to make this price list the
default for all copy transactions.
Fax In the right pane, highlight the desired Fax price lists row by clicking any of the price list’s values
other than its name.
• Select Current tasks > Set as default price list for sent faxes to make this price list the default for
all sent fax transmissions.
– Or –
• Select Current tasks > Set as default price list for received faxes to make this price list the
default for all received fax transmissions.
Note: A single Fax price list can be set as the default for both sent and received faxes.
Scan In the right pane, highlight the desired Scan price list row by clicking any of the price list’s values
other than its name.
Select Current tasks > Set as default price list for Scans to make this price list the default for all
scanner transactions.
Disbursement Each disbursement type must have its own default price list. Therefore, for each disbursement type:
In the right pane, highlight the desired Disbursement price list row by clicking any of the price list’s
values other than its name.
Select Current tasks > Set as default price list for <Disbursement type> to make this price list the
default for the current disbursement type where <Disbursement type> is a previously created
disbursement type.
Disbursement transactions processed under a disbursement type without a default price list cannot
be assigned a cost.
NOTE: If a transaction does not meet any price selection rules, then pricing is applied based on the normal pricing
hierarchy. See Assigning Price Lists on page 158 for details.
Your company is performing pro-bono work for a client, and Configure a price list selection rule for each transaction type
wishes to override all billing regardless of the transaction. for this client.
You have a department that does not do client work, so Accomplish this by either configuring multiple price list
transactions are not billable to clients, but you still wish to selection rules for transaction types, or by creating a price list
track transactions for total cost of ownership. selection rule for each user code or user class name.
You wish to provide a discount on all printing transactions Create one price list selection rule for this client based on the
for a particular client. print transaction type.
You wish to create a price list and apply it to all print Create one price list selection rule for the print transaction
transactions regardless of printer or printer location for a type.
specific time period.
You wish to set surcharges for specific clients or matters Create a price list selection rule
3 Enter a unique Name and a Description for the price list selection rule.
4 Select a Transaction Type from the Type drop down list.
NOTE: Sent faxes, received faxes, and all disbursement types defined within System Manager are displayed as
options when selecting a transaction type for price list selection criteria.
5 Select a Primary price list to apply if the price list selection rule criteria is met.
6 Use the Price List Selection Criteria section to define the criteria for the rule:
a Click Add to open the Criteria Settings dialog box and add the first criteria set.
b Select an Attribute from the drop list. The attribute drop list displays all relevant criteria that can apply to the
selected transaction type.
c Select an Operator from the drop list.
NOTE: Attributes are unique to transaction types. Operators are unique to the Attributes. The list of operators
displayed is dependent on the Attribute selected.
d Click OK to accept your new criteria and close the Criteria Settings dialog box.
e Repeat these steps as necessary to add further criteria.
7 Click OK to accept your new price list selection rule and close the Price List Selection Rules dialog box.
NOTE: When selecting transaction date range dates, be advised that the from and until dates include an unseen
timestamp of 00:00:00AM, therefore the date range 10/01/2014 to 15/01/2014 does not include transactions
processed on January 15th. If you wish to include transactions processed on the 15th, select an end date of 16/01/
2014.
Transaction Re-costing
Equitrac Professional enables you to re-cost transactions that it has not yet sent to your time and billing system, based
on specified conditions such as date range or client/matter.
Use transaction re-costing to manually override current transaction costs in the database and apply new costing to
them. For example, you may want to discount transactions for a particular time period or for a specific client. You may
want to re-cost a group of transactions if the wrong price list was originally applied to them.
NOTE: Transaction re-costing applies to both regular transactions and exceptions that fall within the specified
conditions.
If you change a price list or price list rule before running a re-cost, once you have dealt with any outstanding
exceptions or approvals, Equitrac Professional re-processes them on the basis of new validation information, and
costs them accordingly.
The only situation in which this may be a problem is if you override the default pricing on a re-cost. This may mean
that an exception's cost may change again once corrected, but this is not the standard case.
NOTE: Sent faxes, received faxes, and all disbursement types defined within System Manager are displayed as
options when selecting a transaction type for price list selection criteria.
NOTE: If you choose this pricing method, you must select a transaction type to re-cost transactions. If you leave the
transaction type at the default <ANY> (meaning all transaction types), then the override existing method with drop
list appears empty as it cannot select a price list.
6 Use the Re-cost criteria section to define the conditions under which transactions will be re-costed:
a Click Add to open the Criteria settings dialog box.
b Select an Attribute and an Operator.
Choosing an attribute and operator combination activates and defines the contents of the Criteria Settings
section. Until you choose an attribute and operator combination, the section remains empty.
NOTE: Clicking the Count button in the Count selected transactions section at any time during the criteria
selection process, displays the number of transactions that meet your current criteria selection.
The following table lists the possible Transaction type + Attribute + Operator combinations and outlines how to
enter the Criteria Settings for each:
Any Transaction date BETWEEN Select a date range. See the Note immediately
following this table regarding date ranges.
Copy Device STARTS WITH Enter the name (or partial name) of a Device
Print CONTAINS
Fax EQUAL
Scan Disbursement
Any Matter STARTS WITH Enter a matter code, or partial matter code
CONTAINS
EQUAL
Any Matter Description STARTS WITH Enter a matter description, or partial matter
CONTAINS description
EQUAL
Any Client STARTS WITH Enter a client code, or partial client code
CONTAINS
EQUAL
Any UserCode STARTS WITH Enter a user code, or partial user code
CONTAINS
EQUAL
Print Application name STARTS WITH Enter the name of an application that the print/
CONTAINS copy job was being sent from.
EQUAL
Print Client workstation STARTS WITH Enter the name, or partial name of a client
CONTAINS workstation
EQUAL
Print Submit username STARTS WITH Enter the name, or partial name of the user who
CONTAINS submitted the print job
EQUAL
Print Release username STARTS WITH Enter the name, or partial name of the user who
CONTAINS released the print job
EQUAL
Print Application Class STARTS WITH Enter the application class name of the
name CONTAINS application printing the job
EQUALS
Phone Authentication STARTS WITH Enter the authentication number of the phone
code CONTAINS
EQUALS
Phone Call Site STARTS WITH Enter the call site associated with the phone
CONTAINS
EQUALS
Print Device Class name STARTS WITH Enter the device class name of the device
CONTAINS printing the job
EQUALS
Copy Number of Copies LESS THAN OR EQUAL Enter the number of copies produced by the job
Print LESS THAN
Fax GREATER THAN OR
Scan EQUAL
GREATER THAN
NOT EQUAL
EQUAL
Copy Page count LESS THAN OR EQUAL Enter the page count of the job
Print LESS THAN
Fax GREATER THAN OR
Scan EQUAL
GREATER THAN
NOT EQUAL
EQUAL
NOTE: When selecting transaction date ranges, the from and until dates include an unseen timestamp of
00:00:00AM. For example, the date range 10/01/2015 to 15/01/2015 does not include transactions processed on
January 15th. If you wish to include transactions processed on the 15th, select an end date of 16/01/2015.
c Enter your criteria settings and click OK to return to the Re-cost transaction dialog box.
d Repeat the steps above to define further transaction criteria.
Each row in the grid holds one criterion. If you enter more than one criterion, you can change the boolean operand to
either AND or OR making each criteria selection inclusive or exclusive of each other.
When you apply two logical operators within a rule, the AND operators are evaluated first. Equitrac Professional
permits two or more criteria settings in one rule, assigning AND first, then OR, assuming a usual order of application.
For example:
A or B and C = A or (B and C)
A and B and C or D = ((A and B) and C) or D
A or B and C or D = (A or (B and C)) or D
For example, if you select both a transaction date range and a device as criterion for a re-cost:
• Selecting the OR operand expands the transaction selection to include transactions processed during the date
range as well as all transactions processed by the device, regardless of date.
• Selecting the AND operand narrows the transaction selection to transactions processed during the date range on a
specific device.
CAUTION: Use caution when using the operand AND. Selecting the same criterion twice, such as two devices, and
changing the operand to OR allows the rule to apply transactions matching either criteria. However, leaving the
operand at AND could negate the entire re-costing criteria since a single transaction cannot be processed by more
than one device, or processed on multiple dates, or sent by more than one individual.
7 Select the Include exported transactions checkbox if you want to include already exported transactions in the re-
costing criteria you create. For example, this is useful if you want to retroactively offer a customer a discount on
transactions already posted.
8 Once all your required criteria are created, click OK.
Once you have created the transaction re-costing and clicked OK, System Manager sends the request to CAS for
processing. System Manager shows the status of the re-cost in the right pane. Once complete, the Status changes to
Done. After processing, the transaction re-cost request remains in the right pane as a log entry for historical purposes.
Scenario 1
Assign a base price of 5 cents, 5 cents for stapling, and 1.00 for binding. Otherwise, only charge a per page cost under
the following conditions:
Condition Charge
To see how Equitrac Professional compiles this advanced price list, we apply it to a print transaction consisting of a
stapled six page document that has a separator or banner page for the first page.
The port monitor examines the document and page attributes and passes the necessary information to the accounting
server. The accounting server examines the information and determines that the pages in the print transaction match
the charging rules as outlined below.
The accounting server groups the pages together into page sets according to page attributes. Equitrac Professional
calculates costs for this print transaction’s page sets as shown below.
Scenario 2
Assign a base price of 5 cents for stapling, and 1 dollar for binding. On top of these prices, add a premium under the
following conditions:
Condition Charge
A3 paper $0.05
This scenario is a bit more complex and requires a more detailed structure. Your advanced price list rule structure
appears in the table below.
Stapling 0.05 —
Binding 1.00 —
Size A3 0.25 1
Color 0.40 9
Duplex 0.30 13
Heavy 0.50 15
NOTE: Since you want to add the premiums to the base price, the assigned charge equals the sum of your base price
+ the cost of the associated premium.
To support the pricing structure, the page detail pricing grid requires you to configure the following fifteen rules:
To see how Equitrac Professional compiles this advanced price list, we apply it to a print transaction consisting of a
bound and duplexed six page document that has a separator or banner page for the first page.
The port monitor examines the document and page attributes and passes the necessary information to the accounting
server. The accounting server examines the information and determines that the pages in the print transaction match
the charging rules as outlined below.
Rule match? Yes. Rule#13 Yes. Rule#13 Yes. Rule#13 Yes. Rule#10 Yes, Rule # 3 Yes, Rule # 5
The accounting server groups the pages together into page sets according to page attributes. Equitrac Professional
calculates costs for this print transaction’s page sets as shown below.
Meets page
Page set # Pages in set Assigned cost Calculation Total cost
charging rule
Topics:
Physical Devices Overview
Device Classes
Physical Devices
E-queues
Passthrough Printers
Working with Workstation Devices
Managing Devices Across Multiple Locations
Equitrac Professional tracks all activity produced by devices registered in the Equitrac Professional database. When
users access a registered device to print, copy, fax, or scan, Equitrac Professional tracks and stores the resulting
transaction data on the accounting server for both cost recovery and total cost of ownership purposes. The cost
recovery method uses tracked printing costs to bill-back clients, while the total cost of ownership method tracks costs
associated with printing to measure, monitor, and manage all output and print activity.
For information on device status and evaluating device health over time, see Device Monitoring with DME on page
225. For information on configuring Embedded Devices, see Embedded and Controller Interfaces on page 215. For
information on configuring TouchPoint Consoles, see Configuring TouchPoint Consoles on page 301.
This chapter provides information about:
• the various device types and capabilities that Equitrac Professional supports
• configuring each device in System Manager
• configuring device capabilities and options
CAUTION: You cannot remotely configure printers without first installing the Equitrac Port Monitor software to
both the Print Server, and any workstation intended to remotely configure printers. The Equitrac Port Monitor must
be present on the workstation to enable it to display the Print Spooler User Interface dialog boxes, which are used to
configure the printer in question.
Device Types
Equitrac can track and control printing to multiple device types. When a user accesses a registered device, Equitrac
Professional tracks and stores the transaction data to the CAS.
Device Description
Physical Devices • The actual piece of hardware that prints or copies. Physical devices include any device capable
of printing, faxing, scanning, or copying. Equitrac Professional adds physical devices to the
database automatically when you use Windows to add a print queue.
• See Physical Devices on page 187.
Control Terminals • Peripheral hardware you can attach to a printer or multi-function device to track transactions
and control user access to the device’s features and secure print queues.
• For information about control terminals, see Control Terminal Operation Modes on page
273.
TouchPoint Consoles • Peripheral touch-screen hardware you can use to control access to an output device, to track
transactions and control user access to the device’s features.
• For information about TouchPoint Consoles see Configuring TouchPoint Consoles on page
301.
Device Description
e-queues • A proprietary print queue definition that is not associated with a specific physical device. When
users print, the e-queue holds the documents for release. When users release held documents
from a control mechanism, Equitrac Professional pulls the documents to a physical device for
printing.
• See E-queues on page 197.
Controller Interface • Third-party, manufacturer-specific software bridges that enable limited validation
authentication to occur on the device itself, such as with Xerox JBA.
• For configuration instructions, see Embedded and Controller Interfaces on page 215.
Embedded application • A software application operating on the multi-function device that acts as a controlling
mechanism between the device’s features and the control system resident on the server.
• For configuration instructions, see Embedded and Controller Interfaces on page 215.
Passthrough Printers • A printer port connection using the Equitrac Port Monitor that enables Equitrac Professional to
communicate with an unsupported print device. Associate a Passthrough printer with a target
printer. When a user prints a document, the Passthrough printer tracks and releases the
document to the target printer.
• See Passthrough Printers on page 199.
Workstation Devices • Peripheral printers attached locally to a client workstation. The Desktop Printing feature on each
workstation tracks print transactions through the local printer. Equitrac Professional adds
workstation devices to the database automatically when users print from a workstation to a
local printer.
• See Desktop Print Tracking on page 441.
You can access the status page from the CAS server using one of the following methods:
• Click the Equitrac Web Status shortcut installed to the desktop during installation.
—Or—
• From the programs list in the Start Menu, click Equitrac Professional > Equitrac Web Status.
—Or—
• In the address field of an Internet browser, enter the following URL:
http:\\<server_name>\EQStatus
NOTE: You can also view the Web Administration page for each individual device if you click on the IP Address link for
the device.
Standard View
The Standard view displays all devices as individual entries, according to the name of the device. Each device link
opens a device configuration dialog box. The Standard view also includes two separate groups of all control terminals
and TouchPoint Consoles not yet assigned to a physical device. Each control terminal or TouchPoint Console link
opens a device summary dialog box.
Server View
The Server view displays the local print server group containing all devices for that server, as well as groups for any
other print server with devices. Each device link opens a device configuration dialog box.
The Server view also includes a group of all control terminals and TouchPoint Consoles not yet assigned to a physical
device. Each link opens a control terminal configuration or TouchPoint Console Summary dialog box.
Type View
The Type view displays all device types by group except workstation devices. Each link opens a configuration dialog
box.
In the Custom group view, you can create, edit, populate, and delete custom groups. Creating custom groups of
devices—such as groups by physical location, by manufacturer, and so on—makes viewing all devices on your network
easier.
The Custom group view also includes a group of all control terminals and TouchPoint Consoles not yet assigned to a
physical device. Each link opens a configuration dialog box.
NOTE: You cannot drag and drop certain current or recently upgraded firmware control terminals into a custom
group.
NOTE: Deleted devices cannot be re-added to the database as the same device. The database assigns a unique
identifier to each device, and a record of the device is kept in the database even after the device is deleted from
System Manager. If you delete a device and need to re-add it, you must choose a unique device name.
If the device was tracked using DME, it will no longer appear in the DME console.
CAUTION: The ability to select and deregister licenses in System Manager applies to all license types, but be aware of
the consequences of deregistering core server components or actively-used peripheral components or devices,
before deregistering any licensed component.
Device Classes
Defining a device class is a means of grouping network printers, print queues, and workstation printers, so that you
can apply common tracking methods to the grouped devices simultaneously.
Each device you register in System Manager can belong to only one device class at a time. The first time a user sends a
document to a device, Equitrac Professional assigns the device to the default class. The default class tracks for cost
recovery by default. You can reassign the default status to any class, however, there must be only one default class.
Device class settings take precedence over any document management system (DMS) and application class settings in
terms of the tracking behavior hierarchy. User class tracking settings overrides any tracking configuration you do for
device classes. See Print Tracking Hierarchy on page 346 for details.
You can track a device for cost recovery or total cost of ownership purposes, or both.
NOTE: For more information on these settings and the general tracking behavior hierarchy, see Print Tracking
Hierarchy on page 346.
6 Click Override to set device class overrides. This expands the Device class definition dialog box.
7 In the grid, click <Add...> to open the Override popup tracking behavior for user class association dialog box.
a Select the User class that the override will apply to from the drop-down list.
b Enter an Override description.
c Choose the overriding Tracking behavior from the options in the section.
d Click OK.
8 Repeat the above steps to add other override behaviors to other user classes as required.
9 Click OK to close the Device class definition dialog box.
3 Select the Default class option at the bottom of the dialog box.
4 Click OK to close the dialog box.
NOTE: You cannot delete devices from System Manager using the Device Class view.
3 Right-click the desired class and select Remove class from the menu.
Physical Devices
A physical device is the piece of hardware that performs the print, copy, scan, or fax, including multi-function devices
and embedded options on select manufacturer’s MFPs. Equitrac Professional can track usage on any physical device
that is registered in System Manager.
Within Equitrac, a physical device has three components:
• Device - the device name is registered in the Equitrac database and is used to manage the main device
characteristics. device, port, and queue.
• Port - a port connection on the device that works with the Equitrac Port Monitor to track printed documents sent
to the device. The Port Monitor communicates with the DRE or DCE to control the job requests made to the
device.
• Queue - A virtual list of jobs waiting to print on the device.
You do not have to manually create the three components. Instead, you create the printer using the Operating System’s
(Windows/UNIX) Add Printer utility and assign the Equitrac Port Monitor to the device. Equitrac Professional
automatically adds print queues and port connections to the database when a user prints to the device for the first
time.
CAUTION: Ensure that you apply licenses before managing devices in Windows and configuring devices in System
Manager. If you add licenses after adding physical devices, the print queues do not show up in System Manager until
15 minutes of time passes, you license Equitrac Professional, print a document to the printer or restart the DRE
service; any of these actions will register the devices and populate System Manager.
3 Enter a Name, Hostname or IP address, and Description for the physical device.
4 Select the appropriate Manufacturer and Model for the physical device from the drop lists.
5 Enter Monthly volume and Speed (in pages per minute) data in the fields.
6 Verify the detected color capability setting in the Monochrome settings field. Equitrac Professional automatically
detects this setting based on the SNMP data, but you can change the option to Monochrome if you want to count
all printed documents as monochrome, even when printing in color.
7 Select a Location from the drop-down list.
The device Type displays Physical device.
8 Assign price lists to jobs output from this device’s print queue. See Configuring Price Lists on page 143 for details.
9 Set the Release behavior options. Leave the default setting unless you are setting up Print pull groups. See Creating
Device Pull Groups on page 241 for details.
Rule Set • Apply a routing rule to jobs that are sent to this device. If the job attributes
match the routing rule, the rule is applied. See Routing Rules on page 257.
Print language • Change the default printer language settings that are used by this device. For
more information about language settings, see Data Stream Interpreters on
page 458.
Queue job if PageCounter active • Select this option to have the device queue the document for printing if the
PageCounter associated with the MFP is already in use by another user session.
Track mailbox & proof printing • If there is no PageCounter control terminal associated with a Xerox or Canon
device, you can determine at what point in time Equitrac Professional will track
the transaction details and submit them to CAS.
• Select ‘At output time’ to track these transactions when you release the
document(s) at the device.
• Select ‘At send time’ to track the transaction details when you send the
document(s) to the printer. If you select ‘At send time’, Equitrac will not know if
the job was released, nor how many copies were printed. Equitrac will record
the transaction as one released copy.
Tracking behavior • By default, CAS tracks all devices that appear within System Manager. There
may be cases when you do not want to track print or copy activity at a
particular device, but you still want to control access to the device. Select Do
not track and record printing to enable printing without enabling page
counting or transaction tracking on this device.
DME server • If you installed the DME component, select the DME server that you want to
manage this device. The device will appear in the DME console, and you can
track the SNMP status from there. For more details, see Device Monitoring
with DME on page 225.
2 Using My Computer, browse to the location where you installed Equitrac Professional.
3 Open the Tools folder, and double-click EQPrinterConversionWizard.exe.
7 Select or clear printers in the Convert Printers list, then click Next.
NOTE: The Port Conversion wizard does not populate the description data for physical device, ports, or print
queues. If you want to add a description, you can edit the device, port, or queue summary in System Manager >
Devices.
CAUTION: You cannot remotely configure printers without first installing the Equitrac Port Monitor software to both
the Print Server, and any workstation intended to remotely configure printers. The Equitrac Port Monitor must be
present on the workstation to enable it to display the Print Spooler User Interface dialog boxes, which are used to
configure the printer in question.
1 Using your standard Windows interface, open the Add Printer wizard.
2 Follow the prompts to add a local printer and create a new port.
3 When prompted, select Equitrac Port as the type of port you want to create and click Next.
4 The Add Equitrac Printer Port wizard displays and you are prompted to ensure that the printer device is turned on,
connected to the network, and properly configured. Click Next and select Physical printer as your Device Type
from the drop list.
5 Specify a Printer name or IP address.
6 The wizard supplies a Port name based on the printer name or IP address. Change this name manually, if desired.
7 Click Next to continue with the port configuration options. The Port Configuration screen displays. The Detected
device information displays automatically if the wizard can collect this data from the printer.
Option Description
Name • The name for the port. By default, the port is assigned the device IP Address.
Description • A text description of the port that will appear in System Manager. Enter a good description if you
commonly use the Type view. The description should reflect the device name that the port belongs
to, or the location where the device is located.
Server • Displays the local print server. This field is provided for information only.
Port number • Displays the currently configured port number for this port.
Queue print server • Displays the name of the DRE print server that manages this port.
Pricing • Apply price lists to the jobs output from this port. Price lists assigned to a port will override any
price lists assigned to the physical device.
• See Configuring Price Lists on page 143 for full details.
Rule set • Select the set of Routing Rules that you want to apply to this port. Rules can hold, release, restrict
access to, redirect jobs, reprice jobs, etc.
• You need to configure secure printing on the queue, and create routing rules before they will
appear in this list. See Configuring Print Queues on page 193 and Configuring Price Lists on
page 143 for full details.
Option Description
Connectivity • You can edit this field only when the port communication type is set to RAW. This option does not
apply to LPR and Passthrough ports.
• Choose Hold port Open to ensure that users can only print to the device through the print server,
preventing users from bypassing the accounting server and establishing an exclusive connection
to the network printer.
• Choose Close port on completion to share the printer connection with other non-Equitrac printer
definitions.
Notification page • Determines if users will be notified when print errors occur on this port.
• You must configure System Manager > Configuration > Error Notifications to set the
notification details. See Selecting Notification Methods on page 68.
Uses PJL • If the physical device is connected to a Printer Job Language (PJL) page counter device, enable this
option.
• When disabled, Equitrac Professional uses the Datastream Interpreter page counting method
configured at the physical device level.
• Note that you cannot enable secure printing when the device is connected to a PJL Page Counter.
The PJL page counter does not count pages correctly in a queuing environment.
In the Print Queue Summary dialog box, you can set these options:
Description • A text description of the queue that will appear in System Manager. Enter a good description if
you commonly use the Type view. The description should reflect the device name that the queue
belongs to.
Pricing • Apply price lists to the jobs output from this queue.
• If you leave the Price list at the default setting, the price list configured at the port level will be
applied to all jobs released from this queue.
• See Configuring Price Lists on page 143 for full details.
Secure Printing • Enable this option to hold all jobs in a virtual print queue, rather than forwarding the jobs directly
to the device for immediate output.
• Secure printing is disabled by default.
• If your deployment involves Release Station or control terminal release, you need to enable secure
printing on each queue that should be held for release.
• See Secure Printing Overview on page 238 for full details.
Rule set Select the set of Routing Rules that you want to apply to this port. Rules can hold, release, restrict
access to, redirect jobs, reprice jobs, etc.
You must create rules before they will appear in this list. See Routing Rules on page 257 for full
details.
If you experience problems with a separator page, remove the Equitrac Professional escape codes from the file, then
ensure that the page prints correctly under a non-DRE controller printer. Consult your Microsoft documentation for
details.
Although Equitrac Professional installs a default separator page with the DRE, it is not enabled on any device. The
instructions below use the default separator page provided with Equitrac Professional.
1 On the DRE server, open \Program Files\Equitrac\Professional \Separator Pages\pcl.sep in
any text editor.
2 Choose the escape character that you want to use. The default file uses the \ symbol, but you can choose any
character you want.
This character identifies the syntax used for all escape codes within the file. Choose a symbol that you do not want
to print on the separator page. For example do not use the @ symbol as the escape character if you want the @
symbol to appear anywhere on the separator page (within an email address, for example).
3 Enter the escape codes for the functions you want to print on the separator page. See the table below for a complete
list of codes, and an example.
4 Save the file using a new name with a .sep extension in Program Files\Equitrac\Professional
\Separator Pages.
5 To apply the separator page, open System Manager > Devices, and open the device’s print queue.
6 In the Separator pages field, type the name of the separator page, including the .sep file extension.
\L Prints all following characters until the next escape code. Use this code to add messages on the
print separate page. For example, you could use:
\L Job Name
\Fpathname Prints the contents of the file specified by its path name.
\Hnn Prints the character defined by the nn variable. This variable is a hexadecimal ASCII code. See you
printer manual for specific variable numbers accepted by your device.
\Wnn Defines the width of the separator page. The default width is 80 characters and the maximum
width is 256. Printable characters that exceed this width will not appear on the separator page.
\E Ejects a page from the printer. Enter this variable to end the separator page.
Note that some printers detect this automatically. If you include the /E escape code and the
printer generates an extra blank page between the separator page and the print job, remove this
escape code.
\@ Prints the @ characters. You can use this escape code if you want to append the user name with
the domain name for example.
\N\@\L domain.com
\Q\b Applies the cost of the document that follows the test page, then prints the user balance.
\Q\c Prints the cost of the document that follows the test page.
The example below shows the contents of the default pcl.sep page and the result when you print the separator page.
\U\LTime: \T
The resulting print separator page, where ’USER’ is replaced by the actual
user name
E-queues
An e-queue is a virtual print queue that holds print jobs until the user releases the jobs to a specific printer. Unlike
secure printing, an e-queue consolidates requests from more than one printer, holding all jobs in the virtual queue.
You can define an e-queue as part of a pull group to enable users to pull documents from an e-queue to any of the
printers associated with that particular pull group. For information on configuring pull groups, see Creating Device
Pull Groups on page 241.
Configuring an e-queue
Use the System Manager > System > Devices link to configure an e-queue in Equitrac Professional.
1 In Standard View, click on the e-queue you want to configure.
2 Click an e-queue link in the right pane to open the e-queue summary dialog box.
You can apply a default price list or a primary and optional secondary price list for each applicable function on the
workstation device.
See Configuring Price Lists on page 143 for details on configuring price lists.
NOTE: Generally, you define price lists for an e-queue’s port or print queue. An e-queue’s port or print queue price
list overrides the e-queue’s selected price list.
7 Click the Printer language link to open the PageCounters dialog box and manage the supported downstream
interpreters for the e-queue’s printer driver.
8 Click OK to close the e-queue summary dialog box.
Passthrough Printers
Equitrac Professional does not communicate directly with certain physical printers, such as those using proprietary
communication protocols outside of Raw or LPR. A passthrough printer acts as a translator, converting print
protocols between Equitrac Professional and the target printer.
Add and configure a passthrough printer to pass print transactions to a target printer that does not use the Equitrac
Port Monitor and that Equitrac Professional does not track. Users print to the passthrough printer, which sends the
document to the target printer.
2 In the right pane, click a physical device link of a passthrough printer to open the Physical device summary dialog
box.
3 Enter a Name and Description for the target printer to which passthrough print jobs are sent.
The Hostname/IP address contains the connection to the target printer.
NOTE: In the right pane of System Manager > Devices, the Hostname or IP address of the physical device stores
the target printer name. Only update the Hostname or IP address if you change the name of your target printer.
4 Select the appropriate Manufacturer and Model for this device from the drop lists.
5 Enter Monthly volume and Speed data in the fields.
6 Specify the Monochrome settings for this device. Use this option to define the device as monochrome and prevent
Equitrac Professional from applying a default color price list to color documents printed on the device.
7 Select a Location from the drop-down list.
The Type displays Physical device.
8 Click Pricing to apply a price list to the passthrough printer. You can apply a default price list, or a primary and
optional secondary price list for each applicable function on the passthrough printer.
See Configuring Price Lists on page 143 for details on configuring price lists.
NOTE: Generally, you define price lists for a Passthrough printer’s port or print queue. A passthrough printer’s port
or print queue price list overrides the passthrough printer’s selected price list.
9 If you plan to use the device for secure printing, configure release document device behavior.
• Select the At assigned control terminal option to release documents to the control terminal associated with
the passthrough printer.
• Select the Release documents from pull group option to configure the passthrough printer to pull documents
from a pull group for printing. Enter the desired pull group in the field or click Browse to select from existing
pull groups.
Rule Set Apply a routing rule to jobs that are sent to this passthrough printer. If the job
attributes match the routing rule, the rule is applied. See Routing Rules on page
257.
Note: Generally, you define print rules for a passthrough printer’s port or
print queue. A passthrough printer’s port or print queue print rule
overrides the passthrough printer’s selected print rule.
Print language • Change the default printer language settings that manage the supported
datastream interpreters for the passthrough printer’s print driver. For more
information about language settings, see Data Stream Interpreters on page
458.
Track mailbox & proof printing • If there is no PageCounter control terminal associated with a Xerox or Canon
device, you can determine at what point in time Equitrac Professional will track the
transaction details and submit them to CAS.
• Select ‘At output time’ to track these transactions when you release the
document(s) at the device.
• Select ‘At send time’ to track the transaction details when you send the
document(s) to the printer. If you select ‘At send time’, Equitrac will not know if the
job was released, nor how many copies were printed. Equitrac will record the
transaction as one released copy.
Tracking behavior • By default, CAS tracks all devices that appear within System Manager. There may
be cases when you do not want to track print or copy activity at a particular
device, but you still want to control access to the device. Select Do not track and
record printing to enable printing without enabling page counting or transaction
tracking on this device.
DME server • If you installed the DME component, select the DME server that you want to
manage this device. The device will appear in the DME console, and you can track
the SNMP status from there. For more details, see Device Monitoring with DME
on page 225.
NOTE: To ensure accurate document tracking, select the appropriate datastream interpreter/printer driver
combinations for your devices. For example, to use the Postscript Page Interpreter, use a postscript printer driver.
11 Click OK to save the passthrough configuration settings, or Cancel to close the dialog box without saving any
changes.
NOTE: If you want to register printers from multiple workstations, run the tool at each workstation.
To run the utility to automatically register non-DRE network printers, run the command using the -n and -r
parameters, as follows:
EQRegisterPrinters.exe -n -r
NOTE: When registering network printers, run this command from a single workstation; network printers only need
to be registered once, they do not need to be registered for each workstation that accesses them. The registration
process may take several minutes.
The utility uses the following parameters: [-l] [-r] [-d] [-v] [-t], where
-l lists all printers available to the current workstation
-r registers all available printers with the Equitrac Professional core accounting server
-d performs the requested operation for DRE printers only
-v shows utility version information
-t enables trace logging for troubleshooting
See Configuring Price Lists on page 143 for details on configuring price lists.
NOTE: Generally, you define price lists for a workstation device’s port or print queue. A workstation device’s port or
print queue price list overrides the workstation device’s selected price list.
7 Select a Tracking group option for the workstation device by selecting one of the following options:
• Non-tracked: does not track the device.
• Tracked with popup: tracks the device and displays a popup at print time.
• Silently tracked: tracks the device without displaying a popup at print time.
NOTE: You can change the tracking group of the workstation device by editing the device’s configuration.
8 Click OK to save these settings, or Cancel to close the dialog box without saving any changes.
3 Right-click Ungrouped devices and select Manage custom groups from the drop-down list.
4 In the Manage groups dialog box, enter the desired name for the group and click Add.
5 Repeat these steps as required to add all necessary groups.
6 Click OK to close the Manage groups dialog box and return to the Custom group view. In the example below, a
new custom group named “Workstation” was added.
NOTE: When you first add a device (that is, a printer or multifunction product) to your Equitrac Professional
environment, System Manager assigns that device to the Ungrouped devices group. Therefore, if you have not yet
assigned devices to custom groups, all devices reside within the Ungrouped devices group.
To add a device to a custom group, do the following from within System Manager’s Custom group view:
1 If necessary, expand Ungrouped devices to show your physical devices.
2 Click the desired device, drag it to the appropriate custom group, and release. System Manager adds the device to
the group.
3 Repeat step 2 as necessary to add your devices to the appropriate custom groups.
NOTE: Workstation consolidation is available only for devices addressed using standard TCP/IP ports directly from
the workstation. USB printers or those connected directly to a workstation in some physical way, such as a parallel
port, are not supported.
Workstation ordering
When workstations are added to System Manager using Workstation Network Printer Consolidation, they are
grouped by the referenced Printer Name at the workstation. Workstation names are not listed. The hierarchy for
ordering of workstations in System Manager using Workstation Network Printer Consolidation is as follows:
The workstations in blue above are not displayed in System Manager. Note, however, that in the above example,
workstations 1 and 2 are consolidated under Printer Name 1, because both workstations have named the printer
identically. Similarly, Workstations 1 and 3 are consolidated under Printer Name 2. Note that a workstation can appear
under several printers.
NOTE: Configuration happens at the Device or Printer Name levels only. Per-workstation configuration is possible
only if the workstation in question has a unique name for its assigned device. In the above flowchart, you could
configure the settings for only workstation 3 by changing the configuration settings of Printer Name 2. You could not
configure only workstation 2, because configuring Printer Name 1 effects both workstation 2 and workstation 1.
The information is presented in the System Manager > System > Devices pane in the following way:
Physical device, with associated IP address
There is one entry under the device for workstations 1and 2. This is because, in this example, the workstations in
question use the same Printer Name. Workstation 3 has its own entry because it uses a different Printer Name. If every
workstation in an organization names its devices identically, there will be only one entry under the device. If every
workstation names the same device differently, a new entry is created for each workstation.
Regardless of the Printer Name given to the device at the workstation, all Printer Names are grouped under the
device’s IP address. This allows you to configure all workstation devices by altering the settings of a single device.
The information is presented in the System Manager > Client config > Devices pane in this way:
Device class
Use cases
Once installed and enabled, you will use Workstation Network printer consolidation in various ways under particular
situations. Below are three typical situations you may encounter, and how Workstation Network Printer Consolidation
functionality handles them.
New Installation
During a new installation of Equitrac Professional, existing connections between workstations and MFP devices are
reported to Equitrac Professional to enable cost recovery procedures. Because there is no print server, workstations are
organized in System Manager under the Printer Name of the device they are printing to.
Any number of workstations that share the same Printer Name for a device also share that device’s settings. Changes
made to configuration settings for a particular device are inherited by each workstation under the device. This
facilitates easy administration of devices on multiple workstations, negating the need to administer on a per-
workstation basis. Any physical device or individual workstation devices can be selected in System Manager using the
windows native multi select functionality (either ctrl-clicking or shift-clicking), which allows similar changes to be
affected across multiple devices simultaneously. All information about device classes and individual devices can be
sorted within System Manager by clicking the heading of the column containing the needed information.
A common new installation use case follows:
1 Deploy the software, register the devices, and the workstations.
a Equitrac professional is deployed in an organization that does not use a print server, or has devices that are not
handled through a print server that need to be tracked.
b The first time a print client is installed, configured and run on a workstation, it reports to Equitrac Professional
which printers that workstation is configured to use.
c Equitrac Professional collects the device data and automatically registers the devices in the Equitrac
Professional Core Accounting Server under the default class. The devices inherit the settings attributed to that
class.
d Workstations are ordered under the device based upon the Printer Name given to the device at the workstation.
For detailed information, see Workstation ordering on page 207.
b Other classes are created by the system administrator as needed, to differentiate tracking behavior on the
system. Once created, devices can be moved between classes by right-click/Assign, or by click/dragging the
device between classes. All workstations under the device inherit the tracking settings of the class the device is
part of.
c Previously unregistered physical devices are added to the default class. If you want new devices to be added to a
class of your choosing, any class can be designated as the default class. For detailed information about
managing device classes, see Device Classes on page 183.
d Classes and their related information can be sorted in any way the administrator chooses by clicking the
column heading for the desired sort criteria. For example, classes can be sorted by their name by clicking the
Name header above the column. This can facilitate the use of multi select when administering classes by
grouping many devices contiguously for easy multi-selection.
3 Administer the devices.
a From the System > Devices pane, any device can be clicked to display its Physical device summary dialog box:
b Device settings can be modified as required. All of the changes made at this level are inherited by every printer,
and therefore every workstation, under the device. For detailed information on how to configure physical
devices, see Physical Devices on page 187.
c Devices and their related information can be sorted in any way the administrator chooses by clicking the
column heading for the desired sort criteria. For example, devices can be sorted by their name by clicking the
Name header above the column. This facilitates the use of multi-select when administering devices.
4 Administer the workstations.
CAUTION: This is only supported if the workstation in question has a unique name for the device, and therefore its
own entry under the device. Creating custom settings between workstations that reference devices by identical
names is not supported.
a If a specific workstation printer’s settings need to be different than those of other workstations referencing the
same physical device, the settings can be overridden at the device level, by clicking the Printer Name associated
with the workstation. The Workstation summary dialog box opens, where you can make changes:
b Workstation device settings can be modified as required. Changes made at this level affect only the
workstations using this Printer Name. For detailed information on how to configure workstations, see
Configuring a Workstation Device on page 203.
NOTE: If the workstation shared devices and had named the devices identically to other workstations, no changes
are required.
In the above simple flowchart, there are four Printer Names organized under a device. There are eight workstations
consolidated under the various Printer Names. For more information about how these are ordered, see Workstation
ordering on page 207. Only one workstation under a single Printer Name uses different settings (Settings 2, rather
than Settings 1). In a case like this, when a new Printer Name is added, the workstation associated with the name
inherits Settings 1, because Settings 1 contains the configuration settings shared by the majority of the Printer Names
under the device.
This form of automatic setup is effective in most cases. If the workstation in question must have settings that differ
from the majority of Printer Names under the device, the system administrator must ensure the workstation’s
Printer Name is unique, and must configure its settings after the fact, or must ensure the Printer Name for the
workstation matches the Printer Name of an existing entry with the desired settings to allow the new workstation
to inherit the correct settings.
NOTE: If there are no Printer Names under a device, the new Printer Name inherits the settings of the device, if set
up, or the settings of the default class if it is a new device.
2 The workstation is consolidated under the device by its Printer Name. For information about workstation
ordering, see Workstation ordering on page 207.
3 If the Printer Name is identical to an existing Printer Name with the desired settings, it is consolidated into the
existing Printer Name, and inherits the settings of that name.
4 If the Printer Name is unique, it inherits the settings of the majority of Printer Names under the device.
The system administrator must change the settings for the new Printer Name to the desired configuration.
Topics...
Controller and Embedded Device Configuration
Workflow
Adding a Controller or Embedded Interface to a Device
Xerox Device Configuration
Forcing a Poll or Upload
Removing an Embedded or Controller Interface
Controller and embedded interfaces are discrete software applications that enable varying degrees of validation
authentication on an MFP. Equitrac Professional supports the following controller and embedded interfaces.
Controller Interfaces
A controller interface is a software bridge that enables authentication to occur from the front panel of supported
MFPs. The following are supported controller interfaces:
Xerox JBA
If you are implementing Xerox Job-based Accounting (JBA), you require a Xerox controller interface. For detailed
information about Xerox JBA, see Xerox Device Configuration on page 220.
Embedded Interfaces
An Embedded interface allows specific MFPs to host Equitrac applications that track and report output activity. The
following are supported embedded interfaces:
• Canon MEAP
• HP Laserjet MFP
• Ricoh ESA
• Xerox EIP
• Fuji-Xerox
See the Setup Guide for the appropriate embedded interface for more information.
This chapter contains general information to assign a controller interface to a device, and instructions to setup Xerox
JBA with Equitrac Professional’s System Manager.
2 In the Controller interface summary dialog box, enter a Name and Description for the interface.
3 The Server defaults to the current DCE host. Change the server, if necessary, by selecting another server from the
drop list.
NOTE: The device Type and Status data display automatically. The Controller type is automatically set to Xerox.
b In the Initialize Xerox/Fuji-Xerox dialog box, select the push or pull method of validation:
• Upload accounts forces Equitrac to upload user data to the device.
The data that is uploaded to the device is determined by the Method setting in the Xerox configuration
dialog box within Equitrac Professional. Ensure the Xerox device is configured correctly, as outlined in
Xerox Device Configuration on page 220.
If the device is a Fuji-Xerox machine, ensure that you also select the Enable Fuji-Xerox description
extensions box. Equitrac will configure the device to use the correct extensions.
• Off-box validation forces the device to send a request to Equitrac to validate the data input by the user. See
Off-Box Authentication Options on page 223.
6 The EQXConfig.exe utility launches in the background to change the settings on the Xerox device. If the change is
successful, the utility displays “A level 5/5 set_config request successfully committed...” If unsuccessful, the utility
displays, “Set_config call failed.” If the changes fail, you may need to try again several times.
7 Click OK to save these settings, or Cancel to close the dialog box without saving any changes.
2 In the Embedded device selection dialog box, select an Embedded device type and click OK.
3 In the Embedded device summary dialog box, enter a Name and Description for the definition.
4 The Server defaults to the current DCE host. Change the server, if necessary, by selecting another server from the
drop list.
5 Specify the serial number of the device hosting the embedded application.
NOTE: The Device type will be either Canon MEAP, Ricoh ESA or HP LaserJet.
7 Select the default price list to configure the interface to use the price list for the associated device. If you select an
alternate price list for the interface, the interface price list overrides the device setting.
8 Define specific Behaviors for this interface:
a Define a rule set for Equitrac Professional to apply to documents printed at this device. For more information
on defining and applying rules, see Routing Rules on page 257.
b Specify the offline behavior for this interface in the event that it cannot contact DCE or if the CAS service is
offline. Equitrac Professional uses DCE login caching to let users still log in, make copies and release print jobs
even when CAS is offline. DCE caching allows embedded interfaces to grant device access to previously CAS-
validated users, and caches all user transaction details and then uploads to CAS once contact is re-established.
c Select which third-party scan solution you wish to integrate scans with. Click on Options to configure scan
integration options.
d Enable or disable secure document release. If you enable SDR, select the desired release behavior from the
drop list. For more information on the SDR feature, see Secure Document Release on page 237.
e Specify what, if any, transaction tracking you want the interface to record. In the Embedded device
configuration dialog box, if you do not elect to override defaults, Equitrac Professional will use whatever
tracking options you have already defined on the basis of User, Device, or Application classes. If you enable the
override, however, specify the device functions you want to track.
9 Click OK to save these settings, or Cancel to close the dialog box without saving any changes.
NOTE: To prevent Xerox JBA conflicts with multiple pop-ups for print transactions originating with the Equitrac
Professional Print Client, disable tracking for desktop printers if the Print Client resides on the same machine as the
Xerox embedded print-tracked device. Optionally, you can forego installing the Equitrac Professional Print Client on
this particular PC or server.
NOTE: You must create at least one controller interface before you can configure the interfaces system-wide. Right-
click on a Device in System Manager > Devices, and select Add controller interface from the menu. The Controller
Type is automatically set to Xerox.
1 Open System Manager, and click Configuration > Device Settings > Controller interfaces. The Xerox device
configuration dialog box opens.
2 From the User and account are drop-down list, select an authentication method to determine what account
information the Xerox device prompts users for, and how the Xerox device validates that user. The authentication
method specifies what account data Equitrac Professional sends to the Xerox device to correspond with the Xerox
device user and account ID fields.
NOTE: If you select UserCode and Client, Matter from the method list, users must enter their user Id in the UserCode
field, and the client and matter in the Account ID field. The required format is Client code, followed by a comma,
followed the Matter code. (010121,99933).
3 Change the Case Conversion setting if the Xerox device requires only upper or lower case text. Consult your
Xerox documentation for case requirements.
4 Select or clear the Enable local authentication upload option to specify whether or not Equitrac Professional
automatically sends specific account data to the Xerox device at specified intervals. The controller interface uses
the account data to verify users, charge the associated account, and release documents to the printer.
• Select the option to configure Equitrac Professional to automatically send account data to the Xerox device.
• Clear the option to prevent the DCE from automatically sending account data to the Xerox device. You can
manually force Equitrac Professional to send account data using the Force an upload option available in
System Manager > Devices. See Forcing a Poll or Upload on page 224 for details.
The PIN information users enter at the Xerox device must match the information Equitrac Professional has sent to
the device, regardless of whether you enable or disable automatic authentication upload to devices. Users cannot
use the device until they enter correct authentication values.
5 Adjust the Upload interval to change how frequently Equitrac Professional sends account data to the Xerox
device, when you enable authentication. By default, Equitrac Professional sends user account data once every 24
hours (or once every 1440 minutes).
You must enable authentication before Equitrac Professional sends any account data to the Xerox device. If no
accounts exist, Equitrac Professional sends empty account tables to the device, and the device denies users access
to the machine.
6 Enable Automatic release of all print jobs upon validation to release all user documents to print immediately
after a successful login. This option is used for off-box authentication only.
7 Adjust the Poll interval to change how frequently Equitrac Professional requests job activity details from the
Xerox device. By default, Equitrac Professional requests job activity details once every 30 minutes (or once every
1800 seconds).
When you configure Equitrac Professional to create new accounts automatically, at defined polling intervals,
Equitrac Professional requests job activity details from the device and creates new accounts in the database. See
Auto-creating User Accounts On First Print on page 62 for more details. When adjusting polling values, include
enough time for one poll to complete before the next poll begins.
8 In the Secure access authentication prompts area, enter labels for Title and Login prompt you want to use to
prompt users when logging in to the embedded authentication screen.
9 Select the Enable release all jobs prompt to display an option to release all pending jobs.
10 Select or clear the types of transactions that Equitrac Professional tracks or does not track on the Xerox device,
including copy, print, network scan, received fax, and sent fax transactions.
NOTE: Enabling or disabling transaction type tracking on the controller interface does not configure transaction
type support on the Xerox device. For example, if you do not configure the Xerox device for fax support (sending or
receiving faxes), tracking received faxes or sent faxes through the controller interface does not change fax support
on the Xerox device.
NOTE: On some Xerox models, you cannot enter authentication data with lowercase characters on the panel. Xerox is
case-sensitive when it compares data collected from the print transaction with the accounting codes stored in the
device’s local database. Equitrac Professional must convert all account codes to uppercase before uploading to Xerox
devices, and you must enter authentication data in the Xerox print dialog box in uppercase.
In order for Xerox devices to accept authenticated print jobs and the controller interface to track print jobs correctly,
you must configure the Xerox device and Xerox print drivers as described in the following table.
Install and enable the Network Accounting • Equitrac Professional does not support the Internal Auditron
module on each Xerox device. authentication method.
• When you set the authentication mode on the device, ensure you select
the Network Accounting option.
Enable the Network Accounting • Depending on the Xerox device Authentication configuration, the device
Configuration > Authentication option. can accurately track job information regardless of whether or not the user
and account information exists on that device.
• See the Xerox device documentation for details on configuring options
for the physical device.
Enable the Accounting option on installed • The location of the Accounting option in the Xerox print driver dialog
Xerox print drivers, for each printer to boxes may not be the same for all printer connections you create.
prompt users for user and account ID prior • The option may be located on the Properties > Document Details or the
to printing. Printer Preferences dialog boxes. You may find that the location of the
Accounting option varies by Windows platform, driver language type
(Postscript or PCL), driver version, or device model.
• The Xerox device deletes print jobs to prevent anonymous (un-billable)
printing when any of the following situations apply:
•The Xerox print driver does not have authentication features.
•The Accounting option for the print driver is disabled.
When tracking print jobs through the • Print jobs will be tracked twice if the controller interface for Xerox exists in
controller interface, installed Xerox printer System Manager > Devices to track print jobs through the controller
connections must use Windows or other interface while the Xerox printer connection uses an Equitrac Port
non-Equitrac Port Monitors. Monitor. Both the Equitrac Port Monitor and the controller interface track
the print job.
1 In System Manager > Devices, click the drop-down beside the Xerox device you want to configure, and click on the
Controller interface that you created for the device.
2 In the controller interface summary dialog box, click the Initialize button located under the Device initialization
options.
3 In the Initialize Xerox/Fuji-Xerox device dialog box, select Off-box validation, then select the DCE you want to
use for validation prior to processing the printing activity. For further details, see page 217.
Topics...
DME Workflow
SNMP Communication Requirements
Installing the SNMP Trap Service
Which Devices Does DME Monitor?
Viewing Device Status within the Console
Creating Alert Rules
Assigning Alerts to Devices
Viewing Device Status within the Console
Routing Based on Device Status
The Device Monitoring Engine (DME) is an optional server component that gives an Administrator the power to
identify potential device problems based on historical performance data.
The DRE monitors SNMP messages generated by specified devices for status information. Each time a status change
message is intercepted, DME logs the information in the database. If the new status matches a pre-set alert condition
on that device, a notification message is forwarded to designated individuals or desktops. You can view the current
device status at any time within the DME Console, or you can run reports to ascertain the overall device health, and
plan maintenance based on historical performance.
This chapter provides information about:
• The workflow required to configure and use DME
• Communication required between Equitrac Professional components and SNMP devices to capture status change
information
• Creating Alert Rules that specify the faults you want to be notified about per device
• Assigning rules to specific devices
• Viewing status information within the DME Console
• Generating reports to analyze system status information over time
DME Workflow
Configuring DME to monitor devices is a straightforward task. The DME console automatically contacts the CAS to
determine the list of devices to monitor. Without any further configuration, you can view the current device status
within the Device Monitoring Console, or you can generate reports within the Web Reports to view historical status
detail.
However, if you implement more than one DME, you need to establish which devices each DME will monitor. In
addition, if you want to receive error notifications, you can define Alert Rules that send a notification message when a
particular fault condition occurs. After you establish the rules, you can apply them to one or more devices within the
DME Console.
Follow the workflow below to configure full DME functionality. The remainder of this chapter provides detailed
information about each step in this workflow.
1 Ensure that the SNMPTRAP.EXE service is enabled on the DME server.
You must install and start this service to enable DME to listen for SNMP traps. See Installing the SNMP Trap
Service on page 228 for instructions.
2 Select devices to monitor in System Manager
DME automatically contacts the CAS to retrieve the list of devices to monitor. Within System Manager, you can
manually remove devices from DME monitoring, or assign devices to a particular DME.
3 Create alert rules in the DME Console
Create custom rules that apply only when certain fault conditions occur. Alert rules include configuration
notification options that alert specific Administrators when the fault occurs.
NOTE: To use the DME Console, you must be part of the Device Administrator group within System Manager’s
Access Permissions.
SNMP-enabled
1 Request Monitored Device List Devices
DME
Console
2 Load Monitored Device List
SNMP
status
DB 3 Update Device Status changes
CAS DME
If you prefer not to monitor a particular physical device with the DME, you can set the DME server field to None. The
DME Console will not monitor the status of the device nor will the device appear in the Console.
NOTE: Within the DME Console, the status column updates only when you press the Refresh button. If you are
checking the current status of a device within the Console, make sure you refresh the window to force the Console to
retrieve the current status information from the DME component.
If DME cannot populate the device type information (i.e. it was not provided when you added the device to Equitrac
Professional), the DME Console retrieves the information from SNMP data. DME then populates the Manufacturer
and/or Model fields with the retrieved data, followed by an asterisk *.
Use the following table to map the status code to the SNMP fault condition that has occurred on the device.
Status Description
Unknown This status occurs if the DME has not yet tried to contact the device or if the DME
Console cannot communicate with the DME component.
Near Full Output Tray The output tray has almost reached capacity. Jobs will not print when the tray reaches
capacity.
Overdue Maintenance The maintenance date has passed, as per the date set on the device by a service person
or Administrator.
Warning The device is reporting a general status warning, but DME is unable to specify the cause.
For example, some printers report a warning when a paper tray is empty, even though
that tray is not requested as the paper source for a print job.
Unreachable The DME did not receive a reply when asking the device for its status.
Missing Input Tray An input tray has been removed from the device.
Output Tray Missing An output tray has been removed from the device.
Missing Marker Supply The marker supply has been removed from the device. Marker supply refers to the toner,
ink, dye, etc., that is specifically used on this device.
Full Output Tray The output tray is full and jobs cannot be printed.
Empty Input Tray A job cannot continue because there is no medium in the specified input tray.
Down The printer is reporting its status as DOWN, but DME cannot determine the cause. DME
has received an unrecognized error status.
There are three facets to each Alert Rule: Name, Action, and Criteria.
Name
Each rule must have a unique name. Equitrac Professional stores the rule within the CAS database. Use the name to
identify the rule within the DME Console. You can optionally include a description of the rule which enables other
Administrators to understand the rule criteria at a glance from within the DME Console.
Action
Select one or more notification methods that DME should use when the Rule’s criteria is met. By default, Equitrac
Professional enables the Email and Event Viewer options. The table below describes each option.
Console • Sends a pop-up message to the machine where the DME Console is installed.
Criteria
Criteria refers to the type of fault that will initiate the notification. Criteria optionally refers to the duration and
frequency of occurrence.
DME can monitor SNMP enabled-devices for the following fault types:
You can select one or more fault types in the Alert Rule criteria. If a selected fault occurs on a device to which you
assigned the Alert Rule, the Action options are applied. If you want to receive separate alerts for more than one type of
fault per device, you must create a separate rule for each fault type, then apply the rules to each device as needed.
NOTE: Although you can select multiple fault types, as a best practice you should limit each rule to a single fault only.
An alert is triggered only when a status change is detected while the device is in its “ready” state. If one fault triggers
an alert, and another fault is triggered before the device resets to “ready”, a second alert message is not generated.
Instead, ensure that you select a single fault type per alert rule.
If you want to receive notification of a fault only if the fault continues to occur for a period of time, you can set the
Fault active for field. For example, if you want to receive notification when devices are Unreachable for five minutes
or more, set the Fault active to 5 minutes. If the device was unreachable only for a reboot, it’s likely that the device will
be back online before 5 minutes is exceeded. The DME will only send a notification message when the Unreachable
status persists for the period of time you indicate. Use this setting to minimize the possibility of a false alarm, and
eliminate the need for an Administrator to follow up on false alarms.
Alternatively, you can hold the notification message until the same fault occurs multiple times. For example, if you
want to monitor a device for recurring paper jams, you can set the number of occurrences to 5 jams over the course of
2 days. The DME only sends the notification when the device meets these conditions met, rather than each time there
is a paper jam.
Note that an alert is a one-time event. Once the DME performs the Action dictated by the alert rule, the notification is
sent just once. If you want to be notified more than once of a particular status change, you can use the Fault active for
or More than options. For example, if users within your organization are expected to fix paper jams themselves, you
might want to be notified when the paper jam first occurs, then every 5 minutes. After 20 minutes, you will fix the jam
yourself, or call someone to do it. To accomplish this, create the following alert rules, and apply them all to the device:
DME replaces the substitutions used with the actual fault type, occurrence, duration, or device type values that are
logged for the fault condition that cause the notification.
Custom messages can contain any text that you want, plus the variable substitutions described in the table below.
Substitution Description
%1 Inserts the fault type that triggered the alert. Fault types may be: Down, Offline, Paper Jam, Paper
Low, Paper Out, Toner Low, Toner Out, Unreachable or Warning.
%2 The number of times the fault has occurred. If your Alert Criteria uses the More than field, you
should include the number of occurrences within the message.
%3 The length of time the fault has been active. Duration is calculated using the start time field logged
in the DME database when the fault first occurred. If your Alert Criteria uses the Fault active for
criteria, you should include this information in the message.
To view the Alert rules applied to a device, you can either open the Assign alert rules dialog, or you can click on a
device Hostname in the Devices view to open the Device Properties dialog and review the list of assigned alerts.
—Or—
http://CAS1/EQClient/
In the Web Client, click on the Reports view. To view the device status reports, filter the Subject list by Device. Use
the table below to determine which report to run:
Device Configuration Device name Determine the full suite of devices controlled
Device type and tracked by Equitrac Professional.
IP Address
Manufacturer
Model
Device Faults vs. Usage Total Faults Determine how often a device is down in direct
Total Pages relation to the amount of usage on the device.
Faults per 1000 pages
For more information on Reports, refer to the Equitrac Professional Usage Guide.
Within System Manager > Rules & routing, select Add new rule from the list of Current tasks. Check Device status,
then choose a particular fault condition that will cause jobs to be re-routed. When the DME intercepts a device status
condition that matches the routing rule, it notifies the DRE. The DRE then directs any jobs waiting in the device’s
print queue as per the redirect criteria are met. If a print job is already started on the device, it will not be rerouted.
You can also specify a fault duration for the rule. In the case of a Paper Jam, a user might fix the jam immediately. If
you set the duration, the device must be in the fault state for at least that period of time before the routing rule takes
effect. Most likely, a user will fix a paper jam within 5 to 10 minutes, so consider defining the routing rule to re-route
jobs only after the status remains unchanged for 10 minutes.
CAUTION: Do not enable status-based routing if you are using Follow-You printing. The settings for these options
will conflict and produce unexpected behavior. Choose one option only.
Topics:
Secure Printing Overview
Configure Basic Secure Printing
Configuring Advanced Follow-You Printing
Administering the Secure Print Queue
Secure Document Release Using Release
Station
Secure document release holds printed documents in a secure virtual queue until the user release the documents via a
control mechanism such as a PageCounter, PageCounter Professional, TouchPoint Console, Release Station, or
embedded interface on the MFP.
The secure queue is established on the Document Routing Engine (DRE), and the DRE records each held document’s
status (released, deleted, expired) to provide accurate SDR results reporting.
This chapter provides information about:
• Basic secure printing: setting up virtual print queues that hold jobs until they are released at a control mechanism
by a valid user.
• Follow-You Printing extends secure printing functionality to allow users to pull their print jobs from one secure
print queue to another. To enable this functionality, you must also create device pull groups.
This chapter also provides instructions on configuring and using Release Station to release secure print jobs.
Release
Station
TouchPoint
User
Console
Workstation
PageCounter
In an advanced Follow-You printing setup, the user can choose a different destination printer at the Release Station,
control terminal or TouchPoint Console -- they do not have to release the job to the printer originally selected at the
user workstation.
CAUTION: If you also configure network printing Routing Rules that hold a job, the rules override the secure printing
settings for all devices that are part of a print rule. When a user submits a print request, Equitrac Professional first
checks the print rules to determine if the job should be held. If no rule exists for the destination printer, Equitrac
Professional checks the secure printing settings for the device. If secure printing is not enabled, the job is released
directly to the printer. See Routing Rules on page 257 for full details.
c Click the print queue link to open the Print queue summary dialog.
Destination
Queue in queue
Printer
DRE
Supporting secure document release through Follow-You Printing on PageCounter, PageCounter Professional, or
TouchPoint Consoles requires configuration both in Equitrac Professional and on the terminals/consoles.
b In the Physical Device Summary dialog, select Release documents from pull group. Type in the name of the
pull group (e.g PullGroupA), then click OK to apply the change. You only have to type in the name of the pull
group the first time you use it. Afterward, it will appear in the list automatically.
c Repeat steps a and b for additional physical devices that should be part of the pull group.
d To add the device to multiple pull groups, enter the name of the pull groups into the Release documents from
pull group field, separated by a semi-colon. For example, PullGroupA; PullGroupB; PullGroupC.
NOTE: The Physical Device Summary dialog is the only place you can view a list of available pull groups.
NOTE: Users are not able to print documents across servers when using TouchPoint Consoles. This option is
supported on PageCounter, PageCounter Professional, and Release Station.
3 The user logs on to a Release Station using valid credentials (either Windows login or release key, depending on
the Release Station configuration).
4 The user selects a destination printer (which can be an entirely different printer than the original device to which
he sent the document).
5 The user selects the destination printer.
6 The user selects his document from the list of queued documents.
7 Depending on the Release Station configuration, the user may receive a prompt for payment at this point, or
immediately after he selects a destination printer (step 5).
8 The user selects OK to release the job.
PageCounter Behavior
From the user perspective, the Follow-You release functionality follows this workflow on PageCounter terminals:
1 The user sends a document to a printer configured with a secure print queue.
2 DRE associates the print request with the user’s credentials, and holds the document in the secure print queue.
3 At the control terminal, the user will have one of the following options available for document release, depending
on the release behavior configured for the terminal:
All are released The device releases all queued documents for the current user N/A
automatically.
First is released The device releases only the first queued document. N/A
Select to release User can select one or more documents to release or delete. Document1.txt
Print Del End
Prompt The device prompts the user to release all documents for that Select Use:
user. All Select End
OR
Select Use:
All Select Find*
If the user presses F2 for Select, they can browse the list of jobs on the local server. If they press F3 for Find, they can
locate another print server. The following prompt is displayed:
Choose server name or search all
The user can press F1 to view a list of servers, F2 to search for a print server, or F3 to search for a document across
print servers. If F3 was pressed, the user will see the following:
[Print Server Name]
The user can use the arrow keys to select the server that contains the documents they want to release. The terminal
will then search the select print queue for documents printed by this user. The user can then select a document, print
or delete it, or cancel out of the terminal session.
4 Left-click any document in the list to select it. Hold down SHIFT or CTRL to select concurrent or multiple
documents in the queue.
You can sort documents in the list by clicking any of the column headings visible in the Viewer.
5 To delete selected documents from the queue, do one of the following:
• Select Delete from the Viewer’s File menu.
• Press the Delete key.
• Right-click a selected document and select Delete from the menu.
Select View > Simple view or View > Full view to change the default view depending on how many document details
you want to display.
Select View > Hide to close the Viewer without shutting down the service. The Viewer icon remains visible in the
Windows Task tray. Use the Refresh option to update the Viewer document list while the Viewer is open; the list does
not refresh automatically
To shut down the service, right-click the icon in the task tray and select Exit. You can also select Show/Hide to open
or close the Print Queue Viewer window.
NOTE: Full functionality is only available when you license your Release Station installation through System Manager.
You can run the application unlicensed, but only in view mode, meaning you can view or delete, but not print
documents in the list.
Session Security
Consider your release workstation and document security requirements when you determine the startup process for
user sessions by selecting one of the following options from the drop list:
Option Description
Prompt for release key This option is not applicable to Equitrac Professional.
End session after N seconds of The session times out automatically after a specified amount of time; 60 seconds
inactivity is the default option.
Automatically end session after The session closes automatically when a user releases documents to the printer.
document release
Disable exit for General users cannot close the application, they can only end the current session.
non-administrators
Release Station uses sessions to denote a specific period of usage, which varies depending on your configuration. You
can configure sessions to close automatically after certain actions, to time out, or to remain open.
A session typically begins and ends with a user logging on to the release workstation using Windows logon credentials
to print or delete queued documents.
Closing a session means closing that single incident of usage. The Release Station application stays open, ready for the
next user.
Automatic Refresh
Select one or more options for determining the refresh rate of the Release Station document list.
Option Description
Refresh document list every N seconds Release Station refreshes the document list display after the specified time
interval.
When new document arrives, play a sound Uses a sound file to notify users of new documents in the document list. This
feature uses the default beep or sound defined in your Control Panel >
Sounds setting, which you can change by associating a different WAV file in
place of the default. If you do not have a sound card and speakers, Release
Station uses the system speaker.
Non-Administrator Restrictions
Specify one or more options for users releasing or deleting documents in the print queue.
Option Description
Release one document per Enables users to select a single document for release every session; users with
session multiple documents for release must open a new session for each document.
Use this option to control printer access (for example, to prevent printer
monopolization).
Disable document deletion Users may not delete any documents in the print queue; this works best in
environments where users share accounts.
Disable zero-page, zero-cost document Users may not release any document that has no associated cost, or has content
release that the page counters cannot track.
Features
Select Enable Follow-You Printing to enable users to select print jobs in the Release Station and pull them to a
specific destination printer.
After a successful login, the Release Station displays a list of defined printers on the users local print server. If the
printer is part of a pull group, Equitrac Professional queries all printers within the pull group for print jobs belonging
to this user.
The printer must be part of a pull group to enable this functionality. If the printer is not part of a pull group, the
Release Station displays jobs on the current printer only.
See Creating Device Pull Groups on page 241 for system configuration information. See Using Follow-You on
Release Station on page 254 for instructions to release documents when Follow-You is enabled.
Option Description
Best fit Opens Release Station in the middle of the desktop at the largest size possible for your screen
resolution. You can enable or disable the minimize and window-sizing features.
Small/Medium/Large Specifies the default size for the Release Station window, based on specific resolution settings
for your monitors.
Option Description
Full-screen Release Station window covers the entire desktop, and cannot be minimized. This is the best
option if the workstation is a dedicated Release Station.
If you select this option, you cannot enable minimizing and sizing operations. You can shut
down Release Station in an open-access environment by clicking the Exit button, or in a public/
mixed security environment by logging on as an administrator to access the Exit button.
Hiding Buttons
For Buttons, select to hide one or both of the End Session and Select All buttons.
2 Click Add to open the Add Printer wizard. In the subsequent dialog, enter the name or IP address for the machine
hosting the DRE and click Next.
After you establish a connection to the print server, the list of available printers appears automatically. This list
includes all the devices defined to use an Equitrac port monitor on the specified print server.
NOTE: You must enable secure printing on the selected device in order to use Release Station as a document release
application for that device. For information on enabling and configuring print queues, see Configuring Print
Queues on page 193.
3 Select the printers for which Release Station will display documents.
4 Click Finish to add these printers to your Printers list.
NOTE: If you rename a device definition on the print server, you must remove and re-add the printer to the Release
Station printer list.
2 Print a test page. On the release workstation, use the Control Panel’s Printers feature to send a test page to an
Equitrac Professional printer. An Equitrac Professional printer is one that:
• Uses an Equitrac print monitor.
• Resides on a printer port that has queueing enabled.
• Is configured for use with a Release Station.
3 Start the Release Station application. If you have configured the application to request Windows user credentials at
startup, answer the prompt when it appears.
4 Confirm that your document appears in the list.
5 Select the test document from the list. Selecting the document displays a check mark next to it in the list.
6 Click Print to release the job to the printer.
NOTE: If you install Release Station on a workstation without a valid license, you can view and delete documents
from the print queue, however, you will not be able to print.
CAUTION: Full Release Station functionality is available only if you add a valid Release Station license within System
Manager. If you run the application unlicensed, you will be able to view or delete only, but you will not be able to
print documents in the list.
For security reasons, the user logged into Windows on the release workstation must have administrative privileges in
order to start Release Station.
NOTE: If the network requires domain qualification, the user must enter the Windows domain information in the
login window. Normally, this field defaults to the last-used domain name.
An unsecure session runs in a public mode that is accessible to all users. A login screen is not required, and all
documents appear in the print queue for all users to see and select. This type of session is designed for staffed or
secure release workstations, where only a small group of trusted users or administrators have access to the document
list. To enable unsecure sessions, the administrator must set the Release Station Security Setting to None. See Session
Security on page 248 for details.
2 Click Print to release the document to print, or Delete to remove the document from the queue without printing.
If the Release Station enables multiple document releases, you can click Print all to release them in a batch.
All printers that are configured to send to this Release Station are listed.
NOTE: If the selected printer is part of a pull group, the Release Station displays all compatible jobs from other
printers in the pull group, and on the local print server. For more information on creating pull groups, see Creating
Device Pull Groups on page 241.
Only jobs that the printer is capable of processing are listed in this particular queue. If you selected a destination
printer that does not support the job attributes of the original print request, the job will not appear in the queue.
For example, if you selected duplexing when you originally sent the document to print, but the destination printer
you selected does not support duplexing, the job will not appear in the destination printers queue. However, the
job is still queued at the Release Station, and you can simply choose a different destination printer that matches the
job attributes that the document requires.
NOTE: Note that the print job may be re-costed upon release if the ‘Reprice after release’ feature is enabled.
Ending a Session
You can configure a Release Station session to end:
• when the user manually ends the session
• automatically when the user releases a document
• automatically on a time-out after a period of inactivity
At the close of a session, Release Station resets to the configured size and positioning, and columns resize to the best fit
for current document data.
If you disable the exit for non-administrative users, the Exit (X) button in the top right corner of the window is not
visible. If the user attempts to close the Release Station window using Alt+F4 on the keyboard, the session ends and
the start dialog appears automatically for the next user.
Topics:
Rules Overview
Creating Print Rules
Creating Desktop Print Rules
A routing rule defines the conditions under which Equitrac Professional should manage a network print or desktop
print job on its way to the device, or under which Equitrac Professional should allow or deny a copy request.
Routing rules are useful when you want to create exceptions to the standard handling you define per device, port, or
queue. For example, if you enable secure printing on a queue, but you want to automatically allow jobs through to
print for a particular user group, create a print rule to allow jobs associated with users in the group to bypass the
secure queue and print immediately. Equitrac Professional will hold jobs sent to the queue by a user outside the group
in the secure queue for manual release via a terminal device, TouchPoint Console, or Release Station, but jobs sent by
a group member will print immediately.
Alternatively, you might want particular color copiers to be accessed by certain users only. You can create a copy rule
that allows only a particular group of users to access the copy functions.
All rules must be part of a Rule Set. Within System Manager, you can create a Rule Set, then create multiple rules
within the set. You can then apply the Rule Set to one or more devices, queues, ports, or control terminals.
This chapter provides information to determine:
• the rule types you need to define
• the attributes to assign to each rule to get the result you want
• the actions that you can assign to a rule and the result of each action
• how to apply a Rule Set to a device
Rules Overview
Each routing rule is comprised of three attributes. Equitrac Professional only applies a rule when the type and action
match the attributes of the incoming print/copy job.
Type: Determines if the rule applies to a print, desktop print, or copy jobs. You can also create a rule that applies to all
jobs sent to a device, regardless of type.
Attributes: Sets the characteristics against which the incoming job is compared to determine if there is a match.
Action: If the attributes of the incoming job match the attributes of the rule, take specific action.
To create a Rule Set, open System Manager, and click the Rules & Routing link. From the list of Current tasks, select
Add Rule Set.
In the Rule Set dialog, type a name for the Rule Set. When you apply the set to a device, you can identify the set by this
name. To add rules to the set, click Add. For information on creating rules, see Creating Print Rules on page 261 and
Creating Desktop Print Rules on page 265.
When you make changes to existing print rule criteria, or apply different Rule Sets to queuing actions, the changes
affect all subsequent print jobs. Changes do not affect documents currently in the print queue.
It is also important to note that Rule Sets override the secure printing setting on a device queue. If the following
conditions apply, an Allow rule will override the secure printing setting, and Equitrac Professional will not hold the
job in the secure queue:
• you set secure printing on a queue
• you assign a Rule Set that includes a Print Allow rule to the physical device, port, or queue
• Equitrac matches the Allow rule to the attributes of an incoming print job
For more information on secure printing, see Secure Printing Overview on page 238.
NOTE: If you are using Workstation Direct IP Printing (DRC), you must synchronize the CAS server with the DRC
before new rules take effect. For more information, see Forcing a cache update on page 262.
If you apply a Rule Set to the device, Equitrac Professional evaluates the rules in the set according to the rank order
applied within the Rule Set. Equitrac Professional compares the attributes of the print job to the rule type and rule
attributes. When it finds a match, it applies the rule action to the print job.
If you define more than one Print rule within the Rule Set, Equitrac Professional compares the attributes to each rule
of type until it finds a match. If no match exists, Equitrac Professional applies the action associated with the rule, and
ignores all other rules.
User Workstation
Do job
Is a rule set Yes attributes match Yes Apply rule action
assigned to this any rule
device? definition?
No No
No
Print Actions
Equitrac implements the rule Action only when it locates a match to the rule attributes.
You can select one of seven actions for each network Print rule:
• Hold the document for manual release using Release Station, a control terminal, or an embedded application.
• Redirect and reprice routes the print job to another compatible printer, and recalculates the price using the Price
lists applied to the print queue you select. Update the custom message to let the user know where they can pick up
their print job.
• Send message displays a customized popup message on the user’s desktop or sends an email when they try to print
to the device. The method used depends on the Notification settings in System Manager.
For all actions except Allow and Hold, the user will receive a message if their print job matches a routing Rule Set on
the device they select. You can leave the default messages in place, or click on Custom message to personalize the
message for your users.
NOTE: Force monochrome and Force duplex printing rules have the following characteristics:
• They are only supported on some models using PCL5, PCL6 and PostScript data streams. Please
confirm compatibility in conjunction with your printer drivers before implementing into production.
• There is no message option for Force monochrome and Force duplex. However, it is possible to add a
notification message rule to the rule set. These are the only print actions where a second rule in a rule
set is executed. The criteria of the two rules must match.
• Unlike other rules, where evaluation of a job stops when the criteria for a rule is met, Force
monochrome and Force duplex can be run as a set. When one is chosen, the software looks to see if the
other is active, and if so, runs both. Effectively this creates a Force monochrome/duplex rule.
• They require no additional licenses beyond the standard rules and routing licenses.
• Print jobs are costed based upon the output, not by how they are printed by the user.
NOTE: If the global error notifications are set to use Email, the user will receive the messages via email in addition to
the popup on their desktop. See Selecting Notification Methods on page 68 and Configuring the Mail Server for
Email Notices and Reports on page 70.
When creating custom messages, you can use escape codes as shortcuts for entering certain types of data
automatically. See Escape Codes in Custom Messages on page 268 for more details.
NOTE: The Terminal Services windows service is required to run for custom messages feature to function. You must
start the Terminal Services windows service. By default, this Service is configured to 'Manual'. If the configuration
changes to 'Disabled', custom messages will not pop up.
Although you can use a Redirect rule to direct a document from one device to another, consider carefully the devices
to which you may commonly redirect documents, for use of a compatible Page Description Language such as PCl5/6
or PostScript. Equitrac Professional does not perform job translation on the document in transit. Normally, print job
redirection between devices from the same manufacturer (for example, between different types of HP printers) does
not require any special consideration, because the printers use compatible languages and drivers.
In any case, it is a best practice to test redirection rules to ensure portability of the documents from the source
application to various destination devices. In case of output differences, updating or replacing with a more appropriate
print driver on the client workstation may resolve print errors. The type of client application from which the
document originates is not normally a factor in the cross-device portability of the document itself.
Print Attributes
Equitrac compares the network print job attributes to the defined rule attributes. For a print rule, you can define any
combination of the attributes listed in the table below. A rule is applied only when all selected rule attributes match the
job attributes.
Group Any selected Windows group to which the document’s originating owner belongs.
Note that groups are not searched recursively. To ensure that a rule matches for all intended
users, add all sub-groups to the rule as well.
Size The print driver determines job size in bytes after processing; it will not be the same size as the
file that you create with the printing application.
Title matches A regular expression in the document name, specified by the application sending the print job.
If using server-based printing, where the application name is added to the document title, enter
the application title in the field (i.e. Microsoft Word).
To add multiple titles within a rule, separate each name with a comma.
Day of week The rule will apply only when the network print job is generated. You can use this field to
differentiate weekday vs. weekend print rules.
Time of day The rule will apply only when the print job occurs between specific hours of the day.
Application name The rule will apply to print jobs generated from a specific application only.
This feature is supported only if the Desktop Printing client and the Client Billing option is
installed on the workstation where the job originated.
Device Status Use to redirect print jobs based on device status. The device that you apply the rule to must be a
DME-monitored device.
For example, if the job is offline for a particular period of time, you could route any incoming
print jobs to a different compatible printer.
See Routing Based on Device Status on page 236 for more information.
CAUTION: Create desktop print rules only if you deployed the desktop printing feature within Equitrac Professional
and applied a Desktop Printing license within System Manager.
If Equitrac Professional locates a Rule Set for the selected desktop device, Equitrac evaluates the rules in the set,
starting with the first rule. If a match is found for both rule type and rule attributes, the rule action is applied to the
request.
User Workstation
No No
As an example, you might want to deny users the ability to print to desktop printers when their print job exceeds 50
pages. Or, you could set up a warning message as part of the rule that allows the job to print, but asks the user to
consider printing to a network printer when their jobs exceed 50 pages.
Desktop Actions
Equitrac implements the rule Action only when it locates a match to the desktop print rule attributes.
You can apply one of four actions for each Desktop Print rule:
• Allow sends the document to the user-selected device.
• Deny cancels the request for the user-selected device.
• Send message displays a customized popup message on the user’s desktop when they try to print to a desktop
device. After the user acknowledges the message, the print job will proceed. Click on Custom message to change
the message shown to the user.
• Warn displays a warning to the user when they try to print to a desktop device: "A defined desktop printing rule
limits use to this printer. Press Print to continue printing or Cancel to delete your job." Click on Custom message
to change the message shown to the user.
Desktop Attributes
Equitrac compares the desktop print job attributes to the defined rule attributes. For a desktop print rule, you can
define any combination of the attributes listed in the table below. A rule is applied only when all selected rule
attributes match the job attributes.
Attribute Description
Group Any Windows group to which the document’s originating owner belongs.
Pages The number of print impressions in the job as determined by the page counting method you
select for the printer port.
Select either Greater than or Less than, and type in a page count.
Day of week The rule will apply only when the days of the week selected match the day of the week when the
desktop print job is generated. You can use this field to differentiate weekday vs. weekend print
rules.
Time of day The rule will apply only when the print job occurs between specific hours of the day.
Application name The rule will apply to print jobs generated from a specific application only.
For example, if you define a default rule that denies color printing on local devices, and a second rule that warns users
if they attempt to print a large B&W document to a local printer, Equitrac Professional will check the default first, and,
finding no match for the color document attribute, will check the attributes against the second rule. If the document
exceeds the defined page count limit, the user receives a desktop message.
This diagram depicts the workflow applied when a user sends their print job to a local
desktop printer and the Administrator has set a default desktop print Rule Set.
In the Rules & Routing dialog, right-click on the Desktop Rule Set that you want to set as the default. From the menu,
select Set as default for workstations.
The Rules list will display the notification For workstation devices under the Default Rule Set column.
%n Document name
%o Job owner
%j Job ID
%d Destination device
%a Date
%t Time
Topics:
Control Terminal Overview
Control Terminal Workflow
Creating Configuration Sets
Adding Control Terminals
Configuring the Terminal Database Download
Interval
Managing Control Terminals
PageCounter and PageCounter Professional control terminals are network devices that you install on or near printers,
copiers, fax machines, scanners, or multifunction devices. Control terminals enable users to release print transactions
securely at the printer, or track copy, fax, or scan transactions performed on devices connected to the terminal.
This documentation refers to both PageCounter and PageCounter Professional terminals as control terminals
collectively as they both interact with Equitrac Professional in the same manner. Where a distinction between
PageCounter and PageCounter Professional is required, the documentation will specifically state the terminal type.
For information about configuring PageCounter CDR or NETBuffer devices, see Managing Call Accounting on page
415.
This chapter provides information about adding and configuring control terminals in System Manager.
NOTE: This chapter does not describe configuration for TouchPoint Consoles. Instead, see Configuring TouchPoint
Consoles on page 301.
Central Validation
Control terminals communicate with Equitrac Professional’s device control engine (DCE) to validate transaction data.
Offline Support
Although control terminals use central validation, they also retain validation information to authenticate transaction
data if network connectivity to DCE is lost. Users can still complete their copy, scan, fax and external disbursement
transactions if the transaction is valid according to the most recent validation information.
When network connectivity is restored, the control terminals send the pending transactions to the CAS database.
8 Choose an External input device for this terminal. Control terminals provide a number of data entry tools; see
your control terminal administration guide for details on supported input devices.
9 For PageCounter Professional terminals, enter an Idle hint for the terminal. The hint will show as a callout for the
first field on the terminal.
10 Configure the control terminal operational modes, as described in the following section.
The Copier mode and the Ext. Disbursement mode cannot both be used in the same configuration set. You will
receive an error if you attempt to enable both modes because they use the same interface port.
CAUTION: If you are configuring Copier mode or Ext. Disbursement modes within a configuration set, ensure that
you inspect the ready screen settings before assigning the configuration set to a terminal - in some cases, the ready
screen parameters are not set by default. If this occurs, the terminal will display a static” message.
NOTE: Since you can assign a configuration set to multiple terminals, the modes you enable are applied to all
terminals you associate with the configuration set. Therefore, any changes to a configuration set will be sent to all
terminals associated with it.
The following table lists the available mode types for control terminals:
Copier The terminal’s photocopy mode interfaces with copier devices by means of a Copy Control Cable. You
can only enable one copier mode per configuration set.
Fax The Fax mode interfaces with fax machines. You can only enable one fax mode per configuration set. if
you require a second fax interface, enable the Fax2 mode.
If you enable Fax mode, you must also enable Local fax code.
Fax2 The Fax2 mode interfaces with a second fax machine. You can only enable one Fax2 mode per
configuration set.
If you enable Fax2 mode, you must also enable Local fax code.
Disbursement Disbursement mode enables users to enter disbursements. You can define up to six disbursement
modes in a singe terminal configuration. Prior to adding disbursement modes to a configuration set,
you must define disbursement types. For information, see Define Disbursement Types on page
391.
You can configure each disbursement mode to show a single disbursement type, or all disbursement
types.
Ext. Disbursement The External Disbursement mode interfaces with an external device such as a postage meter. Prior to
adding this mode to a configuration set, you must define disbursement types. For information, see
Define Disbursement Types on page 391.
The terminal interfaces with the external disbursement device through the use of a power interrupt
cable. Therefore you can only define one external disbursement mode per terminal
Local fax code Local fax codes must be used in place of full validation data when validation codes containing alpha-
numeric characters cannot be entered using the standard fax machine keypad.
The local fax code mode enables the user to enter complete validation information at the control
terminal. Once entered, the terminal generates a random 6-digit fax code number to use at the fax
machine when sending a fax. By default, the lifespan of this code is 24 hours.
The control terminal retrieves the validation data corresponding to the fax code used, and instructs
the fax machine to send the transmission to the phone number dialed. Once complete, the control
terminal sends all the transaction data to CAS.
If you enable the Local fax code mode, you must also enable either a Fax or Fax2 mode.
Equitrac Professional defaults a Broadcast code mode automatically, similar to the local fax code
mode, except that it generates a 1-digit fax code number. By default the lifespan of this code is 30
minutes.
NOTE: By default, System Manager assigns the first mode to Copier and leaves the remaining tabs unassigned.
Mode tab names for unassigned modes display as Mode <#>, where <#> indicates the tab number (1-6
respectively). Changing the mode type in a tab changes the displayed name for the tab.
CAUTION: Do not assign the first tab to either the Fax or Fax2 mode as they do not have configurable fields. Assign
the first tab to the Local fax code mode if you plan on using the terminal for a dedicated fax machine only.
3 Change or assign a terminal mode to each of the six available terminal mode tabs, by choosing an option from the
Mode type drop list. You can disable existing terminal modes, by selecting Undefined from the drop list.
NOTE: The Mode type drop list only displays modes that are not already assigned and modes that can be assigned
to more than one tab.
4 Change the Mode Name from the default if you require a more descriptive name or if you have two disbursement
modes and want to differentiate them. This mode name will display in brackets beside the mode type when you
configure the control terminal. See Configuring Control Terminal Mode Options on page 293 for details.
5 Select the History Field level from the drop list. The history field defines the hierarchical level at which the
terminal allows the use of the History key:
• Selecting None disables the use of the History key.
• Selecting User Code enables the use of the History key after a user enters a valid user code. Pressing the
History key displays all historical transactions for the specified user regardless of client or matter codes.
• Selecting Client enables the use of the History key only after a user enters both a valid user code and a valid
client code. Pressing the History key on the terminal displays all historical transactions for the specified user-
client combination, regardless of matter code.
• Selecting Matter enables the use of the History key only after a user enters a valid user code, client code and
matter code. Pressing the History key displays all historical transactions for the specified user-client-matter
combination.
6 Select the SpeedCode Key Field option from the drop list. The SpeedCode key option determines whether
SpeedCode keys are set by user code or are defined globally.
• Selecting User Code enables any user to configure their own SpeedCode keys on the terminal.
• Selecting Global enables the administrator to set global SpeedCode keys to be used by all users of the
terminal. If this option is selected, users are no longer able to configure their own SpeedCode Keys on the
terminal.
7 For Disbursement modes only, choose the Disbursement type from the drop list. This drop list only displays if
the current mode is either disbursement or ext. disbursement and contains a selection of user-defined
disbursement types. See Define Disbursement Types on page 391 for details.
If you select All as the disbursement type, Equitrac Professional inserts an additional field prompt to the terminal
configuration. This field is configurable, and is represented by a new tab called Disb. Type.
NOTE: By default, the Disb. Type field is pre-configured with SmartPrompts that are not editable; see Control
Terminal SmartPrompts on page 281 for details.
8 For Local Fax Code mode only, choose the Phone # position from the drop list. The phone number position
controls the order in which the user must enter the fax code and the phone number for a fax transaction.
• Selecting Last informs the terminal that the user must enter the fax code first followed by an asterisk, and then
the phone number.
• Selecting First informs the terminal that the user must enter the phone number followed by an asterisk, and
then the fax code.
If the user enters the fax code and phone number in the wrong order, the transmission will fail as the terminal is
expecting the two numbers in the opposite order.
CAUTION: If you change the phone number position while editing a configuration set, you can no longer use fax
codes generated by terminals using the previous configuration set at the fax machine. Fax codes provided by
terminals using the previous configuration set were generated expecting the fax code and fax number fields in the
reverse order. If your terminals use custom configuration, you must also update their configuration so they
recognize the change in the phone number position.
9 Click the Ready Screens button to open the Ready screen dialog and configure fields shown on the terminal when
the transaction is processing. Some Modes will have pre-populated ready screen fields, others won’t.
Custom Parameters
Clicking the Custom parameters button enables you to create or over-write custom parameters on the terminal.
CAUTION: When creating custom parameters, you must use specific terminal registry values. Creating incorrectly
constructed custom parameters can cause your terminal to stop functioning as intended. It is strongly
recommended that you only create custom parameters under the direction of a qualified Equitrac technician.
NOTE: Depending on your terminal firmware version, you may find Equitrac Professional does not accept custom
parameters unless you insert a carriage return (press Enter) at the end of each entry, or at the very least after the last
field entry.
NOTE: By default, System Manager maps the first fields under each mode tab as UserCode, Client, Matter, and
Description. However, these fields correspond to validation fields 3, 2, 1, and 4 respectively and may have different
names if you defined different validation fields during the installation and initial configuration process. If you did not
change or add any field mappings, the first four tabs display the defaults and the remaining four display as Field 5
through Field 8 respectively. See Configuring Equitrac Professional Fields on page 83.
Field 1 Matter 3
Field 2 Client 2
Field 3 UserCode 1
Field 4 Description 4
Field 5 Field 5 5
Field 6 Field 6 6
Field 7 Field 7 7
Field 8 Field 8 8
NOTE: The Matter, Client, UserCode, and [field 4] fields display in reverse order in the configuration set dialog to
match their order on the terminal.
To configure control terminal fields, complete the following for each field within each enabled mode of the
configuration set:
1 Set the field state attribute from the drop list. The following table describes each field state option:
Not Visible Not Visible fields are not presented to the user, but you can define an auto-filled value to
send to CAS when transactions are generated. If you select Not Visible, the Auto-Fill (if
non-visible) field becomes the only active field. Enter a default auto-fill value. See Field
String Syntax on page 471 for details on how to enter a value in this field.
Disabled Disabled fields do not show up on the terminal and are not filled in with any default values
in generated transactions.
On NonBillable Only If you select On NonBillable Only, the field will display on the terminal after the user enters a
non-billable matter code (or client code, if you do not use matter codes). See Managing
Validation Data on page 79 for details on configuring Client and Matter Validation codes.
NOTE: You can only configure one prompt field to be visible On NonBillable Only for each terminal operation
mode. Once you assign this value to a field, it is no longer listed as a visibility option for other fields.
2 For Visible fields only, you can change the field Prompt for the terminal. Enter a short descriptive label for the
field. The field prompt displays on the terminal as the field label and informs the user what data is expected. For
On NonBillable Only fields, you can enter a prompt similar to Why Non-Billable or Reason Non-
Billable.
NOTE: Changing the field prompt does not change the displayed name for the tab.
3 Define the Validation mode as Open, Hard, or Hard with verify by choosing an option from the drop list.
The following table lists and describes the three validation modes:
Open Field entry must conform to the syntax defined for the field. Entries are not checked
against a validation table.
Hard Field entry must conform to the syntax defined for the field. Entries are checked against a
validation table.
Hard with Verify This validation mode is the same as Hard, but in addition, presents the user with a dialog
asking them to confirm the entry.
NOTE: For NonBillable Only fields, the validation mode must be set to Open.
4 Define a Max length for the field. Maximum length controls the maximum number of characters that can be
entered.
5 Select the Zero Fill option to automatically append a string of zeros to the beginning the user entry, up to the
maximum field length, as specified in the Max length attribute.
Do not select the zero fill option for On NonBillable Only fields.
6 Define the type of Syntax permissible for the field (alpha, numeric, or alpha-numeric). By default, the field syntax
is alpha-numeric.
For On NonBillable Only fields, define the syntax as 1-16LT (A descriptive text field of any length with any
characters, such as commas and slashes, being valid). See Field String Syntax on page 471 for full details on field
syntax.
7 Choose a Search Mode for this field. Your search mode selection determines the terminal search and scan
behavior for this field. See your terminal documentation for details. The following table lists and describes the
available search mode options:
First Key Code Search by code using the first characters entered.
First Key Description Search by description using the first characters entered.
Manual Code Press Search on the terminal to search by code. If you enter a partial code, the search
attempts to match the entered characters.
Manual Description Press Search on the terminal to search by description. If you enter a partial description,
the search attempts to match the entered characters.
NOTE: For NonBillable Only fields, you must disable Search Mode.
8 Select the Speed Code Enabled option to enable the Speed Code key. This feature is only available on the
PageCounter Professional control terminal. Do not select the speed code enabled option for On NonBillable Only
fields.
NOTE: The Speed Code Enabled option is not available in the UserCode field tab.
9 Select the Recall Last Value option to enable the user to see previously entries for this field. Do not select the recall
last value option for On NonBillable Only fields.
NOTE: The Recall Last Value option is not available in the UserCode field tab.
10 Select the Show Code Description option to enable the user to view validated field descriptions for this field. Do
not select the show code description option for On NonBillable Only fields.
11 Select the Show Code As Asterisks option to enable the terminal to display entered data as asterisks. Do not select
the show code as asterisks option for On NonBillable Only fields.
12 Select the Auto Enter option to enable the terminal to jump to the next field if the maximum number of characters
for a given field has been reached.
13 For Not Visible fields, enter an Auto-fill value (if non-visible) if you want a default value for this field to be sent
to CAS with each transaction. This is the only configurable attribute for, and is only available to, Not Visible fields.
14 For Visible fields, enter an Auto-fill value (if visible) if you want a default value for the field to appear during
transactions. The value you enter here will auto-populate in the field but will be modifiable during a transaction.
This attribute is only available to Visible fields.
15 Click the SmartPrompts button to open the Conditional Prompting dialog and configure any required
SmartPrompts. See Control Terminal SmartPrompts on page 281 for details.
For On NonBillable Only fields, SmartPrompt #1 is pre-configured and is not editable. You can enter up to 3
additional SmartPrompts.
NOTE: When configuring terminal SmartPrompts, all field numbers must be entered using a two digit format.
Therefore field 1 must be entered as field 01.
Follow these steps to configure the control terminal field SmartPrompts for a field in a terminal mode:
1 Click the SmartPrompts button to open the Conditional Prompting dialog.
2 Enter up to four control terminal SmartPrompts. In each case, if a transaction meets the condition you specify, the
terminal performs the specified action; otherwise it performs the associated anti-action.
3 Use the information in the following table to enter a Condition string for each SmartPrompt you create:
Example
Command Description Format
Command Description
V Validation table match V{FIELD#}{TABLE#} V010 Check for Field 1 entry in Table 0.
on specific field
Example
Command Description Format
Command Description
Y Entry in specific field is Y{FIELD#} Y02 Entry in Field 2 has been Verified
verified as yes at as Yes.
Verify Y/N prompt
M Validation Table Match M{FIELD#}{TABLE#}{ M0302~ Check for combined Field 2 and 3
on specific combined DELIMITER} in Table 2.
fields
- Opposite command Use before a -V012 Check that Field 1 entry is not
(Dash or minus sign) specific command found in Table 2.
to indicate the
opposite of a
condition
NOTE: The maximum length for a condition string is 37 bytes (37 characters). Therefore, you can use the above
commands as necessary to build a condition, as long as the total length of the characters comprising the string does
not exceed 37 bytes (including all commands, parameters, and separators).
4 Use the information in the following table to develop Action and Anti-Action strings for each SmartPrompt you
create.
Example
Command Description Format
Command Description
DF Disable specific field DF{field#} DF03 Field 3 is disabled; data entry is not
required.
R Replace specific field R{field#}{char string} R03NONBIL Replace the contents of Field 3
entry with character LABLE with the entry NONBILLABLE.
string (up to 16
characters)
Example
Command Description Format
Command Description
LF Look up specific field LF{destfld#}{srcefld#} LF03025 Look up the entry from Field 2 in
entry (source) in {table#} Table 5; if found, insert the entry’s
specific table; insert the associated description into Field 3
associated description
in another field
(destination)
, Separator character Use between EF03,R03NO Enable Field 3 and place the
(Comma) individual NBILLABLE character string NONBILLABLE in
commands to Field 3
specify multiple
actions or anti-
actions
NOTE: The maximum length for an action/anti-action string is 18 bytes (18 characters). Therefore, you can use the
above commands as necessary to build an action or anti-action, as long the total length of the string does not
exceed 18 bytes (including all commands, parameters, and separators).
NOTE: For NonBillable Only fields, SmartPrompt #1 is pre-configured and is not editable. You can enter up to 3
additional SmartPrompts.
5 Click OK.
Sample SmartPrompts
The following examples show how you can configure the four SmartPrompts in the Conditional Prompting dialog:
SmartPrompt #1: If the code 1234 is entered in Field 1, disable all subsequent fields (field 2 and field 3) and go
directly to the Ready State. Otherwise, leave fields 2 and 3 enabled.
S01"1"2"3"4 DF02,DF03 -
SmartPrompt #2: If the user enters a 5-digit code starting with a 1 in Field 2 and the 5-digit code appears in Table 2,
enable security on Field 3 and place the value CONFIDENTIAL in Field 6 of the transaction record, otherwise disable
security on Field 3 and place the value PUBLIC in Field 6.
SmartPrompt #3: If the code entered in Field 1 is verified as Yes, enable Status Flag 1 (checked in next SmartPrompt
as additional criteria), otherwise disable Flag 1 if it is currently enabled.
Y01 SF01 -
SmartPrompt #4: If Flag 1 is enabled (by the criteria specified in the previous SmartPrompt), enable Field 3 for
additional data entry.
F01 EF03 -
2 Click Add to open the Add new PageCounter/Pro configuration set dialog.
5 In the Fax parameters section, you can change the Phone number syntax value to change the valid phone number
string format. See Field String Syntax on page 471 for details.
6 In the Dial parameters section, you can modify the Syntax and Dial String values for each of the four phone call
types when using fax control terminals. Each phone call type must be defined here to enables the terminals to
recognize field entries as telephone numbers according to the character syntax entered in that field:
• Local: The syntax for a local call, format 555-1212 would be 7N (You cannot enter dashes at the terminal)
• Local Long Distance: The syntax for a local long distance call, format 1-555-1212 would be “17N (the 1 is a
specific positioned character; you cannot enter dashes at the terminal)
• Long Distance: The syntax for a long distance call format 1-305-555-1212 would be “110N (the 1 is a specific
positioned character; you cannot enter dashes at the terminal)
• International: The syntax for an international call format 011-813-3818-4608 would be “0”1”16-13N (011 is
actually three specific positioned characters; the dashes are not entered at terminals).
See Fax Dial Strings on page 286 for further details on dial string syntax.
7 Select the Record incoming faxes option to record incoming faxes.
8 Click OK to save your settings and close the Fax terminal configuration set dialog.
A Appc... Substitute the specified string of characters into the dial buffer, replacing an equal number of
c characters starting at the specified position.
pp — position to start the replacement (01-16 ASCII).
c…c — the characters to substitute; 1-16 ASCII characters (0-9, #, *, A, B, C, or D).
C C Enter the Connect Mode and wait for fax progress messages. This command terminates all
dialing sequences.
F F# Move the specified field data into the dial buffer without modification.
# — the number of the data-entry field (1-8 ASCII).
I Ippc Insert a single character into the dial buffer at a specific position.
pp — position to insert the character (01-16 ASCII).
c — the character to insert.
J Jt Flash the phone line for the specified number of seconds to clear the line.
t — flash time in ASCII-coded decimal seconds (1-255).
M Mc Remove all occurrences of the specified character from the dial buffer.
c — character to remove (one character only).
N NSnn Remove the specified number of consecutive characters from either the start or the end of the
or dial buffer.
Nenn
S — start of buffer.
E = end of buffer.
nn — number of characters to remove (01-16 ASCII).
In the example above, J2 flashes the phone line for 2 seconds, D waits for a dial tone, F8 loads field 8 into the dial
buffer, E sends the contents of the dial buffer, C(cr) connects to the fax machine on the line.
In the above, J2 flashes the phone line for 2 seconds, D waits for a dial tone, K8 dials an 8, D waits for a dial tone again,
F2 loads field 2 into the buffer, G* replaces the dash (-) with an asterisk (*), E sends the buffer, X1 pauses for 1 second,
F8 loads field 8 into the buffer, E sends the buffer, C(cr) connects to the fax machine on the line.
NOTE: Phone speed codes can be from one to three digits long, and must be comprised of numeric characters only.
2 Click <Add...> to add a blank phone speed code row in the grid.
3 In the new row, do the following:
a Enter a unique Name for the phone speed code. The name cannot contain spaces.
b Enter a unique Code, up to three numeric characters long, for use on the control terminal or fax machine.
c Enter the Phone number that the code will dial once entered. The phone number must be numeric, with no
spaces, dots, or hyphens.
4 Click OK to close the dialog.
3 Configure the terminal as instructed in either the PageCounter Administration Guide or the PageCounter
Professional Administration Guide. When prompted for a control system IP, use the IP address of the DCE host.
Ensure that you provide the terminal an appropriate name.
4 Connect the control terminal to the Network.
DCE registers the terminal under its configured name. The terminal appears as unassigned in System Manager
even if it is connected to a device. To assign the terminal to a device, see Assigning a Control Terminal to a Device
on page 296.
5 In System Manager, click the System > Devices link to show the list of current devices in System Manager.
6 Click the name link of the new device to open its Control Terminal dialog.
12 Edit the Validation Entry Timeout interval and Hold Button Time interval as necessary.
13 Click the Pricing button to apply a default price list or primary and optional secondary price list to the control
terminal for copy transactions. See Configuring Price Lists on page 143 for details.
NOTE: Select default to use the price list defined for the device. Selecting a control terminal price list overrides the
device price list.
14 Select the Modes you want to support on this terminal. Modes that are undefined in the selected configuration set
are not available. See Configuring Control Terminal Mode Options on page 293 for details on defining available
modes for a configuration set.
15 Clicking the Copier Options, Fax Options, Fax2 Options and Scan device options buttons corresponding to the
modes you selected in the previous step, enables you to further configure mode options for this terminal. See
Configuring Control Terminal Mode Options on page 293 for full instructions.
16 Click OK to close the Control Terminal dialog and save these settings.
System Manager sends the configuration settings to the terminal.
17 Click Close to exit the Terminal configuration sets dialog.
3 De-select the Disable terminal option if you want the terminal to be active after you have completed this
procedure.
10 Edit the Validation Entry Timeout interval and Hold Button Time interval as necessary.
11 Click the Pricing button to apply a default price list or primary and optional secondary price list to the control
terminal for copy transactions. See Configuring Price Lists on page 143 for details.
NOTE: Select default to use the price list defined for the device. Selecting a control terminal price list overrides the
device price list.
12 Select the Modes you want to support on this terminal. Modes that are undefined in the selected configuration set
are not available. See Configuring Control Terminal Mode Options on page 293 for details on defining available
modes for a configuration set.
13 Clicking the Copier options, Fax options, Fax2 options and Scan device options buttons corresponding to the
modes you selected in the previous step, enables you to further configure mode options for this terminal. See
Configuring Control Terminal Mode Options on page 293 for full instructions.
14 Click OK to close the Control Terminal dialog and save these settings.
15 Attach the control terminal to the device you want to track. Attaching the terminal to a device may require the
assistance of a certified device technician. See the PageCounter Administration Guide or the PageCounter
Professional Administration Guide as appropriate for further information on connecting terminals to devices.
The above step is optional, as you may want to use this terminal as a stand alone device.
16 Connect the terminal’s power supply.
17 Configure the terminal as instructed in either the PageCounter Administration Guide or the PageCounter
Professional Administration Guide. When prompted for a control system IP, use the IP address of the DCE host.
When prompted for a terminal name, use the same name you entered in the Control terminal dialog within
System Manager.
18 Connect the control terminal to the Network.
DCE registers the device and System Manager sends the configuration settings to the terminal.
NOTE: Mode option buttons are disabled for inactive terminal modes. See Configuring Control Terminal Mode
Options on page 293 for details on active terminal modes.
2 Select the Copier Type from the drop list of supported copiers.
3 Adjust the value in the Copier Idle Timeout field, if needed. The default is 150 seconds.
The copier idle timeout interval defines the length of time the terminal will wait between keystrokes, before
returning to the main screen.
4 Adjust the Min. Copy Pulse on time, Min Copy Pulse off time, Max Copy Pulse, and Release Time Multiplier
values in the Copy Pulse Detection section, if required. Consult your device’s documentation for appropriate
values.
If required, click the Reset to Defaults button to restore the System Manager defaults.
5 Click OK.
1 From within the Control terminal dialog, click either the Fax 1 Options or Fax 2 Options button to open the Fax
1 mode options or Fax 2 mode options dialog.
NOTE: Both fax option dialogs are the same, however, you can assign different Fax configuration sets for each here.
2 Select a Configuration Set from the drop list to select the fax configuration set you want to associate to the current
fax mode. Fax configuration sets contain the dial string settings. See Creating a Fax Configuration Set on page
284 for details.
3 Options in the Line Parameters section control telephone line parameters. The list below briefly describes each
parameter.
CAUTION: Line Parameters values should only be changed by, or under the direction of, an Equitrac representative.
Click the Reset to Defaults button to restore the System Manager defaults if you inadvertently changed any of the
default values.
• DTMF Tx Db level: Adjusts the dual tone multi-frequency transaction decibel level.
• DTMF Tx Timing (ms): Adjusts the dual tone multi-frequency transaction timing for sent faxes. The value is
in milliseconds.
• DTMF Rx Timing (ms): Adjusts the dual tone multi-frequency transaction timing for received faxes. The
value is in milliseconds.
• Pulse Dialing Parameters (ms): Adjusts pulse line signal timing. The value is in milliseconds.
• V.34 Fax Speaker Volume: Adjusts the fax speaker volume.
• V.34 Fax: Specifies this configuration as relating to a V.34 fax machine only.
4 Select the Use External Fax Controller option if you are using an external fax controller.
An external fax controller is an external fax modem that connects to the serial port on a PageCounter Professional
terminal. It is a device that extends the capability of PageCounter Professional terminals that do not have their own
internal fax modem. See your control terminal documentation for instructions on configuring a control terminal
to use an external fax controller.
5 Click OK to save your changes and close the Fax 1 mode options or Fax 2 mode options dialog.
3 In the Scan device options dialog, define the following parameters as determined by your choice of scan device
type in the first field:
a Select the Scan device type. Specify Xerox or eCopy v2.
NOTE: When selecting eCopy versions in Equitrac device configuration dialogs, you are actually specifying the Cost
Recovery Connector protocol version.
b Specify your User lookup method. For Xerox solutions, define this option as By User Code.
c Specify the eCopy Client IP address (eCopy v2 only).
d Specify the Server IP address. This is the address of the ShareScan OP or Xerox CenterWare server.
e Specify the device Port (eCopy v2 only). This defaults to 9325, and must mirror the port defined on the eCopy
ShareScan OP server for communication to the terminal. If it is different on the ShareScan OP server, makes
sure the new port number is reflected in this configuration dialog.
f Specify the Activity field separator for transaction records as a comma (eCopy v2 only).
4 Click OK.
3 Click the Current tasks > Assign control terminal link to open the Assign Control Terminal to device dialog.
You can also use the drag + drop method to drag an unassigned control terminal to the destination MFP.
4 From the list of registered devices, select a device to which you want to assign this control terminal.
5 Click OK to close the dialog and assign the terminal.
6 Verify that the right pane reflects the new control terminal association. The control terminal should be listed
under the device with which it is now associated.
2 In the Offline database generation section, select either Use update intervals or Use time of day as the type of
interval you require.
3 Depending on the interval type you selected, set the time interval using one of the following methods:
• For Use update intervals: Change the time (in minutes) in the Update frequency field from the default 15
minutes, if required.
—Or—
• For Use time of day: Change the time of day in the Update time field, and a time period (in minutes) in the
Retry for field defining how long the terminals will continue to attempt to download the database from DCE if
a connection is not available.
4 In the Download behavior section, change the Maximum number of concurrent database downloads from the
default number 3, if required.
However, consider the effects of editing multiple devices with different configurations prior to making any changes to
multiple control terminals:
• Fields that must differ across all devices, such as Name are not editable.
• Empty fields across all devices, display as empty fields.
• Fields configured with different values across the selected devices, appear as empty fields.
• checkboxes with different options selected across the selected devices appear as deselected options.
• Options (checkboxes or drop list) appear as default values, or deselected options.
• If a field value is identical across all devices, the field will show the matching value (whether a checkbox, text value,
or drop list selection).
• If a price list is not applied across all devices, the price drop list box displays the <Default> value.
CAUTION: As a precaution, check the current configuration across all devices prior to changing configuration
settings. Entering a value or selecting an option will assign the value to all the selected devices overwriting exiting
values.
Topics:
TouchPoint Console Overview
Configuration Workflow
Planning General TPC Configuration Sets
Planning TPC Fax Configuration Sets
Setting Global TPC Options
Assigning Configuration Sets to TPC
Assigning TPC to a Physical Device
Manually Adding a TPC to the Devices List
Replacing a PageCounter with a TPC
About Card Reader Support
Determining Card Data Positions
Determining HID Decoding Values
Decoding HID Cards
Checking TPC Status Remotely
TouchPoint Consoles (TPC) are network devices that you install on or near printers, copiers, fax machines, scanners,
or multi-function products (MFP). These touch-enabled consoles control access to output MFPs and their
functionality.
Each TPC can be configured to track the types of transactions users can perform (such as copying, scanning, faxing,
printing, and disbursements). When configuring TPCs, you can create configuration sets that assign similar functions
to groups of TPCs. These configuration sets reduce configuration tasks, and allow you to assign functions once and
then apply a set to each TPC.
This chapter provides information about adding and configuring TouchPoint Consoles in System Manager.
CAUTION: Ensure that each TPC is updated with the applicable firmware version
from the Equitrac Partner Portal at http://partners.equitrac.com. Look under Tech
Support, then click Software Downloads and locate the TouchPoint subheading on the page. For complete
instructions on upgrading TPC firmware, see the TouchPoint Console Installation & Setup Guide.
User Workflow
Users must first authenticate at the TPC before they can proceed with their transactions. After selecting the billing
data (such as client and matter) to charge their transactions against, they can copy, scan, fax or enter disbursements (if
TPC is configured to allow these activities). For print jobs, users must authenticate only – because the user selected
billing data in the print popup on their desktop computer, the user does not need to select this data again and can
continue to the Print Release options if their authentication is accepted.
Administrators can use configuration sets to control the activities and capabilities available on each TPC. For full
details, see Planning General TPC Configuration Sets on page 304 and Planning TPC Fax Configuration Sets on
page 311.
Configuration Workflow
If you are adding TPCs to the Equitrac Professional suite follow the workflow outlined below. If you are upgrading
existing an PageCounter to TouchPoint Consoles, see Replacing a PageCounter with a TPC on page 326.
CAUTION: This workflow assumes that you have already upgraded each TPC to the applicable firmware version and
that TPCs are communicating with the correct DCE server. For initial configuration and firmware update instructions,
see the TouchPoint Console Installation & Setup Guide.
13 TPCs
Configuration Set #1 = Copy/
scan
Print
2 TPCs
Configuration Set #2 = Copy/
scan
Print
Color
prompt
3 TPCs
Configuration Set #3 = Copy/
scan
Print Disb.
1 TPC
Configuration Set #4 = Fax
Only
1 TPC
Configuration Set #5 = Disb.
Only
3 In the Device/features access section, select the SDR login behavior from the Secure document release drop-
down list:
• Select Disable Release jobs to prevent users from releasing held print jobs at the TPC.
• Select Release all jobs on login to release all of the user’s held jobs to print when the user logs into the TPC.
• Select Prompt and select to release jobs to allow users to selectively release their held jobs to print.
• On History
The History list includes the most recent billing selections for the logged-in user.
When Auto advance is enabled and a user selects an entry from the History list, TPC automatically presses the
Start key and proceeds to the Ready screen. If the entry’s billing data is invalid, the user will receive an error
message.
• On Favorites
Favorites list
Favorites are user-configured short-cuts for codes that are used often. The billing codes appear in the Favorites list
and users can select a favorite with one touch.
When Auto advance is enabled and a user selects a favorite, TPC moves users to the Ready screen immediately
after they select an item from the Favorites list. If the billing information saved with the favorite is not valid, users
receive an error message.
Session Time-outs
TPC will log users out after set periods of inactivity. If the user leaves the TPC but has forgotten to log out, TPC will
automatically log the user out of the TPC session and lock the controlled MFP again.
Session time-out settings log the current user out of TPC when there is user inactivity or MFP inactivity. As an
important part in your firm’s security policy, you can configure the following session time-out settings:
User inactivity (seconds) If the user logs in and advances on the TPC to where the MFP is no
longer in Ready mode, and then the user stops using the TPC, the user is
logged off the TPC automatically and the controlled MFP is locked.
Hold/Copier inactivity If the controlled copier, or MFP, connected to the TPC is inactive for this
(seconds) set period of time (default 180 seconds), the user is logged off TPC
automatically and the controlled MFP is locked.
If the user presses Hold, the user inactivity countdown is reset to the
default value. The user can press Hold again at any time to reset the
logout countdown until they are ready to use the controlled MFP.
If the default time counts down and the controlled MFP remains
inactive, the user is logged off the TPC and the controlled MFP is locked.
Enable disbursements No
NOTE: "Prompt for color copy" applies only to copy transactions. Scans do not use this function.
4 Enter a unique name for this configuration set, and include a description that might help you identify the
configuration set contents when you apply the set.
Only the name will appear in the Device dialog, but you can use the description to identify the configuration set
contents from the configuration set list if needed.
5 If you want to make this configuration set the default set, check Default configuration set.
Only one set can be the default set. When a new TPC is added to the system, it will use the default configuration
set until you change it.
6 Choose the combination of options that will make up this configuration set, then press OK to save the set. For
details on the options that appear in this dialog, see these topics:
• User Interface Settings on page 304
• MFP Features and Access on page 305
• Auto advance Settings on page 307
• Session Time-outs on page 308
CAUTION: The default TPC fax configuration sets use settings for telephone systems in the United States and
Canada. If you are using fax-telephone systems in other countries, pay close attention to the dial parameters and any
other country-specific dialing settings.
Dial parameters
Dial parameters establish the valid phone number string format used by the fax device for local, long distance, local
long distance and international dialing. For details on how to set this syntax correctly, see Field String Syntax on page
471.
Fax dial sequences are different than telephone syntaxes, although they are related. The syntax of a phone number
indicates what type of call it is (such as local, long distance, local-long distance or international). Depending on the
type of call, the corresponding dialing sequence includes the phone number and any other commands or information
required to place an outgoing call.
Using any required combination of the dialing sequence commands provided in the following table, you can build the
dialing sequences for each of four types of dial parameters. As shown in the examples that follow the table, each
command is separated from the next by a comma.
A Appc... Substitute the specified string of characters into the dial buffer, replacing an equal
c number of characters starting at the specified position.
pp — position to start the replacement (01-16 ASCII).
c…c — the characters to substitute; 1-16 ASCII characters (0-9, #, *, A, B, C, or D).
C C Enter the Connect Mode and wait for fax progress messages. This command
terminates all dialing sequences.
F F# Move the specified field data into the dial buffer without modification.
# — the number of the data-entry field (1-8 ASCII).
I Ippc Insert a single character into the dial buffer at a specific position.
pp — position to insert the character (01-16 ASCII).
c — the character to insert.
J Jt Flash the phone line for the specified number of seconds to clear the line.
t — flash time in ASCII-coded decimal seconds (1-255).
M Mc Remove all occurrences of the specified character from the dial buffer.
c — character to remove (one character only).
N NSnn Remove the specified number of consecutive characters from either the start or the
or end of the dial buffer.
Nenn
S — start of buffer.
E = end of buffer.
nn — number of characters to remove (01-16 ASCII).
In the example above, J2 flashes the phone line for 2 seconds, D waits for a dial tone, F8 loads field 8 into the dial
buffer, E sends the contents of the dial buffer, C connects to the fax machine on the line.
As an other example, you might want to transmit a fax long distance on a phone switch that requires entry of a
client-matter number. To do so, you would need to:
1 Flash the phone line
2 Wait for a dial tone
3 Dial an “8”
4 Wait for a dial tone
5 Enter the client-matter fax number found in Field 2 with an asterisk (*) between the client code and the matter
code
6 Pause for one second
7 Dial a “1”
8 Dial the phone number
9 Then connect to the receiving location
The corresponding string of dialing sequence commands is as follows:
J2,D,K8,D,F2,K,E,X1,K1,F8,E,C
In the above, J2 flashes the phone line for two seconds, D waits for a dial tone, K8 dials an “8,” D waits for a dial tone
again, F2 loads field “2” into the buffer, G* replaces the dash (-) with an asterisk (*), E sends the buffer, X1 pauses for
one second, F8 loads field 8 into the buffer, E sends the buffer, C connects to the fax machine on the line.
Fax interactions
Under the Fax interactions section, you can define the prompt style, or format, that users must conform to when
keying in a fax code.
Prompt style
At the “Prompt style” setting, select from the drop-down list a popup style that combines user, client and matter codes.
NOTE: We recommend creating a new prompt style that includes the user code to ensure that all transactions are
assigned to a corresponding user. If you do not include a user code in the prompt style, all transactions will be
assigned to a default user or you may receive an exception.
If you click OK, the required phone number position is changed, but be sure to let users know the correct way to enter
the fax numbers.
Unattended faxes
Under Unattended faxes, you can set a time period during which faxes will be transmitted without needing
validation. Any faxes sent between the start and stop times will not require user, client, matter or other validation
codes.
Advanced Options
CAUTION: Advanced fax settings should only be changed with the help of Equitrac Support for non-standard phone
systems.
Reset to defaults
If you want to reset the advanced fax setting options, click Reset to defaults. This setting applies only to the default
installation settings.
4 Enter a name for the new configuration set and enter a description if necessary.
5 Define the setting for Dial parameters, Phone number position and Unattended faxes, and select or clear the
Record incoming faxes option. For details on these dialog options, see Planning TPC Fax Configuration Sets on
page 311.
CAUTION: If you decide to change the position of a phone number, you must manually update the fax dial strings.
The phone number field position (“F” values in the strings) will need to be updated to reflect changes based on the
popup style.
NOTE: Refer to the table below for how to update the dial string according to phone number position and prompt
style. * refers to the default settings.
For more information on fax dial strings, see Fax Dial Strings on page 286.
6 Click Advanced if you need to adjust further options.
7 Click OK to save the new configuration set.
NOTE: The following TouchPoint Console global options also control offline support for authentication in Equitrac
Embedded for Canon MEAP and Equitrac Embedded for Ricoh ESA:
• Maximum users to cache on device
• Maximum days to keep in cache
When configuring these global options, consider that these settings will apply to TPC and to these embedded
applications.
2 In the global options dialog, set the following options if needed:
Option Description
Login access mode • If the TPC cannot contact the DCE server, the TPC operates in offline mode. This option
determines if users are allowed to log in while in offline mode.
• Options are:
• Deny: users cannot log in while TPC is offline from the DCE server.
• Cached Users Only: users can log in to the TPC if they have logged into this TPC at least
once previously (causing their login credentials to be cached on the TPC).
• Allow All: users can enter their validation data to log in, but a validation check will not
occur. Transactions will be logged to the validation data, but if the data is incorrect, an
exception will be created. This is the default option.
Maximum users to cache • If Login Access is set to Cached Users Only or Allow All, set the number of users whose
validation data will be kept in cache on each TPC.
• The default is 500 users.
Option Description
Maximum days to keep in • If Login Access is set to Cached Users Only or Allow All, set the number of days to hold the
cache user validation data on the local TPC cache.
• The default is 30 days. If a user has not logged in within the past 30 days, their validation
data will removed from the local TPC cache. If set to Cached Users Only and the TPC is
offline from the DCE server, this user will not be able to log in.
Broadcast code time-out • Determines the expiry time for a broadcast fax code. The default value is 30 minutes.
• A broadcast code is a randomly generated one-digit code that is associated with a specific
user-client-matter code combination for this set period of time. A broadcast code allows
the user to enter a series of fax numbers in the connected fax machine, as opposed to just
one fax destination. After generating the code, the users has this set period of time to
enter it at a fax machine.
• The time-out value must be short because it is a one-digit code. These codes must be
unique while they are ‘alive’ and each TPC can therefore have only nine “live” broadcast
codes (1 through 9) across all users at any time.
• If you change the default value, inform users of the new time-out.
Local code time-out • Determines the expiry time for users’ local fax codes. The default value is 24 hours.
• A local code is a randomly generated three-digit number (between 100 and 799) that is
stored on the TPC and associated with a logged-in user’s specific billing code
combination for a specified period of time. If not used within this period of time on the
connected fax device, a local code expires and can no longer be used.
• If you change the default value, ensure that you inform users of the new time-out.
Global code time-out • Determines the expiry time for users’ global fax codes. The default value is seven (7) days.
• A global code can be used on any networked fax machine controlled by Equitrac
Professional, rather than just the fax device connected to the local TPC. This code consists
of four digits.
• If you change the default value, ensure that you inform users of the new time-out.
Card reader positions Sets the user code position on the magnetic stripe or proximity card data. See Card ID
Auto-registration on page 327 for further details.
Offline Support
Equitrac Professional supports offline usage in the case when CAS is unavailable. If the CAS service goes offline, users
can still log in, make copies and release print jobs using the DCE login cache. DCE caching allows previously CAS-
validated users to login when CAS is offline.
For example, with DCE caching, if User1 logged in while CAS was online, but User2 did not, then if CAS goes offline,
User1 can still login, but User2 cannot login until CAS comes online again. Once CAS is back online, then User2 can
login, and continue to login even if CAS goes offline again.
NOTE: When DCE is available but CAS is unavailable, users whose credentials are cached at the DCE are able to log in,
make copies and release print jobs from their home Follow-You queue. However, other functions may not operate
normally depending on the end points.
3 Click the name of the TPC you want to assign configuration sets to or configure with advanced settings.
The TouchPoint Console summary dialog opens for the selected TPC.
4 Under the Behavior section, select a Configuration set to apply to this TPC from the drop-down list.
5 If this TPC is fax-enabled only, select the fax set to apply to this TPC from the Fax configuration set drop-down
list.
If the TPC is connected to two fax devices, ensure the Enable secondary fax box is selected.
NOTE: Although a single TPC can have multiple fax lines, you must apply the same fax configuration set to both
lines.
6 If necessary, set the Pricing options. For information on setting pricing for this TPC, see Configuring Price Lists
on page 143.
7 If necessary, select a Rule set option from the drop-down list. For information on applying a rule set to this TPC,
see Routing Rules on page 257.
8 To enable scan tracking on the TPC, select a Scan device type from the drop-down list and configure Options. For
information on scan integration, see the Equitrac Professional Scan Solutions Guide.
9 Select the License for DMS or License for OCR to designate this TPC as one to use for scanning to a Document
Management System or to user Optical Character Recognition functionality, respectively.
NOTE: You must have available licenses to enable these functions. For detailed information about licensing, see the
Equitrac Professional Installation Guide.
10 If necessary, select an Override copier type from the drop down list that corresponds to the copy control cable
connecting this TPC to its MFP. If this TPC is to be configured for Canon color copy tracking, select Canon -
enhanced TCP/IP. For more information, see Canon Color Copy Tracking on page 321.
11 Click OK to save the changes.
Requirements
Equitrac Professional’s server based Canon color copy tracking requires the following:
• Equitrac Professional 5.2.3 or higher
• TCP/IP ports 9007 and 47545 open on your network between DCE and the MFP
• TouchPoint Console (TPC) connected to a supported Canon MFP with a copy control cable
Canon color copy tracking is available with TPCs only. Other Equitrac Professional control device software clients
are not supported.
Supported MFPs
Color copy tracking is supported for all multi-function Canon imageRUNNER products designed for office or
production use. It is not supported on copy only or desktop models.
Communication Workflow
The following diagram depicts the data communication workflow that occurs for color copying tracking with Canon
MFPs and TPCs:
Constraint/limitation Description
Color information is not tracked for Equitrac Professional matches TPC transactions with MFP logs to determine
unassigned TPCs. color attributes of copy transactions. DCE queries the MFP referenced in the
TPC’s physical device. As such, it is critical that the TPC be associated with the
physical device for the Canon MFP for color tracking to work.
Color information will not be tracked with If the network is down, DCE will not have access to the Canon MFP and cannot
copies if the network is down retrieve job details to match with TPC copy information. The resulting
transaction will not have color attributes recorded.
Color copies will not be tracked if the TPC If the TPC is offline, the DCE does not know when a TPC session is started and
is offline so will not query the MFP for color information.
Color copy tracking will not work if there is If there is a delay in the copy job, such as a paper jam, a transaction may not be
a prolonged error condition on the MFP tracked with color details in the Canon log file.
NOTE: To assist with troubleshooting color tracking issues, the DCE will log an event with the Windows Event
subsystem every time it detects 4 or more synchronization problems within a 30 minute period. This will occur
whenever the DCE is unable to determine which TPC transactions are associated with Canon MFP log file entries.
NOTE: Your firm may have stand-alone TPCs that are used only for disbursement entries or fax devices. These TPCs
may not need secure access control or function tracking, and therefore do not need to be assigned to an MFP
through Equitrac Professional.
To assign a TPC to a physical device, or MFP, ensure that you have already assigned a general configuration set and
a fax configuration set (if required) to each unassigned TPC before you complete the following steps.
1 In System Manager, click Configuration > Devices. Ensure that you are using the Standard view to display the
device list.
2 Expand the list of Unassigned TouchPoint consoles by clicking on the plus sign (+).
3 To assign the TPC to a physical device, you can:
a Right-click on an unassigned TPC name and click Assign. The Assign to physical device dialog opens.
b Select a physical device name from the list, and click OK.
—Or—
• Drag-and-drop each TPC to an output device.
In the example below, TPC1 is assigned to the Ricoh Aficio 1060 and therefore appears as a subset of the
device.
TPC now controls access to the output device (MFP) and can be configured to track supported functions and release
secure documents from a print queue.
3 In the Name field, enter the name of the TPC exactly as it was entered in the TPC’s initial configuration.
WARNING: A TPC name is a unique identifier for each TPC. If you do not enter an existing TPC name exactly as
entered during the initial TPC configuration, the TPC will assume that it is a new device and will launch the initial
configuration wizard upon restart.
NOTE: You do not need to complete the Description field in the TouchPoint Console summary dialog. The
Description field is filled automatically with the description entered during the TPC initial configuration or during a
reconfiguration using the TPC Administrative options.
For details about changing the TPC name or description, see the section TouchPoint Console Name in the
“Additional Local Configuration” chapter of the TouchPoint Console Installation and Setup Guide.
4 For the Server option, select from the drop-down list the DCE server that you want to manage this TPC.
5 If necessary, select a Location for this TPC from the drop-down list.
NOTE: The IP Address, Hardware Address, and Firmware version information is not populated until the TPC has
successfully contacted the DCE server.
6 If necessary, set the Pricing options. For information on setting pricing for a TPC, see Configuring Price Lists on
page 143.
7 If necessary, select a Rule set option from the drop-down list. For information on applying a rule set to a TPC, see
Routing Rules on page 257.
8 Choose a general configuration set from the Configuration set drop-down list. See Planning General TPC
Configuration Sets on page 304 for details.
9 Choose a fax configuration set from the Fax configuration set drop-down list. If this TPC is not fax-enabled, you
do not need to set this option.
If there are two fax lines controlled by this device, select the Enable secondary fax box. You can only apply one fax
configuration set to each TPC, even if there are two fax lines.
10 To enable scan tracking on the TPC, select a Scan device type from the drop-down list. For information on setting
the Scan device type, see the Equitrac Professional Scan Solutions Guide.
11 If the TPC is connected to the MFP with a specific copy-control cable type, select it from the Override copier type
list.
12 Click OK to save these settings.
To determine if the Equitrac Professional DCE service successfully communicated with this TPC, open the summary
dialog again. If the IP address field is filled, communication was successful.
4 Use the TPC Installation & Setup Guide to place the TPC on the network. During initial configuration, you can
assign the same IP address as the removed terminal if you select the Static IP option to set the static TCP/IP
address. If using DHCP to assign addresses, ensure that you choose the DHCP option instead.
5 To apply a general configuration set to the new TPC, select a Configuration set from the drop-down list.
6 If this TPC is fax-enabled only, select the fax set you want to apply to this TPC from the Fax configuration set
drop-down list.
If the TPC is connected to two fax devices, ensure the Enable secondary fax box is selected.
7 For information on setting pricing for this TPC, see Configuring Price Lists on page 143.
8 For information on applying a rule set to this TPC, see Routing Rules on page 257.
9 For information on configuring scan with a TPC, see the Equitrac Professional Scan Solutions Guide.
10 In the Devices window within System Manager, drag-and-drop the new, unassigned TPC to the physical output
MFP that the deleted PageCounter was controlling.
NOTE: * The HID iCLASS contactless smart card does not use HID encoding to store data. When configuring Equitrac
Professional to recognize HID iCLASS cards, use only the procedure for setting card reader data position, as described
in Card ID Auto-registration below.
Users will swipe or wave their security cards at the card reader to identify themselves at the TPC. As the administrator,
you must identify the positions within the complete card data where the unique user identification code is located.
The user identification code value can correspond to:
• The user validation code from your time and billing system (the Field 3 value defined in Equitrac Professional
System Manager > Configuration > Field Mapping)
—Or—
• An alternate user code configured for a user (the Alternate user code value defined in Equitrac Professional
System Manager > Users > [User name])
Alternate user codes can be manually added or updated in System Manager, or automatically registered at a TPC with
a card reader. For information about automatic registration of alternate user codes, see Card ID Auto-registration on
page 327.
NOTE: If the MFP fails to respond to card reader activity, check and secure the card reader’s USB connection to the
MFP and restart the MFP.
Card ID Auto-registration
If a user’s alternate user code has not been registered with the Equitrac Professional server, TPC includes an automatic
registration feature. When a user swipes a card at the TPC, if the card ID is unknown, the user will be prompted to log
in with their system user code or network credentials. After their system or network credentials are authenticated,
Equitrac Professional will automatically register the card ID as the alternate user code for that user, thereby enabling
subsequent card access to all TPCs with card readers.
CAUTION: Be accurate in defining the data positions that will uniquely identify and validate each user in your firm. If
the card data positions do not isolate the data value that is unique for each user, your firm may experience incorrect
TPC user logins.
NOTE: While HID options work with embedded devices as well as TPCs, the determination of exact HID content
requires the use of a TPC.
For Equitrac Professional to authenticate the user codes in the HID cards, you need to:
• Determine the binary digit (bit) positions for the ID code and, if used, facility code within the HID card data
• Determine how to identify these HID codes as decimal values
• Configure Equitrac Professional to extract the unique HID codes from the card data value using your determined
settings
You will configure Equitrac Professional for identifying the unique HID data values through both the HID
decoding and Card reader data position settings within the TouchPoint Console global options configuration
dialog.
NOTE: Remember that if you do not need to identify any specific data value within the full HID card data value, you
do not need to set the HID decoding function within the TouchPoint Console global options configuration dialog.
Since the TPC reads HID encoding as 16 octal digits, enter “1” and “16” as your start and end values in the Use data
from position and to fields in the TouchPoint Console global options dialog.
How you determine the specific data positions for the codes on the HID cards depends on your HID card
encoding format:
...a 26-bit HID card 1 Check your HID card order forms to confirm the HID card format, and the facility and ID
encoding format with code lengths.
a facility code, 2 Enter the following values in the HID decoding dialog:
Facility code ID code
Start: 23 Start: 31
End: 30 End: 46
Width: 3 Width: 5
3 Enter the following values as your start and end values in the Card reader data positions
in the TouchPoint Console global options dialog:
Use data from position 1 to 8
These configuration settings will identify 8-digit decimal identifiers within the HID card
data, where the first 3 digits are the facility code and the remaining 5 digits are the ID code.
...an HID card with any ...you need to convert the encoded data stored on HID cards into a format that allows you to
other encoding locate the ID and facility code values within the full data value.
format or an For detailed procedures, see Decoding HID Cards on page 332.
unknown encoding
format, For administrators who understand HID card encoding concepts, review the Case Study
Example: Decoding HID Cards on page 340.
CAUTION: If you do not know the encoding used on your HID proximity cards, this document provides a reasonable
method to determine your card encoding. Determining the encoding type for your firm’s HID cards will require time,
effort, mathematical calculations and deductive reasoning. Therefore, if possible, it is recommended that you contact
your security administrator or HID vendor to determine the encoding type used on your proximity cards or for help.
CAUTION: Your HID cards may include a printed number on the surface of the card. Although this number may be
similar to the facility or ID code encoded within the card, you should still analyze the card data itself to determine the
accurate HID data positions.
To determine specific positions of the encoded ID code and facility code (if used) on the HID card, follow these
procedures:
1 Use a TPC with a card reader to display the HID-encoded card data values for you to record (see page 332)
2 Convert the octal data to binary data (see page 332)
3 Calculate bit positions for the ID code and facility code (if used), within the binary data (see page 334)
4 Determine the decoded data value widths (see page 338)
5 Record the HID decoding values in the TouchPoint global options dialog (see page 339)
4 Set the display size to allow at least 16 digits in the text field. In Microsoft Calculator, click the Qword option.
5 Copy-and-paste or type the 16 octal digits into the text field.
6 Change the number system to binary. In Microsoft Calculator, click the Bin option.
The number is displayed again in binary digits.
CAUTION: You should have a 48-digit binary string for each card. However, the calculator application will usually
delete leading zeros. If necessary, adjust your resulting binary digits to include any missing leading zeros and ensure
there are three binary digits for each octal digit.
Example: Step 2
The five sample HID cards provided 16-digit octal values on the TPC. The following table shows how these sample
values convert to binary data values, including four leading octal zeros represented as 12 (4 octal digits x 3) zeros in
the binary numbers:
0000201550521216 000000000000010000001101101000101010001010001110
0000201550521220 000000000000010000001101101000101010001010010000
0000201550521223 000000000000010000001101101000101010001010010011
0000201550521225 000000000000010000001101101000101010001010010101
0000201550521226 000000000000010000001101101000101010001010010110
26 bits
(with facility
code)
37 bits
(without facility
code)
37 bits
(with facility
code)
NOTE: HID also offers other card formats, such as 35-bit Corporate 1000 cards.
Regardless of the type of proprietary encoding used on the HID card, the HID card reader always returns 16 octal
digits to the TPC. When converted to binary, the 16 octal digits equal 48 binary digits, including zeros for padding. In
addition, the actual digits of the facility and ID codes always appear at the right end of the data string. Therefore,
knowing the type of encoding used on your HID cards will help you greatly in decoding the facility and ID codes from
the card data.
2 Paste the binary strings you converted from the octal string above the ruler. Be sure to add enough leading zeros to
make the string equal to 48 digits.
3 Compare the binary strings against the common card encoding formats (26-bit and 37-bit) to see if your card data
matches any of them. Look for a matching set of digits in the facility code positions of the common card format.
Also, take care to watch for 1’s in your sample binary string to ensure they occur between the leading and trailing
parity bits of a common encoding type.
...matches a common HID card encoding format, ...use the common card encoding format to determine the start and
end positions of the facility and ID codes. Then skip to Step 4:
Determine Decoded Value Widths on page 338.
...does not match a common HID card encoding ...skip to 5. To determine the range of digits that make up the
format AND your firm does not use facility ID code, use one of the following procedures: on page 336.
codes,
...does not match a common HID card encoding ...skip to step #4 below.
format AND your firm does use facility codes,
4 If your firm uses a facility code, follow one of these procedures to determine the range of digits that make up the
facility code. Otherwise, skip to 5. To determine the range of digits that make up the ID code, use one of the
following procedures: on page 336:
If... Then...
you know the facility code 1 Use a calculator, such as Microsoft Calculator, to convert the decimal format of your
for your sample cards, facility code to its binary format.
2 Perform a find, or search, operation in the text editor to locate the digits of the binary
string representing the facility code.
3 In the highlighted search results, use the ruler to calculate the start and end digits of
the facility code.
you do not know the Analyze the data from a number of cards to determine the common, repeating data on
facility code, each card, make the following assumptions:
• The facility code will appear first in the string, counting from the left, and the ID code
will appear on the right end of the string.
• If there is a set of digits on the left that are identical in all strings, then you can assume
that it is the facility code.
NOTE: If you need help identifying your firm’s facility code, contact your security system administrator or HID card
vendor.
NOTE: In the example, the facility code data positions do not match one of the common HID encoding types and
therefore has unique start and end positions.
5 To determine the range of digits that make up the ID code, use one of the following procedures:
If... Then...
...you know the ID codes 1 Use a calculator, such as Microsoft Calculator, to convert the decimal format of your ID
for your sample cards, code to its binary format.
2 Perform a find, or search, operation in the text editor to locate the digits of the binary
string representing the ID code.
3 In the highlighted search results, use the ruler to calculate the start and end digits of
the ID code.
If... Then...
...you do not know the Analyze the data from a number of cards, make the following assumptions:
expected ID codes for • The last binary digit (the 47th) is a parity digit and must be disregarded. ID codes
your sample cards, typically end at bit 46.
• Knowing a range of ID codes that may be encoded on your cards will help you
determine how many binary digits are required for the ID.
Example: Step 3.5a
If you know that the ID codes at your site range between 75,000 and 200,000, you can
calculate that the largest ID code (200,000) in binary would need 18 digits
(110000110101000000).
• The starting bit (at the farthest left) for ID codes will be the first bit after:
• your facility code (if there is one)
—Or—
• what appears to be the leading parity bit.
• If your cards have printed labels on them, converting possible ID data to decimal format
may yield values that are close to the numbers printed on your cards.
Example: Step 3.5b
If the number printed on a sample card was 87343 11082200-1, you could convert the
5-digit number 87343 or the 8-digit number 11082200 to their binary values and
compare each one to the binary string.
The following comparison shows a repeat of the string of digits at the far right end of
the string, 111(minus the last binary digit) and in the middle with 101010.
Full card data: 10000001101101000101010001010001110
Binary value of 87343 (from printed card): 10101010100101111
If you now take the digits from the same location and width in the card data
(10101000101000111) and convert this to a decimal value, you discover its value is
86343, with only one digit different, in the 1,000 digit, than the one on the printed card.
If you repeat this analysis with other sample cards, you may discover a pattern in how
the binary format of the number printed on the card relates to the string of binary
digits, for instance, with only one digit consistently different in the 1,000 digit location.
The image below shows that the ID code is located from digit 29 to digit 46 inclusive. The last binary digit (the 47th) in
the string is a parity digit and can be disregarded.
NOTE: If there are leading zeros before the ID code (and after the facility code, as in the example above), it is possible
that the ID code or the facility code may include more digits than your analysis shows and that your sample card
codes do not represent possible code ranges. To ensure that you identify the largest possible range of digits in the
data and anticipate more variations in the card ID codes, you may want to start the ID code earlier or extend the
facility code.
Example: Step 4b
If the decimal width for a facility code is 3, and the decimal width for the ID code is 6, then the total width for your
unique user authentication codes is 9 (3 + 6).
2 In the HID decoding dialog, record the values for the facility code (if used) and ID code:
Facility code Select this option to make the facility code-value fields available.
Facility code/Start The bit position in the complete binary data value where the facility code begins.
Facility code/End The bit position in the complete binary data value where the facility code ends.
Facility code/Width The number of decimal digits in which the facility code is represented after
conversion from the HID binary value.
ID code/Start The bit position in the complete binary data value where the ID code begins.
ID code/End The bit position in the complete binary data value where the ID code ends.
ID code/Width The number of decimal digits in which the ID code is represented after conversion
from the HID binary value.
NOTE: If you do not know how to determine the HID decoding values, see Determining HID Decoding Values on
page 330.
1 When the administrator swipes the HID card at the HID card reader connected to the TouchPoint Console, the
TPC External Serial Device Interface screen shows the following card data string in octal format:
0000201550521216
2 The administrator translates the octal string to its binary value using the Microsoft Windows Calculator:
0000201550521216 000000000000010000001101101000101010001010001110
Code Type Code (in decimal) Code (in binary) Decimal Digit Width
ID 86343 10101000101000111 5
5 Returning to the HIDEncoding-Ruler.txt file in Notepad, the administrator clicks Edit > Find and enters the
expected binary string representing the facility code (1101101). He clicks Find Next. The search string is
highlighted.
6 The administrator uses the ruler to determine that the facility code may start at digit 20 and is likely to end at digit
26. The facility code (109) ends with an odd number and so the binary digit “1” at position 26 confirms the
likelihood of the administrator’s choice.
7 The administrator clicks Edit > Find again and enters the expected binary string for the ID code
(10101000101000111). He clicks Find Next and the search string is highlighted.
8 The administrator uses the ruler to determine that the ID code may start at digit 30 and end at digit 46. Since there
are three zeros between the end of the facility code (bit 26) and the start of the ID code (bit 30), the administrator
decides to add two digits to the start of the ID code. He therefore uses a starting digit of 28 for the ID code.
9 The administrator knows the facility code of 109 is 3 decimal digits wide and uses this value for the facility code
width.
10 Although the sample ID code (86343) is 5-digits wide, the administrator added two more binary digits to the ID
code to account for a higher number of employee IDs over time. Therefore, the administrator uses a value of 6 for
the ID code width.
11 The administrator can now use the following values to complete the HID decoding dialog:
Facility code/Start 20
Facility code/End 26
Facility code/Width 3
ID code/Start 28
ID code/End 46
ID code/Width 6
12 The administrator then calculates the total width of the unique card value to be 9 decimal digits (3 [Facility code]
+ 6 [ID code]). Therefore, he can enter the following values in the Card reader fields in the TouchPoint Console
global options configuration dialog:
Use data from position 1 to 9
To view information specific to TouchPoint Consoles, select TouchPoint Console from the Device Type drop-down
list, then click Apply.
The list of devices will update and you can view the status of each TPC.
To view a summary of transactions generated on a particular TPC, click the ellipsis (...) under the Transactions
column.
To view the Web Administration page for a particular TPC, click on the IP address of the TPC. The Web
Administration page will launch and you can view more detailed system information about the TPC.
Topics:
Client Popup Workflow
Determining Print Tracking Requirements
Creating and Maintaining Application Classes
Assigning Applications to Classes
Defining Field Validation Requirements
Creating Popup Styles
Creating SmartPrompts
Configuring Print Client User Settings
Testing the Popup
Associating the Popup Style with a Class
This chapter introduces the Equitrac Professional client popup, and provides details on configuring the appearance
and functionality of the popup for both Windows and Macintosh environments. You can define a number of popup
styles and, if desired, assign a different style to each user class defined in Equitrac Professional. This enables you to
customize the transaction data Equitrac Professional collects, based on configurable popup prompts and default field
values.
The client software provides print-time selection functionality using a workstation popup and a separate tool tray
application. Client popup styles also affect what the user sees on TouchPoint Consoles and on any embedded devices
configured. The Administrator can establish popup styles that generate prompts for billing data after the user
identifies themselves at a TPC or at an embedded device.
This chapter provides information about:
• creating application classes and assigning applications to them
• creating and testing popup styles
• associating popups with classes
• identifying draft or reprint transactions, and associating popup behavior for each
Tracking Options
You can set tracking behavior for each user, device, or application class by assigning one of the following tracking
behavior options outlined below.
Display popup The popup appears as per the popup behavior and rules you User Class
configure; Equitrac Professional gathers all document transaction Device Class
details and costs, and posts the transaction to the control system.
Application Class
Hide popup The popup does not appear to the user; Equitrac Professional applies User Class
the configured default hide mode values configured for the popup Device Class
style assigned to this class in the background, and posts transaction
Application Class
details to the control system without user intervention.
Silent tracking for The popup does not appear to the user; Equitrac Professional collects User Class
device management all transaction data including costing, and posts the transaction to Device Class
only CAS only. You can run reports later detailing device performance on
Application Class
the basis of this data, but it never appears in the control system
database.
You do not require a popup style for any class to which you will
assign silent tracking.
Do not track The popup does not appear to the user, and Equitrac Professional User Class
collects no data on the transaction whatsoever. This option is Device Class
applicable only to non-DRE printing in Equitrac Professional 5.2.
Application Class
You do not require a popup style for any class that you will not track.
Determined elsewhere The tracking behavior is determined by the next level in the tracking User Class
hierarchy (either the device or application level). Device Class
For example, you may designate popup behaviors for each of your user, device, and application classes. When you
print a document, Equitrac Professional evaluates the document details to determine the user and the associated user
class. Because user class settings are at the top of the tracking hierarchy, the application applies the assigned user class
tracking behavior when printing the document, and does not check for tracking behaviors defined at the device or
application levels of the hierarchy.
Continuing with the example above, if you configure the user class tracking behavior as Determined elsewhere,
Equitrac Professional checks for device class settings on the selected printer. If the printer is part of an existing device
class, Equitrac Professional applies the popup and tracking behavior assigned to the device class when printing the
document.
NOTE: If the printer is not yet registered in Equitrac Professional, or if it is not a standard network printer, there are
administrative procedures for registering the device and assigning both non-default classes and popups as required.
See Managing Devices on page 175 for more details.
You can also define the device class tracking behavior as Determined elsewhere, in which case if there are no
applicable user class settings for the current print user, and no device class tracking settings defined for the current
printer, Equitrac Professional checks for application class tracking behavior. The application class is the lowest level in
the tracking hierarchy. There are no tracking options below this level, although you can still apply overrides to the
application tracking behavior.
For information on tracking and popup behaviors using a Document Management System, see Configuring Tracking
and Popup Behaviors on page 451.
Silent Tracking
Using the Silent tracking for device management only option to track transactions without prompting users for
validation data. Transactions tracked in silent mode use pre-defined validation codes and are still posted to CAS for
reporting purposes.
Check for
Apply Device Determined Application
Class Tracking No Elsewhere? Yes Class Tracking
Behavior Override
NOTE: You can completely disable popups for all classes by using the Global popup behavior configuration option
in System Manager. See Disabling Popups on page 349 for more details.
• If the user is a legal assistant, the application finds no defined tracking behavior for the user class, checks the
device class, and tracks based on the device’s Display popup configuration. The application tracks all print
transaction and costing details, and posts the transaction to the control system.
• If a system administrator prints to the same device, however, Equitrac Professional checks the user class and device
class settings, and finds the System Administrator class has an override on the device behavior. It does not display
the popup, and only posts transaction details to CAS.
Tracking overrides can only be set at the device and application level. For more information, see Creating a Device
Class on page 183 and Setting Application Class Overrides on page 351.
Disabling Popups
Use this feature if you want to disable the client popup for all print transactions monitored by Equitrac Professional.
1 In System Manager, navigate to System > Configuration > Equitrac Professional settings > Global popup
behavior.
2 In the Global popup behavior dialog, check this option to suppress the popup for all print transactions monitored
by Equitrac Professional. Leave the option unchecked to enable Equitrac Professional to apply popup behaviors
according to the defined tracking behavior hierarchy.
3 The Offline tracking behavior for unknown user, device or application radio buttons are used when the client
workstation (EQSharedEngine) cannot contact the CAS and the exact combination of user, printer and application
has not been printed to before. Typically, the client workstation caches the tracking behavior for each combination
once used, and uses these settings going forward. The tracking behavior modes are identical to those used for user,
printer, and application classes:
• Display popup: The print is tracked and the user sees a popup, unless popup rules cause the popup to be
hidden.
• Hide popup: The print is tracked and the popup is not shown. Hide mode values (or DMS values) are used in
the transaction.
• Silent tracking for device management only: The print is tracked but no client\matter info is posted. This
setting generates an exception unless the Exception rules are altered.
• Do not track: No transaction is posted for locally connected printers. Prints to DRE and DRC prints are
tracked as “Silent tracking for device management only”.
4 Click OK to save the setting, or Cancel to close the window without saving the setting.
For information on the general tracking behavior hierarchy, see Print Tracking Hierarchy on page 346.
NOTE: If you configure a workstation to use local desktop or non-DRE network printers, you can also configure an
Exclusion list of applications that Equitrac Professional does not track.
Application class settings take precedence over DMS settings only in terms of the tracking behavior hierarchy. Both
user and device class tracking settings override any tracking configuration you define for application classes.
4 Assign the relevant tracking behaviors, and any relevant overrides, as defined in the table shown in Tracking
Options on page 345.
5 To set application class overrides, see Setting Application Class Overrides on page 351.
6 If you want to make this new class the default class, to which Equitrac Professional will automatically register all
new applications on first print, check the Default class option.
7 Click OK to close the dialog.
NOTE: Device class tracking behavior overrides application class tracking behavior. See Print Tracking Hierarchy on
page 346 for details.
a Select the User class that the override will apply to from the drop list.
b Enter an Override description.
c Select the overriding Tracking behavior.
d Click OK.
3 Repeat the above steps to add other override behaviors to other user classes as required.
4 Click OK to close the Application class definition dialog.
NOTE: Equitrac Professional does not prompt for confirmation when deleting application classes. If you delete a class
that still has applications assigned to it, Equitrac Professional moves the assigned applications into the default
application class.
4 Specify the filename extension and description for each application you want to track. Filenames must be unique,
to avoid conflicting with other currently-registered applications.
5 Click OK to save these settings, or Cancel to close the Application definition dialog without saving this entry.
NOTE: Each application is given a unique identifier. Once you delete it, the application is effectively closed in the
database. Its identifier cannot be recreated, even by adding a new application with the same name.
When prompted, confirm the deletion, or cancel the action without deleting the application from Equitrac
Professional.
NOTE: Disabling validation on both the client and server side may speed your print transaction process (especially
useful if your network response time lags for any reason), but also introduces the risk of sending erroneous
transaction data to CAS.
Default settings include the Client and Matter fields, Search function, and Last Job Speed Button.
NOTE: The popup’s appearance on a Macintosh workstation is different than the sample shown above, and typically
looks more like a standard Macintosh dialog.
When you configure the popup for use in mixed environments, any features you configure for use that are not
supported by the Macintosh operating system, do not appear in the Macintosh workstation client. They will be visible
as expected in the Windows workstation popup.
The Macintosh environment supports:
• Popup styles defined on CAS to show custom fields on the popup with defined speed buttons and SmartPrompts
only.
• Online validation only, not local caching.
• Users configuring the popup on the local Macintosh workstation to show or hide speed buttons and last job
button.
• Limited tracking mode functionality; the Macintosh popup tracks silently for cost recovery, no cost recover, and
regular popup functionality. There is no support in the Macintosh version for Copy-level control, Page-level
control.
• Limited search functionality; search for child field is available only for specified parent field.
For a full comparison of the features available in Macintosh OS X and Windows environments, please consult the
following table:
Feature OS X WIN
3 Charge splitting:
Subjobs No Yes
NOTE: If you edit an existing style, be aware there is no way to restore the Equitrac default settings on the initial style,
or previous settings on a style you created. If this is a concern, instead of modifying the initial style, create new popup
styles for every variation you foresee using.
General Configuration
1 In System Manager, navigate to Client config > Popup styles.
2 Click Add in the right pane to open the popup designer. You can also right-click an existing popup style and select
Modify to open the popup designer. A Modify <name> popup style dialog opens:
3 Enter a unique Name for this popup style. This is the name that will appear in the styles list in System Manager.
4 Provide a description for this popup style.
5 In the Global settings section, enable or disable Non-billable/Draft printing. This option determines whether or
not the Draft printing checkbox appears on the client popup and allows users to quickly designate specific
transactions as non-billable, thus overriding the status that is determined from the validation codes or other
system rules.
See Configuring Show/Hide Popup Options on page 359 for more information on configuring overrides for
billable/non-billable/inherited status on the basis of popup triggering rules.
NOTE: If you provide invalid Hide mode values or make any errors when configuring Hide mode settings, the client
popup will appear.
1 In the Show/Hide popup options box, click Add to add a new rule, or right-click an existing rule to modify it. The
Rule dialog box opens:
2 In the Rule dialog, provide a name for each hide/show popup rule. Each new rule you create increments the rule
ranking, which determines the order in which Equitrac Professional checks and applies rules. The first rule you
create ranks first, the next rule you create ranks second in the list by default, the following rule ranks third, and so
on.
You can change the ranking manually by selecting and moving one or more rules up and down in the listing in the
Advanced print settings dialog, in the Show/Hide popup options section.
3 Define the transaction criteria which will trigger this rule:
• Application name: Any transactions originating from a particular application.
• Device name: Any transactions originating from a particular device.
• Device Class: Any transactions originating from a device within a specific device class.
• Copies: A number of copies, including reprints, greater or less than the number specified.
• Pages - 1 copy: A number of printed pages in a single-copy document greater or less than the number
specified.
• Pages - active job: A number of printed pages, including multiple copies of a single document, greater or less
than the number specified.
• Pages - including reprints: A number of printed pages, including reprinted pages within a particular
document, greater or less than the number specified. For more information regarding tracking reprints, see
Identifying and Tracking Reprints on page 366.
4 Once you have defined triggering criteria for this rule, specify the Prompt behavior for the popup, either to Show
or Hide on the user’s workstation. If this popup is hidden from the user, Equitrac Professional will populate the
required fields and values in the background based on configuration specified here.
5 Define the Costing behavior for this popup, as either Billable, Non-billable, or Inherited from fields (values you
define for each field when you import them from the time and billing system). Specify whether or not the user can
override this costing behavior on the popup.
6 Select the Ignore "First N copies are non-billable" checkbox to ignore the first N copies are non billable option for
this rule. This option is only available if the First N copies are non-billable option is selected in the Advanced
print settings dialog box.
7 Click OK.
If the document is not a DMS document, Equitrac Professional’s class-level settings and tracking hierarchy determine
popup behavior.
For more information on mapping fields in the popup to fields from the DMS, see Configuring Popup Fields on page
368.
For information on integrating Equitrac Professional with your Document Management System, see DMS Integration
and Configuration on page 447.
Use the following options to define popup behavior in an environment that prints both DMS and non-DMS
documents. For more information on integrating Document Management Systems with Equitrac Professional, see
DMS Integration and Configuration on page 447.
• Select Hide popup for N pages or fewer to suppress the popup for a specified number of pages. Enter the
maximum number of pages for which the popup will operate in the background only. If the user prints more than
the maximum number of pages, the popup displays, and the user must manually provide the required validation
data to continue.
• Select Hide popup for N copies or fewer to suppress the popup for a specified number of copies. This option
suppresses the popup for a specified number of full copies of the same document, regardless of the number of
pages in the document, and also enables you to specify what to do with the copies greater than N (treat them as
billable or non-billable). If the user prints more than the maximum number of pages, the popup displays, and the
user must manually provide the required validation data to continue.
• Hide popup for non-DMS documents: When you enable this setting and a user prints a non-DMS document, the
popup does not display, regardless of the tracking behavior determined by the class-level settings and the tracking
hierarchy. Equitrac Professional tracks the document using the current popup style’s Hide mode validation values.
If you have not enabled this option and the user prints a non-DMS document, the class-level settings and tracking
hierarchy determine the popup and tracking behaviors.
• Hide popup for DMS documents: When you enable this setting and a user prints a DMS document, the popup
does not display, regardless of the tracking behavior determined by the class-level settings and the tracking
hierarchy. Equitrac Professional accesses the DMS to retrieve validation data and charges the print transaction to
the appropriate account. If you do not enable this setting and a user prints a DMS document, Equitrac Professional
accesses the DMS to retrieve validation data, and uses this data to prefill the fields on the popup. The user can
confirm that Equitrac Professional retrieved the appropriate validation information, change the information if it is
incorrect, and complete the print transaction.
Users can also choose to suppress the popup themselves, using the User Settings tool in the Windows tool tray. For
more information on this feature, see the online help for the User Settings tool, available by clicking the Help button in
the tool itself.
2 In the text box, enter the name(s) of the document for which the rule will be applied. Wild cards such as "?" and "*"
are allowed. Limit document names to their own line; do not use a delimiter to separate document names.
CAUTION: Commas are not allowed within document names.
NOTE: This popup style is limited to TouchPoint Consoles and the Print Client (Print Popup). The Embedded popup
styles force entry of Client codes prior to entry of Matter codes.
Using QuickPrint
For most users, the time it takes to send a print request to a physical device is not significant enough to be noticed.
There is, however, a small class of users where an extra few seconds for the job to start printing can be significant. This
delay is often characterized as "Delay to First Page Out", meaning the time it takes from the print request to the time
the first page is ejected from the physical device.
First Page Out delays can occur in Equitrac Professional in those cases where a Print Popup is displayed on the user
workstation because of 2 key factors:
• some users want the ability to cancel a print request at the Print Popup phase
• some corporate policies prevent users from printing documents unless they have entered validated client/matter
codes.
In those cases where neither of those two factors are significant for a specific user class, a site administrator can
effectively eliminate this delay by enabling the QuickPrint feature.
QuickPrint effectively disassociates the validation data collection from the print stream. This means that the print job
is sent to the device at the same time as the Print Popup is displayed on the workstation. When this feature is enabled,
a user can still cancel the Print Popup, but this will not impact the delivery of the print job to the device. When a user
cancels the Print Popup, this cancels client and matter code collection and a transaction is still recorded in Equitrac
Professional but will likely generate an exception for the user (depending on the exception rules configured by the
system administrator).
NOTE: Global History is recognized as an option that might still be necessary, even though WAN optimization is
enabled. Because of this, users have the ability to enable WAN optimization, but still elect to preserve the Global
History behavior of Equitrac Professional.
If you are configuring popup rules specifically for reprints (the Pages — including reprints criteria), you must also
specify how Equitrac Professional will identify reprints, using the following procedure:
1 Open the System Manager > Configuration > Equitrac Professional settings > Reprint Identification dialog.
2 Check the Enable reprint identification option. Reprint identification is disabled by default.
3 Specify the criteria by which Equitrac Professional will identify reprints on the device, such as the device name, or
by matching identical data streams sent to the target device.
If you disable the Device name option, Equitrac Professional will enable you to count as a reprint any document of
the same name as a previously-printed document, even if you sent the earlier print to a black and white printer,
and the current transaction to a color printer.
If you disable the Identical data sent to driver option, you can make minimal edits to the document between print
requests, as long as the changes do not alter the page count, and are sent through the same driver. Increasing or
decreasing the page count will cause Equitrac Professional to treat the document as a new print request, not a
reprint. Selecting a different driver will check the print driver capabilities, causing Equitrac Professional to treat
the document as a new print request.
4 Specify the time frame in which a user must send the same document to the printer for it to count as a reprint. The
default is 24 hours.
5 In the Modify popup style > Advanced print settings > Hide popup options >Add rule dialog, select the Pages
— including reprints criteria, and specify a Greater than value of more than one.
6 Specify the Prompt behaviour to show or hide the print popup for documents triggering this rule, including
reprints. If you plan to hide the popup for reprints, ensure you have defined the default Hide mode values for all
the fields on the relevant popup style.
If the Hide mode values for the popup are empty, the popup automatically assigns the field values from the user’s
previous transaction.
7 Specify the Costing option for this rule, and whether or not the user can override the costing, assuming the popup
appears when the user sends the triggering document to reprint.
You can define each style you create with global settings to enable or disable non-billable/draft printing as an option
on the print popup (shown above).
CAUTION: Hierarchical tracking behaviors, rules, and user overrides may have an effect when draft printing is
enabled.
In the designer’s Rule dialog, if you specify that documents meeting specific rule criteria are billable (the Costing
option under Actions and attributes), you can allow user to override the billing by identifying the document as Draft
on the popup:
If you do not enable the user override option in the Rule configuration, Equitrac Professional disables the option for
Draft printing on the popup.
Selecting Fields
Use the options in this section to determine what fields will actually be visible to the user on the popup. To remove a
field from this list after you’ve added it, right-click the desired field in the Modify popup style dialog, and select
Remove from the menu.
1 In the Fields section, double-click Add to open the Prompt field dialog.
2 From the Field name drop list, select the desired field. Note that certain field options are restricted on the basis of
the field you select from the list.
3 Provide a Label for this field, as you want it to appear on the popup or console. For example, if you select the
UserCode field in the list, you might want the field on the popup or console to show the label User ID.
4 Specify a Default value for this field. This is the data that displays automatically in the popup when it appears to
the user, and is user-editable unless you define this field as Read-only.
5 Specify the Type of field this will be in the popup: Text box, Pick list, or Option list.
If you select either of the List options, click Add to define the contents of the field’s drop list, using the List
definition dialog. Click Add to populate selections in the Pick list or Option list for this field.
6 Syntax refers to a set of rules governing the format of a field entry. When a user enters a code in a field on the
popup, the code is only valid if it uses a specific format. Syntax enables you to define whether the code for each
field should be composed of alphabetic and/or numeric characters and whether the length of that code should be
fixed or of variable length.
If you enable Zero fill for the current field, in the Length field, enter the number of characters the entry in the
current field should have, including the zeros preceding the code.
If you enable Syntax for the current field, in the Mask field, enter the appropriate codes for the desired field entry,
based on the syntax format options shown in the following table.
Entry length # Specifies an exact entry length, where # is a number from 1-99, inclusive.
#-## Specifies a range of lengths, where # is the minimum value for the range,
and ## is the maximum value. The range must be from 1-99, inclusive,
with minimum and maximum values separated by a hyphen.
Specific positioned “X Specifies that a certain character (X) must be included in the entry; any
character character can be used.
If you enable Syntax for the current field, the Error message field enables. In this field, enter an intuitive phrase to
help users correct an inaccurate syntax entry.
b Specify a Subjob value for this field. This option is only accessible if you enable Subjobs in the Legacy options.
See Legacy Configuration Options in the Popup Designer on page 361 for details.
c Select a DMS data type from the drop list to identify the DMS field containing the value you want to retrieve
for the current field. If the current field is the Client field, for example, and the DMS database stores client
values in a field called ClientCode, select the ClientCode field from the drop list.
d If you configure your DMS as an application class that hides the popup on the basis of tracking hierarchy, or if
you configure the popup directly to hide for DMS documents, then Equitrac Professional populates the print
popup automatically on the basis of the DMS field values you specify for the DMS-specific application class
popup.
Field Options
Check any and all of the options that apply to each field you assign to the popup. Option availability depends on the
field name and type you specify.
Option Definition
Required This is a required field; users must provide valid data for the server to accept the print request.
Server validation The server validates data entry for this field when the user presses Print on the popup. Invalid data
returns a warning message on the workstation. Disabling this option also disables SmartPrompts.
Users can override field-level validation with temporary settings in the User Tool.
Allow Overrides Allows users to provide their own data for the field in place of the pre-populated data.
Use SmartPrompt Data entry in this field triggers another dialog prompting for additional information. For more
details on using SmartPrompts, see Creating SmartPrompts on page 377. Enabling this option
also enables Server validation, below.
Option Definition
Read only This field is not user-editable in the popup. Data appears for information purposes only.
Security mode Equitrac Professional masks this field’s entries with asterisks, as a security feature. Enabling this
option disables the Show MRU option, below.
Search capability Users can search for valid entries for this field. Enabling this option displays the Search icon next to
the current field.
Show MRU on print Enables users to access a Most Recently Used list of entries for this field. For example, if you enable
client this feature for the Client field, users can view a list of the ten most recently used client codes, and
select the one they want if it appears in the list. Enabling this option disables the Security mode
option, above.
Auto advance field Enable or disable this option to advance to the next field when the user enters a valid code in the
current field. If the user types an invalid code, a status message appears at the bottom of the popup.
If you do not enable this feature, the user manually advances to the next field.
Client/Matter
In this setup, the information in the matter field must be associated with and nested under the information in the
client field. That is, the client and matter have a "parent/child" relationship. This relationship must be defined, and
then the field properties set:
1 In system Manager, click Configuration > Field Mapping. A Field mapping dialog opens.
2 Set Field 1 to matter, and Field 2 to client.
3 Indicate the parent/child relationship of the codes by designating that matter’s parent field is client. Then, click
OK.
4 Click Popup Styles in the main menu, then open a style for editing by double-clicking it in the right pane. If no
popup styles are currently configured, first configure a new one. See General Configuration on page 358 for more
information about creating popup styles.
5 Create a popup style containing input fields for both client and matter.
NOTE: The popup must list client first, before prompting for matter.
6 Define both client and matter fields in the popup style. This requires users to enter codes for both fields in their
workflow.
3 Click Popup Styles in the main menu, then open a style for editing by double-clicking it in the right pane. If no
popup styles are currently configured, first configure a new one. See General Configuration on page 358 for more
information about creating popup styles.
4 Define only a matter code field in the popup style.
Unique matter within client/matter
In this setup, when users provide a matter code, the respective client code is automatically associated:
1 Define field mappings as described in steps 1 and 2 under Client/Matter above.
CAUTION: The “Unique Matter” control for Equitrac Professional 5 is not available in System Manager. To enable
“Unique Matter” functionality, you must contact Equitrac Support for assistance.
2 Click Popup styles in the main menu, then open a style for editing by double-clicking it in the right pane. If no
popup styles are currently configured, first configure a new one. See General Configuration on page 358 for more
information about creating popup styles.
3 Create a popup style containing both client and matter, or only matter. If you define only a matter field, Equitrac
Professional 5 automatically links the client code associated with the provided matter code and transactions are
associated with both codes properly.
1 In the Speed Buttons section, click Add to add a button to the list. Use the Up/Down buttons to change the Speed
Buttons position in the list.
If you have enabled Subjobs for this popup style, provide the validation values for each of the configured fields for
the Subjob account. This option is only available when you enable Subjobs, and you must specify both main and
Subjob values for each of the defined fields.
If you enable Subjobs for this style, you can use secondary accounts with each Speed Button by specifying the
number of copies assigned to the main account, after which Equitrac Professional will charge the secondary
account.
NOTE: This setting supersedes the value you assign to charge splitting if using Subjobs. For example, if the global
setting is for five prints to the main account before charging a Subjob account, and you define this Speed Button to
charge the Subjob account after two prints, then Equitrac Professional uses this setting instead of the global setting.
1 In System Manager, navigate to Client config > Popup styles, and click on the User-Client-Matter style.
2 In the Fields section, double-click the desired UserCode, Client or Matter entry.
3 In the Prompt field dialog box, uncheck the Show MRU on PrintClient option, and click OK.
4 Repeat this for all fields which you do not want to show the MRU list.
5 Click OK to close the Popup style dialog.
"HideHistory"=dword:00000001
"HideSpeedButtons"=dword:00000001
"HideHistory"=dword:00000001
"HideSpeedButtons"=dword:00000001
5 For any machine on which you have already installed the client popup, stop and restart the EQ Shared Engine
service to enable the client popup to display the new graphic.
Creating SmartPrompts
Use SmartPrompts to gather additional accounting information for particular codes used on the client popup for print
transactions. Equitrac Professional does not validate data entered through SmartPrompts, and does not require
SmartPrompts to submit a print job.
NOTE: If you require information on configuring or using SmartPrompts for Control Terminals, please refer to
Control Terminal SmartPrompts on page 281.
When you assign a SmartPrompt to a particular field in the popup, an additional dialog appears when the user enters
the selected trigger code. The user then enters additional data in the SmartPrompt dialog.
To use SmartPrompts:
• popups for print jobs must not be disabled (see Disabling Popups on page 349)
• you must have custom validation types defined for available fields (see Modifying Field Names and Descriptions
on page 83)
NOTE: The client popup can hold and send 255 characters, though the dialog only displays a maximum of 65
characters. This could result in a discrepancy between what the user enters in the SmartPrompt and what is stored in
the database. For example, the document description “15 copies/Appeal notification/State v. Smith” is 45 characters
long and would be cut off by field length restrictions in the CAS.
3 Provide a descriptive name for this prompt. The name describes the criteria that triggers the SmartPrompt, such as
(in the example shown) a user entering a non-billable code for a print request.
4 Provide a label for this SmartPrompt. This is the text that will appear to the user in the popup.
5 Specify any relevant default value for this prompt, if applicable.
6 Specify the popup field to which this SmartPrompt maps. This is the popup field that triggers the SmartPrompt if
the user enters data matching the criteria you identified in the first column.
7 Check the Prompt if non-billable option to force the popup to show a SmartPrompt if the associated field entry is
flagged by the control system as non-billable. For example, the control system may flag a particular client code as
non-billable; if Equitrac Professional recognizes the non-billable flag, this option forces the SmartPrompt for the
Client field on the popup.
8 Click OK to save the settings, or Cancel to close the window without saving changes.
To remove any of the SmartPrompts you have configured, right-click your selection in the list and select Remove from
the menu.
Removing a SmartPrompt
Right-click on any list item with an assigned SmartPrompt, and select Remove SmartPrompt assignment from the
menu. Confirm the removal when System Manager prompts you.
1 Double click the icon in your tooltray. A Print Client user settings dialog displays.
2 Under Popup behavior, select Suppress popup for minutes if you wish to withhold the popup from appearing
from a user’s screen when printing. Enter a value in the minutes field.
3 Select Disable field-level validation
4 Click on Clear cache if you wish to clear the cache.
NOTE: On 64-bit operating systems, the Clear Cache button only appears if the currently logged in user has
administrative privileges. This is caused by the User Account Control (UAC) settings of the operating system. When
UAC is enabled, all users, including administrators, must have sufficient rights when launching the EQToolTray
application to display the button. To always show the Clear cache button, you must either disable UAC, or run the
EQToolTray application as an administrator.
CAUTION: Using the Clear cache button clears previously used validation codes from your local cache. The data
cache will be rebuilt over time on its own. Use this option if you want to force a re-validation of all local values. The
cache is resynchronized automatically once a day or upon restart of the Print Client, so a manual clear using this
procedure should only be necessary if there have been many changes made to the validation codes on the server in
the last 24 hours and if you feel that they must be reflected in the local print client cache.
5 Select Show Print Client evaluation dialog if you want to see detailed Equitrac Professional evaluation logic to
determine if the popup should show and what values will be pre-filled in its fields.
6 Select Allow print proxy to release jobs if held to change the default value displayed on the print popup. This
option only displays if a user has print proxies and is printing to an SDR printer. If selected on the popup, by
default print jobs to printers with SDR enabled have this option selected, allowing proxies to release print jobs. If
deselected, by default the option is deselected on the print popup, and proxies are not able to release print jobs for
the user.
7 Click OK.
NOTE: The popup’s Easy Search Show/Hide feature, and the History recall buttons, are not configurable in the
popup design. You can enable or disable search and most recently used (MRU) features on a field-by field basis only.
In the popup, the History and (if configured) MRU buttons will display a maximum of the ten most recently used and
validated codes.
6 Specify whether Equitrac Professional will treat this test transaction as a DMS document or not.
7 Specify the total pages and copies for the test transaction.
8 Click Close.
When you have entered values as necessary, one of two things will happen. Either:
• The popup you configured for that class displays.
—Or—
• If you have configured the popup to hide for the conditions you applied in the preview dialog (for example, if
you configured Equitrac Professional to hide the popup for DMS documents, then specified a DMS document
in the test scenario), Equitrac Professional displays an error message stating that the popup will not appear for
the specified test data, as well as an explanation stating why.
CAUTION: When you do the test prints and the Equitrac Professional client popup appears, the application from
which you have printed will be unresponsive, as the popup interrupts it until the print job finishes or you cancel the
job.
Moving the client popup around within the application you have printed from may result in “drawing” problems
where portions of this interrupted application window fail to redraw or appear erased. This will only affect the
application from which the user has printed, and which the client popup has interrupted. Other applications already
open, and any applications the user opens with the client popup active on the desktop will be responsive and
unaffected by the popup.
The user cannot minimize the client popup, though they can minimize the application from which they are printing.
Users may want to move the client popup to the corner of their desktop until which time they are ready to complete
or cancel the print job.
Topics:
Web Client Prerequisites
Setting Default Web Client Preferences
Creating System Filters
Loading Custom Reports
The Equitrac Professional Web Client is both an administrative tool for running reports and a data entry tool for
entering disbursements. As an administrator, you must enable certain configuration settings to allow users to access
the Web Client.
You may also need to inform your users how to access the Web Client. This chapter provides information about
configuration settings required for the Web Client and for using the Web Client to view the current system status.
For information about scheduling auto-generated reports, refer to the Equitrac Professional Usage Guide.
2 In the Permissions dialog, click the permission group link you want to configure.
3 Use the Select Group dialog to choose groups that have access to the selected Web Client function.
4 Verify that your new selection shows in the Configure access permissions section, and click OK.
NOTE: The Record Limit value can be overridden to limits up to 4000. If the value is set higher, Equitrac Professional
returns the value to the default of 1000.
Option Description
Name When this option is selected, the Web Client displays validation data suggestions alphabetically by
name.
Description When this option is selected, the Web Client displays validation data suggestions alphabetically by
description.
None When this option is selected, the Web Client does not offer validation data suggestions.
Search When this option is selected, the Web Client suggests validation data that begins with the
characters entered into the field. For example, typing “Gr” in the Client field would result in “Green
Tree Consulting” and “GRC Inc.”
Scan When this option is selected, the Web Client suggests validation data that contain the characters
entered in the field. For example, typing “Gr.” in the Client field would result in “Green Tree
Consulting” and “Bedrock Aggregates.”
Select the
transaction
type
If you need to delete a row, select the checkbox to the right of the row and click the Delete Row button.
8 Select the System Filter checkbox.
9 Click Save to close the Add Filter dialog.
4 Enter the report file name, without the .rpt file extension. This name must be identical to the file located in the
C:\Program Files\Equitrac\Professional\Web\Reports. For example, if you create a report called
custrpt.rpt, you must enter custrpt in the report file name text box.
If the file name is not identical, the Web Client will not locate and load this report.
5 Enter a Display Name that is used in the Web Client when a user views this report.
6 Choose a Format for the report.
7 Select a Subject.
8 If you prefer to view the report in graphical format, check Graphical Report.
9 Click OK to launch a task in the background that updates the CAS with this report.
NOTE: Some report labels, such as the Company Name, are retrieved from existing system information. This
information was provided when Windows was installed on the workstation. To change these labels, your system
administrator must change the name in the Windows Registry. In the case of Company name, the associated value is
found in the registry at HKLM\SOFTWARE\Microsoft\Windows
NT\CurrentVersion\RegisteredOrganization. Changing registry entries can have undesireable
consequences, and as such should be thoroughly evaluated prior to being made.
Topics:
Disbursements Setup Workflow
Define Disbursement Types
Define Disbursement Price Lists
Define Disbursement Classes
Control Disbursement Access
Define Disbursement Price List Selection Rules
Maintain Disbursements
Equitrac Professional can accommodate cost recovery for firm-specific charges. Chargeable costs such as those
associated with mailing letters, taxi fees, courier charges or client meals, are costs your enterprise likely wants to track
and recover from clients. Such costs are referred to as disbursements. Equitrac Professional enables you to define your
own disbursement types and classes specific to your enterprise.
This chapter provides information about:
• creating disbursement types.
• creating disbursement classes.
• controlling access to disbursement types and classes.
• creating disbursement price lists and defining default price lists.
• creating price list selection rules for disbursements.
• maintaining disbursement types and classes.
2 In the Disbursement types list, right-click All Disbursements and select Add Type from the menu. The
Disbursement type dialog box opens.
5 Click OK to save the changes and return to the Disbursement type configuration and access permissions dialog
box.
NOTE: To create Disbursement Price Lists, you must first have at least one disbursement type defined. See Define
Disbursement Types on page 391 for details.
Disbursement Surcharges
Disbursement types do not allow implementation of tiered or incremental costing. To simulate tiered pricing schemes,
use surcharges. Equitrac Professional applies surcharges sequentially, assuming the relevant criteria match.
There are two types of disbursement surcharges:
• price per item surcharges
• total cost surcharges
Price per item surcharges are available for disbursement price lists with the following pricing scheme: item price x
quantity (price specified by user; x item price specified by administrator).
Total cost surcharges are available for all disbursement price lists with all disbursement types.
The Disbursement surcharges dialog box allows you to add a wide range of surcharge combinations, with percentage
or fixed adjustment. Equitrac Professional applies surcharges in the order in which they appear in the Price per item
Surcharges box.
For example:
5 7 Fixed 0.5
6 ALL Percentage 10
Equitrac Professional enables the use of negative values in the surcharge calculations. Negative values, such as -10
appear as (10).
11 20 Percentage (10)
0 5 Fixed 0.1
a The Item Price Surcharges section is available when you enable the Number of items field prompt in the
selected disbursement type’s Disbursement type dialog box.
The Price per item surcharges section contains a grid that enables you to define surcharges on the item price.
Surcharges are applied in the order in which they appear in the grid. The following types of adjustments can be
made.
Fixed Specify a numeric range of items to which this surcharge should be applied in the
From and To columns of the grid. Select Fixed in the Action column. Specify a
constant value by which item price should be adjusted.
To enter a discount, enter a negative number. For example, entering -5 will give a
discount of 5 dollars, and will appear as (5.00) in the action column.
Percentage Specify a numeric range of items to which this surcharge should be applied in the
From and To columns. Select Percentage in the Action column and specify the
percentage the item price should be adjusted.
To enter a discount, enter a negative number. For example, entering -5 will give a
discount of 5%, and will appear as (5.00) in the action column.
b In the Total cost surcharges section, enter a Fixed surcharge to adjust the total cost value by a dollar amount,
and a Percentage surcharge to adjust the total cost by a certain percent.
Total cost surcharges can be specified for both Price per Item and total cost pricing schemes. If both schemes
are used, Equitrac Professional will adjust the item price, calculate the total cost and then apply the total cost
surcharges respectively.
c Click OK to save your settings and close the Disbursement surcharges dialog box.
CAUTION: Equitrac Professional only supports English (United States) as the Region Format for disbursement
surcharges. Changing the Region settings and then editing disbursement price lists can cause transactions to be
costed incorrectly.
7 Click OK to close the Disbursement price list dialog box and save your settings.
WARNING: You must have at least one price list set up and associated as the default for each disbursement type
before disbursement entries are priced. If you do not have a default price list assigned for a disbursement type,
disbursements entered for that type will have a cost of $0.00 regardless of whether the user specifies all cost
information.
NOTE: Disbursement classes are supported on TPCs and the Web Client.
3 In the Name field, enter a value to be displayed to users when they select a class. Use an intuitive, unique name that
suggests the disbursement types hosted in the class. For example, "Binders".
4 In the Description field, enter a brief description of the disbursement types this class holds. This value is displayed
to users on TPCs to help them quickly select the correct disbursement type. For example "All binder types from
copy center".
5 Click OK. The new disbursement class appears in the Disbursement types list under All Disbursements as a
folder, in alphabetical order.
6 Add disbursement types to the new class either by right-clicking the class and adding a new type (see Define
Disbursement Types on page 391) or by clicking and dragging existing disbursement types into it (see Moving
Disbursement Types on page 403).
3 Select the classes or types to assign permissions to, then in the Access permissions list, click <Add...>. The
Disbursement access permission dialog box opens.
4 From the Access group type drop-down, select the group type assigned to this disbursement class or type:
• TPC config set assigns permissions to specific TPCs.
• User assigns permissions to specific users.
• User class assigns permissions to specific types of users.
• User’s location assigns permissions based upon the location assigned to the logged in user.
5 Depending upon which access group type you chose, assign an Access group or user name:
• For TPC config set access groups, select the particular configuration set from the drop-down list, or <All TPC
config sets> to allow all.
• For User access, enter the network user name of the user, as it appears in the Users pane, into the field.
• For User class access groups, select the particular User class from the drop-down list, or <All user classes> to
allow all.
• For User’s location groups, select a defined location from the drop-down list, or <All locations> to allow all.
6 Click OK. The Name and Group type of the permission appears in the Access permissions list.
NOTE: You can add multiple access permissions to each disbursement class or type, however, once you add a
discrete access group type it is removed from the drop-down list to prevent its addition to the same disbursement
classes or types.
Clearing Permissions
You can remove the access permissions to disbursement types or classes. Removing access permissions by class
removes the permissions from all types that inherit them from the class. Any individually assigned permissions
remain.
To clear permissions, do the following:
1 In System Manager, navigate to System > Configuration > Other settings > Disbursement types. The
Disbursement type configuration and access permissions dialog box opens.
2 In the left pane, click the disbursement type or class you want to modify. Its Access permissions display in the right
pane.
3 In the right pane, right-click the access permission you want to remove and select Remove from the menu. You
can also press DELETE while the access permission is selected.
6 In Price List Selection Criteria section, click <Add...> to open the Criteria Settings dialog box and add the
criteria set.
Maintain Disbursements
To keep your system relevant and up-to-date, you may need to edit or remove disbursement types, price lists, and
price list selection rules. This section describes editing and removing disbursement types only. Disbursement price
lists and price list selection rules are maintained in the same way as regular transaction price lists and price list
selection rules.
Editing Disbursements
To edit the information for a disbursement type, do the following:
1 In System Manager, navigate to System > Configuration > Other settings > Disbursement types. The
Disbursement type configuration and access permissions dialog box opens.
2 Select an existing disbursement type from the listing to open the Disbursement type dialog box. Make any
changes necessary. For an explanation of the editable fields, see Define Disbursement Types on page 391.
3 Click OK to save the changes and return to the Disbursement types configuration and access permissions dialog
box, or click Cancel to close the dialog box without saving the changes.
NOTE: If you try to edit a disbursement type after applying one or more price lists to it, the Disbursement field
prompts options (Number of items, Price per item, and Total cost) become unavailable in this dialog box. You
cannot make changes to the prompt fields, since you already have defined price lists that rely on these settings. You
must remove the price list associations before you can edit these fields.
You may instead prefer to define a new Disbursement type with the desired field prompt options.
Removing Disbursements
If you no longer require a particular disbursement type, you can delete it from the database. When you delete a
disbursement type, you can no longer assign that type to new transactions. However, if you delete a disbursement type
assigned to existing transactions, those transactions are unaffected.
To delete a disbursement type, do the following:
1 In System Manager, navigate to System > Configuration > Other settings > Disbursement types. The
Disbursement type configuration and access permissions dialog box opens.
2 Right-click an existing disbursement type from the listing and select Remove from the menu.
NOTE: If you try to delete a disbursement type after applying one or more price lists to this type, the CAS returns an
error message. You must remove all price lists associations from the selected disbursement type before you can
delete the disbursement type itself.
Topics:
Exception Editing Configuration Workflow
Configuring E-mail Notification
Managing Exception Rules
Auto-charging Exceptions
An exception is a transaction that is missing or contains invalid validation data required by the time and billing
system, or otherwise fails to meet requirements for a complete transaction. For example, if a user prints a document
without specifying the matter code and the popup configuration does not validate user-entered data against CAS,
Equitrac Professional records the transaction but cannot post it to the time and billing system because of the missing
data. It marks the transaction as an exception and the user, or his proxy, must use the Equitrac Web Client to add the
missing matter code.
Equitrac Professional uses rules to determine the status of transaction data before posting the data. You can create
your own rules to determine which transactions can be posted to the time and billing system automatically and which
need to be reviewed or modified before being posted. For your convenience, Equitrac Professional provides a number
of default exception rules. You may edit, deactivate, or remove these rules as necessary to suit your business practices.
This chapter provides information about managing exception rules in System Manager.
NOTE: Before you configure exception emails, ensure you have defined the email server and “Mail from” address for
any system-generated emails. See Configuring the Mail Server for Email Notices and Reports on page 70 for
details on defining these system options.
NOTE: Equitrac Professional bases exception rules on a default association of client/matter data. If you change any of
the field mapping (for example, changing the name of the Client field to Client Account Code), it is also your
responsibility to update the relevant field names for any related transaction exception rules.
NOTE: There are also dependencies for certain exception rules. If you deactivate the “Matter is empty” and the
“Matter is not valid” exception rules, the “User Location not equal to Matter location” exception rule will not work in
the Web Client for reprocessed transactions.
WARNING: New transaction exception rules must be enabled manually. For more information on manually enabling
TERs, see Activating an Exception Rule on page 412.
WARNING: Make sure to select the exception rule by clicking on its transaction state and not the name of the
exception rule itself. If you select the name of the exception rule, a dialog box will be shown.
State Description
Non-exception Transactions meeting the rule criteria are not exceptions and should be posted to
the time and billing system.
Exception Transactions meeting the rule criteria are exceptions and should not be posted to
the time and billing system until they have been fixed in the Equitrac Web Client.
Do not care exception Transactions meeting the rule criteria are exceptions and should not be posted to
the time and billing system but do not need to be fixed in the Equitrac Web Client.
Requires approval exception Transactions meeting the rule criteria are exceptions and should not be posted to
the time and billing system until a designated person has approved the transaction
in the Equitrac Web Client.
6 Use the Transaction exception criteria section to define the criteria for the rule:
a Click Add to open the Criteria Settings dialog.
b Select an Attribute from the drop list. The attribute drop list displays all relevant criteria that can apply to the
selected transaction type.
c Select an Operator from the drop list.
NOTE: The list of operators displayed depends on the Attribute you selected. For more information, see Attributes
and Operators in Rule Behavior below.
d Enter the criteria the transaction must match for the rule to apply.
e Click OK to accept your new criteria and close the Criteria Settings dialog.
f Repeat these steps as necessary to add further criteria.
7 Click OK to add the exception rule.
NOTE: When selecting transaction date range dates, be advised that the from and until dates include an unseen
timestamp of 00:00:00AM, therefore the date range 10/01/2014 to 15/01/2014 does not include transactions
processed on January 15th. If you wish to include transactions processed on the 15th, select an end date of 16/01/
2014.
Transaction Date X X X X X X X
Device X X X X X X X
Amount X X X X X X X
Page Count X X X X
Matter X X X X X X X
Client X X X X X X X
User Code X X X X X X X
Color X X
App. Name X
Client Workstation X
Submit Username X
Release username X
Auto-charging Exceptions
Equitrac Professional enables you to automatically charge a user’s exception transactions to the client and matter
defined as the personal account for the user.
For more information about configuring users, see Managing Users on page 41.
To configure Equitrac Professional to automatically charge exceptions:
1 In System Manager, navigate to System > Configuration > Equitrac Professional settings > Auto-charge
exception settings.
Topics:
Call Accounting Overview
Call Accounting Configuration Workflow
Obtaining Rate Tables
Creating and Configuring Call Sites
Adding Data Collection Sources
Working with Trunks, Extensions, and Routes
Tracing Phone Data
Equitrac Professional’s call accounting feature provides complete cost management for telephone systems.
This chapter provides information about:
• Key call accounting concepts
• Adding and configuring call accounting Call Sites
• Configuring costing for phone transactions
• Adding call data collections sources, such as buffer devices, databases, and file sources
Netbuffer
CAS Time and
Billing
System
Flat File
Key Concepts
The following concepts are important to understanding how call accounting is configured in Equitrac Professional.
Call Sites
A call site is a CDR data source that is tied to a specific geographic location. Call processing and costing configuration
is specific to each call site in Equitrac Professional, however, you can copy a call site if you have several sites you want
to configure in the same way. Call sites can have an number of trunks and/or trunk groups, extensions and/or
extension groups, and routes associated with them.
• identify the city name of the call destination or the call origin of an incoming call, if Caller ID is available
• cost the call according to the latest commercial tariff rate filed by the communications carrier with the government
regulatory body
Rate tables are provided by subscription. If you have obtained a license to use call accounting with Equitrac
Professional, you have a Subscriber ID that allows you to access Equitrac’s rate table FTP site to retrieve updated rate
tables. A scheduled task is automatically created to retrieve rate tables on a timely basis.
Extensions
Extensions are connected with call sites in Equitrac Professional; they represent a terminal point (usually a phone) of
the telephone system Equitrac Professional is connected to. Extensions are reported in the CDR data for all calls
(except trunk to trunk calls) and can be added in System Manager or learned automatically as each extension is used.
Specific extensions can be excluded from a site and extension groups can be created to apply special call processing
and costing for a set of extensions.
Equitrac Professional links calls to users by their extension, as configured via the Client config > Users link. You can
assign multiple extensions to any single user.
Retrieving Rate Tables from the Equitrac FTP Rate Table Update Server
The simplest way to keep rate tables up-to-date is to create a scheduled task to retrieve them. Equitrac Professional
includes a default scheduled task called Monthly rate table FTP update; you can either use this default task, or create
a custom task.
NOTE: To retrieve rates from the FTP server, communication on Port 21 must be allowed.
To create a scheduled task to obtain the rate tables you need from the FTP server, do the following:
1 In System Manager > Scheduled tasks, click <Add...> and select Add scheduled arbitrary command to create a
new arbitrary command scheduled task.
2 Enter a name and description for the task.
3 In the Command line field, enter the following for 64-bit environments:
C:\Program Files\Equitrac\Professional\Tools\eqrtulauncher.exe /t 1
—Or—
For 32-bit environments, enter:
C:\Program Files (x86)\Equitrac\Professional\Tools\eqrtulauncher.exe /t 1
4 Select how frequently this task should be run from the Schedule drop-down list. Carriers update their rates on a
quarterly basis, so you will probably want to run this task monthly.
5 Leave the Start date as the current date, but set the Start time to at least a few minutes from the current time.
6 Select when Equitrac Professional should run the task in the future.
7 Click OK.
Equitrac Professional runs the task at the scheduled time and retrieves the rate tables from the FTP server and load
them to the database. Rate tables are stored in C:\Documents and Settings\%User%\Local
Settings\Application Data\Equitrac\Equitrac Platform Component\5\EQCPSrv\RawRates.
NOTE: It may take several minutes for the rate tables to be retrieved.
Password: rtclient
ftp> cd rtupdate/partnerScripts
6 If you wish to treat calls to some area codes as local calls even if they are not recognized as such by the commercial
tariff rate table, enter those area codes (separated by commas) in the Treat these NPA’s as local field.
Basic Costing
The Basic costing tab allows you to set standard parameters for calls for this call site. Use the field descriptions below
to configure basic costing.
Cost multiplier
Equitrac Professional uses the cost multiplier to adjust the computed cost of a call. For example, to charge an
additional 10% for all calls, set the cost multiplier value to 1.10. To apply a 20% discount to all calls, set the cost
multiplier value to 0.80.
This multiplier is applied last and therefore adjusts any other entered costs or multipliers set on the Special Costing
tab. For more information about special costing, see Special Costing on page 423.
Minimum duration
This is the minimum duration of a call, in seconds, before it will be considered for costing and promotion to a
transaction. This parameter is evaluated after the dial delay (see below) has been subtracted from the actual duration
reported by the telephone system.
Dial delay
This is the number of seconds to be subtracted from the actual call duration reported by the telephone system before
costing the call. This parameter is used to account for dialing and ringing time, since many systems report the call
duration from off-hook to on-hook including the dialing and ringing time. This parameter is used to adjust the call
duration before the call is checked against minimum duration (see above).
Initial period
This is the period, in seconds, that constitutes the initial period for fixed and DDD+fixed costing methods (for
information about costing methods see Special Costing on page 423). For by-the-minute fixed rate costing use 60
seconds, for 1/10th-of-a-minute costing use 6 seconds, and for by-the-second costing use 1 second.
Additional period
This is the period, in seconds, that constitutes additional periods after the initial period for fixed and DDD+fixed
costing methods (for information about costing methods see Special Costing on page 423). For by-the-minute fixed
rate costing use 60 seconds, for 1/10th-of-a-minute costing use 6 seconds, and for by-the-second costing use 1 second.
The additional period does not have to be the same as the initial period.
Special Costing
The Special costing tab allows you to set default rates and fine-tune the costing methods and rates for each call type.
Use the field descriptions below to configure special costing.
Costing method
Select one of the following costing method options:
DDD+fixed Call cost is based on the rate table, and initial and additional period costs.
Fixed only Call cost is based on the initial and additional period costs only.
DDD multiplier
Use this parameter to adjust the tariff cost reported by the rate table. This field is only available if the costing method
is DDD+fixed or DDD only. Setting this parameter is a convenient way to specify costing as a percentage of the
commercial tariff rate.
Select the checkboxes corresponding to the call types you want to apply customized costing to. To override the cost
method defined in Basic costing for a call type, click in the Cost method cell and select a new cost method from the
drop-down list. Enter any additional costs as required.
Advanced
Click the Advanced button to access the Advanced call costing parameters dialog. Use this dialog to expose
additional parameters that may not be available in the user interface, but that are nonetheless available to properly
configure call accounting. This editor can be very useful for complicated configuration of trunk groups, routes, and
extension groups, where the user interface only exposes a subset of all the configurable parameters.
NOTE: Advanced configuration is recommended for technicians and advanced users only.
Transactions
Equitrac Professional receives raw call data from the telephone system, parses it, and stores the parsed data as
transactions. Use the Transactions tab to set parameters that control what data Equitrac Professional will store and
post to the time and billing system.
Select the corresponding checkboxes to store and/or post any of the following call types:
Long-distance Long-distance calls are stored by default. This ensures that all long-distance calls are promoted to
transactions and stored in the database. If you choose to post long-distance calls, enter a minimum
cost the call must meet before it is sent to the time and billing system.
Local Local calls include calls to area codes listed in the Treat these NPA’s as local parameter as well as
those determined by the commercial tariff rate table. If you choose to post local calls, enter a
minimum cost the call must meet before it is sent to the time and billing system.
Zero-rated You can store calls that have a zero cost, but otherwise meet the criteria. This could include toll-free
calls, or any other calls that are zero-rated.
Incoming and Zero- If your telephone system exports incoming call information, you can store it and post it to the time
cost incoming and billing system.
Extensions
Use the Extensions tab to register extensions for which transactions should never be generated. For example:
• extensions that are tracked by another system, such as a PageCounter device fax control device
• a modem
• an extension that should not be tracked for privacy reasons
NOTE: Trunk usage information is still collected for these calls, but they will not be costed or promoted to
transactions.
To add an extension to the exclusion list, click Add, then type in the extension. To remove an extension from the list,
right-click the extension and select Remove.
Method Description
By auth. code User is looked up based on the authorization code. If a call has either a blank or an invalid
auth. code, the user is left unassigned.
By user network login User is looked up based on the user’s network login name.
By site & ext. code User is looked up based on the device’s site and the call’s extension.
By site & ext. alt. code User is looked up based on the device’s site and the call’s alternate extension.
By unique ext. code User is looked up based on the call’s extension, ignoring the device’s site.
By unique alt. ext. code User is looked up based on the call’s alternate extension, ignoring the device’s site.
By auth. code or extension User is looked up based on the auth. code. If a call has either a blank or an invalid auth. code,
the user is looked up based on the call’s site and extension.
By alternative reference For flat file data, the flat file may contain some validation other than that described above.
For example, if flat file contains calling card data, the user is assigned based on the calling
card provided in the flat file.
NOTE: When you change a configuration parameter for any CDR source (an ODBC source, for example), you should
wait one minute before retrieving the CDR from the source. The DCE services requires that time to retrieve and
update the data source change. If you try to retrieve the CDR before DCE has a chance to update the source, you will
not get the results you expect.
To use a custom PRS file, create the file and place it in the following directory:
C:\Program Files\Equitrac\Professional\Accounting Service\Redist\
CDRTranslatorParams
NOTE: You would only need to delete data from the database if the transactions are posted to CAS in the first place.
In some cases, you may simply need to fix your parser so non-identification data goes into the correct fields. In this
case, there would be data in CAS. In others, as for the alert above, you would not need to delete data first.
WARNING: Failure to complete this procedure will result in PageCounter CDR devices never communicating with DCE
for Call Accounting.
To change the HTTP Port in the PageCounterCDR.txt file, use the following procedure:
1 Open a browser and connect to the PageCounter’s web administration page at http://<yourPCCDRIPADDRESS>,
replacing the information in the angle brackets with the IP Address of the PCCDR.
2 Click the Download link, logon, and follow the links to Disk1 > PageCounterCDR.
3 Open the PageCounterCDR.txt file and search for Internet Port.
4 Edit this field from “Internet Port”=dword:00000050 to “Internet Port”=dword:00000b7b.
5 Save the changes.
6 Browse back to the terminal web administration page and select Upload.
7 Browse the location to which you saved the PageCounterCDR.txt file.
8 In the next drop-down list, select the PageCounterCDR folder.
9 Click Upload.
10 Click the Restart link, and confirm that you want to restart the terminal. The change takes affect when the
terminal restarts.
12 Click OK to add the PageCounter CDR data source to the call site.
NOTE: For NETBuffer devices to work correctly with Equitrac Professional, they must be running firmware version
3.70. For information about upgrading firmware, refer to your NETBuffer device documentation.
8 Select the Reject unknown extensions checkbox to cause all calls to and from extensions that do not exist in the
extension list for the call site to be discarded.
9 Select the Inactive device checkbox to indicate that the PageCounter CDR is inactive.
10 In the Raw CDR translation section, select whether you will use WinSMDR.exe to translate CDR data or a custom
translator. If you are using a custom translator, click the ellipsis button (...) and browse to the custom translator
executable. Enter any additional parameters that should be included on the command line when Equitrac
Professional runs the translator in the Extra parameters field.
11 Enter the IP address of the NETBuffer device.
12 In the Channel settings section, enter the following values:
Field Description
Server port IP port number that the CAS is listening on for communication from the device. Set this to
zero (0) to allow the CAS to choose an appropriate port number.
Client port IP port number that the device is listening on for communication from the CAS. By default,
NETBuffers use port 2062. This value cannot be zero (0).
Encryption key The key used to encrypt data flowing between the CAS and the device. This value is always
in uppercase characters.
Poll interval Specifies, in seconds, how often the CAS will poll the device for CDR data. Setting the
interval to zero (0) disables the automatic poll.
Survey interval Specifies, in seconds, how often the CAS will survey the device for information (device
status, error logs, etc.) Polling the device includes a survey.
Broadcast window Specifies how many records can be sent before a checkpoint is performed. This parameter is
size used to fine-tune broadcast performance on a noisy network.
Data timeout Specifies, in milliseconds, the timeout when waiting for a response from the device.
Data retries The number of times to retry device packets if the operation fails.
NOTE: After adding or making a change to an ODBC data source, you should wait one minute before retrieving the
CDR from the source. The DCE services requires up to one minute to retrieve and update the ODBC data source
change. If you try to retrieve the CDR before DCE has a chance to update the source, you will not get the results you
expect.
1 In System Manager > Call accounting, right-click the site you want to add the data source to and click Add
ODBC incoming source.
9 In the Poll interval field, enter the number of minutes Equitrac Professional should wait before polling the
database for new data.
10 Select the Inactive device checkbox to prevent Equitrac Professional from polling the database at this time.
11 In the Raw CDR translation section, select whether you will use WinSMDR.exe to translate CDR data or a custom
translator, and if the latter, select the custom translator executable. Enter any additional parameters that should be
included on the command line when Equitrac Professional runs the translator in the Extra parameters field.
12 In the ODBC source settings section, enter the DSN, User name and Password for the database where the CDR
data is stored. If you have not created a DSN, or you need to modify one you have created, click the ODBC admin...
button to launch the Windows ODBC Data Source Administrator dialog. You can also test the ODBC connection
by clicking the Test button.
13 In the Fetch SQL script field, enter the script to use to fetch the data from the database. You can start by selecting
a template from the Load template from field and customizing the script for your database.
14 If you want the records returned to be sorted by a particular field, enter the field name in the Ordered by field
name field.
15 The Last ordered by value field is updated automatically with the timestamp of the last call record fetched from
the database. Change the value of this field if you want to fetch older records from the database. If this field is
empty, all the data in the database is retrieved.
4 The Call site field automatically displays the Call site you selected to add the file source to, but you can select a
different call site, if necessary.
5 Select a User lookup method. For more information about user lookup methods, see User Lookup Methods on
page 427.
6 Select the Convert date/time of call records from UTC checkbox to convert the date and time of call records from
Universal Time Code to you local time based on the built in GMT offset in the rate table.
7 Select the Reject unknown extensions checkbox to cause all calls to and from extensions that do not exist in the
extension list for the call site to be discarded.
8 The Auto feed data checkbox is selected by default. Clear this checkbox if you do not want the DCE to process the
file data automatically.
9 In the Poll interval field, enter the number of minutes Equitrac Professional should wait before polling the file for
new data.
10 Select the Inactive device checkbox to prevent Equitrac Professional from polling the file at this time.
11 In the Raw CDR translation section:
a Select whether you will use WinSMDR.exe to translate CDR data or a custom translator, and if the latter, select
the custom translator executable.
b Enter any additional parameters to include on the command line when Equitrac Professional runs the
translator in the Extra parameters field.
c Enter the file path for the source file, or click the ellipsis [...] to browse to the file.
Managing Trunks
When Equitrac Professional is configured to learn trunks, new trunks that it encounters are placed in the default
Unassigned trunks group. When you have created trunk groups you can move trunks into those groups by dragging
and dropping the trunk on the trunk group. You can also create trunks manually in a trunk group.
To create a trunk manually, right-click on a trunk group (or the default Unassigned trunks group) and select Add
trunk. Enter a name and description for the trunk. Select the Do not store calls for this trunk checkbox if you do not
want calls from this trunk to be processed and promoted to a transaction.
To remove a trunk, right-click on the trunk and select Remove trunk.
Managing Extensions
When you configure Equitrac Professional to learn extensions, it places new extensions that it encounters in the
default Unassigned extensions group. When you have created extension groups you can move extensions into those
groups by dragging and dropping the extension on the extension group. You can also create extensions manually in an
extensions group.
Follow these steps to create an extension manually:
1 Right-click on an extension group (or the default Unassigned extensions group) and select Add extension.
2 Enter the extension Code, and optionally, an description for the extension.
3 Enter an Alternative code for this extension, if necessary.
4 In the Assign to user field, enter the user name of the user this extension belongs to. Click the Verify button to
verify that the user name you entered exists in the CAS.
5 If this is the primary extension for the user, select the Set as primary extension checkbox.
To remove an extension, right-click on the extension and select Remove extension.
3 In the Raw digits to match field, enter the exact digits that define when this route applies. These digits must
include any passive access codes already absorbed.
4 In the How many digits to absorb field, enter the number of digits that should be stripped from the digits dialed
to process the route properly.
5 In the Digits to prefix field, enter the digits that should be inserted at the beginning of the effective digits dialed to
prepare the call for costing.
6 If the call processing and call costing need to be adjusted further for this route, select the Customize costing for
this route checkbox to enable the Services and Custom rates tabs. For information about using these tabs, see step
4 in Creating and Configuring a Trunk Group on page 436.
Topics:
About Desktop Print Tracking
Desktop Printing Configuration Workflow
Excluding Applications
Workstation devices are printers that Equitrac Professional tracks using the Desktop Printing feature, which is
available as part of the Equitrac Professional Client installation. Desktop print tracking tracks print jobs from any
printer you can connect to a client workstation that does not connect to an Equitrac Professional print server. This
includes local printers on a workstation desktop, or printers using LPT1, USB, or direct network connections.
Desktop print rules enable you to control whether users can print a document to their workstation printer or whether
the job is directed to a network printer based on the job’s attributes.
When tracking desktop printing, you can create and maintain an application exclusion list, which excludes print
tracking for documents printed from specified applications.
••user
user verification
verification
••print
print charge calculations
charge calculations
••output
output tracking
tracking
The Desktop Port Monitor intercepts print requests to the local printer
Desktop Printing supports dual pricing on a per-page basis, and advanced price lists tracking. Desktop print tracking
does not support charging for attributes such as duplexing or page size.
CAUTION: Charging for color attributes is also possible but depends on the properties of the printing application
and the printer driver. If the application and print driver do not differentiate between color and monochrome pages,
color attribute charges for desktop print jobs will not be accurate.
The client popup appears only on the workstation connected to the printer. Users printing to a shared desktop printer
do not see the client popup.
Support for desktop print tracking is installed automatically with the client popup, but requires a Workstation Client
license for activation. When you have installed the client popup and have an available Workstation Client license,
printers local to the workstation are ready for use within your Equitrac Professional environment.
Excluding Applications
The exclusion list specifies applications that Equitrac Professional does not track, and is applicable to all desktop
printer clients (non-DRE printing only). All desktop applications that are included for tracking must be part of an
existing application class in Equitrac Professional. For information about creating application classes in Equitrac
Professional see Creating and Maintaining Application Classes on page 350.
When Equitrac Professional evaluates a print transaction, it first checks whether the document originates with a
tracked application or an excluded application. If the application is on the Excluded list, Equitrac Professional
proceeds with the print and does not track any transaction or document data. If the application is included for
tracking, Equitrac Professional assesses the document data to assign the appropriate tracking and popup behaviors.
NOTE: You must register applications in Equitrac Professional before you can assign the application to the Exclusion
list. Once you exclude an application from tracking, it no longer appears in the Applications view in System Manager.
For more information on adding applications, see Registering Tracked Applications Manually on page 353.
NOTE: If applications on workstations appear to function incorrectly, add the application to the Exclusion list.
2 Click Add to specify an application for Equitrac Professional desktop printing to exclude.
3 Enter an Application Name and Description in the fields and click Add. The application excluded from print
tracking displays in the Additional excluded applications list.
4 Click OK to save the changes, or Cancel to close the window without saving the changes.
Topics:
Handling DMS Documents
Configuring Equitrac Professional For DMS
Integration
Equitrac Professional integrates with select third-party Document Management Systems (DMS), to enable print
tracking and data collection for documents that users generate from these applications. Supported systems include
Hummingbird (DM and DocsOpen), Autonomy iManage, Worldox, and ProLaw. Equitrac Professional with DMS
integration supports multi-copy intervals, charge splitting, and Subjobs.
You can configure Equitrac Professional to collect data from a DMS document and automatically pre-fill the popup
with chosen values from the document's profile. Depending on your DMS vendor, these values may include (but are
not limited to) client, matter, author, document name, and description. Equitrac Professional extracts client and
matter data directly from the DMS, not from the user.
Once you have integrated your DMS with Equitrac Professional, you can configure popup behaviors for DMS
documents, and apply the popup style to the relevant User Classes in System Manager. If you do not configure
Equitrac Professional to track print transactions by any other means (for example, by user class or device), the system
defaults to tracking transaction data by DMS.
For the DMS integration to function properly, you must already be running your DMS software. When you change the
DMS settings in Equitrac Professional, the change will take effect on a user’s workstation the next time a user prints a
document from your DMS.
NOTE: The information in this chapter pertains only to print DMS integration. For information about scan DMS
integration, please see the Equitrac Professional Scan Solutions Guide
NOTE: We recommend installing any Application Integrations from third party document management systems.
These integrations may help Equitrac Professional achieve better document matching and enhance the abilities of
features such as Verify document name. Integrations are most useful in deployments that use multiple libraries.
When configuring the authentication mode in System Manager, you have the option of using a trusted connection, or
of supplying a default user name and password. If your DMS uses Windows authentication, select the trusted
connection option; when Equitrac Professional accesses the DMS to obtain document details, the DMS allows access
based on the Windows user currently logged in to the client workstation. If your DMS does not use Windows
authentication, supply the user name and password of a valid DMS user. When Equitrac Professional accesses the
DMS to obtain document details, the DMS allows access based on this user name-password combination.
The DMS grants access based on the user type of the user name-password combination you provide. If you provide the
user name and password of a user with restricted access to the DMS data, Equitrac Professional may be unable to
retrieve the data you require. If the DMS does not recognize the user name and password, Equitrac Professional
cannot retrieve DMS data at all.
To configure Equitrac Professional to integrate with your DMS, do the following:
1 In System Manager, navigate to System > Configuration > Equitrac Professional settings >DMS configuration.
The DMS configuration dialog opens:
2 In the DMS field, select the desired DMS from the drop-down list. When you select a DMS, the Configure button
becomes active if additional DMS-specific configuration is available.
3 Select the Rename print jobs using DMS field value checkbox, then select the field value you want to use from the
drop-down list. This field is used with secure document release and follow you printing, and substitutes the file
name of the file with the selected associated field (in this case description) of the file from the DMS, making it
easier for users to identify documents.
4 Click Configure to open a DMS-specific configuration dialog.
5 Configure the desired authentication option as follows:
• In the Authentication section, select the Trusted option.
—Or—
a In the Authentication section, select the Login required option.
b In the User name field, enter a valid DMS user name.
c In the Password field, enter a valid DMS password.
6 If necessary, specify the DMS servers you want to integrate (applicable for integration with iManage only):
a In the Servers section, click the Add link.
b Enter the name of the desired DMS server.
c Repeat steps a - b to specify additional servers, as necessary.
d In the Authentication section, specify either the Trusted or Login required option.
e If you select Login required, provide a valid DMS user name and password.
Display popup The popup appears as per the popup behavior and rules you configure; User Class
Equitrac Professional gathers all document transaction details and costs, Device Class
and posts the transaction to the control system.
Application Class
Hide popup The popup does not appear to the user; Equitrac Professional applies the User Class
configured default hide mode values configured for the popup style Device Class
assigned to this class in the background, and posts transaction details to
Application Class
the control system without user intervention.
Silent tracking for The popup does not appear to the user; Equitrac Professional collects all User Class
device management transaction data including costing, and posts the transaction to CAS only. Device Class
only You can run reports later detailing device performance on the basis of this
Application Class
data, but it never appears in the control system database.
You do not require a popup style for any class to which you will assign silent
tracking.
Do not track The popup does not appear to the user, and Equitrac Professional collects User Class
no data on the transaction whatsoever. This option is applicable only to Device Class
non-DRE printing in Equitrac Professional 5.7.
Application Class
You do not require a popup style for any class that you will not track.
Determined The tracking behavior is determined by the next level in the tracking User Class
elsewhere hierarchy (either the device or application level). Device Class
The tracking hierarchy determines whether the popup uses the application, device, or user class’ tracking behavior. For
information on the tracking hierarchy, see Print Tracking Hierarchy on page 346.
NOTE: Equitrac Professional does not track print transactions sent from a DMS viewer. If you want to track DMS
documents, instruct your users not to print directly from the DMS viewer; instead, they should use a document
authoring tool, text editor, or other similar application.
When you have integrated Equitrac Professional with a DMS, two additional settings influence the popup’s behavior.
Unlike the tracking behavior settings applied to each application, device, or user class, these additional settings are
specific to each individual popup style. Equitrac Professional evaluates these settings after evaluating the tracking
hierarchy. Therefore, these settings may override the previously determined tracking behavior.
The applicable settings are in the popup designer under Advanced print settings > Legacy options:
• Hide popup for non-DMS documents: If the tracking behavior is set to display popup, when you enable the hide
setting and a user prints a non-DMS document, the popup does not display, regardless of the tracking behavior
determined by the class-level settings and the tracking hierarchy. Equitrac Professional tracks the document using
the current popup style’s Hide mode validation values. If you have not enabled this option and the user prints a
non-DMS document, the class-level settings and tracking hierarchy determine the popup and tracking behaviors.
• Hide popup for DMS documents: If the tracking behavior is set to display popup, when you enable the suppress
popup setting and a user prints a DMS document, the popup does not display, regardless of the tracking behavior
determined by the class-level settings and the tracking hierarchy. Equitrac Professional accesses the DMS to
retrieve validation data and charges the print transaction to the appropriate account. If you do not enable this
setting and a user prints a DMS document, Equitrac Professional accesses the DMS to retrieve validation data, and
uses this data to prefill the fields on the popup. The user can confirm that Equitrac Professional retrieved the
appropriate validation information, change the information if it is incorrect, and complete the print transaction.
NOTE: When you configure Hide popup options, the Hide options and the Hide mode value take precedence in the
popup behavioral hierarchy over any DMS-specific behavioral configurations.
When you configure a popup style for use with DMS integration, map each applicable Equitrac Professional validation
field to the corresponding field in the DMS database. This mapping tells Equitrac Professional which values to retrieve
from the DMS. If, for example, you are retrieving client and matter data from the DMS, map the Equitrac Professional
client and matter fields to the DMS database fields that contain client and matter codes.
To set DMS-specific options for a popup style, do the following. For complete details on configuring a popup style, see
Creating Popup Styles on page 356:
1 Select Start > All Programs > Equitrac Professional > System Manager. A dialog displays prompting you to
select the core accounting server with which System Manager is associated.
2 Select the local server and click Connect. The System Manager window displays.
3 In the left pane, click the Popup Styles link. The right pane displays the User-Client-Matter popup style, and any
others you have created.
4 Click the desired popup style to open the Modify popup style dialog.
b In the DMS data field, use the drop list to select the DMS field containing the value you want to retrieve for the
current field. If the current field is the Client field, for example, and the DMS database stores client values in a
field called ClientCode, select the ClientCode field from the drop list.
If you configure your DMS as an application class that hides the popup on the basis of tracking hierarchy, or if
you configure the popup directly to hide for DMS documents, then Equitrac Professional populates the print
popup automatically on the basis of the DMS data and Hide mode values you specify for the DMS-specific
application class popup.
7 Repeat step 7 as necessary for the active validation fields in the current popup style.
8 Click OK to save your settings.
For more information about configuring the Print Popup, see Creating Popup Styles on page 356.
Topics:
Regular Expressions
Printer Support
Command Line Utilities and Tools
Field String Syntax
SMDR Translator
Color Values in Transaction Import Files
Format Variables for Custom Date Format Field
Sample Perl Scripts for Perl Script Field
Transformations
This appendix provides administrative and support tool information for advanced configuration and data
manipulation.
Regular Expressions
You can use regular expressions in the Document title pattern of a print rule set.
A regular expression consists of one or more “branches”, separated by ‘|’. The regular expression matches anything that
matches at least one of the branches. For example, “abc” and “def ” are branches in the following regular expression:
abc|def.
Branch
A branch is one or more pieces, concatenated. It matches a match for the first, followed by a match for the second, etc.
For example, “a”, “b” and “c” are pieces in the first branch of the following regular expression: abc|def.
Piece
A piece is an atom possibly followed by a single ‘*’, ‘+’, ‘?’, or a bound. An atom followed by ‘*’ matches a sequence of 0
or more of the atom. An atom followed by ‘+’ matches a sequence of 1 or more of the atom. An atom followed by ‘?’
matches a sequence of 0 or 1 matches of the atom. For example, in the following:
ab - matches “ab” but not “a” or “abb”
Bound
A bound is ‘{‘followed by an unsigned decimal integer, possibly followed by ‘,’ and possibly followed by another
unsigned decimal integer, and then always followed by ‘}’. The integers must be at least 0 and no greater than 255, and
if there are two, the first must be no greater than the second.
An atom followed by a bound containing one integer i, and no comma, matches a sequence of exactly i matches of the
atom. An atom followed by a bound containing one integer i, and a comma, matches a sequence of i or more matches
of the atom. An atom followed by a bound containing two integers i and j matches a sequence of i through j (inclusive)
matches of the atom. For example, in the following:
ab{1}- is equivalent to “ab”
An atom is a regular expression enclosed in ‘( )’ (matching the regular expression within the parentheses), an empty
set of ‘( )’ (matching the null string), a bracket expression, ‘.’ (matching any single character), ‘^’ (matching the null
string at the beginning of a string), ‘$’ (matching the null string at the end of a string), a ‘\’ followed by one of the
characters ‘^.[$()|*+?{\’ (matching that character, taken as an ordinary character), a ‘\’ followed by any other character
(matching that character taken as an ordinary character, as if the ‘\’ had not been present), or a single character with
no other significance (matching that character). A ‘{‘followed by a regular expression character other than a digit is
considered as an ordinary character, not as the beginning of a bound. It is illegal to end a regular expression with ‘\’.
For example,
^New- matches all strings starting with “New”
.xls$- matches all strings ending with “xls” (note that the ‘.’ will match any
character in a pattern)
Bracket Expression
A bracket expression is a list of characters enclosed in ‘[ ]’. It normally matches any single character from the list
enclosed within. However, if the list begins with ‘^’, the list matches any single character not included in the rest of the
list. Two characters in the list separated by ‘-’ is shorthand for the full range of ASCII characters between those two
(inclusive), for example, ‘[0-9]’ in ASCII matches any decimal digit. It is illegal for two ranges to share an endpoint, for
example, ‘[a-c-e]’. In general, special characters, including ‘\’, lose their special significance when used in a bracket
expression.
For example, in the following:
[a-z]- matches any lowercase letter
Collating Element
Within a bracket expression, a collating element (a character, a multi-character sequence that collates as if it were a
single character, or a collating-sequence name for either) enclosed in ‘[.’ and ‘.]’ stands for the sequence of characters of
that collating element. The sequence is a single element of the bracket expression’s list. A bracket expression
containing a multi-character collating element can thus match more than one character, for example, if the collating
sequence includes a ‘ch’ collating element, then the regular expression ‘[[.ch.]]*c’ matches the first five characters of
‘chchcc’.
In the event that a regular expression could match more than one substring of a given string, the regular expression
matches the one starting earliest in the string. If the regular expression could match more than one substring starting
at that point, it matches the longest. Subexpressions also match the longest possible substrings, subject to the
constraint that the whole match be as long as possible, with subexpressions starting earlier in the regular expression
taking priority over ones starting later. Note that higher-level subexpressions thus take priority over their lower-level
component subexpressions.
Match lengths are measured in characters, not collating elements. A null string is considered longer than no match at
all. For example, ‘bb*’ matches the three middle characters of ‘abbbc’; ‘(wee|week)(knights|nights)’ matches all ten
characters of ‘weeknights’; when ‘(.*).*’ is matched against ‘abc’ the parenthesized subexpression matches all three
characters, and when ‘(a*)*’ is matched against ‘bc’ both the whole regular expression and the parenthesized
subexpression match the null string.
Printer Support
Equitrac Professional supports specialized hardware units, printer interfaces, and print job languages. Understanding
the way Equitrac Professional supports and interacts with these components can help you configure your Equitrac
Professional environment to accommodate additional hardware devices or identify potential issues that may impact
system performance.
If you require more information, see your hardware manufacturer’s documentation, or visit their online website.
Equitrac Professional supports the following printer interfaces and print job languages. If you require more
information, see your hardware manufacturer’s documentation, or visit their online website
Printer support varies based on the selected page counter. The following subsections describe the types of hardware
drivers that each page counter supports.
Text Interpreter
The text page interpreter supports text printing. You may use the text page counter, for example, if you are printing
text output from DOS or UNIX-based applications. This interpreter gives page counts only, not document attributes.
When you select this page counting option, you must specify the number of lines per page for text output.
PostScript The Datastream Interpreter requires CPU time on the print server because
it examines print data on the way to the printer.
PCL6
HP-GL/2, HP RTL
Ricoh IPDL-C
Epson ESC/Page
Kyocera Prescribe
This section documents the commonly-used tools not already described elsewhere in this guide; a list of these tools
and links to their details is on the next page.
Any utilities not described here or elsewhere in this guide are intended for service and support purposes only, not for
general administrative usage.
Tool Description
CustomReportIntegrator.exe Use this tool to preload your custom Crystal Reports into Equitrac
Professional; see Loading Custom Reports on page 388.
EQCDRTest.exe Use this tool to test WinSMDR’s translation when you’ve created a new parser
for translating raw CDR data into phone data.
EQExportWizard.exe The transaction Export Wizard; see Exporting Transactions on page 123.
EQModifyDeletedContainerSecurity.exe This tool displays or modifies the access permissions on the deleted objects
container in Active Directory.
EQPrinterConversionWizard.exe and These utilities install with the core Equitrac Professional server components.
EQNT4PrinterConversionWizard.exe
EQPrintQueueViewer.exe The utility installs on the server hosting the document routing engine as part
of the DRE installation. When you have enabled queuing, this tool provides a
graphic interface that enables you to see and delete documents in the print
queue. See Administering the Secure Print Queue on page 245.
EQReExportUI.exe The transaction Re-Export utility, accessed via the Start menu on the CAS
server: Equitrac Professional > ReExport; see Re-exporting Transactions on
page 141.
EQTerminalUpdate.exe The utility installs with the core Equitrac Professional server components. This
tool is for administrators and technicians to update PageCounter and
PageCounter Professional device firmware for terminals equipped with hard
disks. You cannot use this tool to update firmware if the terminal is not
equipped with a hard disk.
Tool Description
EQTransactionPurge.exe The utility installs with the core Equitrac Professional server components. The
utility enables you to purge transactions from the CAS database, based on a
specified date criteria. This is especially useful prior to a database backup or
migration, in which you might not want to include old and unused
transaction records as a means of speeding up the process. You must have
Equitrac Professional administrative privileges on the target server to run this
utility.
EQTrnImportWizard.exe The Transaction Import Wizard; see Using the Transaction Import Wizard
on page 102.
EQValImportWizard.exe The Validation Import Wizard; see Managing Validation Data on page 79.
SmdrDesign.exe and WinSMDR.exe Utilities associated with the SMDR Translator; see SMDR Translator on page
476. For more information on working with CDR data, see Raw CDR
Translation on page 427.
TransactionEditor.exe The Transaction Editor, an alternate tool for accessing data normally
accessible through the Equitrac Professional Web Client, see Working with
Transactions in Transaction Editor on page 117.
1 Double-click the EQCDRTest.exe icon to open the CDR Devices Test Suite.
2 Select the DCE details, including the Device Site and CAS DNS names.
3 Click Get Devices.
4 Select a CDR device from the list.
5 Browse to find and select a Raw CDR File.
6 Click Translate.
7 When the Test Data list box populates, select a row and click Cost.
8 In the Cost hypothetical call dialog, click Cost call.
9 Review the details of the test translation.
Parameters enclosed in brackets ( ) are mandatory, and parameters shown in square braces [ ] are optional.
Parameter Description
- a accountname Account to be granted access to the container. Access permission will be removed if
specified with the -r option.
NOTE: The conversion wizard supports LPR port monitors, although the LPR port monitor option is not available by
default in Windows. You can access this option in the Add Printer wizard.
Before you begin this process, ensure that the devices using the port monitors are turned on, connected to the
network, and configured as required.
1 Run the conversion wizard, EQPrintConversionWizard.exe, located within the Equitrac Professional Tools
directory. Typically, this directory is located under <Root>:\Program Files\Equitrac\Professional.
2 On the Equitrac Printer Conversion wizard welcome screen, click Next.
3 Select the Print server location:
• Select Local machine if the print server resides on the local machine.
—Or—
• Select Remote server if the print server resides on a remote machine.
4 Select a conversion Action:
• Convert printers to use the Equitrac port monitor.
—Or—
• Restore converted Equitrac printers to use their original port monitors.
5 Select or clear printers in the Convert Printers list:
NOTE: The procedures documented in this section are also available as a compiled help file (.CHM) that accompanies
this tool.
Selecting Devices
5 Select terminal devices to update with new firmware by:
a Adding a single device:
• Click Add.
• Enter a valid device IP address and click OK. The Terminal Updater adds the device to the Terminal device
list.
—Or—
6 You can also monitor and manage the Terminal device list by:
a Refreshing the list. Click Refresh to update the device attribute details displayed in the Terminal device list.
NOTE: When rebooting the devices, allow 1 to 2 minutes for the devices to fully reboot before refreshing the
Terminal device list display.
—Or—
b Deleting a device. Select a device in the Terminal device list and click Delete.
NOTE: Press and hold SHIFT to select a consecutive range of devices, or press and hold CTRL to select multiple
devices. To de-select a device, click it again. If you have only one device selected and you want to de-select it, press
CTRL and click the device.
—Or—
c Filtering the list view. You can filter the Terminal device list to display all device types, only PageCounter
devices, only PageCounter Professional V1 devices, or only PageCounter Professional V2 devices. Select the
desired option from the Filter drop list to display only those terminal devices that match the filter you selected.
The Terminal Updater displays all defined devices in the Terminal device list. Both the device type and the device
status affect whether or not you can proceed with the firmware update.
NOTE: The firmware .bin file you specify must match the device type you intend to update, as follows:
Before updating devices, delete the existing validation tables on the devices and ensure that you select the
Automatically restart after firmware update option. Selecting this option ensures that the devices reboot after
receiving the updated firmware:
a To delete validation, select the desired devices from the Terminal device list and click Delete Validation. Press
and hold SHIFT to select a consecutive range of devices, or press and hold CTRL to select multiple devices.
CAUTION: Do not reboot the terminals prior to sending the firmware update.
b Before uploading new firmware, verify that the Automatically restart after firmware update option is
selected. This option reboots each device when the Terminal Updater completes the firmware upload. If this
option is not selected, you must reboot the terminals using the Restart button.
c Click Refresh to refresh the status information in the Terminal device list before proceeding with the firmware
update. Refreshing the list ensures that you have the most up-to-date status for each of the terminals; you
cannot update a terminal's firmware unless it reports an Idle status.
9 When you have deleted validation as necessary, verified the status of the Automatically restart after firmware
update option, and refreshed the Terminal device list, proceed with the update.
a From the Terminal device list, select the terminals you want to update. Only select terminals with an Idle
status.
b When you have selected the desired terminals, click Update to upload the firmware file to all selected terminal
devices. The time required to complete the upload depends on the number of devices you have selected.
c If, during the update, the Terminal Updater encounters a PageCounter terminal without a disk, the Terminal
Updater:
• Changes the terminal's status in the Terminal device list to Failed.
• Does not upload new firmware to the terminal.
• Does not reboot the terminal.
• Continues uploading firmware to valid terminals in the list.
Rebooting Devices
Complete this step only if you neglected to enable the Automatically restart after firmware update option prior to
sending the update; if you enabled this option, all updated terminals reboot automatically.
10 To reboot terminal devices, select the desired devices from the Terminal device list and click Restart. The
Terminal Updater sends a command to reboot each of the selected terminal devices.
NOTE: Press and hold SHIFT to select a consecutive range of devices, or press and hold CTRL to select multiple
devices. To de-select a device, click it again. If you have only one device selected and you want to de-select it, press
CTRL and click the device.
Parameters enclosed in brackets ( ) are mandatory, and parameters shown in square braces [ ] are optional.
NOTE: The -f option toggles a simulation mode; you can run this utility initially without this parameter, to review
the data that the utility will purge (the utility shows the same output without -f as with it). Once you confirm the
parameters and the purgeable data, run the utility again with -f to actually purge the data.
Parameter Description
Entry Length [#] Specifies an exact entry length, where [#] is any number between 0 and 16 inclusive.
Using 0 indicates that the field is optional.
[#]-[##] Specifies a range of lengths, where [#] is the minimum value for the range and [##] is the
maximum value. Range must be between 0 to 16, inclusive, with minimum and
maximum values separated by a hyphen. Using 0 as the minimum field length indicates
that the field is optional.
* Specifies an open entry length, enabling entries from 0 to 16 characters long. However,
the maximum length can be changed in a configuration set. See Configuring Control
Terminal Mode Options on page 293 for details.
Specific Positioned “[X] Specifies the use of a specific character [X] in the entry, where X represents any
Character character you choose to use.
Z Specifies an open syntax — any alphanumeric characters with spaces, dashes, and/or
periods.
Entry Length
With the exception of specific positioned characters, a number or range of numbers precede all syntax command
codes to specify an entry length. The entry-length variable is a number from 1 to 16 inclusive, or a range of numbers
within those limits. Separate numbers specifying a range by a dash (-). To make a field optional, the syntax must
accept 0 as the minimum length (0-16 instead of 1-16).
An asterisk (*) before a character type specifies an open entry length. The entry can contain any number of characters,
of the specified character type.
Use the string-length code (L) to define the total length of an entry. This code is especially useful with an open-length
syntax (*code). Use the string-length code with the terminate code (T) to define a syntax that accepts any entry of the
proper length using any characters.
The following table shows examples of entry lengths:
6-8L.N”. .N 123.456 Variable length from six to eight numeric characters with floating decimal.
1234.5678
12.34567
*LT 1&$5.00+2% Any length of any displayable ASCII characters. Limited only by the maximum
allowable length of the field.
0-16LT (nothing) Optional descriptive text field of any length, including any characters such as
ABC/123,- commas, dashes and slashes.
Character Types
There are four types of characters on Equitrac control terminal keyboards; you can meet most syntax requirements
using these four basic formats:
• Alphabetic: includes all letters from A to Z.
• Numeric: includes all numbers from 0 to 9.
• Special characters: includes the space ( ), the dash (-), the at symbol (@), the period (.) and others.
• Alpha Terminal characters: includes any character on the QWERTY keypad.
These character type syntaxes will not accept special characters in the specified entry.
The following table shows examples of character types:
6c A.B-CD Six character alphanumeric code with one period and one dash.
AB.D-C
10P 12-45-78.0 Ten character numeric code with 2 dashes and 1 period.
1-34-67.90
9Z ABC-567.90 Nine character alphanumeric code with any number of special characters.
AB 4567890
123.567 90
Combining Syntaxes
Occasionally, one syntax string will not be enough to check a single entry field for validation. For example, you may
require the user to enter either a three digit user code, or a two digit speed entry code for validation. In these cases, use
the OR code (/) to combine syntax strings. The slash (/) must separate each individual syntax string.
4N/6N 1234 Code with exactly four numeric characters or six numeric characters.
123456
3A/2N CLC Code in the format of a three-letter user code or a two-digit speed entry
01 code.
SMDR Translator
The program WinSMDR.exe converts raw/native CDR records, stored in a disk file, to a standard SMDR format. This
appendix describes how to use WinSMDR.exe.
where xx is a channel number (0 to 99) used to differentiate among multiple configuration files.
CFG files can be developed, customized, and tested with the help of the SMDRDesigner.exe. The CFG file format is
completely different from the PRS file format that is used for Standard Mode translation. See The WinSMDR.exe
Utility on page 476 for information on using the SMDRDesigner and designing SL1 CFG configuration files.
To use the CFG file, it must reside in the Equitrac Professional root directory.
To use WinSMDR in SL1 translation mode, do the following:
1 Select the Use WinSMDR.exe option in the Raw CDR Translation section of the SMDR Buffer Editor screen.
2 In the edit box, enter SL1 xx, where xx is an indicator of the CFG file to use.
When Equitrac Professional wants to translate a file of raw CDR records, it launches WinSMDR with the following
command line:
WinSMDR.exe SL1 xx <CDR input file> <output file> [/D]
where
• xx is a channel number, 0 to 99, and corresponds to the SL1-xx.cfg file to use.
• {parse file} is the name of the file containing the parsing and conversion parameters. All parse files have the
suffix ‘.PRS’. The SMDR program assumes a ‘.PRS’ suffix. Do not include the extension on the command line.
Note that in addition to the parse file, there may also a record filter file. The filter file has the same name as the
parse file, but the extension is ‘.FLT’. As a result, the use of this extension is reserved.
• {input file} is the full path and name of the file containing the raw/native SMDR records.
• {output file} is the full path and name of the file of generic SMDR records. The SMDR program appends to this
file if it already exists. The format of this file is recognized by SDS.
• [/D] is an optional parameter that invokes debugging mode. If invoked, the output file will contain the input field
along with the output field. This function is used for debugging parsing file formats.
In most cases, the program is setup to be run automatically by specifying it for every SMDR Device in the SMDR
Device List editor. The Conversion Program field is used to specify the translator executable and any parameters. An
example is shown below:
Conversion Program: SMDR ROLM8004
0000000001111111111222222222233333333334444444444555555555566666666667777777777888888
88889999999999000000000011111111
1234567890123456789012345678901234567890123456789012345678901234567890123456789012345
67890123456789012345678901234567
0000000001111111111222222222233333333334444444444555555555566666666667777777777888888
88889999999999000000000011111111
1234567890123456789012345678901234567890123456789012345678901234567890123456789012345
67890123456789012345678901234567
Where:
• {YY}YYMMDDHHMM is the Date and Time of the Call
• DDDDD{DD} is the call duration in seconds
• EEEE is the Extension
• TTTTTTTTTT is the Trunk
• NNNNNNNNNN... is the Digits Dialed
• AAAAAAAAAA... is the Account Code
• DDDDDDDDDD... is the Description
• Y is the call type; O – Outgoing, I – Incoming
Date 1 6 6 1 8 8
Time 7 12 4 9 12 4
Duration 12 16 5 14 20 7
Extension 18 21 4 22 25 4
Trunk 23 32 10 27 36 10
Digits 34 49 16 38 57 20
Account 51 62 12 59 74 16
Description - - - 76 115 40
Field Notes
Account Max 32
Description Max 40
Current WinSMDR.exe can generate both old and new Generic SMDR formats. WinSMDR.exe generates the old
format by default. SDS auto-senses which format it is reading and deals with it accordingly. As much as possible, the
Extended format should be used.
The PRS file contains different sections for defining various parsing parameters:
Section ID Notes
[TEMP_FIELDS] Used to define parsing parameters for extraction of temporary fields. Up to 20 fields are
allowed.
[FILTERS] Used to define text values for temporary fields which would cause a record to be
discarded. The conditions are ORed together (i.e., if any of the specified conditions
hold, the record will be discarded)
[COMMENTS] Used to include reference information, such as raw record format samples,
development notes, warnings, etc.
In this format:
• 14 = field ID
• 034 038 = field position start and end parameters
• 003 822 000 000 = field formatting codes; up to four formatting codes per field
Field IDs:
1 Date 6 Digits 11 End Date
2 Time 7 Account 12 End Time
3 Duration 8 Type 13 Auth. Code
4 Extension 9 Alt. Date 14 Aux. Field 1
5 Trunk 10 Description 15 Aux. Field 2
As can be seen, {Start} parameter starts with letter 'D', which indicates a delimited field. Letter 'D' is followed by the
sequential position of this field in the raw record. {End} parameter is used strictly to specify the delimiter character to
use. The example is read as follows:
Get Extension (i.e., Field ID 4) by extracting the third field in a comma-delimited sequence of fields.
If a call qualifies as Incoming, field [_Incoming] will evaluate to “TRUE” when used with directives in the
[GENERAL] section.
Example:
[FILTERS]
If a call qualifies as Tandem, field [_Tandem] will evaluate to “TRUE” when used with directives in the [GENERAL]
section.
The translator can be instructed to output either one or two records for each Tandem call it encounters. If both
Incoming and Outgoing trunks are given in one CDR record, then two records will need to be written out. Use
TandemOutput parameter in the General section to control how many records are written.
TandemOutput=BOTH|IN|OUT
• Default is BOTH
• IN only an incoming record will be written
• OUT only an outgoing record will be written
Since Tandem calls usually do not have an extension, the translator will assign “TDM” as the default extension. This
can be changed using TandemExtension parameter in the [GENERAL] section.
TandemExtension=TDM
If outputting both Outgoing and Incoming records, it may be necessary to pick a different Trunk ID for the Incoming
record. Recommended way to do this is as follows (requires WinSMDR.exe version 5.12 or greater):
• In the [OUTGOING] section, initialize field 14 (or any other Auxiliary Field) with the alternative Trunk ID value
• In [GENERAL] section, use directives as follows to assign the alternative value to the Trunk ID field:
IF [_Tandem] = “TRUE”
IF [_Incoming] = “TRUE”
ASSIGN [5]=[14]
ENDIF
ENDIF
The above example assumes that the outgoing portion of the Tandem call will be parsed and written out using the
[OUTGOING] call rules.
“ 17 : 15 ” = “17:15”
“ 18:05 ” = “18:05”
“ A000” = “T000”
ACCOUNT FIELD.
0 1 2 3 4 5 6 7 8 9
1234567890123456789012345678901234567890123456789012345678901234567890123456789012345
67890
-----------------------------------------------------------------------------------
-------
-----------------------------------------------------------------------------------
-------
1234567890123456789012345678901234567890123456789012345678901234567890123456789012345
67890
0 1 2 3 4 5 6 7 8 9
ASSIGN
The IF and ASSIGN directives can be used in [GENERAL] section as well. Note that INCLUDE/EXCLUDE set of
directives are not applicable to the [GENERAL] section.
FDL constructs are based on fields and constants. Constants are specified in double-quotes, as per FDL standard.
Fields are specified in square brackets (exception is when fields are used in INCLUDE/EXCLUDE set of directives).
Fields available in PRS files are listed below:
Persistent Fields
100 to 199: 99 persistent fields are available. These fields start off blank, and once initialized, they hold their value until
cleared or re-initialized. They can be re-assigned at any time, and they are used in the same way as other fields.
NOTE: When SMDR translator program terminates, all Persistent Fields are dumped to a file. When SMDR translator
runs again, it re-loads this file and re-initialized Persistent Fields to their values from the previous execution of the
SMDR translator.
Usage of IF and ASSIGN directives is explained through the use of examples. These examples apply to all sections
where the use of directives is allowed. Important thing to remember is the order in which sections are executed.
[FILTERS], [INCOMING_ID] and [TANDEM_ID] sections are executed first, in no specific order. At the very end of
processing, directives of the [GENERAL] section are executed. Below are the rules of when access to various fields is
allowed:
• Temp fields can be created using ASSIGN directive in any section
• Temp fields created in [FILTERS], [INCOMING_ID] and [TANDEM_ID] sections are then usable in the
[GENERAL] section
• Temp fields created in the [GENERAL] section are not usable in the other three sections, since [GENERAL]
section is executed last
• Do not assign values to real fields in [FILTERS], [INCOMING_ID] and [TANDEM_ID] sections; use temp fields
only. Values of real fields are not finalized when these sections are executed, and may change. For that reason, do
not use values of real fields in these sections at all, even to assign values to temporary fields. If a value of a real field
is needed, use [TEMP_FIELDS] section to cut out and format a temp field, which corresponds to the data of the
desired real field.
ASSIGN [25]=“8801”
ASSGIN [25]=+[6]
ENDIF
IF [_INCOMING] = “TRUE” test the value of special field _Incoming. _Tandem special
field can be used in the same way.
ELSEIF
ENDIF
ASSIGN [101]=[100,99]
Field 101 will contain “6”, since the length of text in field 100 is 6.
...
...
ENDIF
The IF directive is true if the length of field 6 (digits dialed) is Greater Than 11.
General Formatting
0 Do nothing
123 Convert from Unix Date (Number of Seconds since Midnight Jan/1/1970)
204 Convert from HH:MM;SS (note semi-colon between minutes and seconds)
207 Convert from HH:MM:SS AM|PM (one or two digit Hour and Minute)
250 Calculate the duration based on Start and End Date/Time: EndDT-
StartDT
257 Convert from Unix Time (Number of Seconds since Midnight Jan/1/1970)
504 Extract the digits dialed code from the Digits*Account format
0 (meaning: COLOR_UNKNOWN)
1 (meaning: COLOR_NO)
For example, if you define the color value as 2 (COLOR_YES) or 3 (COLOR_SINGLE) in the transaction import file,
Equitrac Professional sets the color flag in CAS as a non-zero value.
Variable Description
%U is replaced by the week number of the year (Sunday as the first day of the week) as a decimal
number [00,53].
%W is replaced by the week number of the year (Monday as the first day of the week) as a decimal
number [00,53]. All days in a new year preceding the first Monday are considered to be in week 0.
%% is replaced by %.
For more information on customizing the date format field, see Transforming Field Data on page 130.
Sample 1
sub EQTransform {
# PERL TO INSERT A DASH BETWEEN THE 2nd AND 3rd CHARACTERS
# ON A 5 DIGIT ACCOUNT
# EXAMPLE WOULD CONVERT 12345 to 12-345
return($output);
}
Sample 2
sub EQTransform {
$input_field = $_[0]; # source field
$input_delim = $_[1]; # source delimiter
$string1 = $input_field;
$_ = $string1;
tr/-//d; # Replace every instance of dash with NULL
$string1 = $_;
$string2 = $string1;
$_ = $string2;
tr/(//d; # Replace every instance of left paren with NULL
$string2 = $_;
$string3 = $string2;
$_ = $string3;
tr/)//d; # Replace every instance of right paren with NULL
$string3 = $_;
Sample 3
sub EQTransform {
$input_field = $_[0]; # source field
$input_delim = $_[1]; # source delimiter
Glossary
Symbols
Caution
When you see this symbol in the margin, the accompanying text provides key information about a step or
action that might produce unexpected results if not followed precisely.
Note
When you see this symbol in the margin, the accompanying text provides cross-reference links, tips, or
general information that can add to your understanding of the topic.
Warning
When you see this symbol in the margin, read the accompanying text carefully. This text can help you avoid
making errors that might adversely affect program behavior.
Access Permissions
Settings within the System Manager that limit or grant access to the Equitrac Professional Administrative
Applications.
Accounting Precision
An option within System Manager that determines the number of decimal places used to calculate printing costs. The
default setting is two decimal places.
Administrative Applications
A set of software tools used to manage all Equitrac Professional functionality either locally or remotely. Administrative
Applications can be installed on any Equitrac Professional server component machine.
Alert Rules
A preset rule that triggers an action if a specific fault and defined criteria occurs on a DME-monitored device.
Administrators can be alerted to fault conditions by email, Event Viewer, or by network popup messages.
Billing Code
A unique combination of letters and numbers that represent a charge-back group. Users can assign their print jobs to a
particular code, and the Equitrac Professional database tracks the characteristics of jobs printed to the code.
CAS
The Core Accounting Server controls the accounting database that stores all printer, user, billing code, transaction and
balance information. The CAS also verifies users, calculates copy, fax, scan and disbursement transaction charges, and
assigns charges to an appropriate user, or billing code.
Cluster
A group of servers and other resources that act like a single system to ensure that resources remain available to client
workstations.
Control Terminal
A physical device that releases documents and controls copier access. Equitrac Professional supports PageCounter,
PageControl Stations, and Network Transaction Stations.
Controller Interface
A software bridge between the Equitrac server and a multifunction device that enables device communication. Some
Xerox and Canon devices require a controller interface to configure the behavior and communication requirements of
the device so that Equitrac Professional can track printing activity on the device.
Cost Preview
A software feature that enables users to see the entire cost of a print request before sending the document to the
selected output device.
DCE
A core component of Equitrac Professional, the Device Control Engine provides management of control terminals
and the ability to access the scan and fax features on multifunction devices.
Desktop Printing
Desktop printing tracks the use of local printers connected directly to a user workstation, rather than connected to the
office LAN. These printers are not controlled by a DRE print server. Equitrac Professional groups these devices as
Workstation devices in System Manager.
Device Interfaces
Connections to physical devices that track transactions. There are two types of device interfaces in Equitrac
Professional: Control terminals and Controller interfaces.
Domain Controller
A name shared by a group of computers that use a common accounts database. When importing and synchronizing
accounts using Active Directory Services, you must specify particular Domain Controllers and OU Containers to
import.
DME
The Device Monitoring Engine proactively track the status of selected SNMP-enabled devices. The DRE monitors
SNMP messages generated by specified devices for status information. Each time a status change message is
intercepted, DME logs the information in the database. View DME-related activity in the Device Monitoring Console.
DRC
For optional use in installations where there is no DRE (see below), and therefore no dedicated print server, the
Document Routing Client (DRC) is a locally installed version of the DRE that allows for similar functionality.
DRE
A core component of Equitrac Professional, the Document Routing Engine enables document flow from workstations
to output devices including printers, plotters, scanner, multifunction devices, copiers, etc. DRE communicates
document characteristics to the Core Accounting Server for processing. In a large deployment, multiple DREs are
often required to manage the device load.
Dual Pricing
A feature that allows you to create a primary price list and a secondary price list that is applied under certain
conditions. Equitrac Professional uses the primary price list to calculate the actual transaction cost. Secondary price
lists enable the software to calculate another cost that is stored with the transaction for reporting purposes, but does
not factor into any balance calculations.
Embedded Interface
Platform-specific Equitrac software that is embedded on select MFP’s to handle the transfer of user credentials and
transaction details between the device and the Core Accounting server database.
e-queue
A proprietary print queue definition that implements secure printing and is not associated with a specific physical
device. When users print, the e-queue holds the documents for release. When users release held documents, Equitrac
Professional pulls the documents to a physical device for printing.
Equitrac Port
A proprietary port that is included with the DRE. Each printer that you want to control and track transactions must
use an Equitrac Port. This port communicates with the DRE and ultimately the Core Accounting Server to track user
transactions.
Escape Code
Syntax used to identify variables that should be printed on a print separator page. By default, Equitrac uses the /
character.
Follow-You Printing
A secure printing feature that holds print jobs in a virtual print queue until the user “pulls” the print job to a selected
device. A user can select a particular printer when they submit a print request, then walk to an entirely different print
server and redirect the job to a different compatible printer.
G-H
Home Server
An attribute assigned to a user account indicating the DRE print server that hosts the devices the user typically prints
to. You can assign a Home Server to each user account if you are enabling multi-server Follow-You printing. At a
Release Station or Control terminal prompt, the user can select Home to view all devices on their Home Server. If
looking to release jobs to devices on a different Print Server, the user can use the Search functionality provided
Local Install
All Equitrac Professional server components and Administrative Applications are installed on a single server. This
installation type is often used for small deployments where the overall print and tracking load can be managed on a
single server.
Mailbox Printing
A print job sent to a device with ‘mailbox printing’ or ‘device server’ selected in the device driver. The print job resides
on the device’s hard disk until the user releases the job.
Off-box Validation
An option used for select Xerox devices that forces the physical device to send a request to the Equitrac Core
Accounting Server to validate the data input by the user.
Offline
A situation where the Core Accounting Server is not available to the other core components. Hardware failures, or
communication failures on the network may can an offline situation. Equitrac Professional offers Offline support to
cache data locally until the CAS is back online.
OU Container
A subset of a Domain Controller. When importing OU Containers using Active Directory Services, OU Containers
must contain user account data only.
P-Q
PageCounter
A physical device that is integrated with an output device (copies, scanner, printer) to allow the user to release print
documents or enable copier access at the physical device.
Passthrough Printer
A printer port that acts as a translator between Equitrac Professional and a target printer that cannot communicate
directly with Equitrac Professional. You must convert the printer port to a Passthrough printer port on any devices
that use proprietary communication protocols other than RAW or LPR.
Physical Device
A printer, scanner, copier, plotter or multi-function unit that translates digital data into hardcopy output.
Physical Disk
A local disk subsystem on a cluster node; a physical disk can be shared, but cannot be used as a quorum disk.
Pin2 Encryption
Equitrac stores the secondary PIN information (called PIN2 in the CAS database) using a two-way AES encryption.
Port
A connection on a device that works with the Equitrac Port Monitor to track printed documents sent to the device.
Port Monitor
Examines print job and page attributes, and passes the necessary information to the Accounting Server. The Port
Monitor communicates with the DRE or DCE to control the job requests made to a device.
Price List
A collection of charging rules applied as a set to one or more network printers. These rules define how Equitrac
Professional assigns transaction charges to printing accounts based on attributes such as page count, page attributes,
finishing options, and surcharges.
Pull Group
A logical grouping of printers with similar device capabilities. When secure printing is enabled, users can release jobs
from the pull group queue to any compatible device within the pull group.
Queue
A virtual list of jobs waiting to print on the device.
Release Station
A licensed feature that sets up a network station as a point of controlled document release. Users can view, select,
print, or delete documents held in the secure print queue.
Remote Install
A deployment in which the core Equitrac Professional components are dispersed among two or more server
machines.
Routing
The process of intercepting and changing the destination of network print jobs based on a comparison of job
characteristics against routing rule attributes.
Scheduled Task
A pre-defined task that is set to run automatically at a particular time and interval. Tasks can include report
generation, auto-run of command line utilities, etc.
Secure Printing
A means of controlling document release. When a user prints, the document is held in a virtual queue until the user
releases the document at the output device. The goals of secure printing is to ensure that proprietary information does
not sit in on an output device for public consumption. Secure printing uses the DREs queuing feature in conjunction
with a client application such as Release Station or Print Queue Viewer for user-controlled release. You can also release
documents directly from a control terminal, such as a PageCounter, PageControl Station, or Network Transaction
Station terminal.
Separator Page
A page printed before each released print job on a device. You can configure the job details that appear on the printed
page to assist users when they pick up print jobs output on public printers.
Silent Installation
A method used to install the client features that allows you perform the install on all clients at the same time. Place the
client installation in a central shared folder on a network server, then push the installation to all required clients.
SPE
A core component of Equitrac Professional, the Scan Processing Engine handles all scan jobs from a device, once
authentication and additional information is achieved. An SPE requires at least one DCE to function.
System Manager
An Administrative Application used to apply system-wide configuration settings, customization of the Accounting
Server and Port Monitor settings.
Transaction
The page count, job information, and printer cost information calculated for a single print/scan/copy/fax job.
Unidentified Documents
Transactions for which Equitrac Professional cannot identify the associated account, such as a received fax on a multi-
function device.
User Authentication
A prompt for a user to enter their login credentials when submitting a print request. Equitrac Professional checks the
credentials to ensure that the user is authorized to access the print network.
V-Z
Workstation Device
Workstation printers are printers that Equitrac Professional tracks using the Desktop Printing feature. Any printer you
can connect to a client workstation that does not connect to an Equitrac Professional print server—including local
printers on a workstation desktop, or printers using LPT1, USB, or direct network connections—qualifies as a
workstation device.