Convert unsupported DB vendor specific syntax in Connect SQL to use a PostgreSQL supported function or use application logic to update the query needed; convert schema name.table name to use Pega class references; eliminate unsupported custom DB objects (views, procedures, functions, sequences and triggers) and custom schema names (except OOTB Rules, Data, CustomerData and MKTData)
***Edited by Moderator Marije to change Product details from S.I to Pega 8.8****
This post reads neither as a ‘How to’ Pega product question, nor does it impart any actual Pega-specific Development Knowledge.
The abbreviation GCP appears to referr to ‘Google Cloud Console’. You appear to simply state the role of the Google console. The Google Cloud console provides a web-based, graphical user interface that you can use to manage your Google Cloud projects and resources. I do not believe Pega users need to be told how the console works as that will be documented externally.
As this post does not appear to offer any useful information for Pega developers I will proceed to close the thread.
Posted: 8 months ago
Posted: 20 Mar 2023 16:42 EDT
Sheetal Kumar (kumas10)
Senior Manager, Application Engineering, Financial Services Smart Apps