Please enable JavaScript to view this site.

thankQ Help

There are a number of tasks that need to be automatically run on a periodic basis so that your database is kept in pristine condition and periodic updates are maintained as required. These tasks are maintained by a series of regularly run SQL Server jobs. These jobs are usually timed to be run overnight.

Job

Detail

Default Scheduling

ThankQ Server (Action Rules)

Action Rules - Automatically creates new actions based on the rules that have been set in the Enquiry module.

5.45am daily or as otherwise agreed

ThankQ Server (Auto Close Open Orders)

Auto Close Open Orders - Sets all open orders to the Despatching stage in accordance with the settings in the Lookup Value Days until Order Auto Closes.

6.45am daily or as otherwise agreed

ThankQ Server (Automation - Maintain 6 months Audit Trail)

Automation - Maintain 6 months Audit Trail - Maintains an Audit Trail in Automation Logs for a period of 6 months. Any records older than 6 months are deleted.

6.00am daily or as otherwise agreed

ThankQ Server (Batch Approval Fundraising Stats)

Batch Approval Fundraising Stats - Sets the following for all batches that were approved approved since this job was last run:

New, Existing and Recovered statuses

Rank (for Campaign/Prospecting)

Source Code Statistics

Contact Form Fundraising Statistics

6.30am daily or as otherwise agreed

ThankQ Server (Blank HH Salutations)

Blank HH Salutations - Ensures that records which don't carry household salutations such as members and organisations have these fields set as blank.

5.30am daily or as otherwise agreed

ThankQ Server (Cancel Adjusted Invoices)

Cancel Adjusted Invoices - Cancels invoices if the amount for a payment is adjusted or if a pledge has been written down/canceled.

6.00am daily or as otherwise agreed

ThankQ Server (Clean Logs)

Clean Logs - Automatically clears the logs from the Automation Scheduler, Affinity/Moves Rules and the thankQ Error Log if they are more than a few months old.

6.50am daily or as otherwise agreed

ThankQ Server (Clear DATAIMPORTLOCAL)

Clear DATAIMPORTLOCAL - Removes data from temporary tables in the database. This helps improve the performance of the thankQ database.

6.00am daily or as otherwise agreed

ThankQ Server (Clear Out Power Search Result)

Power Search Results - When running a Power Search in thankQ, the results are stored in a special results table i.e. POWERSEARCHRESULT. Results are categorised in this table according to thankQ user name and machine name.

When running a Power Search, thankQ automatically deletes the previous results for that thankQ user and machine name and replaces them with the new set. We need this job to remove redundant results e.g. ones for users that have since stopped using thankQ.

6.00am daily or as otherwise agreed

ThankQ Server (Contact Activity Consolidated View)

Contact Activity Consolidated View - Updates the list of Contact Activity Records that are found in the Contact Activity tab in thankQ.

The number of records that are retained in this tab can be changed via the Lookup Values. See Consolidated Activity Tab - Show N Years Info for a list of record categories that you can change retention times for.

5.30am daily or as otherwise agreed

ThankQ Server (Continuous Instalments)

Continuous Instalments  If a Pledge is flagged as ‘continuous’ then it is assumed that the supporter in question is to give so much money on a periodic basis until they say otherwise.

This job ensures that all the future payment instalments are maintained If a pledge is monthly it will keep 36 active instalments and if yearly it keeps 3 active instalments (i.e. it maintains 3 years). The value used to create the new instalments is based on the value of the last active instalment. The number of months can be configured in the PledgeInstalmentExtensionPeriod within the Finance folder in Lookup Values in thankQ. The job also updates the donor statistics, which appear on the fundraising tab of the contact form, to reflect the changes being made to the pledges.

5.45am daily or as otherwise agreed

ThankQ Server (Date Fired Actions)

Date Fired Actions – Fires preset date-fired actions based on a set of rules set up in the Date Fired Actions form, e.g. if the user has set a rule to fire an action such as, “to phone someone a specified number of days after a donation of more than $1000 has been received”, an appropriate action will be created as a result of the overnight run. The action will be fired next time the appropriate user logs in.

6.30am daily or as otherwise agreed

ThankQ Server (Event Contact Stats)

Event Contact Stats - Updates the statistical information associated with events i.e. the data within the EVENTCONTACTSTATS. This data analyses the last 20 events associated per contact and their statuses for each i.e. whether they declined, did attend, did not attend etc.

5.30am daily or as otherwise agreed

ThankQ Server (Event Dietary Profile)

Inserts the Dietary Profiles created in Event Contacts into the main Profile of the contact it is linked to so that a record of the Dietary Preferences of a contact is retained for potential use in future events.

5.25am daily or as otherwise agreed

 

ThankQ Server (Everyday Hero)

Special Job to import the Everyday Hero Import File. Contact thankQ Support if you would like to use Everyday Hero.

Not scheduled and does not normally run. Activated only on request.

ThankQ Server (Host Guest Management)

Host Guest Management - Deletes Event Guests if they have also been listed as Hosts, in addition this will also trim certain redundant records in the database for Host/Guest contacts.

6.05am daily or as otherwise agreed

ThankQ Server (Housing Occupants Statuses)

Housing Occupants Statuses - Updates the Housing Relationship Occupant Status for a Contact based on their profile.

5.30am daily or as otherwise agreed

ThankQ Server (Load Flo2Cash Result)

Special Job to import the Flo2Cash Results File. Contact thankQ Support if you would like to use Flo2Cash.

Not scheduled and does not normally run. Activated only on request.

ThankQ Server (Membership Management)

Membership Management - Checks the renewal date of active memberships and ascertains whether or not they have expired. If a membership has expired, then a new entry will be appended to the MEMBERSHIPHISTORY (essentially to record the membership as it was prior to modifications) and the membership status is updated to ‘Lapsed’.

The Phase will be set to Awaiting Renewal should the membership still lie within the period of grace as defined by the lookup value setting ‘Lapsed Period (Months)’ within the Membership Admin folder in thankQ. Should the membership have expired and fall outside this period then the Phase will be set to Awaiting Rejoining.

6.00am daily or as otherwise agreed

ThankQ Server (Populate BATCHITEMLOCKED)

Populate BATCHITEMLOCKED - Adds new date records to the BATCHITEMLOCKED table. This ensures that batches can always be locked at any time in the future.

6.30am daily or as otherwise agreed

ThankQ Server (Rank Statistics)

Rank Statistics - Will check that the rank statistics (for Campaign/Prospecting) have been calculated for all payments and recalculate them if this is not the case.

3.00am daily or as otherwise agreed

ThankQ Server (Recurring Actions)

Recurring Actions - An action can be flagged as recurring in thankQ. This job will check such actions to see if they have been completed. If complete, then the next action will be created according to the schedule - as defined on the Recurrence tab on the All Actions form in the Action Manager.

6.45am daily

ThankQ Server (Refresh User Data)

Refresh User Data - Refreshes all User Panel data for all users of thankQ in case it is not been refreshed.

6.45am daily or as otherwise agreed

ThankQ Server (Sponsorship Management)

Sponsorship Management – Checks the renewal date of active sponsorships and ascertains whether or not they have expired. If expired, then a new entry will be added to the SPONSORSHIPHISTORY. This entry is essentially to record the sponsorship as it was prior to modifications. The sponsorship status is then updated to Lapsed.

6.00am daily or as otherwise agreed

ThankQ Server (Tours)

Tours - Set Tour Bookings as Booked when Sub Tours have time and locations defined and volunteer resource has an allocated contact. Status of the booking must also be Tentative.

6.00am daily or as otherwise agreed

ThankQ Server (Update All GRANTMAKINGFUNDEDBREAKDOWN)

Update All GRANTMAKINGFUNDEDBREAKDOWN - Updates all Grant Making records to add Funding Breakdowns, which give detailed statistics on where the Grant Funding is going.

5.30am daily or as otherwise agreed

ThankQ Server (Update Event Finance Summary)

Update Event Finance Summary - Updates the financial information for each Event in thankQ such as the totals for each source of income (Tickets, Auctions, Donations and Sponsorships) as well as the expenses for each Event.

6.40am daily or as otherwise agreed

ThankQ Server (Update NOOFNIGHTS)

Update NOOFNIGHTS - Updates the field Number of Nights in the Assistance/Accommodation Module, based on the Arrival and Departure date.

6.20am daily or as otherwise agreed

ThankQ Server (Merged Contacts Fundraising Stats)

Merged Contacts Fundraising Stats - Re-calculates the Fundraising Statistics for contacts that were merged since this job had been run.

12.30am daily or as otherwise agreed

 

ThankQ Server (Set Do Not Mail Flag)

Set Do Not Mail

ThankQ provides a facility for the Do Not Mail From Date and Do Not Mail To Date on the Contact Form to be set in advance. ThankQ manages this through an overnight job that is scheduled to run daily on all servers that support thankQ systems. After the job has been run, the Do Not Mail checkbox will be set in accordance with the dates entered into the Do Not Mail From Date and Do Not Mail To Date.

 

Administration Lookup Values also provide a facility for users to override the Do Not Mail setting for particular mailing preferences such as receipts.  

 

Example 1: If a contact has the Do Not Mail From Date set to a previous date, the overnight job will automatically tick the Do Not Mail checkbox.  

 

Example 2: If a contact has the Do Not Mail From Date set as a future date, the overnight job will automatically tick the Do Not Mail checkbox the night before the specified date.

 

Example 3: If a contact has the To Date set to a previous date, then this overnight job will automatically un-tick the Do Not Mail checkbox.

This routine also sets Do Not Mail Lookup Values

1.If a donor has asked not to be mailed, except for a particular mailing preference, an exception needs to be setup under Lookup Values. For example, if a donor wants to receive a receipt and no other mailings, Receipt would need to be set as a parameter value under the Administration Module, Mailing, and Mailing Preference Do Not Mail Exclusions lookup value.

Mailing Preferences

Use From and Use Until Dates

2.The Use From and Use Until dates in Mailing Preferences will be changed to orange when these dates are no longer valid. This indicates that the associated preferred address is no longer applicable. In this case, the thankQ Mail Manager will use the default address if this has been set as a mailing preference.

Using Do Not Mail in conjunction with Mailing Preferences

3.When the Do Not Mail check box is ticked manually, the Use Until fields for all mailing preferences on the Mailing Preferences tab will be set to a date before today’s date. Mailing Preferences that are set up under the Mailing Preference Do Not Mail Exclusions in Lookup Values will be excluded.  If the Mailing Preference specified in Lookup Values does not exist on the Mailing Preferences tab, a Mailing Preference will be created and the address set to the Main address. This will only occur when there is no default Lookup Value for this preference. These settings need to be set up by the thankQ System Administrator.

4.Where a Mailing Preference Do Not Mail Exclusions has been set under lookup values, e.g. for Receipt. And you also have Do Not Mail mailing preference set under mailing preferences e.g. For Receipt. If you tick Do not Mail on the contact page, it will warn you that it will reset mailing preferences and that the Exclusion of Receipt will be reapplied. This means that the mailing preference receipt will receive mail.

Do Not Mail - Contact Deceased

5.If the Do Not Mail reason is set as Deceased, all mailing preferences will be displayed in orange indicating that the mailing preferences are no longer valid. Any “Mailing Preference Do Not Mail Exclusions” that have been previously set in the Lookup values will be overwritten.

Maximum Mailings per Year

6.Under Mailing Preferences, users can set the Max Mailings Per Year for each type of mailing preference. When a particular type of mailing exceeds the maximum mailings, the system will automatically set the record to Do Not Mail in the Mail Manager only and the Do Not Mail Reason as Maximum Mailing Qty Exceeded. The settings on the Contact form will not be changed.

Setting Do Not Mail when Mailing Preferences Use Until Date is not Set

If Do Not Mail is ticked, the overnight job will automatically set the Use Until date to today. This will prevent future mailings from being sent.

6.00am daily or as otherwise agreed

Maintenance Jobs

Jobs that are run only on the maintenance database and are used to support the SQL Database in the backend.

Collect DMV Data

Collects certain thankQ Maintenance data and logs it for support purposes. Requires our SQL Account to have sysadmin privileges in SQL Server.

Every 3 hours between 9:30am and 10pm or as otherwise agreed

Log Backup

Creates hourly SQL Server logs. These logs are usually stored in the following SQL Server Directory.

C:\ThankQ\SQLServer\Backup\<SERVERNAME>\<DATABASENAME>\LOG

Every hour between 2am and 12am or as otherwise agreed

Nightly Jobs

Creates daily SQL Server database backups which are normally retained for at least 7 days before being automatically deleted.

These backups are usually stored in the following SQL Server Directory.\ThankQ\SQLServer\Backup\<SERVERNAME>\<DATABASENAME>\FULL

Note that the above directory will vary depending on the way in which your database was configured.

In addition this job will also perform a number of other database maintenance procedures such as optimising database indexes and checking database integrity.

12.00am daily or as otherwise agreed