Re: Line Breaks via Remedy REST API

2018-06-25 Thread LJ LongWing
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

Line Breaks via Remedy REST API

2018-06-25 Thread Kevin M Candelaria
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

Re: Line Breaks via Remedy REST API

2018-06-25 Thread Kevin M Candelaria
{ "values": { "Submitter": "appadmin", "Work Log Submitter" :"Michael

Re: Line Breaks via Remedy REST API

2018-06-25 Thread LJ LongWing
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

RE: [E] Re: Line Breaks via Remedy REST API

2018-06-25 Thread Fred Grooms via ARSList
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

Re: [E] Re: Line Breaks via Remedy REST API

2018-06-25 Thread Kevin M Candelaria
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

Log says escalation enabled AND "is turned off"

2018-06-25 Thread Joel D Sender
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