×

Message

Failed loading XML... EntityRef: expecting ';' Entity 'raquo' not defined Specification mandate value for attribute async EntityRef: expecting ';' Specification mandate value for attribute async attributes construct error Couldn't find end of Start Tag script line 1 Opening and ending tag mismatch: meta line 1 and script xmlParseEntityRef: no name xmlParseEntityRef: no name xmlParseEntityRef: no name xmlParseEntityRef: no name xmlParseEntityRef: no name EntityRef: expecting ';' xmlParseEntityRef: no name xmlParseEntityRef: no name xmlParseEntityRef: no name xmlParseEntityRef: no name xmlParseEntityRef: no name EntityRef: expecting ';' xmlParseEntityRef: no name EntityRef: expecting ';' xmlParseEntityRef: no name EntityRef: expecting ';' xmlParseEntityRef: no name xmlParseEntityRef: no name xmlParseEntityRef: no name EntityRef: expecting ';' error parsing attribute name attributes construct error Couldn't find end of Start Tag e.minHeight line 1 xmlParseEntityRef: no name xmlParseEntityRef: no name error parsing attribute name attributes construct error Couldn't find end of Start Tag links.length line 1 xmlParseEntityRef: no name EntityRef: expecting ';' xmlParseEntityRef: no name xmlParseEntityRef: no name Opening and ending tag mismatch: meta line 1 and head Opening and ending tag mismatch: img line 1 and noscript Opening and ending tag mismatch: noscript line 1 and a Opening and ending tag mismatch: img line 1 and div Opening and ending tag mismatch: a line 1 and div Opening and ending tag mismatch: img line 1 and noscript Opening and ending tag mismatch: noscript line 1 and a Opening and ending tag mismatch: img line 1 and div Opening and ending tag mismatch: a line 1 and div Opening and ending tag mismatch: div line 1 and nav Opening and ending tag mismatch: div line 1 and header Opening and ending tag mismatch: hr line 1 and li Opening and ending tag mismatch: li line 1 and ul Opening and ending tag mismatch: ul line 1 and div Opening and ending tag mismatch: li line 1 and div Opening and ending tag mismatch: ul line 1 and div Opening and ending tag mismatch: div line 1 and article Opening and ending tag mismatch: article line 1 and div Entity 'hellip' not defined Specification mandate value for attribute async xmlParseEntityRef: no name xmlParseEntityRef: no name xmlParseEntityRef: no name xmlParseEntityRef: no name xmlParseEntityRef: no name xmlParseEntityRef: no name xmlParseEntityRef: no name xmlParseEntityRef: no name xmlParseEntityRef: no name StartTag: invalid element name xmlParseEntityRef: no name EntityRef: expecting ';' xmlParseEntityRef: no name EntityRef: expecting ';' error parsing attribute name attributes construct error Couldn't find end of Start Tag a.length line 1 xmlParseEntityRef: no name EntityRef: expecting ';' xmlParseEntityRef: no name EntityRef: expecting ';' error parsing attribute name attributes construct error Couldn't find end of Start Tag mutation.addedNodes.length line 1 Specification mandate value for attribute async attributes construct error Couldn't find end of Start Tag script line 1 Opening and ending tag mismatch: div line 1 and script Opening and ending tag mismatch: img line 1 and noscript xmlParseEntityRef: no name error parsing attribute name attributes construct error Couldn't find end of Start Tag a.length line 1 Opening and ending tag mismatch: noscript line 1 and script Opening and ending tag mismatch: img line 1 and body Opening and ending tag mismatch: script line 1 and html Premature end of data in tag nav line 1 Premature end of data in tag div line 1 Premature end of data in tag header line 1 Premature end of data in tag div line 1 Premature end of data in tag div line 1 Premature end of data in tag div line 1 Premature end of data in tag body line 1 Premature end of data in tag link line 1 Premature end of data in tag head line 1 Premature end of data in tag html line 1

OpenText Correspondence Tracking

An enterprise-class solution that helps organizations track and improve coordination and communication for incoming correspondence that requires a formal response.

Organizations require a solution that will provide an easy-to-use, automated process for receiving, tracking, and responding to incoming correspondence in a way that provides timely responses, reduces backlog, and provides a full history of all interactions. OpenText Correspondence Tracking fits this by effectively tracking and improving coordination and communication for any incoming correspondence, from both internal and external sources.

The solution extends the capabilities of the Open Text Enterprise Content Management (ECM) Suite with a comprehensive offering to support the capture, tracking, and management of correspondences and related administrative tasks. Organizations use it to track all correspondence in any format and ensure that the necessary response has been made, determine how long it took to respond, and what the response contained. Significantly improve your efficiency and productivity with this comprehensive solution for tracking inbound and outbound correspondences, managing correspondence handling processes, and storing correspondence content in a secure, long-term archive.

Benefits

  • Decrease operating expenses by eliminating the need for physical storage of documents
  • Improve customer service and satisfaction through quick action and informed response to correspondence
  • Increase productivity by automating processes and removing the reliance on paper-based, manual processes
  • Reduce the risk of mismanaged information and inquiries getting lost or going astray
  • Ensure compliance to institutional regulations and policies
  • Guarantee security and privacy of information while increasing transparency at all levels of your organization

Features

  • A Correspondence Dashboard provides a single view for 1-click access to Inbox, In-Progress, Management, Search, Report and Administration features.
  • Support for multiple correspondence types (i.e. business processes) via the ability to configure an additional form to capture the process-specific metadata and an additional workflow to automate the required process steps.
  • Users can easily create and/or view references to existing correspondence that is related to the one currently being worked eliminating the need for the same (or similar) response to be re-written from scratch for multiple inquiries.
  • Metadata corresponding to workflows, attachments, and correspondents is maintained in configurable forms that are associated with workflow. Virtually all form fields can be customized.
  • Integrated scanning and fax solutions allow hardcopy and fax documents to be easily ingested into the solution. Text created by OCR is stored (and indexed) with the scanned image, allowing for full text search of scanned images.
  • An Optional DoD 5015.2 Records Management feature is available for managing incoming and outgoing correspondence as official records.

Correspondence Tracking