Agentry Barcode scan and focus change on Windows Mobile

[former_member300040]

Hello,

we have a field for a barcode scan on our screen and want to configure it in a way that when the barcode scan is done, the focus changes to the next field (or screen) automatically. We have already done the following:

- Define the field as scan enabled

- Select the Rules/Hyperlink/Special Value tab, in the Rules section, check the 'Change focus' box to Automatically change focus to next field

This works fine in the Agentry Test Environment, but does not work on our client device, which is a Windows Mobile 5.0.

Can anyone please help me on this?

Best regards

Christian

Tags edited by: Michael Appleby

[mark_pe]

Christian,

What is the version of your Agentry client? We change the focus logic a few times in different version for scanning. I need to find out which Agentry client version you used so I may give some information about it.

Regards,

Mark Pe

SAP Senior Support Engineer

[former_member300040]

Hi Mark,

it´s v6.0.38.0

Kind regards

Christian

[mark_pe]

Based on what I know from (Agentry request # AG-14008 and AG-11570), the design for scan focus in Agentry is as follows:

How the scan focus works in Agentry (Agentry 6.0.22 time frame):

• The scan focus moves in a sequential order; it moves from one field to the next from top to bottom.
• The scan focus only populates fields that are scannable, skipping hidden or disabled scan fields.
• When the focus reaches the bottom, it cycles back to the top most scannable field.
• If the user edits the barcode manually, the scan focus will automatically advance to the next scannable field.
• There is an optional (enabled from Editor) scan button to the right of each scan field. It allows the user to select a particular field for scanning, and overwrites the existing barcode. Hence, resetting the scan focus.

Tested in: Casio IT 800. Released in Agentry 6.0.22 and higher.

With the design spec listed above, hopefully this gives some insights on how it is supposed to work.

Regards,

Mark Pe

SAP Senior Support Engineer

[former_member300040]

Hello Mark,

thanks for your reply!

Unfortunately, the client device still does not behave as needed, while in the Agentry Test Environment it works fine!

We have a screen (for a Fetch) which contains only one field, which is a scan field.

We want the application to start the fetch automatically after the barcode scan is done. Therefore, we have configured the field as "automatically change focus to the next field". In the Agentry Test Environment this works fine; when filling this field using the Scanner Simulation, the fetch starts automatically. On the Windows Mobile device, the user still has to click "OK" to move on, which is quite awkward with hundreds of scans per day.

Do you have any idea why the client does not behave in the same way as the ATE?

Kind regards

Christian

[mark_pe]

Christian,

The ATE (Agentry Test Environment) is the simulator while the PocketPC WinCE is a different client. The goal of the ATE is to simulate as much as possible the different devices. It has logic in it to try to simulate a few sets of different devices.

The final testing in pre-production is the actual device.

It could be for your actual device (What brand and model is it?) may need to be tweak by engineering to support such use case (There are a lot of devices out there). Either the model is not supported (Did you check the supported device list?) or the model was tested a long time ago and has not been re-certified. Note: 6.0.38 version is a much newer client. Some of the older devices may not have been retested against a newer Agentry version. Normally a company will read the supported device list and check what version of Agentry was it certified for. If the document states it was tested 6.0.10 then it should work 6.0.10 and higher BUT there are changes normally in software.  There were scanning changes too. So if you check the supported device list and your version is much higher than what is listed in that document then most likely the feature may or may not be supported (or some recent changes to the code affected that device). Some training on talking about patches (Enterprise Scale Mobility with SMP - Agentry Support: Debugging (1/3) - YouTube)

As far as I know the single match action when fired or triggered will do the defined action. If you say that this defined action "Fetch" works in the ATE but does not in the PDA (Windows Mobile 5) then it might be an issue with the actual device (Client specific).

If you want to file a bug for this:

The steps that you could do is to prepare to sending this to our support organization (component MOB-SYC). http://services.sap.com/support. What will be needed are as follows:

1) Export of the Agentry Editor that describes this scanning - no match action or single match.
2) A document that explains where in the editor the customization is located and reproduction step on what to press and enter once we get into your device. Include the actual barcode scan sheet.
3) We would need the actual device brand so we can try to use a similar device/same device to test internally.

4) If we do not have the device then we may ask you to loan us a device for testing (Need to follow sending procedures).

5) A client dump of your application (You need to zip up the contents of the installation directory of Agentry in your PDA device - all the files including the executable of Agentry, sst, dll and others). The goal here is we would copy this client dump into a device.  We would need your login/password to enter the device. We would follow your steps presented on item 2 above. We would also analyze your item 1 above. If we determine it is an issue then we would file a bug and escalate it (produce an AGS number) to be fixed in the next patch (based on schedule and priority). Delivery date may be TBD.

6) All other information like device model/brand, Agentry client version used, Agentry Server/Editor version and others.

7) Describe your business case and use case.

The end goal of that request is to get an Agentry AGS number. That number is what you need to get this in front of the management team (development team) to talk about when it could be schedule. Try to get that number when you open an SAP message. To get that number, item 1~7 are needed (This will avoid the ping pong effect of SAP Support asking a question and you specifying it).

Regards,

Mark Pe

SAP Senior Support Engineer

[mark_pe]

Christian,

I forgot to add. You also would need the ATE dump (login/password) so that the developers can compare and contrast the differences when you present your case in SAP.

Regards,

Mark