Notifications

524 views

Description

When sending a very large email from the email client, the following errors appear in the localhost log and the email is not saved or sent:

WARNING *** WARNING *** Evaluator: org.mozilla.javascript.EcmaError: "sys_email" is not defined.
Caused by error in <refname> at line 1
==> 1: sys_email.sys_id

WARNING *** WARNING *** Evaluator: org.mozilla.javascript.EcmaError: "sys_email" is not defined.
Caused by error in <refname> at line 1
==> 1: sys_email.body.sys_meta.internal_type

WARNING *** WARNING *** Evaluator: org.mozilla.javascript.EcmaError: "sys_email" is not defined.
Caused by error in <refname> at line 1
==> 1: sys_email.body.getED().getInternalType() == 'string'

WARNING *** WARNING *** Evaluator: org.mozilla.javascript.EcmaError: "sys_email" is not defined.
Caused by error in <refname> at line 1
==> 1: sys_email.reply_to.getDisplayValue()

WARNING *** WARNING *** Evaluator: org.mozilla.javascript.EcmaError: "sys_email" is not defined.
Caused by error in <refname> at line 1
==> 1: sys_email.recipients.getDisplayValue()

WARNING *** WARNING *** Evaluator: org.mozilla.javascript.EcmaError: "sys_email" is not defined.
Caused by error in <refname> at line 1
==> 1: sys_email.copied.getDisplayValue()

WARNING *** WARNING *** Evaluator: org.mozilla.javascript.EcmaError: "sys_email" is not defined.
Caused by error in <refname> at line 1
==> 1: sys_email.blind_copied.getDisplayValue()

WARNING *** WARNING *** Evaluator: org.mozilla.javascript.EcmaError: "sys_email" is not defined.
Caused by error in <refname> at line 1
==> 1: sys_email.subject.getDisplayValue()

WARNING *** WARNING *** Evaluator: org.mozilla.javascript.EcmaError: "sys_email" is not defined.
Caused by error in <refname> at line 1
==> 1: sys_email.sys_id

WARNING *** WARNING *** Evaluator: org.mozilla.javascript.EcmaError: "sys_email" is not defined.
Caused by error in <refname> at line 1
==> 1: sys_email.body.getDisplayValue()

Steps to Reproduce 

  1. Log in to a base system instance.
  2. Navigate to Incident > Open.
  3. Open any incident record.
  4. Check for the email client on the record.



  5. If the email client is not visible:
    1. Navigate to System Definition > Dictionary.
    2. In the Table column, find Incident (Type = Collection).
    3. In the Attributes section or tab, add the attribute email_client=true.
  6. Click the email client icon.
  7. Enter a valid recipient email address.
  8. Paste in the content of the attached Change content.rtf file.
  9. Try sending the message.
    Note that the email is not sent.

Workaround

This is expected behavior and cannot be changed in any current or future release. The email client is not intended for large email messages and is limited to 1Mb by default. The general limit on a POST submission is 2Mb. When a large file is pasted into the email client and then combined with other system-generated data in the POST, the volume of data exceeds the amount the system is able to receive.

There is a related issue where unsaved comments and work notes are placed into the URL. For more information, see KB0598961: Email client quick message from incident form fails to open when long text is present in work notes or additional comments fields.


Related Problem: PRB619995

Seen In

Calgary Patch 5
Fuji Patch 12 Hot Fix 1

Associated Community Threads

There is no data to report.

Article Information

Last Updated:2017-01-16 12:27:28
Published:2017-01-09
Change Content.rtfPRB619995_screenshot.png