This article covers local interaction very well:
The main consequence of overriding it is the possible introduction of application conflicts, because your application goes from being run in it's own container to being linked with the local system.
I would run a small test of five users printing to the same printer at the same time to make sure there are no application conflicts with the tag enabled. But it should be fine for your use case.
I actually remember enabling this tag for the same reason in a Hyper-V deployment of FM12 a few years ago.
Thank you Mike for your answer, however we habe already set the local interaction tag, however we do not realize any performance changes.
What happened in the meantime: we realized, that we still had a Filemaker 10 installation on Citrix with APPV, so we run a test with the ex/imported data for Version 10, and realized that the speed was similar to a local FileMaker 13 installation!
Now also FileMaker 13 is installed on Citrix with APPV and we must realize, that Version 13 again is similar to a local installation (7 Min 73 APPV versus 4 Min 50 for 6239 A4 letters). On FileMaker 12 we had about 2 hrs 30.
Always with <LOCAL_INTERACTION_ALLOWED>TRUE</LOCAL_INTERACTION_ALLOWED>
Conclusion: Something wrong with the FileMaker Windows Version 12 in the sense, that it is very slow on Citrix APPV.