The Interpreter Manual Item Import feature allows manual item information that is captured outside of the FastTrack360 system to be imported into interpreted timesheets.
The manual items are imported via an import batch process, which applies the manual item data to identified interpreted timesheets within the Interpreter Review module. The import batch process consists of the following general steps:
Uploading the import file.
Defining the field mapping.
Queuing the import batch for processing. Each of these steps is described in more detail below.
Uploading the Manual Item Import File
The import batch process is initiated by uploading an import file, which contains the data that will be used to create manual items in interpreted timesheets that have not been reviewed. The import file must be formatted so the system can read the file and its content. For example, the first row of the import file must contain column headers that can be mapped to FastTrack interpreted timesheet manual item. For more information, see Import File Format Validation.
Defining the Field Mapping
If the format of the import file format is valid the system will read and display the column headers from the import file. The column headers must be mapped to the corresponding interpreted timesheet manual item fields to inform the system what data is supplied in the import file and what that data corresponds to within the FastTrack system.
A set of field mappings that are configured when importing an import file can be saved as a template, which can be applied whenever an import file that originates from the same source is processed in the future. This prevents the need to manually configure the field mapping each time an import is processed. For more information, see Saving Field Mapping Templates.
Queuing the Import Batch for Processing
Once the field mapping has been configured it is possible to queue the interpreter manual import batch for processing. On attempting to queue an import batch for processing, the system performs field mapping and data type validation to ensure that manual items can be theoretically created based on the mapping and types of data provided within the import file. For more information, see Field Mapping & Data Type Validation.
If the validation succeeds the import batch is sent to the Process Queue, where the batch undergoes processing. The amount of time that it takes for a queued batch to complete processing depends on a number of factors such as the following:
the number of prior import batches already queued for processing the number of individual rows within the import file.
When processing of an import batch is completed, the following occurs:
any manual items that can be successfully created based on the data in the import file are created in the related interpreted timesheet where the timesheet is ‘Not Reviewed’.
the status of the batch is set to Completed or Completed with Exceptions.
Once the processing of an import batch is completed you can do the following:
download the original import file
download the exception report that identifies the rows from the import file that failed to import successfully and the exception reasons that explain why each exception row failed to import
download the validation report that identifies all rows from the import file that imported successfully
view the import batch audit information.
If a system error occurs when an import batch is queued for processing the status of the batch will be set to Failed and no manual items will be created in interpreted timesheets in Interpreter Review. If this occurs, you will need to process the original import file as part of a new manual item import batch.