Published content within Content Publishing cannot be saved or edited in a language other than the base language of the instance - Known Error

Published content within Content Publishing cannot be saved or edited in a language other than the base language of the instance Description An issue has been identified preventing published content within Content Publishing - Content Layout from being saved or edited in a language other than the base language of the instance.

The issue is only experienced when the Agent Workspace for HR Case Management (sn_hr_agent_ws) application is installed before the Content Publishing (sn_cd) application.

As a result, the Schedule Content (sn_cd_content_visibility) table is installed in the "Agent Workspace for HR Case Management" scope, when it should have been installed in the "Content Publishing" scope.

Steps to Reproduce

Install Agent Workspace for HR Case Management application. Install Content Publishing application. Install any language pack (i.e. German). Enable ' sn_cd.enable_language_switching ’ system property. Go to Content Publishing - Content Library. Create a Rich Content record in English and Publish it (or update an existing Published record). Open the previous record. Change your language to German. The "Editor öffnen" button is enabled. Click it to launch the editor. Edit any content and click the "Speichern" button to save the changes. Expected result : Edited content can be saved. Actual result : Edited content cannot be saved and the following is experienced:

403 error on the network tab of the Web Browser: /api/now/table/sn_cd_content_portal/[SYS_ID]?sysparm_display_value=all&sysparm_input_display_value=true Node logs display this warning: com.glide.script.RhinoEcmaError: "isPublished" is not defined. sys_script_include.c404c384432021101080006e99b8f26a.script Workaround This issue has been permanently fixed for new installations with these versions:

Content Publishing (sn_cd): com.snc:app-content-publishing-34.0.2 Agent Workspace for HR Case Management (sn_hr_agent_ws): app-hr-workspace-v2-4.0.0 There is no workaround. To fix existing instances impacted by this issue , the Schedule Content (sn_cd_content_visibility) table scope must be updated from “Agent Workspace for HR Case Management” to “Content Publishing”. This fix is a database update that cannot be accomplished by an admin user; it requires assistance from Customer Support.

FAQ:

Q. How to confirm if an instance is impacted? A. Check the Schedule Content (sn_cd_content_visibility) table scope. Navigate to Tables (sys_db_object), filter on Name=sn_cd_content_visibility and personalize list to display ‘Package’ column which contains the scope value for the record:

If the table scope is "Content Publishing" then the instance IS NOT impacted If the table scope is "Agent Workspace for HR Case Management" then the instance IS impacted Q. How will impacted instances receive the fix? A. External communications (COMM) notifications are being sent to customers of impacted instances.

For impacted production instances, Customer Support will proactively create a case and contact the instance owner to schedule the change request to apply the fix. For impacted sub-production instances, customers can raise a case with Customer Support to have the fix applied. When creating the Customer Support Case, reference this KB article and a Technical Support Engineer will schedule the Change request to implement this fix. Q: Will the implementation of the fix cause downtime or impact performance? A: No downtime and no performance impact are expected when applying the fix.

Q. Are regulated environment instances impacted? A. Yes, if they meet the criteria listed above.

Q. Are On-Premise instances impacted? A. Yes, if they meet the criteria listed above.

Q. Once the fix via Change request is implemented on an instance, is there anything else needed to address this issue? A. No, nothing else is needed once Customer Support applies the fix.