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.

Difference between revisions of "GGUS:VO Biomed Dashboard Interface FAQ"

From EGIWiki
Jump to navigation Jump to search
 
(13 intermediate revisions by the same user not shown)
Line 4: Line 4:
[[Category:FAQ Interfaces (GGUS)]]
[[Category:FAQ Interfaces (GGUS)]]
<hr />'''FAQ for the Biomed VO dashboard interface'''
<hr />'''FAQ for the Biomed VO dashboard interface'''
; Updated: 2012-07-06
=!!!This page is currently under construction!!!=


The content of this page has been moved to [[GGUS:VO_TEAM_Ticket_Interface_FAQ]]
<!--
=Purpose=
=Purpose=
This document describes the interface used by Biomed VO dashboard for submitting and updating team tickets in GGUS. <br>
This document describes the interface used by Biomed VO dashboard for submitting and updating team tickets in GGUS. <br>
Line 57: Line 56:
|GHD_Description       || Optional    || Detailed description of the problem.Length is up to 4000 chars.
|GHD_Description       || Optional    || Detailed description of the problem.Length is up to 4000 chars.
|-
|-
|GHD_VO_Specific       || Optional    || Flag indicating whether a problem is specific to a given VO or not. Possible values are "Yes" and "No". Defaults to "No".
|GHD_Involve               || Optional    || Mail addresses of people involved in ticket solution process.
|-
|GHD_Priority               || Optional    || Ticket priority level. Possible values are "less urgent", "urgent", "very urgent" and "top priority". Defaults to "less urgent".
|-
|GHD_Problem_Type       || Optional    || Possible values are given here: [[GGUS:Type_Of_Problem]]. Defaults to "Other".
|-
|-
|GHD_Name               || Optional    || Name of ticket submitter.
|GHD_Routing_Type       || Optional    || Manages whether the ticket will be routed to an NGI/ROC directly or to TPM. Please provide value "SITE/ROC" for bypassing the TPM. Defaults to "TPM".
|-
|-
|GHD_Priority               || Optional    || Ticket priority level. Possible values are "less urgent", "urgent", "very urgent" and "top priority". Defaults to "less urgent".
|GHD_Soap_Client_Data          || Optional    || Hidden free text field for keeping soap client data.
|-
|-
|GHD_Type_Of_Problem       || Optional    || Possible values are given here: [[GGUS:Type_Of_Problem]]. Defaults to "Other Services".
|GHD_Submitter               || Optional    || Name of ticket submitter.
|-
|-
|GHD_User_Notification       || Optional    || Manages the submitter notifications. Possible values are "Solution", "Every Change" and "Never". Defaults to "Solution".
|GHD_User_Notification       || Optional    || Manages the submitter notifications. Possible values are "Solution", "Every Change" and "Never". Defaults to "Solution".
|-
|-
|GHD_Routing_Type       || Optional    || Manages whether the ticket will be routed to an NGI/ROC directly or to TPM. Please provide value "SITE/ROC" for bypassing the TPM. Defaults to "TPM".
|GHD_VO_Specific       || Optional    || Flag indicating whether a problem is specific to a given VO or not. Possible values are "Yes" and "No". Defaults to "No".
|}
|}


Line 88: Line 91:
|-
|-
|GHD_Affected_Site    || Optional    || Site affected by the problem. Possible values are site names from GOCDB and OIMDB.
|GHD_Affected_Site    || Optional    || Site affected by the problem. Possible values are site names from GOCDB and OIMDB.
|-
|GHD_Responsible_Unit  || Optional    || Support unit in charge of the ticket. GGUS support units are listed at https://ggus-helmut.ggus.eu/pages/resp_unit_info.php.
|-
|-
|GHD_Assign_To        || Optional    || Add mail address for assigning a ticket to a dedicated person.
|GHD_Assign_To        || Optional    || Add mail address for assigning a ticket to a dedicated person.
Line 95: Line 96:
|GHD_Carbon_Copy      || Optional    || Add mail addresses for notifying people on this ticket. Please use semi-colon as delimiter.
|GHD_Carbon_Copy      || Optional    || Add mail addresses for notifying people on this ticket. Please use semi-colon as delimiter.
|-
|-
|GHD_VO_Specific      || Optional    || Flag indicating whether a problem is specific to a given VO or not. Possible values are "Yes" and "No". Defaults to "No".
|GHD_Detailed_Solution || Optional    || Solution text required if changing status to "solved" or "unsolved".
|-
|-
|GHD_Priority       || Optional    || Ticket priority level. Possible values are "less urgent", "urgent", "very urgent" and "top priority". Defaults to "less urgent".
|GHD_Involve       || Optional    || Mail addresses of people involved in ticket solution process.
|-
|-
|GHD_Subject          || Optional    || Ticket subject.
|GHD_Internal_Diary    || Optional    || Internal comment for support staffs only.
|-
|-
|GHD_Type_Of_Problem  || Optional    || Possible values are given here: [[GGUS:Type_Of_Problem]]. Defaults to "Other Services".
|GHD_Priority       || Optional    || Ticket priority level. Possible values are "less urgent", "urgent", "very urgent" and "top priority". Defaults to "less urgent".
|-
|-
|GHD_Detailed_Solution || Optional    || Solution text required if changing status to "solved" or "unsolved".
|GHD_Problem_Type      || Optional    || Possible values are given here: [[GGUS:Type_Of_Problem]]. Defaults to "Other Services".
|-
|-
|GHD_Public_Diary      || Optional    || Public comment that will trigger a notification to the ticket submitter.
|GHD_Public_Diary      || Optional    || Public comment that will trigger a notification to the ticket submitter.
|-
|-
|GHD_Internal_Diary   || Optional    || Internal comment for support staffs only.
|GHD_Responsible_Unit  || Optional   || Support unit in charge of the ticket. GGUS support units are listed at https://ggus.eu/pages/resp_unit_info.php.
|-
|GHD_Soap_Client_Data  || Optional    || Hidden free text field for keeping soap client data.
|-
|-
|GHD_Status            || Optional    || Ticket status. Possible status values are listed here: [[GGUS:Status_Values]]
|GHD_Status            || Optional    || Ticket status. Possible status values are listed here: [[GGUS:Status_Values]]
|-
|GHD_Subject          || Optional    || Ticket subject.
|-
|GHD_VO_Specific      || Optional    || Flag indicating whether a problem is specific to a given VO or not. Possible values are "Yes" and "No". Defaults to "No".
|}
|}


===Output values===
===Output values===
In case of success this operation will return the ticket ID used for calling the OpModifyTeam operation.
In case of success this operation will return the ticket ID used for calling the OpModifyTeam operation.


==OpGetTeam==
==OpGetTeam==
This operation is being used for getting the data of a team ticket searching by ticket ID. The result gives the fields like listed below.  
This operation is being used for getting the data of a team ticket searching by ticket ID. The result gives the fields like listed below.  


===Input values===
* GHD_Request_ID
===Output values===
* GHD_Affected_Site
* GHD_Affected_Site
* GHD_Affected_VO
* GHD_Affected_VO
* GHD_Assign_To
* GHD_Carbon_Copy
* GHD_Carbon_Copy
* GHD_Assign_To
* GHD_Modified_Date
* GHD_Create_Date
* GHD_Create_Date
* GHD_Description
* GHD_Detailed_Solution
* GHD_Detailed_Solution
* GHD_Description
* GHD_Public_Diary
* GHD_Internal_Diary
* GHD_Internal_Diary
* GHD_Status
* GHD_Involve
* GHD_VO_Specific
* GHD_Last_Login
* GHD_Last_Modifier
* GHD_Last_Modifier
* GHD_Meta_Status
* GHD_Modified_Date
* GHD_Priority
* GHD_Priority
* GHD_Problem_Type
* GHD_Public_Diary
* GHD_Responsible_Unit
* GHD_Soap_Client_Data
* GHD_Status
* GHD_Subject
* GHD_Subject
* GHD_Type_Of_Problem
* GHD_Submitter
* GHD_VO_Specific




==OpGetListTeam==
==OpGetListTeam==
This operation is being used for getting the data of a bundle of team ticket searching by any criteria. It requires using the field labels in GGUS DB instead of XML labels like the other SOAP operations. Please contact the GGUS team for help before using this operation. <br>
This operation is being used for getting all records of type "TEAM" affecting VO "biomed". The result is limited to the latest 500 records. <br>
The result gives the same fields like operation OpGetTeam. Additionally the ticket IDs are part of the result records.
 
The maximum number of records returned is limited to 500.
===Input values===
None.
 
===Output values===
The result gives a couple of basic fields for getting an idea about what each ticket is related to. For getting details an OpGetTeam operation should be executed.
 
* GHD_Affected_Site
* GHD_Affected_VO
* GHD_Last_Modifier
* GHD_Modified_Date
* GHD_Priority
* GHD_Problem_Type
* GHD_Request_ID
* GHD_Responsible_Unit
* GHD_Status
* GHD_VO_Specific
* GHD_Subject


-->


==  What if I have questions which are not dealt with by this FAQ? ==  
=  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.
Open a [https://ggus.eu/pages/ticket.php GGUS ticket] indicating that it should be directed at the GGUS team.
{{GGUS search}}
{{GGUS search}}

Latest revision as of 10:02, 24 July 2013

GGUS-logo.jpg


GGUS wiki / GGUS FAQ / GGUS Documentation / GGUS Helpdesk

FAQ for the Biomed VO dashboard interface

The content of this page has been moved to GGUS:VO_TEAM_Ticket_Interface_FAQ

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


Retrieved from "https://wiki.egi.eu/w/index.php?title=GGUS:VO_Biomed_Dashboard_Interface_FAQ&oldid=58244"