Export menu should be disabled or enabled by script

The current Communication Studio (CS) behavior requires enabling or disabling the Export menu via script when starting the CS from another application.

This issue was encountered at the Customer site.
 

Issues at Customer:
Problem 1: When a customer wants to download the PDI.xml and config.nxd to their Hilscher device using their own application, they need the ability to disable the Export menu.

Desired Behavior:
For Customer, the Communication Studio should:
Allow the Export menu to be enabled or disabled via script when launching CS from another application. This ensures flexibility for Customer's specific use cases.