Local working directory integrity check for Managed and NAD InTouch applications

This feature allows to compare deployed application and the application in the local working directory. When launching WindowViewer for a managed and NAD application, a file time stamp and file content hash comparison is performed between the deployed application and the application in the local working directory. The comparison is limited to specific file types including .dlls, .exe, .vedef. If the files do not match WindowViewer will copy the deployed application to the local working directory and run the application.

To enable the integrity check

1. In the Application Manager, go to Tools > Node properties > Security.

2. Select the Enable local working directory integrity check for Managed and NAD InTouch Applications check box.

   Note: This option is independent of the Limit access to Standalone InTouch applications to users in InTouchDevelopers and InTouchOperators groups option. You may enable them both, or independently, on the same node.

3. Select OK.

   

   Note: The copying process may cause delay in staring the WindowViewer. If Network Application Development (NAD) is enabled on a node, the security mode options will be disabled.

Behavior in Managed InTouch application

After comparison if the files do not match, then it indicates that either:

• There is a new version of the application that has been deployed.

• The contents of application files in the local working directory have been modified.

In both scenarios, WindowViewer will copy the deployed application to the local working directory and run the application. This will cause a delay in startup time.

The application’s InTouch.ini file has two additional settings:

4. Name: NewDefaultLocalWorkingDirectory

   • For new applications in 2023R2 or later the value is 1.

   • For migrated applications in 2023R2 or later the value is 0.

5. Name: VIEWEDMANAGEDDIALOG

   When you navigate to File > Configure > WindowViewer > Managed application, the value is set to 1. This is because the notification that the local working directory has been updated is only shown once.

Notification:

For new managed applications, the notification states that the default local working directory has been updated to %LOCALAPPDATA%\ArchestrA\ManagedApp.

For migrated managed applications, the notification states the recommended local working directory is %LOCALAPPDATA%\ArchestrA\ManagedApp.

To restore the default working directory:

In WindowViewer of a managed application, go to Files > Configure > WindowViewer > Managed application and select the Restore Default present at the bottom of the page.

The Local working directory field will be updated to:

%LOCALAPPDATA%\ArchestrA\ManagedApp

Behavior in NAD InTouch application

After comparison if the files do not match, then it indicates that either:

• The NAD Repository has been updated.

• The contents of application files in the local working directory have been modified.

In both scenarios, WindowViewer will copy the NAD Repository application to local working directory and run the application.

If NAD was previously enabled on a node prior to SP 2023 R2, and then upgraded to SP 2023 R2 or later, then the local working directory path is not modified. A notification is displayed recommending the new file path.

The default Local working directory path for NAD on new installations of System Platform 2023 R2 or later is:

C:\Users\*USER*\AppData\Local\NAD