First read this topic: Before you upgrade
The existing access settings which are in User settings, can unfortunately not be upgraded which means Role access needs to be assigned after upgrading. This can also be done in the Actions module (where multiple Roles can be assigned to one Action) or it can be done in the Settings > Roles module (where multiple Actions can be assigned to a Role).
If the setting is not found, the default warnings will be displayed, these include:
The stored procedure TRANS_WARNING can be copied and easily converted into a Custom Message Stored Procedure.
If you’re running QuickEasy in a Client/Server environment, please test that fbclient.dll is running on client pc’s before committing the install. If FBClient.dll is not found in the C:\Windows\SysWOW64\ folder, look for the GDS32.dll file, copy it and rename it to FBClient.dll.
where VATITEMS.FROMTYPEID [not] in (3,4)
This needs to change to:
where VATITEMS.TYPEID [not] in (-2,-3)
The new key for the VATITEMS.TYPEID is
These enhancements are the first steps towards achieving a central, consolidated Settings module which will eventually only contain Global and Role settings - for ease of administration, User settings will eventually all be converted to Role settings. We’re also moving away from the model where all the settings are added by default to a model where you only need to add settings that will differ from the default setting. Warnings are displayed when Settings are duplicated or otherwise invalid.
If only one setting is selected, the setting value can be populated when the setting is added. See image below:
The Timekeeping Touch interface has been enhanced as follows.
If the Task has already been started, a Note and a Stop button will appear instead.
A double-touch (Click) on a Task will execute the Start/Stop button.
This is a new, very light customisable module type which allows for a number of input fields and an Action that can read the input fields. Ideal for scanners.
Amongst other things, Actions can also be used to populate the Planning Board to a Calendar.
Remember to update Reports that use Calculated fields BEFORE running this upgrade.
Ie. You first need to create a Report, customise the Chart, Save Grid and then you can link it to a Dashboard.
The Role Settings include:
The number of Rows x Columns need to match or exceed the number of reports listed in the DashBoard - Reports setting. If, for example, the dashboard displays 5 Reports, you need 2 Rows with 3 Columns or 3 Rows with 2 Columns - the last Row will then only display 1 Report.
The old Dashboard will be deprecated in the next version upgrade, so be sure to migrate your Dashboard to our new shiny Dashboard before then.