I haven’t found the specific answer to this question so far.
The usage case: I’m deep in within my TB document hierarchy when suddenly I get an idea or action that I would like to record (not neccessarily linked to the actual level). I typically record this idea in the text field of separate note adding a textual tag such as “IdeaX” to mark it as an idea.
What I would like to do is have an agent running which
-
Automatically recognises the note as an “Idea” note
-
Move the note from the current location to a designated container which is just to hold ideas.
I can do 1) easily. My problem is that for my solution of 2) the Agent keeps adding aliases to the designated container rather than the original note, one new alias for each scan. To illustrate what I’ve done I show you the contrived example below. First the overview of the Agent, Note and Container.
Then the Agent Query to identify the note (which works)
A finally the action as specified to move the Note to the Container.
I roughly understand what’s happening e.g. that the Agent keeps rediscovering the note and then moving the alias within the Agent to the Container. But how to accomplish my task ?
Many thanks for your help