Scheduling Reports in MINT - Revision history

Alnaucler at 19:21, 20 February 2020

2020-02-20T19:21:13Z

← Older revision		Revision as of 21:21, 20 February 2020
Line 33:		Line 33:
	In the repository, the clock icon next to a report indicated that a job is scheduled for that report:		In the repository, the clock icon next to a report indicated that a job is scheduled for that report:
	[[File:MINT_report_schedule_icon.png\|center]]		[[File:MINT_report_schedule_icon.png\|center]]
	{{NavBox ~~Business Intelligence~~}}		{{NavBox Hub}}
	[[Category:~~VIE~~]]		[[Category:NoPublic]]

Evinek at 11:28, 21 June 2017

2017-06-21T11:28:38Z

← Older revision		Revision as of 13:28, 21 June 2017
Line 1:		Line 1:
	~~{{Under construction\| This page is under construction}}~~
	{{TOC right}}		{{TOC right}}

Evinek at 11:27, 21 June 2017

2017-06-21T11:27:42Z

← Older revision		Revision as of 13:27, 21 June 2017
Line 22:		Line 22:
	<li>'''File Handling''': specify if a new run should overwrite the previous output(s) or not. If not, a timestamp pattern can be defined in order to differentiate between the outputs. This allows to keep a history of reports in a structured way and can thus be very useful.</li>		<li>'''File Handling''': specify if a new run should overwrite the previous output(s) or not. If not, a timestamp pattern can be defined in order to differentiate between the outputs. This allows to keep a history of reports in a structured way and can thus be very useful.</li>
	<li>'''Output destination''': specify where to save the output - this can be a folder in the repository or alternatively an FTP server. It is recommended to create an archive folder in the repository to save the report outputs.</li>		<li>'''Output destination''': specify where to save the output - this can be a folder in the repository or alternatively an FTP server. It is recommended to create an archive folder in the repository to save the report outputs.</li>
	~~</ol>~~
	Once the configuration is done, click on the next tab to proceed.		Once the configuration is done, click on the next tab to proceed.
	</li>		</li>
	<li>'''Notification''': allows to specify email recipients whom the outputs should be automatically sent to. Specify recipients in '''To''', '''cc''', eventually '''bcc''' of the email, a subject and an email text. Finally, specify whether the email should only contain a link to the report output (in which case the user needs to have an account to log in to MINT) or include the output as an attachment (according to the format(s) specified in the '''Output''' tab; in that case the user does not need any account for MINT).</li>		<li>'''Notification''': allows to specify email recipients whom the outputs should be automatically sent to. Specify recipients in '''To''', '''cc''', eventually '''bcc''' of the email, a subject and an email text. Finally, specify whether the email should only contain a link to the report output (in which case the user needs to have an account to log in to MINT) or include the output as an attachment (according to the format(s) specified in the '''Output''' tab; in that case the user does not need any account for MINT). It is also possible to send status notifications, i.e. whether or not the report run successfully. This can be useful information for the MINT administrator. It is possible to choose to send status notifications only in case of failure, in case of success, or both.</li>
	</ol>		</ol>
	<li>Once all configuration is done, click '''Save''' to save the job and provide a name and optionally a description.</li>		<li>Once all configuration is done, click '''Save''' to save the job and provide a name and optionally a description.</li>
	~~</ol>~~
	The job is then displayed in the job list and can further be edited, disabled or deleted by clicking on the respective icons.		The job is then displayed in the job list and can further be edited, disabled or deleted by clicking on the respective icons.
	[[File:MINT_report_schedule_job_list.png\|center]]		[[File:MINT_report_schedule_job_list.png\|center]]
			</ol>
	Note that the job list is always report-specific, i.e. only the jobs for the particular chosen report are displayed - there is no global view of all jobs defined within an organisation.		Note that the job list is always report-specific, i.e. only the jobs for the particular chosen report are displayed - there is no global view of all jobs defined within an organisation.

			In the repository, the clock icon next to a report indicated that a job is scheduled for that report:
			[[File:MINT_report_schedule_icon.png\|center]]
	{{NavBox Business Intelligence}}		{{NavBox Business Intelligence}}
	[[Category:VIE]]		[[Category:VIE]]

Evinek at 10:26, 21 June 2017

2017-06-21T10:26:12Z

← Older revision		Revision as of 12:26, 21 June 2017
Line 25:		Line 25:
	Once the configuration is done, click on the next tab to proceed.		Once the configuration is done, click on the next tab to proceed.
	</li>		</li>
	<li>'''Notification''' ~~(labelled report.scheduling.job.edit.notifications)~~: allows to specify email recipients whom the outputs should be automatically sent to. Specify recipients in '''To''', '''cc''', eventually '''bcc''' of the email, a subject and an email text. Finally, specify whether the email should only contain a link to the report output (in which case the user needs to have an account to log in to MINT) or include the output as an attachment (according to the format(s) specified in the '''Output''' tab; in that case the user does not need any account for MINT).</li>		<li>'''Notification''': allows to specify email recipients whom the outputs should be automatically sent to. Specify recipients in '''To''', '''cc''', eventually '''bcc''' of the email, a subject and an email text. Finally, specify whether the email should only contain a link to the report output (in which case the user needs to have an account to log in to MINT) or include the output as an attachment (according to the format(s) specified in the '''Output''' tab; in that case the user does not need any account for MINT).</li>
	</ol>		</ol>
	<li>Once all configuration is done, click '''Save''' to save the job and provide a name and optionally a description.</li>		<li>Once all configuration is done, click '''Save''' to save the job and provide a name and optionally a description.</li>

Evinek at 10:25, 21 June 2017

2017-06-21T10:25:52Z

← Older revision		Revision as of 12:25, 21 June 2017
Line 13:		Line 13:
	<li>The job schedule editor is composed of four tabs:</li>		<li>The job schedule editor is composed of four tabs:</li>
	<ol>		<ol>
	<li>'''Schedule''' ~~(labelled report.scheduling.schedule)~~: allows to specify a schedule for the report execution. The recurrence can be None, Simple or Calendar. ''None'' means that the job is executed only once (either immediately or at a specified date). The ''Simple'' mode allows to specify a time interval and an end date for the job execution. The ''Calendar'' mode allows to schedule the job according to a calendar, e.g. every Monday in certain months at 8 am. Once the configuration is done, click on the next tab to proceed.</li>		<li>'''Schedule''': allows to specify a schedule for the report execution. The recurrence can be None, Simple or Calendar. ''None'' means that the job is executed only once (either immediately or at a specified date). The ''Simple'' mode allows to specify a time interval and an end date for the job execution. The ''Calendar'' mode allows to schedule the job according to a calendar, e.g. every Monday in certain months at 8 am. Once the configuration is done, click on the next tab to proceed.</li>
	<li>'''Parameters''': this tab is only enabled if the report to be scheduled has input controls (filters). If there are any, then the values for those input controls need to be specified. In this example, the report has the following parameters: a start date between two date values, a type of activity and a province. A value needs to be specified for each of those parameters.		<li>'''Parameters''': this tab is only enabled if the report to be scheduled has input controls (filters). If there are any, then the values for those input controls need to be specified. In this example, the report has the following parameters: a start date between two date values, a type of activity and a province. A value needs to be specified for each of those parameters.
	[[File:MINT_report_schedule_parameters.png\|center]]		[[File:MINT_report_schedule_parameters.png\|center]]
	Once the configuration is done, click on the next tab to proceed.</li>		Once the configuration is done, click on the next tab to proceed.</li>
	<li>'''Output''' ~~(labelled report.scheduling.job.edit.output)~~: this section allows to specify what the output of the report execution should be. Three options need to be specified:		<li>'''Output''': this section allows to specify what the output of the report execution should be. Three options need to be specified:
	<ol>		<ol>
	<li>'''Output Format''': check one or several output formats (e.g. CSV, DOCX, Excel, PDF, etc.)</li>		<li>'''Output Format''': check one or several output formats (e.g. CSV, DOCX, Excel, PDF, etc.)</li>

Evinek at 10:22, 21 June 2017

2017-06-21T10:22:02Z

← Older revision		Revision as of 12:22, 21 June 2017
Line 9:		Line 9:
	<li>In the repository, right-click on a report and select '''Schedule...'''		<li>In the repository, right-click on a report and select '''Schedule...'''
	[[File:MINT_report_schedule.png\|center]]</li>		[[File:MINT_report_schedule.png\|center]]</li>
	<li>In the '''Scheduled Jobs''' window, click '''Schedule ~~Job~~'''		<li>In the '''Scheduled Jobs''' window, click '''Create Schedule'''
	[[File:MINT_report_schedule_job.png\|center]]</li>		[[File:MINT_report_schedule_job.png\|center]]</li>
	<li>The job schedule editor is composed of four tabs:</li>		<li>The job schedule editor is composed of four tabs:</li>

Evinek at 14:42, 5 March 2015

2015-03-05T14:42:55Z

← Older revision		Revision as of 16:42, 5 March 2015
Line 1:		Line 1:
	{{Under construction\| This page is under construction}}		{{Under construction\| This page is under construction}}
	~~{{Warning\|There is currently an issue with the email notification from MINT. The problem is under investigation and will be resolved ASAP.}}~~
	{{TOC right}}		{{TOC right}}

Evinek at 10:57, 23 January 2015

2015-01-23T10:57:30Z

← Older revision		Revision as of 12:57, 23 January 2015
Line 33:		Line 33:
	[[File:MINT_report_schedule_job_list.png\|center]]		[[File:MINT_report_schedule_job_list.png\|center]]
	Note that the job list is always report-specific, i.e. only the jobs for the particular chosen report are displayed - there is no global view of all jobs defined within an organisation.		Note that the job list is always report-specific, i.e. only the jobs for the particular chosen report are displayed - there is no global view of all jobs defined within an organisation.
			{{NavBox Business Intelligence}}
			[[Category:VIE]]

Evinek at 08:05, 23 January 2015

2015-01-23T08:05:37Z

← Older revision		Revision as of 10:05, 23 January 2015
Line 31:		Line 31:
	</ol>		</ol>
	The job is then displayed in the job list and can further be edited, disabled or deleted by clicking on the respective icons.		The job is then displayed in the job list and can further be edited, disabled or deleted by clicking on the respective icons.
	[[File:~~MINT_report_scheduled_job_list~~.png\|center]]		[[File:MINT_report_schedule_job_list.png\|center]]
	Note that the job list is always report-specific, i.e. only the jobs for the particular chosen report are displayed - there is no global view of all jobs defined within an organisation.		Note that the job list is always report-specific, i.e. only the jobs for the particular chosen report are displayed - there is no global view of all jobs defined within an organisation.

Evinek at 08:05, 23 January 2015

2015-01-23T08:05:16Z

← Older revision		Revision as of 10:05, 23 January 2015
Line 18:		Line 18:
	[[File:MINT_report_schedule_parameters.png\|center]]		[[File:MINT_report_schedule_parameters.png\|center]]
	Once the configuration is done, click on the next tab to proceed.</li>		Once the configuration is done, click on the next tab to proceed.</li>
	<li>'''Output''' (labelled report.scheduling.job.edit.output):</li>		<li>'''Output''' (labelled report.scheduling.job.edit.output): this section allows to specify what the output of the report execution should be. Three options need to be specified:
	<li>'''~~Notification~~''' (~~labelled report~~.~~scheduling~~.~~job~~.~~edit~~.~~notifications):~~</li>		<ol>
			<li>'''Output Format''': check one or several output formats (e.g. CSV, DOCX, Excel, PDF, etc.)</li>
			<li>'''File Handling''': specify if a new run should overwrite the previous output(s) or not. If not, a timestamp pattern can be defined in order to differentiate between the outputs. This allows to keep a history of reports in a structured way and can thus be very useful.</li>
			<li>'''Output destination''': specify where to save the output - this can be a folder in the repository or alternatively an FTP server. It is recommended to create an archive folder in the repository to save the report outputs.</li>
	</ol>		</ol>
			Once the configuration is done, click on the next tab to proceed.
			</li>
			<li>'''Notification''' (labelled report.scheduling.job.edit.notifications): allows to specify email recipients whom the outputs should be automatically sent to. Specify recipients in '''To''', '''cc''', eventually '''bcc''' of the email, a subject and an email text. Finally, specify whether the email should only contain a link to the report output (in which case the user needs to have an account to log in to MINT) or include the output as an attachment (according to the format(s) specified in the '''Output''' tab; in that case the user does not need any account for MINT).</li>
	</ol>		</ol>
			<li>Once all configuration is done, click '''Save''' to save the job and provide a name and optionally a description.</li>
			</ol>
			The job is then displayed in the job list and can further be edited, disabled or deleted by clicking on the respective icons.
			[[File:MINT_report_scheduled_job_list.png\|center]]
			Note that the job list is always report-specific, i.e. only the jobs for the particular chosen report are displayed - there is no global view of all jobs defined within an organisation.