The Reporting Server provides report-specific schedules to assist you in managing the processing and distribution of reports. All schedules specify a type of recurrence, which can be monthly, weekly, or daily.
This section explains how to add, edit, delete, and manage report schedules, as well as how to run the schedules on demand and enable or disable schedules in Bold Reports On-Premise.
The schedules page displays the schedules that are accessible to the user based on their permissions.
Schedules can be created only if the user has Create All Schedules
permission. Schedules can be created in three ways:
+
symbol in the left side menu.+
symbol in the left side menu and choose Schedule
to create a new schedule.
Click the Actions
button in the reports grid context menu and select Schedule
to schedule the corresponding report.
Once the dialog box opens, the category and report values are preselected by default,
Categories or Reports can be changed from the schedule dialog box itself.
Click Schedules
in the left side panel of the Report Server, and then click the Create Schedule
button.
Select the required category from the Category
dropdown. After selecting the category, corresponding reports under that selected category will be displayed in the Report
dropdown,
Select the required report from the dropdown.
Select the export name from the dropdown options, including Schedule Name, Report Name, Timestamp and Date Format.
The parameters available for the report will be shown in the scheduler dialog.
Select the parameter values to schedule and export the reports with this filter.
To modify the parameter values, you should enable the
Set Parameters
option in the schedule dialog box.
Select the recurrence type, recurrence, start date and end date in the `Add Schedule’ dialog box.
Reports can be scheduled hourly, daily, weekly, monthly, and yearly.
The application’s time zone will be displayed below the date picker. The start time of the schedule will be converted to the client’s time zone and displayed on the right side for the user’s convenience.
You can compress the exported reports into a zip file by selecting the Enable File Compression option in the schedule dialog box. This is not mandatory, and you can decompress it at any time by simply unchecking that option.
Exported reports can be made more secure with password protection by enabling the Enable Password Protection option in the schedule dialog box. The Default Password option is selected by default.
For the default password, the password will be generated as a combination of the first and last four characters of the email.
You can customise the password protection rules for exporting reports by choosing the Custom Password option.
However, the username or first name is mandatory in the password condition.
For instance, let’s consider a sample user with the following details:
First Name : John
Last Name : Michael
Email: johnmichael@gmail.com
With this sample user, the possible password combination and its unlock password have been explained below.
Password Rule | Unlock Password |
---|---|
First four characters of Email + Last four characters of First Name |
johnJohn |
First four characters of First Name + First four characters of Last Name |
JohnMich |
First four characters of Email + Last four characters of Last Name |
johnhael |
The mail template defines the text that is sent via email to the Report Server user.
Initially, the default template will be displayed in the mail template. If the custom password is enabled, the user can add a password hint to the mail template if necessary.
And you can also customize the email template to your preference.
By selecting the variable the scheduled user variable is directly assigned from the server to the mail template.
Exported reports can be sent to individual users or groups by selecting the Email attachment option.
Additionally, the exported reports can be sent to external recipients by providing the Email Id
, and you can add multiple external recipients at once Separating the emails with a comma(,). For example [recipient1@gmail.com,recipients2@gmail.com].
Note: Email attachment is selected by default..
Exported reports can also be saved to any location by selecting the Save as file option.
To save the exported report, Export Path and Max reports count have to be filled.
Export Path - Location to save the exported report. By default, the folder path will be \Export, and the default root path location will be C:\BoldServices\app_data\reporting\Jobs.
Edit the default folder path location to specify the required folder path in the Export path.
You must specify the required root path, which can be updated in the Shedule Report Setting export path.
Max reports count - Specify the maximum number of exported reports to be saved at this location.
Overwrite the Existing file - Enabling this option will overwrite existing files in the export folder.
Notify Recipients - Enabling this option will send notifications to the recipients.
To save the exported file at a network location, you must provide the path in UNC format as shown below,\\172.34.203.23\test\Export
Root directory path: \\172.34.203.23\test
Relative path: \Export
The root directory path can be specified in Shedule Report Settings, while the relative path can be specified when creating the schedules.
If the test folder does not exist, a test folder will be created automatically while running the schedules.
Write permission for that required root directory path folder.
When clicking the Schedule, the report will be scheduled for the selected recurrence.
Read, Write, Delete permissions for that Specific Schedule will be added for the user who created the schedule.
Category, report, name, recurrence type, recurrence, start and end dates, export format, and the recipients can be changed in the Edit Schedule dialog box.
Schedules can be made to run on demand by using this Run Now option in the schedule grid context menu. The Report will be exported in the format specified and sent to the recipients.
Schedules can be disabled at any time, which will ignore any future occurrences. When enabled, it will get the next occurrence and run accordingly.
Schedules can be deleted from the Report Server when they are no longer required.
Click the Actions button in the schedules grid context menu and select Delete to delete the schedule.
The following table illustrates the list of available APIs related to schedules in Bold Reports On-Premise.
Action | HTTP Method | Endpoint | Description |
---|---|---|---|
AddSchedule | POST | /api/site/{tenant-name}/v1.0/reports/schedule | Adds schedule to the server. Schedule details should be passed as input. |
UpdateSchedule | PUT | /api/site/{tenant-name}/v1.0/reports/schedule/{scheduleid} | Updates schedule. Should provide Schedule ID in the path parameter and schedule details as input. |
RunScheduleReport | GET | /api/site/{tenant-name}/v1.0/schedules/{scheduleId}/run | Runs a scheduled report. Should provide a Schedule ID in path parameter. |
GetScheduleItemDetail | GET | /api/site/{tenant-name}/v1.0/reports/schedule/{scheduleId} | Returns the respective schedule details. Should pass Schedule ID in path parameter. |
GetScheduleItems | GET | /api/site/{tenant-name}/v1.0/reports/schedule/items | Returns the list of scheduled items. |
GetSchedules | GET | /api/site/{tenant-name}/v1.0/items | Returns the list of schedules for the current user. ItemType should be Schedule. |
IsScheduleNameExists | POST | /api/site/{tenant-name}/v1.0/items/is-name-exists | Returns an item's existence, whether the given schedule name already exists or not on the server. Schedule name and ItemType as Schedule should be passed in the request body. |
GetScheduleDetail | GET | /api/site/{tenant-name}/v1.0/items/{id} | Returns the specified schedule details from the server. Schedule item ID should be passed as a path parameter. |
DeleteSchedule | DELETE | /api/site/{tenant-name}/v1.0/items/{id} | Deletes the specified schedule from the server. Schedule item ID should be passed as a path parameter. |