Fuel Module and Key Maps

During the revamp of the Amicus POS fuel module, a list of functionality that needed to be retained was made. One of these items was being able to assign a key map to a pump. At first this seemed easy, but then we realised that the way it is currently implemented would not suffice.

When the fuel module was initially created it was designed to be very modular. So much so that it did not have to be a plug-in for Amicus; as long as the plug-in loading program supported the framework we created it would just work. As a result, we devised a different way to map keys than how Amicus did it. At the time this was proving to be a better way, but since we have enhanced Amicus we noticed that we could no longer let these module-based key maps be apart from the regular Amicus key maps.

First, it is confusing for a user to have key maps in two locations. Also, the product pad key map logic looks only at the Amicus key maps.

However, the main reason for redesigning this is because we need to be able to specify which pump the ‘press pump’ key map is going to affect. In the old system, the screen only had 8 slots, and therefore had 8 key maps. Now, we can have an infinite number of pumps (in theory), so we need to be able to set all of them up.