...
| Panel |
|---|
...
The sp:JeopReportRequest API method can be used to obtain jobs and standard activities that are jeopardy.
...
On This Page: |
Related Pages: |
...
| Panel |
|---|
The |
Description
The sp:JeopReportRequest API method allows a customer jobs and standard activities that are in breach of the customer’s rules (e.g. running late or breaking customer promise).
The API method returns a snapshot of the current set of work items (jobs and standard activities) in jeopardy for a given subset of scheduling units/teams at the time of the call.
Users of the API may want to only consider a work item in jeopardy when the clock time is past the appointment or contract latest for the work item concerned. (This allows systems integrating with the API to avoid informing customer that an appointment has been missed, when there is still a chance that its commitment could be made.) The options field in the sp:JeopReportRequest API method accept values which will enable jeopardy to be suppressed in these circumstances.
| Note |
|---|
Jeopardy tolerances are taken into account when reporting jeopardy conditions through calls to |
Order of Jobs Returned
Jobs will be returned in the following order:
- Jobs are grouped by FRU (if more than 1 FRU or teams from more than 1 FRU specified);
- Unresourced jobs for the FRU will be returned first; and
- Resourced jobs are then grouped by team within the FRU.
Marked Jobs
It is possible for the Gantt user to mark the jobs as having been ‘dealt with’. This does not stop API calls being made for these jobs, and there is no indication on the API call made that the job has been marked.
Definition
The definition of this API is:
| Include Page | ||||
|---|---|---|---|---|
|
Return Structure
The API returns a non-standard return structure.
| Include Page | ||||
|---|---|---|---|---|
|
Return Codes
In addition to the Standard Return Codes, the possible Return Codes from this API are:
| Include Page | ||||
|---|---|---|---|---|
|