AutoStore 5.0. Route Components Reference Guide. March 2009

Transcription

1 AutoStore 5.0 March 2009 Notable Solutions, Inc Key West Ave., Suite 200 Rockville, MD

2 Introduction... 8 ABM Importer... 9 Product Overview and Feature Highlights... 9 Using The Component... 9 The Configuration of ABM Importer RRTs for ABM Importer Troubleshooting tips / Restrictions and Limitations ApplicationXtender Product Overview and Feature Highlights Using The Component RRTs for ApplicationXtender Enterprise Connector Troubleshooting Tips / Restrictions and Limitations Captaris Alchemy Product Overview - Feature Highlights Using This Component Building a Process With Captaris Alchemy RRTs for Captaris Alchemy Troubleshooting Tips / Restrictions and Limitations Content Management Queue Documentum Product Overview and Feature Highlights Using the Component The configuration of Documentum 4.x and 5.x RRTs for Documentum 4.x and 5.x Troubleshooting Tips / Restrictions and Limitations DocuShare Product Overview and Feature Highlights Using the Component The Configuration of DocuShare RRTs of DocuShare Troubleshooting Tips / Restrictions and Limitations Domino.Doc Product Overview and Feature Highlights Using the Component The Configuration of Domino.Doc RRTs of the Domino.Doc Component Troubleshooting Tips / Restrictions and Limitations FileMagic Product Overview and Feature Highlights Using this Component The Configuration of FileMagic RRTs for FileMagic Page 2

3 Troubleshooting Tips / Restrictions and Limitations FileNet Product Overview and Feature Highlights Using the Component Installing and configuring FileNet client The Configuration of FileNet RRTs for FileNET Troubleshooting Tips / Restrictions and Limitations Folder Store Product Overview and Feature Highlights Using the Component The Configuration of Folder Store RRTs for Folder Store Troubleshooting Tips / Restrictions and Limitations Fortis Product Overview and Feature Highlights Using this Component RRTs for Fortis Troubleshooting Tips / Restrictions and Limitations FTP Store Product Overview and Feature Highlights Using the Component The Configuration of FTP Store RRTs for FTP Store Troubleshooting Tips / Restrictions and Limitations Hummingbird/Open Text edocs Product Overview and Feature Highlights Using the Component The Configuration of Hummingbird/Open Text edocs RRTs for Hummingbird/Open Text edocs Troubleshooting Tips / Restrictions and Limitations IBM Content Manager Product Overview and Feature Highlights Using this Component The Configuration of IBM Content Manager RRTs for IBM Content Manager Troubleshooting Tips / Restrictions and Limitations imanage Product Overview and Feature Highlights Using the Component The Configuration of imanage RRTs for imanage Troubleshooting tips / Restrictions and Limitations Interwoven Worksite MP Product Overview and Feature Highlights Page 3

4 Using the Component The Configuration of Interwoven Worksite MP RRTs for Interwoven Worksite MP Troubleshooting Tips / Restrictions and Limitations Interwoven WorkSite TM NT Product Overview and Feature Highlights Using this Component The Configuration of Interwoven Worksite TM NT RRTs for Interwoven Worksite TM NT Troubleshooting Tips / Restrictions and Limitations IXOS Product Overview and Feature Highlights Using the Component: The Configuration of IXOS RRTs of IXOS route component Troubleshooting Tips / Restrictions and Limitations Kyocera ABMSync Product Overview and Feature Highlights Using the Component The Configuration of Kyocera ABMSync RRTs for Kyocera ABMSync Troubleshooting Tips / Restrictions and Limitations LAN Fax Product Overview and Feature Highlights Using the Component The Configuration of LAN Fax RRTs for LAN Fax Troubleshooting Tips / Restrictions and Limitations LaserFiche Product Overview and Feature Highlights Using the Component The Configuration of LaserFiche RRTs for LaserFiche Troubleshooting Tips / Restrictions and Limitations Lotus Notes/Domino Product Overview and Feature Highlights Using the Component The Configuration of Lotus Notes/Domino RRTs for Lotus Notes/Domino Troubleshooting Tips / Restrictions and Limitations Microsoft Exchange Product Overview and Feature Highlights Using theccomponent The Configuration of Microsoft Exchange RRTs for Microsoft Exchange route component Troubleshooting tips / Restrictions and limitations Page 4

5 MultiRouter OpenForms Product Overview and Feature Highlights Using this Component The Configuration of OpenForms RRTs for OpenForms Troubleshooting Tips / Restrictions and Limitations OpenText Livelink (9.x) Product Overview and Feature Highlights Using the Component The Configuration of OpenText Livelink 9.x RRTs for OpenText Livelink 9.x Troubleshooting Tips / Restrictions and Limitations Send to Database Product Overview and Feature Highlights Using the Component The Configuration of Send to Database RRTs for Send to Database Troubleshooting tips / Restrictions and limitations Send to Database (Bulk) Product Overview and Feature Highlights The Configuration of Send to Database (Bulk) RRTs for Send to Database (Bulk) Troubleshooting tips / Restrictions and limitations Send to Folder Product Overview and Feature Highlights Using the Component The Configuration of Send to Folder RRTs for Send to Database Troubleshooting Tips / Restrictions and Limitations Send to FTP Product Overview and Feature Highlights Using the Component The Configuration of Send to FTP RRTs for Send to FTP Troubleshooting Tips / Restrictions and Limitations Send to HTTP Product Overview - Feature Highlights Using This Component Building a Process With Send to HTTP RRTs for Send to HTTP Troubleshooting Tips / Restrictions and Limitations Send to Mail Recipient Page 5

6 Product Overview and Feature Highlights Using the Component The Configuration of Send to Mail Recipient RRTs for Send To Mail Recipient Troubleshooting Tips / Restrictions and Limitations Send to PC Product Overview and Feature Highlights Using the Component The Configuration of Send to PC How to configure Send to PC Client RRTs for Send to PC component Troubleshooting Tips / Restrictions and Limitations Send to Printer Product Overview and Feature Highlights Using the Component The Configuration of Send to Printer RRTs for Send to Printer component Troubleshooting Tips / Restrictions and Limitations Send to SFTP Product Overview and Feature Highlights Using the Component The Configuration of Send to SFTP RRTs for Send to SFTP Troubleshooting Tips / Restrictions and Limitations SharePoint Product Overview - Feature Highlights Using This Component Building a Process With SharePoint RRTs for SharePoint Troubleshooting Tips / Restrictions and Limitations SharePoint Portal TM Product Overview and Feature Highlights Using the Component The Configuration of SharePoint Portal RRTs of Microsoft SharePoint 2003 component Troubleshooting Tips / Restrictions and Limitations TRIM Captura 4.x Product Overview and Feature Highlights Using the Component The Configuration of TRIM Captura 4.x RRTs for TRIM Captura 4.x Troubleshooting Tips / Restrictions and Limitations TRIM Context 5.x Product Overview and Feature Highlights Using the Component Page 6

7 The Configuration of TRIM Context 5.x RRTs of TRIM Context 5.x component Troubleshooting Tips / Restrictions and Limitations VB/Java Script Product Overview and Feature Highlights Using the Component The Configuration of VB/Java Script RRTs of VB/Java Script Troubleshooting Tips / Restrictions and Limitations Sample Scripts WebDAV Product Overview - Feature Highlights Using This Component Building a Process With WebDAV Rote RRTs for Knowledge Package Loader Troubleshooting Tips / Restrictions and Limitations WORLDOX Product Overview - Feature Highlights Using This Component Building a Process With WORLDOX RRTs for WORLDOX Troubleshooting Tips / Restrictions and Limitations XML Generator Product Overview - Feature Highlights Using This Component Building a Process With XML Generator RRTs for XML Generator Troubleshooting Tips / Restrictions and Limitations Page 7

8 Introduction Welcome to Notable Solutions, Inc. s AutoStore 5.0. This document is a property of NSi and any use of the material requires explicit permission form NSi. Within this document, you will find the following for each Route Component associated with AutoStore Version 5.0: An overview of the component and its highlights Proper usage of the component Basic and advanced configuration methods including configuration of RRTs Troubleshooting tips Restrictions and limitations The following components are associated with AutoStore Version 5.0 and are therefore described in great detail in this reference guide: ABM Importer ApplicationXtender Captaris Alchemy Content Management Queue Documentum 4.x and 5.x DocuShare Domino.Doc FileMagic FileNet Folder Store Fortis FTP Store Hummingbird/Open Text edocs x IBM Content Manager imanage Interwoven MP Interwoven NT IXOS Kyocera ABMSync LAN Fax LaserFiche Lotus Notes/Domino Microsoft Exchange MultiRouter OpenForms OpenText Livelink (9.x) Send to Database Send to Database (Bulk) Send to Folder Send to FTP Send to HTTP Send to Mail Recipient Send to PC Send to Printer Send to SFTP SharePoint 2003 SharePoint 2007 TRIM Captura 4.x TRIM Context 5.x WebDAV WORLDOX VB/Java Script XML Generator Page 8

9 ABM Importer Product Overview and Feature Highlights ABM Importer allows distribution of address book entries among groups of digital senders. Now you can create device groups and automate administrative tasks related to managing and maintaining the address books within each device. Use this component in conjunction with ABM Exporter to create primary/secondary device configuration. Configure the ABM Exporter to extract address book entries from a single primary device, and create secondary device group using your ABM Importer. When this process runs, all your address book entries get exported out of the primary device and imported into secondary devices. This is the best way to synchronize your HP Digital Sender address book entries across all your organization. Once these two components are setup, the administrator needs to maintain the address book entries on the primary device and all updates to primary automatically propagated to all secondary devices. This component provides Supports device group configuration Single or multiple group support Supports all address book databases including: o Public o User profiles o Public Fax o Printers o Function keys o Prompt fields Selective address book updates allows you to select a subset of address book types. Using The Component Use ABM Importer to create groups of HP Digital Sender devices and send address book updates in batch mode. To create the address book batch file you must use ABM Exporter. ABM Exporter allows you to export entries out of one HP Digital Sender and store them into a batch file. ABM Importer can take input directly from ABM Exporter or from a Poll Directory Component. When using Poll Directory is Capture Component, you should place the batch files into the inbox directory of the Poll Directory Component. It is important to realize that all device database entries are cleared out prior to new batch file entry load starts. Use ABM Importer to: Create groups of Secondary devices. Keep backup files of your address book entries in batch file format (using ABM Exporter) and restore address book entries. Do mass updates across all your HP Digital Sender Devices Create Primary/Secondary device relationship using ABM Exporter and ABM Importer component pairs within the same process. Manage multiple device groups. Propagate your manual entries from one device to many devices Support both older version of firmware and new release including the prompt field definitions. Page 9

10 The Configuration of ABM Importer Fieldname Network Appliance (NA) Group Function Add Define new Network Appliance (NA) group. Each group has its own member devices. The device members should be mutually exclusive and not overlapping. If a device is a member of two groups then that device will receive the same batch twice. Rename Rename an existing NA group. Group Configuration Delete Select a NA Group from the drop down list and press Delete to remove the group from the list. Password Enter the administrator password to the HP Digital Sender machines. Note that all passwords for all devices within the same NA Group must be the same. If you have devices that have different passwords, you must create different NA Groups for each set of device with the same password. Confirm Password Re-enter Administrator password. This must match the Password field value. Network Appliances Clear Address Books Prior to Import Select each checkbox to force a clear message into the HP Digital Sender device and clear its entries prior to loading the Batch file entries. Insert Insert a device address into this NA Group. Delete Select a device address and press Delete to remove the selected device from the group Page 10

11 RRTs for ABM Importer This component does not generate any RRTs Troubleshooting tips / Restrictions and Limitations Problem Description The devices begin to accumulate entries rather than getting an exact copy of the batch file Some devices do not get any updates Solution You must set up the proper checkboxes to clear the address book entries. Check the right set of checkboxes and send the batch file again. The devices that do not get updated entries after ABM Importer runs are either 1) have a different Administrator password or 2) cannot be accessed during the time that ABM Importer was running. Or 3) have a very old version of the firmware. You must make sure to have the latest firmware on all your HP Digital Sender devices. Restrictions and limitations You can only send batch files to be sent to HP Digital Senders. The only component that is capable of generating batch files automatically is the ABM Exporter. You can use the ABM Exporter to export out the address book entries and store them into a batch file as a back up and use the ABM Importer to restore the pre-existing batch files. Page 11

12 ApplicationXtender Product Overview and Feature Highlights The purpose of this component is to store documents into Documentum ApplicationXtender, a content management software package that brings large amounts of data online in a cost-effective manner. ApplicationXtender has robust and comprehensive security to protect sensitive business information. Access to information within applications can be limited, which can further protect confidential information. In addition, user privilege security is provided so that users can be restricted from performing specific functions. ApplicationXtender provides comprehensive electronic file management capabilities and supports a wide range of electronic content, which provides users of this component the opportunity to use content creatively and flexibly to enhance core business activities. This component provides: The following is a list of features that this component provides: Secure your user name and password. Select an application that you will store the documents into. Set the Title/Subject/Author/Keywords/Comments associated with your documents. Place the document into a queue for further processing. Set the Field Values of the application that you selected. This component is mostly used with the Digital Sender or Poll Directory capture components. Capture the files using a capture component and then process them through the ApplicationXtender component. This component can process any file type such as TIF, BMP, RTF, PDF, HTML. Using The Component A sender device captures content data once and routes it to SharePoint Portal Server - Create your process with Digital Sender capture component. Use the application Xtender process component to manipulate the captured data within ApplicationXtender repository, and save the data to SharePoint Server. This AutoStore process provides a uniform capture capability across the enterprise and storage to the desired application/media. The configuration of ApplicationXtender General Tab Fieldname Function Page 12

13 DSN User name Password Application Pass-through Enter the Data Source Name to which you would like to connect. Enter a user name that is appropriate for the selected data source. If the Application Xtender system is using the Windows NT security provider, you must precede the user name with a domain and a slash. For example, documentation\rfrost indicates rfrost is a user on the documentation domain. Enter the password that coincides with the user name that you entered. An application is the highest level of organization in ApplicationXtender. Use application for storing and retrieving documents. Every time you store a document in an application, you must enter index information for that particular document into the index fields. The ApplicationXtender component stores the index information in a database so that you can search it later to retrieve documents. This option is available on the Application Xtender econnector (process) component. If enabled, the documents are passed on to the next component in the process. Attributes Tab Fieldname Title Subject Author Keywords Comments Function Entire title of the document Subject within ApplicationXtender Author used for storing the document Keywords for easier document retrieval - must be separated by comma Comments coming with the document Page 13

14 Queue Tab Fieldname Submit document to queue Queue Name Description Function Select whether or not a document should be placed into a queue. If you decide to place the document into a queue, you need to provide a queue name. Select the name of the queue that you would like to place the document into, after storing it into ApplicationXtender. Enter a description for the job in which the document will be submitted to a specified queue. Field Values tab When a document is added to an Application Xtender application, enter data for each of the index fields in the application. Each index field defined will be used to hold descriptive information about the documents stored in the application. Field - Enter the field name. Type - Enter the field type. The field type can be "Text", "Integer", "Date", "Boolean", etc. Required - Enter whether or not the field is required to be set. The process cannot be saved until the required fields are assigned a value. Value - Enter the value of the field. RRTs for ApplicationXtender Enterprise Connector The RRT ID for ApplicationXtender Process component is APX. The ApplicationXtender Route component does not generate an RRT. Reserved Replacement Tag Names (RRTN) Name ID Description Identifier of the document stored in ApplicationXtender. Sample: ~APX::ID~ - replaces the identifier value referring to a particular document stored in ApplicationXtender. For example consider a workflow process with MFP component as capture component, followed by the ApplicationXtender process component and the Send to Mail Recipient route component. In the Send to Mail Recipient component, place ~APX::ID~ as the subject of the . This workflow sends to the designated recipient with the ID of the document just stored into ApplicationXtender as its subject. This and all other s sent from this process can later be used as an inventory of sorts, of the documents successfully stored into ApplicationXtender. Later, if you want to reference the document, you can search ApplicationXtender for the document with this specific ID. Page 14

15 Troubleshooting Tips / Restrictions and Limitations Problem Description No applications appear in the Application field dropdown list. An error message pops up that you have to enter a value for all required fields. Solution Make sure the username and password are valid. Also, make sure that in the Application Generator, you created an application with corresponding user rights. Make sure that all fields that have the value YES under required has a field value. Restrictions and limitations This component is compatible with ApplicationXtender Version 5.x. Page 15

16 Captaris Alchemy Product Overview - Feature Highlights The Captaris Alchemy route and econnector components provide the full capability for routing documents with their associated metadata to Captaris Alchemy document management system. Alchemy is used in many organizations for archival, access, and distribution of fixed content including images and electronic documents. The only difference between the Captaris Alchemy route and econnector components is that the econnector component has two additional options in the General tab: Activate check box - makes the component active. If this check box is not selected, the component won't perform any actions during files processing. Pass-through check box - makes the document(s) available to the downstream components, when selected. These two options are absent in the Captaris Alchemy route component configuration. The Captaris Alchemy econnector and route components provide the following features: Automate document routing into Alchemy document management system. Select and create dynamically folders into which users can store documents. Control user access to databases, folders and documents. Set the schema for the simplified URL that allows displaying the stored file in Alchemy. Assign properties or fields to the routed document. Automatically update index build after the document is stored in Alchemy. Using This Component The Captaris Alchemy component allows users to capture documents using various capture components, process the captured documents through process components, and then, seamlessly and automatically, submit the documents and their associated metadata to Alchemy. An example of using the Alchemy component. The following use-case describes a typical scenario for capturing documents and routing them to Alchemy. Create a workflow with the FTP Poll capture component, the Professional Barcode component, the ABBYY FineReader OCR component and the Captaris Alchemy route component. Set the metadata of the routed documents in the Fields tab of the Captaris Alchemy component. Configure the other components in the workflow. User scans a batch of documents with barcode cover page that describes the field attribute for each document. The documents are then placed in the folder that is accessed through FTP. Now, when you start a process: FTP Capture component polls the scanned document with a pre-defined schedule. Professional Barcode component reads the barcode value out of the cover page while splitting the scanned batch into separate documents. ABBYY FineReader OCR converts the scanned documents into searchable PDF. Captaris Alchemy route component delivers the searchable PDF documents to Alchemy DMS along with the corresponding metadata. Building a Process With Captaris Alchemy The component configuration window has three tabs: General tab - sets general connection parameters for logging into the Captaris Alchemy document management system. Document tab - specifies the destination folder and the name of the routed document. Fields tab - assigns properties or fields to the routed document. Page 16

17 General tab In this tab you can specify general connection parameters for logging into Captaris Alchemy document management system. The parameters are: Activate - select this check box if you want to store captured document into Captaris Alchemy document management system. If this box is not checked, the component won't perform any actions during files processing. This option is only available to the Captaris Alchemy econnector component. Pass-through - if this check box is selected, the component will pass the document to the next component in the process. This option is only available to the Captaris Alchemy econnector component. Options file - type in the path to the options file that contains parameters for connection to Alchemy or select it using button. By default, this file is located in C:\Documents and Settings\%User%\Local Settings\Application Data\imr\alchemy\, where %User% is the Windows user name. If this field is left empty, the currently configured parameters will be used. You can use one or several available RRTs in this field. Database - enter the database you want to connect to manually or click the button. This button opens the Select Database dialog that allows you to select a database from all available databases in Alchemy DMS. You can use RRT in this field to determine database dynamically. Security group - enter the security group you want to connect to manually or click the button. This button opens the Security Group dialog that allows you to select from the list of security groups for the selected database. You can use one or several available RRTs in this field. Note: The Security Group dialog will show the list of security groups only if you have already connected to the database. For the first time, you have to enter the security group manually in order to connect to the database. Group password - enter a valid password to connect to the selected security group. This field is only enabled if the Security group is specified. Database password - enter a valid password to connect to the selected database. If the Security group is specified, this field becomes disabled. URL schema - enter a schema for the simplified URL that allows the stored file to display in Alchemy. You can use one or several available RRTs in this field. The default value for the schema is Page 17

18 Rebuild database - if you select this check box, the component will update the index, i.e. full-text index resource file containing every word that was extracted from every document. Only after the index is updated, can the document be found in the database by searching. Without an update of the index you can only find the document by browsing. Document tab In this tab you can specify the destination folder, title and filename of the routed document and set the security groups of the users that will have access to the document. Folder - select a valid folder for the specified Database using the button. This button opens the Select Folder dialog that allows you to select a folder from the list of all the folders for the database. Note: If this field is left empty, the documents will be sent to the root folder of the database Additional path - after you have selected the folder, you have the option to set a path to be appended to the folder path. If the folder specified in the appended path does not exist, the component will make a request to Alchemy to create this folder dynamically. You can use one or several available RRTs in this field. Rename title - select this check box to set the title of the document. Enter the title in the rename field, next to this check box. You can use one or several available RRTs in this field. The default renaming schema for the title is ~IMR::FileName~_~IMR::Counter~~IMR::FileExt~. Note: If this option is not selected, the resulting filename of the document will be assigned to the title. Rename file group allows you to set the filename property of the document. Select one of the options: Note: Rename with document title - select this option if you want to assign the document title to the filename. Using this schema - select this option to set the renaming schema for the filename. Enter the filename in the rename field, next to this check box. You can use one or several available RRTs in this field. The default renaming schema for the filename is ~IMR::FileName~_~IMR::Timestamp~~IMR::FileExt~. If the Rename title option is OFF and ~IMR::Title~ RRT is used in renaming schema for the filename, this RRT will be replaced by the original filename, since new name is not given to the file yet. However, the external ~IMR::Title~ RRT will be replaced by the resulting filename. Security groups group allows you to specify the security groups of the users that will have access to the document. Add - click this button to add a security group using the opened Security group dialog. Select from the drop down list of security groups for the selected database. Page 18

19 Edit - click this button to edit a selected security group using the opened Security group dialog. Select from the drop down list of security groups for the selected database. Remove - select one or several security groups from the list and click this button to remove the selected items from the list. Select Folder This dialog allows you to select a folder for the database selected in the General Tab. Root - click this button if you want to save the document in the root of the database. When you click this button, the following warning message appears: "Are you sure you do not want to store in a folder, rather the root of the database?" Click Yes to proceed. Fields tab In this tab you can assign properties or fields to the routed document. Add - click this button to add a new field to the fields list. The Add a Property dialog box will open. Modify - click this button to modify the selected field properties. The Modify a Property dialog box will open. Remove - select one or several fields, and then click this button to remove the selected field(s) from the list. Page 19

20 Add/Modify a Property This dialog allows you to add a property to the document properties list or to modify the selected property. Property - enter a name of the property manually or select from the drop down list of the available properties for the selected database. You can use one or several available RRTs in this field. Note: You can enter any text in this field, but if the entered property name is not specific for the database, an error message will occur in runtime. The opportunity of entering any text is provided only for using RRT as property name. Value - enter the property value or select it using the button if it is available. For example, if the selected property has Data type, this button is available and opens the Select a Date dialog that allows selecting a date from the calendar. You can use one or several available RRTs in this field. Type - this field displays the type of the selected field. RRTs for Captaris Alchemy Component RRT ID The RRT ID for this component is IMR. Reserved Replacement Tag Names (RRTN) Replacement Tag Names (FRTN) The following table describes the reserved RTN values for this component. Name FileName FileExt Counter Server Database FileID GUID Title URL Description The original file name value. Original file extension value. An incremental counter based on the duplicate file names found within a directory. The counter value concatenated with a name provides a unique file name. Name or address of the Alchemy IMR server. Alchemy database title. Identifier of the document sent to the Alchemy server. Global unique identifier (GUID) generated for the each input file. The resulting title of the exported document. URL for access to the document sent to the Alchemy server. This RRTN is only applicable to the Captaris Alchemy econnector component and can be used in proceeding components. The following example provides sample usage for your reference: o ~IMR::FileName~~IMR::Counter~~IMR::FileExt~- when used in the Rename title field, this RRTNs are replaced with MyDocument2.doc if the original file name is MyDocument.doc and MyDocument1.doc file already exists in the destination folder. Field Replacement Tag Names (FRTN) This component does not support any FRTN values. Page 20

21 Special Set Replacement Tag Names (SSRTN) This component supports the Date/Time tag names listed below: SSRTN Description %a Abbreviated English weekday name (Sun-Sat) %A Full English weekday name (Sunday-Saturday) %b Abbreviated English month name (Jan-Dec) %B Full English month name (January-December) %d Day of month as 2-digit decimal number (01-31) %D Day of month as decimal number (1-31) %H Hour in 24-hour format (00-23) %I Hour in 12-hour format (01-12) %j Day of year as decimal number ( ) %m Month as decimal number (01-12) %M Minute as decimal number (00-59) %p Current locale's A.M./P.M. indicator for 12-hour clock %S Second as decimal number (00-59) %U Week of year as decimal number, with Sunday as first day of week (00-53) %w Weekday as decimal number (0-6; Sunday is 0) %W Week of year as decimal number, with Monday as first day of week (00-53) %y Year without century, as decimal number (00-99) %Y Year with century, as decimal number Timestamp Composed date time stamp (YYYYMMDDhhmmss) Examples of usage of the above SSRTN include: o ~IMR::%Y~-~IMR::%m~ will be replaced by o ~IMR::Timestamp~ will be replaced by o Troubleshooting Tips / Restrictions and Limitations Problem description If you send two different files with the same names, they overwrite each other. When you use multiple processes with the component, some files (near 1% from the total amount) are rejected and not routed to the Alchemy. Solution There are two ways of solving this problem: 1. Select the Rebuild database check box. 2. Use Rename file option to set the unique filename for each document. To solve this problem, use the File Options component in the workflow process and configure it to move the rejected files to the folder that is used as the input folder by the Captaris Alchemy component. The rejected files will be routed to the Alchemy after some time. Restrictions and limitations Alchemy Client has to be installed on the machine that is running this component. Page 21

22 Content Management Queue PLEASE REFER TO **FOR DETAILED INFORMATION ABOUT THIS COMPONENT THE AUTOSTORE 5.0 CAPTURE COMPONENT REFERENCE GUIDE** Page 22

23 Documentum Product Overview and Feature Highlights Documentum is a Route component that is used to store information of any kind including text, graphics, scanned images, even sound and digital movies into company repositories called Docbases within the Documentum system. Each Docbase stores two kinds of information for each document: Document Content - the file you create using applications such as word processors or spreadsheets. Metadata, or properties the properties of descriptive characteristics, such as the document s type, format, title. This component allows: Storage of documents within the Documentum system. Instantiation of custom components; Documentum custom component are invoked to perform additional custom processing on stored documents. Dynamic folder path creation. This enables the path to be set at runtime and if the folder path does not exist then it will be created. Using the Component Examples of common business cases: The multi-functional devices are configured with a Documentum button, where pressing this button, images are scanned and then stored in a designated path in the Documentum System. The configuration of Documentum 4.x and 5.x General Tab Fieldname Docbase User Name Password Domain Path Class Name Function The Documentum database that stores both document content as well as the metadata. Enter the user name that will be used to connect to the Docbase. Enter the password for the specified user name. If required, enter the NT Domain of the specified user name. Enter a destination for the Docbase incoming documents. Enter the programmatic identifier of the custom Documentum component that is to be invoked once a document is stored in Documentum. Documents settings tab Fieldname Type Format Name Title Subject Keywords Authors Function Enter the object type of the document. Enter the format of the document. Enter the file name of the document. Enter the title of the document. Enter the subject of the document. Enter the keywords associated with the document. This is used mainly for searching. Enter the authors of the document. Page 23

24 RRTs for Documentum 4.x and 5.x This component does not generate Runtime Replacement Tags, however all the parameters can contain RRT strings. For example, when POP3 is the capture (source) component, the Documentum "User Name" parameter can be set to "~POP::To~". Troubleshooting Tips / Restrictions and Limitations Problem Description N/A Solution N/A Restrictions and limitations This component requires the Documentation Foundation Classes (DFC) version or greater. Page 24

25 DocuShare Product Overview and Feature Highlights Use the DocuShare econnector and DocuShare Route components to process and store documents into the DocuShare document management system. DocuShare users can efficiently store content from variety of sources into DocuShare repository. Once the content is captured, it becomes available for retrieval and collaboration across the network within the organization. Now you can design and implement workflows that capture electronic documents from a variety of sources such as MFPs, network/local folders, PC desktop, POP3 servers to manage and store your documents into DocuShare. The only difference between DocuShare econnector and route components is that econnector component has two additional options in the General tab: Activate check box, which allows to make the component active, if selected. If this check box is not selected, the component won't perform any actions during files processing. Pass-through check box, which makes the document(s) available to the next component in the process, if selected. These two options are not available in the route component configuration. The DocuShare process and route components provide the following DocuShare features: Automate document routing into DocuShare document management system. Select and create dynamically collections into which users can store documents. Select workspaces into which users can store documents (for DocuShare Server version 6.0 CPX only). Control user access to collections, workspaces and documents. Maintain multiple versions of a document, track its revision history, and lock a document to prevent simultaneous editing. Using the Component Scan documents from a variety of MFP devices directly into DocuShare: Design a workflow process by selecting the type of MFP used in scanning of the documents. From the component tray, select the desired process components and select the DocuShare route component for storing the scanned document into DocuShare. You can configure the DocuShare component to assign document attributes such as Title, Description, Keywords, Expiration Date, etc. that uniquely identify the document. With the server running, the walk-up MFP user (with or without authentication), enters a pre-configured function key on the control panel of the MFP device, the document with the set attributes is routed directly into DocuShare. Capture electronic documents from a local/network folder directly into DocuShare: design a workflow process by selecting Poll Directory capture component. From the component tray, select the desired process components and select the DocuShare route component for storing the scanned document into DocuShare. You can configure the DocuShare component to assign document attributes such as Title, Description, Keywords, Expiration Date, etc. that uniquely identify the document. With the Server running, the walk-up MFP user (with or without authentication), presses a pre-configured function key on the control panel of the MFP device, the document along with the set attributes is routed directly into DocuShare. Page 25

26 The Configuration of DocuShare General Tab Use this tab to enter the server connection settings for logging on to the DocuShare server. Fieldname Activate Server Address Use Proxy Server User Name Password Domain Function Select this check box if you want to store captured document into DocuShare document management system. If this box is not checked, the component won't perform any actions during files processing. This option is only available to DocuShare econnector component. Enter the URL of the DocuShare Server that you would like to connect to. You can enter the server address manually or browse using (...) button. This button opens the dialog box that displays the list of the available DocuShare Servers that are currently mapped in the DocuShare Client Select this check box to enable use of a Proxy Server if your DocuShare Server is on a private intranet and you are attempting to connect to a DocuShare site that is on the Internet. Enter the address of the Proxy Server in the field that is next to this check box. The entered address should consist of the following components: protocol prefix, server name or IP address, followed by ":", port number. For example, Enter a valid user name. This user name along with the associated password and domain (if LDAP is configured) is used to authenticate the user in to the DocuShare Server. It is mandatory to fill out this field. Enter a valid password. This password along with the associated user name and domain (if LDAP is configured) is used to authenticate the user into the DocuShare Server. It is mandatory to fill out this field. Enter the Domain if the DocuShare site uses the LDAP add-on. This domain along with the associated user name and password is used to authenticate the user into the DocuShare Server. It is mandatory to fill out this field. Page 26

27 Impersonate Pass-through If this field is checked, and a valid value is placed for the impersonator's name, the owner of the document is changed to be the impersonator. Also, the Initial Parameters on the Document tab are changed to reflect this new owner. If this box is checked, this component will pass the document to the next component in the process. This option is only available to with DocuShare econnector (process) component. Document tab Use this tab to set the document attributes Fieldname Rename Title Function Select this check box to set the title of the document. Enter the title in the rename field, next to this check box, which becomes enabled. The title should be short, but descriptive, and can contain spaces and punctuation marks. You can use one or several available RRTs in this field. If this option is not selected, the original filename of the document will be assigned to the title. If this option is selected and the rename schema field is empty, the title will be ~XDS::FileName~_~XDS::Timestamp~~XDS::FileExt~. E.g., if the original filename is Mydocument.doc, the title will be Mydocument_ doc. Note: In the previous versions of the component ~XDS::Counter~ was used in the rename schema for the duplicate file names. The current version of the component uses the ~XDS::Timestamp~ for this purpose, however the configurations containing ~XDS::Counter~ are still supported, in order to provide compliance with the previous component versions. Rename file Select this check box to set the filename of the document. Enter a filename in the rename field, next to this check box, which becomes enabled. You can use any Page 27

28 component's RRT in the rename field. If this option is not selected, the original filename of the document will be assigned to the filename. If this option is selected and the rename schema field is empty, the title of the document will be assigned to the filename. Summary Description Enter a short description of the document. The summary appears below the document's title. You can use one or several available RRTs in this field. Enter a description of the document in this field or use (...) button that opens the Enter Description dialog that allows you to enter the more long and detailed description. You can use one or several available RRTs in this field. You can include HTML tags in the document s description. Enter Description This dialog allows you to enter a detailed description of the document that you send to the DocuShare. You can use one or several available RRTs in this field. Enquoted multiline text - if this check box is selected, the entered text is stored in the special format. The text is put in quotes, the \ and " symbols are transformed to \\ and \"and the line feeds are marked as \r\n. E.g., if the entered text consists of two lines: "First line" and "Second line", it will be transformed to "\"First line\"\r\n\"second line\"". Select this check box if you want to use a multiline text as a description. If this check box is not selected, the entered text format will not be changed anyway. If you use line feeds in the entered text, the Enquoted multiline text check box becomes selected and disabled. Note: If the description contains RRT that can be replaced by the value that contains \,",\r,\n symbols or quotes at the beginning and the end of the text, the Enquoted multiline text check box should not be selected. Keywords Expiration Date Enter a comma-separated list of words to associate with the document. You can use one or several available RRTs in this field. Keywords help to categorize documents and can be used to find documents in a search. Enter the date on which the document is no longer needed manually or select using (...) button. This button opens the Select Date dialog that allows you to select a date. You can use one or several available Date\Time RRTs except for ~XDS::Timestamp~ in this field. The sent documents will be marked as expired on the server after the specified date. After that you can search for the expired documents on the server and delete Page 28

29 or archive them. Note: The default value for the date in the Select Date dialog is always the current date, even if you have previously specified some other date. Max Versions Enter the maximum number of versions of the document that you can save in DocuShare. When a new version of a document is saved to DocuShare, the oldest version is deleted. Note: The component can not add a new version to the existing document. When you send a document, it gets version number 1 in DocuShare. If after that you add new versions of this document using web interface, the number of versions will be limited by the specified Max versions value. Collection A DocuShare site consists of a number of repositories called collections, in which documents and other objects are stored. The administrator determines the initial set of containers/collections that appear on the DocuShare home page. Select the path to the container or folder in which a document will be stored using (...) button. This button opens the Select Collection dialog. Note: When you use DocuShare Client version 6.0 and DocuShare Server version 6.0 CPX you can also select a workspace to send documents into. Appended Path - after you have selected the container/collection, you can optionally set a path to be appended to the collection path. If the collection in the appended path does not exist, the component will create this collection dynamically. You can use one or several available RRTs in this field to create the appended path dynamically. It is mandatory to fill out the Collection field. In the case when the Collection field is empty and the Appended path is specified, the configuration may be saved, but the error will occur in runtime. Note: If two or more collections with the same name are located in the DocuShare, and you specify this name in the Appended Path field, another collection is created with the collection name and "_Ambiguous" appended to the collection name. The documents will be stored in this collection. Select Collection This dialog allows you to select a collection in which a document will be stored. Please select a collection of documents - this field displays the collections of the DocuShare server as a tree. Select a collection in which a document will be stored. Note: When you use DocuShare Client version 6.0 and DocuShare Server version 6.0 CPX this field also displays workspaces. You can select a workspace to send documents into. Page 29

30 Lock Document Initial Permissions...or specify a collection identifier - this field displays the identifier that is associated with the selected collection on the DocuShare server, e.g. Collection-23. You may select a collection by entering the identifier manually in this field. If you have entered the incorrect identifier, the configuration can be saved but in runtime the error message will occur. Note: If you have first specified the collection, and then want to empty the Collection field, you can empty the...or specify a collection identifier field and click OK. If you are the logged-on owner of the document or a logged-on user with Write access to the document, you can lock the document to keep other users from editing the document. Initial Permissions Same as container: Assigns the container s access permissions to the document. Same as container except write restricted to owner: Assigns the users who have Reader access to the container with Reader access to the document. The document's owner is the only user with Write access to the object. Restricted to owner: Assigns full access permissions only to the document s owner. Fields tab Use this tab to add field values to your document or clone of the document. Page 30

31 Fieldname Document Type Add Function Enter the document type you want to store into DocuShare manually or select using (...) button.. This document type has to be an existing document type or clone of an existing document type. It is mandatory to fill out this field. If an invalid document type is used (a document type that does not exist on the DocuShare server), the configuration can be saved, but in runtime the error message will occur and the process will fail. Cannot create file object for document type (test_type). The parameter is incorrect. Tip: You can dynamically and automatically route documents to DocuShare repository. You can also define attributes for the document that will be associated to the document as the document is stored. For example, you can create a super set of all (or some) fields along with associated fields values from the list of available document types. To do this, browse to the first documents type, for example "Contracts" along with the desired fields. Proceed to browse for the second document type, for example "Proposals", and append the desired fields, and so on. At this point you have selected all the desired fields (from multiple document types) and field values. Now change the Document Type to an RRT (i.e. Dynamically set document type), for example ~POP::Subject~. When you run the Server, with POP3 as your capture component, s with subject field label "Contracts" will only have the "Contracts"-related field values populated. s with subject field label "Proposals" will only have the "Proposal"- related field values populated, and so on.. You can create field values that get stored with the document in DocuShare. Click on Add button and the "Add a property" dialog box appears. Select the properties that you want to add to your file. These properties are subject to change depending on which Document Type you choose. Each Document Type has its own specific set of fields. Add/Modify Property This dialog allows to select the properties that you want to add to your file. These properties are subject to change depending on which Document Type you choose. Each Document Type has its own specific set of properties. Page 31

32 Property - enter property name manually or select from the drop-down list of the properties that are specific for the selected Document Type. You can use one or several available RRTs in this field. Value - enter property name manually or select using button. This button is enabled only if the set of specific values exists for the selected property. The button opens the Select Menu Property dialog box that allows to select one of the specific values for the property. You can use one or several available RRTs in the Value field. Note: When you select a property, the Value field displays the default value that is provided by the DocuShare Client. For some property types, e.g. , the DocuShare Client does not provide the default values, therefore the Value field does not display the default values for such properties. Type - this field displays the type of the selected property. Required - this field indicates if the selected field is required or not. Modify Remove Refresh Click on the Modify button to modify the field value attributes. Click on the Remove button to remove a field value. Click on this button to re-retrieve the most up-to-date list of fields from DocuShare server. When you initially run the component, the list of fields is populated. However, when you add and/or modify fields using the Add and/or the Modify buttons, the most updated list is not retrieved unless you click on the Refresh button.. RRTs of DocuShare The RRT ID for this component is XDS Reserved Replacement Tag Names (RRTN) The following table describes the reserved RTN values for this component. Name FileName FileExt Title URL Description Returns the original file name value. Returns the original file extension value such as.txt,.doc, etc. Returns the resulting title of the document. Returns the URL of the document stored in DocuShare. This is only applicable to the DocuShare econnector component and can be used in proceeding components. The following examples provide sample usage for your reference: ~XDS::FileName~ - When used in the "Rename title" field, this RRTN is replaced with the value MyDocument if the original file name is MyDocument.doc. ~XDS::Title~ - When used in the "Rename file" field, this RRTN is replaced with the value Report if the value entered in the Rename title field is Report. Field Replacement Tag Names (FRTN) This component does not support any FRTN values. Page 32

33 Special Set Replacement Tag Names (SSRTN) This component supports the Date/Time tag names listed below: SSRTN Description %a Abbreviated English weekday name (Sun-Sat) %A Full English weekday name (Sunday-Saturday) %b Abbreviated English month name (Jan-Dec) %B Full English month name (January-December) %d Day of month as 2-digit decimal number (01-31) %D Day of month as decimal number (1-31) %H Hour in 24-hour format (00-23) %I Hour in 12-hour format (01-12) %j Day of year as decimal number ( ) %m Month as decimal number (01-12) %M Minute as decimal number (00-59) %p Current locale's A.M./P.M. indicator for 12-hour clock %S Second as decimal number (00-59) %U Week of year as decimal number, with Sunday as first day of week (00-53) %w Weekday as decimal number (0-6; Sunday is 0) %W Week of year as decimal number, with Monday as first day of week (00-53) %y Year without century, as decimal number (00-99) %Y Year with century, as decimal number Timestamp Composed date time stamp (YYYYMMDDhhmmss) Examples of usage of the above SSRTN include: ~XDS::%Y~-~XDS::%m~ will be replaced by ~XDS::Timestamp~ will be replaced by Troubleshooting Tips / Restrictions and Limitations Problem Description The Rename Title does not work properly when used with RRTs. "Could Not Configure DocuShare Client Environment" error occurs when you attempt to start the service. This error message is displayed on the service Status Monitor window. "Unable to Load DSSUP2. Cannot Confirm DocuShare Client Configuration error occurs when you attempt to start the service. This error message is displayed on the service Status Monitor window. The document is not sent to the DocuShare server and the Status Monitor shows the following error message: Solution Make sure that you are logged into the service (Log On NT as) with the correct permissions. Whoever was logged into the machine when DocuShare Client was installed has to be running the service. This error occurs when the DocuShare client is not installed on the machine running the service or when the service was not started with the correct permissions. This error occurs when the service cannot locate the DocuShare Client libraries. This is caused when the DocuShare client is not installed on the machine running the service or when the service was not started with the correct permissions. This message means that an invalid Document type is specified (a document type that does not exist on the Page 33

34 "Cannot create file object for document type #type#. The parameter is incorrect.", where #type# is the configured Document type. (HTTP/ Internal Server Error) Error code (-400) error occurs. DocuShare server). Please specify the correct Document type. Make sure that all the required properties of the Document Type have default values specified on the DocuShare server. Restrictions and limitations DocuShare Client has to be installed on the machine that is running this component. The version of the DocuShare Client should be the same as the version of DocuShare Server. This component works with DocuShare Server versions 4.0.1, 5.0 and 6.0 CPX. This component is only storing documents, collections and workspaces and is not capable of storing any other object types such as bulletin, group, etc.. When you change the Server Address, you have to update the Collection (even if the same collection path exists on both servers) and the Document Type, since internally, associations are made to these specific fields, which are hidden from the user. In some situations you may browse to a specific collection path, and then decide to delete the collection from the DocuShare server. If for some reason you decide to recreate a new collection with the same name, the DocuShare component configuration has to be updated to reflect this change, since internally, associations are made to collections. Collections are internally identified by a specific Handle (refer to the DocuShare Administrator s Guide) which will change once it is deleted and recreated. Therefore, it is not recommended to delete Collections from a DocuShare server without updating the DocuShare component configuration. When several files are sent to the DocuShare server at the same time, and RRTs are used in the Rename title field, the component may not have enough time to index all the sent files correctly on the server. This can lead to appearing of several documents with the same title on the DocuShare server. To avoid this, it is not recommended to send many files during the short period of time. When you use RRTs in the Appended path field for creating new collections, the component may not have enough time to index all the collections correctly on the server. This can lead to appearing of several collections with the same name on the DocuShare server. To avoid this, it is not recommended to send many files during the short period of time. For correct work of the component it is not recommended to change the specific sets of properties for document types on the DocuShare server while the documents are being uploaded on the server. When several (5-10 or more) concurrent processes with the component are working, some of the processes may send files to DocuShare with a considerable time delay. Page 34

35 Domino.Doc Product Overview and Feature Highlights The Domino.Doc Component provides scalable content capture server software technology to help you capture your corporate business content into Domino Document Manager Family of products. Domino.Doc improves your organization's efficiency through enhanced collaboration and information management. Domino.Doc Route Component delivers scalability, flexibility and low cost of ownership required to support enterprise-wide document, content, and records capture, while serving as a foundation for corporate content capture. This component provides: The Domino.Doc Route component offers server based content routing into Domino.Doc document management application. This integration allows for: Content based routing Route documents based on the document content. Multi-Server integration write into one or many Domino.Doc servers. Full messaging integration Combine Domino.Doc route component with other components to take advantage of Notes or Exchange integration features. Offers integration with Libraries, Cabinets, and Binders Capture content at any level and expand your content capture reach by taking advantage of your Domino.Doc hierarchies. Integration with Profiles Transfer index data from devices, users, documents, or other type of content directly into integrated profiles. Using the Component Write documents and index data into the back end libraries. Write index data into Domino.Doc and store a URL (or other types of identifiers) pointing into the document location from other systems into Domino.Doc. This method allows you to create a record and link the documents into a central location. Use Runtime Replacement Tags (RRT) to dynamically link multiple components together and allows close integration of extracted content into your Domino.Doc document management system. The Configuration of Domino.Doc General Tab Page 35

36 Fieldname Protocol Server User Name Password Function Select the Protocol from the drop-down list. Type the Server Name where Domino.Doc has been installed. You can also enter the IP address for the Domino.Doc server. Type the name of the user that has sufficient access to this server for completing the task at hand. Type the password for the user. Document Tab Fieldname Library Path Function Type the full path name (must be DNS enabled) to the Domino.Doc Library. (For Example, the following would be the Server name followed by the Path Name: Cabinet Binder Profile Title Comment Where the Server Name = DominoServer and the path to the Domino.doc Library = domdoc/dominodoc2lib.nsf) Type the Domino.Doc cabinet of choice. Type the Name of the Binder. Select the document Profile where the index values are located. Using Field Values tab, map the index fields into the document Profile field. Type the Title for the document. After the document(s) have been found the new document will be appended to the existing documents. Type the comment for this document. Page 36

37 Field values tab Fieldname Add Modify Remove Function You can add field name entries and field values to a document. Click on the Add button and the Field Values dialog box appears. Enter the field name and the corresponding value for the field name. Click on Modify to change the field name value. Click on Remove to remove the field name entry. RRTs of the Domino.Doc Component This component does not generate Runtime Replacement Tags, however all the parameters can contain RRT strings. For example, when POP3 is the capture (source) component, the Documentum "User Name" parameter can be set to "~POP::To~". Page 37

38 Troubleshooting Tips / Restrictions and Limitations Problem Description The Server name is not a known TCP/IP host name error. Domino / Notes are on the same machine, and you get a TCP /IP error the <server name> is not a known TCP/IP host Solution Make sure the Script is pointing to the correct Domino Server Name. Also, make sure you have a connection to that server on your connection document. Make sure the Server is not referred to by its FQDN which in most cases is wrong, such as MYSERVER.MYCOMPANY.COM. Actually this is not registered on the Internet as a FQDN, so the client may try to look it up though the DNS and never find it. To solve this make sure of the following: 1. If you have a bogus input in the FQDN for the server on the address book remove it or for best results. 2. Put in the server name <the Domino server name not the domain name > and on the HOSTS file on your machine as an entry for this new Host EX MyDominoServer Make sure you can ping the server name from the command prompt. 1- Check for our previous solution on the previous troubleshooting tip for Server connection + DNS / host name resolution from address book 2- If by any chance you did a mistake and pointed to the C:\LOTUS\DOMINO during the installation of AutoStore instead pointing to the right folder which C:\LOTUS\NOTES, you must remove some the following.. [a] Remove AutoStore [b] Remove Domino from your systems path ; ex, c:\lotus\domino [c] Make sure you install a full notes client [d] Make sure you include your Notes executables in the systems path; ex. c:\lotus\notes [e] Reboot your machine [f] Remove this entry from your NOTES.INI in your server folder EXTMGR_ADDINS=extpwd [g] Delete the following file from your DOMINO folder c:\lotus\domino... nextpwd.dll [h] install AutoStore again and point to the correct Notes folder. [i] Reboot your machine and load DOMINO and then start you work. Restrictions and limitations You must have Lotus Notes Client installed on the same server. You must have Domino.Doc desktop installed on the same server. You must make sure to have the Lotus Notes Client on the PATH variable. Important Note: If you have Lotus Domino Server on the PATH variable, this component will not work. You must make sure the password DLL is placed within the Lotus Notes Client directory. Page 38

39 FileMagic Product Overview and Feature Highlights Use the FileMagic econnector and FileMagic Route components to process and store documents into the Westbrook FileMagic Document Management System. FileMagic users can efficiently store content from a variety of sources into a database. Once the content is captured, it becomes available for retrieval and collaboration across the network within the organization. Now you can design and implement workflow that capture electronic documents from a variety of sources such as MFP devices, network/local folders, PC desktop, POP3 servers to manage and store your documents into FileMagic. The only difference between FileMagic econnector and FileMagic route component is that the econnector component provides a document Pass-through option. This option, when selected, passes the document to the next component in the process. This component supports FileMagic Version 2.2 with Service Pack 5. Using this Component Scan documents from a FTP site directly into FileMagic: Design a workflow process by selecting FTP site that has a series of files to be processed. You can configure the FileMagic component to assign document fields, depending on the Document Type that was selected. The document with the set attributes is routed directly into FileMagic. The Configuration of FileMagic General tab Enter the FileMagic attributes in this tab. Field Name User Name Password Database Description Enter a valid user name. This username along with the associated password is used to authenticate the user into FileMagic Enter a valid password. Select the database you want to store documents into. Page 39

40 Document tab Enter document attributes in this tab. Field Name Document Type Folder Description Description Select from the available document types that you would like to associate to the document you are storing. Document Types define the nature of the contents of a document, including all the fields used to index documents of this type. For example a Medical Form has the name of the patient and the doctor. The patient name and the doctor name fields would be associated with that document type. The fields are used for indexing the documents. In other words, depending on the document type you choose you have different fields associated to the document. Select the folder that you would like to store the document into. If the folder does not exist, the files are stored in the root of the database. With this component, dynamic folders cannot be created. Enter a description of the original document. Fields tab Enter the Field attributes in this tab. Page 40

41 Add Modify Remove You can create field values that get stored with the document in FileMagic. Click on Add button and the "Add a property" dialog box appears. Select the properties that you want to add to your file. These properties are subject to change depending on the Document Type you choose. Each Document Type has its own specific set of fields. Click on Modify button to modify the field value attributes. Click on Remove button to remove a field value. RRTs for FileMagic Component RRT ID The RRT ID for this component is FMG. Reserved Replacement Tag Names (RRTN) The following table describes the reserved RTN values for this component: Name ID Description The unique identifier for the stored document, which can be used by the econnector in proceeding components. Example: Configure a process with the FileMagic econnector and Send to Database Route component. When Send to Database component is configured with the appropriate table, specify a field with the value of ~FMG::ID~. Once the documents are successfully stored into FileMagic and sent to the Send To Database component, the database will have an entry for the ID of the document saved. Troubleshooting Tips / Restrictions and Limitations There is no information available at this time. Page 41

42 FileNet Product Overview and Feature Highlights FileNet component is used to provide full integration with FileNet Image Server and FileNet Document Server. This component provides the full capability for routing documents and index data into FileNet libraries, classes, and folders. Dynamic mapping using RRT values provides ability to map all available index data extracted from a document content or captured from users to be stored into FileNet depository. Integration with FileNet document security is also provided by the component. The security integration allows assigning users and groups that will have permissions for accessing documents routed to FileNet, and setting access levels for these users and groups. The only difference between FileNet Route and FileNet Process component is that FileNet Process component has two additional options in the General tab: Activate check box, which allows to store captured document into FileNet, if selected. If this check box is not selected, the component won't perform any actions during files processing. Pass-through check box, which makes the document(s) available to the downstream components, if selected. These two options are not available in FileNet Route component configuration. Note: FileNet client software must be installed on the same machine as Workflow Service and it must be fully configured prior to setting up the FileNet component. For this component to work with FileNet Image Services the following software should be installed: On the FileNet machine: Image Services, release On the Server machine: IDM Desktop 3.3, build erk For work with FileNet Content Services the following software should be installed: On the FileNet machine: Content Services 5.4, 5.3, or 5.2. On the Server machine: IDM Desktop 3.3, build erk ; FileNet Client Library: Integration Build Release "yu " (includes FileNet CS 54x Client Libraries "yu " and FileNet CS 43x Client Libraries "yu "). FileNet component is used to store documents and field values in FileNet document libraries. The following features are provided: Connect to FileNet with desired user name and password Select the desired FileNet document library and folder to store files into Assignment of FileNet class properties to the files Add field values to documents Allow access to specific FileNet users and groups, which is provided through integration with FileNet document Security settings. Using the Component Scan documents from a variety of MFP devices directly into FileNet: Design a workflow process by selecting the type of MFP used in scanning of the documents. From the component tray, select the desired process components and select the FileNet route component for storing the scanned document into FileNet. You can configure the FileNet component to assign any document attributes acceptable by the FileNet library. With the server running, the walk-up MFP user (with or without authentication), enters a pre-configured function key on the control panel of the MFP device, the document with the set attributes is routed directly into FileNet. Page 42

43 Allow users to send documents from desktop directly into FileNet: Use the AutoCapture component as a capture source and FileNet as a route component in your workflow process. In AutoCapture configuration create a form that allows users to enter necessary document attributes. Set up the FileNet route component to use corresponding RRTs for filling document properties. For example, you can require users to select document class before submitting documents to AutoCapture server, so that a file deposited to the FileNet library will have correspondent document class. You also might want to add an OCR process component to the workflow in order to recognize image documents and index them on the FileNet server making it possible to search through routed documents. Installing and configuring FileNet client Below is the common procedure for installation and configuring FileNet client. Installation: 1.1. Install IDM ToolKit 3.3 package. Note: Setup program will reboot the computer without prompting. Save all documents before installation process During installation make sure that the Image Services and Content Services components are selected. Explorer Integration is recommended (for configuration testing purposes). All types of Microsoft Office integration are not recommended Install Content Services Admin Tools\Client.Lib\Win32\English\ package. Configure ODBC source (for FileNet Content Services only): 2.1. Open Administrative Tools/Data Sources (ODBC) Select System DSN tab Click Add, select SQL server, click Finish In the Create a new data source to SQL server wizard specify the values obtained from FileNet server administrator: Name: FileNet Storage manager Server name Server: FileNet server (SQL server) machine name Click Next Security: check SQL Server authentication (if FileNet server does not use LDAP) Select Connect to SQL Server to obtain default check box. Specify database administrator user name and password (login "sa" with empty password by default) Click Next Select Change the default database to check box and select FileNet content service database name (name of Library system in the CS configuration). Click Next Keep page defaults. Click Finish Click Test data source to make sure it is accessible. Click OK to complete ODBC configuration. Configure FileNet Neighborhood library Open Start/Programs/FileNet IDM/Configure Select Set default preferences for new users check box to allow FileNet Route component to work in service mode with the FileNet library. 3.3 Click Add Select FileNet service type (Image Services for IS or Document Services for CS) Specify Library name (may be any text string) For Content Services specify: System: Library system name (from the FileNet CS configuration on the server) Host machine: ODBC source name (as configured in 2.4.1) For Image Services specify: Domain: first part of NCH domain name (as configured in FileNet IS setup) Organization: second part of NCH domain name (as configured in FileNet IS setup) Click OK to add the library. The new library should appear in the Preferred Libraries list. Check if the library is accessible using FileNet Neighborhood shortcut on the desktop (if Explorer Integration has been installed) or in the Windows Explorer. You should obtain FileNet user name and password from the FileNet server administrator. Note: Make sure to log off from the library so that the FileNet component can place files there. Page 43

44 The Configuration of FileNet General tab In the General tab you can set connection parameters and define document options such as the document class and destination folder. Activate This check box is present only in process component configuration window. Select this check box if you want to store captured document into FileNet. If this box is not checked, the component won't perform any actions during files processing. Pass-through This check box is present only in process component configuration window. Select this check box if you want the document(s) to be available to the rest of the components in your process. Connection Parameters Use network name - Select this checkbox if you want to use the network name to connect to FileNet server instead of defined user name. User name - Enter a user name for accessing FileNet. The user name can also be assigned to external values using RRTs. Password - Enter the password for the defined user name. Document library - Select FileNet document library which you plan to use for routing documents. Document Options Document class - Select document class belonging to the chosen library. Stored files will receive properties of the class (e.g. its fields). Index - Select this checkbox to index stored files. Destination folder - Select a destination folder where the files will be stored in. The folder belongs to the chosen library. You can use RRTs within the folder name to create the destination path directly during file processing. Page 44

45 Field Values tab In the Field Values tab you can create and edit fields for the selected Document class. All routed documents will have these fields. List of fields - At the top of this tab, there is a list of fields, which belong to the selected class, along with their values. Add - To add a field, click the Add button or double click the empty space in the list. The Add field dialog will open. Edit - To edit a field, select the field in the list and click Edit or double click the chosen field. The Edit field dialog will open. Delete - To delete a field, select the field in the list and click Delete or use the Delete key of your keyboard. Note: If during processing of a document, the component cannot set a certain field value (if its name or value is not correct for the specified document class), the field will be ignored. If a value of a required field is not provided, the FileNet library will not accept such document for storage, and an error will be reported by the component in the Status Monitor window. Add/Edit field value Field name - Enter a name for the field or select one from the FileNet server. To do this, click the "..." button near the Field name string, and the Select class field dialog will open. Note: You cannot use a field which does not belong to the class in the library or does not exist. If you try to use a non-existent field, an error message will appear. Field value - Assign a value to the field. You can type a value into the Field value string or click the "..." button near it, and the Field value dialog will open. Note: RRTs can be used as Field names and as Field values, but the values of the tags must be correct: RRTs for field names must assign fields which belong to the class Page 45

46 RRTs for field values must satisfy the fields' types You may use the component's RRTs only in Field value field. Use ~FNR::Counter~ to generate unique field value.. Select class field In this dialog there is a list of fields belonging to the selected Document class. Select a field that you want to assign to deposited files in your process. Name - is a name of the field. Label - is a field label. Required - the property shows if the field is required to be filled in or not. Current value - is the current value of the field. Field value In this dialog, you can set value for the field according to its type. Field name - is the name of the field entered in the Add/Edit field value dialog. Field label - is the label of the field entered in the Add/Edit field value dialog. Field value - enter the desired field value. Document Security tab In this tab you can assign access rights for files being placed to the FileNet system. You can specify proper access levels for users and groups. Please note that the behavior of this tab depends on the Services type, so that only permissions allowed by a certain FileNet server can be entered. If the component cannot connect to the FileNet server, no such checks will be performed. Access list - At the bottom of the dialog there is a list of users and groups who have rights for the deposited files. You can configure access level for each of them according to customary levels of the selected library. Page 46

47 Users and Groups - To add a user or a group select the corresponding radio button. When you select an item in the access list, the radio button is checked, which corresponds to the item type (user or group). Name - Select from the drop-down list the name of a user/group which you are going to add to access list. Access Level - Set an access level to be assigned to the selected user/group. Members - If a group is selected in the access list, the Members button opens a list of the group's members. The members list is not editable. Add/Modify - Click Add to add a user or a group to the access list. Click Modify to change attributes of an existing item. To add a user or a group to the access list, select the user or the group from the Name drop-down list, set the Access level and click Add. The user or the group will be added to the list. For Image Services, you can modify groups and users who have each of 3 access levels available. For Document Services, you can modify the access level for any user or group. To do so, select an item in the access list. Change the access level (for Document Services) or select another user or group name (for Image Services). At this time, the Add button is replaced with the Modify button. Press Modify. Your changes will be reflected in the access list. Remove - To deny a user/group access to files, select a user/group in the access list and click Remove. Notes: 1. Image Services allows exactly 3 access levels: read, write, append/execute. 2. The FileNet component allows entering RRTs in the Access level and in the user/group Name fields. However, if security settings contain RRTs, they cannot be validated by the component at the configuration time. 3. In some cases Services type (Image/Document) is unknown at the configuration time. For example, when RRT is used as the Library. In such cases no input validation is performed, and the user should specify permissions manually. Valid access types are: For Document Services: Owner None Viewer Author Admin For Image Services: Read Write Append (for "Append/Execute" access) When this component processes the document, all invalid entries are ignored. If some of Image Services "read", "write" or "append/execute" access rights does not have a valid user/group name specified, the component grants such access type to default user "(ANYONE)". When there are no valid permissions provided for the Document Services library then the document's permissions defaulted to the current user (i.e. user specified on the General tab) as Owner. RRTs for FileNET Component RRT ID The RRT ID for this component is FNR Reserved Replacement Tag Names (RRTN) The following table describes the reserved RTN values for this component. Name Description FileName The original file name value. FileExt Original file extension value. Counter Automatically selected number to form unique value Page 47

48 Examples usage of the above RRTN include: ~FNR::FileName~~FNR::Counter~ is replaced with "MyDocument2" for the value of Field1 field assigned to routed MyDocument.doc file if the file with Field1=MyDocument1 already exists in the destination folder. Field Replacement Tag Names (FRTN) This component does not have any FRTNs. Special Set Replacement Tag Names (SSRTN) This component supports the Date/Time tag names listed below: Name Description %d Day of month as decimal number (01 31) %j Day of year as decimal number (01 366) %I Hour in 12-hour format (1 12) %H Hour in 24-hour format (00 23) %P Current locales AM/PM indicator for 12-hour clock %M Minute as decimal number (00 59) %m Month as decimal number (01 12) %b Abbreviated english month name (Jan - Dec) %B Full english month name (January - December) %S Second as decimal number (00 59) %U Week of year as decimal number, with Sunday as first day of week (00-53) %W Week of year as decimal number, with Monday as first day of week (00-53) %w Weekday as decimal number (0-6; Sunday is 0) %a Abbreviated english weekday name (Sun - Sat) %A Full english weekday name (Sunday - Saturday) %y Year without century as decimal number (00-99) %Y Year with century as decimal number Examples usage of the above SSRTN include: ~FNR::%Y~-~FNR::%m~ will be replaced by " Note: All the component's RRTs may be used only in Field value field in Add/Edit Field Value dialog of the component configuration. Use ~FNR::Counter~ to generate unique field value. Troubleshooting Tips / Restrictions and Limitations Problem description Library is not found in FileNet Neighborhood At run-time, an error occurs: "Failed to create library object for 'DefaultIMS:Imaging:FileNet'. Error Number: Error Description: Item is not in collection." Solution This message appears when FileNet document library is not correctly selected in General tab of the component's configuration. To verify that the library exists, use browse "..." button near the Document library string. Possible reason is that the Server does not have permissions for accessing the library. At the configuration time, FileNet is accessed with currently logged user credentials, whereas at run-time, the Server typically uses Local System account. In order to allow this account accessing FileNet libraries, you should make them accessible for all local users. Page 48

49 Run the utility Configure (Start, Programs -> FileNet IDM). At the bottom of the IDM Configure window, there are two radio buttons: "Set preferences for currently logged on user (<user name>)" and "Set default preferences for new users". Depending on the selection, you will be able to view and edit the list of libraries accessible for current user only or for every user of this machine, correspondingly. In order a library to be accessible by Local System account, you should create it with the "Set default preferences for new users" option switched on. Note. The radio buttons are only visible if current user is Power User or Administrator. In other case it will not be possible to create libraries available for all users. Cannot retrieve fields list for the document class The documents are not stored in the FileNet destination folders RRTs of other components are not replaced This message appears when FileNet document class is not correctly chosen in General tab of the component's configuration. To verify that the class is input correctly, use browse "..." button near the Document class string. Verify that Document folder is set correctly. The User which you define to connect to FileNet must have access to write into the folder. Also check the document security options and verify that you have rights to view files in the folder. Check if there is a blocking component (e.g. Data Interchange) in your process. Only RRTs of the components which appear after the blocking component can be replaced in the configuration entries of the FileNet component. The component is intended for work with FileNet Image Services and FileNet Content Services. For this component to work with FileNet Image Services the following software should be installed: On the FileNet machine: Image Services, release On the Server machine: IDM Desktop 3.3, build erk For work with FileNet Content Services the following software should be installed: On the FileNet machine: Content Services 5.4, 5.3, or 5.2. On the Server machine: IDM Desktop 3.3, build erk ; FileNet Client Library: Integration Build Release "yu " (includes FileNet CS 54x Client Libraries "yu " and FileNet CS 43x Client Libraries "yu "). Page 49

50 Folder Store Product Overview and Feature Highlights Folder store component is a Store component that allows files to be copied into any local or network directory. Using directories is one of the fastest methods for implementing a document storage system as, storing files into flat folders requires no database, no application, and lower cost of ownership. Using Folder Store you can create business rules for folder location, security access, and file naming of scanned imaged and processed file. This component is also capable of checking security access level of the user prior to storing documents into folders. Using the check security feature, users scanning document into folder destination can only store into the destination directory if proper access level is provided by the administrator. Using this feature an organization can implement a secured storage location that only accepts files based on security settings. If you enable the Check User Security option, you need to have Active Directory Services with a minimum of Windows NT and Service Pack 3 and later. Using the Component Use this component to: Create dynamic folder names and locations. Option to rename the file, based on document index information, field values, or field value references. Option to Check User Security to check user level security against the destination folder location. Only accept users with write permission to store files into destination location. All types of files including images can be processed through this component. Folder store is fully integrated with other components such as Barcode, Form Recognition, OCR, PDF, etc. For example, a barcode value can be used as part of destination folder name to create dynamic destination folder based on barcode values on the document. A list of most common usage scenarios are provided below: A very common usage scenario is where a user logs into a device, scans a document and the document is placed in user's directory on a shared network drive. Use this component to store information into a folder where another process will be reading the information for processing. Page 50

51 The Configuration of Folder Store Use the options here to define the structure of how documents are stored. Folder path Enter the destination folder path that you want files to be copied to. The server must have write access to this folder. The input device can dynamically set the folder path. Overwrite existing file If this attribute is set to Yes, the current file overwrites any file that has the same name. Rename file Check this box if you want the output file to be renamed based on the Rename Schema settings. Schema Enter the Schema name for the output file name. You can use Runtime Replacement Tags (RRT) to dynamically set the value of the schema. If the Rename file checkbox is checked off, however a schema name is not provided, then at runtime the Schema name defaults to: ~FLD::FileName~_~FLD::Counter~~FLD::FileExt~. For example, if the input file name is File.tif, the renamed file will be File_1.tif. Check user security If this attribute is set to Yes, the system checks the user's or sender's security level to verify the write access. This refers to a look up in the user's Active Directory Services to see if the user has security rights to copy the files to the designated folder. Check User Security option enables the server to check for the write permission availability on the destination folder for the user specified in the field "User Name". The LocalSystem account in the service manager can be replaced by DOMAIN\username with the username's password to allow any process to write to any shared network folder that the user who's account is used (DOMAIN\username) to write to the shared network folder. Username Enter the user name for the directory. The most common usage includes use of RRT variables to replace the User Name field. Page 51

52 RRTs for Folder Store Component RRT ID The RRT ID for this component is FLD Reserved Replacement Tag Names (RRTN) The following table describes the reserved RTN values for Schema field of this component. Name FileName Counter FileExt Description The original file name value. An incremental counter based on the duplicate file names found within a directory. The counter value concatenated with a name provides a unique file name. Original file extension value The following example provides some sample usage for your reference: ~FLD::FileName~~FLD::Counter~ - replaced with the value Document5 if the original file name was Document and there were up to 4 (Document1 to Document4) files already within the destination folder path. Field Replacement Tag Names (FRTN) This component does not have any FRTNs and replacement of field names with metadata values. Special Set Replacement Tag Names (SSRTN) This component supports the Date/Time tag names listed below: SSRTN Description %a Abbreviated weekday name %A Full weekday name %b Abbreviated month name %B Full month name %d Day of month as decimal number (01 31) %H Hour in 24-hour format (00 23) %I Hour in 12-hour format (01 12) %j Day of year as decimal number ( ) %m Month as decimal number (01 12) %M Minute as decimal number (00 59) %p Current locale s A.M./P.M. indicator for -hour clock %S Second as decimal number (00 59) %U Week of year as decimal number, with Sunday as first day of week (00 53) %w Weekday as decimal number (0 6; Sunday is 0) %W Week of year as decimal number, with Monday as first day of week (00 53) %y Year without century, as decimal number (00 99) %Y Year with century, as decimal number Examples of usage of the above SSRTN include: ~FLD::%Y~-~FLD::%m~ will be replaced by Page 52

53 Troubleshooting Tips / Restrictions and Limitations Problem Description Access is denied to a directory Path not found message Solution User does not have appropriate access rights to the directory. Check with the administrator to grant you the proper rights. Make sure the username used for mapping drives is the same as the username that runs the service. Go to Setting>Control Panel> Service Manager to view the username that is logged into NT. Confirm this is the same user that mapped the drives, as map drives is user-based. Restrictions and limitations It is recommended to have a ~FLD::Counter~ in the schema name definition rather than "%c". Page 53

54 Fortis Product Overview and Feature Highlights Use the Fortis econnector and Fortis Route components to process and store documents into the Westbrook Fortis Document Management System. Fortis users can efficiently store content from a variety of sources into a database. Once the content is captured, it becomes available for retrieval and collaboration across the network within the organization. Now you can design and implement workflow that capture electronic documents from a variety of sources such as MFP devices, network/local folders, PC desktop, POP3 servers to manage and store your documents into Fortis. The only difference between Fortis econnector and Fortis route component is that the econnector component provides a document Pass-through option. This option, when selected, passes the document to the next component in the process. This component supports Fortis Version 2.2. The Fortis econnector and route components provide the following Fortis features: Automate document routing into Fortis document management system. Add metadata to documents for indexing Using this Component Using this component to: Scan documents from a FTP site directly into Fortis: Design a workflow process by selecting FTP site that has a series of files to be processed. You can configure the Fortis component to assign document fields, depending on the Document Type that was selected. The document with the set attributes is routed directly into Fortis. Capture electronic documents from a local/network folder directly into Fortis: Design a workflow process by selecting Poll Directory capture component. From the component tray, select the desired process components and select the Fortis route component for storing the scanned document into Fortis. You can configure the Fortis component to assign document fields, depending on which Document Type was selected. With the Server running, the walk-up MFP user (with or without authentication), enters a pre-configured function key on the control panel of the MFP device, the document along with the set attributes is routed directly into Fortis. General tab Enter the Fortis attributes in this tab. Page 54

55 Field Name User Name Password Database Description Enter a valid user name. This username along with the associated password is used to authenticate the user into Fortis. Enter a valid password. Select the database you want to store documents into. Document tab Enter document attributes in this tab. Field Name Document Type Folder Description Description Select from the available document types that you would like to associate to the document you are storing. Document Types define the nature of the contents of a document, including all the fields used to index documents of this type. In other words, depending on the document type you choose you have different fields associated to a document. For example a Medical Form has the name of the patient and the doctor. The patient name and the doctor name fields would be associated with that document type. The fields are used for indexing the documents. Select the folder that you would like to store the document into. If the folder does not exist, the files are stored in the root of the database. With this component, dynamic folders cannot be created. Enter a description of the original document. Page 55

56 Fields tab Enter the Field attributes in this tab. Field Name Add Modify Remove Description You can create field values that get stored with the document in Fortis. Click on Add button and the "Add a property" dialog box appears. Select the properties that you want to add to your file. These properties are subject to change depending on the Document Type you choose. Each Document Type has its own specific set of fields. Click on Modify button to modify the field value attributes. Click on Remove button to remove a field value. RRTs for Fortis Component RRT ID The RRT ID for this component is FTS. Reserved Replacement Tag Names (RRTN) The following table describes the reserved RTN values for this component: Name ID Description The unique identifier for the stored document, which can be used by the econnector in proceeding components. Example: Configure a process with the Fortis econnector and Send to Database Route component. When Send to Database component is configured with the appropriate table, specify a field with the value of ~FTS::ID~. Once the documents are successfully stored into Fortis and sent to the Send To Database component, the database will now have an entry for the ID of the document saved. Troubleshooting Tips / Restrictions and Limitations There is no information available at this time. Page 56

57 FTP Store Product Overview and Feature Highlights This component is a destination component that provides you with the mechanism for storing files that are fed from a source component to the FTP site for storage. Additional control over the FTP site transmission is provided through support for secured FTP sites as well as bandwidth flow-control. You can design your process according to your business process, such that a client (anonymous or specific) may then open an FTP session to this server for document retrieval, etc. as required by the business process. Active flow control Secured FTP site access Supports dynamic file renaming and storage Using the Component The following are examples of how this component may be used: An enterprise where PDF documents from several sources need to be placed on an FTP server. These documents may then be processed for printing, or sending out as Connectivity of remote offices to central office can easily be implemented using FTP component. Scanners from all remote sites can easily be connected to central site using a secured FTP protocol. Control the bandwidth usage when connecting remote scanning offices through use of the Bandwidth control feature of FTP component. Bandwidth control lowers the impact of implementing distributed scanning on transmission infrastructure. The Configuration of FTP Store Set the attributes of the FTP site here. Server name Specify the IP address or the server name of the FTP site. You can also specify the ftp site as ftp://company-site.com User name Specify the username of the client that will have access right to the ftp site. After you specify the user name, specify the password associated with this user. If you do not specify the username, by default the access right will be set to anonymous. Page 57

58 User password Specify the password that is associated with the username. Destination Folder Path You can specify the folder where the documents will be stored on the ftp server. If you specify a new folder in the dialog box, a new folder with the same name is created on the FTP server. However, if you do not specify a path or folder name, the data gets stored on the root directory of the FTP server. Overwrite Destination File Check this box if you want the newly created files on the FTP site to get overwritten on the existing files of the same name on the FTP site. If you do not check this option, the file will automatically be appended with a number that is incremented each time a newer version of the file is to be stored on the FTP site. Rename File Check this box is you want the output file to be renamed based on the Rename Schema settings Schema Enter the Schema name for the output file name. You can use Runtime Replacement Tags (RRT) to dynamically set the value of the schema. Advanced Setting Use the options in this tab to optimize the flow control settings. Activate Flow Control FTP component provides an easy method to flow control the speed at which the data is transmitted. The purpose of the flow-control option is to provide means to manage the impact of FTP transmission may have on the transmission bandwidth from remote sites. The flow control knobs allow you to control the size of the buffer and the transmission interval of each buffer. Additional control is provided to test the flow control speed and provide an easy to use method to check the transmission speed. Check the Activate Flow Control box to activate the flow control options. Transfer Rate in Milliseconds use this knob to set your desired transfer intervals in Milliseconds. The longer the interval the slower the transmission rate. Buffer Size in Bytes use this knob to set the size of each transmitted buffer. The larger the buffer size the higher the transmission rate and the larger impact on the bandwidth. Page 58

59 Run Test test will be conducted against your FTP site. Make sure you have specified correct FTP site, user name and password. The tests are conducted using 100Kbytes buffers and at the end of each test cycle the results are reported in 100 Kbytes/X Seconds. Where X is the number of seconds it takes to send 100 Kbytes. Normal B/W documents are between 25 to 50 Kbytes. The size of images could vary based on type of scanner settings and you should observe your scanner setting parameters. Please note that you must have write access to conduct FTP testing against a site. Stop use the stop button to terminate test buffer Note To use the test feature, you must have access to the FTP site from your machine. This feature establishes connection to the FTP site and transmits dummy data to the FTP site to test transmission bandwidth. RRTs for FTP Store Component RRT ID The RRT ID for FTP Store component is FTP Reserved Replacement Tag Names (RRTN) The following table describes the reserved RTN values for Schema field of this component. Name FileName Counter FileExt Description The original file name value. An incremental counter based on the duplicate file names found within a directory. The counter value concatenated with a name provides a unique file name. Original file extension value The following example provides some sample usage for your reference: ~FTP::FileName~~FTP::Counter~ - replaced with the value Document5 if the original file name was Document and there were up to 4 (Document1 to Document4) files already within the destination folder path. Field Replacement Tag Names (FRTN) This component does not have any FRTNs and replacement of field names with metadata values. Special Set Replacement Tag Names (SSRTN) This component supports the Date/Time tag names listed below: SSRTN Description %a Abbreviated weekday name %A Full weekday name %b Abbreviated month name %B Full month name %d Day of month as decimal number (01 31) %H Hour in 24-hour format (00 23) %I Hour in 12-hour format (01 12) %j Day of year as decimal number ( ) %m Month as decimal number (01 12) %M Minute as decimal number (00 59) %p Current locale s A.M./P.M. indicator for -hour clock %S Second as decimal number (00 59) %U Week of year as decimal number, with Sunday as first day of week (00 53) %w Weekday as decimal number (0 6; Sunday is 0) %W Week of year as decimal number, with Monday as first day of week (00 53) %y Year without century, as decimal number (00 99) %Y Year with century, as decimal number Page 59

60 Examples usage of the above SSRTN include: ~FTP::%Y~-~FTP::%m~ will be replaced by Troubleshooting Tips / Restrictions and Limitations Problem Description Solution Access denied message Check username/password to make sure it is valid. Check the access rights for the user. Check to make sure there are no firewalls Page 60

61 Hummingbird/Open Text edocs Product Overview and Feature Highlights The purpose of the Hummingbird/Open Text edocs route and econnector components is to store documents into the Hummingbird/Open Text edocs DM server, where records can be identified or searched for, by using database queries. The component runs on a client machine that has access to the Hummingbird/Open Text edocs DM server. This component works with the Hummingbird/Open Text edocs DM server versions and The major features of this component are: Connect to the Hummingbird/Open Text edocs DM server using the correct user name and password. Select the library that you want to send the documents into. Select the profile for the sent document. Set typist and impersonator for the sent document. Rename the sent document. Set the folder that you want to send the documents into. Specify file types to the file extensions. Set permissions to the sent document. Set values of the fields of the sent document. Send any document or image file to the specified destination in the Hummingbird/Open Text edocs DM server. Using the Component This component is mainly used to store any type of content from various sources. This component allows you to meet your regulatory and archival requirements with ease. See a sample list of use cases below. Corporate Content Repository: To protect valuable corporate information, you would want to use Hummingbird. For example if you want to store documents onto a server where other people in a group, all of which have access rights, can view the document. You can save these documents into the server, and then, give the users in a particular group access to the files. Direct device connectivity: Allow your uses to archive important documents by pressing just a few button on a scanning device. Use the Hummingbird component to directly connect various devices such as digital copiers, desktop scanners, production high-speed scanners (see OneStep with fast scanner driver support), desktop files and other types of files to back end Hummingbird/Open Text edocs DM server. Batch Import Server: Use this component along with Poll Directory to create batch import directories, where files read in from various directories can be imported directly into back-end Hummingbird/Open Text edocs DM server. Uniform Capture Process tools: Create capture business rules that dictates how your corporate content is captured into back-end document management system using our process designer tools. Connect files to back end DM: Use POP3 or SMTPCapture to connect content and archive all s within a inbox or all s sent to an SMTP gateway into your back-end Hummingbird/Open Text edocs DM server. Page 61

62 The Configuration of Hummingbird/Open Text edocs General Tab Fieldname User Name Function Enter the user name which is used to connect to the Hummingbird/Open Text edocs DM server. Note that this user must have permissions to store documents in the desired library. Each library has its own user list. You can use RRT values to create dynamic login based on the user sending documents. It is mandatory to fill out this text box. Note: When you use an RRT in the User name text box, you will be able to connect to the server only while processing, when the RRT will be replaced. Password Domain Enter the password that coincides with the user name entered. Enter the domain name. This text box should be filled out depending on the User name that you use. If you specified your library user name as your User name, leave this text box blank. If you specified a Windows Domain LAN account as your User name, enter the name of the Windows Domain. If you specified a NetWare version 3 LAN account as your User name, enter the name of the NetWare server. If you specified a NetWare version 4 LAN account as your User name, enter the name of the NetWare tree. Logon Type Library The user should select the appropriate logon type specified by the DM Server. The user can select from: Library Microsoft Network Network Bindery Network NDS Enter the library to which the user will connect to manually or click the button. This button opens the Select Library dialog that allows you to choose a library from Page 62

63 the drop-down list. Please note that the user must have proper permission levels to access this library. It is mandatory to fill out this text box. When you choose a library, two other text boxes become active. For example, if your library is of type default, then the text boxes are always disabled. However, if your library is of type legal, finance or government, then the text boxes become enabled, allowing you to set the other required features for those specific libraries. 1. For the finance library, the required fields that need to be set are Account and Department. 2. For the legal library, the required fields are Client and Matter 3. For the government library, the required fields are Organization and Department. Profile Typist Rename Pass-through Impersonate Enter the profile you want to use for storing the document manually or using the button. This button opens the Select a Profile dialog that allows you to choose a profile from the drop-down list and displays a title of the chosen profile. It is mandatory to fill out this text box. Enter the user name of the user the document s Last Edited By field will be set to. You can enter the user name manually or click the button. This button opens the Typist dialog that allows you to choose a user from the drop-down list of users in the Hummingbird/Open Text edocs DM library. Select this check box if you want to rename the document and enter a schema that will be used for renaming. If this check box is not selected, and the library does not take duplicate names, the document will fail to store if another document with the same name already exists in that library. This field is available only with the Hummingbird econnector component. If you enable this option, the Hummingbird econnector component passes the document onto the next component in the process. When you select this check box, the author of the document becomes the person entered in the Impersonate text box instead of the value specified in User name. Otherwise, the User name is the author. With impersonation selected, this individual is given security access as well. You can enter the value in the Impersonate text box manually or click the button. This button opens the Impersonate dialog that allows you to choose a user from the drop-down list of users in the Hummingbird/Open Text edocs DM library. It is mandatory to fill out this text box if the Impersonate check box is selected. Document Tab Page 63

64 Fieldname Folder Function Enter the folder that you would like to add the file to manually or using the button. This button opens the Folders dialog, that allows you to select folder from the available folders that are displayed as a tree. If you leave this field blank, the file is added to the root directory. Add Click this button to open the Add File Extension dialog that allows you to enter the extension and relate it to a document type: File extension - enter the extension (for example txt ). File type - select the file type that will be related to the specified extension (for example, MS WORD ). You can specify numerous file extensions and types. Modify Click this button to open the Modify File Extension dialog that allows you to modify file type for the selected extension: File extension - enter the extension (for example txt ). File type - select the file type that will be related to the specified extension (for example, MS WORD ). Remove Inherit from folder Full Access for Author/Typist/Impersonator Select this button to remove a file extension. If you select this check box, the document will inherit the permission of the folder where it is stored. If you select this check box, the typist, author and impersonator are granted full access rights to the document. Page 64

65 Fields tab Use this tab to set values of the fields that are created in the DM Designer by a user on the Hummingbird/Open Text edocs DM server. The tab displays all available fields for the selected profile. For each field the following parameters are displayed: N - number of the field Field - name of the field. Names of the required fields contain '*' symbol. ID - internal identifier for the field. Required - contains "Yes" if this field is required and "No" if it is not required. Value - value of the field. Only this parameter can be modified. Edit -click this button to set the value of the selected field. This button opens the Field Value dialog that allows you to choose the value from the drop-down list. Clicking this button is equivalent to double-clicking on the selected item. Note: It is mandatory to specify values of the required fields. RRTs for Hummingbird/Open Text edocs The RRT ID for this component is HUM Reserved Replacement Tag Names (RRTN) Name FileName Counter ID Library Description The original file name value. An incremental counter based on the duplicate file names found within a directory. The counter value concatenated with a name provides a unique file name. ID number of the document stored in Hummingbird/Open Text edocs DM server. This RRT is present only for the econnector component. Library to which documents are stored. This RRT is present only for the econnector component. Page 65

66 DocName Domain The document name stored in Hummingbird/Open Text edocs DM server. This RRT is present only for the econnector component. Domain used to login into Hummingbird/Open Text edocs DM server. This RRT is present only for the econnector component. Note: The ~HUM::FileName~ and ~HUM::Counter~ RRTs can be used only in the Rename field. The ~HUM::ID~, ~HUM::Library~, ~HUM::DocName~ and ~HUM::Domain~ RRTs are available only for the subsequent components in the process chain. The following example provides some sample usage for your reference: ~HUM::FileName~~HUM::Counter~ - replaced with the value Document5 if the original file name was Document and there were up to 4 (Document1 to Document4) files already within the destination folder path. Field Replacement Tag Names (FRTN) This component does not have any FRTNs. Special Set Replacement Tag Names (SSRTN) This component does not have any SSRTNs Troubleshooting Tips / Restrictions and Limitations Problem Description The Document Type combo box does not get populated. When you select a folder in the Folders dialog, click OK, and then reopen this dialog, another folder is displayed as selected. Solution Make sure you have provided the user name, password, domain and the appropriate Logon type and library. This is possible if some folder is available from a Library and from a Workspace at the same time on the server. This is the server feature and does not influence on the component work. Restrictions and limitations This component works with the Hummingbird/Open Text edocs DM server versions and You may add to one library at a time. You cannot select multiple libraries. The component sends only the documents with extensions specified in the File extensions list. Only Profiles that have the TYPIST_ID field are supported. Other profiles, such as search profiles cannot be used in storing a document. The fields that are listed are fields that are not hidden and not read-only. Therefore, if a field is specified to be hidden or read-only, then it is not shown as a field property. Certain fields are excluded from the listing of fields. This is because they are used on the dialogs themselves. An example includes DOCNAME, which refers to the documents name. If this field actually exists on the profile form, its value is either the original name of the document or the value of the Rename Schema. Other fields excluded are AUTHOR, AUTHOR_ID, SECURITY, TYPIST, APP_ID, TYPIST_ID, and APPLICATION. Page 66

67 IBM Content Manager Product Overview and Feature Highlights The IBM Content Manager 8.3 Component provides scalable content capture server software technology to help you capture your corporate business content into IBM Content Manager Family of products. IBM Content Manager improves your organization's efficiency through enhanced collaboration and information management. IBM Content Manager 8.3 Route Component delivers scalability, flexibility and low cost of ownership required to support enterprisewide document, content, and records capture, while serving as a foundation for corporate content capture. The IBM Content Manager 8.3 Route Component offers server based content routing into IBM Content Manager application. This integration allows for: Routing documents into IBM Content Manager 8.3, defined as a certain ItemType. Initiating document routing processes that direct documents and folders from one user to another during the life cycle of a document. Assignment of certain attributes belonging to an ItemType, predefined in IBM Content Manager 8.3 servers. Using this Component You can use IBM Content Manager 8.3 to: Write documents, itemtype and attributes into the back end databases. Use Run Time Replacement Tags (RRT) to dynamically link multiple components together and allows close integration of extracted content into your IBM Content Manager 8.3 system. The Configuration of IBM Content Manager General tab Set the Server attributes in this tab. Field Name Database User name Password Description Type the Database Name where IBM Content Manager 8.3 has been installed. You can also enter the IP address for the IBM Content Manager 8.3 Database. Type the name of the user that has sufficient access to this server for completing the task at hand. Type the password for the user. Document tab Field Name File Type Description Select the File Type from the IBM Content Manager 8.3 Server that you wish to associate with this document. The file types include several variants of audio, image, and video. In order to browse, click on the button. Start Documents On Process Specify if a document routing process will be attached to this document. Owner Specify the owner of this process. Priority Specify the priority of the document routing process. The priority of a document moves it up or down in the processing order in a system-assigned Page 67

68 worklist. Documents with higher priority values are processed before those with lower values. Item Type Select the Item Type from the IBM Content Manager 8.3 Server. In order to browse, click on the button. Attribute Values tab Enter Attribute value entries in this tab. Supported Common Base Attribute Type in this version: DK_CM_CHAR DK_CM_DATE DK_CM_DECIMAL DK_CM_DOUBLE DK_CM_INTEGER DK_CM_SHORT DK_CM_TIME DK_CM_TIMESTAMP DK_CM_VARCHAR Not supported Base Common Attribute Type: DK_CM_BLOB DK_CM_CLOB The following attributes type will be converted into the formats below: DATE: YYYY-MM-DD DECIMAL: (-)XXX.XX (X stands for a digit) TIME: HH.MM.SS TIMESTAMP: YYYY-MM-DD-HH.MM.SS.NNNNNN (Year-Month-Day-Hour.Minute.Second.Microseconds). By Default, the values for the DATE, TIME and TIMESTAMP will take in the current time. Field Name Add Description You can add attribute name entries and attribute values to a document. Click on the Add button and the Attribute Values dialog box appears. Attributes that are marked with an "*" are required for importing the document. Select the attribute and set the corresponding value for the attribute. Note: Some attributes might have a child component, which is an optional second or lower level of an item type. Each child component is directly associated with the level above it. In addition, some child components may have a minimum and maximum number of entries for each item. Please refer to your Administrator. To obtain the table fields, click on the button. Modify Remove Click on Modify to change the attribute value. Click on Remove to remove the attribute entry. RRTs for IBM Content Manager Component RRT ID The RRT ID for this component is IBM Page 68

69 Reserved Replacement Tag Names (RRTN) This component does not have support RRTN. Field Replacement Tag Names (FRTN) This component does not have support FRTN. Special Set Replacement Tag Names (SSRTN) This component supports the Date/Time tag names listed below: SSRTN Description %a Abbreviated weekday name %A Full weekday name %b Abbreviated month name %B Full month name %d Day of month as decimal number (01 31) %H Hour in 24-hour format (00 23) %I Hour in 12-hour format (01 12) %j Day of year as decimal number ( ) %m Month as decimal number (01 12) %M Minute as decimal number (00 59) %p Current locale s A.M./P.M. indicator for -hour clock %S Second as decimal number (00 59) %U Week of year as decimal number, with Sunday as first day of week (00 53) %w Weekday as decimal number (0 6; Sunday is 0) %W Week of year as decimal number, with Monday as first day of week (00 53) %y Year without century, as decimal number (00 99) %Y Year with century, as decimal number Examples usage of the above SSRTN include: ~IBM::%Y~-~IBM::%m~ will be replaced by Troubleshooting Tips / Restrictions and Limitations Problem Description Logon Failure Exception: DKUsageError Solution Make sure the correct IBM Content Manager Database name has been provided. Also, make sure you have a connection to that server on your connection document and the correct Username and Password has been provided. This means unallowed value appears in some field. It could happen if a mandatory field is empty, like "Username"; or an attribute value is not allowed. For example, value out of range, or wrong format. Warning: Attribute does not belong to the Item Type and is ignored. Warning: Current System does not support this attribute type, and is ignored... The Attribute provided does not belong in the list of attributes for this Item Type. Make sure the Name of the Attribute is passed in and not the Display Name. Refer to the IBM Content Manager System Administration Client for the appropriate Attribute names. Current System supports only some Attribute Types. Please refer to Attribute Values Tab for information about what are supported, and what are not. Page 69

70 Restrictions and limitations The following restrictions apply to installation of this component: You must have IBM DB2 Runtime Client and the IBM DB2 Content Manager Client for Windows 8.3 installed on the same server. You must have the installation path of the client on the PATH variable. (for example: C:\Program Files\IBM\db2cmv8\Client ) Page 70

71 imanage Product Overview and Feature Highlights imanage DeskSite is an Enterprise Document Management System that can manage repositories of millions of documents for thousands of users and provides searching, document check in/out, versioning, document profiling, complex security features and more. For complete information on all the features, please refer to the imanage DeskSite documentation or The imanage component allows organizations to further take advantage of their imanage Systems, by sending documents directly from different sources such as Digital Senders, Multi-functional devices, Scanners or a POP3 account into imanage, offering enough flexibility to layout this process in a manner that adjusts to the business rules of the organization. The imanage component allows you to store a document and all the profile information associated with it, such as Name, Description, Default Security, Type, Class, Author, Operator and custom profile fields that are particular to the imanage implementation such as Client and Matter. This component will also allow you to specify Users and Groups that will have access to the document, as well as level of access they will have. Use this component to import any kind of document into imanage, as long as you set up valid Type and Class associations for all the documents Using the Component Use the imanage component to extend the capabilities of an imanage system and provide users with alternate means to store documents. This component, when used in combination with other Capture (source) and Process (filter) components will allow an organization to implement very complex workflows, either involving interactive participation of the users or unattended environment. Use this component to categorize documents using index data that was obtained from barcode coversheets, or indexing stations using OneStep, or from Multi-functional devices that support indexing. Use POP3 Capture component with imanage Route component in a workflow scenario where users documents to a general-purpose Public folder in imanage. Assume the business process is that we are only interested in knowing who sent the document along with a brief description of the document. The following provides a step-by-step description of what need to take place: A user writes an using his/her imanage User Name in the subject field, and a brief description of the document in the body. The user will then attach the document he/she wants to send to imanage. After the is prepared the user will send the to an address defined through the POP3 component. POP3 captures the and proceeds to detach the document and create Runtime Replacement tags based on the headers that can be used by imanage. The system will proceed to route the document to imanage component. The administrator has configured imanage with fixed values for each one of the required parameters, except for the Author field and Document Description. Instead of using a fixed values, RRT from the POP3 component, ~POP::To~ (Which represents the To field of the received) has been assigned to the Author and ~POP::Body~ (which represents the message body of the ) has been assigned to the Description. Page 71

72 The Configuration of imanage This tab allows you to configure the parameters for connecting the imanage library to where the documents will be stored. General tab Fieldname Server Database User Name Operator Author Function Enter the imanage DeskSite Server Name or host IP address. Enter the imanage Database Name. Enter the imanage User Name. The User Name must have proper permissions to be able to create documents and publish them in the specified Database/Server. Enter the operator of the document, this user has read/write access, and can set the document's access rights. Enter the author of the document. This user has maximum security rights, and is the Novell owner of the document. Page 72

73 Document tab In this Tab you can configure the generic profile information for the documents that will be stored in imanage. Fieldname Name Description Default Security File Function Enter the short name for the document. The short name can be up to 16 characters long. Enter a text description of the document. This field can be up to 254 characters long. This is the general security settings for this folder. There are 3 possible default security settings: When the default security setting is set to PUBLIC, all users with access to the library will be able to view and edit the document and its profile information EXCEPT those users and groups of users to whom you specifically deny access in the Security configuration tab. When the default security setting is set to PRIVATE, no users have access to the document EXCEPT the Author and Operator named in the General configuration tab as well as users and groups to whom you specifically grant access in the Security configuration tab. When the default security setting is set to VIEW, all users have read only access to the document EXCEPT the Author and Operator named in the General configuration tab as well as those users and groups to whom you specifically grant full access, read-write access or no access in the Security configuration tab. In this section, enter the file attributes. The file type is normally based on the application that was used to create the file. Document class defines the default settings for the document. Click on Add to enter the extension of the file and the document type and class that will be associated with it. To Modify or Remove an extension, type, class association after it had been added, select the respective item from the list and click on Modify or Remove. For example if the process is receiving scanned images (TIFF or PDF format) from a Multi-functional device, click on Add to create two entries. One entry for documents with extension tif and another entry for documents with extension pdf. You can also accomplish this by dynamically setting these values at runtime by using scripting in AutoStore or by using a combination of the different Runtime Replacement Tags Page 73

74 provided by other components. Field value In this tab, specify Field Value name and values that identify the custom fields that you want to associate to the stored document. Fieldname Add Function Click on Add to enter the name of the custom category in the Name box and the value for it in the Value box. When entering the name of the custom field please take into account that this must be the internal name that imanage uses to refer to this field, which can be Custom1, Custom to Custom30. If you are entering values for custom fields Custom1 and Custom29, you must provide valid values that come from the Custom1 and Custom29 lookups, these fields also have a subcategory associated to them. For Custom1 the subcategory is Custom2 and for Custom29 the subcategory is Custom30. For the subcategory fields, you must provide valid values from the Custom2 and Custom30 lookups associated to the Custom2 and Custom30 fields. Keep in mind that if you are entering values for custom fields Custom2 and Custom30, you must provide valid values for fields Custom1 and Custom29 respectively. If you are entering values for custom fields Custom3 to Custom12 you must provide valid values that come from the Custom3 to Custom14 lookups. In general you must ensure that valid values are provided for all fields that are required to be filled in, based on the Class that will be associated with the document. Failure to do so will cause the document to be rejected since all the required fields were not found. As with other parameters in the configuration, you can enter a combination of fixed and Runtime Replacement Tags in the Field Values tab, or for more complex workflows scripting can be used to populate these values at runtime. Page 74

75 Modify Remove Select the field value that you would like to modify and click on Modify. Select the User/Group that you would like to remove and click on Remove. Security tab This tab allows you to specify which user groups can have access to the document you are storing. You can also identify the access level these users will have. Fieldname Add Group Function To add a Group to the list click on Add and enter the name of a valid imanage Group, and then select the desired access level from the list. As with other parameters in the configuration this value is generated dynamically for each stored document, whatever method the user decides to use (fixed values, RRTs or Scripting modification) the final value that the component will use must be valid. Add User Failure to specify valid Groups in imanage will result in failure and the document will not be processed. The four possible types of access are: Read-only access: This means that the user can view the document in readonly form, but cannot make changes and save them to the library as the same document. Read-write access: This means that the user has full view and edit privileges to the document. Users with read-write access can change profile information for the document, but they cannot change the Author or Operator, or edit access privileges. Only the Author or Operator and those to whom they grant full access can edit these fields. Full access: This means that the user has full view and edit privileges to the document, plus they can change the security settings for the document. The Author and Operator have full access, and they can grant full access to others. No Access: Means that the user cannot access the document. If a user has no access to a document, the document does not show up in any search of the library that he or she performs. If the document is in a public project, users who have no access to the document do not see the document when they click on that project icon. To add a User to the list, click on Add and enter the name of a valid imanage User, Page 75

76 and then select the desired access level from the list. As with other parameters in the configuration this value can be generated dynamically for each stored document, whatever method the user decides to use (fixed values, RRTs or Scripting modification) the final value that the component will use must be valid. Failure to specify valid Users in imanage, will result in failure and the document will not be processed. Remove The four possible types of access are: Read-only access: This means that the user can view the document in readonly form, but cannot make changes and save them to the library as the same document. Read-write access: This means that the user has full view and edit privileges to the document. Users with read-write access can change profile information for the document, but they cannot change the Author or Operator, or edit access privileges. Only the Author or Operator and those to whom they grant full access can edit these fields. Full access: This means that the user has full view and edit privileges to the document, plus they can change the security settings for the document. The Author and Operator have full access, and they can grant full access to others. No Access: Means that the user cannot access the document. If a user has no access to a document, the document does not show up in any search of the library that he or she performs. If the document is in a public project, users who have no access to the document do not see the document when they click on that project icon. Select the User/Group that you would like to remove and click on Remove. RRTs for imanage This component does not generate Runtime Replacement Tags, however all the parameters can contain RRT strings. For example, when POP3 is the capture (source) component, the "Author" parameter can be set to "~POP::To~", which represents the "To" field of the received. Set the "Description" parameter to "~POP::Body~, to represent that the message body of the has been assigned to the Description. In this example, we have a document in imanage and we know who sent it and what it the subject of the is. Troubleshooting tips / Restrictions and Limitations The imanage component does not support version handling. Any document added will be added as new documents. The user can add a new version of the document afterwards by using any other imanage interface that has versioning features. The Subclass category can not be specified through the imanage component, do not try to set it through the Field Values tab since this is not considered a custom category. Page 76

77 Interwoven Worksite MP Product Overview and Feature Highlights Interwoven WorkSite MP provides you with the ability to increase your productivity by enhancing your content management and collaboration activities. This integration with commonly used applications simplifies content management activities by providing you with easy access to the documents and other materials. Users can create a new document, open an existing document, save a document as a new version, change profile information and perform many other document management functions all without ever leaving their familiar application interface. The Interwoven WorkSite MP Route and econnector components allow organizations to further take advantage of their Interwoven WorkSite MP Systems, by sending documents directly from different sources such as Digital Senders, Multifunctional devices, Scanners or a POP3 account into Interwoven WorkSite MP, offering enough flexibility to layout this process in a manner that adjusts to the business rules of the organization. The only difference between the Interwoven WorkSite MP Route and econnector components is that the Interwoven WorkSite MP Route component solely stores the files and doesn't pass the files on, as it is the last component in the process. If activated, the Interwoven WorkSite MPeConnector passes the files to the next component in the process. Using the Component Use this component to create Projects, Document Folders and Categories instantly or at run time. The Configuration of Interwoven Worksite MP General Tab Enter the server and access attributes in this tab. Page 77

78 Field Value Activate Server Username Password Domain Application Name Library Facility Impersonate Description Check Activate to activate the econnector. To inactivate the component, leave the box unchecked. When the econnector is inactive, initial files will not be processed. Enter the name of the WorkSite MP Server you are connecting to. Enter the Username of the user that can obtain access to the WorkSite MP server. Enter the password that is associated with the user name. Enter the domain associated with the Username. Enter the name to be associated with in the Worksite MP clients when documents are imported. Enter the Library that will be used to obtain access to on the server. Enter the facility within the library that will be accessed. Select this option and provide a user for the Impersonate field to make the owner of the document this user instead of the user specified in the User field. The user provided in the Impersonate field is also the user that will be used to create the destination for the document, if the destination has not already been created. Destination Tab Enter the destination folder attributes in this tab. Field Value Destination Selection Description Documents can reside in either Collaboration spaces or Knowledge spaces. The Collaboration Space provides hierarchical structures to provide better context to the content. This is much like the actions a user would take, creating various levels of folders on his/her machine or a central file server. In addition to the hierarchical nature of Collaboration Spaces, security can be applied to this hierarchy as opposed to requiring Page 78

79 the security to be placed on each document. With the extra features of issues, milestones, calendar events, etc., the Collaboration Space is the ideal area to manage the work-in-progress stage of content. On the other hand, Knowledge Spaces provide an area to store published content that needs to be accessed by a wider audience. This information can be stored once but linked to multiple points in a hierarchical category structure. Browse for Destination You can either Browse for destination folder or Manually specify the destination folder attributes. Click on the ellipses to locate an existing destination folder using the Facility Browser. This option provides the benefit that the user can add to other user's folders (which they have access to). Also, the database allows folders with the same name to be added, therefore by using this folder browser, you can designate which folder to choose if multiple folders of the same name exist. Note: This can only be used if a valid Server, Username, Password, Domain, Library and Facility are given within the General Tab, since these are necessary to provide access to the Collaboration spaces and Knowledge spaces. Facility Browser Appended Path Note: If this folder gets deleted at a later time in the database (by administrator), this folder cannot be retrieved later and the Status Monitor will report an error. If the folder is deleted from the database, then it should be re-setup in the component configuration. This is because each folder has an id, and if a folder is deleted, the folder with the specified id cannot be retrieved later and the status monitor will report an error. Lists all of the existing Collaboration Spaces and Knowledge spaces under the Facility that was provided on the General Tab. Use this to browse and instantly create Projects and Document Folders under a Collaboration Space and Categories under a Knowledge Space. A path that is appended to the destination selected from the Facility Browser. It can be an already existing path, or one that is created at run time. Depending on what type of Destination that was selected in the Facility Browser, it will create either a series of Document Folders, or Categories. If a Collaboration Space, Document Folder or Project was specified, then the Appended path will create or search for Document Folders. If a Knowledge space or a Category was specified, then the Appended Path will be associated with Categories. Example: Path = CollaborationSpace1\ Appended Path = 1\2\3\4 Assuming that the Path "CollaborationSpace1" is a Collaboration Space, If Document Folder 1 does not exist, it will create Document Folder 1. Path Manually Specific Destination If document Folder 2 does not exist under Document Folder 1, then it will create it. This will continue until all of the document Folders have been created (if they do not already exist). The path that is selected from the Facility Browser, which can include any of the following types of destinations: Collaboration Space Knowledge Space Category (which resides under a Knowledge Space ) Document Folder (which resides under a Collaboration Space) Project (which resides under a Collaboration Space). Use this option to specify a destination manually. You can select to add to: Page 79

80 Knowledge Space Collaboration Space Document Folder ID Document ID Add to Collaboration Space Path Add to Knowledge Space Path Folder ID Document ID Use Document Versioning Category Properties This is effective if the Server, Username, Password, Domain, Library, and Facility on the General tab are NOT currently set/valid, if multiple WorkSite MP servers will be using the same configuration, or if the WorkSite MP server is not currently running. This provides you the option to add documents under an existing Collaboration Space. Specify a hierarchy of Projects and Document Folders under an already existing Collaboration Space. The path under the Collaboration Space can be an already existing path, or one that is created at run time. If this path does not exist, a series of Sub- Document Folders will be created under this Collaboration space. Note: If a Document Folder and a Project contain the same name under a Collaboration Space, the Project folder will have priority. This provides you the option to add documents under a specific Knowledge Space. Specify a hierarchy of Categories under an already existing Knowledge Space. The path under the Knowledge Space can be an already existing path, or one that is created at run time. If this path does not exist, a series of Sub-Categories will be created under this Knowledge Space. Sends documents to the folder that is specified by the Folder ID generated by WorksiteMP. Send documents to a document that already exists, specified by the Document ID generated by Worksite MP. Enables document versioning, incrementing the version number each time a document is replaced. Description: Description of the Category Type: Option of Primary or Secondary Category. Inherit Security: Check this option to inherit the security policy from the parent Category. Otherwise, provide the security policy that should be set to the Category. Note: Security cannot be inherited from a Knowledge Space. If the Server, Username, Password, Domain, Library, and Facility on the General tab are valid, and the a destination was specified through the Facility Browser under the Browse for Destination, then the list of available security policies reflect those that are currently available under the Knowledge Space. Otherwise, it shows the default list of Public, Private or View. Metadata: A list of Metadata and Values that can be associated with this Category through the Object Modeler within WorkSite MP. Inherit Metadata: Check this option to inherit the Metadata from the parent Category. Note: A list of Metadata associated with the Category will be displayed only if the Server, Username, Password, Domain, Library, and Facility on the General tab are valid. If the Metadata type is a table/trustee, and can take multiple values (if designed to do so within the Object Modeler of WorkSite MP), then multiple values within the list can be selected and delimited by a ",". However, if only a single value can be chosen from a metadata type, then only one list option can be selected. If the Metadata type is a Trustee, then all members of the Collaboration space are displayed for the user. Page 80

81 Link to Categories: Links the document to multiple existing categories. Link to Categories Document Folder Properties Displays the categories that are available under the selected parent Knowledge Space. Additional Categories: If the categories under the Knowledge space cannot be viewed, then the path of the category can be provided instead or the Category ID can be given. The list of Additional Categories are delimited by ;. Description: Description of the Document Folder Inherit Security: Check this option to inherit the security policy from the parent Document Folder. Otherwise, provide the security policy that should be set to the Document Folder. Note: Security cannot be inherited from a Collaboration Space. If the Server, Username, Password, Domain, Library, and Facility on the General tab are valid, and the a destination was specified through the Facility Browser under the Browse for Destination, then the list of available security policies reflect those that are currently available under the Collaboration Space. Otherwise, it shows the default list of Public, Private or View. Tags: A list of tags that already exist within the Collaboration Space that can be associated with this Document Folder. Use + to display the current tags that are available and - to remove them from the field. Tags are delimited by ;. Metadata: A list of Metadata and Values that can be associated with a Document Folder through the Object Modeler within WorkSite MP. Inherit Metadata: Check this option to inherit the Metadata from the parent Document Folder. Note: A list of Metadata associated with the Document Folder will be displayed only if the Server, Username, Password, Domain, Library, and Facility on the General tab are valid. If the Metadata type is a table/trustee, and can take multiple values (if designed to do so within the Object Modeler of WorkSite MP), then multiple values within the list can be selected and delimited by a ",". However, if only a single value can be chosen from a metadata type, then only one list option can be selected. If the Metadata type is a Trustee, then all members of the Collaboration space are displayed for the user. Project Properties Name: Name of project to be created under the Collaboration Space. Description: Description of project to be created under the Collaboration Space. Security: An existing Security Policy under the Collaboration Space that can be applied to the project. Tags: A set of tags that already exist within the Collaboration Space that can be associated with this Project. Use "+" to display the current tags that are available. Tags are delimited by ;. Metadata: A list of Metadata and Values that can be associated with this Project through the Object Modeler within WorkSite MP. Note: A list of Metadata associated with the Project Folder will be displayed only if the Server, Username, Password, Domain, Library, and Facility on the General tab are valid. If the Metadata type is a table/trustee, and can take multiple values (if designed to do so within the Object Modeler of WorkSite MP), then multiple values within the list can be Page 81

82 Metadata selected and delimited by a ",". However, if only a single value can be chosen from a metadata type, then only one list option can be selected. If the Metadata type is a Trustee, then all members of the Collaboration space are displayed for the user. Field: The name of the Metadata field Column Name: Within the Library Manager, a Metadata table can have many columns (which were specified within the Object Modeler). However, there is no primary column name for each Metadata field within a Metadata table. Therefore, if the Metadata field chosen is of type Metadata Table, and the ellipses button is accessible and a valid Server, Username, Password, Domain, Library, and Facility on the General tab have been provided, then when selecting the Value for this type, it will return a field ID to indicate which field was selected. However, if access to this ellipses is not given and the Metadata field is of type Metadata table, then the column name of the Metadata should be provided and the Value should be the Value desired under this column. Value: The value associated with the Metadata field. For Example: Consider a table named: State that has 3 Columns: Name, Description, Size. Within the Library Manager, 2 fields were provided for this table. First field has: Name - MD, Description - East Coast, Size - 28,000 Second field has: Name - VA, Description - East Coast, Size - 24,000 If the first field is desired to be chosen under table State and access to the ellipses is given and a list of Values are provided then, the ID for this field under this table is given as the Value. However, If access is not given, then a column Name should be given that distinguishes the fields, as well as the value under that column. If the first field is desired to be chosen, then the Column Name should be Name and the Value should be MD. If the Column Name is given as Description and the Value is given as East Coast, then the it randomly picks one of the first two fields within this table. Therefore, use caution when selecting a column name. Page 82

83 Document Tab Enter the document attributes in this tab. Field Value Pass Through Documents Rename Document Description Format Version Comments Security Description Check this option to pass the documents to the subsequent components in your process. This option is only available with the econnector component. Check this box if you want to rename the document. The description to be set for this document. The format to set this document once stored. This format list comes from the Application Formats list under the Library Manager. To view this list, click on the ellipses. NOTE: The list of available formats will be displayed only if the Server, Username, Password, Domain, Library, and Facility on the General tab are valid. Version Comments to be given to the document. Security policy to be given to the document. Click the ellipses to view the list of security policies available. The security policies listed are those specific to either the Collaboration Space or Knowledge Space chosen. Otherwise a default list of Public, Private and View are provided. Inherit Security Check this option to inherit the security policy from the Document Folder or Category that the Document will be stored in. Page 83

84 NOTE: A list of available security policies will be displayed only if the Server, Username, Password, Domain, Library, and Facility on the General tab are valid, and Browse for destination was selected. Metadata A list of Metadata and Values that can be associated with a Document through the Object Modeler within WorkSite MP. Field: The name of the Metadata field Column Name: Within the Library Manager, a Metadata table can have many columns (which were specified within the Object Modeler). However, there is no primary column name for each Metadata field within a Metadata table. Therefore, if the Metadata field chosen is of type Metadata Table, and the ellipses button is accessible and a valid Server, Username, Password, Domain, Library, and Facility on the General tab have been provided, then when selecting the Value for this type, it will return a field ID to indicate which field was selected. However, if access to this ellipses is not given and the Metadata field is of type Metadata table, then the column name of the Metadata should be provided and the Value should be the Value desired under this column. Value: The value associated with the Metadata field. For Example: Consider a table named: State that has 3 Columns: Name, Description, Size. Within the Library Manager, 2 fields were provided for this table. First field has: Name - MD, Description - East Coast, Size - 28,000 Second field has: Name - VA, Description - East Coast, Size - 24,000 If the first field is desired to be chosen under table State and access to the ellipses is given and a list of Values are provided then, the ID for this field under this table is given as the Value. However, If access is not given, then a column Name should be given that distinguishes the fields, as well as the value under that column. If the first field is desired to be chosen, then the Column Name should be Name and the Value should be MD. If the Column Name is given as Description and the Value is given as East Coast, then it randomly picks one of the first two fields within this table. Therefore, use caution when selecting a column name. Tags NOTE: A list of Metadata associated with the Document will be displayed only if the Server, Username, Password, Domain, Library, and Facility on the General tab are valid. If the Metadata type is a table/trustee, and can take multiple values (if designed to do so within the Object Modeler of WorkSite MP), then multiple values within the list can be selected and delimited by a ",". However, if only a single value can be chosen from a metadata type, then only one list option can be selected. If the Metadata type is a Trustee, then all members of the Destination are displayed for the user. A set of tags that already exist within the Collaboration Space or Knowledge space that can be associated with this Document Folder. Use "+" to display the current tags that are available. NOTE: A list of available Tags will only be displayed if the Server, Username, Password, Domain, Library, and Facility on the General tab are valid and Browse for Destination was selected to specify the destination. Tags are delimited by ;. RRTs for Interwoven Worksite MP Component RRT ID The RRT ID for both the Interwoven WorkSite MP econnector and Route components is WMP. Page 84

85 Reserved Replacement Tag Names (RRTN) The following table describes the reserved RTN values for this component: Name FileName Counter Name FileExt FileDesc FileNumber FileId ContainerId FileSize FileVersion FileComment OwnerName OwnerFullName OwnerDomain Owner OwnerAddress1 OwnerAddress2 OwnerState OwnerCity OwnerPostalCode OwnerPhone Library Facility Date Day Month Year Hour Minute Second Description Original Document Name An incremental counter based on the duplicate file names found within a directory. The counter value concatenated with a name provides a unique file name. Document Name Document Extension Document Description Document Number stored The unique Id associated with the document that is imported into the Interwoven Worksite MP database. The unique Id associated with the Document Folder or Category in Interwoven Worksite MP that the document is imported into. Size of the Document Document Version Comments associated with the Document User Name of the Document Owner Full Name of the Document Owner Domain of the Document Owner address of the Document Owner Home address1 of the Document Owner Home address2 of the Document Owner Home state of the Document Owner Home city of the Document Owner Home Postal Code of the Document Owner Home Phone Number of the Document Owner Library that the Document was stored in Facility that the Document was stored in Date document was created Day document was created Day document was created Year document was created Hour document was created Minute document was created Second document was created The following example provides some sample usage for your reference: ~WMP::FileName~~WMP::Counter~ - replaced with the value Accounting 5 if the original file name was Accounting and there were up to 4 (Document1 to Document4) files already in the destination folder path. NOTE: The Reserved RTN values FileName, and Counter can only be used with the Rename field of this component. In other words, you may not use ~WMP::FileName~, ~WMP::Counter~, in any other component but Interwoven WorkSite MP and it must be used with the Rename field of this component only. Field Replacement Tag Names (FRTN) This component does support FRTNs for metadata field names. The following example provides some sample usage for your reference: Page 85

86 ~WMP::%Industry%~ is replaced by Computer if the user types in Computer for the field name called Industry. Special Set Replacement Tag Names (SSRTN) This component supports the Date/Time tag names listed below: SSRTN Description %a Abbreviated weekday name %A Full weekday name %b Abbreviated month name %B Full month name %d Day of month as decimal number (01 31) %H Hour in 24-hour format (00 23) %j Day of year as decimal number ( ) %m Month as decimal number (01 12) %M Minute as decimal number (00 59) %p Current locale s A.M./P.M. indicator for -hour clock %S Second as decimal number (00 59) %U Week of year as decimal number, with Sunday as first day of week (00 53) %w Weekday as decimal number (0 6; Sunday is 0) %W Week of year as decimal number, with Monday as first day of week (00 53) %y Year without century, as decimal number (00 99) %Y Year with century, as decimal number Examples usage of the above SSRTN include: ~STF::%Y~-~STF::%m~ will be replaced by Troubleshooting Tips / Restrictions and Limitations This component currently only supports Interwoven WorkSite MP 4.1 SP1. Page 86

87 Interwoven WorkSite TM NT 8.0 Product Overview and Feature Highlights Interwoven WorkSite is a Document Management System that offers out-of-the-box, tight integration with popular Windows applications such as Microsoft Office, WordPerfect, Microsoft Outlook, Lotus Notes and Novell GroupWise. Users can create a new document, open an existing document, save a document as a new version, change profile information and perform many other document management functions all without ever leaving their familiar application interface. The Interwoven WorkSite Route and econnector components allow organizations to further take advantage of their Interwoven WorkSite Systems, by sending documents directly from different sources such as Digital Senders, Multifunctional devices, Scanners or a POP3 account into Interwoven WorkSite, offering enough flexibility to layout this process in a manner that adjusts to the business rules of the organization. The only difference between the Interwoven WorkSite Route and econnector components is that the Interwoven WorkSite Route component solely stores the files and doesn't pass the files on, as it is the last component in the process. The Interwoven WorkSite econnector passes the files to the next component in the process. WorkSite NT client must be installed on the same machine as the server. The main component features are: The Interwoven WorkSite component allows you to store a document and all the profile information associated with it, such as Name, Description, Comments, Security, Type, Class, Author, Operator and custom profile fields that are particular to the Interwoven implementation such as Client and Matter. This component will also allow you to specify Users and Groups that will have access to the document, as well as level of access they will have. Use this component to import any kind of document into Interwoven WorkSite, as long as you set up valid Type and Class associations for all the documents. Using this Component Use the Interwoven WorkSite NT component to extend the capabilities of an Interwoven WorkSite NT system and provide users with alternate means to store documents. This component, when used in combination with other Capture and Process components will allow an organization to implement very complex work flows, either involving interactive participation of the users or unattended environment. Use SMTP Capture component with Interwoven WorkSite NT Route component in a workflow scenario where users documents to a general-purpose Public folder in Interwoven WorkSite. Assume the business process is that we are only interested in knowing who sent the document along with a brief description of the document. The following provides a step-by-step description of what need to take place: 1) An , with a document attached and a Subject of "Transactions" and a Body of "Transactions from the past month", is captured through the SMTP Gateway that was configured in the SMTP Capture component. 2) SMTP Capture captures the and proceeds to detach the document and create Runtime Replacement tags based on the headers that can be used by Interwoven WorkSite. 3) The system will proceed to route the document to Interwoven WorkSite NT component. The administrator has configured Interwoven WorkSite NT with fixed values for each one of the required parameters, except for the Author field, Document Description and Document Comments. Instead of using fixed values, RRTs from the SMTP Capture component will be used. Specifically, ~SMP::From~ (representing the From field of the received) will be assigned to the Author, ~SMP::Body~ (representing the message body of the ) will be assigned to the Comments and ~SMP::Subject~ (representing the subject of the ) will be assigned to the Description of the document. Page 87

88 The Configuration of Interwoven Worksite TM NT 8.0 General tab Enter the server and access attributes in this tab. Field Value Activate (only for econnector component) Server Username Password Database Operator Author Description Check Activate to activate the econnector. To inactivate the component, leave the box unchecked. When the econnector is inactive, initial files will not be processed. Enter the name of the WorkSite Server you are connecting to. Enter the user name used for logging on to the WorkSite Server. Enter the password that is associated with the user name. Enter the name of an existing database on the server. You can browse for a database if a valid Server, User name and Password are provided in the configuration. Enter the name of an existing user which will be marked as the Operator on all documents that will be stored. An operator can be looked up if a valid Server, User name, Password, and Database is already entered in the General Tab configuration window. Enter the name of an existing user which will be marked as the Author on all documents that will be stored. An Author can be looked up if a valid Server, User name, Password, and Database is already provided in the configuration. Page 88

89 Destination Tab Enter the destination folder attributes in this tab. Field Value Destination Selection Description You can either browse for the destination folder or manually specify the destination folder attributes: Browse for Destination: Click on the ellipses to locate an existing destination folder. This option provides the benefit that the user can add to other user's folders (which they have access to). Also, the database allows folders with the same name to be added, therefore by using this folder browser, you can designate which folder to choose if multiple folders of the same name exist. The user can only browse for the folders if a valid Server, User Name and Password were provided on the General Tab. If this folder gets deleted at a later time in the database (by administrator), this folder cannot be retrieved later and the Status Monitor will report an error. If the folder is deleted from the database, then it should be re-setup in the component configuration. This is because each folder has an id, and if a folder is deleted, the folder with the specified id cannot be retrieved later and the status monitor will report an error. o o Root Path: Enter the Root Path for the folder Appended Path: Once you select a root path from the browse button, you can add an appended folder path to the original folder path. This way, you can create folders or designate folders at run time. Manually Specify Destination: o MyWorkspaces: This provides you the option to add documents under MyWorskpaces. Page 89

90 o MyFolders: This provides you the option to add documents under MyFolders. Path: The folder path you can provide under MyWorkspaces or MyFolders. If MyWorkspaces was selected, then the first folder in the path should be a workspace. If this workspace does not exist, then the workspace will be created. Since documents can only be stored in document folders, you must provide a folder under this workspace as well. Otherwise, the documents will be stored in the document worklist. For example, if you select the MyWorkspace option, and provide a path of "Customers/Pending/", the server will first search for a workspace called "Customers" and create the workspace (if the workspace doesn't exist). Then, a document folder called "Pending" is created (if it does not exist). However, a path such as "Customers/" can not be solely given under MyWorkspaces because a document cannot be stored under a workspace. If you select the MyFolders option, then any folder that does not currently exist will be created. o o Document Folder ID: Sends documents to the folder that is specified by the Folder ID generated by Interwoven Worksite NT. Appended Path: Creates or designates a path of folders under the folder specified by the Document Folder ID. Document Number: Replaces a document that currently exists within the database. Use Document Versioning: Enables or disables versioning on the documents when they are replaced. NOTE: If the Browse for Destination or Manually Specify Destination option is selected, and no folder path is entered, then all documents will be stored in the document worklist. If at anytime, multiple folders with the same name exist at the same folder hierarchy level (except for when a Root Path is specified under the Browse for Destination option), then the document will be stored under a new folder with the same name as that folder with _AMBIGUOUS appended to the name. Set Folder Properties For example, consider if the Root Path under Browse for Destination is Transactions\ and the Appended path is: Customers. Since Transactions was specified using the Folder browser, it is ok if multiple folders with Transactions are available. However, if multiple folders under Transactions have the name Customers, then a folder is created with the name Customers_AMBIGUOUS and all documents are placed into this folder. This same procedure is followed under Manually Specify Folder for the Path. Set folder properties for folder path you have configured, as well as folders that have not been created yet. Folder Properties are only set to those folders that have not been created yet. Set Folder properties for folders that will be created at run-time. Folder Description: Enter a description for the folder if the folder does not yet exist. Inherit Folder's Profile Information Fields from Parent Folder: If a folder is a subfolder of another folder, then checking this box will copy the parent folder's fields onto this new folder. This will only happen if a parent folder exists. Profile Information Fields for Folders: Select the profile fields you wish to set for the folder. The Name is the Property field name and the value is the value associated with the Name. For some Names, a list of values are given in the database. Therefore, the value is limited to those options in the database. If you provide a name, and then hit the value button on the value field, then those options become available for you to choose from. In this case, if a value not associated with the name is given, then an error will be provided once an Page 90

91 attempt is made to create the folder. If a Name property does not associate with a lookup list, then any value can be provided. NOTE:The fields custom21-custom24 can only accept a date value, as these fields have been specifically designated as date fields within Interwoven.The fields custom25- custom28 can only accept a Boolean (True or False) value, as these fields have been specifically designated as Boolean fields within Interwoven. The lookup option for the name will only be available if the Server, User name, Password and Database were entered on the General tab. The lookup option for the value will only be available if the Server, User name, Password and Database were provided on the General tab and a valid Property Field Name is provided on this dialog. NOTE: If the inherit option is selected and fields are provided in the profile information field list, then the folder will first inherit the parent folder's fields and then set the fields given in the list. Therefore, any fields in the profile information field list will overwrite the folder's fields if they were inherited. Document tab Enter the document attributes in this tab. Field Value Pass Through Documents Rename Documents Description Check this option to pass the documents to the subsequent components in your process. This option is only available with the econnector component. Check this option to rename the document. Page 91

92 Description Comments Shared As Document Security Enter a description to be assigned to the documents. Enter comments to be given to the documents. Sets the level for sharing the document as Private, Public or View.. Delimit Name by: Specify a character/sting delimiter to split on list of multiple names. For example: "User1, User2, User3" is given and the delimiter is "," and the access right is Full Access. This gives Full Access to User1, to User2 and to User3 without having to type in each user one at a time. Add Group: Click on the ellipses to locate the desired group name(s) and specify the document access level you want to grant to the group. Set Document Properties Add User: Click on the ellipses to locate the desired user name(s) and specify the document access level you want to grant to the user. Type: Click on the ellipses to locate the desired extension type for the file. You can look up the available application extensions by providing the Server name, User name, Password, and the name of the Database on the General tab. o o The type must be a valid extension that is set up under "Type" in the WorkSite database manager/dbadmin. Class: Click on the ellipses to locate the desired class type for the file. You can look up the available class types by providing the Server name, User name, Password, and the name of the database on the General tab. Classes are custom-defined categories for identifying and differentiating documents in the database. This must be a valid/existing Class that was created in the WorkSite database manager/dbadmin. Inherit document's profile information fields from folder: Check this option to allow the document to inherit the folder's field values (if the folder exists). Profile Information Fields for Document: Setup and modify Field information and Subclass information fields for the document. If you have entered a valid Class, Server name, User name, Password, and Database, then you can look up the Fields that have been set up in the WorkSite database manager/dbadmin. You can add a Subclass to your document, however only one subclass can be permitted for each document. If you provide a subclass, then only that subclass' profile information fields on the subclass dialog will be assigned to the document (Not all of the fields listed in the profile information fields on the add file dialog, therefore all other fields that are provided in the profile information fields list on the add file dialog are ignored). A subclass may or may not be required depending on the Class that you entered. This should be checked for in the WorkSite database manager/dbadmin. When adding fields, an exclamation mark next to the field indicates that the field is mandatory. If a document requires a field and the field is not entered, then the document will not be stored. RRTs for Interwoven Worksite TM NT 8.0 Component RRT ID The RRT ID for this component is IM8. Page 92

93 Reserved Replacement Tag Names (RRTN) The following table describes the reserved RTN values for this component. Name FileName FileComment FileDesc FileExt Counter Name FileId FileSize FileVersion FolderId Day Hour Min Month Year DayOfWeek DayOfYear OpName OpDomain OpPhone OpExt OpFax OpLocation Op AuthorName AuthorDomain AuthorPhone AuthorExt AuthorFax AuthorLocation Author Description Original Document Name. The Comment of the Document that will be stored. The Description of the Document that will be stored. The Extension of the Document that will be stored. An incremental counter based on the duplicate file names found within a folder. The counter value concatenated with a name provides a unique file name. The File Name of the Document that will be stored. The ID/Number of the Document that will be stored. The Size of the Document that will be stored. The Document Version. The unique Interwoven WorkSite ID of the Destination Folder. The Creation day of the Document within IManage. The Creation hour of the Document within IManage. The Creation minute of the Document within IManage The Creation month of the Document within IManage The Creation year of the Document within IManage The day of week the document is created within IManage. The day of week the document is created within IManage. The name of the Operator of the document. The domain of the Operator of the document. The phone number of the Operator of the document. The phone extension of the Operator of the document. The phone Fax number of the Operator of the document. The location of the Operator of the document. The address of the Operator of the document. The name of the Author. The domain of the Author. The phone number of the Operator of the document. The phone extension of the Author of the document. The Fax number of the Author of the document. The location of the Author of the document. The address of the Author of the document. The following example provides some sample usage for your reference: ~IM8::FileName~ - replaced with the value Accounting if the original file name was Accounting. Field Replacement Tag Names (FRTN) This component does support FRTNs for field names. The following example provides some sample usage for your reference: ~IM8::%Client%~ is replaced by Government if the user types in Government for the field name called Client. Special Set Replacement Tag Names (SSRTN) This component does not have any SSRTNs. Page 93

94 Troubleshooting Tips / Restrictions and Limitations Problem Description Interwoven WorkSite Error (Document profile is invalid. The field is invalid: ). Solution Check that an invalid field value was not given for the associated Field Name. Several of the fields are custom-defined categories that have a table associated with a field of document profile information. Document profile information fields are configured as lookup fields, which means that the only information users can enter in these fields comes from their associated tables. In addition, The Client/Matter and Practice/Subpractice tables are special custom tables that allow further creation of custom categories by which users can identify and differentiate documents in the databases. The Client/Matter and Practice/Subpractice tables are distinct from the other custom tables in one important way: each item listed in the Client and Practice tables is the parent of a unique set of Matter or Subpractice table entries. When a user makes a selection in the Client or Practice fields, the user should select only the choices available for the Matter and Subpractice fields that are associated with the Client or Practice that the user has selected. Refer to the setup of these tables within the WorkSite database manager/dbadmin. Page 94

95 IXOS Product Overview and Feature Highlights IXOS provides a complete integration into IXOS application. This component is responsible for creating all necessary interface files to properly store documents as well as index data into IXOS. The interface also provides the flexibility to create custom commands as well as dynamic command entries through use of RRT variables. The IXOS also provides for full support of IXOS SAP interface that allows you to create command files with attributes and variables necessary to write your files into IXOS with proper links into your SAP system back end. This component support IXOS econserver Batch Import server interface V5.0. Using the Component: This interface is used to archive any desired documents, including document attributes, transparently in IXOS- ARCHIVE. The documents are created within the import directories and are then entered in the archive system by the archive server. The documents, including the attributes, must be transferred according a defined form. AutoStore IXOS components allows creation and transfer of documents according to defined directory on the Archive server referred to as EXT_DIR. The sub-structure of this directory is predefined and is described in the Batch Import guide from IXOS. Within the IXOS, the path for EXT_DIR is specified when it is installed. You must point to the same EXT_DIR when you are using AutoStore IXOS Component. You must, of course, also ensure that sufficient space is made available in EXT_DIR in order to transfer external documents. The IXOS interface allows you to create standard batch import files within the EXT_DIR subdirectory structure. The EXT_DIR subdirectory is depicted in illustration below. The Component user provides the EXT_DIR root directory on the EXT_DIR Tab of the IXOS component. The component is responsible for creating the appropriate subdirectories. For details on the EXT_DIR sub-directory structure see Batch Import with Attributes guide from IXOS. The IXOS component creates necessary directory and files under EXT_DIR which includes creation of: IXATTR file All attributes headers and corresponding fields. COMMAND file All commands related to the image files and attributes. LOG file Empty log file created to allow logging by IXOS Batch Import process. Image file(s) Captured image file in TIFF or PDF format. This interface also supports SAP R3 attributes and commands as well as Flexible Header structures for free format creation of IXATTR or COMMAND interface file entries. For details on all attributes and command variables see Batch Import with Attributes guide from IXOS. Note: You can use RRTs for creating your file entry variables. Example of use of RRTs are use of ~L1B::BARCODE~ within the value field of the IXATTR entry. This type of RRT usage allows all IXATTR and COMMAND attributes to be dynamically driven from the meta data values. Page 95

96 The Configuration of IXOS IXAT TR File Builder This tab is designed to help you create the Attribute File for each job. The entries within this tab are created within the Attribute file every time new documents are placed into the IXOS directories. You can select the header and attributes from the predefined list of fields or create attribute entries using the Flexible Formatting interface. The predefined headers and attributes provide the standard set as well as SAP R3 entries to allow development of SAP integration for IXOS. The Flexible Formatting allows custom attribute lines to be entered and helps in further customization of the IXOS interface. You can use all RRTs to create dynamic attribute entries. Examples of dynamic attributes using RRT are listed below: If you enter the following as Flexible Formatting entry R3_CLIENT ~L1D::1,1~ Where ~L1D::1,1~ represents the first barcode on the first page of the document. Assuming the barcode value was XXX then the entry in the Attribute file will be: R3_CLIENT XXX Use RRTs to create entries within the batch file that link your IXOS batch file entries into other document related values such as barcodes, user field entries (on devices such as Multifunction Devices), form field values, zoned OCR field value, or values available for any other component. This is a powerful feature that allows organizations to create custom solutions based on their document content capture requirements. For full description of IXOS Attribute entries see IXOS econserver Batch Import server interface V5.0 for detail description of all Attribute entries and structure. Page 96

97 Command File Builder The Command File Builder Tab allows you to create the correct entries within the command file interface. There are two methods of creating entries: Method 1: Using the predefined headers This method allows you to select the command entries from a list of defined entries. This interface makes it easy for you to select from a list of available entries and quickly complete your Command line. The header command entries allow you to select entries such as COMP with Component Type: PDF. The Command entry created as the result would be: COMP 1.pg PDF And the Command line entry would be: COMP 1.pg PDF <filename> Method 2: Using the Flexible Formatting The Flexible Formatting allows you to type in your entries and create a complete set of entries based on your custom requirements. The flexible command formatting allows you to create entries such as: COMP 1.PDF PDF Use Flexible entries to create custom commands for your IXOS application. See IXOS econserver Batch Import server interface V5.0 for detail description of all command entries and structure. Page 97

98 EXT_DIR tab This entry simply allows you to select a directory for you, where documents and attributes are transferred within a defined directory on the econserver archive server. The required sub-directories within this server are automatically created by AutoStore. You must point to the EXT_DIR as defined by the Batch Import Server interface. Use RRTs to create dynamic EXT_DIR entries such as: C:\ ~L1D::1,1~\EXT_DIR Where ~L1D::1,1~ is generated by the barcode component and represents the first barcode on the first page of the document and will be replaced with the actual value of the barcode at runtime. For example if the first barcode on the first page is XXX then the directory used to write the files will be: C:\XXX\EXT_DIR RRTs of IXOS route component This component does not generate Runtime Replacement Tags, however all the parameters can contain RRT strings. For example, when POP3 is the capture (source) component, the Documentum "User Name" parameter can be set to "~POP::To~". Troubleshooting Tips / Restrictions and Limitations There is no information available at this time. Page 98

99 Kyocera ABMSync Product Overview and Feature Highlights This component is used to import address-book entries into the Kyocera device(s). The address-book information may be imported from a variety of sources such as, another device, Lotus Notes ABMSync, Lotus Notes ABMSync Client, MS Exchange ABMSync Client, and MS Exchange ABMSync. This component support the following features: Import data in to a single or multiple Kyocera devices. Import data from: o o o o Lotus Notes ABM Sync Lotus Notes ABMSync Client MS Exchange ABMSync MS Exchange ABMSync Client Another Kyocera device Obtain an up-to-date list of Kyocera devices on the network by using Refresh button Notify the user by when the user is added to additional devices. o Configure the settings used for the notification Using the Component Please make sure the following is all valid and makes sense: Create a backup file of the address-book from a primary Kyocera device: Setup your first process to export the address-book file entries and store them as a batch file into a folder (Kyocera ABM Sync Capture > Folder Store). Load the address-book entries into other devices. Create one or many processes to poll the directory where the batch file is stored and distribute the batch file to many devices (Poll Directory >Kyocera ABM Sync Route). Use the File Option component to capture failed files back to the same Failure directory for reprocessing. Keep a copy of the batch file and retry importing the address-book entries in case of failure: Setup your first process to export address-book entries from one device, and write into many devices. Use the File Options component to safe keep the batch file in a Reject directory in case of a failure. (Kyocera ABM Sync Capture>File Options>Kyocera ABM Sync Route). Setup your second process to check and read the Reject directory from Process Use the File Options component to capture failed files to the same Failure directory for reprocessing. (Poll Directory to File Options to Kyocera ABMSync Route). Page 99

100 The Configuration of Kyocera ABMSync General Tab This tab displays a list of all devices that import data. The data is imported into these devices from either from Lotus Notes ABMSync, Lotus Notes ABMSync Client, MS Exchange ABMSync Client, MS Exchange ABMSync, or from another device. Add Click on Add and a dialog box opens, displaying a list of all devices (by Host Name and IP Address) on the network. Click Refresh to initiate a new search for the devices on the network. Select the desired device(s) that import data and click on OK. Remove Click on this button to remove a device from the list. New User tab Configure this tab to notify a user that has been added to the device user list. This tab allows you to configure the settings that is used for generating the destined to the new device user. Page 100

101 New User Notification If checked, the user is notified by to what device(s) the user was added to. An is sent to that individual with their user name, password (random or static), and the name of devices they were added to. Random Password If checked and a new user entry has been made into the User Profile table, a password is automatically generated. The user will use this password to log into the Kyocera device. Note: If User Profile entries are imported from Kyocera ABMSync Capture component, the User Profile table of the device is completely synchronized with the device from the Kyocera ABMSync capture component. However, if the User Profile entries are imported from Lotus Notes ABMSync or MS Exchange ABMSync, 2 scenarios may occur: If the entry that is being imported already exists in the User Profile table of the slave device, then the password from that table is kept. Otherwise, if you checked off a Random Password, the password for that user is set. Static Password Enter the desired password. The user will use this password to log into the Kyocera device. Settings If you select the New User Notification check box, populate the following fields: Field Name SMTP Server User name Password Description Enter the name of the SMTP server you want to send s from. Enter the user name of the person to send s from. Enter the password of the user to login into the SMTP server. Page 101

102 From Subject Body Enter a string for the from field of the . Enter the subject to be displayed for the . You ca use RRTs in this field. Enter the body of the . By default the scanner, password, and user name RRTs are placed in the body of the . RRTs for Kyocera ABMSync Component RRT ID The RRT ID for this component is KIM Reserved Replacement Tag Names (RRTN) The following table describes the reserved RTN values for the Schema field of this component. Name MFD UserName Password Description Scanner(s) on which this particular user was added to. User name used to login to the device locally. Password of the user to login to the device locally. By default the body of the includes the above three Reserved Replacement Tag Names. The following example provides some sample usage for your reference: ~KIM::MFD~- replaced with a comma-separated list of device hostnames. Field Replacement Tag Names (FRTN) This component does not have any FRTNs and replacement of field names with metadata values. Special Set Replacement Tag Names (SSRTN) This component does not support any SSRTNs. the Date/Time tag names listed below: Troubleshooting Tips / Restrictions and Limitations There is no information available at this time. Page 102

103 LAN Fax Product Overview and Feature Highlights The LAN Fax component supports faxing capabilities using a third-party LAN fax server. The LAN Fax component communicates with the network fax server via a common directory folder using HP Scanfax technology. This folder can be a network folder as long as the LAN fax component and the LAN fax server both have read and write access to it. Although not required, it is recommended that the LAN fax server be installed and the common folder established, before configuring the LAN Fax settings. This component provides: Send faxes using a LAN fax server. Capture documents from remote sites using any Scanner, any Multi-functional device or Digital Copiers and route images to any of the supported fax servers. Creates billing account numbers for fax billing records. Note that JPG and PDF formats are not supported by the LAN Fax component. Using the Component Copy-to-Fax: Connect all your network enabled Digital Copiers to your enterprise Fax Servers Scan-to-Fax: Connect your desktop scanner directly to enterprise Fax Server. -to-Fax: Capture documents using POP3 or SMTPCapture and route them to enterprise Fax Server for processing Directory-to-Fax: Poll a directory and push each file into Fax Server. If you are designing a process that would capture files from a Poll Directory component, and route to LAN Fax component, make sure to use a Data Interchange process component after the Poll directory component. XML-to-Fax: Receive AutoStore XML documents and send via fax Use VBScript: Use VBScript to lookup fax address books and integrate with your back-end fax database address books. The Configuration of LAN Fax General Tab Fieldname Fax Number Billing Account Description Function Enter the comma-separated destination fax number(s). This is an optional field that if supported by the fax server, a billing code can be entered. This code may be used for accounting purposes. This is an optional field. If the fax server supports this, you can enter a description of the Page 103

104 Scanner Name User Name fax. This is an optional field. If supported by the fax server, you can enter the scanner name where the fax is originating from. This is an optional field. Faxes sent without specifying a user name, will be faxed out from the LAN fax server's default user account. In order to send a fax through a specific user account on the LAN fax server, enter a user name that exactly matches the user LAN account on the LAN fax server. Fax Settings Tab Fieldname Error Correcting Mode Retry Interval Resolution Maximum Transmission Speed Function Check this box to enable Error Correction. Most fax machines have a feature called ECM (error correction mode). ECM enables the machines to continue transmission or reception despite minor (and usually intermittent) problems with the quality of the telephone line connection. When the quality of the telephone line connection is poor, transmission time will increase as the two machines repeat data signals in an attempt to complete the transmission. If you would like the LAN Fax product to retry a failed fax transmission (e.g. the phone line was busy), enter a value between 1 and 99. Enter 0 if you don't want the LAN Fax product to attempt re-transmission of a failed transaction. If you have enabled Retry on failed fax transmissions, choose the number of minutes the LAN Fax product should wait between retry attempts. Enter an integer between 1 and 60. Select the quality of the fax by choosing a resolution from the drop-down list. The maximum baud rate at which you want faxes to be transmitted. The LAN Fax product may also limit the transmission speed. Check your LAN fax server hardware and software specifications. Page 104

105 LAX Fax Inbox Fieldname Folder Path Overwrite Existing File Rename File Schema Function The fully qualified path of the common folder that will be used to place fax data in order to communicate with the LAN fax server. This folder can be a Network folder as long as this LAN Fax component and the LAN fax server software both have read and write access to it. If the folder is a network folder, enter the UNC (e.g. \\my_server\my_share_drive\my_share_folder). Check this box to overwrite files with the same name. Check this box to rename the output file based on the Rename Schema settings. Enter the schema name used to reformat the output file name. You can use Runtime Replacement Tags (RRT) to dynamically set the value of the schema. RRTs for LAN Fax The RRT ID for this component is LFX Reserved Replacement Tag Names (RRTN) Name FileName Counter FileExt Description The original file name value. An incremental counter based on the duplicate file names found within a directory. The counter value concatenated with a name provides a unique file name. Original file extension value The following example provides some sample usage for your reference: ~LFX::FileName~~LFX::Counter~ - replaced with the value Document5 if the original Schema name was Document and there were up to 4 (Document1 to Document4) files already within the destination folder path. Field Replacement Tag Names (FRTN) This component does not have any FRTNs and replacement of field names with metadata values. Page 105

106 Special Set Replacement Tag Names (SSRTN) SSRTN Description %a Abbreviated weekday name %A Full weekday name %b Abbreviated month name %B Full month name %d Day of month as decimal number (01 31) %H Hour in 24-hour format (00 23) %I Hour in 12-hour format (01 12) %j Day of year as decimal number ( ) %m Month as decimal number (01 12) %M Minute as decimal number (00 59) %p Current locale s A.M./P.M. indicator for -hour clock %S Second as decimal number (00 59) %U Week of year as decimal number, with Sunday as first day of week (00 53) %w Weekday as decimal number (0 6; Sunday is 0) %W Week of year as decimal number, with Monday as first day of week (00 53) %y Year without century, as decimal number (00 99) %Y Year with century, as decimal number Troubleshooting Tips / Restrictions and Limitations Problem Description A fax document could not be sent to the recipient. HPF files are not written to the destination directory Solution Verify that the number entered is a valid fax destination. Check the LAN fax server's log for details Make sure you are using UNC and not mapped drives for your folder path. Mapped drives are not supported. Also make sure the server has read and write permission to the folder. Restrictions and limitations The LAN fax server is what validates the fax numbers you are sending to. This component does not notify you if you send to an invalid fax number, however, the LAN fax server activity log does. JPG and PDF formats are not supported by LAN Fax component. LAN Fax component can be used to send faxes using one of the following supported LAN fax servers. o Any Way Office EDITION o AVT Makers of RightFAX o Biscom FAXCOM o CASTELLE FaxPress o Com-EM-Tex o David by Tobit Software o Esker Faxgate o Esker LanFax o FACSys Fax Messaging Gateway o Faxination o FAXmaker o FaxNow! o FaxPlus/OpenFAXport by 3Com o Ferrari electronic o Gold-Fax o Hexar FaxSwitch o Imecom Integral FaxMerkur (SCH Technologies) Page 106

107 o MRS Unified Messaging System o Object-Fax o Omtool o RTEFAX o Tobit FaxWare o TOPCALL o Zetafax If you are designing a process that would capture files from a Poll Directory component, and route to LAN Fax component, make sure to use a Data Interchange process component after the Poll directory component. Page 107

108 LaserFiche Product Overview and Feature Highlights Use the LaserFiche econnector and LaserFiche Route components to process and store documents into LaserFiche Document Management System. LaserFiche users can efficiently store content from a variety of sources into a database. Once the content is captured, it becomes available for retrieval and collaboration across the network within the organization. Now you can design and implement workflows that capture paper and electronic documents from variety of sources such as MFP devices, network/local folders, PC desktop, POP3 servers to manage and store your documents into LaserFiche. The only difference between LaserFiche econnector and LaserFiche route component is that the econnector component provides an Activate option as well as document Pass-through option. The Pass-through option, when selected, passes the document to the next component in the process. This component supports LaserFiche Client Version The LaserFiche econnector and route components provide the following LaserFiche features: Automate document routing into LaserFiche document management system. Add metadata to documents for indexing Dynamic folder creation and the storage of documents into various repositories. Apply tags to documents Ability to index all pages of document Rename the document Using the Component Scan documents from an FTP site directly into LaserFiche: Design a workflow process by selecting FTP site that has a series of files to be processed. You can configure the LaserFiche component to assign document fields, depending on the Document Type that was selected. The document with the set attributes is routed directly into LaserFiche repository. Capture electronic documents from a local/network folder directly into LaserFiche: Design a workflow process by selecting Poll Directory capture component. From the component tray, select the desired process components and select the LaserFiche route component for storing the scanned document into LaserFiche repository. You can configure the LaserFiche component to assign document fields, depending on the Document Type was selected. With the Server running, the walk-up MFP user enters a pre-configured function key on the control panel of the MFP device and the document along with the set attributes is routed directly into LaserFiche repository of choice. Page 108

109 The Configuration of LaserFiche General tab Enter the general attributes of the LaserFiche repository where you want the documents to be saved into. Activate Check this box to enable the LaserFiche process component. The Activate checkbox is beneficial when your process involves creation of MFP function keys. LaserFiche component can be turned ON or OFF per function key of the MFP using the Activate check box. This option is only available to the LaserFiche econnector. Server Enter the name of the server on which the Repository is located This is a required field. User Enter the name of the user connecting to the Repository. Password Enter the password of the user connecting to the Repository. Repository Enter the repository you want to connect to. This is a required field. Template Choose a template to associate with documents. This is an optional field. Templates provide the highest retrieval efficiency whey they are used to categorize different types of documents. Using a template allows to quickly eliminate a lot of possible results when performing a template search. You may then use fields to further narrow the search results. Volume Choose a volume to associate with documents. This is a required field. Pass-through If enabled, the documents are passed on to the next component in the process. This option is only available on the econnector (process) component. Page 109

110 Document tab In this tab, please enter the document attributes. Rename Select this check box to rename the document. If checked, but the schema field is left blank, a default schema of ~LFC::FileName~_~LFC::Counter~ will be used. Folder Select the folder to store documents into. If left blank, documents will be stored in the root folder of the Repository. Tags Choose tags that you would like to apply to documents. Index All Pages Select this option to index documents upon creation. Note: if a Repository has been configured to Always index on document creation, the documents will be indexed regardless. However, if this option is not configured for a Laserfiche Repository, the newly created documents can be chosen to be indexed or not. (Consult Laserfiche Administration Console help file). Page 110

111 Fields tab In this tab, set the fields that are assigned to a chosen template. Name: The name of a field to assign a value to. Type: Specifies a field's data type. This determines what type of data can be stored in a field. The available options are listed below: Char: This type of field accepts any alphanumeric ASCII character (Lists can be displayed). Long Integer: This type of field accepts integers equal to or less than 3,999,999,999. Integer: This type of field accepts integers equal to or less than 64,999. Date: This type of field accepts numeric date values. Date values will be formatted according to the short date format defined in the Regional and Language Options dialog box, which can be found in the Windows Control Panel. For example, using the English (United States) setting, December 25, 2004 would appear as 12/25/2004; however, using the English (United Kingdom) setting, it would appear as 25/12/2004. Date/Time: This type of field accepts a numeric date value followed by a numeric time value. Date values will be formatted according to the Window's short date format. Time values will be formatted according to the Window's time format. Both of these formats are defined in the Regional and Language Options dialog box, which can be found in the Windows Control Panel. For example, using the English (United States) setting, December 25, 2004 would appear as 12/25/2004; however, using the English (United Kingdom) setting, it would appear as 25/12/2004. R: Requires a user to set a value for the corresponding field when modifying a document's field data. Value: The value of a field. If a default value is available, the value is shown. RRTs for LaserFiche Component RRT ID The RRT ID for this component is LFC. Reserved Replacement Tag Names (RRTN) The following table describes the reserved RTN values for Rename Schema field of this component. Name FileName Counter ID Description The original file name value. An incremental counter based on the duplicate file names found within a directory. The counter value concatenated with a name provides a unique file name. Unique ID of document stored into LaserFiche. This is applicable to LaserFiche econnector. Page 111

112 The following example provides some sample usage for your reference: ~LFC::FileName~~LFC::Counter~ - replaced with the value Document5 if the original file name was Document and there were up to 4 (Document1 to Document4) files already within the destination folder path. Field Replacement Tag Names (FRTN) This component does not have any FRTNs and replacement of field names with metadata values. Special Set Replacement Tag Names (SSRTN) This component does not support Date/Time tag names. Troubleshooting Tips / Restrictions and Limitations If you are unable to connect to LaserFiche through Process Designer, make sure that you have a valid username/password. Also, make sure that the client is working correctly, by opening LaserFiche Client and ensuring that you can connect outside of this workflow application. Page 112

113 Lotus Notes/Domino Product Overview and Feature Highlights Notes/Domino Store is a destination component that can be used to store information of any kind, text, graphics, scanned images, even sound and digital movies in company repositories called databases within the Lotus Notes/Domino system. Each database stores two kinds of information for each document: document content -this is the file you create using applications such as word processors or spreadsheets. metadata, or properties - refers to descriptive characteristics, such as the document s type, format, title, subject, keywords, and author. This component provides: Use this component to store documents within the Notes/Domino system. Use the search field to update/add document content or metadata to an existing record in the Notes/Domino database Using the Component The MFP devices can be configured with a Notes/Domino button, where, by pressing this button, images are scanned in and then stored in a designated database in the Notes/Domino System. The Configuration of Lotus Notes/Domino General Tab Field Name Server Password Functions Optional input, if the database is remote, this is reference to a server on which the database is located, Enter the password for the current User ID that is being used by the Notes/Domino Page 113

114 Database Name Form Name Attachment Field Rename File Schema Calculate Computed Fields Ignore Validation Errors system to log in to a database. Enter the file name of an existing database. You can also choose the database dynamically by using RRTs. So you can point for example to a invoice database of a certain year upon user input. Enter the title of a form note in the selected database. Enter the field within the selected form that incoming document content/file will be stored in. Check this box if you want the output file to be renamed based on the Rename Schema settings. Enter the Schema name for the output file name. You can use Runtime Replacement Tags (RRT) to dynamically set the value of the schema. When this checkbox is selected, AutoStore will trigger a recalculation of field formulas after a record is created or updated. This allows the pre-designed field formulas to recalculate all related field forms upon creation of a record using AutoStore. This checkbox can only be selected if Calculate Computed Fields and Validation Formulas in the Form is selected. This checkbox will allow AutoStore to ignore any field validation errors that might be caused. If you do not select this checkbox, any field validation error will cause a failure in creation of a record. Field values tab Page 114

115 Field Name Add Functions Use this button to assign values to fields of the selected form. You can select the search key if you want a search of the notes database prior to creation of a new record. If the search of the database returns only one record matching the search key, the incoming document content and metadata is added to the existing record. Modify Remove Set Field Value On Search If the search returns more that one match, a new record will be created in the database. Use this button to modify field values of the selected form. Use this button to delete field values of the selected form. When search keys are used, if a matching document is found, then the any existing field in the record is replaced with the field values in the current job. RRTs for Lotus Notes/Domino The RRT ID for this component is LND Reserved Replacement Tag Names (RRTN) Name FileName Counter FileExt Description The original file name value. An incremental counter based on the duplicate file names found within a directory. The counter value concatenated with a name provides a unique file name. Original file extension value The following example provides some sample usage for your reference: ~LND::FileName~~LND::Counter~ - replaced with the value Document5 if the original file name was Document and there were up to 4 (Document1 to Document4) files. Field Replacement Tag Names (FRTN) This component does not have any FRTNs and replacement of field names with metadata values. Special Set Replacement Tag Names (SSRTN) SSRTN Description %a Abbreviated weekday name %A Full weekday name %b Abbreviated month name %B Full month name %d Day of month as decimal number (01 31) %H Hour in 24-hour format (00 23) %I Hour in 12-hour format (01 12) %j Day of year as decimal number ( ) %m Month as decimal number (01 12) %M Minute as decimal number (00 59) %p Current locale s A.M./P.M. indicator for -hour clock %S Second as decimal number (00 59) %U Week of year as decimal number, with Sunday as first day of week (00 53) %w Weekday as decimal number (0 6; Sunday is 0) %W Week of year as decimal number, with Monday as first day of week (00 53) Page 115

116 %y Year without century, as decimal number (00 99) %Y Year with century, as decimal number Troubleshooting Tips / Restrictions and Limitations Problem Description User experiences: "Unable to find path to server" or "Server is not responding". Solution There are a few different situations that might prevent this component from connecting to a particular Notes server: The server is temporarily unavailable. If you can't connect to the same server using the Notes client, but you have been able to connect to that server in the past, this is the most likely reason. The server is not reachable through any of the network ports that are enabled for the current location. If you can't connect to the same server using the Notes client, and you've never connected to that server before, this might be the problem. Contact your Notes administrator to determine which port(s) you need to use. The server is not reachable through the network port used by this component. If you can connect to the same server using the Notes client, this is the most likely reason. This happens because the Notes client will use all available network ports when trying to reach a server, while this component use only one port, typically the first one enabled for the current location. You can do the following to enable a network port: Reorder the ports so that the port you need to access the server is listed first. To do this, you can use File>Tools> User Preferences>Ports in the Notes client, or you can edit NOTES.INI and reorder the ports in the "Ports=" entry. Cannot create documents in the database. If you can't create a document, open the Lotus Notes client - choose File>Database>Access Control to see the Access Control List for the database the document is in. To create a document, you must have Depositor access or greater. In addition to having one of these access levels, you must also have the option "Create documents". selected Restrictions and limitations This component must be installed on a computer that has either the Lotus Notes client or the Lotus Notes\Domino server installed. The path to the Lotus Notes\Domino directory must be on the system path. This component uses the Notes ID specified in the Notes initialization file (notes.ini) when attempting to log on to Lotus Notes\Domino server. Page 116

117 Microsoft Exchange Product Overview and Feature Highlights Microsoft Exchange Store is a Route component that can be used to store information of any kind text, graphics, scanned images, even sound and digital movies in public folders within the Microsoft Exchange server. Documents can be routed to dynamic folders, a destination form can be selected, and index field in the form can be set. Public folders facilitate the exchange of information between groups of people within an organization. Public folders store two kinds of information for each document: document content and metadata, or properties. Document content is the file you create using applications such as word processors or spreadsheets. Properties are descriptive characteristics, such as the document s type, format, title, subject, keywords, and author. This component provides: Use this component to store documents in public folders within the Microsoft Exchange server. Use the search field to update/add document content or metadata to an existing record in a public folder. Using theccomponent The Multi-functional devices can be configured with a Microsoft Exchange button, where by pressing this button, images are scanned in and then stored in a designated public folder of a Microsoft Exchange server. The Configuration of Microsoft Exchange General Tab Field Name Server Mailbox Folder Path Form Name Subject Text Function Type in the name of the Exchange server that AutoStore will log in to and place files on. Enter an alias or account name of a user on the Microsoft Exchange server. Click on to be presented with a list of available public folders. Select the folder where you want to place your files, and click OK. Click on and the process designer will automatically display all the forms available in the specified public folder. In the Select Form Use this field to set the subject property of the newly created document. Use this filed to set the body property of the newly created document. Page 117

118 Field values tab Field Name Add Modify Remove Set Field Value on Search Function Click on Add to assign field name and value to the exchange custom forms. If you designate field to be a search key, the component will attempt to find a single record matching all fields designated with the search key enabled. If a single record is found matching all search keys, the document will be added to that record. If multiple records are found matching all search keys, a new record will be created and the document will be attached to this new document. Click on this button to Modify field value attributes. Click on this button to Remove a field value. If a record is found matching all search key(s), and the set field value is checked, the matching record field values will be updated. RRTs for Microsoft Exchange route component This component does not generate Runtime Replacement Tags, however all the parameters can contain RRT strings. Page 118

119 Troubleshooting tips / Restrictions and limitations Problem Description The form you want is not available in the public folder. You cannot create a record in the public folder Solution You may not have permission to use the form, or you may be required to use another form to add information to the public folder. See the folder owner or your administrator. Contacts for a public folder appear on the Summary tab in the Folder name Properties dialog box. (Right-click the folder, and then click Properties.) You may not have permission to create items in the folder. See the folder owner or your administrator. Some public folders require that you post information by using a particular form that you may not have set up. For information about forms, see your administrator. The item type needs to match the folder type. For example, you can't add a task item in a mail folder type. If you want to create a new item of a different item type than the folder, create the item in the matching folder type and then move the item into the public folder. Restrictions and limitations This component must be installed on the Microsoft Exchange server or on a client machine that has Microsoft Outlook. If installed on a client machine with Microsoft Outlook, then the feature Collaboration Data Objects must be installed. The Log On NT As account on the AutoStore Service Manager must be the NT account associated with the selected exchange mailbox. This is required to perform NT authentication and gain access to the Exchange Server. If you are storing to Exchange Public folders, do not store in a folder that ends with the <space> character. For example, My<space>Folder is ok, but My<space>Folder<space> will not work. If you are running two tasks to two Exchange servers, such as storing documents to two storage areas on different servers, follow these guidelines: Make sure the same mailbox exists on both servers. 1. Make sure the mailbox has the same name that the service is using on the AutoStore server. 2. Make sure you have sufficient rights available for both servers. Page 119

120 MultiRouter The multi-router configuration screen lists the destination components that are available for your process. Use the multi-router to select one route (destination) component from the list of available components. Use the multi-router component to set the route (destination) component attributes by clicking the component configuration button on the right side of the list. The selected component remains highlighted to indicate that it is active within the multi-router list. Page 120

121 OpenForms Product Overview and Feature Highlights The OpenForms capture and route components feature an integration between the workflow server and the ABBYY FormReader Enterprise Edition for AutoStore, providing flexible, scalable, and cost-effective forms capture, processing, and archival. Use OpenForms Route component to route documents from variety of MFPs and digital copiers into a server-based ABBYY FormReader Enterprise engine. Upon recognition and processing by ABBYY FormReader Enterprise engine, the processed forms and associated data is handed into the workflow capture component. Use the OpenForms Capture component to subsequently retrieve the processed documents for workflow processing into the desired Document or Database Management Systems. A thorough understanding of ABBYY FormReader Enterprise is required and it is highly recommended to have ABBYY FormReader Enterprise Edition for AutoStore configured prior to configuration of the workflow. This component features a flexible hand-over of documents from variety of MFP devices and digital copiers into ABBYY s FormReader engine. Documents are routed directly from the MFP devices and digital copiers into a server-based ABBYY FormReader Enterprise engine. Mapping of extracted fields directly into destination fields of workflow's variety of document and database management systems. Custom workflow handling based on document template setting. Using this Component In order to create a complete workflow for processing forms, you are required to implement a multi-process workflow. Capture multiple form types from an MFP device, route to ABBYY for form recognition and processing, deliver to workflow process where the workflow provides customized storage for each form type. In the first process, define and configure the capture component along with the OpenForms route component. This component retrieves the images and metadata from Image folder for recognition and processing. In the second process, define and configure the OpenForms capture component to collect the processed images along with metadata from ABBYY engine for storage/archival into the desired document management system or database. You may use RRTs for naming folders and files. The Configuration of OpenForms In order to create a complete workflow for processing forms, design a 2-process workflow. In the first process define the capture component and configure the ABBYY FormReader Enterprise route component to route the images to the ABBYY engine. In the second process, define the ABBYY capture component to pick the processed images along with the metadata from the ABBYY engine for storage/archival into the desired document management system or database. Note: You must be running ABBYY FormReader Enterprise Edition Version for AutoStore Version 6.0. Populate the ABBYY Form Reader Enterprise Route component attributes. Batch type Page 121

122 Enter the Batch type you want to process. A batch type is a description of page templates, document templates and their sequence, registration parameters, and setting and rules required for batch recognition and data validation. Each batch to be processed by OpenForms server is associated with a certain batch type. Use the ABBYY Administration Station to create a Batch Type. Then the batch type becomes available to OpenForms Route component for selection. Please refer to ABBYY FormReader Enterprise Edition for AutoStore documentation for further detail. Image folder Enter the folder path of where you want the captured images saved for processing. This folder path must match the image folder path that is set in ABBYY FormReader Registration server. The image folder must be configured as a UNC. In this case both ABBYY server and the workflow server must have read/write access to this UNC. When the ABBYY Registration Station is started for the first time, the path to the image folder must be configured. The ABBYY Registration Station checks this folder to pick up images for recognition by the ABBYY Enterprise engine. Valid image types are listed in the table below: Type BMP PCX PNG JPEG TIFF DCX PDF Color Back-and-white, gray, color Back-and-white, gray Black-and-white, gray, color Gray, color Black-and-white - not compressed, CCITT3, CCITT4, Packbits; gray - not compressed, Packbits, JPEG; color not compressed, JPEG Black-and-white, gray Files in PDF image-only format (separately paid option) NOTE: The most recommended input format is TIFF CCITT Group 4 compression. The most recommended scanning resolution is 300 dpi for normal printed and hand-printed text. For very small text higher resolution might be required. Parameters OpenForms route component sends the captured forms to the ABBYY FormReader Enterprise Server for recognition and further processing. Upon completion of processing the output files are generated and passed to the OpenForms capture component. Use the Parameters setting to create association between the form and additional form related information (metadata). The metadata is then sent to ABBYY FormReader Engine. For example, when setting up the batch type, you can specify "City" as a registration parameter. In this case the MFP user will be prompted to fill out the field corresponding to this registration parameter. This registration parameter and the user-entered information will then become available to the OpenForms capture component and can be saved to the desired storage/archival system. Two types of parameters can be created: ABBYY Parameter - Enter the registration Parameter Name as it appears within ABBYY administration station. Enter the corresponding value for the registration parameter. This value can then be made available to the OpenForms component. The parameter value can be defined as an RRT or a static value. Workflow Process Parameter - Enter Parameter Name as it appears within workflow configuration. Enter the corresponding value for this parameter. This value can then be made available to the OpenForms component. The parameter value can be defined as an RRT or a static value. Page 122

123 RRTs for OpenForms Component's RRT The RRT ID for OpenForms capture component is AFS. Reserved Replacement Tag Names (RRTN) The following table describes the reserved RTN values for this component. Name Description ABBYY.%<>% Returns the value of ABBYY registered parameter that is specified between the "%". For example ~AFS::ABBYY.%BANK_NAME%~ returns the value of "BANK_NAME". Please refer to ABBYY FormReader Enterprise documentation for more detail about registration parameters. PROCESS.%<>% Returns the value of the workflow service parameter that is specified in "<>". PageCount DocType DocStatus DocNumber ImagePath BatchID <N>,PageNumber <N>,PageType <N>,PageStatus Returns the number of pages within the ABBYY-defined form. Returns the document type as defined in ABBYY. Returns the status of the ABBYY processed document. Returns the number of documents. For example, if you scan 3 documents and each document is 2 pages long, the returned values can be1, 2, 3 for the first, second, and third document. Returns the folder path to the ABBYY-processed image. This is the folder path to the output image after ABBYY has completed processing. Returns the ABBYY assigned unique identifier of a batch. Returns a number that corresponds to the original scanned image page. For example, assume three 5-page forms are captured(scanned). For the first form, ~AFS::2,PageNumber~ returns a number "2". For the second form. ~AFS::2.PageNumber~ returns a number "7", and for the third form this RRT returns number "12". Returns a page type as defined in ABBYY for the Nth page of the form. Returns a page status as defined in ABBYY for the Nth page of the form. The following example provides some sample usage for your reference: ~AFS::DocType~~AFS::PageCount~ - replaced with the value Form5 if the document type was Form and the form was 5 pages long. Field Replacement Tag Names (FRTN) This component supports FRTNs and replacement of field names with metadata values. The following provides several examples of how FRTN is used: AFS::%<FieldName>%~ Returns the value for the <FieldName> in the form. This RRTN is equivalent to ~AFS::0,%<FieldName>%~. ~AFS::<N>,%<FieldName>%~ Returns the value for the Nth occurrence <FieldName> in the entire form. ~AFS::0,%<FieldName>%~ Returns the value for the first occurrence of <FieldName> in the entire form. For example, if a form consists of multiple pages, and there are 5 occurrences of field name "Customer", this RRTN returns the value of the first occurrence of "Customer". ~AFS::-1,%<FieldName>%~ Returns the value for the last occurrence of <FieldName> in the entire form. For example, if a form consists of multiple pages, and there are 5 occurrences of field name "Customer", this RRTN returns the value of the last occurrence of "Customer". Page 123

124 AFS::*,%<FieldName>%~ Returns the value for all occurrences of <FieldName> in the entire form. For example, if a form consists of multiple pages and there are 5 occurrences of field name "Customer", this RRTN returns the comma-separated values of all the occurrences of "Customer". Special Set Replacement Tag Names (SSRTN) This component doesn't support any SSRTNs. Troubleshooting Tips / Restrictions and Limitations Problem Description Workflow process log file indicates that image is successfully routed to ABBYY, however ABBYY server has not received the image. Workflow process log file indicates that service is unable to route documents Service Manager fails to start. The Process fails to store the documents into the destination directory. The Process fails. Restrictions and limitations You must be running ABBYY FormReader Enterprise Edition for AutoStore Version 6.0. ABBYY FormReader Enterprise for AutoStore does not support PDF file format. Solution Make sure the access rights to the image folder are set properly. Verify that the service is running with a user credential that has read/write access to the image folder. You must be Logged On not under Local System account, but as an Administrator to this local machine. For example: \\<machine name>\administrator; password: passadmin. Make sure the Image Folder path matches the Image Folder path configured in ABBYY FormReader Registration Station. Make sure the input document file format is supported by ABBYY FormReader Enterprise. Page 124

125 OpenText Livelink (9.x) Product Overview and Feature Highlights Use the OpenText Livelink (9.x) route and econnector components to send documents and data into the OpenText's Livelink 9.x application. The integration between the server and Livelink enables Livelink users to capture documents from a variety of server Capture components into this document management system. The component supports sending documents into Livelink ECM 9.2 and Livelink ECM servers. Log on to Livelink and identify the folder, category and fields within the component where you want the document to be stored. Set up your workflow process to capture content from the specified Capture component and then store the content in the specified Open Text Livelink folder. The integration between the server software and the OpenText Livelink takes advantage of Livelink features, such as multiple category support, security options, multi-value document and folder naming support. This component supports the following features: Connect to the Livelink 9.x server using different connection types. Set impersonator to the sent document. Send document to the selected folder on the server. Various document versioning support. Document lock for enhanced security. Integration with Livelink security options and features. Assigning attributes to the sent documents. Multiple category and folder structure support. Using the Component This component is mainly used to store any type of content from various sources. This component allows you to meet your regulatory and archival requirements for records retention with ease. See a sample list of use cases below. Knowledge Management - Capture, process, organize, share and store valuable corporate information into Livelink 9.x document management system. Direct device connectivity - Allow users to archive important documents by pressing just a few buttons on a scanning device. Use the OpenText Livelink (9.x) component to directly connect various devices such as digital copiers, desktop scanners, production high-speed scanners, desktop files and other types of files to back end Livelink 9.x. Batch Import Server - Use this component along with Poll Directory to create batch import directories, where files read in from various directories can be imported directly into back-end Livelink 9.x. Uniform Capture Process tools - Create capture business rules that dictate how your corporate content is captured into back-end document management system using our process designer tools. Connect files to Livelink DMS - Use POP3 or SMTPCapture components to connect content and archive all s within an inbox or all s sent to an SMTP gateway into Livelink for archival, management, or sharing. Page 125

126 The Configuration of OpenText Livelink 9.x General Tab Enter the general attributes that define connectivity to the Livelink application. Field Name Server Database Username Password Port Impersonate Function Enter the IP address or the host name of the OpenText Livelink 9.x server. Enter the name of the Livelink database you are connecting to. If a null string is specified, the system uses the default database assigned to the dftconnection variable in the [general] section of the opentext.ini file. Enter a valid Livelink username. The processed documents are associated with this username. Enter a valid password. Enter the port number that the server uses to communicate with the OpenText Livelink server. The port number value must match the port number that is configured on the OpenText Livelink software. If you select this option, you have to supply the user name to impersonate. Make sure to use administrator s user name and password for impersonation to work. Advanced Click on Advanced button to activate security mechanism used by Livelink API (LAPI) software to exchange data with the Open Text Livelink server. The following options are available: Direct Connection Non-secure Tunneling Non-secure Proxy Server Tunneling Secure Tunneling Direct Connection - By default, this component uses a direct connection, which does not ensure the confidentiality of data passed over the Internet or any unsecured network. The messages are passed as unencrypted plain text. If someone intercepts the plain text message, they may be able to view its contents. Page 126

127 Non-secure Tunneling - Non-secure tunneling is when a LAPI application exchanges data with a Livelink server by transmitting unencrypted (plaintext) Hypertext Transfer Protocol (HTTP) messages through the Web server integrated with a Livelink server. The server sends data in a HTTP request to the Web server integrated with the Livelink server. The Livelink CGI process acts as a proxy that forwards the request to the Livelink server (similar to how it responds to a Livelink request made over a socket connection). The Livelink server processes the server request, generates a response, and returns it to the Livelink CGI. The Livelink CGI process forwards the Livelink server's response to the Web server, which returns the response to the server. Field HTTPUserName HTTPPassword LivelinkCGI Description User name known to the Web server. Password of the HTTPUserName account. URL to the Livelink CGI integration process. When this option is selected, the information on the General tab should be changed accordingly: Field Default Value Use Server WebServerHost the name of the machine on which the Web server is running on. Port 80 the non-secure port to the Web server. Connection (null string) use the default Livelink database connection assigned to the dftconnection variable in the [general] section of the opentext.ini file. User Name LivelinkUserName the Livelink user account that has access to the Livelink server. Password LivelinkPassword the password of the LivelinkUserName user account. Non-secure proxy server tunneling - Non-secure proxy server tunneling is when a LAPI application exchanges data with a Livelink server by transmitting unencrypted (plaintext) Hypertext Transfer Protocol (HTTP) messages through the Web Proxy Server, which passes messages to the Web server integrated with a Livelink server. The server sends data in a HTTP request to the Web proxy server, much like a Web browser requests data from a Web server through the Web proxy server. The Web proxy server forwards the request to the Web server integrated with the Livelink server. The Livelink CGI process acts as a proxy that forwards the request to the Livelink server (similar to how it responds to a Livelink request made over a socket connection). Page 127

128 The Livelink server processes server's request, generates a response, and returns it to the Livelink CGI. The Livelink CGI process forwards the Livelink server's response to the Web server, which returns the response to server application through the Web proxy server. Field Value Description HTTPUserName myhttpusername User name known to the Web server. HTTPPassword myhttppassword Password of the HTTPUserName account. LivelinkCGI The full URL to the Livelink CGI integration process, where host is the Livelink host name and port is the Web server port number. When this option is selected, the information on the General tab should be changed accordingly: Field Default Value Use Server ProxyServerHost the name of the machine on which the Web proxy server is running. Port 8080 the port to the Web proxy server. Connection (null string) the default Livelink database connection assigned to the dftconnection variable in the [general] section of the opentext.ini file. User Name LivelinkUserName the Livelink user account that has access to the Livelink server. Password LivelinkPassword the password of the LivelinkUserName user account. Secure Tunneling - This option requires Livelink Secure Connect. You must separately purchase and install Livelink Secure Connect before you can implement secure communications. Livelink Secure Connect includes RSA BSAFE cryptographic and security protocol software from RSA Security, Inc. The data is virtually impossible to decipher if intercepted but is easily converted to plaintext by the application that is intended to receive the data. The server sends data in a Secure Hypertext Transfer Protocol (HTTPS) request to the Web server integrated with the Livelink server. Browsers use the HTTPS protocol to encrypt user page requests and decrypt pages returned by a Web server. The Web server negotiates the SSL connection with the server through a SSL handshake and decrypts the application's request. The Livelink CGI process acts as a proxy that forwards the request to the Livelink server (similar to how it responds to a typical Livelink request). The Livelink server processes server's request, generates a response, and returns it to the Livelink CGI. The Livelink CGI process forwards the Livelink server's response to the Web server, which encrypts the response and returns it to the server. Field Default Value Use HTTPUserName myhttpusername a user name known to the Web server. HTTPPassword myhttppassword the password of the myhttpusername account. LivelinkCGI /livelink/livelink.exe the URL to the Livelink CGI integration process. CA Root Certificates A secure LAPI client application requires the root certificate of the Certificate Authority (CA) from the secure Web server integrated with a Livelink Server to verify the authenticity of the certificate passed. In most cases, third-party CAs provide instructions on how to obtain their root certificates on their Web sites (for example, or Optionally, you can export some CA root certificates from Microsoft Internet Explorer 5.0 and later. When this option is selected, the information on the General tab should be changed accordingly: Page 128

129 Field Default Value Use Server WebServerHost the name of the machine on which the Web server is running. Port 443 the secure port to the Web server. Connection (null string) use the default Livelink database connection assigned to the dftconnection variable in the [general] section of the opentext.ini file. User Name LivelinkUserName the Livelink user account that has access to the Livelink server. Password LivelinkPassword the password of the LivelinkUserName user account. Document tab Enter the document attributes for the document that is being stored in the Livelink application. Field Name Description Folder Function Enter a description of the document you are storing. Enter the OpenText Livelink folder destination that you want to store the document. You can enter the folder manually or click the button. This button opens the Select Destination dialog that allows to select a folder from the list of available folders on the server. You can dynamically create folders from here. Note: The Livelink 9.x server supports using '/' symbol in folder names. If you want to enter the folder name with '/' symbol, please use ':' before it in order to make the component to interpret this symbol correctly, i.e. as a part of name but not the delimiter between folder and subfolder names. For example, 1. If C is a subfolder of B and B is a subfolder of A, then enter A/B/C. 2. If C is a subfolder of A/B, then enter A:/B/C. 3. If B/C is a subfolder of A, then enter A/B:/C. Lock File Select this check box to limit the availability of the document. When this check box is selected, only the user who is logged in can gain access to the document in the future. If this check box Page 129

130 Pass-through Replace New Version Rename is not selected, the document is available to all users. The Pass-through option is available with OpenText Livelink econnector component. When this option is selected, the document is passed through to the next component in the workflow process. Select this option if you want the newly processed document to replace the existing document. Select this option if you want to store the newly processed document without overwriting the existing document with the same name. Enter the name of the newly processed file. Please refer to the component's RRT section for further detail. System tab This tab displays additional system attributes configured on the Livelink server and contains the buttons for managing the attribute list: Add - click this button to add an attribute in the opened Add an attribute dialog. Modify - select an attribute in the list and click this button to modify the selected attribute in the opened Modify an attribute dialog. Remove - select an attribute in the list and click this button to remove the selected item from the list. The system attributes are applied to every document in the Livelink application. Note: If the values of some required nodes are not set, and you want to save the configuration, the following warning message will be displayed: "Would you like to save, although all required system nodes are not set?" If you click OK, the configuration is saved. Follow the steps below to create new attributes in the Livelink application: 1. Click the Administer Additional Node Attributes link in the System Administration section on the Livelink Administration page. 2. On the Administer Additional Node Attributes page, click the Add a New Attribute link. Page 130

131 3. On the Add New Attribute page, type a unique name for the attribute in the Name field. 4. Click one of the following attribute types in the Type drop-down list: Text : Field Text : Popup Text : Multiline Flag : Checkbox Date : Field Date : Popup Number : Text field Number : Popup Add/Modify an attribute This dialog allows you to add/modify a system attribute of the document. Node - select name of the attribute from the drop-down list or type it manually. This field can contain RRTs from the previous components. Note: In the previous version of the component other components' RRTs in attribute names were sometimes replaced incorrectly. However in the current version of the component, they are replaced correctly, thanks to the new form of storing attribute values in the configuration file. Therefore, if some configuration was created with the previous version of the component and has the attribute name that contains other component's RRT, and you open this configuration with the current version of the component, do not remove this attribute and then try to save this configuration, the following warning message appears: "Saving configuration file in the new format can lead to a breach of compatibility. Would you like to save?" Value - enter the value of the attribute manually or select using the button if it is available. Type - this text box displays the node attribute type. Required - this text box displays "yes" if the attribute is required, and "no" if it is not required. Categories tab In this tab, you can create and remove associations between the processed document and the categories defined in the Livelink application. Every category associated with the document is displayed as a separate tab. To create an association with a new category, click the Select button. To remove the selected association click the Remove button. Page 131

132 Select Click this button to select a category that you want to associate your document with and populate the field values if appropriate. The button opens the Categories dialog which allows you to select one of available categories. When you associate a document with a category, the new tab appears. This tab allows you to add, modify and remove the attributes for the selected category using Add, Modify and Remove buttons correspondingly. You can associate your document with multiple categories. Remove Click on Remove to remove the association between a document and a category. Add/Modify an attribute This dialog allows you to add/modify the attribute or the set of attributes associated with the selected category. Node - select name of the attribute or the set of attributes from the drop-down list or type it manually. This field can contain RRTs from the previous components. Note: In the previous version of the component other components' RRTs in attribute names were sometimes replaced incorrectly. However in the current version of the component, they are replaced correctly, thanks to the new form of storing attribute values in the configuration file. Therefore, if some configuration was created with the previous version of the component and has the attribute name that contains other component's RRT, and you open this configuration with the current version of the component, do not remove this attribute and then try to save this configuration, the following warning message appears: "Saving configuration file in the new format can lead to a breach of compatibility. Would you like to save?" Value - enter the value of the attribute manually or select using the button if it is available. If you select a set of node attributes, you cannot set a value to it and 'Not applicable to Sets' is displayed in the Value text box. In this case, the button opens the Set Node dialog that displays the attributes from the selected set and contains the buttons for managing the attribute list. Type - this text box displays the type of the attribute or the set of attributes. Required - this text box displays "yes" if the attribute or the set of attributes is required, and "no" if it is not required. Page 132

133 RRTs for OpenText Livelink 9.x The RRT ID for this component is OTX. Reserved Replacement Tag Names (RRTN) The following table describes the reserved RTN values for this component. Name FileName Counter FileExt Description The original file name value. An incremental counter based on the duplicate file names found within a directory. The counter value concatenated with a name provides a unique file name. Original file extension value The following example provides some sample usage for your reference: ~OTX::FileName~~OTX::Counter~ - replaced with the value Document5 if the original file name was Document and there were up to 4 (Document1 to Document4) files already in the destination folder path. Field Replacement Tag Names (FRTN) This component does not have any FRTNs and replacement of field names with metadata values. Special Set Replacement Tag Names (SSRTN) This component does not have any SSRTNs. Troubleshooting Tips / Restrictions and Limitations Problem Description No categories are available when you are configuring Categories tab. When you use the Non-secure Tunneling or Non-secure proxy server tunneling connection types, the files are not sent to the server. Solution May be you have not created any categories on the Livelink Enterprise Server, or your user name and password are incorrect. Please make sure that the categories are configured and check the user name and password. Install Java SE Runtime Environment of version or above for the correct work of those connection types. Restrictions and limitations The component supports sending documents into Livelink ECM 9.2 and Livelink ECM servers. You cannot create categories through this component. A category has to be created via the OpenText Livelink application configuration first. You may not create fields through this component. Fields have to be created via the Livelink application configuration first. Page 133

134 Send to Database Product Overview and Feature Highlights Use this component in a process to directly write images, files, or data into ODBC database tables such as Microsoft Access, or Visual Fox Pro. Application of this component includes direct table update on any application SQL table with images and data elements, or creation of document archival system. The ODBC Data Source must be properly set up prior to configuring this component. This component provides: Select from various Data Sources to store data and binary documents into. Provides Username and Password for access security. Select the Table Name that you want to place the image and field values into. Select the binary Image Field Name, the column in the table which you want to save the image in. Add, Modify, Remove Field Values to a database table. Using the Component The most common use of this component is for archival purposes. Files, data, and documents can be stored in binary format into ODBC compliant database tables for long term archival and record keeping. As an example, one of the more common processes that can take advantage of this component is having the Multi-functional Device (MFD) as a Capture (source) component. From the MFD, configure this component and assign Runtime Replacement Tags to store the images, files, and new field names, into the Data Source that you select. This component can be used with any file/document type. The Configuration of Send to Database General tab Page 134

135 Field Name Data Source User Name Password Table Name Image Field Name Function Provide the Data Source name that you want to use (i.e., Microsoft Access). This is a required field. Enter the user name to log in to the Data Source. Enter the password to log into the Data Source. Select the Table Name which you want to connect to. This is a required field. Select the field in the table that you want to save the image to. Image Field Name has to be a large binary field (BLOB), otherwise, when the process is run, it will fail. This field must be configured. If you need to create new fields in the database, proceed to Field values tab and select Add. Field values tab Field Name Add Modify Remove Function Click this button to add a new field value entries to the database table. The new field value can contain Runtime Replacement Tags. Click on this button to modify the field value entries for the database table. Click on this button to remove a field value entries from the database table. RRTs for Send to Database The RRT ID for this component is SDB Reserved Replacement Tag Names (RRTN) Name FileName Counter FileExt Description The original file name value. An incremental counter based on the duplicate file names found within a directory. The counter value concatenated with a name provides a unique file name. Original file extension value The following example provides some sample usage for your reference: ~SDB::%m~-~SDB::%d~-~SDB::%Y~ will be replaced by Field Replacement Tag Names (FRTN) This component does not have any FRTNs and replacement of field names with metadata values. Page 135

136 Special Set Replacement Tag Names (SSRTN) SSRTN Description %a Abbreviated weekday name %A Full weekday name %b Abbreviated month name %B Full month name %d Day of month as decimal number (01 31) %H Hour in 24-hour format (00 23) %I Hour in 12-hour format (01 12) %j Day of year as decimal number ( ) %m Month as decimal number (01 12) %M Minute as decimal number (00 59) %p Current locale s A.M./P.M. indicator for -hour clock %S Second as decimal number (00 59) %U Week of year as decimal number, with Sunday as first day of week (00 53) %w Weekday as decimal number (0 6; Sunday is 0) %W Week of year as decimal number, with Monday as first day of week (00 53) %y Year without century, as decimal number (00 99) %Y Year with century, as decimal number Troubleshooting tips / Restrictions and limitations Problem Description Error displayed when selecting the Table browse button. Solution You either do not have a valid user name and password, or you have an invalid Data Source. Make sure the Data Source you selected is actually connected, and configured properly. Restrictions and limitations If you need to create a database table, you should do so from within the database and create the tables from there. You cannot create tables dynamically from this component. Data Source, Table Name, and the Image Field Name fields are mandatory and have to be configured.. The Image Field name must be a BLOB field. All images within a BLOB field are stored as binary values. To extract and view the images you must develop your own image extraction tool. Page 136

137 Send to Database (Bulk) Product Overview and Feature Highlights Use this component in a process to Batch write files, or data into ODBC database tables such as Microsoft Access, or Visual Fox Pro. Application of this component includes direct table update on any application SQL table with data elements, or creation of document archival system. The ODBC Data Source must be properly set up prior to configuring this component. The Configuration of Send to Database (Bulk) General tab Field Name Data Source User Name Password Table Name Function Provide the Data Source name that you want to use (i.e., Microsoft Access). This is a required field. Enter the user name to log in to the Data Source. Enter the password to log into the Data Source. Select the Table Name which you want to connect to. This is a required field. Field Mapping tab Page 137

138 Field Name Field Delimiter Direct Mapping DB Fields Type Batch Field Function Enter the Field Delimiter used in the CSV file. If this box is checked, the database field names are mapped automatically from the column names from the first row in the CSV file. If this checkbox is un-checked, you would manually type in the Batch fields manually. The first row of the CSV file must be reserved for column names. Displays the database fields from the selected table in the database. Displays the database field type. Automatically mapped or manually enter the CSV header field names from the first row. RRTs for Send to Database (Bulk) This component does not generate Runtime Replacement Tags, however all the parameters can contain RRT strings. Troubleshooting tips / Restrictions and limitations There is no information available at this time. Page 138

139 Send to Folder Product Overview and Feature Highlights Send to Folder is a Route component that copies files to any local or network directory. Using directories is one of the fastest methods for implementing a document storage system as storing files into flat folders requires no database, no application, and lower cost of ownership. With Send to Folder component, you can create business rules for multiple folder locations, security access, and file naming of scanned imaged and processed file. This component is also capable of checking security access level of the user prior to storing documents into folders. Using the check security feature, users scanning document into folder destination can only store into the destination directory if proper access level has been granted to the user by the administrator. Using this feature an organization can implement a secured storage location that accepts files only based on security settings. The Send to Folder Route and econnector components are identical except the Send to Folder Route component solely stores the files and doesn't pass the files on, as it is the last component in the process. The Send to Folder econnector passes the files onto the next component in the process. The Send to Folder econnector also allows you to enable or disable pass-through of documents. This option makes the document available/not available for other components in the process. This component requires Active Directory Services with minimum of NT 4.0. This component provides: Create dynamic folder names and locations. Option to rename the file, based on document index information, field values, or field value references. Option to Check User Security to check user level security against the destination folder location. Only accept users with write permission to store files into destination location. Enter additional information about the nature of documents stored in the folder along keywords and comments. All types of files including images can be processed through this component. Send to Folder is fully integrated with other components such as Barcode, Form Recognition, OCR, PDF, etc. For example, a barcode value can be used as part of destination folder name to create dynamic destination folder based on barcode values on the document. Using the Component A user logs into a device, scans a document and the document is placed in user's directory on a shared network drive. Use this component to store information into several folders where other processes will read the information for processing. Page 139

140 The Configuration of Send to Folder General Tab Field Name Folder Path Overwrite Existing File Schema Check User Security User Name Function Enter the destination folder path that you want files to be copied to. The server must have write access to this folder. The input device can dynamically set the folder path. If the overwrite option is not selected, and a file under that name already exists in that destination, an error message is generated. Rename File Check this box if you want the output file to be renamed. Enter the Schema name for the output file name. You can use Runtime Replacement Tags (RRT) to dynamically set the value of the schema. If this option is enabled, the system checks the user's or sender's security level to verify the write access. This refers to a look up in the user's Active Directory Services to see if the user has security rights to copy the files to the designated folder. Enter the user name for the directory. Summary tab Page 140

141 Field Name Title Subject Author Category Keywords Comments Function Enter the Title of the document. Enter a subject for your document. Enter the author of the document. Enter a category for the document. Enter keywords for the document. The Keywords assist with searching for the file. Keywords may be separated by either "," or " " (space). Enter comments that can provide information about the file. RRTs for Send to Database The RRT ID for this component is STF Reserved Replacement Tag Names (RRTN) Name FileName Counter FileExt Path Description The original file name value. An incremental counter based on the duplicate file names found within a directory. The counter value concatenated with a name provides a unique file name. Original file extension value The folder path entry. For example, if you have configured 3 folder paths, then this RRTN can take the following values: Path1, Path2, Path3. Path1 refers to the first path entry configured, Path2 refers to the 2nd path entry configured, etc.. The following example provides some sample usage for your reference: ~STF::FileName~~STF::Counter~ - replaced with the value Document5 if the original file name was Document and there were up to 4 (Document1 to Document4) files already in the destination folder path. Note: The Reserved RTN values FileName, Counter, FileExt can only be used with the Rename field of this component. In other words, you may not use ~STF::FileName~, ~STF::Counter~, ~STF::FileExt~ in any other component but Send to Folder econnector and it must be used with the Rename field of this component only. Note: You can use the C format specifiers to create and display the counter with the required number of leading spaces or leading zeros. For example, if the file name is Test.doc, and the rename schema is ~STF::FileName ~~%03STF::Counter~~STF::FileExt~, the resulting file names are Test001.doc, Test002, etc.. If the file name is Test.doc and the rename schema is ~STF::FileName~~%3STF::Counter~~STF::FileExt~, the resulting file names are Test 1.doc, Test 2.doc, etc.(note the 2 spaces after "Test"). Field Replacement Tag Names (FRTN) This component does not have any FRTNs and replacement of field names with metadata values. Special Set Replacement Tag Names (SSRTN) SSRTN Description %a Abbreviated weekday name %A Full weekday name %b Abbreviated month name %B Full month name %d Day of month as decimal number (01 31) %H Hour in 24-hour format (00 23) %I Hour in 12-hour format (01 12) %j Day of year as decimal number ( ) %m Month as decimal number (01 12) %M Minute as decimal number (00 59) Page 141

142 %p Current locale s A.M./P.M. indicator for -hour clock %S Second as decimal number (00 59) %U Week of year as decimal number, with Sunday as first day of week (00 53) %w Weekday as decimal number (0 6; Sunday is 0) %W Week of year as decimal number, with Monday as first day of week (00 53) %y Year without century, as decimal number (00 99) %Y Year with century, as decimal number Troubleshooting Tips / Restrictions and Limitations Problem Description Error dialog box pops up when creating a folder path. The Path RRTN is not replaced with a path folder. Solution Make sure invalid characters are not used in the folder path definition. The invalid characters are: \ / : *? " < > This situation occurs when you specify a Path, such as Path8, where only 6 folder path entries are configured with the Send to Folder component. Check to make sure the Path number is valid. Restrictions and limitations No information is available at this time. Page 142

143 Send to FTP Product Overview and Feature Highlights The Send to FTP component provides you with the mechanism for storing files that are fed from a capture component to the FTP site for storage. This component is available either as an econnector (process) component or as a route component. Additional control over the FTP site transmission is provided through support for secured FTP sites as well as bandwidth flow-control. Design your process according to your business process, such that a client (anonymous or specific) may open the FTP session to this server for document retrieval, etc. as required by the business process. The Send to FTP Route and econnector (Process) components are identical except the Send to FTP Route component solely stores the files and doesn't pass the files on as it is the last component in the process. The Send to FTP econnector component, however passes the files onto the next component which could either be another process or a route component. The Send to FTP econnector also allows you to enable/disable pass-through of documents which will make the document available/not available for other downstream components to process. This component provides: Configuration of multiple FTP sites. Active flow control. Secured FTP site access. Supports dynamic file renaming and storage. Using the Component Send to FTP component is very similar to the FTP Store component with a few added functionality. The following are examples of how this component may be used: An enterprise where PDF documents from several sources have to be placed on several FTP servers. These documents may then be processed for printing, or sending out as , depending on the business need. Connectivity of remote offices to central office can easily be implemented using FTP component. Scanners from remote sites can easily be connected a multiple sites using a secured FTP protocol. Control the bandwidth usage when connecting remote scanning offices through use of the Bandwidth control feature of FTP component. Bandwidth control lowers the impact of implementing distributed scanning on transmission infrastructure. Page 143

144 The Configuration of Send to FTP Main window Set the attributes of the FTP site(s) here. Field Name Activate Pass-through document(s) Add Function Check this box to activate this component in the workflow. This option applies only to the econnector component. Check this box if you want the document(s) to be available to the rest of the components in your process. This checkbox is available for the Send to FTP econnector component. Click on Add to add FTP site(s) to your process. It opens Configurations dialog. Configurations Page 144

145 Field Name Server User Name User Password Folder Path Overwrite Existing Rename File Schema Function Specify the IP address or the server name of the FTP site. You can also specify the FTP site as ftp://company-site.com. Specify the user name of the client who will have access rights to the FTP site. After you specify the user name, specify the password that is associated with this user. If you do not specify the user name, the access rights are set to anonymous by default. Specify the password that is associated with the username. You can specify the folder where the documents will be stored on the FTP server. If you specify a new folder in the dialog box, a new folder with the same name is created on the FTP server. However, if you do not specify a path or folder name, the data is stored on the root directory of the FTP server. Select this check box if you want the newly created files on the FTP site to overwrite the existing files that have the same name. If you do not select this option, the file will automatically be appended with a number that is incremented each time a newer version of a file with the same name is stored on the FTP site. Check this box is you want the output file to be renamed. Enter the Schema name for the output file name. You can use Runtime Replacement Tags (RRT) to dynamically set the value of the schema. Advanced settings Activate Flow Control FTP component provides an easy method to flow control the speed at which the data is transmitted. The purpose of the flow-control option is to provide means to manage the impact of FTP transmission may have on the transmission bandwidth from remote sites. The flow control knobs allow you to control the size of the buffer and the transmission interval of each buffer. Additional control is provided to test the flow control speed and provide an easy to use method to check the transmission speed. Check the Activate Flow Control box to activate the flow control options. Transfer Rate in Milliseconds use this knob to set your desired transfer intervals in Milliseconds. The longer the interval the slower the transmission rate. Page 145

146 Buffer Size in Bytes use this knob to set the size of each transmitted buffer. The larger the buffer size the higher the transmission rate and the larger impact on the bandwidth. Run Test Run Test test will be conducted against your FTP site. Make sure you have specified correct FTP site, user name and password. The tests are conducted using 100Kbytes buffers and at the end of each test cycle the results are reported in 100 Kbytes/X Seconds. Where X is the number of seconds it takes to send 100 Kbytes. Normal B/W documents are between 25 to 50 Kbytes. The size of images could vary based on type of scanner settings and you should observe your scanner setting parameters. Please note that you must have write access to conduct FTP testing against a site. Stop use the stop button to terminate test buffer Note: To use the test feature, you must have access to the FTP site(s) from your machine. This feature establishes connection to the FTP site and transmits dummy data to the FTP site to test transmission bandwidth. RRTs for Send to FTP The RRT ID for this component is FTP Reserved Replacement Tag Names (RRTN) Name FileName Counter FileExt Path Description The original file name value. An incremental counter based on the duplicate file names found within a directory. The counter value concatenated with a name provides a unique file name. Original file extension value The folder path entry. For example, if you have configured 3 folder paths, then this RRTN can take the following values: Path1, Path2, Path3. Path1 refers to the first path entry configured, Path2 refers to the 2nd path entry configured, etc.. The following example provides some sample usage for your reference: ~FTP::FileName~~FTP::Counter~ - replaced with the value Document5 if the original file name was Document and there were up to 4 (Document1 to Document4) files already in the destination folder path. Note: The Reserved RTN values FileName, Counter, FileExt can only be used with the Rename field of this component. In other words, you may not use ~FTP::FileName~, ~FTP::Counter~, ~FTP::FileExt~ in any other component but Send to Folder econnector and it must be used with the Rename field of this component only. Note: You can use the C format specifiers to create and display the counter with the required number of leading spaces or leading zeros. For example, if the file name is Test.doc, and the rename schema is ~FTP::FileName ~~%03~~FTP::Counter~~FTP::FileExt~, the resulting file names are Test001.doc, Test002, etc.. If the file name is Test.doc and the rename schema is ~FTP::FileName~~%3~~FTP::Counter~~FTP::FileExt~, the resulting file names are Test 1.doc, Test 2.doc, etc.(note the 2 spaces after "Test"). Field Replacement Tag Names (FRTN) This component does not have any FRTNs and replacement of field names with metadata values. Special Set Replacement Tag Names (SSRTN) SSRTN Description %a Abbreviated weekday name %A Full weekday name %b Abbreviated month name %B Full month name %d Day of month as decimal number (01 31) %H Hour in 24-hour format (00 23) %I Hour in 12-hour format (01 12) Page 146

147 %j Day of year as decimal number ( ) %m Month as decimal number (01 12) %M Minute as decimal number (00 59) %p Current locale s A.M./P.M. indicator for -hour clock %S Second as decimal number (00 59) %U Week of year as decimal number, with Sunday as first day of week (00 53) %w Weekday as decimal number (0 6; Sunday is 0) %W Week of year as decimal number, with Monday as first day of week (00 53) %y Year without century, as decimal number (00 99) %Y Year with century, as decimal number Troubleshooting Tips / Restrictions and Limitations Problem Description Files cannot be copied into the destination directory. Solution Make sure that the destination ftp folder has Write access. Check username/password to make sure it is valid. Check the access rights for the user. Check to make sure there are no firewalls. If overwrite existing is not checked off, make sure that a file with the same name does not already exist. Restrictions and limitations No information is available at this time. Page 147

148 Send to HTTP Product Overview - Feature Highlights Send to HTTP component is used to send data to the web-sites that contain web-forms. The component can send values for filling out web-form input fields and one or several files received on input. The number of values and files to be sent and their names depend on the selected web-site settings. The component uses HTTP protocol for data sending and allows to use SSL encrypting. The only difference between Send to HTTP Route and Send to HTTP Process component is that Send to HTTP Process component configuration has two additional options: Activate check box, which allows to send file to the web-site, before further processing by the downstream components, if selected. If this check box is not selected, the component won't perform any actions during files processing. Pass-through check box, which makes the file(s) available to the downstream components, if selected. These two options are not available in Send to HTTP Route component configuration. The component has the following features: The component's configuration contains a web browser for downloading web-sites and editing the downloaded web-form fields. The fields list can be filled automatically by the web-form fields from the downloaded web-site. SSL encrypting can be used for sending data to the web-sites that support secure communication. Anonymous connection to the web-site can be used instead of entering user name and password. The NTLM authentication can be used for sending data to the web-site that supports Integrated Windows authentication. The Basic authentication can be used for sending data to the web-site that supports Basic Windows authentication. The component allows to check HTML response text for matching a regular expression or a substring in order to determine success or failure of the data sending. Using This Component The most common usage cases for the component are: Sending information to the web-sites that contain login, search and other mechanisms, by means of fill-out forms. Sending information to the web forms that allow file attachments. The following use case provides a sample of the component application: Scan documents from an MFP device, save directly into a web-site containing a web-form: Design a workflow process with two components: an MFP component that corresponds to the selected type of an MFP device, and the Send to HTTP component. Download the desired web-site in the Web Browser window of the Send to HTTP configuration. Configure field values, which uniquely identify the document. Configure both components and start the process. Now when the MFP user enters a pre-configured function key on the control panel of the MFP device, the scanned document is routed directly into the web-site and the form fields are filled out with the configured field values. Page 148

149 Building a Process With Send to HTTP In the component's main window you can choose a web-site and determine all parameters and data for sending. Activate - this check box is present only in process component configuration window. Select this check box if you want to send the file(s) to the web-site before further processing by the downstream components. If this box is not checked, the component won't perform any actions during files processing. Pass-through - this check box is present only in process component configuration window. Select this check box if you want the file(s) to be available to the rest of the components in your process. Address - enter URL of the web-site containing the form you are going to fill out. This field can contain " or " followed by the domain name or IP address. For example, or Alternatively, this field can contain only the domain name or IP address, e.g. or It is mandatory to fill out this field. View - click this button to browse the selected web-site. The Web Browser dialog window will open. Fields group displays a list of the web-site form fields with the values to be sent and buttons for managing the fields. You can add, edit or remove a field using the Add, Edit and Remove buttons correspondingly. Note: The fields can be determined automatically if you load the web-site in the Web Browser dialog window. The values of the fields can be configured directly in the downloaded web-form. Add - click this button to add a new field to the fields list. The Field Properties dialog box will open. Edit - click this button to edit properties of the selected field from the list. The Field Properties dialog box will open. Remove - select one or several fields and click this button to remove the selected field(s) from the list. File field(s) - enter names of the attached files you wish to send. The number of the files and the file field names must correspond to the web-site form. Authentication group allows to select the type of authentication. Page 149

150 NTLM - select this check box to set Integrated Windows authentication. If you select this check box, you must enter system user name and password for connecting to the site. In this case the password is sent to the site in encrypted form. Basic - select this check box to set Basic Windows authentication. If you select this check box, you must enter system user name and password for connecting to the site. In this case the password is sent to the site in clear text. If you do not select neither NTLM nor Basic authentication, you can connect to the web-site as an anonymous user without entering user name and password. This is possible if the web-site settings allow anonymous access. If you select both NTLM and Basic authentication, the component first of all verifies if the NTLM authentication is supported by the web-site. If the verification is successful, the component uses the NTLM authentication. Else, the component verifies if the basic authentication is supported by the web-site. If the verification is successful, the component uses the basic authentication. Else, the anonymous access is used for connection. If the anonymous access is disabled on the web-site, the following error message appears in runtime: "Web-server authentication failed. One of possible reasons: incorrect user name and/or password". User name - enter user name to connect to the site. This field is enabled only if either the NTLM check box or the Basic check box is selected. It is mandatory to fill out this field. Password - enter user password to connect to the site. This field is enabled only if either the NTLM check box or the Basic check box is selected. Note: If the NTLM authentication is ON on the web-site and the computer where the component is running is in the service domain, the authentication will be passed in any case and the domain user name and password will be used for the authentication. The Authentication settings will be ignored in this case. The specified User name and Password make sense only if the computer is not in the service domain. SSL encrypting - select this check box if you want to use SSL encrypting for your data. You may use this feature only if the web-site supports secure communication with SSL encrypting. If the web-site requires secure communication, it is mandatory to select this option. HTML response check group allows to check the HTML response text for matching a regular expression or a substring in order to determine success or failure of the data sending. Check HTML response - if you select this check box, the HTML response text will be compared with a regular expression or a substring to determine success or failure of the data sending. Search for - enter a text that will be compared with the HTML response text. Match regular expression - if you select this check box, the text entered in the Search for field will be interpreted as a regular expression. E.g., [0-9] will be interpreted as a number in the interval from 0 to 9. Match substring - if you select this check box, the text entered in the Search for field will be interpreted as a substring. E.g., [0-9] will be interpreted as "[0-9]" string. Successful match denotes routing failure - if you select this check box, the text entered in the Search for field is compared with the HTML response text, and a successful match will mean a failure of data sending. If this checkbox is not selected, the component will interpret a successful match as a successful data sending. Match case - if you select this check box, the text entered in the Search for field is compared with the HTML response text case-sensitively. If this check box is not selected, the comparing is case-insensitive. Note: The component checks the HTML text contained in the HTTP response, that is put in the component service log. This text can differ from the web browser text since it can be generated by script. Page 150

151 Web Browser In this window you can download the desired web-site, edit the values directly in the form fields and save these values. Address - enter URL of the web-site containing a fill-out form. This field can contain " or " followed by the domain name or IP address. For example, or Alternatively, the field can contain only the domain name or IP address, e.g. or If the web-site URL was previously entered in the Address field of the Main window, this field displays the entered URL. Go - click this button to download the selected site. When the web-site is downloaded, the values previously configured in the fields list of the Main window are displayed in the web-form fields. You can edit the field values directly in the downloaded web-form. When you click OK, the Web Browser window closes, and the field values in the Main window are replaced by the values that you have entered in the corresponding fields of the downloaded web-form. If the fields list in the Main window does not contain the fields from the downloaded site, these fields are automatically added to the fields list with the configured values. Note: 1. OK button is disabled until the web site is downloaded completely. You can enter the field values during the process of the site loading, but when the loading is completed, the entered values are changed to the values previously configured in the fields list of the Main window. Therefore, it is recommended to edit form field values only after the OK button becomes enabled. 2. If the selected site does not contain any fill-out forms and you click OK, the following message will appear: "The selected site does not contain form fields", and the window will not close. Page 151

152 Field Properties Use this dialog box to add a new field or edit a selected field from the fields list. Field name - enter field name. It is mandatory to fill out this field. Field value - enter field value. RRTs for Send to HTTP Component RRT ID The RRT ID for this component is HTP. Reserved Replacement Tag Names (RRTN) This component does not have any RRTNs. Field Replacement Tag Names (FRTN) This component does not have any FRTNs. Special Set Replacement Tag Names (SSRTN) This component supports the Date/Time tag names listed below: Name Description %d Day of month as decimal number (01 31) %j Day of year as decimal number (01 366) %I Hour in 12-hour format (1 12) %H Hour in 24-hour format (00 23) %P Current locales AM/PM indicator for 12-hour clock %M Minute as decimal number (00 59) %m Month as decimal number (01 12) %b Abbreviated english month name (Jan - Dec) %B Full english month name (January - December) %S Second as decimal number (00 59) %U Week of year as decimal number, with Sunday as first day of week (00-53) %W Week of year as decimal number, with Monday as first day of week (00-53) %w Weekday as decimal number (0-6; Sunday is 0) %a Abbreviated english weekday name (Sun - Sat) %A Full english weekday name (Sunday - Saturday) %y Year without century as decimal number (00-99) %Y Year with century as decimal number Here is the sample use case of the above SSRTN: ~HTP::%Y~-~HTP::%m~ will be replaced by Page 152

153 Troubleshooting Tips / Restrictions and Limitations Problem description Status monitor shows the following error message: "The connection with the server has been reset or terminated, or an incompatible SSL protocol was encountered" and the component rejects the input file. Status monitor shows the following error message: "Webserver authentication failed. One of possible reasons: incorrect user name and/or password" and the component rejects the input file. Status monitor shows the following error message: "Server does not support the specified authentication type(s)" and the component rejects the input file. Status monitor shows the following error message: "The HTML response includes the substring indicating the invalid response data" and the component rejects the input file. Status monitor shows the following error message: "The HTML response includes the regular expression indicating the invalid response data" and the component rejects the input file. Status monitor shows the following error message: "The server name or address could not be resolved" and the component rejects the input file. Solution This message may appear in the following situations: 1. SSL option in the Windows IIS is turned ON and the SSL encrypting option in the component's configuration is turned OFF. Select the SSL encrypting check box. 2. The file size exceeds the web-site restrictions. Try to decrease the file size. 3. The specified resource cannot be found on the web-server. Check that you have entered correct URL of the web-site in the Address field. This message may appear in the following situations: 1. The Windows IIS has anonymous access disabled and you do not select neither the NTLM nor the Basic check box. Select the NTLM check box or the Basic check box. 2. You have selected both the NTLM and the Basic check boxes, but the web-site does not support neither NTLM nor basic authentication and the anonymous access is disabled. Contact the web-site administrator. 3. You have selected the NTLM check box or the Basic check box, but the specified user name or password are incorrect. Use the correct credentials. This message may appear in the following situations: 1. You have selected the NTLM check box but the web-site supports only basic authentication. Select the Basic check box. 2. You have selected the Basic check box but the web-site supports only NTLM authentication. Select the NTLM check box. This message means that the HTML response was checked for matching a specified substring and the result of the verification was interpreted as a routing failure. This message means that the HTML response was checked for matching a specified regular expression and the result of the verification was interpreted as a routing failure. This message means that the specified server name is incorrect. Make sure that you have specified correct URL of the web-site in the Address field. Page 153

154 Status monitor shows the following error message: "The server name or address cannot be resolved or the server returned an invalid or unrecognized response" and the component rejects the input file. The Component reports succeeded result even when a job failed to be accepted by a web-site and the sent information failed to appear in a web-site form. This message means that the specified server name is incorrect or the server response can not be recognized. Make sure that you have specified correct URL of the web-site in the Address field. The component checks the HTML text contained in HTTP response, that is put in the component service log. It can differ from the web browser text since it can be generated by script. Restrictions and limitations Web service uses the default HTTP and HTTPS ports. The component requires Internet Explorer 5.01 or a later version. The component requires Windows XP SP1 and later, Windows 2000 SP3 and later or Windows Server 2003 SP1 and later versions. When you use many processes for sending files to a web-server on Windows XP, the maximal number of processes in the component's configuration should be 10 for a proper operation of the component. The component submits form data only in multipart/form-data format that is used when the files are uploaded together with form field values. The component does not support data interchange if the server expects another data format, e.g. application/x-www-form-urlencoded. Page 154

155 Send to Mail Recipient Product Overview and Feature Highlights Send to Mail Recipient is a route component providing standard SMTP and Microsoft Exchange messaging capabilities. Use this component in your process, to send the processed file as an attachment to designated recipient(s). This powerful component allows you to distribute files, metadata, and additional information via . For example, use Digital Sender component as your source component to scan documents and then convert the scanned documents into PDF files and them as an attachment to designated recipient(s). Use this component to: Specify the desired SMTP gateway for delivering the message. Specify the desired Microsoft Exchange for delivering the message. Attach processed files to an and send to designated recipient(s). Return the processed files as attachment to the sender (requires sender ). Using the Component Consider a process where you want to capture documents, process them and send the processed documents as an attachment. Setup the process, by configuring the proper capture, process and add the Send to Mail Recipient component. Then, setup the Send to Mail Recipient properties. Set the Server Name to the SMTP gateway used for sending . For example, webmail.company_name.com or use the IP address of your SMTP mail server. Set the From field to who is sending this . You can use the RRTs of other components to dynamically set the values for From field. As an example, when your capture component is a POP3 and you like to have the processed file be sent back to the sender then set the From and the To field to ~POP::From~. This person would receive processed documents back by simply sending document to a POP3 account. Subject: and Body: are optional fields. The subject would be the same as any subject of an that you would want to send. For example, Corresponding documents would be such a subject. The body of the would be anything additional that you would want to add to the . Keep in mind that you can use RRTs of other components in any fields to create custom and dynamic values. There are no restrictions on the file input types of this component. Any file type can be processed through this component. Page 155

156 The Configuration of Send to Mail Recipient General tab Enter the Server and attributes SMTP Settings Enter the following SMTP Server attributes Field Name Server Test Port Requires Authentication Log on using NTLM Authentication Function Provide the server IP address or the host name of the SMTP server to which you will send your through. This is a required field. Click on the Test button to verify connectivity to the SMTP server IP address you entered. Enter the port number on which the SMTP service is listening. Check this option to perform authentication with SMTP server. User Name: The username used in conjunction with the password field when authenticating with the SMTP server. Password: The password used in conjunction with the username field when authenticating with the SMTP server. If unchecked then basic (clear text) authentication is used otherwise it will use integrated windows authentication. Page 156

157 Microsoft Exchange Settings Enter the following Microsoft Exchange Settings Field Name Server Test Mailbox Function Provide the server IP address or the host name of the Microsoft Exchange server to which you will send your through. This is a required field. Click on the Test button to verify connectivity to the Microsoft Exchange server IP address you entered. Enter the exchange mailbox that the will be sent out from. The mailbox name is normally the same as the NT user name. Note: If the Mailbox field is using RRTs to define dynamic Mailboxes, then it is recommend to use the username/password of an exchange administrator that has read/write access to all the exchange server mailboxes. User Name Password Domain Save copies of messages in Sent Item folder Enter the username used in conjunction with the password field when authenticating with the exchange server. The user should have access to the configured mailbox. Enter the password used in conjunction with the username field when authenticating with the exchange server. Use password encryption only with static passwords. If you are Note: using RRTs to define dynamic passwords, then the literal RRT string is encrypted. Enter the domain that the user name belongs to. If this option is checked, then a copy of message sent out will be kept in the sent items folder of the configured mailbox. Message tab Enter the message attributes here. Page 157

158 Field Name From To CC BCC Subject Body Function Specify the internet address of the sender. You must populate this field. Specify the internet address of the recipient of the . You must populate this field. Specify the internet address of the Cc recipient of the . This is an optional field. Specify the internet address of the Bcc recipient of the . This is an optional field. Specify the subject of the . This is an optional field. Provide a body and additional information for this This is an optional field. RRTs for Send To Mail Recipient This component does not generate Runtime Replacement Tags, however all the parameters can contain RRT strings. For example, when POP3 is the capture (source) component, the "To" parameter can be set to "~POP::To~". Page 158

159 Troubleshooting Tips / Restrictions and Limitations Problem Description This component is not sending . The s are rejected by the SMTP gateway server. The addresses entered in the To field are not validated. Non-compliant addresses could be used. Solution Make sure your sever name and the recipient s is correct. If you have multiple recipients, make sure they are separated by a semicolon. Make sure the SMTP relay parameter is turned on. Use the Notification Process component in your process. Using the Notification component allows you to require a user name and password so that you can prevent noncompliant addresses from being used. Restrictions and limitations With SMTP Server, Server Name, From are mandatory fields. Make sure to enter valid values for each of these fields. With Microsoft Exchange Server the Server Name, Mailbox, User Name, Password, Domain, From, and To are mandatory fields. Make sure to enter valid values for each of these fields. Send to Mail Recipient component does not validate addresses. Page 159

160 Send to PC Product Overview and Feature Highlights Send to PC is a Route (destination) component that can be used to deliver documents to a designated inbox on user PCs that are running the Send to PC client application. The Send to PC component maintains a list of NT user names for client PCs that are currently connected to the Server. When processing a job, the Send to PC component will be assigned a list of users that the documents with a job should be delivered to. The assigned list will be compared with the maintained list to determine the location of the document delivery. The user can specify a Secret Key on the Send to PC client application. This will prevent document delivery if the secret key for that user is not specified. This component provides Use this component to deliver documents to a designated inbox on a client PC. Deliver documents to one or more client PCs. Document delivery to designated client inboxes can be protected by defining a Secret Key on the Client application. Documents will only be delivered if the Secret Key has been provided. This component works independent of the type of Capture component used in the process. Using the Component Send to My PC: The Multi-functional Devices that have authentication enabled, can be configured with a Send to PC button, where by pressing this button, images are scanned in and then delivered to the authenticated users designated inbox. This will also alleviate extra load/stress on the mail server. Send to user workstation: Any user can now scan documents from an MFD and designate a user inbox for delivery. This allows the recipient to be anywhere within the network. The Configuration of Send to PC Field Name Send to Default Domain Function Enter a comma separated list of NT users that incoming documents should be delivered to. Domain name that will be attached to user names in the Send to list that are without a Page 160

161 Domain name. Connection Options For example if there is a user called JohnD on Domain US1, and the default domain is US1, either user name JohnD or US1\JohnD can be entered into this field. In this case the domain portion of the user name is not required. However, if there is a user JohnD on domain US2 as well, then the domain name and user name must be entered as US2\JohnD. You have the option of changing connection port settings: File Transmit Port: This port is used to deliver incoming documents to client PCs. The default value is set to Registration Port: This port is used by client PCs to register with this server component. The default value is set to Separator Note: If you are running the server and client components on the same machine, the File Transmit Port and Registration Port should be set to different values. The separator that is placed in between the user name and secret key. If secret keys are not being used, then entering the user name is sufficient. The secret key is an option on the Send to PC Client. If the Send to PC Clients have entered a value in the secret key input box, then, in order to send a document to that client s PC, the secret key would have to be provided in the Send To input box of the Send to PC server component. The way to separate the user name from the secret key is to use the separator character in between. It is recommended to use "@" character as the separator. Please refer to Component's RRT for an example. How to configure Send to PC Client Page 161

162 Field Name Server Test User Name Secret Key Automatically start when windows starts up Automatically connect at start-up Directory for files received Connect Disconnect Function The Send to PC server that will be delivering documents This button can be used to check the validity of the specified Send to PC server. The user currently logged on NT Domain\User name. The secret key that will protect your inbox. If a secret key has been defined then documents will be delivered to this inbox only if the appropriate key is provided. As a convenience, Send to PC client will start every time you turn on your computer. If you want to disable this feature, just remove the check mark next to this option. As a convenience, the Send to PC client will connect automatically to the defined Send to PC server at start-up. If you want to disable this feature, just remove the check mark next to this option. The directory where incoming documents will be saved to. The path can be directly typed into the field or a Browse key, to the right end of the field, helps search the hard disk. Click on this button to connect to the specified Send to PC server and register as client that is able to receive documents. Click on this button to disconnect from the Send to PC server. RRTs for Send to PC component This component does not generate Runtime Replacement Tags, however all the parameters can contain RRT strings. Troubleshooting Tips / Restrictions and Limitations Problem Description Client cannot connect to a running send to PC server Solution Do the client and server computers have Microsoft TCP/IP installed? If not, install the TCP/IP protocol. Check to make sure that client computer can ping the server computer (via IP address) ping <server_ip_address> If there is no reply, then probably your computer is configured incorrectly or there is a problem with the physical network connection of your computer. Check to make sure that the Registration and File Transmit ports on the server and client match. By default the port(s) are set to Also, make sure that the ports are not blocked by a firewall. You can check by using telnet at the command prompt to connect to the port Restrictions and limitations Document metadata will not be delivered to the client s PC. Documents will not be delivered to NT groups. The client directory for received files cannot be dynamically set/changed at runtime. If the user is logged in to 2 different PC's at the same time, the documents will be delivered to the PC that the user logged into last. Page 162

163 Send to Printer Product Overview and Feature Highlights Use the Send-to-Printer component to send scanned images directly to a printer. This component also allows you to select the printer size, source, and zoom level. All print drivers for each printer must be installed and configured on the server. Use the Send-to-Printer component to define and designate a printer as the destination for images that are sent to the server. This component enables the Multi-functional devices to define copying function keys that scan documents and automatically send them to a defined printer location. Send to printer provides batch printing of commonly used image files formats such as TIFF and JPEG. It also allows the user to print PDF format by acquiring a special license. With this component you can print documents to any printer that is configured in the machine where the system is running. The system can also switch between printers based on the name or the extension of the document filename. Send to Print can be used both as a Process component or Route component in a process workflow, depending on the needs of the user. This component uses Lead Technologies to manipulate different file formats without using any native application in the service machine. The printing process is achieved by using the printer drivers installed in the service machine, because of this you must setup previous to configuring the process any printers that you want the component to use. This component provides: Many business processes that deal with image documents incorporate printing as part of their workflow. The Send to Printer component provides the means to satisfy many of the printing needs in a document management environment. Whether obtaining a printed version of a document is the final goal of the process, or the system relies on printed versions as an alternate source of information for users, the Send to Printer component can be used to accommodate many scenarios where unattended printing will be necessary. The Send to Printer configuration only allows you to specify parameters that are common to most print drivers, such as Paper size, Printer name, Pages per sheet, Number of Copies, and Orientation. Other parameters that are specific to a printer must be set in the local printer configuration. Using the Component To use this component the user must first decide whether sending to a printer will be the final step of the workflow or an intermediate one. This will define if Send to Printer is used in the configuration as a Process component or as a Route component. Use the Send-to-Printer component to accomplish these tasks: Remote Copy: Scan files and route them to a remote printer. File type based printing: Scan files and send them to printers according to file types Colour Copy: Scan in colour and send the images to a colour printer Print broadcast: Create process chains with Poll Directory Capture component and Send to Printer Route component to broadcast multiple copies of document to multiple printers. Special Printer Features: The automatic stapling, and other specific features of a printer, can be done by creating a copy of the printer driver which has the stapling option on by default and using this specific driver. Printing confirmation page: Use File Options within your workflow process to store documents into a "Success" or "Failure" directory. If you want confirmation page to be printer on success or failure, use Poll Directory with Send to Printer to route files from Success or Failure Directory to a printer. Page 163

164 The Configuration of Send to Printer Field Name Activate Keep Printer Name Paper Number of copies Orientation Zoom Add Remove Function Activates the Send-to-Printer component to send images to the printer. This option is only available when Send to Printer Process component (not Route component) is used. Check this box to keep the original file and not delete it. Select the printer name from the drop-down list of configured printers on the server. Enter the paper size. The values that appear in the drop-down list depend on the model of the printer selected. Paper Source indicates the paper source based on available paper sources on the printer driver. If you click the Auto Select option, the printer uses the paper tray that supports the paper size you have selected. If you choose a paper source other than Automatically Select, make sure that the correct form (paper size) is assigned to the paper source. Enter the number of copies you want to print. To print a complete copy of the document before the first page of the next copy is printed, select the Collate check box. If you prefer to print all copies of the first page and then print all copies of subsequent pages, clear the check box. Choose here how the document will be oriented on the page. If you choose Portrait, the document will be oriented vertically and if you choose Landscape, the document will be oriented horizontally. Specifies the number of pages that appears on each printer page. Adds a printer tab for a defined file extension. All files that include the file extension are routed to the printer defined here rather than to the printers defined in General tab. Deletes the selected tab (except the General tab). Page 164

165 RRTs for Send to Printer component This component does not generate Runtime Replacement Tags, however all the parameters can contain RRT strings. Troubleshooting Tips / Restrictions and Limitations Problem Description Server stops processing when trying to print document. An error occurs when trying to print a PDF file, even though the system is licensed for PDF printing. Solution The print driver is trying to get interactive information. Make sure your printer configuration does not request any information from the user. For example if your printer keeps a copy of the printing job, make sure the printer does not need to ask the name of the file, but this is generated by the printer driver. If you are using the system as a service any kind of interactive actions will cause the service to stop until a response is given. Note that for the case that you are using the interactive version of the system it might be desirable that the printer request additional information from the user. The PDF format you are trying to use is not supported. If the application that generates the PDF document can generate one of the PDF supported formats, use this instead if your business process allows it. Restrictions and limitations Only non-interactive printer drivers are supported. The supported file formats for Send to Printer are: JPEG Formats JPEG File Interchange Format Tagged Image File with JPEG compression JPEG 2000 Format. This file format contains image data and extra information about the contents and organization of the file. GIF Formats CompuServe GIF TIFF Formats Tagged Image File Format, with no compression and with RGB colour space and 8-bit greyscale. Tagged Image File, with no compression and with CMYK colour space. Tagged Image File, with no compression and with YCbCr colour space. Tagged Image File with PackBits Compression and RGB colour space. Tagged Image File with PackBits Compression and CMYK colour space. Tagged Image File with PackBits Compression and colour YCbCr space. Tagged Image File with CMP Compression. Tagged Image File with JBIG Compression. Tagged Image File with a vector image saved as a DXF Tagged Image File with JPEG 2000 Compression. This file format contains only a stream of image data. Tagged Image File with Wavelet CMP Compression. BMP Formats Windows BMP, with no compression. Page 165

166 Windows BMP, with RLE compression. OS/2 BMP version 1.x. OS/2 BMP version 2.x. Wireless Bitmap file. Type 0. WMF and EMF Formats Windows Meta File Windows Enhanced MetaFile Exif Formats Exif file containing a TIFF image, with no compression and with RGB colour space. Exif file containing a TIFF image, with no compression and with YCbCr colour space. Exif file containing a JPEG compressed image 1-Bit FAX Formats TIFF, compressed using CCITT. TIFF, compressed using CCITT, group 3, 1 dimension. TIFF, compressed using CCITT, group 3, 2 dimensions. TIFF, compressed using CCITT, group 4. Raw FAX, compressed using CCITT group 3, 1 dimension. Raw FAX, compressed using CCITT group 3, 2 dimensions. Raw FAX, compressed using CCITT group 4. IOCA, compressed using CCITT group 3, 1 dimension. IOCA, compressed using CCITT group 3, 2 dimensions. IOCA, compressed using CCITT group 4. IOCA, compressed using IBM MMR, with the MO:DCA wrapper. IOCA, uncompressed, with the MO:DCA wrapper. Other 1-Bit Formats MacPaint. Portable Bitmap - ASCII File. Portable Bitmap - Binary File. XBitmap File. Microsoft Paint. Page 166

167 Send to SFTP Product Overview and Feature Highlights The Send to SFTP component provides you with the mechanism for storing files that are fed from a capture component to the SFTP site for storage. Additional control over the SFTP site transmission is provided through support for secured FTP sites as well as bandwidth flow-control. Design your process according to your business process, such that a client may open the SFTP session to this server for document retrieval, etc. as required by the business process. Send to SFTP component provides the following features: Allow configuration of multiple SFTP sites. Use SFTP (Secure File Transfer Protocol) protocol. Dynamic file renaming and storage support. Active flow control. Using the Component The following are examples of how this component may be used: An enterprise where PDF documents from several sources have to be placed on several SFTP servers. These documents may then be processed for printing, or sending out as , depending on the business need. Connectivity of remote offices to central office can easily be implemented using SFTP component. Scanners from remote sites can easily be connected to multiple sites using a secured FTP protocol. Control the bandwidth usage when connecting remote scanning offices through use of the Bandwidth control feature of SFTP component. Bandwidth control lowers the impact of implementing distributed scanning on transmission infrastructure. The Configuration of Send to SFTP Main Window In the main window you can create new SFTP-sites, edit or remove the existing SFTP-sites. Add Press "Add button" to add a new SFTP-site into the list. It opens "Site Configuration" dialog. Edit Select a site from the list and press "Edit" button to change its settings. It opens "Site Configuration" dialog. Page 167

168 Remove Select a site or several sites in the list and press "Remove" button to remove them. Site Configuration In this tab you can specify SFTP-site configuration. Site name Enter the name of SFTP-site. Server address Enter the IP address or the server name of the SFTP-site. It is obligatory to fill this field. User name Enter the user name of the client who will have access rights to the SFTP-site. After you specify the user name, specify the password that is associated with this user. It is obligatory to fill this field. Password Enter the password that is associated with the user name. It is obligatory to fill this field. Destination folder path Input the folder where the documents will be stored on the SFTP-server. If you specify a new folder in this field, a new folder with the same name is created on the SFTP-server. However, if you do not specify a path or folder name, the data is stored in the root directory of the SFTP-server. Overwrite destination path Switch on this option if you want the newly created files on the SFTP site to overwrite the existing files that have the same name. If you do not select this option, the file will not be overwritten, and respective error message will appear in WorkFlow processor. Rename file Switch on this option if you want the output file to be renamed. The field Schema becomes enabled. Schema Enter the schema name for the output file name. You can use Runtime Replacement Tags (RRT) to dynamically set the value of the schema. Advanced Press "Advanced" button to test. It opens "Advanced" dialog. Page 168

169 Advanced Activate flow control Switch this option on to activate the flow control options: Transfer rate (milliseconds) Use this knob to set your desired transfer intervals in Milliseconds. The longer the interval the slower the transmission rate. Buffer size (bytes) Use this knob to set the size of each transmitted buffer. The larger the buffer size the higher the transmission rate and the larger impact on the bandwidth. Run test Press "Run Test" button to begin test. The test will be conducted against your SFTP-site. Make sure you have specified a correct server name, user name and password. The tests are conducted using 100Kbytes buffers. At the end of the test the results are reported in 100 Kbytes/X Seconds where X is the number of seconds required for sending 100 Kbytes. The size of regular B/W documents is between 25 to 50 Kbytes. You can always stop test by pressing "Stop" button. Then the results are reported in Y Kbytes/Z seconds, where Y is the number of Kbytes which the test has been able to process; Z is the number of seconds taken to send Y Kbytes. Stop Use the "Stop" button to terminate test buffer. Test result This field displays the progress of the test. NOTE: To use the test feature, you must have access to the SFTP-site(s) from your machine. This feature establishes connection to the SFTP-site and transmits "dummy data to the SFTP-site to test transmission bandwidth. RRTs for Send to SFTP Component RRT ID The RRT ID for the component is SFP. Reserved Replacement Tag Names (RRTN) The following table describes the reserved RTN values for Schema field of this component. Name FileName Counter FileExt Description The original file name value. An incremental counter based on the duplicate file names found within a directory. The counter value concatenated with a name provides a unique file name. Original file extension value Page 169

170 The following example provides some sample usage for your reference: ~SFP::FileName~~SFP::Counter~ - replaced with the value Document5 if the original file name was Document and there were up to 4 (Document1 to Document4) files already within the destination folder path. NOTE: The Reserved RTN values FileName, Counter, FileExt can only be used with the Rename field of this component. In other words, you may not use ~FTP::FileName~, ~FTP::Counter~, ~FTP::FileExt~ in any other component but Send to FTP and it must be used with the Rename field of this component only. NOTE: You can use the C format specifiers to create and display the counter with the required number of leading spaces or leading zeros. For example, if the file name is Test.doc, and the rename schema is ~FTP::FileName ~~%03FTP::Counter~~FTP::FileExt~, the resulting file names are Test001.doc, Test002, etc.. If the file name is Test.doc and the rename schema is ~FTP::FileName~~%3FTP::Counter~~FTP::FileExt~, the resulting file names are Test 1.doc, Test 2.doc, etc.(note the 2 spaces after "Test"). Field Replacement Tag Names (FRTN) This component does not have any FRTNs and replacement of field names with metadata values. Special Set Replacement Tag Names (SSRTN) This component supports the Date/Time tag names listed below: SSRTN Description %d Day of month as decimal number (01 31) %j Day of year as decimal number ( ) %I Hour in 12-hour format (01 12) %H Hour in 24-hour format (00 23) %p Current locale s A.M./P.M. indicator for -hour clock %M Minute as decimal number (00 59) %m Month as decimal number (01-12) %b Abbreviated month name %B Full month name %S Second as decimal number (00 59) %U Week of year as decimal number, with Sunday as first day of week (00 53) %w Weekday as decimal number (0 6; Sunday is 0) %W Week of year as decimal number, with Monday as first day of week (00 53) %a Abbreviated weekday name %A Full weekday name %y Year without century, as decimal number (00 99) %Y Year with century, as decimal number Examples usage of the above SSRTN include: ~SFP::%Y~-~SFP::%m~ will be replaced by Troubleshooting Tips / Restrictions and Limitations SFTP service uses default port. Non-standard settings of SFTP service are not supported. Problem Description Solution Files cannot be copied into the Make sure that the destination folder has Write access. destination directory. Check username/password to make sure it is valid. Check the access rights for the user. Check to make sure there are no firewalls. If overwrite existing is not checked off, make sure that a file with the same name does not exist yet. Page 170

171 SharePoint 2007 Product Overview - Feature Highlights SharePoint 2007 component is used to route documents and list items, e.g. tasks or issues to Microsoft SharePoint. The component allows assigning necessary properties to the sent files and setting access rights to the routed documents and list items. The only difference between SharePoint 2007 Route and SharePoint 2007 Process component is that SharePoint 2007 Process component has two additional options in the General tab: Activate check box, which allows to store captured document into SharePoint 2007 server, if selected. If this check box is not selected, the component won't perform any actions during files processing. Pass-through check box, which makes the document(s) available to the downstream components, if selected. These two options are absent in SharePoint 2007 Route component configuration. The component was designed for using with Microsoft Office SharePoint Server 2007 and Windows SharePoint Services 3.0, each one further referred to as SharePoint 2007 Server. Note: The component has a server module which represents a web service running on SharePoint 2007 Server. To properly connect to a remote SharePoint 2007 Server from a client machine, the user has to install this web service on the SharePoint 2007 Server machine. The component provides you with the following features: Provide general SharePoint 2007 Server information to specify where to route documents into: Server, User name, Password, Site, Document Library, Folder Path. Create list items and add them to the specified list of SharePoint 2007 Server. Add properties or fields to the routed documents and list items. Provide user with permissions i.e. access rights to the routed documents and list items. Rename the routed document with the schema name by using RRTs. Overwrite documents with the same name. A routed document is written to the specified path as a new version of the existing document with the same name, if this functionality is set for the specified document library. Overwrite list items with the same field values of the fields, which are indicated as key fields. Using This Component Use this component to store documents into a centralized, unified interface for enterprise users and highly flexible deployment options. The use cases below provide a sample of the component application: Scan documents from an MFP device, save directly into a folder within SharePoint 2007 Server: Design a workflow process with MFP component corresponding to the selected type of MFP device and SharePoint 2007 Route component. Configure SharePoint 2007 Route component to route the scanned documents into SharePoint folder with assigning of the properties, that uniquely identify the document. Configure both components and start the server. Now when the walk-up MFP user enters a pre-configured function key on the control panel of the MFP device, the scanned document with the configured properties is routed directly into SharePoint 2007 Server. Send s directly into SharePoint 2007 Server: Design a workflow process with SMTP Capture component, SharePoint 2007 Process component and Send to Folder Route component. Select the Activate check box in SharePoint 2007 Process configuration. Configure all 3 components and start the server. Now all incoming s sent to an SMTP gateway are i) saved into a pre-configured folder on the SharePoint 2007 Server for archival, management or sharing and ii) routed to the desired folder on the computer or network folder according to Send to Folder configuration. You also can configure SharePoint 2007 Process component to route list items with some information to take stock of s on the server. Building a Process With SharePoint 2007 The component configuration window consists of three tabs: Page 171

172 General tab - Set general connection parameters to log in to SharePoint2007 Server. Documents tab - Specify the parameters of the routed documents. List Items tab - Create list items which you want to send to SharePoint 2007 Server and specify their parameters. General tab In the General tab you can set general connection parameters to log in to SharePoint 2007 Server. Activate - this check box is present only in process component configuration window. Select this check box if you want to store captured document into SharePoint 2007 Server, before further processing by the downstream components. If this box is not checked, the component won't perform any actions during files processing. Pass-through - this check box is present only in process component configuration window. Select this check box if you want the document(s) to be available to the rest of the components in your process. Connection group allows to specify parameters to log in to SharePoint2007 Server: Server address - enter the path to the SharePoint 2007 Server where you will be storing the documents or list items. This field can contain " or " followed by server name or IP address. For example, or Alternatively, it can contain only server address, e.g. sp in this case the component will insert " before it automatically. It is mandatory to fill out this field. User name - enter the user name which will be used to log in to the server. If you are using a domain user account to connect to SharePoint 2007, enter the user name with the domain name, e.g. ORGDOMAIN\SpUser. The local server users can enter only the user name, e.g. SpUser. It is mandatory to fill out this field. User password - enter the user password which will be used to log in to the server. Site - enter the name of the SharePoint site where you want to store the documents or list items either manually or select from the drop-down list. You can specify a subsite of the site entering its name after the parent site name followed by "/", e.g. SubSite1/SubSite1_1. If a site is not specified, the component will store documents or list items in the base SharePoint directory. Page 172

173 Documents tab In the Documents tab you can specify the parameters of the routed documents. Route Documents - select this check box if documents routing is planned. If this check box is not selected, the component won't route any documents. Document library - enter the name of the document library that you want to work in either manually or select from the drop-down list. If the specified library does not exist on the server, the configuration can be saved, however in runtime the error message will occur. It is mandatory to fill out this field. Folder path - enter the name of the folder where the routed files will be stored either manually or browse to the desired folder using (...) button. The button opens the Select Folder dialog box. Select Folder This dialog box displays the folders of the selected document library as a tree. Select the folder where routed documents will be stored and click OK. You can create a folder dynamically by entering a new name for the folder. You can also create a subfolder of the existing folder by entering the subfolder name after the folder name followed by "/", e.g. Folder1/ New folder. You can use one or several available RRTs to create folder names. Note: You cannot use ~SPS::Counter~ to dynamically set folder names. Page 173

174 Rename schema - select this check box if you want to rename a routed document. In order to do this enter the schema for the output file name in the field next to this check box. You can use one or several available RRTs to dynamically set the value of the schema. If this check box is not selected, the routed file will keep its original name. If this check box is selected, however a rename schema is not specified, then at runtime the Schema name defaults to: ~SPS::FileName~_~SPS::Counter~~SPS::FileExt~. For example, if the input file name is File.tif, the renamed file will be File_1.tif. Check in comment - this field is enabled only if Check in option is selected. Enter a comment to the document which you are checking in. You can use one or several available RRTs in this field. Note: You cannot use ~SPS::Counter~ to create check in comment. Check in - if you select this check box, other users will see the document changes. Overwrite - if you select this check box, a routed document replaces the existing document with the same name in the specified path as a new version. In other words, the version of a routed document will be increased by 1.0 in comparison with the version of the existing document having the same name. However, if a document with the same name does not exist in the specified path, the version of the new routed document will be set to 1.0. Note: Creation of a new version is possible only if this functionality is set for the specified document library. Otherwise, the routed document will simply replace the existing document of the same name. If the Overwrite check box is not selected, and a document with the same name exists in the specified path, the routed document will be rejected. Permissions - click this button to set the permissions, i.e. access rights which users or groups will have. The Permissions Settings dialog box will open. Fields group allows assigning properties or fields to the routed document. Add - click this button to add a new field to the fields list. The Add Field dialog box will open. Edit - click this button to edit properties of the selected field from the list. The Edit Field dialog box will open. Remove - select one or several fields and click this button to remove the selected field(s) from the list. Note: Permissions Settings Each document library has its own specific set of fields. If this folder requires a set of mandatory fields, these fields will be assigned to the document anyway. If the user has not specified the values of mandatory fields, they will be set to default values specific to the folder. In this dialog you can indicate users or groups that can access routed document for different needs. The dialog window displays the current list of permissions given to users or user groups. Type column displays one of two alternatives: User or Group. User Name column displays the name of corresponding user or group. Permissions column displays access right, the corresponding user or group has. Inherit permissions from its parent folder or library - if this check box is selected, the document will inherit permissions from its parent folder or library. In this case, the buttons on the right side of this dialog are disabled. If this check box is not selected, the buttons are enabled. Add - click this button to add a new permission to the permissions list. The Add Permission dialog will open. Page 174

175 Edit - click this button to edit the properties of the selected permission. The Edit Permission dialog will open. Delete - select one or several permissions and click this button to remove the selected permission(s) from the list. Restore - click this button to return to the previous list of permissions. Add/Edit Permission In this dialog you can add a new permission to the permissions list or edit the properties of the selected permission. Type - click one of two option buttons: User or Group in order to choose, who will have a permission: a user or a group. Name - enter the name of the user or the group which will have a permission. If you choose the User type, you can enter the user name in one of the following forms: Login name, e.g. mydomaincom\johns or johns Display name, e.g. John Smith , e.g. johns@mydomain.com and click the button next to this field to make the component attempt to validate the specified user. The component searches the user in the SharePoint2007 user list, and if the user is not found, searches it in the domain users list. If the validation is successful, the user name is displayed in the Name field in the form of display name. If the validation fails, the following message occurs in the lower part of the dialog: "User name could not be resolved". If you choose the Group type, you can enter the group name manually or select using (...) button next to this field. This button opens the Select Name dialog. Permissions - enter a permission to corresponding user or group either manually or select from the drop-down list. Notes - enter a comment to the permission. If you choose the Group type, this field contains the description of the selected group, on default. Select Name In this dialog you can select the group which will have a permission. Name - enter name manually or select from the drop-down list of the SharePoint groups. Add/Edit Field In this dialog you can add a new field to the fields list or edit the properties of the selected field. Each document library has its own specific set of fields. You may add any field from this set. If this folder requires a set of mandatory fields, Page 175

176 these fields will be assigned to the document anyway. If the user has not specified the values of mandatory fields, they will be set to the default values specific to the folder. Name - enter field name either manually or select from the drop-down list of the fields specific to the document library. The names of the mandatory fields are marked off with *. Note: You can enter any custom field name, but if the entered name is not specific to this document library, the document will not be routed and the error message will occur. Value - enter field value either manually or select from the drop-down list of the values specific to this field. Note: If the specified field points to a user, you can enter the value of this field in one of the the following forms: Login name, e.g. mydomaincom\johns or johns Display name, e.g. John Smith , e.g. johns@mydomain.com If the specified field points to a date, you can enter the value of this field in one of the server locale supported date formats, e.g or Jun, 20, If the specified field points to a hyperlink, you can enter the value of this field in one of the following forms: < or < [ or [ or You can use one or several available RRTs to create field values. Note: You cannot use ~SPS::Counter~ to dynamically set the value of the schema. List Items tab In the List Items tab you can create list items which you want to add to a list of SharePoint 2007 Server and specify their parameters. List item is specified as a set of fields and their values. Page 176

177 Route list items - select this check box if list items routing is planned. If this box is not checked, the component won't route any list items. List - enter the name of the list of the specified server where the routed list items will be stored manually or select from the drop-down list. If the specified list does not exist on the server, the configuration can be saved, however in runtime the error message will occur. It is mandatory to fill out this field. Overwrite - if this check box is selected, existing list items are automatically replaced by the items with the same values of key fields, when new items are added to the specified path. The fields can be indicated as key fields with the use of the Search keys button, which becomes enabled. If this check box is not selected, newly created list item will be placed in the specified path without any update operations. In other words, if a list item with the same field values already exists in the specified path, a new instance will be created. There will be two list items with the same field values in the specified path. Search keys - this button is enabled only when the Overwrite check box is selected. Click this button to indicate particular list item fields as key fields. The Search Keys dialog box will open. Note: If you use the Overwrite option and specify a particular list item field as key field, this field should be added to the Fields list for correct replacement. Permissions - click this button to set the permissions, i.e. access rights, which users or groups will have. The Permissions Settings dialog box will open. Fields group allows assigning properties or fields to the routed list items. Add - click this button to add a new field to the fields list. The Add Field dialog box will open. Edit - click this button to edit properties of the selected field from the list. The Edit Field dialog box will open. Remove - select one or several fields and click this button to remove the selected field(s) from the list. Note: Each list has its own specific set of fields. If this list requires a set of mandatory fields, these fields will be assigned to the list item anyway. If the user has not specified the values of mandatory fields, they will be set to default values specific to the list. If you use the Overwrite option and want some list item fields to be replaced by the new values, you should add these fields to the Fields list for correct replacement, even if these fields are mandatory. Search Keys In this dialog box you can indicate particular list item fields as key fields. The component will compare existing list items of the specified list with the routed list item. To do this, it will compare the field values of the specified key fields of the routed list item with the values of the same fields of the list items existing in the specified list. List items search keys group contains a list of key fields and the buttons for managing this list. Add - click the button to add a new key field to the list. The Add Search Key dialog box will open. Delete - select one or several key field(s) and click this button to delete the selected key field(s) from the list. Add Search Key Page 177

178 Use this dialog box to add a new key field to the key fields list. Key name - enter name of a key field either manually or select from the drop-down list of fields. The names of the mandatory fields are marked off with *. RRTs for SharePoint 2007 Component RRT ID The RRT ID for this component is SPS. Reserved Replacement Tag Names (RRTN) The following table describes the reserved RTN values for this component. Name FileName Counter FileExt Description The original file name value. An incremental counter based on the duplicate file names found within a directory. The counter value concatenated with a name provides a unique file name. Original file extension value. DocumentURL URL of the document stored in SharePoint 2007 ListItemURL URL of the list item stored in SharePoint 2007 Examples of usage of the above RRTN include: ~SPS::FileName~~SPS::Counter~ is replaced with the filename created by using SharePoint 2007 component. Field Replacement Tag Names (FRTN) This component does not have any FRTNs. Special Set Replacement Tag Names (SSRTN) This component supports the Date/Time tag names listed below: Name Description %a Abbreviated weekday name %A Full weekday name %b Abbreviated month name %B Full month name %d Day of month as decimal number (01-31) %H Hour in 24-hour format (00-23) %I Hour in 12-hour format (01-12) %j Day of year as decimal number ( ) %m Month as decimal number (01-12) %M Minute as decimal number (00-59) %p Current locale's A.M./P.M. indicator for -hour clock %S Second as decimal number (00-59) %U Week of year as decimal number, with Sunday as first day of week (00-53) %w Weekday as decimal number (0-6; Sunday is 0) Page 178

179 %W Week of year as decimal number, with Monday as first day of week (00-53) %y Year without century, as decimal number (00-99) %Y Year with century as decimal number Examples of usage of the above SSRTN include: ~SPS::%Y~-~SPS::%m~ will be replaced by Note: ~SPS::Counter~ can be used only in Rename Schema field. Do not use ~SPS::DocumentURL~ and ~SPS::ListItemURL~ in Rename Schema field and Folder path field, because the values of those RRTs contain backslashes and if you choose to use any of those RRTs in any of those fields, it would create an error as no file name or folder name can contain a backslash. When using SharePoint 2007 Process component, do not use ~SPS::DocumentURL~ and ~SPS::ListItemURL~ RRTs in subsequent component's Rename Schemas. This is because the values of those RRTs contain backslashes and if you choose to use any of those RRTs as part of a Rename Schema, it would create an error as no file name can contain a backslash. Troubleshooting Tips / Restrictions and Limitations Problem description The list of SharePoint sites is not visible for selection in the Site field of the General tab. The Status Monitor shows the following mesage: "Cannot connect to #Server#. Check site name and login settings.", where #Server# is the specified Server address. A document is not sent to the server. The Status Monitor shows the following message: "Document library #Libraryname# could not be found", where #Libraryname# is the specified name of the Document library. A list item is not sent to the server. The Status Monitor shows the following message: "List #Listname# could not be found", where #Listname# is the specified name of the List. A document is not sent to the server. The Status Monitor shows the following message: "Field #Fieldname# could not be found", where #Fieldname# is a name of an added field. A list item is not added to a list on the server. The Status Monitor shows the following message:"list item is not created. Value does not fall within the expected range.". A document or a list item is not sent to the server and the Status Monitor shows one of the following error messages: 1. "The request failed with HTTP status 503: Service Unavailable." Solution Probably the component cannot connect to SharePoint 2007 Server. Make sure that you have entered correct connection parameters. If they are correct, check if the user has sufficient access rights to the SharePoint 2007 server. Contact your server administrator. Probably the component cannot connect to SharePoint 2007 Server. Make sure that you have entered correct connection parameters. If they are correct, check if the user has sufficient access rights to the SharePoint 2007 server. Contact your server administrator. Probably you have specified a non-existent library in the Document library.field. Specify the correct library name. Probably you have specified a non-existent list in the List field. Specify the correct list name. Each document library has its own specific set of fields, and you may specify only the fields from this set. Probably #Fieldname# field does not belong to the set of specified fields. Remove this field from the component configuration. Each list has its own specific set of fields, and you may specify only the fields from this set. Probably some field does not belong to the set of specified fields. Remove this field from the component configuration. These messages are concerned with SharePoint 2007 server failure. Try again later or contact your server administrator. Page 179

180 2. "The underlying connection was closed: An unexpected error occurred on a receive." 3. "The server committed a protocol violation. Section=ResponseHeader Detail=Header name is invalid at System.Net.HttpWebRequest.GetResponse()". When you enter " followed by server name, e.g. in Server address field, a document is not routed and the Status Monitor shows the following error message: "Request Entity Too Large. at System.Net.HttpWebRequest.GetResponse() at WSS3Gateway.CWSS3Gateway.SendRequest(String suser, String spassword, String sdomain, String uri, Byte[] postbody, Int64 postlength)". Status Monitor shows the correct component work, but the routed document or list item is not visible on the SharePoint site. The reason of this problem is concerned with SSL settings on the server. Do one of the following: 1. Enter " followed by IP address, e.g. in Server address field. 2. Make a request to your server administrator to check on the "Ignore user certificates" option. Probably the user has not sufficient access rights to the SharePoint 2007 server. Contact your server administrator. Restrictions and limitations There may be instability while working with the files of big size. The maximal limit is near Mb and it depends on parameters of a computer and the SharePoint limitation. Page 180

181 SharePoint Portal TM 2003 Product Overview and Feature Highlights Use this component is to store documents into a centralized, unified interface for enterprise users and highly flexible deployment options. This component allows the process to use the SharePoint Portal Server (SPS) for document management. The only difference between SharePoint Portal 2003 Route and SharePoint Portal 2003 Process component is that SharePoint Portal 2003 process has one additional field in the field values tab (pass-through) which is not available for the Route component. With the latest version of the SharePoint 2003 Component,.NET does not need to be installed on the machine that is running the Server. This component provides: Provide the general SharePoint Portal information (Server, User name, Password, Domain, Site, Document Library, Folder Path) to specify where to insert the files into. If there are multiple files of the same name, you may rename the file with a schema name. If a file name has already been used, a counter is appended to the file name. For example, if the file s original name was test.txt, the rename schema can rename the files to test1.txt, test2.txt, test3.txt for any reoccurrences of test.txt. You can change document attributes by selecting Add button and under the Field Values dialog box, you can select the Title of the document, and place a new value for it. Using the Component In a process, the SharePoint Portal 2003 component is frequently used with the Digital Sender component and the Poll Directory component. In this type of process, SharePoint 2003 component picks up files and stores them in Microsoft SharePoint Portal 2003 Server. If a file is stored in a folder that you want to share with the rest of the enterprise, you can create a process that uses Poll Directory as the capture component. Save the file that you want to share in a designated Input folder, and then use SharePoint Portal 2003 as the Route component. You can only use this process component when the route component in your process can accept field values (such as Lotus Notes, ODBC, and so on). Note: To properly connect to a remote SharePoint Portal server from a client machine, the user has to run SP2003WebServiceSetup.msi file located in the WebService Installation folder on the SharePoint server. In order to do this, the user should locate the WebService Installation folder in the AutoStore directory on the client machine, copy it to the machine running SharePoint server, and run the setup file. Page 181

182 The Configuration of SharePoint Portal 2003 General tab Field Name Function Server When you add the SharePoint Portal 2003 component, you need to choose the SharePoint server where you will be storing the documents. User Name Enter a valid login into SharePoint Portal Password Domain Site NOTE: If the user name entered is not an administrator on the SharePoint machine, SharePoint will not allow the user to log on. Enter a corresponding password for the User Name that you entered. Enter the domain that SharePoint Portal 2003 is running on. Sites Directory is where you can create various sites to store your documents in. Choose the site where you want to store your information, and then select the Document Library you want to work in. If a site is not specified, and the user decides to browse for a document library, the document libraries in the base SharePoint directory (root directory) will be shown. Therefore, a site is not required, although a document library is still required. Document Library When using the SharePoint Services 2003 you can browse the sites by clicking onto the 3 ellipses (they are referenced as site-name ). When using a SharePoint Portal Server you have to enter the name manually (the reference is site-names ) Select the Document Library that you want to work in. Document libraries can have document libraries within them. Therefore, when you hit the browse button for Page 182

183 Document Library, you are presented with a tree view of document libraries within document libraries. In SharePoint you can have infinite document libraries inside document libraries, as long as your computer has space to support it. The user has to select a work site with the icon in order for the OK button to be enabled. This is because you can only store documents within the Work site, which is a child Document Library. Folder Path After you select the Document Library, you would need to select the Folder Path of the Document Library. Enter the Folder Path of the Document Library. Folders can have multiple folders within them, just like any folder you create on your computer. The OK button is always enabled as long as you select any folder. The folder you want to store the file in can have other folders in it. You can create a folder dynamically by entering a new name for the folder. Rename Rename Schema If a folder path is not specified, it will store it in the root directory of the document library. You can rename the file that is coming in to the SharePoint Portal component. You can choose to Rename Schema by checking this box. Enter the Schema name. Please refer to the component's RRT to learn about the replacement tags for this component. If the Rename Schema field is left blank, this field will be set to ~SPS::FileName~~SPS::Counter~~SPS::FileExt~. Overwrite Pass-through For example if the Rename radio button is selected but the Rename Schema field is left blank, and the file test.doc was processed through this component, the rename schema will change the name of the file to, test1.doc. If the rename schema is not used, this field will determine whether or not a file that already exists in SharePoint with the same name will be overwritten or not. If this box is not checked, the process will fail to store a document with the same name. If this box is checked, this component will pass the document to the next component in the process. This is only valid for SharePoint Portal 2003 econnector (process) component. Page 183

184 Columns tab Field Name Add Function You can add new field names and field values to the file that is being stored in SharePoint Portal. You can add fields such as the title of the file, or any other fields that you need. Click on Add button and the Field Values dialog box appears. The browse button next to the Name field opens up the Select Field dialog box. Select the fields that you want to add to your file. These fields are subject to change depending on which Document Library you choose. Each document library has its own specific set of fields. The field types that are currently supported are: Text, Number, Boolean, Currency, and Note (i.e. multiple lines of text). Modify Remove All field types are supported. Click on Modify button to modify the field value attributes. Click on Remove button to remove a field value. RRTs of Microsoft SharePoint 2003 component The RRT ID for this component is SPS. Reserved Replacement Tag Names (RRTN) Name FileName Counter FileExt Path Description The original file name value. An incremental counter based on the duplicate file names found within a directory. The counter value concatenated with a name provides a unique file name. Original file extension value The folder path entry. For example, if you have configured 3 folder paths, then this RRTN can take the following values: Path1, Path2, Path3. Path1 refers to the first path entry configured, Path2 refers to the 2nd path entry configured, etc.. Page 184

185 The following example provides sample usage for your reference: ~SPS::FileName~~SPS::Counter~ is replaced with the filename created using SharePoint 2003 ~SPS::SPSURL~ (Where SPSURL is the field name designated for the SharePoint to store URL references into)for SharePoint Portal process component, is replaced with the URL of the document Field Replacement Tag Names (FRTN) This component does not have any FRTNs and replacement of field names with metadata values. Special Set Replacement Tag Names (SSRTN) This component does not have any SSRTNs. Troubleshooting Tips / Restrictions and Limitations Problem Description Cannot run the component. Cannot locate documents that you stored in "Forms" folder. Solution To properly connect to a remote SharePoint Portal server from a client machine, the user has to run SP2003WebServiceSetup.msi file located in the WebService Installation folder on the SharePoint server. In order to do this, the user should locate the WebService Installation folder in the AutoStore directory on the client machine, copy it to the machine running SharePoint server, and run the setup file. Avoid storing documents into "Forms" folder, instead create a new folder and store the documents in the newly created folder. Restrictions and limitations It is not recommended to store documents into "Forms" folder, instead create a new folder and store the documents in the newly created folder. For "Currency", only valid numbers, with no $ or any other characters are valid. If the user name entered is not an administrator on the SharePoint machine, SharePoint will not allow the user to log on. If the Rename radio button is enabled, and the Rename Schema field is left blank, this field will be set to ~SPS::FileName~~SPS::Counter~~SPS::FileExt~ With SharePoint 2003 process component do not use RRT ~SPS::URL~ in subsequent component's Rename Schemas. For example if your process contains SPS2003 process component and a Folder Store route component, you cannot use the ~SPS::URL~ in the Rename Schema field of Folder Store component. This is because the value of this RRT value contains backslashes and if you chose to use it as part of a Rename Schema, it would create an error as no file name can contain a backslash. Page 185

186 TRIM Captura 4.x Product Overview and Feature Highlights TRIM Captura is a Route component that is used to store documents into a document management system, where records can be searched for, identified, and a system of active and inactive records can be used. TRIM is a unique tool for Records Management, because it is both "object-oriented", and it can be configured to your requirements through the use of "record types" which may be hierarchically arranged. To say that TRIM is "objectoriented" means that the "objects" or items within the database e.g. files and folios, are the focus of attention and not the processes performed on them. Therefore, if a task were to be performed on a record, it's just a matter of choosing which record and then what task (move it, delete it, etc). The hierarchy model allows TRIM to reflect a real-world environment. The ability of TRIM to contain records within other records means that performing a task against a file (for example, a movement) can also apply to the contained correspondence. This component provides Find, update, or create a record. When finding a record, you have the option of creating a new version and to check in the record. Change the values of the fields associated with the record, and you can also use the rename schema, for multiple files with the same name. Access the records in a secure manner by way of providing a username and password. Using the Component If you want to protect valuable corporate information, ensure that an organization complies with reporting requirements, and enable the organization to easily access data, you would want to use TRIM. To batch store records, you can create a process using Poll Directory as capture component, and place the records in your input folder of the Poll Directory and use TRIM Captura as your store. To create a new version of an existing record, simply setup your process with the appropriate Capture component and TRIM Captura Route component. Set up the TRIM Captura attributes, select the Find Record checkbox, and enter the value of the record that you want to make a new version of. You have the option of entering a comment regarding the change. If this is a new record, click on the New Version checkbox. Now, instead of replacing the document, a new version of the document will be created. Do not use the Find option if you want to create a brand new record. With the Find option, you can create new versions of existing records and not a new record. Page 186

187 The Configuration of TRIM Captura 4.x General tab Field Name User Name Password Database Find Record Comments New Version Check in Record Type Title Container Enclose Security Level Function Enter the username for the TRIM database. Enter the login password for the TRIM database. Enter the database name. If you want to find an existing record, check this box. To create a new one, do not check this box. Depending on which you choose, you have to fill out the appropriate information. Enter a comment to the document. When checked, the document replaces the latest version of the document currently attached to the record. This parameter is ignored if there is no electronic document already associated with the record. The user can choose whether or not they want to check the file in. If they decide to check in the file, others can access the file and make changes in TRIM Context. This allows for only one copy of the file to be updated at any one time by putting a lock on the file. When a document has been Checked Out, TRIM takes a copy of the document and places in a DOS Directory or to a program called TopDrawer. The document then can be accessed and edited as required. When the document is returned or checked back into TRIM, it will be checked back in under the same TRIM Record Number. Select from all electronic record types, by clicking the browse button. The title of the document, which can later be used for searching. This field cannot be left blank. Select from the containers, by clicking the browse button. A container allows you to place a record inside another (for example, a document inside a file). When checked, the record s current location will be the container record that you selected, which allows for easier searching in the database later on. Distinguish records by a successive classification. For example, records that are Page 187

188 Priority External Reference Barcode classified TOP SECRET are higher in restriction than those classified as UNCLASSIFIED. Security Levels ensure that records may only be accessed by Units, Staff Positions and Staff Members who have the same Security Level or a higher Security Level than that allocated to a record. Enter the Priority of the document. Set the external reference of the document. Use this field to set the barcode of the document. Field Values tab Field Name Add Function You can add field name entries and field values to a record that is being stored in TRIM Captura. You can add field names from a list of names already in TRIM database. Click on the Add button and the Field Values dialog box appears. Select the field name from the drop-down list of available field names that are already defined in TRIM database. Enter the corresponding value for the field name. Modify Remove Rename File Schema For example, if you want to change the title of the document, you can change it by selecting the Add button and under the Field Values dialog box, you can select the Title of the document, and place a new value for it. Click on this button to modify field values of a record that is being stored in TRIM Captura. Use this option to remove Field Name entry. If you check this check box, you can enter the new file schema name that is being processed in to the TRIM Captura component. For example, if a file is named test.txt. In the Rename File Schema, you can enter the string example_%n.%e. When the component is running and the file test.txt comes in for processing by TRIM Captura, it renames the file to example_test.txt where %n is replaced by the file name ( test ) and the %e is replaced by the files Page 188

189 Replace Invalid characters with extension ( txt ). You can add a counter suffix (%c), if the file name has already been used. For example, if the original file name is test.txt, the rename schema renames the files to test1.txt, test2.txt, test3.txt for any reoccurrences of test.txt. If the file name has invalid characters, this feature allows you to replace that character with a valid character. For example, if "/" occurs when processing files with the Barcode, you need to replace the character with a valid character such as "a". RRTs for TRIM Captura 4.x The RRT ID for this component is TRI. Reserved Replacement Tag Names (RRTN) Name FileName FileExt Description The original file name value. Original file extension value The following example provides sample usage for your reference: ~TRI::FileName~ is replaced with the filename created using TRIM Captura (4.x) Field Replacement Tag Names (FRTN) This component does not have any FRTNs and replacement of field names with metadata values. Special Set Replacement Tag Names (SSRTN) This component does not have any SSRTNs. Troubleshooting Tips / Restrictions and Limitations Problem Description The field value list does not have anything for me to select from. Solution Either there are no field values to be set (unlikely) or it cannot connect to the database because it is an invalid database name or you do not have TRIM installed. Restrictions and limitations The container record must be of a higher level record type than the current record. If it is not, an error message is displayed when running the application as a service. Do not use the Find option if you want to create a brand new record. Title is a mandatory field and has to be supplied. External Reference, Priority, or Security Level are optional fields. Page 189

190 TRIM Context 5.x Product Overview and Feature Highlights The purpose of this component is to process documents into a TRIM Context document management system, where records can be searched for, identified, and a system of active and inactive records can be used. The Trim Context Route (Store) and Process (Filter) components are identical except the TRIM Context Route component solely stores the files and doesn't pass the files on as it is the last component in the process. The TRIM Context filter passes the files onto the next component which could either be another filter or a store for the process. TRIM Context is based on the Microsoft Distributed Component Object Model (DCOM). It also uses a multi tier network architecture model, which adds additional options to distribute processing activity, reduce network traffic, and reduce the activity on the database server. It generally improves application performance. The TRIM Context needs to be installed on the server in order for files to be stored. This component provides: Ability to either find a record and subsequently update it Ability to create a new record. When finding a record, you have the option of creating a new version of the record and to check in the record. Under the field values tab, you can add, modify, or remove fields and values associated with the record, Ability to rename schema, when you have multiple files of the same name. This component can be used with the Digital Sender and the Poll Directory, where it can pick up the files and then store them into TRIM Context data base. Any document or image file can be used as input to TRIM context component. Using the Component If you want to protect valuable corporate information, ensure that an organization complies with reporting requirements, and enable the organization to easily deal with issues in the event that documents are subject to litigation, you would want to use TRIM. Keeping the document safe within TRIM is what would be a best fit. You can create a process with Poll Directory as the Capture component, and archive documents into TRIM Context using this route component. Use scanners or Multi-functional Devices (MFD) to convert paper documents into images and store them into TRIM Context for long term archival. You can use OneStep with your desktop ISIS or TWAIN compliant scanner to capture data as well as images. Use Barcode cover sheet feature of the TRIM Context to print barcodes and use the barcode reader in conjunction with TRIM Context component to store the scanned documents into a pre-existing container/library/folder. Although you can dynamically create document libraries, you cannot create folders with TRIM Context component. Page 190

191 The Configuration of TRIM Context 5.x General tab Field Name Database Find Record Function Enter the name of the database that you would like to use for saving all the files in. If the database exists, you can verify the name of the database by clicking on the browse buttons next to the Record Type or next to the Container to verify the database name. If the database name does not show up at either of those places, the database probably does not exist. To add a file into TRIM Context, you can either search for a file and modify it or you can create a new file. Select Find Record to modify an existing file. There are several options available to you if you decide to modify the file. You can create a new version of the document, check in the document and add comments. Record Number Click on the browse button to select the desired record number. New Version When you select find record, you have the option of specifying if you want to make a new version of the record. If you check this box, the electronic document will be added as a new version of the document. As a result, the new document replaces the latest version of the document currently attached to the record, preserving the existing version of the document. Each record has a unique record identifier or URI, hence if you decide not to replace the old version, both records are saved under the same name, however, they will have different URLs. New record Record Type This parameter is ignored if there is no electronic document already associated with the record. Select this option to create a new record. If you want to create a new record, simply specify the record type in this field. Record types are either TRIM Context default record types or user defined record types. For example, a record type can be Document. After selecting the record type, you Page 191

192 Container can add a Title to the record and select the corresponding Container. Enter the container name associated with the record. When setting the container, you have to specify the container URI (unique record identifier). This will set the container of the current record to be the record with a URI of the container you choose. The container record must be of a higher level record type than the current record. When setting the container, you must also specify whether or not you want to enclose the record. Enclose Pass through If this check box is checked, the record s current location will be the container record that you selected, this allows for easier search in the database later on. This option is only available for the TRIM Context econnector component. When this option is selected, the document is passed to the next component in the process. Properties tab Field Name Title Security Classification Notes Author Keywords Finalize Function Enter the title for the document. Select the security level for the document. Browse for a classification for the document. Enter notes/comments for the record. Choose the author of the record. Choose keywords to be associated to the document. The keywords must be separated by commas. If checked, the current version becomes the final version of the record. This implies that no more changes can be made to the record. Page 192

193 Field values tab Use this tab options to add, modify and remove fields to the record. Field Name Add field values Function You can add field name entries and field values to a record that is being stored in TRIM Context. You can add field names from a list of names already in TRIM database. Click on the Add button and the Field Values dialog box appears. Select the field name from the drop-down list of available field names that are already defined in TRIM database. Enter the corresponding value for the field name. Modify field values Remove field values For example, if you want to change the title of the document, you can change it by selecting the Add button and under the Field Values dialog box, you can select the Title of the document, and place a new value for it. Click on this button to modify field name entries and field values of a record that is being stored in TRIM context. Click on this button to remove fields from the record, click on Remove. RRTs of TRIM Context 5.x component This component does not generate Runtime Replacement Tags, however all the parameters can contain RRT strings. For example, when POP3 is the capture (source) component, the "Record Type" parameter can be set to "~POP::Subject~" to dynamically set the record type using the subject field of the . Troubleshooting Tips / Restrictions and Limitations Problem Description Field value list does not have items to select from An error message is displayed when running the application as a service. Solution Either there are no field values to be set (unlikely) or it cannot connect to the database because it is an invalid database name or TRIM is not installed. The container record must be of a higher level record type than the current record. Restrictions and limitations The container record must be of a higher level record type than the current record. If it is not, an error message is displayed when running the application as a service. The URI (Unique Record Identifier), uniquely identifies objects of a given type and is assigned internally (its not shown to users of TRIM Context). Users cannot manipulate the URI setting. Page 193

194 VB/Java Script Product Overview and Feature Highlights Use this component as Process (Filter) or Route (Destination) with the most common scripting languages to manipulate and create your own custom built capture application. You can now create your own custom capture component by simply writing your scripts for accessing external databases, manipulating internal files, or validating index data fields. Access external data sources, lookup information that adds value to your capture process and merge the necessary external data elements. Scripts allow the user to do various activities, and provide a greater flexibility to the user. Create custom built capture components in fraction of a time and customize your capture processes according to your needs As files come in, you can run a designated script to alter the files, do various tasks such as saving them somewhere on the machine, or many other desired tasks. This component supports VBScript and Jscript scripting languages This component provides: This component allows you to choose the desired scripting language. The two available options are: o JScript o VBScript This component can be used as process or route, and can be used in any process. Any file type can be processed by this component. Using the Component Access external database files from within your capture task and validate captured data elements against your internal databases. Manipulate and reformat the file in mid-stream to match your custom needs. Apply other application wrappers on files to provide yourself with custom control over the document format, security and presentation. Add, delete, or modify field index data values to the process data space, reduce manual data entry and increase your data throughput Use this component when a specific file type file is received and there is a need to inform certain people. You can run a script which sends an every time that particular file type is received. This provides a lot of flexibility to the users. If this component is used as Router (Store), the script you choose should provide the Route (store) functionality. For more information on scripts in AutoStore please refer to the AutoStore SDK or the AutoStore forum at Page 194

195 The Configuration of VB/Java Script General tab Enter the general script attributes Field Name Name Language Script Function Enter the name of the function that you want to run. For example, you may have many different _OnLoad functions in your script. You have to specify which one you want to use. If you specified Test as the value of your Name field, then the Test_OnLoad function will run. Select the desired option from the drop down box whether you want to use a VBScript or JScript. Browse your computer for the Script that you want to run. The script must be available on the same directory location at runtime. Page 195

196 Fields tab Enter the field names and values that you want to use in the script Field Name Add Modify Remove Function Add a new field to be used within a script. The field name will be the variable name used within a script and the field value will be the value of the variable within the script. Click on the Modify Browse your computer for the Script that you want to run. The script must be available on the same directory location at runtime. RRTs of VB/Java Script This component does not generate Runtime Replacement Tags, however all the parameters can contain RRT strings. For example, when POP3 is the capture (source) component, the "Record Type" parameter can be set to "~POP::Subject~" to dynamically set the record type using the subject field of the . Troubleshooting Tips / Restrictions and Limitations Problem Description Clicking OK, does not close the dialog box. VBScript/JScript error. Solution You have either failed to enter a Name, select a Language, or specify a Script. Make sure the file that you selected as your script is a valid file, with a valid file extension. Restrictions and limitations You have to specify the Name, Language and Script. The Script you specify has to be a valid script. Standard JScript and VBScript limitations exist when it comes to variable naming conventions. Field name cannot start with a number - If it does start with a number, the number will be removed from the field name. Field name cannot start with a _ - However, it may contain any number of _ within the variable name. All spaces in a field name will be replaced with a _ All double and single quotes will be removed Page 196

197 All other invalid characters for field names will also be removed (e.g. %, $, #, ) Sample Scripts Standard JScript and VBScript limitations exist when it comes to variable naming conventions. Field name cannot start with a number - If it does start with a number, the number will be removed from the field name. Field name cannot start with a _ - However, it may contain any number of _ within the variable name. All spaces in a field name will be replaced with a _ All double and single quotes will be removed All other invalid characters for field names will also be removed (e.g. %, $, #, ) Page 197

198 WebDAV Product Overview - Feature Highlights WebDAV component is used for sending files to WebDAV servers, such as SharePoint and WebDAV folders. The component allows to assign necessary properties to the sent files. The only difference between WebDAV Route and WebDAV Process component is that WebDAV Process component has two additional options in the General tab: Activate check box, which allows to store captured document into WebDAV server, if selected. If this check box is not selected, the component won't perform any actions during files processing. Pass-through check box, which makes the document(s) available to the downstream components, if selected. These two options are not available in WebDAV Route component configuration. The component provides you with the following features: Route documents to WebDAV servers. Use either integrated Windows identification or User name and Password to log on to the server. Load folder tree from the server in the component configuration and display it to the user for selection of a file destination. Add properties to routed documents and set their values. Verify if the entered property value is applicable to the property and can be used in combination with the other properties. Using This Component The use cases below provide a sample of the component application: Scan documents from an MFP device, save directly into a folder within WebDAV Server: Design a workflow process with MFP component corresponding to the selected type of MFP device and WebDAV Route component. Configure WebDAV Route component to route the scanned documents into WebDAV folder with assigning of properties that uniquely identify the document. Configure both components and start the server. Now when the walk-up MFP user enters a pre-configured function key on the control panel of the MFP device, the scanned document with the configured properties is routed directly into WebDAV Server. Send s directly into WebDAV Server: Design a workflow process with SMTP Capture component, WebDAV Process component and Send to Folder Route component. Select the Activate check box in WebDAV Process configuration. Configure all 3 components and start the server. Now all incoming s sent to an SMTP gateway are i) saved into a pre-configured folder of the WebDAV server for archival, management or sharing and ii) routed to the desired folder on the computer or network folder according to Send to Folder configuration Building a Process With WebDAV Rote The main component's window consists of two tabs: General tab - Set parameters for connecting to a DAV server and determine destination folder. Properties tab - Assign necessary properties to the sent file. General tab In the General tab you can set the parameters for the DAV server connection and the output file destination. Page 198

199 Activate - this check box is present only in process component configuration window. Select this check box if you want to store captured document into WebDAV server. If this box is not checked, the component won't perform any actions during files processing. Pass-through - this check box is present only in process component configuration window. Select this check box if you want the document(s) to be available to the rest of the components in your process. Connection group allows you to set the parameters for connection to WebDAV server. WebDAV server - enter a path to WebDAV server. This field can contain " or " followed by the server name or IP address. For example, or Alternatively, it can contain only the server name or IP-address, e.g. server1 or It is mandatory to fill out this field. NT Authentication - select this check box to log on to the server by using Integrated Windows identification instead of user name and password. If this check box is not selected, enter the user name and the password for authentication. User name - enter the user name to log on to the server. If NT Authentication check box is not selected, it is mandatory to fill out this field. Password - enter the password to log on to the server. Destination group allows you to set the output file destination parameters. Folder - enter a path to the output files destination folder on the server either manually or browse to the desired folder using the (...) button next to this field. Clicking this button opens the WebDAV Folder dialog box. The component allows to create the folder path dynamically. One or several available RRTs can be used in this field. Rename file - select this check box to specify the file name for the output document using the Schema field. If this check box is not selected, the input file name will be used. Schema - determine the output file name by using renaming schema. This field can contain RRTs. Note: If the Rename file check box is selected and a rename schema is not provided, then at runtime the Schema name defaults to: ~DAV::FileName~_~DAV::Counter~~DAV::FileExt~. For example, if the input file name is File.tif, the renamed file will be File_1.tif. Overwrite existing file - if you select this check box, and a file under the specified name already exists in the output folder, the component overwrites this file. If this check box is not selected, and a file under the specified name already exists in the destination, an error message is generated. WebDAV Folder Page 199

200 The dialog box displays folders of the WebDAV server as a tree. Select the folder where the routed documents will be stored and click OK. Properties tab The Properties tab allows you to set the routed document's properties with their values. Each property is identified by name, value and server, which are displayed as table columns. Name - displays the name of the property in the following form: [namespace]name, where [namespace] is a namespace. Namespaces vary depending on the server type. The common namespace for all servers, which support WebDAV, is "DAV:". The possibility to configure standard properties of "DAV:" namespace depends on the specified WebDAV server properties. Value - displays property value. Server - displays server type. Use the following three buttons for managing the properties from the list: Add - click this button to add a new property to the list. The Add Property dialog will open. Edit - click this button to edit a property from the list. The Edit Property dialog will open. Delete - select one or several properties and click this button to remove the selected property(ies) from the list. Note: Removing a property is permanent and can not be undone. If you click Cancel after removing a property and then reopen the tab, the removed item will not appear. Add/Edit Property Field In this dialog box you can add a new property to the list or edit the selected property. Server - choose a server type from the drop-down list of the available types. Name - enter property name either manually or select it from the drop-down list of standard properties associated with the server. Entered name must have a following form: [namespace]name, where [namespace] is some string that should end with ":" symbol. This string is interpreted as a namespace. Namespaces vary depending on the server type. The common namespace for all servers, which support WebDAV, is "DAV:". The possibility to configure standard properties of "DAV:" namespace depends on the specified WebDAV server properties. It is mandatory to fill out this field. Page 200

201 Note: If you specify the property name as [namespace]name, the resulting property on the WebDAV server will have the following form: [namespace]:name, i.e. ":" symbol will be inserted between namespace and name. For example, if you specify My:time or DAV:displayname properties, these properties will look like My::time or DAV::displayname on the WebDAV server. Description - displays the property description if you choose one of the standard properties associated with the server. Otherwise, the field is disabled. Value - Enter value of the property. The component verifies whether the entered value is applicable for the property and can be used in combination with the other properties. RRTs for Knowledge Package Loader Component RRT ID Component's RRT ID is DAV. Reserved Replacement Tag Names (RRTN) The following table describes the reserved RTN values for the component: RRTN's FileName Counter Description The original file name value An incremental counter based on the duplicate file names found within a directory. The counter value concatenated with a name provides a unique file name. FileExt The original file extension value Here is the sample use case of the above RRTN: ~DAV::FileName~~DAV::Counter~~DAV::FileExt~ will be replaced by MyDocument2.txt, if the original file name is MyDocument.txt and MyDocument1.txt file already exists in the output folder. Field Replacement Tag Names (FRTN) This component does not have any FRTNs. Special Set Replacement Tag Names (SSRTN) This component supports the Date/Time tag names listed below: SSRTN's Description %a Abbreviated weekday name %A Full weekday name %b Abbreviated month name %B Full month name %d Day of month as decimal number (01-31) %H Hour in 24-hour format (00-23) %I Hour in 12-hour format (01-12) %j Day of year as decimal number ( ) %m Month as decimal number (01-12) %M Minute as decimal number (00-59) %p Current locale's A.M./P.M. indicator for -hour clock %S Second as decimal number (00-59) %U Week of year as decimal number, with Sunday as first day of week (00-53) %w Weekday as decimal number (0-6; Sunday is 0) %W Week of year as decimal number, with Monday as first day of week (00-53) %y Year without century, as decimal number (00-99) %Y Year with century, as decimal number Here is the sample use case of the above SSRTN: ~DAV::Y~-~DAV::m~ can be replaced by Page 201

202 Troubleshooting Tips / Restrictions and Limitations Problem Description When you try to use NT Authentication, an error message "Cannot connect to #Server#" appears, where #Server# is the name of the selected WebDAV server. Solution Try to use the WinHTTP proxy configuration utility Proxycfg.exe to set the WinHTTP proxy configuration settings correctly. To enable NT authentication between Client (computer with the WebDAV component) and Server (computer with WebDAV server), at the command prompt of the Client type proxycfg -p proxy_server "<local>;server", where proxy_server is the name of the computer with proxy server. If there is no proxy server in the network, specify some other computer name. Execute this command. For more information or if the command does not work see The Status monitor shows the following message: "Error WebDAV Route: Cannot set file properties." The file is not sent to the WebDAV server. When you use many processes with the component at the same time, not all of the processed files are routed to the output folder. Note: When you use this method, there may be problems with connection to the WebDAV server when using IP-address in the WebDAV Server field. Probably, you have set a property which is not applicable to the specified server or some property is read-only and can not be configured. Contact you server administrator to make sure that the configured properties are applicable to the specified WebDAV server and are not read-only. The issue is connected with high load of the IIS server where the WebDAV server is located. For more information see US. Restrictions and limitations There may be instability while working with big size files. The maximal limit is near Mb and it depends on parameters of a computer and the WebDAV server limitation. When you use the WebDAV component to send files to the SharePoint server and the type of the sent files differs from the type specified for the SharePoint document library, the unique file name can not be guaranteed when using ~DAV::Counter~ RRT, hence the documents can be overwritten. In this case you should use an additional method to guarantee a unique file name, e.g. using SSRTN in the rename schema. Page 202

203 WORLDOX Product Overview - Feature Highlights Worldox component is used to copy documents into the directories of Worldox, an enterprise-capable document management system from World Software Corporation. The component receives input files and configures output documents by adding Worldox metadata based on the component's configuration, which includes settings for document's profile group, field values for each field of the document profile and document relations. Communication with the Worldox system is performed via Worldox API. Since the API does not validate data, the component performs field length validation and table validation itself. If data validation or document placement fails then the component rejects such document. The only difference between Worldox Route and Worldox Process component is that Worldox Process component has two additional options in the General tab: Activate check box, that allows to store captured document into Worldox system, if selected. If this check box is not selected, the component won't perform any actions during files processing. Pass-through check box, that makes the document(s) available to the downstream components, if selected. These two options are not available in Worldox Route component configuration. The component provides you with the following features: The component working process can be started without previous starting Worldox GX. You can specify Worldox user in the component's configuration in order to connect to Worldox. You can determine the document profile parameters such as description, additional comments and field values in the component configuration. The component performs field length validation for profile fields. If the validation fails, the component rejects such document. The component can set parent-child relations for the output files. The output document will be specified as a child document to another document in the same group of input documents or to a file which already exists in a Worldox folder. You can use component's RRTs to determine most of the configuration parameters: Worldox user code, output directory, profile group, output file name, document profile settings, parent file path for "parent-child" relations setting, network mapping settings. Thus all of these parameters can be determined both immediately and at runtime. Using This Component Use the component for a complete preparation of your documents for working with Worldox document-management system. You can use the component for copying existing documents from your folders to Worldox directories. You can also use it as a route component in a workflow, where documents are processed by one or several process components and need to be stored into the Worldox system immediately after processing. The following example illustrates how the component can be used. Scan documents from an MFP device, recognize text from the scanned images and save text and image files directly into Worldox profile group: Design a workflow process with an MFP component corresponding to the selected type of MFP device, ABBY FineReader OCR component and Worldox Route component. Configure ABBY FineReader OCR to generate plain text output files. Specify the desired Worldox profile group and the output folder corresponding to it in the General tab of Worldox Route. In the Document Profile tab, enter file description, additional comments and configure profile fields by selecting field values of the routed documents. In the Document Relations tab, select the Set another document as parent check box and set parent document number to "-1". In the Network drives tab, map the network drive to the specified Profile group folder. When all three components are configured, start a process. Now when the MFP user enters a pre-configured function key on the MFP's control panel, the scanned image is recognized and routed directly into the specified Worldox profile group with the corresponding text file as a child. Page 203

204 Building a Process With WORLDOX The component configuration window consists of four tabs: General General tab - Define general settings for Worldox user information, output document profile group and its destination. Document profile tab - Define the settings for the document profile. Document relations tab - Define "parent-child" relations for documents. Network drives tab - Configure network drive mappings. The General tab allows you to define general settings concerning Worldox user information, profile group and name of the output document. Activate - this check box is present only in process component configuration window. Select this check box if you want to store captured document into Worldox system. If this box is not checked, the component won't perform any actions during files processing. Pass-through - this check box is present only in process component configuration window. Select this check box if you want the document(s) to be available to the rest of the components in your process. Worldox user - in this section you can set the parameters that allow you to start the component working process without starting Worldox GX. In the first field, select a user identification method. If you use Specify user code, you must enter Worldox user code in the second field. If you select System user, the component will try to connect to Worldox using your system login name. In this case the second field becomes disabled. If you use Specify user code and leave the second field empty, the component will be able to work only if Worldox GX was started previously. Note: In general case it is recommended to start the Worldox GX before starting the component working process to avoid Worldox API failure. Reconnect - click this button to check the connection to the Worldox server. If the connection was successful, the following message will appear: "Worldox client software initialized successfully". Otherwise an error message appears stating "Worldox failed to initialize the client software. Error returned: Operation failed. Please check that the Worldox network drives are mapped, Worldox user is configured properly or the Worldox GX client is running". Page 204

205 Note: If the Wordox GX software was started previously, the current Worldox GX credentials are used for initialization in the following situations: When you select Specify user code in the first field of the Worldox user section and leave the second field empty When you enter some value that is neither Specify user code nor System user in the first field. When you click the Reconnect button in either of the above situations, the following warning message appears: "The currently running instance of the Worldox GX client software is used. To use Worldox during the document processing please specify a correct Worldox user code in the configuration." If the Wordox GX software is not started and you enter some value that is neither Specify user code nor System user in the first field of the Worldox user section and click the Reconnect button, the following warning message appears: "Worldox failed to initialize the client software. Error returned: Worldox software is not loaded. Please check that the Worldox network drives are mapped, Worldox user is configured properly or the Worldox GX client is running". Profile group - allows you to determine profile group of the document. In the first field you can select one of two methods of the determination: For output folder: the profile group is determined by its base folder entered in the Output folder field. Specify identifier: you can enter the profile group identifier in the second field and the third field will display profile group name. Alternatively, you can click the button to select one of the profile groups available for the currently logged Worldox user in the opened Select Profile Group dialog window. Output folder - specify the output folder either manually or browse to the folder using the select one of the special values using the The special values are: button. Base folder for the profile group, determined at runtime. Network drive mapped to base folder for the profile group, determined at runtime. button. You can also Network resource path of the drive mapped to base folder for the profile group, determined at runtime. Output folder corresponding to the document s profile (field values), determined at runtime. Currently available base folder for the specified profile group. Currently available network drive for the specified profile group. Currently available network resource path for the specified profile group. Auto name - selecting this check box causes the component to determine automatic name for the new document. The auto name represents an automatically generated document ID number. The document ID format is the Worldox system setting. Rename file - by selecting this check box, the user can specify file name for the output document using Renaming schema field. This field can contain RRTs. Replace existing file - selecting this option causes the component to overwrite the existing file with the same name in output directory. Add as new version - selecting this check box causes the output file to be written and saved as a new version of the existing file. The existing file will be preserved as the older Worldox version of the file. Worldox allows to create up to 15 file. If this option and the Replace existing file option are turned off, the document will be rejected in the case if a file with the same name already exists in the output folder. Select Profile Group In this dialog window you can select one of the available profile groups for the user. Current user - displays current Worldox user name and user code. Page 205

206 Select one of the available profile groups - displays the list of the available profile groups for the user. Network map - displays network drive mapped to the base folder for the selected profile group. Document Profile Use this tab to configure metadata associated with the document or Worldox document s profile. Description - enter document s description. Additional comments - enter additional comments to the document. Fields - create a list of the Profile fields. To do so, use the Add and the Edit buttons. This list can contain up to 7 fields determined by the profile group. Add - click this button to add a new field to the document's profile fields list. The Add Field Value dialog box will open. Edit - click this button to edit a field value from the document's profile fields list. The Edit Field Value dialog box will open. Remove - select one or several fields and press this button to remove the selected field(s) from the document profile. Edit Field Value Page 206

207 In this dialog window you can edit a field value from the document's profile fields list. Field First field in this section displays the selected field number. The second field displays the selected field description. Field value source - use the combo-box to choose one of four alternatives: Specified value Determine default for saving at runtime Determine default for copying at runtime Determine default for moving at runtime If one of the three last options is selected, then the component will determine default value at runtime. In this case the Specified value field becomes disabled. Specified value - if you have selected the Specified value option for the Field source value, enter field value manually or click the button. This button brings up a menu with following alternatives: Set default value for saving Set default value for copying Set default value for moving Select value from the table First three items fill the Specified value field with the defaults currently available to the Worldox user. The last alternative opens the Select Field Value dialog. This dialog displays an available field table for the currently configured field. You can select a value from the table. If there is no field table for the selected field, the opened menu will contain only three first alternatives. Value description - displays description of the Specified value, if the value is a table item. Field flags - displays some information about the options of the field. The options can not be selected by user, they are the settings for the selected profile group. Page 207

208 Add Field Value In this dialog window you can add a field value to the document's profile fields list. Field In the first field in this section you can select a new field number. The second field displays the selected field description. Field value source - use the combo-box to choose one of four alternatives: Specified value Determine default for saving at runtime Determine default for copying at runtime Determine default for moving at runtime If one of the three last alternatives is selected, the component will determine default value at runtime. In this case the Specified value field becomes disabled. Specified value - if you have selected the Specified value option for the Field source value, enter the field value manually or click the Set default value for saving Set default value for copying Set default value for moving Select value from the table button. This button brings up a menu with following alternatives: First three items fill the Specified value field with the defaults currently available to the Worldox user. The last option opens the Select Field Value dialog. This dialog displays an available field table for the currently configured field. You can select a value from the table. If no field table for the selected field is available, the opened menu will contain only three first options. Value description - displays a description of the Specified value, if the value is a table item. Field flags - displays some information about the options of the field. The options can not be selected by the user, they are the settings for the selected profile group. Page 208

209 Select Field Value In this dialog box you can select a value from the profile field value table. Select field value from the table - this table corresponds to Worldox profile field value table for the selected field. It contains the value code column and the value description column. Select a row from the table and click OK to set a value for the currently configured field. Document Relations This tab allows you to specify the Worldox document "parent-child" relations of the output files. Set another document as parent - if this option is selected, the output document will be specified as a child document to another document in the same group of input documents. This option can be useful, if in the workflow the Worldox Route component is placed after a component that generates several output files. You must enter an order number of parent document in the Parent document number field. A positive parent document's number is considered as an order number of the input document's list. A negative number is considered as a reverse-order number : -1 for the last (Nth) document, -2 for the last but one document, etc. If the specified number is out-of-bounds, then no relation will be set. If the parent file is the document which has not been placed yet, the component delays relationship until the parent file is placed into the output folder. For example, when in the workflow the Worldox Route component follows after the ABBYY OCR component, the original image can be set as a "parent" document to the generated text files. Set file as parent - when this option is selected, the output document will be specified as a child document to a file which already exists in a Worldox folder. User should specify parent s file path (including directory and file name) manually or using "..." button. This field can contain component's RRTs. If the parent file is the same as the child file the component does not set relation. Set relation only if parent exists - this option is available only if you choose the Set file as parent option. When the option is turned off and the selected file does not exist in the specified folder, the component delays relationship until the parent file is placed into the specified folder. If the option is on, the relation is not set. Page 209

210 Network Drives In this tab you can set all the necessary mapped network drives for a proper operation of the component. In particular a network drive with Worldox server and a network drive containing base profile group folder should be mapped. Map network drives - displays a list of mapped network drives. If some network drives have already been mapped without the use of the component configuration, it is not necessary to add them to the Map network drive list. In this case you have to make sure that the service user has an access to these drives for a proper operation of the component. Note: In general case it is recommended to add already mapped network drives to the Map network drive list. Add - click this button to map new network drive. The Add New Network Drive Mapping dialog box will open. Clicking this button is equivalent to double clicking the Map network drives field when no network drive selection is made. Edit - click this button to edit mapping parameters of the selected network drive from the list. The Edit Network Drive Mapping dialog box will open. Clicking this button is equivalent to double clicking the selected drive in the Map network drives field. Remove - select one or several network drives and press this button to remove the selected network drive(s) from the list. Add currently mapped drives - click this button to open the Select Network Drives dialog box where a table of currently mapped drives is displayed. In this dialog box you can select one or more currently mapped drives and add them to the list. Network drive user authentication - enter user credentials necessary for mapping network drives. Use current user credentials - selecting this option causes the component to use current user authentication parameters for component's service. If this option is not selected, you must enter user name and password. Obtain password via RRT - select this option to use one or several component's RRTs for password determination. Add New Network Drive Mapping Use this dialog window for mapping a new network drive. Drive letter - enter a letter for naming new network drive, for example Z:. Resource path - enter a path to a resource corresponding to a new network drive either manually or browse to the resource using the button. Use distinguished authentication settings for this drive - select this option to determine credentials in the This network drive mapping authentication section. If this option is not selected, the section is disabled. Page 210

211 This network drive mapping authentication - in this section you can enter user credentials necessary for the network drive mapping. If you select Use current user credentials, the component uses current user authentication parameters for component's service. Otherwise, you must enter user name and a password. With checking the Obtain password via RRT option you can use one or several component's RRTs for password determination. Edit Network Drive Mapping Use this dialog window for editing mapping parameters of the currently mapped network drive. Drive letter - displays a letter corresponding to selected network drive. Resource path - enter a path to a resource corresponding to a new network drive either manually or browse to the resource using the button. Use distinguished authentication settings for this drive - select this option to determine credentials in the This network drive mapping authentication section. If this option is not selected, the section is disabled. This network drive mapping authentication - in this section you can enter user credentials necessary for the network drive mapping. If you select Use current user credentials, the component uses current user authentication parameters for component's service. Otherwise, you must enter user name and a password. With checking the Obtain password via RRT option you can use one or several component's RRTs for password determination. Select Network Drives In this dialog box, you can select one or more currently mapped drives and add them to the list. Select one or more network drive mapping - this table presents a list of currently existing mapped network drives. The columns are: drive, network resource and configured mapping. Select one or more table rows and press OK to add them to the list of mapped network drives in Network Drives tab. RRTs for WORLDOX Component's RRT ID Component's RRT ID is WRC. Reserved Replacement Tag Names (RRTN) This component supports two groups of the reserved RTNs: o File specific RRTNs Name FileName FileExt Description The original file name value Original file extension value o Profile group specific RRTNs Name BaseFolder NetworkDrive NetworkPath ProfileFolder Description Base folder for the profile group Network drive where the base folder for the profile group is mapped to Network resource path where the base folder for the profile group is located Output folder corresponding to the document s profile (field values) Note: Replacement of the Profile group specific RRTs is performed after the Document Profile settings have been loaded and the profile group determined. These RRTs can be used inside the Document Profile settings only if you select Specify identifier for profile group determination on General tab. If you use the For output folder method, these RRTs can not be used inside the Document Profile settings. The following example provides some sample usage for your reference: Page 211

212 ~WRC::BaseFolder~~WRC::FileName~.~WRC::FileExt~ replaced with the value "M:\image1.tif" if the base folder for the profile group is M:\, and the input file is image1.tif. Field Replacement Tag Names (FRTN) This component does not have any FRTNs and replacement of field names with metadata values. Special Set Replacement Tag Names (SSRTN) This component supports the Date/Time tag names listed below: Name Day YearDay Hour12 Hour24 Locales Minutes Month MonthAbbr MonthDigital Seconds WeekDay WeekDayAbbr WeekDayDigital WeekSunday WeekMonday Year Year2Digit Description The day of month (1-31) when the file was placed into Worldox The day of year (1-366) when the file was placed into Worldox The 12-based hour (1-12) when the file was placed into Worldox The 24-based hour (0-23) when the file was placed into Worldox A.M./P.M indicator for 12-hour clock when the file was placed into Worldox The minute (00-59) when the file was placed into Worldox Full (January-December) month when the file was placed into Worldox Abbreviation (Jan-Dec) month when the file was placed into Worldox Digital (1-12) month when the file was placed into Worldox The second (00-59) when the file was placed into Worldox Full (Sunday-Saturday) when the file was placed into Worldox Abbreviated (Sun-Sat) week day when the file was placed into Worldox Digital (0-6) week day when the file was placed into Worldox The number of the week in year (1-53) when the file was placed into Worldox (Sunday is the first day of week) The number of the week in year (1-53) when the file was placed into Worldox (Monday is the first day of week) Full 4-digit year when the file was placed into Worldox 2-digit (00-99) year when the file was placed into Worldox Examples usage of the above SSRTN include: ~WRC::%Y~-~WRC::%m~ will be replaced by " ". Troubleshooting Tips / Restrictions and Limitations Problem description A component does not generate an output file. Status Monitor displays the following message "Worldox failed to initialize API. Error: Operation failed". Status monitor displays the correct operation of the component but there are no files in the output directory. "Parent-child" relations are not set when you use the Set another document as parent option. Solution A component's service may not have a connection to Worldox system. If you used the Specify user code connection method in the General tab, the entered user code may be incorrect. Check it and enter correct user code. Press Reconnect to make sure that the connection was successful. If you used the System user method, your system login name may not belong to a Worldox user codes list. Contact your Worldox administrator or try another connection method. May be data validation has been failed and output file has been rejected. Field length of some profile field may be incorrect. Check if the profile field values in the document profile have a proper length. The specified number of parent document may be out-ofbounds. It means that its absolute value exceeds the number of input documents. Enter the correct parent document number. Page 212

213 "Parent-child" relations are not set when you use the Set file as parent option. The document profile parameters determined with the use of RRTs are empty or not replaced. Add as new version option is on, but a new version of the output file does not occur in the output folder. No file is placed into the output directory. Status monitor displays the following message: "Worldox failed to copy file #name# to ". Error returned: destination file already exists", where.#name# is output file's name with a path. When you send files with.tmp extension, the Status Monitor shows the following message: "Worldox failed to set document profile. Error returned: Cannot get first item in the list." and the file is rejected. ~WRC::ProfileFolder~ RRT fails to be generated or is generated incorrectly. For example, if ~WRC::BaseFolder~ is Y:\ and the profile has two subdirectory fields: FLD13 and FLD23, then the ~WRC::ProfileFolder~ is replaced with "Y:\" instead of "Y:\FLD13\FLD23\". This behavior has irregular nature and depends of background programs running, set of input files, etc. Sometimes, when the component's configuration dialog opens, the component's service window hides under another window. When you use the Auto name option, the file is not placed into the output directory and the Status Monitor shows the following message: "Worldox failed to produce automatic file name for the output directory #path#. Error returned: Operation failed", where #path# is the output folder path. Status monitor shows the following message: "Worldox 1. May be the parent file is the same as the child file. Use another file as a parent. 2. If the Set relation only if parent exists option is off, and the selected file does not exist in the specified folder, place the selected file into the specified folder, and the component will set a relationship. 3. If the Set relation only if parent exists option is on, and the selected file does not exist in the specified folder, the relation can not be set. Use an existing file in the folder as a parent. May be you used Profile group specific RRTs for document profile parameters determination and the Profile group was determined with the For output folder method. You may use these RRTs for document profile settings only if the Profile group is determined by the Specify identifier method. Change the profile group determination method or do not use these RRTs inside the Document Profile settings. Probably there are already 15 versions in the output folder, thus Worldox limitation has been exceeded. Specify another output file name. May be the file with the same name already exists in output directory and neither the Replace existing file, nor the Add as new version options in General tab are selected. Select one of the options. The.tmp extension is related to the internal Worldox file format, therefore files with this extension can not be processed correctly. Try to change the file extension. This problem is connected with Worldox API software instability. To improve stability of Worldox API it is recommended to make sure that there are no viruses in the system and to remove all background file scanners, i.e. indexing services, real time virus scanner, etc. However in some situations this does not help. To assure avoiding this problem do not use ~WRC::ProfileFolder~ RRT in the Output folder field. Instead this field should contain manually-formed output path. For example, if the selected profile contains two subfolder fields "FLD13" and "FLD23" then the output folder should contain "~WRC::BaseFolder~FLD13\FLD23". Although this will not prevent warnings about ~WRC::ProfileFolder~ RRT, all documents will be processed correctly. This problem is not critical and is related to the RRT window that is displayed before the component's configuration dialog. The problem can be resolved by minimizing another window. Worldox software may be configured incorrectly to produce auto name for the routed file. Apply to Worldox administrator or use the Rename file option instead of the Auto name option. There may be a problem with the output folder, for Page 213

214 failed to copy file #name# to ". Error returned: Operation failed.". The file is not placed to output folder or placed with incorrect profile. example, the place limit may be exhausted. If the file size is rather big, the reason may be in Worldox API feature that concerns copying files of a size about 600Mb and larger. In this case the file profile is not created correctly even if the file is correctly copied. Try to decrease the file size. Restrictions and limitations. The component's service should have all permissions required to communicate with the Worldox software and to access to the output folders. A user must have a user code for identification in Worldox system. User code will be checked for validation during the document s processing. The network drive with Worldox server and a network drive containing base profile group folder should be mapped. Page 214

215 XML Generator Product Overview - Feature Highlights XML Generator component is used for mapping the data received by means of RRTs to XML files. In particular, the component provides mapping of table data to XML format. Such table data are generated by several components, for example, by OpenForms Capture or Professional Barcode. Mapped tables may have any number of dimensions. The number of rows in any dimension can be in a range set up by the user, for example, a range for a 2-dimensional table may be set from 1 to 10 rows. The required XML structure should be described with a template which is also an XML file. Using this XML file the generic structure of the output file can be defined. The XML Generator Route and econnector components are identical except that the XML Generator econnector component has the following additional options: The Activate check box which allows to make the component active. By default, this check box is not selected. If this check box is not selected, the component will not perform any actions during file processing. The Pass through check box for generated XML document. If this check box is selected, the XML document is available to the rest of the components in the process. When this check box is not selected, the Output to: check box is selected and disabled. The Output to: check box for generated XML document. When this check box is selected, the generated XML document will be routed to the specified output folder. If the Output to: check box is not selected, the Pass through check box is selected and disabled. This behavior concerns only generated XML document. The Pass through check box for original document(s). If this check box is selected, the original document is available to the rest of the components in the process. If the Pass through and the Output to: options are not selected, the original documents are eliminated. The features of the component are: Mapping data received by means of RRTs to XML files. Loading of XML template file, displaying all nodes and their attributes as a tree for describing the output file structure. Setting output file node and attribute values, based on the template, using the component's RRTs and RRTs generated by any other component. Multiplying the desired node within parent node any number of times for displaying table data in output XML file. Using This Component Two cases of using XML Generator can be proposed: Mapping non-tabular data Mapping tables Following examples illustrate the above two ways of using the component: 1) Mapping non-tabular data. An example of non-tabular data may be presented by RRTs generated by POP3 component that registers input mails from a mail server: ~POP::Body~, ~POP::CC~, ~POP::Date~, ~POP::From~, ~POP::Subject~, ~POP::To~. Consider a workflow with POP3 as a process component and XML Generator component. First configure POP3 component by setting the server, user name, password, port number information. Next, configure XML Generator component: load a template and choose an output directory for XML files. The structure of the template may be as follows: Page 215

216 <?xml version="1.0" encoding="iso "?> < > <info> <from>from</from> <subject>subject</subject> <date>date</date> <to>to</to> <CC>CC</CC> </info> <body>body</body> </ > Finally, replace the template nodes with POP3 component's RRTs. XML Generator component generates the output XML file mapping input mails information. 2) Mapping tables. An example of data containing tables may be presented by the RRTs generated by the Professional Barcode component that represent barcode values for every page of a document. Consider a configuration with Professional Barcode as a process component and XML Generator component. In XML Generator configuration, browse the following template: <?xml version="1.0" encoding="iso "?> <Root> <Document> <Page> <Number>Data</Number> <FirstBarcode>Data</FirstBarcode> <SecondBarcode>Data</SecondBarcode> </Page> <AllBarcodes>Data</AllBarcodes> </Document> </Root> Based on this template, set a configuration of the output file. First, multiply the Page node by inserting a counter m with Min value=1 and Max value=3. Next, replace the Number node value with m, the FirstBarcode node value with ~FRB::m,1~, the SecondBarcode node value with ~FRB::m,2~ and the AllBarcodes node value with ~FRB::*,*~. If the original document has 3 pages, with the first page containing 2 barcodes, e.g. code1, code2, the second page containing no barcodes, and the third page containing 2 barcodes, e.g.code3, code4, then the output XML file for this document is as follows: <?xml version="1.0" encoding="iso "?> <Root> <Document> <Page> <Number>1</Number> <FirstBarcode>code1</FirstBarcode> <SecondBarcode>code2</SecondBarcode> </Page> <Page> <Number>2</Number> </FirstBarcode> </SecondBarcode> </Page> <Page> <Number>3</Number> <FirstBarcode>code3</FirstBarcode> <SecondBarcode>code4</SecondBarcode> </Page> <AllBarcodes>code1, code2, code3, code4</allbarcodes> </Document> </Root> Page 216

217 Building a Process With XML Generator In the XML Generator (econnector) Configuration dialog window, you can determine a structure, name and destination of the generated XML file and the routed original document(s). In particular, you can load a template file displaying generated XML file structure as a tree. You can edit the structure by setting node values and attribute values, as well as by multiplying nodes. The window consists of the following parts: Configuring the structure of the generated XML file Settings for name and destination of the generated XML file Settings for name and destination of the original document(s) Activate - this check box is present only in the XML Generator econnector configuration window. Select this check box if you want to make the component active. If this box is not checked, the component will not perform any actions during file processing. XML template group allows to configure the structure of the generated XML file. Source - enter the path to the XML template file and then click the (...) button. Properties - set the output file structure based on the template: In order to change value of an attribute, select the desired attribute in the template and press the Properties button. Attribute value can be changed in the opened Edit Attribute dialog box. In order to multiply a node, select the required node and press the Properties button. The options of repeating one node within the parent node can be set up in the opened Multiply Node Block dialog box. In order to change a node value, select the required node's value and press the Properties button. The node value can be changed in the opened Edit Node Value dialog box. Generated XML document group allows to configure settings for name and destination of the generated XML file. Page 217

218 Pass through - this check box is present only in the XML Generator econnector configuration window. Select this check box to make the XML document available to the rest of the components in the process. When this check box is not selected, the Output to: check box is selected and disabled. Output to: - for XML Generator econnector configuration, this element contains a check box and a field. When the check box is selected, the generated XML document will be routed to the specified output folder. If this check box is not selected, the Pass through check box is selected and disabled. The field allows you to enter a destination for the generated XML file manually or using the ( ) button. For the Route component, this element contains only a field that allows to enter a destination for the generated XML file manually or using the ( ) button. Rename schema - select this check box to specify the file name for the generated XML document using the schema field. You can use RRT to dynamically set the value of the schema. The.xml extension will be set automatically to the generated document. If the Rename schema check box is not selected, the generated XML file name defaults to ~XMR::FileName1~#Counter#.xml, where #Counter# is a unique identifier based on the presence of files with the same name in the work directory. For example, if the first original file is File.doc, the generated XML file will be File1.xml. Note: If the component has no documents on input, the default name of the generated XML file will be generatedxml1.xml. If the Rename schema checkbox is selected, however a schema name is not provided, then at runtime the schema name defaults to ~XMR::FileName1~_~XMR::Counter~.xml. For example, if the first original file name is File.tif, the renamed file will be File_1.xml. Original document(s) group allows to configure settings for name and destination of the original document(s). Pass through - this check box is present only in the XML Generator econnector configuration window. Select this check box to make the original document(s) available to the rest of the components in the process. Output to: - if this check box is selected, the original document(s) will be routed to the specified output folder. Enter a destination for the original document(s) manually or using the ( ) button. Note: You can check and uncheck the Pass through and Output to: options in any combinations for the original documents. If the Pass through and Output to: options are not selected, the original documents are eliminated. Rename schema - select this check box to specify the file name for the original document using the schema field. You can use RRT to dynamically set the value of the schema. If the Rename schema check box is not selected, the original document name will be used. If the Rename schema checkbox is selected, however a schema name is not provided, then at runtime the schema name defaults to ~ XMR::FileName~_~ XMR::Counter~~XMR::FileExt~. For example, if the input file name is File.tif, the renamed file will be File_1.tif. Overwrite existing file - if this check box is selected, the component overwrites existing file with the same name in the output directory. This option is at the same time related to both the generated XML document and the original documents. If this option is checked, both the XML document and the original documents are overwritten. Otherwise, if this option is unchecked, the presence of a file with the same name for the XML document or the original document will cause the error message and stop further processing for this file. Note for XML Generator econnector (RRTs): The following six RRTs included in the Available RRTs list of the XML Generator econnector process component will not be available for the configuration of the subsequent route component of your AutoStore process: File Counter File Name File Extension File Content by Index File Name by Index File Extension by Index Page 218

219 The above RRTs will be replaced by the following two RRTs: File Path XML File Path Page 219

220 Using XML template The required XML structure of the output file should be described with the following XML file, which is actually a template. You can load a template file in XML Generator (econnector) Configuration dialog box. All nodes, their attributes and values are displayed in a tree. Based on the template file, you can replace nodes and attributes by the available RRTs and insert counters for multiplying nodes. In order to change the value of an attribute, select the desired attribute in the template and click the Properties button. Attribute value can be changed in the opened Edit Attribute dialog box. Attribute value can be replaced by one of the available RRTs or a combination of several RRTs. In order to change the value of the node, select the required node's value, and click the Properties button. The node value can be changed in the opened Edit Node Value dialog box. The node value can be replaced by one of the available RRTs or a combination of several RRTs. You can also insert counters for creating nested multiplied nodes. When the component detects nested multiplied nodes, it treats the corresponding counters as nested. For example, a template file can have the following structure: <?xml version="1.0" encoding="iso "?> <!-- Generated in XML Route Component. --> <ParentNode> <ChildNode ID="1"> <GrandChildNode ID="1">Data</GrandChildNode> <GrandChildNode ID="2">Data</GrandChildNode> <GrandChildNode ID="3">Data</GrandChildNode> </ChildNode> <ChildNode ID="2"> <GrandChildNode ID="1">Data</GrandChildNode> <GrandChildNode ID="2">Data</GrandChildNode> <GrandChildNode ID="3">Data</GrandChildNode> </ChildNode> </ParentNode> In this structure ChildNode is a nested node for ParentNode, and GrandChildNode is a nested node for ChildNode. In order to multiply a node, select the required node and click the Properties button. The options of repeating one node within the parent node can be configured in the opened Multiply Node Block dialog box. When the configuration is completed, press OK. The component saves all the settings in a configuration file. These settings modify the configuration of the component, but not the template file itself. The window in the XML Generator (econnector)configuration dialog box displays the structure of the output file as a tree replacing the original template nodes and attributes values with values set up by the user. Editing Attribute The Edit Attribute dialog box allows you to change the value of an attribute. Attribute name - this field displays the name of the attribute. Page 220

221 Attribute value - enter a new value of the attribute. The value can be replaced by one of the available RRTs or a combination of several RRTs. Note: You cannot use ~XMR::Counter~ for attribute value setting. The values for the attributes named Version and Encoding cannot be replaced. All RRTs must be replaced - if this option is on, the component cannot generate the output XML file without replacing all RRTs used in the attribute value structure by real data. By default, this option is off and RRTs having not been replaced, appear as blanks in the output XML file. Reset - click this button to return back to the original attribute value, which is provided in the XML template. Multiplying node The Multiply Node Block dialog box allows you to configure the options of repeating one node within the parent node. The dialog box contains the following fields: Node name - this field displays the name of the selected node. Counter label - enter any string, which will be used as a counter for table rows. Counter label is case-sensitive. Min value - enter minimum value of the counter. Max value - enter maximum value of the counter. Maximum number of repeated nodes can be Max value - Min value + 1. Max value and Min value should be integer values. If you enter non-integer value or RRT in any of those fields, it will cause the following error message: "Please, enter an integer value". Max value and Min value can be both positive and negative, but Max value must be greater or equal to Min value. If the entered Min value is greater then entered Max value, it will cause the following error message:"max value should be greater or equal than min value". If the number of RRTs replaced by data is greater than Max value, RRTs with the numbers exceeding Max value will be ignored and the tables will be truncated. If RRTs have not been generated for some table rows corresponding to counter values, then these rows will also be removed from tables. Thus, the tables will contain only the rows with data received using RRTs. Remove - click this button to remove information about the counter from configuration. It clears all fields in a dialog box. You can multiply one or several nodes. The order, in which single and multiplied nodes appear in the output XML document cannot be modified. Page 221

222 Editing Node Value The Edit Node Value dialog box allows you to change the value of a node. Node value - enter one of the available RRTs (or a combination of several RRTs) to replace node value. Note: You cannot use ~XMR::Counter~ for node value setting. All RRTs must be replaced - if this option is on, the component cannot generate the output XML file without replacing all RRTs used in the node value structure by real data. By default, this option is off, and RRTs which have not been replaced appear as blanks in the output XML file. Reset - click the button to return back to the original node value, which is provided in the template. RRTs for XML Generator Component RRT ID Component's RRT ID is XMR. Reserved Replacement Tag Names (RRTN) The following table describes the reserved RTNs for this component: RRTN Description FileName File name of original document without extension and without path FileExt Counter FilePath XMLFilePath File extension of original document An incremental counter based on the duplicate file names found within a directory. The counter value concatenated with a name provides a unique file name. File path to the output directory of original document(s). This applies to the XML Generator econnector component only. File path to the output directory of the generated XML document. This applies to the XML Generator econnector component only. Special Set Replacement Tag Names (SSRTN) This component supports the Date/Time tag names listed below: SSRTN Description %a Abbreviated weekday name %A Full weekday name %b Abbreviated month name %B Full month name %d Day of month as decimal number (01-31) %H Hour in 24-hour format (00-23) %I Hour in 12-hour format (01-12) %j Day of year as decimal number ( ) %m Month as decimal number (01-12) %M Minute as decimal number (00-59) %p Current locale's A.M./P.M. indicator for -hour clock %S Second as decimal number (00-59) %U Week of year as decimal number, with Sunday as first day of week (00-53) %w Weekday as decimal number (0-6; Sunday is 0) %W Week of year as decimal number, with Monday as first day of week (00-53) Page 222