Open RuleForm harness and private edit the rule and save the harness.As per the image the activity rule is distorted.Check in the scripts and styles whether pzActivityOverrides css is added or not?If it is not present,add the file.
Currently we ran into different other problems which blocks me from checking your suggestions. Also we will run the upgrade script again with a newer JDBC driver, we are not 100% sure whether the initial upgrade ran fine. I will give you guys an update next week, many thanks for your help!
We ran the upgrade wizard once again it didn´t help.
First of all this is the setup:
We migrated our onpremise 7.2.2 Pega environment via Pega Upgrade Wizard to 8.3. We use it in a cloud environment (Openshift) with Tomcat (9.0.31). So the Oracle DB is on premise (Oracle JDBC driver 184.108.40.206.0), the rest is in the cloud / containerized. The Upgrade Wizard was started remotely with ojdbc8 drivers, there where no connectivity issues or the like. The db Setup is a schema copy of our current 7.2.2 environment.
After checking the attached Setup logs two error types pop up a lot:
internal.ddlcomp.DDLGenerator) WARN - Could not find a class definition for History-PegaSample-Integration-Data
( internal.loaders.FastLoader) ERROR - 0 rows updated returned for instance of type Data-Rule-Summary with key RULE-HTML-SECTION EMBED-ACTIVITYSTEPS PZPARAMS (mentioned by PICADA in a previous post).
Also a ORA- error pops up for not being able to call a stored procedure, however we gave the deployment user all rights as described (CALL is not mentioned there, only EXECUTE procedures...). But this shouldn´t be the root cause since we ran the upgrade wizard for another app with the same error, but it didn´t have a negative effect on the Designer Studio UI.
The FastLoader errors seem to be the reason for all the missing rules / artifacts but there is exception which leads to the root cause of this issue. I read that a synch between PR4_RULE_LIBRARY and PR4_RULE_VW tables for rules schema could be an issue here, but for example on our running Pega app for 7.1.9 the mentioned tables / counts for specific rule types also are not in synch, still it works perfectly fine.
What could be the solution for this? Did we miss anything or the like?