You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a NK service node is triggered, it should be possible to pass additional metadata through the service node and receive that metadata on the output.
For example, if I pass the following data to a switch, I would expect the following output:
I already have message passthrough enabled, but it seems that a service node builds a completely new message and disregards almost all values passed to it's input.
Any more details?
If this is specific to some hardware or specific software version, please explain here.
Additional comments?
Additional comments here, if any.
Any code or functions to add?
No response
The text was updated successfully, but these errors were encountered:
+1 for this request. Thanks for a great addition to NR. Its pretty much a NR convention that msg objects are passed-through with the node only making the specified changes based on its function.
+1 for this request. Thanks for a great addition to NR. Its pretty much a NR convention that msg objects are passed-through with the node only making the specified changes based on its function.
Your Current NRCHKB Plugin Version
1.5.0
Operating System
No response
What is your idea?
When a NK service node is triggered, it should be possible to pass additional metadata through the service node and receive that metadata on the output.
For example, if I pass the following data to a
switch
, I would expect the following output:Service node input
Service node output
I already have message passthrough enabled, but it seems that a
service
node builds a completely new message and disregards almost all values passed to it's input.Any more details?
If this is specific to some hardware or specific software version, please explain here.
Additional comments?
Additional comments here, if any.
Any code or functions to add?
No response
The text was updated successfully, but these errors were encountered: