Jump to: navigation, search

Jdruker/AlternativeAlternativeDataStreamsTable

Example of possible alternative format

Tanya, the following is the format you suggested, but I don't think we should use it because when a particular feature is available in Cloud is not a function of the GIM release. So we'll have some rows where both columns are the same, even if the actual dates when effective support became available in premise vs. cloud are different. And the cases where one of the columns is not populated will either (usually?) be because of the data source or because GIM has not been upgraded to that version for any tenant in the Cloud. So not only will this format tie us in to constant maintenance based on an XPD (with all the attendant issues of co-ordination and notification), but the resulting information will be confusing. But there is value in being able to tell cloud vs. premise support at a glance, so if we're willing to accept the constant maintenance (which would be a trivial update to a boolean parameter in the Library markup), maybe we could keep it as one "Introduced in GIM" column and add an "Available in" column that straddles checkmark-only columns "On-Premises" and "Cloud".

Error: No field named "Feature" found for any of the specified database tables.
Application Data Source Reporting Feature Delivery Mechanism Introduced in Genesys Info Mart Release More information
On-Premises Cloud
This page was last edited on March 25, 2019, at 18:28.
Comments or questions about this documentation? Contact us for support!