IT-incidents
This template can help you create an API to integrate IT-incidents. The template contains all relevant entities and properties of an incident (context 128 in table 'Job').
All relations from 'Job' to another entity have minimum read access to the 'Description'. This way you can easily receive the right information. Below is an overview of all entities, properties and filters of this template.
Additional entities, properties and filters can be added, which may be missing from the template but are necessary for your process. All entities can be found through the 'Entity overview' in the customisation tool of IFS Ultimo (consult application administrator or consultant).
Entities and properties
Job
Id
Description
Context
CostCenter
CommunicationMedium
Department
Employee
Equipment
EquipmentType
Failtype
Feedbacktext
Priority
Processfunction
ProgressStatus
ReportForeignKeyEmployee
ReportText
ScheduledStartDate
ServiceContract
ServiceContractTargetFinishedDate
ServiceContractTargetResponseDate
Site
SkillCategory
Space
Status
StatusActiveDate
StatusCreateReportDate
StatusFinishDate
TargetDate
Text
Vendor
WorkorderType
ExternalId
DataProvider
CostCenter
Description
CommunicationMedium
Description
Department
Description
Employee
Description
Equipment
Description
OwnerEmployee
Site
Space
EquipmentType
Description
Failtype
Description
Priority
Description
ProcessFunction
Description
ProgressStatus
Description
ServiceContract
Description
Site
Description
SkillCategory
Description
Space
Description RoomNumber
Vendor
Description
WorkorderType
Description
Filters
Job
Context
=
128
Job
Status
IN
1,2,4,16
CommunicationMedium
Context
=
0
CommunicationMedium
Status
=
0
Costcenter
Context
=
1
Costcenter
Status
=
2
Department
Context
=
1
Department
Status
>=
0
Employee
Context
=
1
Employee
Status
>=
0
Equipment
Context
=
32
Equipment
Status
=
2
EquipmentType
Context
IN
2, 128
EquipmentType
Status
>=
0
Failtype
Context
=
2
Failtype
Status
>=
0
Priority
Context
=
2
Priority
Status
>=
0
Processfunction
Context
=
2
Processfunction
Status
=
1
ProgressStatus
Context
=
1
ProgressStatus
Status
>=
0
ServiceContract
Context
=
8
ServiceContract
Status
>=
0
Site
Context
=
1
Site
Status
>=
0
Skillcategory
Context
=
1
Skillcategory
Status
>=
0
Space
Context
=
1
Space
Status
>=
0
Vendor
Context
=
1
Vendor
Status
>=
0
Workordertype
Context
=
2
Workordertype
Status
>=
0
Change job status
For changing a job status we provide a 'POST' action that triggers a workflow in Ultimo. Below is an overview of all properties of this workflow. It's by default only possible to change jobs that comply with filters of entity 'Job', as described above. When those filters changed, this also applied to this workflow.
Property
Accessor
JobId
Optional
ExternalId
Optional
ProgressStatus
Required
Date
Required
Employee
Required
Text
Optional
Hours
Optional
Hourcode
Optional
HourTariffCategory
Optional
EquipmentProgressStatus
Optional
EquipmentProgressStatusRemark
Optional
Last updated