Installing com.glide.ai_record_activity plugin does not create sys_ai_record_activity shard table causing NullPointerException errors. - Known Error

Installing com.glide.ai_record_activity plugin does not create sys_ai_record_activity shard table causing NullPointerException errors. Description The issue occurs when the AI Record Activity plugin (com.glide.ai_record_activity) is installed. The platform should create the sys_ai_record_activity shard tables during installation, as these are necessary for sharding and retrieving AI record activity details on the record page. However, the shard tables for sys_ai_record_activity are not created after the plugin is installed, causing NullPointerException when the platform tries to access them.

Impacted Versions :

Zurich Patch 4 and above Yokohama patch 11 and above Australia Patch 0. Note : AI Record Activity plugin is GAIC dependencies.

Steps to Reproduce

1. Install the GenAI Q4 feature or upgrade an existing instance to ZP4/Yp11/AP0. 2. Ensure the plugin com.glide.ai_record_activity is installed. 3. Observe system logs or error output. The following error may appear:

Current Behaviour: Error getting record for sys_ai_record_activity: java.lang.NullPointerException.

Expected Behaviour: No errors related to com.glide.ai_record_activity.

Workaround This problem has been fixed. If an upgrade is possible, please refer to the Fixed In section to determine the latest version with a permanent fix that the instance can be upgraded to.

If upgrading to the Fixed version is not possible, you can use the following workaround:

IMPORTANT : Ensure that the Application Scope is set to Global from the Application Picker before running the script. Simply selecting Global scope within Background Scripts is not sufficient, as records may still be created in the session scope.

Run the attached script KB2898934_Workaround_Script as background script.This background script will create the missing sys_ai_record_activity shard tables and synchronize the shard configuration

FAQs

Q: How do I know if an instance is impacted by this problem?

A: Run the attached script Check Impacted Version in background scripts and check for the at_risk value in the output. If the at_risk is true, run the workaround script mentioned above to remediate the issue.

Q. Does this workaround need to applied before upgrade or after upgrade ?

A. This workaround need to be applied only after upgrade to impacted version.