Skip to main content
Kofax

Complete list of possible TCfW Status

Summary

12462

Description

The following list holds the text and a description for each status that a message can have in TCfW. Furthermore, the attached Excel file also provides the icon that is shown for each status in TCfW.

Status List

Text Description
Screen Shot 2018-07-20 at 9.51.44 AM.png New Message No action has been performed. The message has yet to be printed or viewed. Entry cannot be marked completed
Screen Shot 2018-07-20 at 9.52.08 AM.png Touched Entry already opened. Message has been printed or viewed. You can mark the entry as completed now.
Screen Shot 2018-07-20 at 9.52.27 AM.png Sending Sending in progress
Screen Shot 2018-07-20 at 9.52.38 AM.png Active - Forwarded Sending in progress and message routed to next node
Screen Shot 2018-07-20 at 9.53.00 AM.png Inactive - Problems Message marked completed due to a send error
Screen Shot 2018-07-20 at 9.53.20 AM.png Completed Message has been sent successfully (Send entry and message not marked for automated deletion => still in ACOMINFO file.)
Screen Shot 2018-07-20 at 9.53.36 AM.png Completed Message has been sent successfully
Screen Shot 2018-07-20 at 9.53.47 AM.png Completed - Log Entry Only the log entry exists; the message itself has been deleted.
Screen Shot 2018-07-20 at 9.54.17 AM.png Cancelled Message was cancelled by the sender
Screen Shot 2018-07-20 at 9.57.45 AM.png Cancelled - Log Entry Message was cancelled by the sender. Only the log entry exists; the message itself has been deleted
Screen Shot 2018-07-20 at 9.57.54 AM.png New Message Resubmitted message. The message has yet to be printed or viewed
Screen Shot 2018-07-20 at 9.58.28 AM.png New Message (reception error) No action has been performed. The message has yet to be printed or viewed. Entry cannot be marked completed (See Reception Error)
Screen Shot 2018-07-20 at 9.59.12 AM.png Touched (reception error) Entry already opened. Message has been printed or viewed. You can mark the entry as completed now. (See Reception Error)
Screen Shot 2018-07-20 at 9.59.27 AM.png Sending(reception error) Sending in progress (See Reception Error)
Screen Shot 2018-07-20 at 9.59.45 AM.png Active - Forwarded(reception error) Sending in progress and message routed to next node (See Reception Error)
Screen Shot 2018-07-20 at 10.00.12 AM.png Inactive - Problems(reception error) Message marked completed due to a send error (See Reception Error)
Screen Shot 2018-07-20 at 10.00.50 AM.png Completed(reception error) Message has been sent successfully (See Reception Error)(Send entry and message not marked for automated deletion => still in ACOMINFO file.)
Screen Shot 2018-07-20 at 10.01.06 AM.png Completed(reception error) Message has been sent successfully (See Reception Error)
Screen Shot 2018-07-20 at 10.01.35 AM.png Completed(reception error) Only the log entry exists; the message itself has been deleted. (See Reception Error)
Screen Shot 2018-07-20 at 10.01.57 AM.png Cancelled(reception error) Message was cancelled by the sender (See Reception Error)
Screen Shot 2018-07-20 at 10.02.08 AM.png Cancelled - Log Entry(reception error) Message was cancelled by the sender. Only the log entry exists; the message itself has been deleted (See Reception Error)
Screen Shot 2018-07-20 at 10.02.26 AM.png New Message (locked) Number locking is active for this channel. (See Number Locking)
Screen Shot 2018-07-20 at 10.03.19 AM.png Sending (locked) Number locking is active for this channel. (See Number Locking)
Screen Shot 2018-07-20 at 10.07.20 AM.png Waiting No send attempts have been made yet. When sending internally this status means that the message has not been touched (viewed, printed, copied)
Screen Shot 2018-07-20 at 10.07.33 AM.png Active Sending in progress. At least one sending attempt was made. When sending internally this status means that the message was touched
Screen Shot 2018-07-20 at 10.08.08 AM.png Sending Sending in progress.
Screen Shot 2018-07-20 at 10.08.57 AM.png Active - Forwarded Sending in progress and message routed to next node.
Screen Shot 2018-07-20 at 10.09.14 AM.png Inactive - Problems Message marked completed due to a send error
Screen Shot 2018-07-20 at 10.09.46 AM.png Sent OK Message was delivered successfully (Send entry and message not marked for automated deletion => still in ACOMINFO file.)
Screen Shot 2018-07-20 at 10.09.57 AM.png Sent OK Message was delivered successfully
Screen Shot 2018-07-20 at 10.10.21 AM.png Sent OK - Log Entry Message was delivered successfully. Only the log entry exists; the message itself has been deleted
Screen Shot 2018-07-20 at 10.10.46 AM.png Cancelled Message was cancelled by the user
Screen Shot 2018-07-20 at 10.11.10 AM.png Cancelled - Log Entry Message was cancelled by the user. Only the log entry exists; the message itself has been deleted
Screen Shot 2018-07-20 at 10.11.21 AM.png Waiting Resubmitted message. No send attempts have been made yet
Screen Shot 2018-07-20 at 10.11.48 AM.png Waiting(reception error) No send attempts have been made yet. When sending internally this status means that the message has not been touched (viewed, printed, copied)
Screen Shot 2018-07-20 at 10.12.14 AM.png Active(reception error) Sending in progress. At least one sending attempt was made.
Screen Shot 2018-07-20 at 10.12.43 AM.png Sending(reception error) Sending in progress. (See Reception Error)
Screen Shot 2018-07-20 at 10.13.04 AM.png Active - Forwarded(reception error) Sending in progress and message routed to next node (See Reception Error)
Screen Shot 2018-07-20 at 10.13.27 AM.png Inactive - Problems(reception error) Message marked completed due to a send error (See Reception Error)
Screen Shot 2018-07-20 at 10.13.52 AM.png Sent OK(reception error) Message was delivered successfully (See Reception Error)(Send entry and message not marked for automated deletion => still in ACOMINFO file.)
Screen Shot 2018-07-20 at 10.18.44 AM.png Sent OK(reception error) Message was delivered successfully (See Reception Error)
Screen Shot 2018-07-20 at 10.19.14 AM.png Sent OK - Log Entry(reception error) Message was delivered successfully (See Reception Error)
Screen Shot 2018-07-20 at 10.19.28 AM.png Cancelled(reception error) Message was cancelled by the user (See Reception Error)
Screen Shot 2018-07-20 at 10.19.45 AM.png Cancelled - Log Entry(reception error) Message was cancelled by the user. Only the log entry exists; the message itself has been deleted (See Reception Error)
Screen Shot 2018-07-20 at 10.19.54 AM.png Waiting(locked) Number locking is active for this channel. (See Number Locking)
Screen Shot 2018-07-20 at 10.20.14 AM.png Sending(locked) Number locking is active for this channel. (See Number Locking)
Screen Shot 2018-07-20 at 10.20.33 AM.png Active - Forwarded(locked) Number locking is active for this channel. (See Number Locking)
Screen Shot 2018-07-20 at 10.20.52 AM.png Active(locked) Number locking is active for this channel. (See Number Locking)
Screen Shot 2018-07-20 at 10.21.07 AM.png Send Attempt A logged send attempt from the short-term archive. This means e.g. for a fax line that all cases where the distant subscriber was busy or not reacha other reason are now documented in the short term archive
Screen Shot 2018-07-20 at 10.21.27 AM.png Completed Message has been sent successfully
Screen Shot 2018-07-20 at 10.21.37 AM.png Cancelled Message was cancelled by the sender
Screen Shot 2018-07-20 at 10.21.52 AM.png Completed (See Search Too Complex)
Screen Shot 2018-07-20 at 10.22.02 AM.png Cancelled (See Search Too Complex)
 
Description
Screen Shot 2018-07-20 at 10.22.15 AM.png Log entry

More detailed information

Number Locking

Number locking is active for this channel. Since another message with the same telephone number is already active, this message is locked.

Reception Error

This icon will be used if the field TS_DOCUMENT_ERR contains information concerning a reception error, such as a partly received message.

Search Too Complex

If a search is getting too complex, TC/Archive may return entries, which do not meet all search criteria.

TC/Archive reports in all affected entries of a search result if some of the search conditions could not be resolved because too many matching strings exist in a particular volume. This may happen when using wildcards, e.g. when searching for "A*" in the text content.

The search string "A*" matches all words in the index starting with ‘A’ like "aback", "abacus", "abaft", "abalone", "abandon" etc., but there is a maximum of 100 strings whose occurrences can be combined in one search.

If the limit of 100 would be exceeded, the complete search attribute is skipped (treated as always true).

A TCfW client release 3.04.01 or higher will mark the entries, which may not meet all search criteria, with a special icon containing a question mark. In any search too complex case the result may contain more entries than the correct selection, but not less.

Keywords: Status, TCfW, Client

  • Was this article helpful?