Address Keyboard Shortcut Conflict with Dutch Keyboard Layout in Manage

Summary:
Dutch users have reported that keyboard shortcuts do not perform expected actions in Manage. Instead of executing the intended commands, the shortcuts result in typing the characters associated with the shortcut combination. This issue is due to the way Windows handles the Ctrl + Alt combination, treating it as an AltGr key when using the Dutch (NLD) keyboard layout. Ref Case: TS017653477

Steps to Reproduce:

1. Install the Dutch keyboard layout (NLD) in Windows.

2. Change the keyboard layout to Dutch (Netherlands) in the Windows taskbar.

3. Log into Manage.

4. Navigate to the Work Order Tracking application.

5. Hit Enter to display a list of Work Orders.

6. Open one of the Work Orders, which places focus on the Description field.

7. While on the Work Order tab, press Ctrl + Alt + N.

   • Result: The highlighted text in the Description field is replaced by "ñ".

   • Expected Result: The application should navigate to the next record.

8. Press Ctrl + Alt + P.

   • Result: The letter "ö" is typed instead of navigating to the previous record.

   • Expected Result: The application should navigate to the previous record.

Additional Observations:

• The issue does not occur when using the English (ENG) or Swedish (SWE) keyboard layouts.

• The problem is reproducible in other applications such as Google Docs, where the same shortcut behaves differently depending on the keyboard layout.

• The SRE team has identified that Windows hijacks the Ctrl + Alt combination to function as AltGr, which is used for typing special accented characters.

• This issue does not occur on macOS, as macOS does not treat Ctrl + Alt as AltGr.

Proposed Enhancement:
We request an enhancement to allow Manage to recognize and process keyboard shortcuts correctly, regardless of the keyboard layout. Potential solutions include:

1. Implementing an alternative shortcut mechanism that does not conflict with AltGr behavior.

2. Providing an option in Manage to configure keyboard shortcuts to avoid conflicts with Windows keyboard layouts.

3. Detecting the keyboard layout and dynamically adjusting shortcuts to prevent unintended character input.

Business Impact:
This issue affects Dutch users' productivity, as they are unable to use navigation shortcuts effectively. Instead, they must manually click through records, which slows down their workflow. Resolving this conflict would improve usability and consistency across different keyboard layouts.

References:
A discussion on StackExchange highlights the underlying issue and possible workarounds:
https://superuser.com/questions/592970/can-i-make-ctrlalt-not-act-like-altgr-on-windows