I was trying to copy a (reuse) message node which I wanted to be treated as a separate message node. My requirement is to a make minor change to the message to the user at 2 different places. However I see that the second message node when updated also effects the earlier message node. How can we achieve something like this. I m sure the concept of reusability exists and may be I m missing something.
Reusing a node will create a copy that is linked / mirrored to the other copies. Any change in one node, even minor, will change all copies of the node. This can be handy when you need to update multiple nodes at one time. However, I’ve found node reuse is most impactful in situations where the content changes can be expressed in a variable. A message node {{variable}} can be more than just an entity value. It can contain the unique message text needed to modify your message node. I have used the “content” variable type and the “environment” variable type when the text or values are static. One other option is to break your message into two (or more) nodes and separate the static message from the variable message. That way you can reuse the static piece wherever needed.