Difference between revisions of "Template: DeprecationNoticeList"
From Genesys Documentation
(Edited the Engage FAQs section) |
|||
| Line 27: | Line 27: | ||
}} | }} | ||
{{ConditionalText|Genesys Engage= | {{ConditionalText|Genesys Engage= | ||
| − | == | + | ==FAQs== |
| − | === | + | ===Why does Genesys deprecate features and functionality? === |
Maintaining multiple versions of the same functionality impacts our ability to provide the most value to as many customers as possible. | Maintaining multiple versions of the same functionality impacts our ability to provide the most value to as many customers as possible. | ||
| − | === | + | ===What happens when Genesys announces a deprecation? === |
A feature deprecation signifies that Genesys will cease enhancements or improvements to what is being deprecated. Our intention is to let you know as early as possible that we are making a change, and to help you if you are impacted by that change. | A feature deprecation signifies that Genesys will cease enhancements or improvements to what is being deprecated. Our intention is to let you know as early as possible that we are making a change, and to help you if you are impacted by that change. | ||
| − | === | + | ===How much notice will Genesys give for deprecations? === |
There will be a minimum of 6 months from the day of announcement before the feature or functionality is retired. | There will be a minimum of 6 months from the day of announcement before the feature or functionality is retired. | ||
There can be circumstances requiring the accelerated retirement of functionality: | There can be circumstances requiring the accelerated retirement of functionality: | ||
| − | Essential Changes: These represent changes necessary to ensure the integrity of our services, and therefore need to occur as quickly as possible. In these situations, customer communications will be issued with as much advance notice as possible. | + | * '''Essential Changes:''' These represent changes necessary to ensure the integrity of our services, and therefore need to occur as quickly as possible. In these situations, customer communications will be issued with as much advance notice as possible. |
| − | Third-party Software: Features and functionalities integrated with third-party software may need to be retired due to the third-party vendor making their piece of the integration unavailable. In these situations, the timing and pace of the retirement is determined by the third-party vendor, and customer communications will be issued with as much advance notice as possible. | + | * '''Third-party Software:''' Features and functionalities integrated with third-party software may need to be retired due to the third-party vendor making their piece of the integration unavailable. In these situations, the timing and pace of the retirement is determined by the third-party vendor, and customer communications will be issued with as much advance notice as possible. |
| − | === | + | ===Is there a way I can keep the old feature or functionality? === |
No. Once the deprecation date is reached, the feature will be removed. | No. Once the deprecation date is reached, the feature will be removed. | ||
| − | === | + | ===What communication will Genesys give for deprecation? === |
Genesys Advisors and/or Account Managers will communicate deprecations. | Genesys Advisors and/or Account Managers will communicate deprecations. | ||
Deprecation notifications will be posted here on the Genesys Engage documentation site and will be communicated via in-product messaging when appropriate. | Deprecation notifications will be posted here on the Genesys Engage documentation site and will be communicated via in-product messaging when appropriate. | ||