The following Schema is the Trouble Ticket API Request Response Schema. Pierre Gauthier Nortel Networks 2001. Trouble Ticket Event Property Descriptor. Extends the EventPropertyDescriptor. Trouble Ticekt CreateEvent Property Descriptor. Extends the TroubleTicketEventPropertyDescriptor. TroubleTicketCloseOutEventPropertyDescriptor. Extends the TroubleTicketEventPropertyDescriptor. TroubleTicketCancellationEventPropertyDescriptor. Extends the TroubleTicketEventPropertyDescriptor. TroubleTicketAttributeValueChangeEventPropertyDescriptor. Extends the TroubleTicketEventPropertyDescriptor. TroubleTicketStatusChangeEventPropertyDescriptor. Extends the TroubleTicketEventPropertyDescriptor. The following request runs a query and returns the matching TroubleTickets. The attributeName array indicates which attributes are to be returned. If the attributeName is null or empty then all possible attributes are returned. The howMany attribute is used to restrict the number of Trouble Ticket values returned per response message. If the number of matching Trouble Tickets exceeds the "howMany" value then multiple response messages are returned. The result set is an array of Trouble Ticket values (the amount is determined by the howMany attribute of the Request message). The endOfReply indicates whether there are any more response messages to be returned. The sequence number indicates the order of this response in the set of responses to be returned. Siince there can be a number of response messages generated and there is no mechanism to insure the responses are sent sequentially, the sequence number provides a mechanism for preserving the order in which the the response messages are returned. The operation may fail because an IllegalArgument has been provided or because a System exception occured. . Returns the TroubleTicket identified by the key. The attributeName list indicates which attributes are to be returned. If no attributeName is provided then all possible attributes are returned. The value for the TroubleTicket is returned. The following exceptions are returned if an error occurrs. This is the plural version of getTroubleTicketByKey. It takes in a list of TroubleTicket keys. A list of TroubleTicket values is returned. The following exceptions are returned if an error occurrs. This is an associative lookup which will return the Trouble Ticket values matching the TroubleTicket, identified by the TroubleTicketValue template. The attributeName array indicates which attributes are to be returned. If the attributeName is null or empty then all possible attributes are returned. The howMany attribute is used to restrict the number of Trouble Ticket values returned per response message.If the number of matching Trouble Tickets exceeds the "howMany" value then multiple response messages are returned. The result set is an array of Trouble Ticket values (the amount is determined by the howMany attribute of the Request message). The endOfReply indicates whether there are any more response messages to be returned. The following exceptions are returned if an error occurrs. This is an associative lookup which will return the Trouble Ticket values matching the TroubleTicket, identified by the TroubleTicketValue templates. The attributeName array indicates which attributes are to be returned. If the attributeName is null or empty then all possible attributes are returned. The howMany attribute is used to restrict the number of Trouble Ticket values returned per response message.If the number of matching Trouble Tickets exceeds the "howMany" value then multiple response messages are returned. The result set is an array of Trouble Ticket values (the amount is determined by the howMany attribute of the Request message). The endOfReply indicates whether there are any more response messages to be returned. The sequence number indicates the order of this response in the set of responses to be returned. The following exceptions are returned if an error occurrs. This request is used to change the attributes of an TroubleTicket. Only the attributes which are present in the Trouble Ticket Value are changed. Only the message header is returned. This is sufficient to indicate that the TroubleTicket was changed. The following exceptions are returned if an error occurrs. The following request close a TroubleTicket given its key. Only the message header is returned. This is sufficient to indicate that the TroubleTicket was closed. The following exceptions are returned if an error occurrs. Creates a new Trouble Ticket and returns the key for the new object. A single TroubleTicket value is the only parameter passed into the request. This returns the TroubleTicketKey corresponding to the TroubleTicket which was created. This is returned if an exception occurrs. The following request escalate a TroubleTicket given its key and an escalation list. Only the message header is returned. This is sufficient to indicate that the TroubleTicket was escalated. The following exceptions are returned if an error occurrs. The following request cancel a TroubleTicket given its key. Only the message header is returned. This is sufficient to indicate that the TroubleTicket was canceled. The following exceptions are returned if an error occurrs. The following request tries to create multiple Trouble Tickets each with a different set of attribute values. The operation is best effort i.e. the operation will try to set the attributes of every newly created trouble tickets with their new set of values. The return value is an array of TroubleTicketKeyResult which contains ALL the trouble ticket results (both the failed and success). Each trouble ticket key result contains the exception that would have been raised if the create operation had been called on a single trouble ticket. The operation may fail because an IllegalArgument has been provided or because a System exception occured. The following request tries to set multiple Trouble Tickets each with different values. The operation is best effort i.e. the operation will try to update the attributes of every targeted trouble tickets with their new attribute values. The resyncRequired flag indicates if the lastUpdateVersionNumber should be used to detect a staled object condition. The return value is an array of TroubleTicketKeyResult which contains only the trouble ticket keys for which the update operation failed. Each trouble ticket key result contains the exception that would have been raised if the set operation had been called on a single trouble ticket. The operation may fail because an IllegalArgument has been provided or because a System exception occured. The following request tries to set multiple Trouble Tickets each with the same value. The operation is best effort i.e. the operation will try to update the attributes of every targeted trouble tickets with their new attribute values. The return value is an array of TroubleTicketKeyResult which contains only the trouble ticket keys for which the update operation FAILED. Each trouble ticket key result contains the exception that would have been raised if the set operation had been called on a single trouble ticket. The operation may fail because an IllegalArgument has been provided or because a System exception occured. All the trouble tickets matching the attribute values provided in the value template are set with the attribute values provided in the trouble ticket value. Only the trouble tickets matching all the attribute values provided in the value template are updated.The operation is best effort i.e. the operation will try to update the attributes of ALL the targeted trouble tickets matching the Template with the provided Trouble ticket Value. (failuresOnly) The result set is an array of Trouble Ticket Result (the amount is determined by the howMany attribute of the Request message). The endOfReply indicates whether there are any more response messages to be returned. The operation may fail because the trouble ticket could not be found or because the update could not be applied to the targeted trouble ticket. Each trouble ticket key result should contain the exception that would have been raised if the SET operation had been called on a single trouble ticket. All the trouble tickets matching the attribute values provided in the value template(s) are set with the attribute values provided in the trouble ticket value. Only the trouble tickets matching all the attribute values provided in the value template(s) are updated.The operation is best effort i.e. the operation will try to update the attributes of ALL the targeted trouble tickets matching the Template(s) with the provided Trouble ticket Value. If multiple Templates are provided then the semantic is to apply an OR operation between the Templates. The result set is a list (the amount in the list is determined by the HowMany element) of TroubleTicketKeyResult. The endOfReply indicates whether there are any more result sets being returned. The sequence number indicates the result set TroubleTicketKeyResult, since there can be a number of response messages generated and there is no mechanism to insure the responses are sent sequentially, there needs to be a method of preserving the TroubleTicketKeyResult of the response messages. The operation may fail because the trouble ticket could not be found or because the update could not be applied to the targeted trouble ticket. Each trouble ticket key result should contain the exception that would have been raised if the SET operation had been called on a single trouble ticket. If no trouble ticket are found then the javax.ejb.FinderException is raised. If the operation can’t proceed for any other reason (backend failure) then the javax.oss.SetException should be raised. If none of the objects could be modified then the javax.oss.SetException should be raised. This request is used to escalate multiple Trouble Tickets given their keys. The operation is best effort i.e. the operation will try to close all the targeted trouble tickets given their keys. The return value is a list ( representing an array of TroubleTicketKeyResult ) which contains only the trouble ticket keys for which the escalate operation failed. Each trouble ticket key result contains the exception that would have been raised if the escalate operation had been called on a single trouble ticket. The operation may fail because an IllegalArgument has been provided or because a System exception occured. This is the best effort version of the EscalateTroubleTicketByTemplate request that allows the client to escalate all the TroubleTickets matching an TroubleTicket Template . The result set is a list (the amount in the list is determined by the HowMany element) of TroubleTicketKeyResult. The endOfReply indicates whether there are any more result sets being returned. The sequence number indicates the result set TroubleTicketKeyResult, since there can be a number of response messages generated and there is no mechanism to insure the responses are sent sequentially, there needs to be a method of preserving the TroubleTicketKeyResult of the response messages. The operation may fail because an IllegalArgument has been provided or because a System exception occured. This is the best effort version of the EscalateTroubleTicketsByTemplates request that allows the client to escalate all the TroubleTickets matching an TroubleTicket Template(s). If multiple Templates are provided then the semantic is to apply an OR operation between the Templates. The return value is a list of TroubleTicketKeyResults which can be used to extract the operation results based on the value of the return_mode parameter: The result set is a list (the amount in the list is determined by the HowMany element) of TroubleTicketKeyResult. The endOfReply indicates whether there are any more result sets being returned. The sequence number indicates the result set TroubleTicketKeyResult, since there can be a number of response messages generated and there is no mechanism to insure the responses are sent sequentially, there needs to be a method of preserving the TroubleTicketKeyResult of the response messages. The following exceptions are returned if an error occurrs. The operation may fail because the trouble ticket could not be found or because escalating the targeted trouble ticket is not allowed. Each trouble ticket key result should contain the exception that would have been raised if the ESCALATE operation had been called on a single trouble ticket. If no trouble tickets are found then the javax.ejb.FinderException is raised. If the operation can’t proceed for any other reason (backend failure) then the EscalateTroubleTicketException should be raised. This request is used to close multiple Trouble Tickets given their keys. The operation is best effort i.e. the operation will try to close all the targeted trouble tickets. The return value is a list (representing an array) of TroubleTicketKeyResult which contains only the trouble ticket keys for which the close operation failed. Each trouble ticket key result contains the exception that would have been raised if the set operation had been called on a single trouble ticket. The operation may fail because an IllegalArgument has been provided or because a System exception occured. This is the best effort version of the CloseTroubleTicketByTemplate request that allows the client to close all the TroubleTickets matching an TroubleTicket Template . The returnMode attribute is used to indicate what information should be returned. The result set is a list (the amount in the list is determined by the HowMany element) of TroubleTicketKeyResult. The endOfReply indicates whether there are any more result sets being returned. The sequence number indicates the result set TroubleTicketKeyResult, since there can be a number of response messages generated and there is no mechanism to insure the responses are sent sequentially, there needs to be a method of preserving the TroubleTicketKeyResult of the response messages. The following exceptions are returned if an error occurrs. This is the best effort version of the CloseTroubleTicketsByTemplates request that allows the client to close all the TroubleTickets matching an TroubleTicket Template. This operation will try to close all the trouble tickets matching the Template(s) . If multiple Templates are provided then the semantic is to apply an OR operation between the Templates. The return value is a list of TroubleTicketKeyResults which can be used to extract the operation results based on the value of the return_mode parameter: The result set is a list (the amount in the list is determined by the HowMany element) of TroubleTicketKeyResult. The endOfReply indicates whether there are any more result sets being returned. The sequence number indicates the result set TroubleTicketKeyResult, since there can be a number of response messages generated and there is no mechanism to insure the responses are sent sequentially, there needs to be a method of preserving the TroubleTicketKeyResult of the response messages. The following exceptions are returned if an error occurrs. The operation may fail because the trouble ticket could not be found or because removing the targeted trouble ticket is not allowed. Each trouble ticket key result should contain the exception that would have been raised if the CLOSE operation had been called on a single trouble ticket. If no trouble ticket are found then the javax.ejb.FinderException is raised. If the operation can’t proceed for any other reason (backend failure) then the javax.oss.trouble.CloseException should be raised. This request is used to cancel multiple Trouble Tickets given their keys. The operation is best effort i.e. the operation will try to cancel all the targeted trouble tickets given their keys. The return value is an array of TroubleTicketKeyResult that contains only the trouble ticket keys for which the Cancel operation failed. Each trouble ticket key result contains the exception that would have been raised if the cancel operation had been called on a single trouble ticket The operation may fail because an IllegalArgument has been provided or because a System exception occured. This is the best effort version of the CancelTroubleTicketByTemplate request that allows the client to cancel all the TroubleTickets matching an TroubleTicket Template . The returnMode attribute is used to indicate what information should be returned. The result set is a list (the amount in the list is determined by the HowMany element) of TroubleTicketKeyResult. The endOfReply indicates whether there are any more result sets being returned. The sequence number indicates the result set TroubleTicketKeyResult, since there can be a number of response messages generated and there is no mechanism to insure the responses are sent sequentially, there needs to be a method of preserving the TroubleTicketKeyResult of the response messages. The following exceptions are returned if an error occurrs. The operation may fail because the trouble ticket could not be found or because removing the targeted trouble ticket is not allowed. Each trouble ticket key result should contain the exception that would have been raised if the CANCEL operation had been called on a single trouble ticket. If no trouble ticket are found then the javax.ejb.FinderException is raised. If the operation can’t proceed for any other reason (backend failure) then the CancelTroubleTicketException should be raised. If none of the objects could be canceld then the CancelTroubleTicketException should be raised. This is the best effort version of the CancelTroubleTicketsByTemplates request that allows the client to cancel all the TroubleTickets matching an TroubleTicket Template(s). If multiple Templates are provided then the semantic is to apply an OR operation between the Templates. The return value is a list of TroubleTicketKeyResults which can be used to extract the operation results based on the value of the return_mode parameter: The result set is a list (the amount in the list is determined by the HowMany element) of TroubleTicketKeyResult. The endOfReply indicates whether there are any more result sets being returned. The sequence number indicates the result set TroubleTicketKeyResult, since there can be a number of response messages generated and there is no mechanism to insure the responses are sent sequentially, there needs to be a method of preserving the TroubleTicketKeyResult of the response messages. The following exceptions are returned if an error occurrs. The operation may fail because the trouble ticket could not be found or because caneling the targeted trouble ticket is not allowed. Each trouble ticket key result should contain the exception that would have been raised if the CANCEL operation had been called on a single trouble ticket. If no trouble ticket are found then the javax.ejb.FinderException is raised. If the operation can’t proceed for any other reason (backend failure) then the CancelTroubleTicketException should be raised. If none of the objects could be canceld then the CancelTroubleTicketException should be raised. This is the same as createTroubleTicket except it allows the client to create a number of TroubleTickets in the system. A list of TroubleTicketValues is passed into the request. This returns a list of TroubleTicketKeys corresponding to each TroubleTicket which was created in the system. It is assumed that a successful completion will create all the trouble tickets with their corresponding values and that no changes will be commited otherwise. This is returned if an exception occurrs. This is the plural version of the setTroubleTicket request. The only difference is that it takes a list of TroubleTicketValues. This operation is used to set multiple trouble tickets each with a different set of attribute values. Each trouble ticket is set with the attribute values provided in the corresponding element of the trouble ticket value array. All the entities matching the provided keys (i.e contained in each TroubleTicketValue of the array) must be found otherwise the XML FinderException message should be sent. If the same key is duplicated (i.e there is more than one entry in the array targeting the same trouble ticket) then the XML DuplicateKeyException message is sent. The operation is atomic i.e. the operation must successfully update all the attributes of the ALL the corresponding trouble ticket otherwise the XML SetException message is sent (assuming that all the trouble tickets were found i.e XML FinderException was not sent and no key duplication was present). The Response is the SetTroubleTicketsByValuesResponse message which contains only the message header. This is sufficient to indicate that the TroubleTickets were changed.It is assumed that a successful completion will update all the attribute values of the ALL the trouble tickets matching the provided keys with values with their corresponding values and no changes will be commited otherwise. The following exceptions are returned if an error occurrs. All the entities matching the provided keys (i.e contained in each TroubleTicketValue of the array) must be found otherwise the XML FinderException message should be sent. If the same key is duplicated (i.e there is more than one entry in the array targeting the same trouble ticket) then the XML DuplicateKeyException message is sent. The operation is atomic i.e. the operation must successfully update all the attributes of the ALL the corresponding trouble ticket otherwise the XML SetException message is sent (assuming that all the trouble tickets were found i.e XML FinderException was not sent and no key duplication was present). This is a version of the setTroubleTicket request that allows the client to set a number of TroubleTickets (passing in a list of TroubleTicketKeys to identify those TroubleTickets) with the same values (passing in a single TroubleTicketValue). All the trouble tickets matching the provided keys are set with the attribute values provided in the trouble ticket value. All the entities matching the provided keys must be found otherwise the javax.ejb.FinderException should be raised. The operation is atomic i.e. the operation must successfully update all the attributes of the ALL the corresponding trouble ticket otherwise the javax.oss.SetException is raised (assuming that all the trouble tickets were found i.e the javax.ejb.FinderException was not raised). Only the message header is returned. This is sufficient to indicate that the TroubleTickets were changed. It is assumed that a successful completion will update all the attribute values of the ALL the trouble tickets matching the provided keys with values based on the Trouble ticket Value modifier or that no changes will be commited. The following exceptions are returned if an error occurrs. All the trouble tickets matching the provided keys are set with the attribute values provided in the trouble ticket value. All the entities matching the provided keys must be found otherwise the javax.ejb.FinderException should be raised. The operation is atomic i.e. the operation must successfully update all the attributes of the ALL the corresponding trouble ticket otherwise the javax.oss.SetException is raised (assuming that all the trouble tickets were found i.e the javax.ejb.FinderException was not raised). This is a version of the setTroubleTicket request that allows the client to set all the TroubleTickets matching an TroubleTicketTemplate with the same values (passing in a single TroubleTicketValue). Only the trouble tickets matching all the attribute values provided in the value template are updated. Only the message header is returned. This is sufficient to indicate that the TroubleTickets were changed. It is assumed that a successful completion will update all the attribute values of the ALL the trouble tickets matching the template with values based on the Trouble ticket Value modifier. The following exceptions are returned if an error occurrs. If no trouble ticket matching the value templates are found then no exception is raised. The exceptions and their semantics are the same than the ones raised in the equivalent JVT operation. The operations are atomic i.e. the operation must successfully update all the attributes of the ALL the corresponding trouble ticket otherwise the javax.oss.SetException is raised. This is a version of the setTroubleTicket request that allows the client to set all the TroubleTickets matching at least one of the TroubleTicketTemplate with the same values (passing in a single TroubleTicketValue). Only the message header is returned. This is sufficient to indicate that the TroubleTickets were changed. The following exceptions are returned if an error occurrs. If no trouble ticket matching the value templates are found then no exception is raised. The exceptions and their semantics are the same than the ones raised in the equivalent JVT operation. The operations are atomic i.e. the operation must successfully update all the attributes of the ALL the corresponding trouble ticket otherwise the javax.oss.SetException is raised. This request is used to escalate multiple Trouble Tickets given their keys. The operation is atomic i.e. the operation must successfully escalate all the corresponding trouble tickets otherwise the EscalateTroubleTicketException is raised (assuming that all the trouble tickets were found FinderException was not raised). The return type for the operation is just the header. It is assumed that a successful completion will escalate all the trouble tickets matching the provided keys or that no changes will be commited. The operation is atomic i.e. the operation must successfully escalate all the corresponding trouble tickets otherwise the EscalateTroubleTicketException is raised (assuming that all the trouble tickets were found FinderException was not raised). This request is used to escalate all the targeted TroubleTickets using the template Trouble Ticket value. All the trouble tickets matching the attribute values provided in the value template are escalated. The operation is atomic i.e. the operation must successfully escalate all the corresponding trouble tickets otherwise the EscalateTroubleTicketException is raised. The return type for the operation is just the header. It is assumed that a successful completion will escalate all the trouble tickets matching the template. If no trouble ticket matching the value template is found then no exception is raised. The javax.ejb.ObjectNotFoundException should only be raised if the TroubleTicketKey is provided as part of the Value template. This request is used to escalate all the targeted TroubleTickets using the Trouble Ticket template(s). All the trouble tickets matching the attribute values provided in the value template(s) are escalated. The operation is atomic i.e. the operation must successfully escalate all the corresponding trouble tickets otherwise the EscalateTroubleTicketException is raised. The return type for the operation is just the header. It is assumed that a successful completion will escalate all the trouble tickets matching the template(s). If no trouble ticket matching the value templates is found then no exception is raised. The FinderException should only be raised if all the Value Template(s) are populated with a TroubleTicketKey value and no object is found. This is the plural version of the CloseTroubleTicket request. The only difference is that it takes a list of TroubleTickets to be closed (indicated by a list of TroubleTicketKeys). All the trouble tickets matching the provided keys are closed. The operation is atomic i.e. the operation must successfully close all the corresponding trouble tickets otherwise the proper Exception messages should be sent. Only the message header is returned. This is sufficient to indicate that the TroubleTickets were closed. It is assumed that a successful completion will close all the trouble tickets matching the provided keys or that no changes will be commited. The following exceptions are returned if an error occurrs. This is a close operation, that determines which TroubleTicket to close by using an associative lookup. TroubleTickets are closed based on the values of the attributes in the TroubleTicketValue template passed into this request. This operation is not MANDATORY. Only the message header is returned. This is sufficient to indicate that ALL the TroubleTickets were closed. The following exceptions are returned if an error occurrs. This is a close operation, that determines which TroubleTicket to close by using an associative lookup. TroubleTickets are closed based on the values of the attributes in the TroubleTicketValue templates passed into this request. Only the message header is returned. This is sufficient to indicate that ALL the TroubleTickets were closed. The following exceptions are returned if an error occurrs. This request is used to cancel multiple Trouble Tickets given their keys. All the trouble tickets matching the provided keys are canceld. All the entities matching the provided keys must be found otherwise the FinderException should be raised. The operation is atomic i.e. the operation must successfully cancel all the corresponding trouble tickets otherwise the CancelTroubleTicketException is raised (assuming that all the trouble tickets were found i.e the javax.ejb.FinderException was not raised). The return type for the operation is just the header. It is assumed that a successful completion will cancel all the trouble tickets matching the provided keys or that no changes will be commited. The operation is atomic i.e. the operation must successfully cancel all the corresponding trouble tickets otherwise the CancelTroubleTicketException is raised (assuming that all the trouble tickets were found i.e the javax.ejb.FinderException was not raised). All the trouble tickets matching the attribute values provided in the value template are canceld. If no trouble ticket matching the value template is found then no exception is raised. The operations are atomic i.e. the operation must successfully cancel all the corresponding trouble tickets otherwise the CancelTroubleTicketException is raised. The return type for the operations is just the header. It is assumed that a successful completion will cancel all the trouble tickets matching the template. If no trouble ticket matching the value templates are found then no exception is raised. The ObjectNotFoundException should only be raised if the TroubleTicketKey is provided as part of the Value template. All the trouble tickets matching the attribute values provided in the value template(s) are cancelled. If no trouble ticket matching the value templates is found then no exception is raised. The operations are atomic i.e. the operation must successfully cancel all the corresponding trouble tickets otherwise the CancelTroubleTicketException is raised. The return type for the operations is just the header. It is assumed that a successful completion will cancel all the trouble tickets matching the template. If no trouble ticket matching the value templates are found then no exception is raised. The FinderException should only be raised if all the Value Templates are populated with a TroubleTicketKey value and no object is found. The following is an XML representation of an TroubleTicket. TroubleTicketKey (uniquely identifies an TroubleTicket) This is a representation of a Trouble Ticket Value array. The TroubleTicketKey uniquely identifies an TroubleTicket. This is a representation of a Trouble Ticket Key array. The TroubleTicketKeyResult encapsulates all the information necessary to indicate the result of a BEST EFFORT operation on a specific trouble ticket. The trouble ticket key result is used in operations involving the update of multiple managed entities, in the deletion of multiple managed entities or in the creation of multiple managed entities. It contains thetrouble ticket entity key, a Boolean value indicating if the set, delete or create operation was succesfull for that managed entity and finally a reason for the failure This is a representation of an array of Trouble Ticket Key Results returned by a Best Effort Template based bulk operation This is a representation of a ActivityDuration array. This is a representation of an Authorization array. This is a representation of a CustomerRoleAssignment array. This is a representation of a Escalation array. This is a representation of a RepairActivity array. This is a representation of a SPRoleAssignment array. This is a representation of a TroubleLocationInfo array. This is a representation of a AccessHours array. This is a representation of a TimeInterval . This is a representation of a TimeInterval array. This is a representation of a TimeInterval . This is a representation of a suspect object. This is a representation of an array of suspect objects. The EscalationList is a MultiValuedList, used In oder to minimize the amount of data required to add or remove a single attribute value from the corresponding TT multi-valued attribute. The RelatedAlarmList is a MultiValuedList, used In oder to minimize the amount of data required to add or remove a single attribute value from the corresponding TT multi-valued attribute. The RepairActivityList is a MultiValuedList, used In oder to minimize the amount of data required to add or remove a single attribute value from the corresponding TT multi-valued attribute. The ActivityDurationList is a MultiValuedList, used In oder to minimize the amount of data required to add or remove a single attribute value from the corresponding TT multi-valued attribute. The CloseTroubleTicketException exception is returned by the OSS through Java XML/JMS interface to report that the invoked TryCloseTroubleTicket(s) or CloseTroubleTicket(s) could not be completed. The CancelTroubleTicketException exception is returned by the OSS through Java XML/JMS interface to report that the invoked TryCancelTroubleTicket(s) or CancelTroubleTicket(s) could not be completed. The EscalateTroubleTicketException exception is returned by the OSS through Java XML/JMS interface to report that the invoked TryEscalateTroubleTicket(s) or EscalateTroubleTicket(s) could not be completed. The following is an XML representation of the QueryAllOpenTroubleTickets. The following is an XML representation of the QueryByEscalation. An Event that is sent in the case in which some value of the TroubleTicket has changed. The event is thrown in the case of 1) setTroubleTicket(s).Request has been called and changed the value of an TroubleTicket 2) Some values of the TroubleTicket have been changed during the execution of a TroubleTicket by implementation. . Base Content of Attribute Value Change Event An Event that is published in the case where a new TroubleTicket is created. The event is emitted when a new TroubleTicket is created Base Content of Create Event An Event that is published in the case where a TroubleTicket is closed. Base Content of CloseOut Event An Event that is published in the case where a TroubleTicket is cancelled. Base Content of Cancellation Event An Event that is published in the case where the is a TroubleTicket Status Change. Base Content of StatusChange Event