Posted: 21 Nov 2019 12:19 EST Last activity: 26 Nov 2019 12:45 EST
User Fingerprint scanner
We need to use a fingerprint scanner to get the fingerprint and sent the image to our Pega application. The scanner is connected to an Android tablet and there is already a code that has been written in Android to interact with the SDK of the scanner.
What's the best approach? Do we need SDK Android and therefore a Pega Mobile License? or is there any way to consume from our Application the fingerprint image from the Android module?
***Edited by Moderator Marissa to update platform capability tags****
I don't know if this would be considered the "best" approach but it might be the path of least resistance.
Assuming the image already exists on the Android device doing the scanning, why not build a specialized portal for the users of that device that provides just the functionality need to attach images to specific cases? You could then create a data page of the cases that are in the proper status for scanning and allow only the Add Attachment functionality for each case.
This all assumes that the Android device has network connectivity. This way, you could use a browser. I would hesitate to do this as an offline activity as it would really complicate the case design unnecessarily.
I have definitely not considered all your requirements because I am not privy to them, but this seems like a reasonable option based on what you have presented. One thing that is not clear to me based on your post is whether the users of the fingerprint scanner are the standard users of the application or if the scanner operators are a handful of users that do only that task. For example, for a few jobs I have worked, I had to submit fingerprints and I went to a specific office with a specific set of users who only collected fingerprints. That would be the context of my suggestion.
The user of the fingerprint scanner are the standard users of the application and the Android device has network connectivity. Although It definitely does sound like a good option. If I'm understing this approach correctly it will still require Mobile Android License, right?