Message
Scheduler Messages
The messages below are shown on Scheduler / Schedule as "Last Message" and also on Scheduler / Queue as "Message".
Completed Messages
Failed Messages
Qt glass importVehicleData
This job automates the import of Glass vehicle data from the Glass SFTP server.
This can also be done manually from the system menu Fleet / Import Data > Glass Data.
Go to the Glass Data page for details about this process and for set-up steps.
Parameters
These are the parameter settings that are available for this job method.
Set-up
Qt glass importVehicleData Weekly
By arrangement with Glass, weekly files can be supplied. In this case, set up a second weekly job.
The weekly import process is less extensive than the monthly import process and is intended to get a new variant record in place so that quoting can begin.
Warning: Make sure you keep the monthly import job running. The weekly file is a small data update to update pricing and configuration changes that cannot wait until the next monthly update. New makes are only created when the monthly job is run.
Weekly File Import Notes
If the import file contains new variants and there is no Make record in the system, these records will be skipped. New Make records are created in the Monthly Import process
Weekly Files
The weekly files supplied are shown below. Your file list may vary depending on your arrangements with Glass.
Weekly File Name
The job parameter for Filename can be left blank.
Glass generates their weekly files each Monday with the following name format: weeklyDDMMYY.zip (for example: weekly050824.zip).
Weekly File Selection Rules
The scheduler job uses the following logic for selecting a file to import:
Scenario 1: Filename is blank - First Time Importing
Today is Wednesday 07/08/2024, Filename is not specified, no files have ever been imported
Looks for the previous Monday's file: weekly050824.zip (Mon 05/08/2024)
File cannot be found, looks for weekly060824.zip (Tues 06/08/2024)
File cannot be found, stops process
Scenario 2: Filename is blank - Subsequent Imports
Today is Wednesday 07/08/2024, Filename is not specified, last imported file is weekly080824.zip (Mon 05/08/2024)
Looks for Monday 05/08/2024 + 7 days = weekly120824.zip (Mon 12/08/2024)
File cannot be found, looks for Monday 05/08/2024 + 8 days = weekly130824.zip (Tues 13/08/2024)
File cannot be found, stops process
Scenario 3: Filename is Populated
Today is Wednesday 07/08/2024, Filename is GlassWeek.zip, last imported file is weekly080824.zip (Mon 05/08/2024)
Looks for GlassWeek.zip
File cannot be found, stops process
Catch-e Staff Notes
When a file has been imported, the audit records for the import can be found in the audit table.
Interface Query Incremental
This job type is used to export data from one of the source tables for all the records that have changed since this job last ran. To do that it uses a special timestamp field called the dirty_flag. Each time a record is edited and saved, the dirty_flag is set to the current system time. To find only these records, you can add the following condition to your query:
dirty_flag != '0000-00-00 00:00:00' You can optionally set the dirty_flag on completion by checking on the Reset Dirty Flag option. This allows you to create multiple jobs for the same source table, only resetting the dirty_flag in the final job.
The interface file is saved in the DMZ Subfolder you define. Once in your DMZ it can be accessed using FTP by external applications. The interface file will be named by concatenating the Source Table name with the current timestamp (YYYYMMDDHHMMSS) separated by a full stop (period) to give a unique name, for example:
fm_clients.20130127153201 Warning: Any existing locks on the source table will be removed together with the associated sessions to guarantee a table lock can be acquired. This will cause those users to be thrown back to the login screen. Therefore this scheduler job type should only be used out of office hours.
Parameters
The Scheduler Job Screen has the following input parameters: