When using g_form.setMandatory in a client script to set work_notes or comments fields mandatory the Post button disappears - Known Error

When using g_form.setMandatory in a client script to set work_notes or comments fields mandatory the Post button disappears Description The post button disappears if using a client script to set the work_notes or comments fields to mandatory.

Steps to Reproduce

Create a client script on the incident table. Set On Change, for assigned_to field In the script add g_form.setMandatory("work_notes", true);

Testing by adding an assignee to the incident record the post button will disappear Also occurs for "comments" field

Workaround This is expected behavior and by design in all currently supported releases.

When the Journal field on the form is mandatory the Post button on the Activity Stream is disabled by design. Posting in the Activity Stream compose field would clear the value in the journal field of the Form. This would cause an error when saving because it is mandatory. For this reason, the Post button is disabled and they may use the Save/Update to post comments. Due to the number of defects this caused it will not be reverted to the previous behaviour. As an alternative, if the journal/comment field is not mandatory this will enable the Post button.