Copying journal entries throws an NPE when the target table doesn't have Comments or Work Notes fields - Known Error

Copying journal entries throws an NPE when the target table doesn't have Comments or Work Notes fields Description The new journal entry copying mechanism assumes the target table has a comments and/or work_notes journal field, and doesn't check before attempting to modify said fields. This results in a null pointer error. Steps to Reproduce

Create a Connect Action that creates a record off of a support conversation (replace "new_call" with any non-TASK based table, or any table without comments or work notes).

response.newRecord("new_call", { short_description: conversation.document.short_description || "", caller: conversation.document.opened_by });

Create a Support conversation.

As the agent, use the new action to spawn a new record.

Submit the record form.

Note that the action doesn't behave as expected, and there is a null pointer error in the logs.

Workaround Add Work Notes and Comment journal fields to the table.