What change types are part of the Genesys Cloud API Change Management Policy?

The Change Management Policy for the Genesys Cloud API includes several categories specifically designed to manage how changes are communicated and enacted. One of the key types involved in this policy is deprecations.

Deprecation refers to the process of marking a feature or functionality as obsolete, signaling to users that it may be removed in the future. This is crucial for maintaining a structured approach to software development and user experience, allowing developers and users to adapt their applications and strategies accordingly before any feature is fully removed. By providing a clear indication that certain functionalities will no longer be supported, Genesys ensures that users have sufficient time to transition to newer alternatives, thus minimizing disruption and enhancing overall service reliability.

In contrast, the other options, while they may relate to various aspects of change management, do not represent the specific categories highlighted within the Change Management Policy. The daily change type would imply frequent updates which are more routine, while breaking changes are typically higher severity adjustments that may not align with the more measured approach of deprecation. Emergency changes would suggest urgent revisions without the preparatory context that deprecation provides. Overall, the structure surrounding deprecation within the policy supports long-term sustainability and user adaptation towards changes in the API.