Creating jobs

Users with administrative authorisations can define and change jobs. Depending on the configuration, jobs can be started automatically or manually by users with the appropriate authorisation. Make sure that not too many jobs start at the same time and that the load of execution is distributed across several service clients (server installation). Jobs for data backup must generally take place outside of business hours, as the server or individual workstation is restarted and all clients are shut down for this purpose.

• Create a new job
  1. Go to the  Configurations tab on the function bar and select  Jobs >  New.
  2. Enter a unique Name and Title for the job.
  3. Select a Service Client from the selection list.
     Note: As of Bp Event 12, several service clients can be set up to distribute the job processing load.
• Define further settings for the job
  1. Set a Max. runtime and, if necessary, be informed about the faulty execution with a follow-up job.
  2. Enter a precise description of the job in the text field Remarks .
  3. For jobs of the "Data backup" type, enter the target Directory (storage location of the log files) and the number of Backups .
     Example: Number of backups is 7, the eighth backup overwrites the first one.
  4. If the Start time/Condition is "Series", click on  Open to define the series..
  5.  Activate the job in the horizontal toolbar.
  6.  Save your input by clicking on the icon in the top left-hand corner of the input window.

  Read more on Setting up the data backup and Notifications on faulty data backups

• Specify the job type

  The type determines which other options can be set for the job.

   

  Task	Creates a notification for users or user groups Example: If the number of people at an event is changed and saved, the chef will receive a notification.
  Account exchange	Automated export or import of account data Example: Synchronising accounts with another system (interface)
  Archiving	Compresses sent letters and reduces the images they contain to screen resolution to reduce the data load. Example: The data volume of correspondence from 5 years ago is compressed.
  Check data	Performs a time-controlled, automatic data check Alternative: Execute manually by going to the  Help tab and selecting  Maintenance >  Data >  Check.
  Delete data buffer segment	Deletes parts of the data buffer
  Data monitoring	Monitors tables and their changes and send notifications by email or triggers follow-up actions. Example: The job can check all events at the end of the day and notify users or user groups of missing advance invoices.
  Check data file	Performs a check of the database. The results are displayed in the job log. Alternative: Check manually in the MSC server window by selecting Check data file (for expert-guided sessions only)
  Data backup	Saves a backup of your database in the specified directory at the specified time Read more on Data backup
  Download emails	Queries the email accounts on the available mail servers and retrieves new messages.
  Send email	Sends the emails written in BP Event at specified times.
  Export	Exports formatted table contents to a file or sends them to a web server
  Delete emails permanently	Empties the recycle bin in the mailbox
  Import	Loads formatted file content into a table or retrieves data from a web server
  Start job	Starts more jobs
  Command lines	Executes scripts (command lines)
  Message	Sends internal messages to users or user groups
  System and job log clean-up	Deletes logs older than the limit set under  Administration >  Settings >  Log settings > Delete log files.
  Transaction	Executes a job sequence as a compact unit. If a job in this job sequence fails, a roll back to the start of the first job can be initiated.

• Set a start time/condition for a job

  The start time or condition determines when the job is executed.

   

  Immediately	Execution immediately after activating and saving the job. The job is executed once.
  Time	Starts the job on a specified date.
  Series	The job is repeated regularly, the date and time must be specified or series conditions defined (e.g. backup only on weekdays). Make sure that several jobs in a series are not started at the same time.
  External callup	The job can be started by an HTTP request. The person starting the request must belong to a user group and be authenticated as a user of that group.
  Function bar	The job is listed under  Start Job in the  Home tab of the function bar and can be started directly.
  Data entry window	Allows certain user groups to start jobs from the toolbar of various records (e.g. accounts, events, event segments). The record closes and opens automatically as soon as the job has finished.
  Save data entry window and close	Performs a check of the database. The results are displayed in the job log. Alternative: Check manually in the MSC server window > Check data file (for expert-guided sessions only)
  In transaction	The job is part of a transaction, i.e. a job sequence
  Start database	The job is executed when the Bp Event Server process starts or, in the case of a single-user installation, when the programme starts.
  Close database	The job is executed when the Bp Event Server process is terminated or at the end of the programme for single-user installations.
  After execution	The job only starts after another defined job has been completed.
  After time-out	Used to monitor a job and triggers a follow-up action (job) if the job to be monitored has exceeded its specified execution time
  After error	Starts after an error has occurred in a job to be monitored Example: Email with information about a faulty data backup is sent to the IT department
  After cancellation	Starts after another job has been cancelled
  After job	Started after a specified job, regardless of whether it was completed with or without an error