Scanning performance

We’re trying to improve the scanning performance of our operators and the idea of preventing users from scanning into a new operation unless the previous one was completed came up. I’m sure this idea was discussed on here before and implementing that into a BPM that shows an error message shouldn’t be that difficult.

The issue with the above is that some of our operators would just ignore that error altogether and end up not scanning altogether.

I’m thinking that instead of an error message (exception), the BPM would trigger a dismissible warning. However, I’m looking for a way to count how many times a user dismisses that BPM warning message so that we can see which operators aren’t following procedure.

I was thinking that it can either increment a custom numeric field, or it can set a boolean custom field to true on the related labor record, which then can be aggregated in a BAQ.

If anyone can point to any starting material that would be great.

Hey Martin,

I’ve done something similar to what you described using a BPM Data Form. The user is prompted with a message related to the error, then has the option to continue or not. If the user clicks “do not continue”, an exception is then thrown. If they hit continue, they proceed with the transaction and the transaction details get logged to a UD table in the BPM. Then the UD table data can be brought into a BAQ. A UD field on the laborDtl table could work too.