View table: JDTest_FeatureSupport
Table structure:
- prodshort - String
- feature - String
- GenesysEngageMulticloud - Wikitext
- GenesysEngageOnPrem - Wikitext
- comment - Wikitext
This table has 5 rows altogether.
| Page | prodshort | feature | GenesysEngageMulticloud | GenesysEngageOnPrem | comment |
|---|---|---|---|---|---|
| User:Jdruker/FeatureSupport | GIM | Data Export | yes | yes | The method of accessing the export package is different in Genesys Engage multicloud, but support for the feature itself is unchanged. |
| User:Jdruker/FeatureSupport | GIM | GDPR support | yes | yes | The method of providing the input JSON file is different in Genesys Engage multicloud, but support for the feature itself is unchanged. |
| User:Jdruker/FeatureSupport | GIM | Interaction threads | no | yes | Link to on-premises information: Interaction Threads |
| User:Jdruker/FeatureSupport | GIM | SDR reporting | no | yes | The feature will be supported when Designer supports sending reporting data via Kafka |
| User:Jdruker/FeatureSupport | GIM | UI to manage Genesys Info Mart | no | yes | There is no equivalent to GIM Manager in Genesys Engage multicloud. Some monitoring features formerly provided by GIM Manager — for example, ?latency? — are available through Prometheus and/or logs, but there is no ability to run jobs on an ad hoc basis, schedule jobs, and so on. |