Understanding Job Number Syntax

Abstract

Within strokeone, job order numbers are represented by two sets of numbers separated by a forward slash character:-

e.g. 200123/12

These two sets of digits are individually termed job number and stroke suffix, so in actuality a job order number is a composite, made up from :-
<Job Number> &"/" &<stroke suffix>

The numbers allocated to each set of digits varies depending on whether a new or duplicate of an existing job order is requested.

New Job Order

When a brand new job is requested

•  the job number allocated is the next available sequence number in the internal job number counter.
• the stroke suffix is set as 1

For example, assume the last job order recorded in the system was 200355/1.

• The next job number available is 200356
• New Job orders are always given a /1 stroke suffix

Thus the job order number would be 200356 /1

You can therefore infer that a stroke suffix of 1 represents a new job

Duplicating an existing Job Order Number

When a user requests to raise a duplicate of an existing job order, they highlight the existing job order that they want to duplicate.

They have a further two choices to make when they elect to duplicate an existing job order.:-

• They can choose to have a new job number
• They can choose to have same job number but new stroke suffix

Duplicating and retaining the same job number, but getting new stroke suffix

• the job number allocated is identical to the existing job number selected for duplication.
• the stroke suffix allocated is the next available sequence number in the suffix counter for that job number.

For example, assume the user selected to duplicate job order 200356 / 10. Assume also that a job order number of 200356/11 already exists:-

• The Job Number would remain the same  - so 200356
• The next available sequence number in the stroke suffix counter for this job number would be 12

Thus the job order number would be 200356 /12

You can therefore infer that a stroke suffix of greater than 1 is by definition a repeat job

Duplicating an existing Job Order, but assigning a new number

When a user requests to raise a duplicate an existing job, but assign a whole new job number, they are effectively cloning an existing job as the one they are about to write up is very similar.

In this circumstances

• the job number allocated is the next available sequence number in the internal job number counter.
• the stroke suffix is set as 1
  

For example, assume the user selected to duplicate job order 200356 / 10, but assign a new job order number.
Assume the last existing job number allocated by the sequence counter was 290001.

Thus the new cloned job order number would be 290002 /1
You'll notice that the numbering syntax here is identical to when a new job order is created. The salient difference is that the job order itself would contain information cloned from the original job.

Duplicating an historic (legacy) Job Order Number

When a job number exists in a legacy system, and is duplicated in the new system, the numbering syntax is as follows:-

and you wish to preserve the legacy job order number, but increment the stroke suffix, users

• the job number specified is identical to the legacy job number selected for duplication.
• the stroke suffix allocated is the next available sequence number in the suffix counter for that job number.

For example, assume the user selected a historic job number,  job order 500 / 21.

• The Job Number would remain the same  - so 500
• The next available sequence number in the stroke suffix counter for this job number would be 22

Thus the job order number would be 500 /22