While running portal in Pega Constellation I am getting below error.
Can you check whether “CoExistanceCaseDT” data transform exists?
Hello, Just create the rule that system says as missing, which is CoexistenceCasesDT in @baseclass.
The CoExistenceCasesDT missing error is actually a known issue in Pega Constellation. The important thing is that the error itself is usually not the root cause of the portal failing to load. It is an internal Data Transform used by the Constellation coexistence framework and it is created only when required. This is a handled exception and should not stop the application or portal from loading.
If your portal keeps loading indefinitely, then something else is usually failing. Check you browser console and look for HTTP forbidden or TLS errors. If you find those(HTTP 403 or TLS is not enabled - most common), then its a config problem.
Make sure the following DSS - ConstellationSvcURL and ConstellationPegaStaticURL pounts to the correct URL. Also, if you are using constellation through OAuth, validate your OAuth security settings.
If you simple go ahead and create an empty DT with the same name, it will only remove the exception from the logs which only suppresses the symptom and does not fix the underlying portal-loading problem if another configuration issue exists
This is fixed in the latest patch versions. Can you confirm your Pega version?
We are working on Pega 24.2.4
In that case, this DT is not the problem. Its happening probably due to a misconfiguration somewhere. When you launch the portal, what do you see - page stuck at loading with a spinner or a blank page?
Can you please check the browser/network console by pressing F12 and see if there are any HTTP or TLS errors as I have mentioned above?
I checked for both DSS, have no values. Also we can’t check the console, so can’t say anything on HTTP or TLS error.
Yes when we launch the portal, page stuck at loading with a spinner. Even if we try to open a case or create a case through dev studio same loading issue occurs.
If it is stuck with a spinner, then mostly it is related to TLS error as we have seen with other clients. You need to validate your configurations specifically on the Oauth side.