The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
The following practices are recommended to all developers. The aim is to reduce the number and extent of any updates that may be necessary.
The order of elements within the interface schema and messages may change, within the constraints of the interface specification. Developers should avoid unnecessary dependence on the order of elements to interpret information exchanged with Cisco Unified Communications Domain Manager 10.6(x).
New interface methods, operations, actions, requests, responses, headers, parameters, attributes, other elements, or new values of existing elements, may be introduced into the Cisco Unified Communications Domain Manager 10.6(x) interfaces. Developers should disregard or provide generic treatments where necessary for any unknown elements or unknown values of known elements encountered.
Notifications, operations, methods, actions, requests, responses, headers, parameters, attributes, and other elements from previous versions ofCisco Unified Communications Domain Manager 10.6(x) interfaces, will remain, and will maintain their previous meaning and behavior to the extent possible and consistent with the need to correct defects.
Applications should not be dependent on interface behavior resulting from defects (behavior not consistent with published interface specifications), since the behavior can change when defects are fixed.
The use of deprecated methods, operations, actions, handlers, requests, responses, headers, parameters, attributes, or other elements should be removed from applications as soon as possible to avoid issues when those deprecated items are removed fromCisco Unified Communications Domain Manager 10.6(x) or its interfaces.
Application Developers should be aware that not all new features and new supported devices (for example, phones) will be forward compatible. New features and devices may require application modifications to be compatible or to make use of the new features or devices.
The Developer tools that are available in Mozilla Firefox and Google Chrome allow all the actions exposed by each API to be displayed as they are being called in the GUI. This gives us the opportunity to view the request and response actions as they occur, and provide the details of what each API provides and its relationship to the GUI.
With Developer tools enabled, the network tab of the Developer tools show the information that is contained in each request and response as you navigate and use the GUI. This allows service providers a direct view as to what data each API requires.