hat jemand von Euch schon mal soetwas gemacht? Und koennte es mir eventuell sogar erklaeren?
---- Schnipp ---
ich kann die Störungen auf dem Testsystem per WebService auslesen.
INC00028 | New | Neuanschluß eines Telefons per Hand zur Bestimmung von request.getContext()
INC00027 | Closed | Hier ein Ticket im neuen System
INC00026 | InProgress | Test auf Email-Adresse aus einem Ticket
INC00025 | New | Test
INC00024 | New | ID nicht da.
INC00023 | Closed | Ein Test auf die Haustechnik ...
Um eine Störung im System anzulegen braucht es den Wert einer Variablen
( z.B. request.setContext("QA-System"); ).
Die Installationsanleitung sagt zu diesem Parameter folgendes:
Initial configuration and manual steps
For the availability of the new functionality no further configuration is necessary. For the configuration of the functionality itself, please read the following sections.
The Installation of these Webservices adds a Data-definition to the Global Configuration that contains two Attributes, for which values need to be assigned to render any Webservice calls operational. The Data-definition is CUSTM42GlobalConfigurationServices and it contains the String-Attribute SupportedContexts into which a comma-separated list of possible values must be supplied. Most Webservice calls require a Context parameter in the passed Request object, which must be one of the listed values defined as described above. The Data-definition CUSTM42GlobalConfigurationServices also contains a Relation-Attribute DefaultTicketCreator that holds a reference to a User that is used as the default creator for Tickets if a Webservice call supplies no value for it. Both of these Attributes are not visible anywhere in the UI oif the Service-Store. To make them editable, whoever administrates the Service-Store can either set the values directly in the database, or add a dialog-page for the Global Configuration CI and put UI-controls there and subsequently set the values in the Global Configuration dialog.
---- Schnapp ---
LG aus der Hitze
Alexandra
