Can you give an example of a body that you are providing that it's removing
those?
On Mon, Jun 25, 2018 at 7:28 AM Kevin M Candelaria wrote:
> Hello,
>
>
>
> It appears that the Remedy REST API does not respect white space and line
> breaks when creating new Work Log entries. Does anyone have a
Hello,
It appears that the Remedy REST API does not respect white space and line
breaks when creating new Work Log entries. Does anyone have a solution for this
(that preferably does not require opening Developer Studio)?
--
ARSList mailing list
ARSList@arslist.org
{
"values": {
"Submitter": "appadmin",
"Work Log Submitter" :"Michael
Ok...so, according to www.json.com, a string need to contain "Any Unicode
character except " or \ or control character".so, white space and
enters are typically going to be considered a control characterso they
are not allowed to be used in strings...so, you didn't specify what the
I see the \n which is correct for a line break in a json. Is the issue that
there should be a line break before and after the line of "Line Break?". If so
then the system that created the json is not converting them correctly (as they
should also have been converted in the json to be \n
This helps, Thanks! the problem was with my node js code.
From: ARSList on behalf of Fred Grooms via
ARSList
Sent: Monday, June 25, 2018 11:51 AM
To: ARSList
Cc: frederick.w.gro...@verizon.com
Subject: RE: [E] Re: Line Breaks via Remedy REST API
I see the
ARSlisters,
I have an unmodified OOB escalation in ITSM that should run, but is 'turned
off'.
It starts the notification process after a survey is created in "SRM:Survey"
LOG:
/* Checking "SRM:SRV:TriggerSurveyNotification" (enabled) : is turned off
/* Checking
7 matches
Mail list logo