Mike Smith ArcticIT

Our client has terminals within a store spread out over a larger geographic area. These areas often have sporadic poor network connections. The user needs to be able to perform shift operations before leaving for the day and going to a different location in the store. Some examples of operations that may be needed are: 707 - Activate Device 1053 - Blind Close Shift 1054 - Suspend Shift

After selecting a category and viewing the products it should retain the last view you used. If you switched to list view should remember this setting and use same view for next selection.

When working with shifts through the manage shifts screen should be able to filter and sort by the various columns available on the screen.

Would like the ability to print an x-report to the screen instead of only to physical hardware. If no printer is hooked up to the register may still want to print the x-report and view on screen.

We have added an info code to the declare tender operation to be able to enter shift notes that need to be passed on relative to the shift being closed. Need the ability to enter more than 100 chars as part of the information.

On the POS management screens (Manage Shifts) would like ability to add info code or other information. For example a shift may have a bag number where the cash is held. Would like this to show up on the Manage Shifts screen.

We have a customer who has a common set of products and amounts that get sold but there may be many of these sold. In order to facilitate counting of funds for checks would like ability to itemize and calculate checks by amount.

Allow for a configuration option of minimum password age for how long a worker password must be used before it can be changed by the worker again. This follows best practice as specified for Windows: https://docs.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/minimum-password-age From that page... "Setting the number of days to 0 allows immediate password changes, which is not recommended. Combining immediate password changes with password history allows someone to change a password repeatedly until the password history requirement is met and re-establish the original password again. For example, suppose a password is "Ra1ny day!" and the history requirement is 24. If the minimum password age is 0, the password can be changed 24 times in a row until finally changed back to "Ra1ny day!". The minimum password age of 1 day prevents that."

Many organizations do not work with coins and would like the ability to sort the tender declaration screen denominations from largest to smallest. This would allow them to have the larger denominations at the top of the screen.