AX1672
Scheduler task: Web Report Processing
This task performs multipass processing on a web report. The report is processed over a dimension with a filter automatically applied to limit the data in the report to the current dimension value. The result of each pass is either a PDF or Excel output file, which can be saved to a designated folder location and/or emailed.
IMPORTANT: Only web reports created from product-delivered templates can be processed by this task. Consult the separate product documentation for more information on any web report templates delivered with your product. Web reports that were created in the Report Builder cannot be processed at this time.
General task properties
The general task properties at the top of the task settings determine the report to process.
Item | Description |
---|---|
File to Process |
The web report to process for the task. Click the Browse button to open the Axiom Explorer dialog, and then select a report to process. You can select any template-based web report that you have access to within the Reports Library. Only one report can be selected for each File Processing task. If you want to process multiple reports, you can add multiple File Processing tasks to the Scheduler job. TIP: Once the file is selected, only the file name displays in the task. If you want to know the folder location of the selected file, hover your cursor over the field. The folder location is listed in the tooltip. |
Override file to process |
Optional. Specifies a Scheduler job variable to override the file to process. The override file will then be used for processing instead of the original file. This feature allows you to pass in an alternate file to process, when using Run Event or Raise Event to trigger the Scheduler job for processing. To use a job variable, enter the variable name in curly brackets, such as NOTES:
|
Advanced options
When the task is configured to output multiple files (File Generation is set to Multiple Output Files), then multiple passes can be separated into sub-jobs, which can then be processed at the same time. This parallel processing can improve the performance of the task.
For example, imagine that you are multipass processing a report by department. If the task is processed sequentially, then the task would process Dept 100 and finish it, then move to Dept 110 and finish it, and so on. When parallel processing is used instead, Depts 100-199 can be separated into one sub-job, Depts 200-299 into another sub-job, etc. Because the sub-jobs are processed in parallel, multiple departments are processed at the same time, so the overall task can complete more quickly.
Item | Description |
---|---|
Maximum Parallel Jobs |
The maximum number of subordinate jobs to run in parallel. The default number is 4. This is the total number of sub-jobs that can be run at the same time for this task. Ultimately the number of sub-jobs that are run in parallel depends on the number of Scheduler threads that have been configured for use at your organization, and the number of Scheduler threads that are currently available (threads that are not processing other higher-priority jobs). |
Processing Batch Size |
The number of multipass passes to include in each sub-job at a time. The default number is 10. Passes are determined based on the multipass list of items. For example, if you are processing by department (DEPT.DEPT), then each department is a separate pass. If the batch size is set to 10, then each sub-job would process 10 departments at a time. In most cases, the default settings are sufficient. If you are experiencing lengthy processing times and want to optimize performance, you can adjust this setting as follows: divide the number of passes by the number of available Scheduler threads. For example, if there will be 100 passes and there are 4 Scheduler threads, set the batch size to 25. |
NOTE: There is no way to disable parallel processing if the task is eligible; however, you can adjust the parallel processing settings if desired.
Report processing properties
The report processing properties in the middle of the task settings determine the output of the task.
Item | Description |
---|---|
Processing Type |
Select one of the following to determine the output format of each pass:
|
Save or Email Files |
Select one of the following to determine the delivery method for the output:
|
File Generation |
Select one of the following to determine whether the output is saved as a single file or multiple files:
|
File Name |
Specify how the output file (or files) should be named. You can do the following:
If the task will generate multiple output files, then the file name (or the output folder path) must use a processing variable so that the output of each pass is unique. If the task will generate a single output file, then variables are not required. To use a processing variable, you can type the variable or you can click the pencil icon For example, you could set the file name to NOTE: Processing variables and Scheduler variables use different syntax. Processing variables are enclosed in square brackets. Scheduler job variables are enclosed in curly brackets. |
Sheet Name |
Specify how the sheet for each pass should be named. This property only applies when the processing type is Export to Excel. You can do the following:
If the task will collect all of the output into a single spreadsheet file, then the sheet name must use a processing variable so that the output of each pass is unique. If the task will generate multiple output files, then variables are not required. To use a processing variable, you can type the variable or you can click the pencil icon For example, you could set the sheet name to NOTE: Processing variables and Scheduler variables use different syntax. Processing variables are enclosed in square brackets. Scheduler job variables are enclosed in curly brackets. |
Export to Excel Settings
Complete the following properties if the processing type is Excel.
Item | Description |
---|---|
Include Column Headers |
Specifies whether column headers are included in the file output. By default this is set to On, which means column header text is included in the first row of the spreadsheet. Column grouping headers and multi-row headers are not included. If this option is set to Off, then column headers are omitted from the file output and the data starts in the first row of the spreadsheet. |
Include total row |
Specifies whether the total row is included in the file output. By default this is set to On, which means that the total row is included in the spreadsheet. If this option is set to Off, then the total row is omitted from the file output. NOTE: This option only applies when the web report being processed is a dynamic row report with the total row enabled. If the web report being processed uses a fixed row structure, then the total and subtotal rows defined in the fixed row structure are always included in the spreadsheet. |
Export to PDF Settings
Complete the following properties if the processing type is PDF.
Item | Description |
---|---|
PDF Orientation |
Select the orientation for the PDF, either Portrait or Landscape. Portrait is the default orientation. |
Page Size |
Select the page size for the PDF. You can choose from the following standard page sizes: A3, A4, A5, Legal, Letter, or Tabloid. Letter is the default size. |
Output File Settings
Complete the following properties if file output is being saved. These settings do not apply if the output is email only.
(missing or bad snippet)Email Settings
Complete the following properties if file output is being emailed. These settings do not apply if the output is saved only.
Item | Description |
---|---|
Recipient column | Optional. Specify a table column that holds the desired email recipients for each pass. This option only applies if File Generation is set to Multiple Output Files, so that each pass will be sent a separate email. You can type the name of a table column, or click the column button The specified column can contain any of the following: email addresses, user login names, and/or role names. The column can contain multiple values separated by a semicolon. The recipients listed in the column will be used as the To address for the email (in addition to any recipients listed directly in the To field). If the column contains a user login name, that user's email address as defined in security will be used. If the column contains a role name, the email will be sent to all users in the role. To verify that the recipient column will resolve as you expect for each pass, you can click the Preview Multipass List button in the Multipass Data Settings section. The specified recipient column displays in this preview so that you can see the recipient column values associated with the multipass column values. NOTE: The recipient column must have a one-to-one relationship with the values in the specified multipass column. |
To | Specify the To recipient(s) for the email. This is required if a recipient column is not specified. If a recipient column is specified, the recipients listed here will be added to the recipients listed in the column for each pass. You can type one or more email addresses, user login names, and/or role names. Separate multiple recipients with semicolons. If a user login name is listed, that user's email address as defined in security will be used. If a role name is listed, the email will be sent to all users in the role. NOTE: If File Generation is set to Multiple Output Files, the recipients in the To field will receive a separate email for each pass. The only way to dynamically send the emails to different recipients per pass is to use the Recipient Column option. |
CC | Optional. Specify the CC recipient(s) for the email. This field follows the same rules as the To field. |
BCC | Optional. Specify the BCC recipient(s) for the email. This field follows the same rules as the To field. |
From | Select one of the following to specify the From address for the email:
|
Subject Line | Enter the subject line for the email. Processing variables can be used in the subject line when File Generation is set to Multiple Output Files. To use a processing variable, you can type the variable or you can click the pencil icon For example, you could set the subject line to |
Body Text | Enter the body text for the email. Processing variables can be used in the body text when File Generation is set to Multiple Output Files. To use a processing variable, you can type the variable or you can click the pencil icon |
Scheduler job variables can be used in any of the email settings except the From setting.
Multipass properties
The multipass properties at the bottom of the task determine how the report will be processed over a dimension.
Item | Description |
---|---|
Multipass Column | Specify the column to use for multipass processing. You can type a Table.Column name, or click the column icon The report will be processed once for each unique value in the specified column (except for any values excluded by the Source Filter). A filter is applied to the data query in the report so that the data is limited to the current pass value. For example, if you are processing by Dept.Dept, then the report will be processed once for each department, and the report data will be limited to only the data for that department. Keep in mind the difference between processing by a data table column such as GL2022.Dept, versus a dimension table column such as Dept.Dept. When processing by GL2022.Dept, the report will be processed by each department with data in the GL2022 table. When processing by Dept.Dept, the report will be processed by each department in the Dept table. To verify the list of values for processing, click the Preview Multipass List button to view the list of items. The first 100 values are shown, in the order they will be processed. If the task configuration includes a Recipient Column (in the email settings) or a Sort By column, these columns are also shown in the preview. |
Current Pass Header | Optional. Define a header to display in the report output file. This option only applies if the processing type is Export to PDF. The current pass header should use processing variables to display information about the current pass. To use a processing variable, you can type the variable or you can click the pencil icon For example, you can define a header such as: Processed by [MULTIPASS_COLUMN] [CURRENT_VALUE] When processing by Dept.Dept, this would resolve such as Processed by Dept 22000 By default, if the current pass header is left blank, then the PDF output will not include a header to indicate the current pass information. However, it is possible that the template used to create the report may have been designed with a dynamic header that will display this information. |
Sort By | Optional. Specify one or more sort columns for the list of multipass values. You can type a Table.Column name, or click the column icon By default, the values are sorted by the multipass column in ascending order. The Sort By field only needs to be used if you want the values to be sorted in descending order instead, or if you want the values sorted by a different column in the same table. The processing order is only relevant when File Generation is set to Single Output File, since it determines the order of each individual pass within the single file. When outputting to Multiple Output Files, the order is still used during processing but it has no useful impact on the outcome. |
Source Filter | Optional. Specify a filter to limit the multipass list of items. You can type a filter, or you can click the filter icon When the multipass list of values is generated, any value that does not meet the source filter will be excluded from processing. By default, all values in the specified multipass column are processed if the source filter is left blank. |
Scheduler job variables can be used in any of the multipass settings.
The following processing variables can be used in various settings within the Web Report Processing task, in order to dynamically change the setting using information for the current pass.
Item | Description |
---|---|
[CURRENT_VALUE] | This variable returns the current multipass processing value. For example, if you are processing by Dept.Dept, and the current pass is for department 20000, the variable will be replaced by the value "20000" for this pass. This variable is typically used in settings such the file name, sheet name (when generating Excel output), and folder path. |
[CURRENT_PASSNUMBER] | This variable returns the current pass number. For example, if the current pass is number 20 of 35 passes, the variable will be replaced by the value "20" for this pass. |
[MULTIPASS_COLUMN] | This variable returns the name of the multipass column. For example, if you are processing by Dept.Dept, the variable will be replaced by the value "Dept" for all passes. This variable could be used whenever you want to reference the name of the dimension processed. For example, instead of just referencing the current value in the file name, you might want to reference the column name and the value. A variable construction like |
Processing variables can only be used in certain settings, and sometimes only when the output is multiple files (versus a single file). See the documentation for each individual setting to see if processing variables are supported in that setting.