Glossary
10 minute read
Last updated on September 27, 2023
Dispatcher Phoenix
| Word | Definition |
|---|---|
| Active Input | An input is any entry point into a workflow (Input Folder, MFP User Box, MFP Panel, LPR In, SMTP In, etc.) and is considered active when the workflow is running or is scheduled to run. MFPs used within Release2Me workflows are also considered active inputs. |
| AD | Active Directory (AD) is a Microsoft product that consists of several services that run on Windows Server to manage permissions and access to networked resources. |
| Add-In Manager | This tool is used to view, download, install, or uninstall updates to Dispatcher Phoenix applications. |
| Add-In Modules | A set of features, functions, or nodes that expand or enhance your existing Dispatcher Phoenix installation. |
| ADF | Automated Document Feeder (ADF) used on scanners and MFPs to feed pages into the machine so that multiple pages can be scanned at one time, eliminating the need to scan a document one page at a time. |
| Advanced Routing | Dispatcher Phoenix processing including routing by email, the page count, or color content of the document. |
| Automatic Web Registration and Activation | The process of registering and activating your Dispatcher Phoenix installation with a Solutions Engineering Center (SEC) website login, password, and purchase code. |
| bEST | This stands for bizhub Extended Solution Technology (bEST) and it enables seamless integration between Konica Minolta MFPs and software applications residing on a PC or server. Those software applications (for print management, cost control, document workflow, etc.) can be accessed directly from the device panel. |
| Bubble Grader | A grading and assessment solution for educators and administrators in K-12 as well as colleges and universities. |
| Canvas Properties | The settings and customization options for the background or “canvas” of the workflow. |
| Collection Node | The starting node that collects files (e.g. Input Folder, MFP Panel, etc.) for further processing/distribution of a Dispatcher Phoenix workflow. |
| Connector (Node) | A type of distribution or output node that allows Dispatcher Phoenix to route files to a third party applications (e.g. OnBase Connector, Google Drive Connector, etc.). |
| Connector (Workflow Builder) | A pathway between two nodes. Connectors can include Standard, Yes, No, and/or Error transitions and illustrate the direction a document will travel through the workflow. |
| Default Error Node | A customization setting in the Canvas Properties that automatically collects documents that error out of a workflow without using a separate error transition. |
| Distribution Node | The ending node of a workflow path that distributes files to an output (e.g. Output Folder, Printer, etc.). |
| Document Indexing | The process of associating data or search terms to a document in order to facilitate search and document retrieval. |
| Document Management Systems | Applications that enable organizations/businesses to manage their documents in electronic format, storing these documents for subsequent search and retrieval. |
| Document Manipulation | Dispatcher Phoenix’s custom file editing tools including Advanced Bates Stamp, Redact, Highlight, Annotate, and more. |
| File Parsing | Parsing is a process performed on files based on pre-defined rules. A Parser Rule is a process within a workflow that performs a Search For, Distribute, Insert, or Replace operation, based on the conditions you define. |
| Flatbed Scanner | A scanner where the document is placed on platen glass for scanning. |
| FTP | File Transfer Protocol (FTP) is a standard Internet protocol for transmitting files between computers on the Internet over Transmission Control Protocol (TCP)/Internet Protocol (IP) connections. |
| Graphical Workflow Builder | The highly intuitive, drag-and-drop tool for creating Dispatcher Phoenix workflows. |
| HTTP | Hypertext Transfer Protocol (HTTP) is the communications protocol used to connect to Web servers on the Internet or on a local network (Intranet). Its primary function is to establish a connection with the server and send resources such as Hypertext Markup Language (HTML) pages back to the user’s browser. |
| Icon (Node) | The image associated with the node that can be customized for each workflow to suit your needs. Users can upload custom icons to suit each node in their workflow. |
| Image Processing | The analysis and manipulation of a digitized image, especially in order to improve its quality. Dispatcher Phoenix image processing tasks include despeckle, deskew, mirror image, negative image, rename, and watermark. |
| IFB | Dispatcher Phoenix’s Index Form Builder (IFB) allows end-users to create custom displays for the MFP for document indexing, processing, and folder browsing. |
| LDAP | Lightweight Directory Access Protocol (LDAP) enables you to locate organizations, individuals, and other resources such as files and devices on a network, whether on the public Internet or on a corporate Intranet. |
| License File | A package downloaded from the SEC website that allows you to manually register or update the Dispatcher Phoenix Software. |
| LiveFlo | Real-time workflow animations that allow you to view where your documents are in a workflow. |
| Manual Registration | The activation of Dispatcher Phoenix software or add-in(s) by visiting the SEC website and entering your Purchase Code and Lock Code or Unlock Code. |
| Metadata | A set of data that describes and gives information about files or node settings that can be used for additional document processing tasks or saved in a separate file. |
| MFP | A multi-function peripheral (MFP) is a device that performs a variety of functions that would otherwise be carried out by separate peripheral devices. As a rule, it includes at least two of the following: a printer, a scanner, and/or a copier. |
| MFP Registration Tool | The management interface for searching, finding, and registering devices. |
| MFP Simulator | A tool that simulates Dispatcher Phoenix workflows on the MFP without requiring a connection to a physical MFP. |
| Node (Workflow) | A piece or a specific process of a workflow. Nodes include collection, process and distribution activities. |
| Node Properties | The settings and customization options for a node. |
| OCR | Optical Character Recognition (OCR) is technology that transforms text in image formats into editable and searchable text, enabling file conversion and intelligent routing. |
| ODBC | Open Database Connectivity (ODBC) is a standard Application Programming Interface (API) for accessing databases. |
| Patch Code | A patch code is a pattern of parallel, alternating black bars, and spaces (a barcode), developed for use in automated scanning. When scanning the document, the patch code can be recognized and acted upon. |
| Process Node | Any document processing or manipulation task (Annotate, Highlight, Redact, Deskew, Despeckle, Merge, Split, etc.) between the Collection Node(s) and the Distribution Node(s) in a Dispatcher Phoenix workflow. |
| Purchase Code | The unique ID associated with each license of Dispatcher Phoenix. This code is used to activate, register, or deactivate Dispatcher Phoenix or an Add-In Module. |
| Registered MFP | An MFP that is configured for use in a bEST workflow. |
| Release2Me | A simple, convenient, and secure print release system unique to Dispatcher Phoenix. |
| Schedule Workflow | The process of setting up the workflow to run at a specific interval. Users have the ability to choose for a workflow to run only during a specified date range or to run the workflow indefinitely. Furthermore, a workflow can be scheduled to run on a particular day and time of the week. The scheduler can be run as a service or an application. |
| Selected MFP | The MFP currently selected for configuration, registration, deletion, or use in a workflow. |
| SMB | Server Message Block (SMB) is a network protocol used by mostly Windows-based computers that allows systems within the same network to share files, printers, serial ports and other resources. |
| SMTP | Simple Mail Transfer Protocol (SMTP) is a protocol used in sending and receiving e-mail. Users typically use a program that uses SMTP for sending e-mail and either Post Office Protocol 3 (POP3) or Internet Message Access Protocol (IMAP) for receiving e-mail. |
| Toggle Shared Status | An icon on the main application Tool Bar that, when turned on, shares the workflow. This allows any user who has access to the computer to use the running workflow and, when off, is no longer shared to other users who have access to the computer. |
| Transition | The action of a file moving from one process to another. There can be more than one transition out of a single process/node in a workflow. |
| Unlock Code | This is a represents the system that Dispatcher is installed on and is not generated until the software is installed. The unlock code is used in the event you need to transfer a Dispatcher Phoenix license. |
| Validate | A process that checks the accuracy of your workflow or index form to ensure all of the fields and settings needed to run the workflow are accounted for. |
| WebDAV | Web-based Distributed Authoring and Versioning (WebDAV) allows users to collaboratively edit and manage files on remote web servers. WebDAV is a protocol that is an extension of the Hypertext Transfer Protocol. |
| Workflow Services | The background task that enables Dispatcher Phoenix to automate your document processing workflows. |
Dispatcher Phoenix Web
| Word | Definition |
|---|---|
| Active Node | The cluster server that currently owns cluster group resources and responds to network requests made to those services. |
| Batch | A group of documents that are processed in a scan operation. |
| Batch Indexing | An indexing process for a large volume of documents. |
| Batch Processing | Processing a large volume of documents, generally into a few files or one file, using an intelligent capture software application to process the scanned or captured file(s). |
| Batch Scanning | A scanning process for a large volume of documents. |
| Bubble Sheet Generator | A time-saving tool for educators to create and manage Bubble Sheet tests and templates. |
| Card Registration | An admin tool used to register user ID cards (e.g., HID Proximity, iCLASS and MIFARE etc.) with an organization’s Directory Server. Once the card is registered, the card can be used at MFPs and provide Single Sign-On user authentication to Dispatcher Phoenix. |
| Cluster | A group of two or more replicated servers (also known as “nodes”) that are deployed to increase the availability, reliability, and/or performance of the group over that provided by a single server. Once joined together in a cluster, the nodes remain in constant communication. |
| Document Separation | The process of dividing images/files in the batch into documents. Dispatcher Phoenix Workstation supports the following document separation methods: Page Count, Blank Page, Barcode, Patch Code, or None (creates a single document). |
| Failover | The process of moving resources from one server to another in the case of failure. Using an Active/Passive configuration, a passive server remains in standby mode, waiting for the active server to fail. If the primary server becomes unavailable because of failure or maintenance, the passive server immediately takes control of the cluster resources and services. Failover occurrs within a failover cluster. |
| Failover Cluster | A cluster designed to provide failover services (if a failure occurs on the primary member of the cluster, the primary server’s resources will automatically restart on another server that is also a member of the cluster). |
| Heartbeat | A network “packet” sent at a regular interval between nodes in the cluster to confirm that they are still online. |
| Load Balancing | Distributes the processing and traffic evenly across all servers in a cluster, or server “farm”. |
| Offload Server | A server designed to collect and complete labor-intensive tasks, such as OCR, in order to increase the efficiency of the primary server. |
| Node (Enterprise) | A server that is part of a cluster. |
| Passive Node | The cluster server that does not currently own cluster group resources but is available if the active node fails. |
| Sharing | The ability to manage access to workflows in Dispatcher Phoenix Web for specific users and/or user groups. |
| TWAIN | Scanning protocol connecting scanners with applications on personal computers. |
| Verification | The process of verifying documents for quality assurance purposes prior to routing to long-term storage. |
| Workstation | A dedicated scan station that supports any manufacturer’s high-speed TWAIN scanning devices. The Workstation application allows a user to auto-separate documents by number of pages, blank pages, barcodes, or patch codes in a real-time display. Workstation provides pre and post-scan options that allow scan operators to reorganize scanned documents and manipulate pages (reorder, rotate, flip, rescan, insert, etc.) using drag-and-drop functionality. |
Back to top