Limitations in ID Scanner plugin 3.2.1 - ID Scanner 3.2.1

ID Scanner Plugin Guide 3.2.1

Applies to
ID Scanner 3.2.1
Last updated
2023-03-27
Content type
Guides > Plugin and extension guides
Language
English
Product
ID Scanner
Version
3.2

The ID Scanner plugin 3.2.1 integration includes the following known limitations.

Issue Description
2762891 Some ID card formats include two-digit year digits that are outside the range supported by the Gemalto driver and custom parser. These cards return the wrong century and are treated as expired. For example, a card that expires in 2077 is read as having expired in 1977.
1043780 For a keyboard wedge scanner, only the following keys are supported for CarriageReturn and LineFeed: Enter key, Down Arrow key, and Ctrl+Shift+J key combination.
1043268 For a keyboard wedge scanner, the keyboard layout must be set to U.S. English.
1018920 When you upgrade from ID Scanner 3.0, the 3M scanner is not created automatically in the Security Desk plugin option.
Workaround: Create the 3M scanner manually.
791247 If you have moved and your new address is indicated on your driver's license using a sticker, your old address is read when the document is scanned.
Workaround: Enter the new address manually.
791082 If a user without custom field visibility makes changes to the ID Scanner options, they might inadvertently remove document mappings for the custom fields they cannot see.
790954 In the Cardholder management or Visitor management task, you can only extract document fields that are mapped to custom cardholder or visitor fields if you have the field visibility.
790944 If you only map a document field to a cardholder or visitor custom field, that document field appears in the ID Scanner dialog box for both cardholders and visitors, but it remains blank for the entity you did not map the document field to.