Scheduler Messages

The messages below are shown on Scheduler / Schedule as "Last Message" and also on Scheduler / Queue as "Message".


Completed Messages

Message

Description

Billing locked

Displays in auto_build_claims when no claims can be created because the billing records were locked when the job was run

Nothing to build!

Displays in auto_build_claims when no claims have been created

Nothing to invoice

Displays in sp / approvals / auto_post_claims when no claims have been selected to post (either because none were found or the claims did not meet the posting criteria)

Nothing to import for x day(s)

If "Warning Days" is populated, the message 'Nothing to import for x days' is recorded when the job runs and a new file has not been processed after that number of days (Glass import)


Failed Messages

Message

Description

Bad input for /sp/approvals/auto-post-claims API service

Displays in sp / approvals / auto_post_claims when a required table was locked when this job was run, so it could not be completed. The job will run again when next scheduled to do so

Duplicate column names!

If the SQL contains duplicate SELECT field names this message may appear and the job will fail to run. Column headings need to be unique in scheduler outputs or attachments. Revise query so that there are no duplicate column names

Failure executing query #. Message: Statement could not be executed (45000 - 1644 - Billing already locked!)

The executeScript job started, but could not be completed. A billing lock could not be secured for one of the scripts in the query. The script number is shown in the message. The job remains active and will run again when scheduled to do so

Fuel recharge billing locked by: {user_login}

If the billing is being edited by another person while the scheduler job is running, the job will fail. Re-run the job

Import timeout exceeded. Review timeout set in global control glass_vehicle_data_import_timeout

The scheduler job method qt / glass / import_vehicle_data will return this message if it takes longer to run than the stored timeout in the control glass_vehicle_data_import_timeout. Update the control timeout if this occurs

Import timeout exceeded. Review timeout set in global control glasses_vehicle_data_import_timeout

The scheduler job method qt / glasses / import_vehicle_data will return this message if it takes longer to run than the stored timeout in the control glasses_vehicle_data_import_timeout. Update the control timeout if this occurs

Locked by user: {user_login}

General lock message when another user has the record locked

Mail bad attachment

If the job has "Mail Attachment" set to 'Office(xlsx)', check that there is a record for 'DocumentConversion' for the role that is running the job

Import has failed. Unable to perform this action! Please try again. If the problem persists please contact your system administrator

This error can occur if the credentials stored in glass_sftp_connection are incorrect. Confirm the credentials with your Glass Account Manager

Import has failed. Validation error(s): Data - File {MmmYY}eis.zip does not exist

The scheduler job method qt / glass / import_vehicle_data will return this message if the expected Monthly data file is not available in the Glass SFTP folder. A file for the next month is normally provided around the 25th of the month (for example: On 24/07/2024, the file 'Aug24eis.zip' has been provided). If this message occurs late in the month, follow this up with your Glass Account Manager

Support has been notified. System error, Catch-e notified

Possible causes: (1) Amazon SES is your chosen email method, but you have set attachment file size too high (Amazon SES will only process email attachments up to 7.5MB); (2) qt / red_book / import_vehicle_data: one or more of the files provided by RedBook contain the wrong number of columns. Catch-e Support will be notified of the issue. This can happen if RedBook has added new columns to one of your import files and the changes have not been added to the Catch-e System. Either a code change is required to incorporate the new columns, or RedBook will need to update their files to revert to the prior format


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.

Parameter

Notes

Import type

Choose from 'Monthly' or 'Weekly'. The weekly job allows you to receive a small amount of vehicle data to enable quoting, but the monthly data contains the full suite of details you need. You will always need to have a monthly job running. Visit the Weekly page for details of how these files are selected

Filename

The file name can be left blank. The job seeks out the required file. Weekly files have the following name format: weeklyDDMMYY.zip (for example: weekly050824.zip). Monthly files have the following name format: MmmYYeis.zip (for example: Aug24eis.zip)

Warning Days

Enter the expected turnaround time for your file from Glass. This can be a value between 0-365, the default value is 0. If the "Warning Days" field is blank or '0', no alerts or warnings are ever generated. If you have a stored value, the Scheduler / Queue "Message" will show the number of days that have passed since the date of the expected file turnaround. Example 1: For a 'Weekly' file, you could enter '7': On day 6 "Message" is blank; On day 7 "Message" = 'Nothing to import for 7 days'; On day 8 "Message" = 'Nothing to import for 8 days'. Example 2: For a 'Monthly' file, you could enter '31': On day 30 "Message" is blank; On day 31 "Message" = 'Nothing to import for 31 days'; On day 32 "Message" = 'Nothing to import for 32 days'

Set-up

Configuration

Module

Table

Field

Setup / Reference Data > gb_controls

qt

gb_controls

glass_sftp_connection (Host, Port, Username, Password)


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.

Filename

Comments

WEEKLY.TXT

Summary of vehicle description, new gross price, fuel type and options

WKY78114.BRK

Brakes

WKY78114.COU

Countries

WKY78114.CYL

Cylinders

WKY78114.DRI

Drive

WKY78114.FUE

Fuel

WKY78114.STR

Steering

WKY78114.SUS

Suspension

WKY78114.VAL

Valves

WKY78114.VIL

(Vehicle Identification List)

WKY83114.OCD

Equipment

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

  1. Looks for the previous Monday's file: weekly050824.zip (Mon 05/08/2024)

  2. File cannot be found, looks for weekly060824.zip (Tues 06/08/2024)

  3. 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)

  1. Looks for Monday 05/08/2024 + 7 days = weekly120824.zip (Mon 12/08/2024)

  2. File cannot be found, looks for Monday 05/08/2024 + 8 days = weekly130824.zip (Tues 13/08/2024)

  3. 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)

  1. Looks for GlassWeek.zip

  2. 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:

Parameter

Type

Description

Query ID

Lookup

The query_id of an existing query that will produce the output for the interface file. The query normally includes the condition dirty_flag != '0000-00-00 00:00:00' to export only records that have changed. A search icon is provided to find the required query. Query ID cannot be blank

Source Table

Selection

The name of the master table (i.e. the one containing the dirty_flag field that can be reset). Sets the format for the interface file. Can be either: fm_clients, fm_contracts, or fm_drivers

Attachment Format

Selection

Choose the required format for the attachment file from 'Office(xlsx)', 'Office(xls)', 'Text (csv)', 'Text (txt)' or 'XML'. 'Office(xlsx)' is the default value and saves with an xlsx suffix. Further parameter variables are hidden if this format is chosen. 'Office(xls)' enables you to customise the presentation of the generated files. Further parameter variables are hidden if this format is chosen. 'Text (csv)' generates a text delimited file and uses the CSV (Comma Separated Variable) format. 'Text (txt)' generates a text delimited file and uses the Text (Tab Delimited) format. 'XML' generates an XML based file

Column Headings

Checkbox

If you turn this on, the first row of the output will contain column headings

Format Column Headings

Checkbox

Used in conjunction with Format Column. If you turn this on, the column headings will be formatted by replacing underscores with spaces and words will be capitalised

Separated By

Text

Sets the character(s) used to separate columns / fields in the output. For example: using the option '|' will create a pipe separated file. In the special case where {tab} is being used for the separator, all tabs in the data will be replaced with white spaces to conform to the IANA standard for TSV files

Text Delimited By

Text

Sets the character used to delimit columns / fields in the output if they contain special characters. Special characters include double quotes, newlines, and this delimiter character itself. The 'none' option will add no delimiters and is useful when the query itself adds the delimiters (for example: creating a custom interface file to specification)

Omit Final Line Break

Checkbox

If you turn this on, there will be no line break after the last row of output. This is required by some third party software for import purposes. This is turned off by default

Singleton Tags

Checkbox (XML)

If you turn this on, tags with empty values will use the singleton style format (for example: <tag/> as opposed to <tag></tag>)

Indent Size

Integer (XML)

Sets the indentation (whitespaces) used. This must be an integer between 0 and 9. The default is 2

Newlines

Checkbox (XML)

If you turn this on, all lines will end in a newline character. This improves readability when viewing or printing the XML from non-specialised text editors

DMZ Subfolder

Text

Is the subfolder in the DMZ area where your interface file will be created. If left blank, it will be created in the DMZ home folder. If the subfolder does not exist, it will be created. Subfolders can be nested. Example: 'reports/out'

Reset Dirty Flag

Checkbox

Sets the dirty_flag for all records in the Source Table to '0000-00-00 00:00:00' on successfully exporting the records