Hey @xmechwizardx
As @Narelle pointed out, this feature was sent back to the backburner while we iron out some bigger loopholes.
That being said, the particular problem with this feature you mentioned has been fixed in the upcoming hotfix 2.2.1, currently scheduled to be released early this week.