Designer Reference
Overview
All Fieldpine POS Systems include the Designer toolkit allowing tailoring to extend the POS to specific requirements. With version 2.5.4 of the ePos system, the designer is included in the posgreen.exe file, prior to this version it was shipped as a seperate executable. A basic design principle of the POSGreen and other counter versions of the POS is "keep running" and to avoid producing error messages to users that are non critical. This also means that much of the syntax verification and setup validation is removed, which makes the counter level operations faster, less memory hungry and able to utilise smaller specification machines. The opposite of this is when POSDesigner is enabled. Designer mode has extended checking controls, syntax validation and assorted internal checks. The POS designer mode is able to operate exactly like the counter POS, but because it may generate extra obscure warnings, it is not suitable for general counter operation. Runtime ErrorsWhen the POS detects some types of errors, such as missing files or invalid keywords, it will log a runtime error. These errors are not displayed to the user of a counter version, but are recorded in memory. For counter POS operation, the POS is able to continue normally without user intervention. You can review runtime errors by displaying the configuration report for a lane. Runtime Errors are also recorded in the crash.out file should the system crash. In a network environment, the first occurrance of an error is broadcast on the network. Test LevelsThe POS also includes a Test Level control, which allows more and more functionality to exposed for testing and development purposes, but without compromising the rigourous production testing required. Fieldpine do NOT support any functionality at levels greater than 0, however you are welcome to provide feedback and bugs, this is why the test level system was introduced, to allow retailers early access to pending functionality. There are 6 test levels currently defined:
The test level control is available from the debug screen, where a level may be entered. It is not necessary to restart the POS after changing the test level, although some screens may need refreshing. |