Use the following workaround to install CSDK v20, when CSDK v22 is already installed:

1. Before installing CSDK v20, open the file AUTORUN.ini (in the build root) with a text editor for editing.

2. Navigate to the section "[@PREREQUISITE5@]", which is responsible for installing "Visual C++ Redistributable 2015 (x86)".

3. Within the section, navigate to the line starting with "RequireOn=" and delete all the characters in the line AFTER the equal sign.

4. Close the file and launch SETUP.exe again.

OPLA is not updated when installing CSDK 22 side-by-side with CSDK version 21.

Though you can continue to use your old OPLA server with CSDK v22, we recommend upgrading it. The new OPLA version distributed with CSDK v22 has security and stability improvements justifying the upgrade. Use the command line and proceed with the following steps to upgrade OPLA:

1. Stop the OPLA service with the following command:

   OPLA service -stop

2. You can find the new OPLA in the OPLA subfolder of the CSDK v22 installation package. Copy all files from this subfolder except appsettings.json, overwriting the old files on the computer hosting OPLA.

   Ensure that the system date and time is set up on the computer.

3. Your upgraded OPLA can use the existing configuration file. If you need to update your configuration, refer to the "Prepare OPLA for the first use" section in the Getting Started Guide.

4. Start the OPLA service with the following command:

   OPLA service -start

When Workflow XML Designer runs for the first time, it creates files in the user's AppData folder. It is possible that a security software classifies this as a suspicious activity and blocks the file operations, displaying an error message that the access is blocked.

Workaround: Run the Workflow XML Designer application again in elevated mode, using the Run as administrator command in the context menu. After the first successful run, you do not need to use elevated mode again.

Workflow XML Designer v22 cannot load the .ocrjob files prepared in Workflow XML Designer v20 or v21.

Workaround 1: Customers should export their workflow to XML format in the Workflow XML Designer v20 or v21. This XML can be loaded to Workflow XML Designer v22.

Workaround 2: Before opening your .ocrjob file in Workflow XML Designer v22, use a plain text editor and perform the following updates:

1. Replace all "Formatter.PF" strings with "Formatter.pf".

2. Replace all "FormatterSetting.PF" strings with "FormatterSetting.pf".

3. Look for the following block and delete it:

   <f:PFSetting.fm>
     <fp:fmSetting />
   </f:PFSetting.fm>

4. Replace all "PFSetting" strings with "pfSetting".

5. For v20 files, also replace "Nuance.OmniPage.CSDK" strings with "Kofax.OmniPageCSDK".