To Do Entry Processes

These are background processes whose main purpose is to generate To Do Entry records based on a certain condition. Refer to To Do Entries Created By Background Processes for the details. The section that appears below simply lists these processes.

*Batch Control ID*	*Program Name*	*Description*	*Multiple Threads*	*Extra Parameters*	*Records Between Commits / Minutes Between Cursor Re-Initiation*
C1-RGSTL	Java	This background process creates a To Do entry for registration forms that have been in a given status for too long.	Yes	MAX-ERRORS	N/a / N/a
C1-TXSTL	Java	This background process creates a To Do entry for tax forms that have been in a given status for too long.	Yes	MAX-ERRORS	N/a / N/a
TD-BCUPL	CIPQBCEB	This background process creates a To Do entry for every billable charge upload record that's in error.	No	MAX-ERRORS	200/15
TD-BIERR	CIPQBIEB	This background process creates a To Do entry for every bill that's in error.	Yes	MAX-ERRORS	200/15
TD-BSERR	CIPQBSEB	This background process creates a To Do entry for every bill segment that's in error.	Yes	MAX-ERRORS	200/15
TD-BTERR	CIPQBERB	This background process creates To Do Entry for any other batch processes that ended in error. A To Do Entry is only created if one does not already exist.	No	MAX-ERRORS	200/15
TD-CCCB	CIPQCCCB	This background process creates a To Do entry for customer contacts that have been flagged to generate a To Do entry on a future date. Note well, most To Do background processes create To Do entries in the pending state. If the customer contact indicates a specific user should be notified (as opposed to notifying a group of users - a role), the To Do entry will be created in the being worked state and it will be assigned to the designated user.	Yes	LEAD-DAYS = Number of days before the customer contact's reminder date that the To Do entry should be created. Valid values of 0 to 99 are acceptable. MAX-ERRORS	200/15
TD-CLERR	CIPQCLEB	This background process creates a To Do Entry for any batch process that has root objects that created an error. A To Do Entry is only created if one does not already exist.	Yes	MAX-ERRORS	200/15
TD-DTCST	CIPQDTCB	This background process creates a To Do entry for deposit control staging / tender control staging records that are in error.	No	MAX-ERRORS	200/15
TD-MODTL	CIPQODMB	This background process creates a To Do entry for every disputed match event	Yes	NO-OF-DAYS = Number of days old the match event must be before a To Do entry is created (this prevents young entries from appearing on To Do lists) MAX-ERRORS	200/15
TD-MONTL	CIPQONMB	This background process creates a To Do entry for every open, non-disputed match event	Yes	NO-OF-DAYS = Number of days old the match event must be before a To Do entry is created (this prevents young entries from appearing on To Do lists) MAX-ERRORS	200/15
TD-NOBC	CIPQNBCB	This background process creates a To Do entry for every account that doesn't have a bill cycle but has active obligations.	Yes	MAX-ERRORS	200/15
TD-PYERR	CIPQPAYB	This background process creates a To Do entry for every payment that's in error or that is unfrozen.	Yes	MAX-ERRORS	200/15
TD-PYUPL	CIPQPYUB	This background process creates a To Do entry for every payment staging record that's in error.	No	MAX-ERRORS	200/15
TD-UNBAL	CIPQPYEB	This background process creates a To Do entry for every payment event that's unbalanced.	Yes	MAX-ERRORS	200/15
TD-XAIUP	CIPQXAUB	This background process creates a To Do entry for every XAI Upload Staging in error.	Yes	MAX-ERRORS	200/15

Please refer to Column Descriptions for more information on the columns used in the table above.