Routing Rule New Line Syntax
Hi all,
I'm working on a routing rule for Ens.Alert. I'd like to add some text to the email alert but I'm having trouble formatting the text. I want a new line after the original alert with my own text. I will attach a screenshot. Looking at the "assign" line, I'm looking for what I need to use in place of "\r\n" to make a new line.
(I had troubles uploading the screenshot, but the only thing that is missing in the picture is the end of the sentence and an ending ")
Best,
Erin
Comments
I do this via a DTL, but I would think it would work here. I use $char(13).
Good luck,
Brian
As @Brian Schoen alluded to, $CHAR -- abbreviated to $C if you want to be one of the cool kids -- is what you need. $C(13,10) is the line-end sequence in Windows. $C(10) is Unix. $C(13), though, is old-school Macintosh* 
* Also works for HL7 Segment delimiters 
Hi Jeff.
Since I'm one of the cool kids, I used $C. However, I get the following error whether I use $C, $CHAR and $Char. If I get rid of the $C(13,10) then my new text appends to Document.AlertText as I would expect. I have gone through the documentation but I'm not finding anything. Any suggestions? It seems like it should be simple.
.png)
Thanks,
Erin
Mmmyyyeaaaaaah, You're going to want to do that in a DTL:
Create a rule that appends the text to the target.AlertText property:
You can add conditionals to provide different alert explanation values based on the SourceConfigName or by parsing the source.AlertText text to find something interesting.
Finally, stick the DTL in the Send rule for whatever operation you're sending alerts to.
In my experience, most/all $ objectscript functions ($CHAR, $PIECE, etc) are not available for use in a Routing Rule. Some of them ($PIECE for example) have "built-in" workarounds in the defined Utility Functions - so in the rule, you can just do "Piece(foo,bar,x,y)" just like you would normally use elsewhere, sans $.
My use case for wanting a linebreak available in a Routing Rule is slightly different from @Erin Dolson 's
(I wanted to output some slightly neater Trace messages) but I think what I did below would work for that + other use cases as well.
Just for fun / to prove it is possible, I created a workaround that will retrieve a $C(13,10), by using a custom utility function:
1. In a class that was already extending Ens.Rule.Functionset, I defined a new classmethod:
/// Get linebreak chars (Carriage Return, Line Feed; ASCII 13, 10). Intended for use in routing rules (trace) where CRLF is not easily accessible.ClassMethod CRLF() As %String
{
q $C(13,10)
}2. In my Routing Rule, I call the function in a Trace (or Assign) action's Value node like any other:
.png)
and the trace itself looks like:
.png)
[You could easily modify the new utility function to pass back any other char - or really, the best solution IMHO (which I will probably end up implementing in my environment) would just be to create the full wrapper to $CHAR itself via a passed parameter and call it "CHAR"]
FYI / N.B.: I'm on HealthShare (Ensemble) Health Connect 2018.1 but I'm fairly sure this should work for at least as far back as 2016 if not earlier since custom utility functions have been supported for quite some time.
So I went and created the $CHAR wrapper utility function and got it to work; It wasn't *quite* as simple as I thought it would be (couldn't simply pass the whole string parameter through to $C, and need to remember to pass the param as a single quoted string) so I thought I would share in case someone else wanted to go this route :)
As before, review the instructions for Defining Custom Utility Functions and ensure the class extends Ens.Rule.FunctionSet
/// Wrapper to built-in objectscript function $CHAR./// Intended use = linebreaks ($C(13,10)) in routing rules (trace) where CRLF not easily accessible.ClassMethod Char(pCharString As%String) As%String
{
#dim outString,thisChar As%String = ""#dim numChars As%Integers numChars = $L(pCharString, ",")
//q:(numChars<2) $C(pCharString)if (numChars<2){ s outString = $C(pCharString) }
// more than one char, iterate over them to call $C and build outStringelse{
for n=1:1:numChars {
s thisCharCode = $P(pCharString, ",", n)
s outString = outString_$C(thisCharCode)
}
}
q outString
}I originally had the post-conditional quit for the single-char cases, but felt assigning and using outString was slightly better since it was more consistent coding. Though I wonder if the post-conditional is slightly more efficient... (very outside of my wheelhouse)
Then make sure to pass a single quoted string in the Routing Rule, but otherwise it's just like calling $C:
.png)