$cfg{xxx} doesn't work on source/destination connectors #6088
ppazos
started this conversation in
Feature/Enhancement Ideas
Replies: 1 comment
-
Context: On this post https://forums.mirthproject.io/forum/mirth-connect/support/13981-map-variables-c-vs-co-vs-just I have seen how $ is implemented. If this implementation is correct, then the behavior I'm seeing doesn't make sense (I have tested all the steps done by $() using $r{xxx}, $co{xxx}, and so on, and all return an empty value). My guess is there might be a problem translating the expression
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I have a variable 'folder_folder' in the Configuration Map.
In a File Reader connector I can access it via ${source_folder}, but the more specific $cfg{source_folder} doesn't work. When I click Test Read, that value is just empty.
With $cfg{}
With ${}
Then in the Channel Script Deploy I added
logger.info($cfg('dest_folder'));
which actually displays the correct path in the log when I deploy the channel.So there is an issue with the
$cfg{xxx}
access from the Source/Destination Connector configuration, which doesn't happen when accessing from JS with$cfg('xxx')
.Any ideas?
I'm on MC 4.4.0
Beta Was this translation helpful? Give feedback.
All reactions