Alert.png The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.

GGUS:NGI IBERGRID Interface FAQ

From EGIWiki
Revision as of 10:23, 30 March 2012 by Ggrein (talk | contribs)
Jump to navigation Jump to search
GGUS-logo.jpg


GGUS wiki / GGUS FAQ / GGUS Documentation / GGUS Helpdesk


FAQ for the Interface between GGUS and NGI_IBERGRID Ticketing System

Reference link

http://swegus.ific.uv.es/helpdesk/

Technical details

Name of the Tool
1or0
Programming language
PHP
Redundancy
No
Help, Documentation, Example code
http://swegus.ific.uv.es/helpdesk/?action=howto

Data transfer from GGUS to NGI_IBERGRID ticketing system

INTERFACE CURRENTLY DISABLED!! For transferring data from the GGUS system to the IBERGRID help desk system GGUS uses the web services provided by the IBERGRID help desk system. Available operations are:

  • OpCreate for creating a new ticket in IBERGRID help desk system and
  • TicketModify for updating an existing ticket.

Additional information can be found at http://swegus.ific.uv.es/helpdesk/?action=webservices.

Field mapping create from GGUS to NGI_IBERGRID

unknown

Field mapping modify from GGUS to NGI_IBERGRID

unknown

Data transfer from NGI_IBERGRID ticketing system to GGUS

INTERFACE CURRENTLY DISABLED!! For transferring data from the IBERGRID help desk system to GGUS the IBERGRID help desk system uses the web services provided by GGUS system. Available operations are of GGUS system are:

  • OpCreate for creating a new ticket in GGUS system,
  • TicketModify for updating an existing ticket and
  • TicketGet for reading values of an existing ticket.

Field mapping create from NGI_IBERGRID to GGUS

unknown

Field mapping modify from NGI_IBERGRID to GGUS

unknown

Attachments

n.a.

Comments

In relation to how the supporters manages to contact the user, here at IBERGRID the supporter have the option "send email to user", in this case an email is sent to the user (and only in this case), and the message is included in the History field. Later is updated at GGUS. The email is obtained from GGUS with the field E-mail. As I see with an email with every update, two emails will be sent to the user once the supporters sent an email to the user from the local helpdesk. Here, we can just forget about the process of sending an email since GGUS will send it. In that case the local helpdesk would only update the message to GGUS and the email with the message would be send by GGUS.

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