i understand what you want but is not the way eramba works, “add” means you “add” no matter where that item is applied. the idea that visualisations (which is. what prevents the user from seeing other packages) should be applied to “fields” within a form is not something we have now.
its pretty complicated piece of code to build and we are not nearly there to be honest. next year we want to start working on field level actions (user defined workflow, triggers, etc) so maybe this is something to consider when we get there.