Differences between the InTouchViewApp object and other AutomationObjects
- Last UpdatedJul 02, 2024
- 1 minute read
The InTouchViewApp object is unlike other AutomationObjects. You cannot perform some operations you can normally do with other AutomationObjects.
-
If you try to configure an InTouchViewApp instance, a message appears asking if you want to open its parent template instead. You cannot configure the instance directly, only the parent template.
-
If you try to open more than one InTouchViewApp template for configuration at a time on one node, IDE prevents you from doing so. Close WindowMaker, WindowViewer, and Application Manager and retry. Alternately, you can edit the InTouchViewApp object on a different node with InTouch WindowMaker.
-
If you close the IDE while editing an InTouch application with WindowMaker, WindowMaker prompts you to save any changes. It then closes and the InTouchViewApp template is checked in.
-
If you close the IDE while testing an InTouch application with WindowViewer, WindowViewer closes.
If you want to:
-
Change the association between the InTouchViewApp and the InTouch application, create a new derived InTouchViewApp template instead.
-
Use ArchestrA security (Galaxy security) in InTouch, deploy a WinPlatform instance to the node on which the deployed managed InTouch application is running.