Not able to save context dictionary in Pega Marketing 8.4
Hi Team,
I am not able to save context dictionary in pega marketing 8.4. The progress bar is not moving forward. Please find the screenshot.
Do I need to enable any agent or configuration? It was working fine in 8.3 marketing. Thanks in advance.
Regards,
Nizam
***Edited by Moderator Marissa to update Platform Capability tags****
Hi Raghu,
Please find the audit log screenshot. I have also seen the log files but there were no exceptions related to this.
Regards,
Nizam
BTW: I saw that it is configured to use ICEApp:Artifacts as the ruleset to save the rules. Our recommendation is to use the Rules ruleset to save anything related to Context Dictionary as Artifacts is used to save any rules generated runtime.
I would suggest you to try saving it again. Please follow these steps:
The Save button is currently hidden as iI guess it has failed midway. Please update the IsContextDictionarySaveIsInProgress DSS and set the value to false.
Switch to App Studio
Launch Tracer and in its settings, please check the Asynchronous Activity checkbox in the Event Types.
Go to Context Dictionary landing page and hit Save and click Save in the popup.
In Tracer you will see a line highlighted in green line with the value "Queue Activity" under the Event Type column. Please click on the Queue Activity value and check if there are any failures in the traced activity.
The above will help you debug and identify the failure.
Thanks Raghu. I am getting the below exception in tracer. There is a function "GetDatabaseType" which is getting failed.
Regards,
Nizam
This usually is an indication of the codesets not loaded properly. Can you please try restarting your instance and clear the temp folder as well and give it another shot.
Based on the exception screenshots, the issue is with utility function. You need clear rule cache and aba cache. And also, re-assemble or save again the rule for which the assembly is failed.
Yes it worked after doing rule reassemble. Thanks.
Hi,
There could be multiple reasons why that can happen. Please click on the Audit Log tab and see if it reports any errors. Also check the logs to see if there is any failures/exceptions. If yes then you would need to investigate in to it or publish it here andwe can take a look.