Hey all esp. @wotnak so I’m testing it out, specifically testing how it works compared to is_movement
. An asset is only moved with is_movement
once the date of the is_movement
has passed… so if you set a future log, the movement will not occur until you hit that date.
Overall, while maybe a little confusing, it is accurate and reasonable.
I tested this behavior with the is_termination
and found that it doesn’t work the same - a termination log placed in the future will terminate (archive) the asset today.
I think we want behavior that exactly mimics the is_movement
, both because they are similar in the UI and because the concepts are the same.
What do you think?