Difference between revisions of "GGUS:ROC CERN Interface FAQ"
Line 8: | Line 8: | ||
|tech-docu-link=n.a. | |tech-docu-link=n.a. | ||
|transfer-from-ggus=Data transfer from GGUS to SNOW is done using SOAP web services provided by SNOW. | |transfer-from-ggus=Data transfer from GGUS to SNOW is done using SOAP web services provided by SNOW. | ||
Due to incompatible data types in several fields GGUS implemented a wrapper tool for covering this issue. The wrapper tool is implemented in PHP. | Due to incompatible data types in several fields GGUS implemented a wrapper tool for covering this issue. The wrapper tool is implemented in PHP.<br> | ||
|transfer-to-ggus=Data transfer from SNOW to GGUS is done using SOAP web services provided by GGUS system. | Used operations are: | ||
* insert, | |||
* update, | |||
* get.<br><br> | |||
'''Incidents and requests'''<br> | |||
If a GGUS 'incident' becomes a GGUS 'change request' nothing will change in the related SNOW ticket. It will continue its life as an incident INC999999.<br> | |||
If a GGUS ticket becomes a 'Change request' in GGUS before transferring it to SNOW, GGUS will create a "Request" in SNOW. | |||
The ticket synchronization will be the same as for incidents. | |||
|transfer-to-ggus=Data transfer from SNOW to GGUS is done using SOAP web services provided by GGUS system.<br><br> | |||
'''Incidents and requests'''<br> | |||
If a SNOW 'incident' INC999999 becomes a SNOW "Request" REQ888888, its number will be sent to GGUS and, in the same web service call, the GGUS field " Ticket category" will change value automatically (triggered by SNOW) from 'incident' into 'change request'. GGUS will synchronize with the SNOW request from now on.<br> | |||
Used operations are: | Used operations are: | ||
* OpCreate, | * OpCreate, |
Revision as of 16:26, 9 May 2012
GGUS wiki / GGUS FAQ / GGUS Documentation / GGUS Helpdesk
FAQ for the Interface between GGUS and ROC_CERN Ticketing System
Reference link
Technical details
- Name of the Tool
- Service Now (SNOW)
- Programming language
- n.a.
- Redundancy
- No
- Help, Documentation, Example code
- n.a.
Data transfer from GGUS to ROC_CERN ticketing system
Data transfer from GGUS to SNOW is done using SOAP web services provided by SNOW.
Due to incompatible data types in several fields GGUS implemented a wrapper tool for covering this issue. The wrapper tool is implemented in PHP.
Used operations are:
- insert,
- update,
- get.
Incidents and requests
If a GGUS 'incident' becomes a GGUS 'change request' nothing will change in the related SNOW ticket. It will continue its life as an incident INC999999.
If a GGUS ticket becomes a 'Change request' in GGUS before transferring it to SNOW, GGUS will create a "Request" in SNOW.
The ticket synchronization will be the same as for incidents.
Field mapping create from GGUS to ROC_CERN
unknown
Field mapping modify from GGUS to ROC_CERN
unknown
Data transfer from ROC_CERN ticketing system to GGUS
Data transfer from SNOW to GGUS is done using SOAP web services provided by GGUS system.
Incidents and requests
If a SNOW 'incident' INC999999 becomes a SNOW "Request" REQ888888, its number will be sent to GGUS and, in the same web service call, the GGUS field " Ticket category" will change value automatically (triggered by SNOW) from 'incident' into 'change request'. GGUS will synchronize with the SNOW request from now on.
Used operations are:
- OpCreate,
- TicketModify.
Field mapping create from ROC_CERN to GGUS
unknown
Field mapping modify from ROC_CERN to GGUS
unknown
Attachments
Attachments are handled in a separate web service. The available operation is:
- AddAttachment
Comments
n.a.
What if I have questions which are not dealt with by this FAQ?
Open a GGUS ticket
indicating that it should be directed at the GGUS team.
Search
- Please use this link to search inside the GGUS FAQ