Scheduled Tasks

The installation program sets up the scheduling of external tasks that are run during off-hours. You can view completed tasks by using Windows Explorer and navigating to the Tasks folder under your system folder (WINDOWS or WINNT, depending on the operating system).

Your installation may not use all scheduled tasks listed in this topic and may require additional items to be activated and set up.

Refer to the Financial Institution Administrator Guide for more information.

Modifying Scheduled Tasks

If you need to change the scheduled times of any task,

From a command prompt or Run prompt,

Type taskschd.msc.

Click Task Scheduler Library > IMM.

Task Scheduler

  • AdHocDocs:

    This utility downloads Adobe Sign completed documents without using eSign. This tool is used to download signed, ad-hoc documents from the Remote Signature server to the eSign server.

  • eSign ADUsers Sync:

    This utility synchronizes user information with the following information listed their associated Active Directory listing.

    • Name
    • User Email
    • Manager
    • Group Association
    • Permissions

    By default, this task is scheduled to run once a week, every Sunday at 10 AM.

  • eSign Merge Service Restart: This utility restarts the iDocmerge Service.

  • TeAPurge:

    Note:

    This utility should only be run during off hours. Running this utility during business hours may affect the eSign server performance. Contact support for assistance regarding multiple daily purges.

    This utility is a generic clean-up utility, which removes several of the items that can grow with time and cause performance issues. It is a multi-threaded utility and performs most efficiently on a multi-processor server. In its default configuration, it processes all threads concurrently.

    The utility is scheduled to run each day at 3:00 AM, which allows enough time to finish processing before business hours. This time can be adjusted by editing the task.

    The processes that it performs are:

    1. Removes old saved sessions. This setting can be modified for each Financial Institution. This is accomplished by setting the Retain Active Sessions (Days) setting for the each FI, which may be set from 1 to 90 days. It will remove both the database records and the files related to the obsolete sessions. If you set Retain Active Sessions (Days) to 90 days, TeAPurge will delete sessions older than 90 days.

    2. Removes audit trail information. This is controlled for each Financial Institution in the Retain Audit Trail setting, which may range from 90 to 360 days. This process removes old rows from the database in several tables that are used to hold history information.

    3. Moves documents from the ArchivedDocuments table to the ArchivedDocumentsHistory table. When documents are archived, a physical copy is stored in the Archive folder and a database entry is made in the ArchivedDocuments table.

    4. Documents are retained in the ArchivedDocuments table based on the Retain Archived Docs (Days) setting (between 30 and 360 days) at which time the database entry is moved to the ArchiveDocumentHistory table.

    5. Documents are retained in the ArchiveDocumentHistory table based on the Retain Archived History Docs (Days) setting (between 30 and 2,555 days). Based on your settings, it is possible for files to remain searchable up to 8 years.

    6. Removes files in each FI's Temp, Error and ArchiveOther folders, based on internal settings. Error files are retained for 30 days, while files in the other two folders are retained for up to 24 hours. (For troubleshooting purposes, these settings may be changed by IMM Support.)

    7. Removes documents from the AddOnArchivedDocuments table if they have been marked as Sent, based on the Retain Archived Docs (Days) setting (between 30 and 360 days). Removes files in each FI’s ReturnDocuments folder if they have been marked as Sent and Delete Archived History Files is checked. (Refer to the Administrator Guide [FI Settings - Archive Tab] for settings.)

    8. AuditHistory rows are deleted based on the DELETE_TRAIL_DAYS setting. [This setting may be changed by IMM Support. Default: 365 days].

    9. DocSessionDetails rows are deleted only if there are no remaining AuditHistory rows (item 8) that are associated with a DocSessionDetails row. DocSessionDetails rows will be deleted when their age in days is greater than the maximum of any of the following four values:

     

    1. 365 days

    2. DELETE_ARCHIVE_DAYS

    3. DELETE_DOC_SESSION_DETAILS_DAYS

    4. DOCQ_DELETE_AFTER_DAYS.

    In this manner, a DocSessionDetails row will never be deleted before its associated Archive, Session, or Pending Web Transaction.

    1. Deletes expired sessions from the TeAASP database.

    2. TeAPurge will log an error in the Eventviewer in the case of a database size overflow error.

    3. When Archive on Session Expiration (Completed Sessions) is checked, IMM eSign will automatically archive sessions that have signature capture complete before they are purged.

    4. Based on Download Documents for Sessions Status (Days), physical, archived documents, which have been indexed, will be deleted. Corresponding database records will not be modified.

  • TeAWebDownload:

    This is a utility which is installed during the server component installation. It downloads signed, completed documents from the document delivery system only if Remote Signatures (HostAdmin) is activated. Files are stored in each Financial Institution’s Archive folder.

    The utility is scheduled to run each day at 2:00 AM, which allows enough time to finish processing before business hours. This time can be adjusted by editing the task.

  • TeAWorkflowPurge:

    A task for this utility is created during the eSignPlus add-on installation.

    During scheduled operation, only sessions with completed or cancelled status will be deleted.

    Sessions in active state will continue to exist in workflow, even after the eSign purge limit has been reached. The documents for all active sessions existing past the purge limit are also not deleted.