- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-17-2017 01:22 AM
SEVERE *** ERROR *** REST Msg Outbound - RESTMessageClient : Error constructing REST Message/Method: org.mozilla.javascript.Undefined@967d97/org.mozilla.javascript.Undefined@967d97
java.lang.IllegalArgumentException: No enum constant
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-25-2017 01:43 AM
Thanks for the reply Chuck.
Sorry for the delayed response.
The error is caused by the presence of two UI Macros:- business rule outbound rest and business rule outbound rest formatter.
You can refer the workaround in the below mentioned link:-

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-17-2017 05:43 AM
Can you provide some additional details on what you are trying to accomplish? Details (table names, catalog items, etc) are encouraged. Screen shots are always appreciated. Any scripts involved are helpful too!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-17-2017 10:54 PM
Thanks for the reply Chuck.
Actually I have been assigned a task to find this error and report it.We need to fix this issue.
Any help will be appreciated.

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-18-2017 06:17 AM
I would start by going through System Web Services> REST> Outbound and inspecting the outbound REST messages and their associated methods. If possible, use the "test" button to try them out (note, you may need to supply sample variables for URI parameters.) After each test, check the log.
If that fails to yield results, I recommend reaching out to customer support. I'll be interested to hear what they have to say.
HI Service Portal - ServiceNow
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎05-25-2017 01:43 AM
Thanks for the reply Chuck.
Sorry for the delayed response.
The error is caused by the presence of two UI Macros:- business rule outbound rest and business rule outbound rest formatter.
You can refer the workaround in the below mentioned link:-