JOBS.AVALOQAGENT.FETCHAVALOQTASKS

You use JOBS.AVALOQAGENT.FETCHAVALOQTASKS jobs to generate Automation Engine Jobs out of existing tasks from the target Avaloq system. JOBS.AVALOQAGENT.FETCHAVALOQTASKS jobs query for tasks in the Avaloq database and generate an XML file with the Avaloq task data that you then import into the Automation Engine.

For information about the Automation EngineImport/Export function, please refer to the official Automic Automation documentation at Using > Designing > Working with Objects > Importing and Exporting.

To Create a JOBS.AVALOQAGENT.FETCHAVALOQTASKS Job

You create jobs in the Explorer list in the Process Assembly perspective.

Do one of the following:
- Click the Add Object button in the toolbar
- Right-click anywhere in the list and select Add Object.
On the Add Object dialog, do one of the following:
- In the Search field, start typing the type of object you want to create.
- Expand Job (JOBS) > AVALOQAGENT and select the type of job that you want to create.
Click the Add button. The Object Name dialog is displayed.
Enter a descriptive Name. Optionally, enter a short and descriptive Title that helps you recognize the purpose of the object.
Click OK.

The Avaloq job is created and available in the Explorer list and a new page opens to the Fetch All Avaloq Tasks tab.
In the Connection Settings section, in Avaloq Instance select the Connection object that will establish the communication between the Automation Engine and your Avaloq system.
In the Generate Import File for Avaloq Tasks section enter the following:
- Template File
  
  Name and path of the XML file to be used for generating the Automation Engine jobs is stored.
  
  When you execute the JOBS.AVALOQAGENT.FETCHAVALOQTASKS job, this template is created. It contains the structure expected by the Automation Engine for importing it.
  Note:
  - The first two lines and the last line in this file are used as header and footer in the output file respectively.
  - This file must be stored on the host where the Avaloq Agent runs.
  Example
  
  Automic/AvaloqAgent/Avaloq_Template_Job.xml
- Output File
  
  Name and path of the XML file that the JOBS.AVALOQAGENT.FETCHAVALOQTASKS will create and that can be then imported into the Automation Engine system. This output file is stored on the host where the Avaloq Agent runs.
  
  Example
  
  tmp/Avaloq_Export_Jobs.xml
- Avaloq Task Name / Avaloq Internal Task ID Filter
  
  SQL standard query to identify the Avaloq tasks for which the JOBS.AVALOQAGENT.FETCHAVALOQTASKS job will create Automation Engine jobs. You can use the following keywords for filtering Avaloq jobs:
  - @TASKINTLID#
  - @TASKID#
  - @DESCRIPTION#
  - @CONNECTION#
  - @DATE#
  - @TIME#
  If you leave this field empty, Automation Engine jobs are created for all available Avaloq tasks.
  
  Example
  
  Enter %EOD Performance% to generate Automation Engine jobs for all Avaloq tasks whose names contain EOD Performance.
- Target Connection
  
  Connection object that establishes the communication between the Avaloq system from which you export the Avaloq jobs and the target Avaloq Agent solution where you want to import the generated output file.
  
  Example
  
  You may want to generate the XML file from your TEST environment and, after validating the results, import the jobs into your PROD system. In this case, you enter the Connection object used with the PROD system here.
- Business Unit ID
  
  Avaloq Business Units from which the JOBS.AVALOQAGENT.FETCHAVALOQTASKS job will generate the corresponding Automation Engine jobs.
  
  If you leave this field empty, the Avaloq tasks will be taken from all available Business Units.
Go to the Attributes page. In the Execution Settings section, select the corresponding Avaloq Agent.
Go to the Rapid Automation tab to configure the job reporting options. For more information, see Job Reports and Optional Reports.