go to post Scott Beeson · Jan 19, 2016 I'm curious how this one even happened, it's especially confusing since Timothy is the one that is reporting it!
go to post Scott Beeson · Jan 19, 2016 Another note, UI ambiguities like this are less of an issue if you add simple tooltips.
go to post Scott Beeson · Jan 19, 2016 Oh wow, so that's a "Reply" button? Honestly the arrow is pointing the wrong way. That's the standard for "Forward" and I assumed it was a share button. Please fix.
go to post Scott Beeson · Jan 15, 2016 And just to elaborate a little, what I was trying to do involved a lookup table. Let's say I had an FTP adapter that picked up files from /ftpdir/ and 1 subfolder deep. If I had /ftpdir/green/ /ftpdir/red/ I could then have entries in the lookup table for "green" and "red" and (relatively) easily create a rule to do stuff based on the folder. What I'm trying to do now is be able to block things. So I have a lookup table named "BlockCustomer". I could create the key value pair "green:1" and then use $PIECE on the proposed .SourcePath property to determine if it should be blocked. Although now that I think about it, I guess this could be done with the message header. However if I have multiple facilities for a single customer the given field in the header may differ. I'm not sure.
go to post Scott Beeson · Jan 15, 2016 If you think this is a valid request worth implementing I would think a dedicated property like .SourcePath that contains "/hl7/1/yellow" would be best to avoid as much string manipulation as possible. I'd like to hear other opinions though.
go to post Scott Beeson · Jan 15, 2016 I think using message header information is the obvious solution, but my reasons for doing this were slightly more complicated. No need to elaborate though as I think I'll end up writing a custom function. Thanks for the input. User Dmitry Maslennikov has stated on this StackOverflow question that it does include the full path but when I looked in the viewer it was visually truncated. I hadn't been able to verify in code yet. I'll see if I can validate and if it's not there then use part of the message header.
go to post Scott Beeson · Jan 14, 2016 Looks like there have been some minor modifications, but still...
go to post Scott Beeson · Jan 14, 2016 Perfect! Reminds me of Master Pages for older .NET applications. This is what I suspected but since I didn't know the term "pane" I couldn't search the documentation. Thank you! Perhaps the docs I linked can be updated to reference the page on "panes"
go to post Scott Beeson · Jan 13, 2016 This seems to happen on every form. Also, once you backspace all the content you cannot get the curser back in the editor without refreshing the page.
go to post Scott Beeson · Jan 13, 2016 So is the <form> required or can you specify the data controller some other way?
go to post Scott Beeson · Jan 13, 2016 Looks like they removed this from all but the main index. But you're right, the quality of the photo is terrible.
go to post Scott Beeson · Jan 13, 2016 Related: There is no feedback when you rate a post. I had to refresh the page before I was sure it even worked.
