There are scenarios where users have Custom Exports set up against the system, which may be run manually or set to run as a Windows Service. These work fine (and will continue to with this feature) in an on-Premise setup of Syrinx.

If however the system is set up on Syrinx Cloud then the user(s) won't have access to the file or windows service settings.

This new feature allows these 'views' and 'sprocs' that are to be output to a file to be configured in the task scheduler so the user can control the frequency with which they are run.

Topics included in this article

• Configuration  

• Task Scheduler

• Running the Tasks

Configuration

Before this will work, a couple of items need to be configured, both of which need to be patched into the system. As this relates to custom work, this would be done as part of the project, and support/implementation would be involved in this element.

• A new System Option needs to be patched in to turn on this feature within the Task Scheduler; this will add the 'Export SQL to File' option within the Scheduler.
• The tasks to be run need to be patched into the Task Scheduler Export SQL table. These entries will include the object to run, the type (View or Sproc), the filepath where it will save the file, and the filename.
  • Here is an example of an entry - ('qCashPayments','V','C:\temp\TaskScheduler\SQL2File','CashPayments_|DT',2,1)

Task Scheduler

Once the above is set up in the Task Scheduler, you will need to add a new Task to your configuration.

You can add the task to a new Configuration or an existing one.

Refer to the main Syrinx Task Scheduler knowledge article for more general information on the Scheduler

You would configure this as usual with Log Filepath, who to email Logs to, etc.

Running the Tasks

When the setup is complete, the task will appear to run when manually opening the task scheduler.

You can run the task manually from here, or if it is running as a service, it will run at the frequency you have set.

If you have multiple views or sprocs to run, it will run through them sequentially.

The files will be output to the filepath destination set previously for retrieval.