Visit Boris website Job definition - create
Accessing the job definitions screen

Accessing the job definitions screen

The job definitions screen

The job definitions screen

Job definitions are used if you wish to create, allocate or dispatch jobs from within Boris. If you don’t wish your users to receive their “Work List” of jobs on the device then there is no need to create any job definitions. If you do wish to centrally create and allocated jobs (or if an external system is feeding jobs into Boris) then you need to create a job definition. The definition specifies the information that is to be recorded when a job is created. Boris requires a number of items for each job and these don’t need to be part of your job definition. They are : customer, location, date, user to allocate the job to, group of users to allocate the job to. The job definition will contain any additional information that you wish to record, for example fault description, contact name, contact phone number, time. Each of the items within the job definition will have a type of “text”, “list” or “date”.

A job becomes allocated when it has been assigned a date and either a user or group of users (or both). Until then, it will appear under “Unallocated jobs”. Once the date and user/group have been specified the job will appear under “Outstanding jobs” and will be synched down to the PDA of any assigned user when they sync.

Click on the Add Definition button and you will be asked to fill in the fields below.            
How job definitions affect device users

How job definitions affect device users

Main

Add a new Job definition.

Add a new Job definition.

*Description A descriptive text to identify this item
Version Enter free text to identify historical changes.  This does not trigger any additional saved copies and is purely for information.
Display name Enter a free text alternative name for the job.  Whilst the description might be quite wordy, this could be a shorter version to appear on buttons.
Display name plural Enter free text to display when multiple jobs are initiated as computers do not always cope with the vagaries of the English language.  For example, adding an 's' to the job definition of ‘delivery’ would clearly be incorrect so indicating a plural of ‘deliveries’ would ensure that reports made sense.
*Associated template Select an existing template from this drop-down list. For more information on creating templates, click here.

Advanced

Suppress prompt for customer and location

A Job needs a customer and a location associated with it.  However, this is not always appropriate if it is an internal job so tick this box to use a default.

Suppress prompt for group This is usually ticked as jobs are usually allocated to an individual user rather than group.  However, if unticked a job can be allocated to a number of users at the same time and will be marked as complete by the first user to complete a form.  If ALL users in a group are to complete the form, use batch allocate.
Keep previous results when part of a document lifecycle Tick this box if you wish to store a copy of the original data in any jobs created from an existing form/job.  The stored data is not visible on the device but is available for use on reports and this is useful for demonstrating changes between periodic events, such as rental loss/damage, assessement/follow-up scores, etc.  This is a bespoke option and will need to be discussed with Boris support.

Job lists

Job lists allow text or external job data to be displayed on the job list pages. These can be the defaults or they can be defined specifically.
Column 1 (defaults to Date)

By default this shows the date for which the Job is scheduled. It can be customised to one of the job definition items.

Column 2 (defaults to Customer)

By default this shows the customer for whom the Job was created. It can be customised to one of the job definition items.

Column 3 (defaults to Location)

By default this shows the location for which the Job was created. It can be customised to one of the job definition items.

Column 4 (defaults to Template)

By default this shows the template with which the Job is associated. It can be customised to one of the job definition items.

Column 5 (defaults to User)

By default this shows the user to whom the Job is allocated. It can be customised to one of the job definition items.

Columns 6-12 Select the required item from the drop-down list.
$date - Date Date job scheduled to start
$customer - Customer Customer name
$location - Location Customer location
$template - Template Template name
$user - User User the job is allocated to
$workHistory - Completed forms List of comleted forms for the job
$issub - is sub-job? Indicates whether the job is a sub-job with a hyperlink showing the job hierarchy
$wosts - Status Supplementary-status for the job (ie 'awaiting invoicing' rather than 'complete')
$wopdf - Job PDF document A link to the PDF attached to the job
$woatt - Job attachments A link to other job attachments
$endDate - End date Date the job is scheduled to end
$empty-Empty Deliberately left blank so that the list can be formatted.  This means that if some job definitions in the list show items that others omit subsequent columns still line up. 
See Also

 

 


Parts copyright 2014 Boris Software Ltd. Parts copyright 2014 Firetronic Software Ltd. Parts copyright 1998-2014 Cadence Computing Ltd. All Rights Reserved.

Menus, prompts, fields and options are from a typical installation - some items may not appear as shown. Please contact Boris support for information on additional features.