Snapshot API: Jobs (includes sub-jobs)

The snapshot API endpoint for clients is regenerated overnight. It contains the following information for all jobs and sub-jobs on the Glide system:

Jobs:

Field name Field type Meaning
GlideID Integer The Glide ID/Unique identifier for this job. (Unique)
WorkflowSystemID Integer The Glide ID for the workflow system associated with the job. (List available at GET /systems/list)
WorkflowSystem VARCHAR(30) The name of the above workflow system.
JobCreated Date The date the job was created on Glide.
JobDate Date The job date (e.g. Year End, etc).
IsTaxYearBased Options Yes or No - indicates whether this job is associated with a tax year structure.
TaxYearID Integer Indicates the tax year associated with the job, applicable where IsTaxYearBased = Yes.
JobDeleted Boolean 1 = Deleted, 0 = Not deleted
JobStatusID Options 0 = Not started, 1 = In progress, 2 = Completed.
JobStatus Options The above job status in text form.
JobUrgencyID Options 0 = Normal, 1 = Approaching (yellow), 2 = Urgent (orange), 3 = Overdue (red).
JobUrgency Options The above options in text form.
ClientID Glide client ID (Integer) The unique identifier for the client in Glide (I.e. GlideID from the clients snapshot).
ClientCode VARCHAR(16) The client code.
ClientName VARCHAR(128) The client's name.
JobOfficeID Glide office ID (Integer) The unique identifier for the office associated with the job.
JobOffice VARCHAR(30) The name of the office.
Slot1ID Glide user ID (Integer) The unique identifier for the user occupying slot 1 (typically reserved for the main client partner).
Slot1User VARCHAR(8) The initials for the above user.
Slot2ID Glide user ID (Integer) The unique identifier for the user occupying slot 2 (typically reserved for the main client manager).
Slot2User VARCHAR(8) The initials for the above user.
Slot3ID Glide user ID (Integer) The unique identifier for the user occupying slot 3.
Slot3User VARCHAR(8) The initials for the above user.
Slot4ID Glide user ID (Integer) The unique identifier for the user occupying slot 4.
Slot4User VARCHAR(8) The initials for the above user.
Slot5ID Glide user ID (Integer) The unique identifier for the user occupying slot 5.
Slot5User VARCHAR(8) The initials for the above user.
Slot6ID Glide user ID (Integer) The unique identifier for the user occupying slot 6.
Slot6User VARCHAR(8) The initials for the above user.
Slot7ID Glide user ID (Integer) The unique identifier for the user occupying slot 7.
Slot7User VARCHAR(8) The initials for the above user.
Slot8ID Glide user ID (Integer) The unique identifier for the user occupying slot 8.
Slot8User VARCHAR(8) The initials for the above user.
Slot9ID Glide user ID (Integer) The unique identifier for the user occupying slot 9.
Slot9User VARCHAR(8) The initials for the above user.
Slot10ID Glide user ID (Integer) The unique identifier for the user occupying slot 10.
Slot10User VARCHAR(8) The initials for the above user.
Slot11ID Glide user ID (Integer) The unique identifier for the user occupying slot 11.
Slot11User VARCHAR(8) The initials for the above user.
Slot12ID Glide user ID (Integer) The unique identifier for the user occupying slot 12.
Slot12User VARCHAR(8) The initials for the above user.
Slot13ID Glide user ID (Integer) The unique identifier for the user occupying slot 13.
Slot13User VARCHAR(8) The initials for the above user.
Slot14ID Glide user ID (Integer) The unique identifier for the user occupying slot 14.
Slot14User VARCHAR(8) The initials for the above user.
Slot15ID Glide user ID (Integer) The unique identifier for the user occupying slot 15.
Slot15User VARCHAR(8) The initials for the above user.
Slot16ID Glide user ID (Integer) The unique identifier for the user occupying slot 16.
Slot16User VARCHAR(8) The initials for the above user.

Sub-jobs:

Joining this data source to your query is useful where you are interested in any of the following:

  • The current stage of a job.
  • The current holder of a job.
  • The route of a job.
  • The next target of a job.

All of the above data points are associated with the sub-job, as opposed to the job. Depending upon the workflow structure, jobs can have more than one sub-job.

If you are solely interested in joining the actual/target date data to the job, this can be achieved without reference to the sub-job.

Field name Field type Meaning
GlideID Integer The Glide ID/Unique identifier for this sub-job. (Unique)
GlideJobID Integer The Glide ID/Unique identifier for the job this sub-job belongs to.
JobDeleted Boolean 1 = Deleted, 0 = Not deleted (referring to the job).
SubJobDeleted Boolean 1 = Deleted, 0 = Not deleted (referring to this sub-job).
WorkflowSystemID Integer The Glide ID for the workflow system associated with the job. (List available at GET /systems/list)
WorkflowSystem VARCHAR(30) The name of the above workflow system.
WorkflowSubSystemID Integer The Glide ID for the workflow sub-system associated with the job. (List available at GET /subsystem/list)
WorkflowSubSystem VARCHAR(40) The name of the above workflow sub-system.
RouteID Integer The Glide ID for the route associated with the sub-job. (List available at GET /subsystem/{WorkflowSubSystemID}/routes)
Route VARCHAR(40) The name of the above route.
CurrentStageID Integer The Glide ID for the stage associated with the current stage of the job. (List available at GET /editor/systems/{WorkflowSystemID}/elements/list)
CurrentStage VARCHAR(250) The name of the current stage of the sub-job.
JobHolderID Glide user ID (Integer) The unique identifier for the user that is currently holding this sub-job.
JobHolder VARCHAR(8) The initials for the above user.
NextTarget Integer (signed) The number of days remaining (+), past (-) the next target date.
NextTargetStageID Integer The unique identifier for the stage that is being targeted by the above target. (List available at GET /editor/systems/{WorkflowSystemID}/elements/list)
NextTargetStage VARCHAR(40) The milestone achieved text for the above stage. I.e. what we are trying to do by the target date.

Still need help? Contact Us Contact Us