Helium implements a default change tracking strategy for persistent objects. This change tracking strategy generates change logs that is used by the Helium / Journey middleware to synchronise objects between Helium and Journey applications. The change logs can also be used as a basic audit trail.

The @NotTracked object annotation designates an object should not be considered for Helium's default change tracking. In general, persistent objects that should not be considered for change tracki...

Unfortunately this is the only way to do so. Helium DSL is based on a Model-View-Presenter (MVP) pattern that couples presenters and views more closely than say the MVC pattern does. This means that referencing variables or functions from one unit should specifically be designated as the variables or functions in that specific unit. Read a bit more about these two patterns here:
https://stackoverflow.com/questions/2056/what-are-mvp-and-mvc-and-what-is-the-difference
[https://www...