By: Brenton Blawat

While this could very easily go into a tangent about software design, this article is going to be focused on Bugs which one may see in the Wavelink Product. — What is the purpose? To provide methods by which one can work around the issue until Wavelink corrects the issues in the product.

So if you find an issue, let me know so I can post it here. Be sure to report these bugs to Wavelink as the issues cannot be corrected unless they are reported to Wavelink..

Wavelink Avalanche Frozen Screen / Loading Freeze / Blank Screen

While running in a RDP (Remote Desktop) connection, it appears that the software is frozen. The Title Bar of Wavelink Avalanche Mobility Center is at the top of the screen, but the core application does not load into view. This has to do with some weird JAVA rendering that happens upon loading of the software.

Work Around: Minimize the Wavelink Avalanche Mobility Center then click on the application in the Task Bar. The screen will come back.

Bug Status: Reported to Wavelink

Wavelink Avalanche Blank Selection Criteria Issue

Selection Criteria Blank = Bad Thing

Not a lot of people understand the “inherent” blank selection criteria. By setting the selection criteria to nothing, it in fact, deploys to everything. This becomes more complicated when you start thinking form the perspective of using != (does not equal) in selection criteria.

E.G. If I were to say only IP != 10.10.10.10 & IP != 10.10.10.11, the software would deploy to every device. Why? Well and IP address can’t be two values at the same time, therefore, the software will deploy will deploy to every device.

Work Around: There currently is no work around for this issue.

Bug Status: Reported to Wavelink

Wavelink Avalanche Selection Criteria Logical Arguments

Model = “Sym50” & IP = 10.10.10.10 – 10.10.10.15 OR IP = 10.10.200.10 – 10.10.11.230

This issue has to do with Wavelink’s in ability to parse the statements as we would expect them to… The above statement would be evaluated as:

Model = “Sym50” & IP = 10.10.10.10 – 10.10.10.15

OR

IP = 10.10.200.10 – 10.10.11.230

Why? Well Wavelink uses a character sorting algorithm, with reads letter by letter and only evaluates AND and OR via parenthetical statements. This means for the example above, the server will first evaluate if Model = “Sym50” & IP = 10.10.10.10 – 10.10.10.15 are true. It then will check to see if IP = 10.10.200.10 – 10.10.11.230 is true.

In reality, you want the package to be deployed ALL of the Model = “Sym50”, and those IP addresses which are between IP = 10.10.10.10 – 10.10.10.15 OR IP = 10.10.200.10 – 10.10.11.230.

If and & and an | (OR) are used in the same statement, Wavelink should force the use of parentheses.

Work Around: Use Parentheses in your selection criteria. So for the example:

Model = “Sym50” & (IP = 10.10.10.10 – 10.10.10.15 OR IP = 10.10.200.10 – 10.10.11.230)

The Wavelink Server will evaluate are the IP addresses between (IP = 10.10.10.10 – 10.10.10.15 OR IP = 10.10.200.10 – 10.10.11.230)? Are the model numbers of those units equal to “Sym50”?

Bug Status: Reported to Wavelink

NEW! Wavelink Avalanche Duplicate Devices

It appears a bug they once upon a day ago fix has re-entered the system. It appears that the software is reporting duplicate handheld entries for devices with the same MAC addresses, Terminal IDs and IP addresses for the handhelds.

Work Around: Manually delete the duplicate devices from the server. Obtain a script from Wavelink to delete these duplicate devices

Bug Status: Reported to Wavelink

NEW! Wavelink Avalanche Group Selection Criteria Issue

Group = "MobileDeviceGroupName”

This issue has to do with the ability to send software out to Mobile Device Groups. The key behind this was to group sets of handhelds into Mobile Device Groups.

E.G. One of my clients created a mobile device group for each individual location they have for controlled deployments (1050 locations). In doing this they wanted to send specific software to groups of stores via Group = "MobileDeviceGroupName”.

The result of the selection criteria is the same as leaving the selection criteria blank; it will deploy the software to EVERY handheld in the system. Architectural flaw, it needs to be corrected.

Work Around: There currently is no work around for this issue.

Bug Status: Reported to Wavelink

UPDATE! Wavelink Avalanche Enabler v3.50-56 Launch Times

There seems to be an inherent bug in the Wavelink Enabler v3.50-56 where it takes 5 seconds for any application to launch from their “Desktop Interface”. It seems to be linked, or ironically similar, to their default auto-launch time of 5 seconds. Any and all applications (including extensions of .exe and .ica) take 5 seconds to launch.

Work Around: There currently is no work around for this issue other than waiting 5 seconds for each application.

Bug Status: A test Enabler has been sent to me for testing. I will provide it here if it appears to fix the issue!

For More Free Training by BIT Tangents: Go to Wavelink Training (Click Here)

Info on Author: Brenton Blawat is a Wavelink Consultant who has worked closely with the Avalanche product for over 5 years. He has integrated Wavelink AMC (and variants) into a multitude of corporations including but not limited to: Seneca Foods Corporation, American Eagle Outfitters, and Alexian Brothers Health System.

** BIT Tangents nor any of its contributors are liable for damages as a result of following these instructions. These instructions are intended as guidelines for best practices and are to be used at the executioners own risk! All re-productions / digital copies of this content must be approved in writing by an authorized representative of BIT Tangents. **