HTML form field allows base64 image content insertion as value, due to which it automatically re-attaches images from the field into the form - Known Error

HTML form field allows base64 image content insertion as value, due to which it automatically re-attaches images from the field into the form Description When you copy-paste text + images (from Word, email, etc.) to an HTML Field and save the record quickly without waiting the upload to be completed, reloading the record automatically re-attaches images to the record and gets displayed in the Activity stream as a new attachment.

Steps to Reproduce

1. Open an existing Incident record from Service Operations Workspace. 2. Create a new HTML Field in this record. 3. In the HTML field copy-paste text + images from a Word doc or email. 4. save the form. (try to submit the request as soon as notifications start appearing and html field is out of loading state, try pasting from a .docx or email for better replication) 5. Reload the form.

Expected behaviour: Record form opens normally and images are not getting reattached.

Actual behaviour: Images from the variable are getting reattached everytime you open the record. Newly re-attached images are show in the Activity Stream. These images can also be found in the sys_attachment table.

(Please note from here on, we will refer a record as a broken/corrupt record which has an HTML field which does not save the images properly and causes multiple uploads)

Workaround Preventing a corrupt record from being created: If one doesn't want the issue to happen to their newly created record, they should ensure to wait for some moment before saving the form, when the image upload is in progress.

Fixing a broken record: Assuming the HTML Field is not readonly, another way to stop this in existing records is by:

1) Open the form and see that the activity stream of the record is showing all the images getting uploaded one by one. 2) After all the upload is done, click inside the HTML field and then outside of it. This should make the form dirty/unsaved (you can observe a "º" on the record tab). If the form doesn't become dirty/unsaved, just cut all the content from the HTML field and paste it there again (and wait for the upload to be completed). This should definitely make the form go to dirty/unsaved state. 3) Save it again. 4) Now if you close and reopen the form, it should not be having the issue anymore.