Navigation: Floria Batch Jobs > Welcome >

Batch Job Details

Previous Next

 

 

 

Use this screen to record details about a batch job.

 

Working Folder
The working folder is where files related to the batch job will be saved. Default location is "C:\Logs", which is also the default location for the IrisBG command line tool Iris3task.exe logfile. More details about the Iris3task.exe command tool can be found in the IrisBG help file.

IrisBG Logon Name and Password
Please note that "Single Sign On" does not apply for batch jobs. Username and password must always be given.

Collection ID
Click on the button to target one or multiple collection sites with one job.

Job Type

Import Data
Import data will execute the irisBG Command Tool Iris3task.exe. For more details about optional parameters for Iris3task.exe , please consult the IrisBG help file.

Other import data options are:

Autocommit data to IrisBG (If the data is without any errors, it will automatically be accepted into the system).

Attach datafile to email on error (The failed data file will be sent as an attachment by email).

Retry on fail when row count <= {number} (If the import fails, the system will remove failed rows and try again. This feature is only supported for database import or csv files).

Column mapping (csv).
A column mapping file contains two rows for mapping column names from the source to IrisBG column names.
                    Row one contains the column names used in the original file.
                    Row two contains the matching IrisBG column name.
There is no need to include columns that have the same name in the the source and IrisBG.

Upload to Web Explorer
Upload to Web Explorer will execute the irisBG Command Tool Iris3task.exe. For more details about optional parameters for Iris3task.exe, please consult the IrisBG help file.

Export Data
Run a report with a predefined report filter via the IrisBG Command Tool Iris3task.exe. Report filters was introduced in IrisBG version 3.5.5, January 2016.

App Manager
Send data from the Floria Handheld App (formerly IrisBG Handheld) Service to the Desktop Inbox and upload data to the Floria App Service at regular intervals.

Custom
 Please include a full path to the executable file, including parameters.

Data Source / Data Processing

File Data Source
Use the wildcard symbol (*) as part of the filename to process multiple files. Example: c:\MyImportFiles\*.xlsx
Wildcard symbols are supported for files only. If you would like to process multiple folders, make a new copy of the batch job, and change the folder name.

Database Data Source
You may use the following parameters in the Data Query to dynamically filter out records based on previously processed jobs.

{JobName}

{JoblastSuccessAnsiDateTime}*

{JobLastExecutedAnsiDateTime}*

*The Ansi Date Time Format is on the form yyyy-MM-dd HH:mm:ss and is compatible with most modern database platforms.

Split data when record count exceeds
When importing images, we recommend that this value is set to 100, especially if you are loading very high resolution images.

Cancel when record count exceeds
This can be used as a check to ensure that a data query that returns abnormal amount of records are not processed any further.

Email Notification

Email Notification
You can use built-in parameters to construct topic and email messages (Click "<-Template" to preload topic and message).

Topic example : Floria Batch Job "{jobname}" was completed at "{jobfinishedtime}" (result = {jobresult})

Parameters available for email topic and message are:

{JobName}

{JobStartedTime}

{JobFinishedTime}

{JobResult} : "Success", "Failed", "Processed". The outcome of custom jobs are unknown. They will be given status "processed"

{JobCount} : The number of records processed. Only available when a database data source is used.

{JobId} : JobID is constructed of jobname + # + date + Time: Example: "IMAGE_IMPORT#20151201_170105"

{JobFilename} : The full filename used for processing of this job. Data import job file example: "IMAGE_IMPORT#20151201_170105.csv"

 

 

 

 

© 2020 Botanical Software Ltd - www.botanicalsoftware.com