Welcome to v6.6 - please at least read the "Details" below each chapter in this "top" section of the Release Notes.
v6.6 Release rev. 18918, was released 29. January 2020.
See the full list of all logged changes on our website: https://www.farmerswife.com/releasenotes/
Native v6.6 changes:
- 1 Warning: The new v6.6 "64bit" fw Server installers on Windows and Mac support the auto-upgrade for the fw Client app in certain scenarios.
- 4 HOT Features
- 10 Features
- 3 Important Other change
- 23+ Bug fixes
... and also take a look into the new highlights summary "Whats New in v6.6": https://blog.farmerswife.com/farmerswife-release-v6.6
Check out our Getting Started videos for new Advanced Users joining your team! https://www.youtube.com/playlist?list=PLA74zQEGurSW7WY9LJqO0jWLjaQnMXxPI
Upgrading to fw v6.6 - see details!
- You need to be on "Gold Support" past the date of the planned release of this version.
- You need to have a "Version 6.6" license at hand, before starting the upgrade process.
- To be eligible for a v6.6 license you need to have a valid support subscription (Gold or Silver) with us, at least up to 29th January 2020 or later.
ONLY upgrade your farmerswife (fw) system from v6.5 Release rev. 18623 or later!
The fw-Client-AutoUpgrade functionality is ACTIVE in certain scenarios.
The built-in "Full Installer download" farmerswife (fw) Client auto-upgrade is active on:
- the NEW macOS "64bit" Server on macOS 10.14 Mojave and later
- the Windows 64bit Servers
The "64bit" fw Server installers can only serve "64bit" fw Client full installers or provide the simple in-application auto-upgrade for already upgraded "64bit" fw Clients!
Any fw Client app on Mac running BELOW macOS Mojave must be manually upgraded by using the "macOS-32bit" installer after each upgrade!
The "32bit" fw Server installers DO NOT support any auto-upgrade!
This built-in Full-Installer-download auto-upgrade functionality - requires local OS user permissions read. write AND execute. This will be triggered upon first log-in to the already upgraded fw Server application.
This means, upon login with the fw Client Desktop app, the user has to choose a location where the installer file will be stored on the local machine ... to then automatically continue with the upgrade process.
- Your farmerswife Server application must have been running on version 6.5 Release rev. 18623, or later.
- Inform your colleagues about this new version BEFORE you upgrade.
- Run a "Full Backup" BEFORE the upgrade.
- While the Full Backup is taking place, you could now take a look into the documents provided in the "Read And Use Me Upgrade Package" you were issued together with your license of the previous Released version.
- The upgrade itself might require a couple of "Forced Shutdowns" for it to finish.
- If needed, see more detailed information in the Upgrade Instructions.
- Ensure you have the latest Java version (JRE on Windows/Linux, JDK on Mac OS X) installed, for the Web Client and Mobile Web Client to work properly and in the most secure way. Watch out on Windows: here you can run the fw Server application in 32bit mode (farmerswife.exe) or 64bit mode (farmerswife 64bit.exe); and depending in which mode you're running the WIFE Server, you _must_ have JRE installed in the corresponding 32bit or 64bit version.
farmerswife Server upgrade on Mac:
BEFORE you upgrade, verify which macOS or OS X version your farmerswife Server host Mac is running on!
macOS 10.14 Mojave is the only macOS on which all fw Server installers will work!
The NEW macOS "64bit" farmerswife_Server will work ONLY on macOS 10.4 Mojave and macOS 10.5 Catalina and later!
We strongly recommend to ensure your Mac host computer is running on macOS 10.14 Mojave for the successful upgrade from previous versions!
- Copy the NEW farmerswife Server package to the machine hosting the WIFE Server.
- Un-zip and rename it to include "NEW" in the package name.
- Place it in the same location as the previous running farmerswife Server.
- Quit the running WIFE Server.
- Rename the previous farmerswife Server, to include "OLD" in the package name.
- On both packages do <Control> + click and select "Show Package Contents" in the pop-up menu.
- In the OLD package select the "system" and "files" folders* and use <Control> + click and select "Copy 2 Items".*
- In the NEW package use <Control> + click and select "Paste 2 Items".
- Now copy the new Version 6.6 license files into the "system" of the NEW WIFE server.
- On the 1st start-up only, right-mouse click and use "Open" to launch the fw Server and allow it to run to start the actual upgrade process.
Note: The upgrade itself might require a couple of "Forced Shutdowns" for it to finish; this depends on your usage of the system.
From now on you can simply double click on the NEW farmerswife Server package icon to launch it.
- Once everything worked out fine, remove or update any Dock or Desktop links. And if needed remove the OLD Server package; because up until now, this was a working "roll-back" backup, just in case something went wrong.
- After the upgrade, start the farmerswife Server as usual.
* You might also need to copy the "html_templates" (only if used and if it contains customized templates) folder. And if you are using any 3rd party integration scripts, don't forget to manually migrate these from OLD WIFE Server package > Contents > "Show Package Contents" > lib > scripts > ... and then here only copy the integration script files from the according sub-folder and not the whole "scripts" folder.
Note: The "files" folder might not even be there, since it was broken out, to reside on some other storage device within your network.
farmerswife Server upgrade on Windows and Linux:
On Windows you should only be using the new "Windows-x64-64bit_farmerswife_Server...exe" installer, available since v6.5.
On any old 32bit Windows machines the fw Client application has to be manually upgraded by using the "Legacy-Windows-x86-32bit_farmerswife_Client.exe" after each system upgrade.
On Linux there is still only the "Legacy-Linux64" Server installer available.
- Make sure you are logged into the host machine with the same admin user as on the initial installation of the farmerswife server application.
- Copy the NEW farmerswife Server installer file to the machine hosting the WIFE Server.
=> On Windows this is a .exe file
=> On Linux use these instructions: https://support.farmerswife.com/a/solutions/articles/17000026005-server-and-client-installation-linux
- Quit the running farmerswife Server.
- Now copy the new v6.6 license files into the "system" of the NEW WIFE server.
- Double click to run the installer file in the same manner as the previous installation (for example did you use "Run As Administrator" on Windows?).
- Follow the instructions of the install wizard.
- After the upgrade, start the farmerswife Server as usual.
The farmerswife Client desktop applications can potentially use the fw Server auto-upgrade functionality...
... by using the "FULL" Client upgrade process; OS admin user permissions Read, Write AND Execute are necessary on the initial upgrade.
If your farmerswife Server is macOS 64bit (Mojave or Catalina) or Windows (64bit):
Windows "64bit" fw Clients will perform an auto upgrade when they first connect to the upgraded 6.6 fw server.
macOS (Catalina and Mojave) clients will perform a full install when they first connect to the upgraded 6.6 server.
If your farmerswife Server or fw Clients are or running a macOS version earlier than Mojave, or a Windows 32 bit, or Linux your clients will NOT upgrade automatically!
Use these direct download links for the farmerswife Client desktop application installers:
macOS 10.14 Mojave & macOS 10.15 Catalina "64bit" fw Client: http://www.farmerswife.com/downloadsWeb/fw_client_v606.dmg
Windows "64bit" fw Client: http://www.farmerswife.com/downloadsWeb/fw_client_v606.exe
Linux "32bit" fw Client: http://www.farmerswife.com/downloadsWeb/fw_client_v606-32bit.bin
IMPORTANT for the supported auto-upgrade functionality in later versions:
For the farmerswife Client applications on Windows the "simple in-application" auto-upgrade process to work (once supported in later versions), "normal user" Operating System permissions (Read / Write) are sufficient. You log-in, you confirm that you want to upgrade, the needed files are transferred, the WIFE Client restarts, done.
IMPORTANT when upgrading the WIFE Client on Mac: If you have a mix of Admin and Standard users on a Mac, make sure to be logged-in as a Standard user. Then after mounting the .dmg file, drag-and-drop it to the Applications folder. You then need to authenticate with the Admin users credentials! The farmerswife Client will not work for the Standard user, if installed while being logged-in as the Admin user. For the farmerswife Client applications the "simple in-application" auto-upgrade process is supported, "normal user" Operating System permissions (Read / Write) are sufficient. You log-in, you confirm that you want to upgrade, the needed files are transferred, the WIFE Client restarts, done. This upgrade process is not explained in any further detail.
Once you've successfully upgraded, please inform us by sending a short email to firstname.lastname@example.org; this is very important information for us which helps us to provide the best possible support for you.
Latest free universal iOS farmerswife app v5.0.828 is available on Apple's App Store, click on "+" to see the details!
The latest iOS farmerswife app is v5.0.828, and is available on Apple's App Store since 08-April-2019.
IMPORTANT: Requires iOS 12
And due to iOS 12 requirements for new submitted apps this will result in the previously working 3rd party external barcode scanner support to no longer work, as this was removed by Apple.
The previous farmerswife app v5.0.825 (available since 4-June-2018) works from iOS 9 through to iOS 12.
NOTE: iOS 9 required since iOS farmerswife app v5.0.706.
Requires farmerswife v6.1 SP1 and later versions!
You should upgrade as soon as possible to the latest released version 6.4, but at least to v6.1 SP1 rev 16195.
If you can't upgrade your fw Server application to v6.1 SP1 rev 16195 or later (was released 20. July 2016), then you can't use the latest available iOS farmerswife app on iOS 8.4 or later.
You will get a "Error Failed To Connect" message.
How to install the iOS farmerswife app:
On your Apple mobile device go to the "App Store" app and search for "farmerswife"; depending on which iOS version you have installed, it will show you different iOS farmerswife app versions.
Latest iOS farmerswife app version is 5.0.828; it requires iOS 12 and later (ideally you're always on the latest iOS version).
Version 5.0.59 requires iOS 7 or later. This is the iOS 7 optimized version.
For iOS 6, the latest iOS farmerswife app is still version 5.0.34.
IMPORTANT for older versions:
The latest v5 universal iOS farmerswife app for iOS 7 or later: v5.0.59 is available on Apples App Store since 12-September-2014.
Your WIFE Server needs to be at least on version 6.1 SP1 or later to use iOS farmerswife app version v5.0.59 and later.
Running a separate TEST WIFE Server
This chapter describes the recommended best practice on working on and with a separate TEST farmerswife (fw) Server system.
This might be needed when running on Beta versions, or new Service Packs or in general when you first want to run an upgrade check, or evaluate new modules or new functionality on a separate TEST fw Server environment.
You can always use a fw Server app in "Demo Mode" (also with your database (DB) files) and it will run for 60 min. and you have 40 sessions.
An additional "TEST fw Server" license can be provided upon request, available for customer with a valid service agreement in place;
include in your request the Company Name, the info of the local static IPv4 address and the used Operating System of the machine to host the TEST fw Server.
farmerswife supports Push and Feed functionality, and various other email notifications (if enabled); and it can be integrated to various other 3rd party systems; and you can also break out folder structures to network shares which are normally locally hosted on the fw Server's host machine, etc.
All this functionality is therefore also enabled by default on a separate new TEST fw Server environment you might be using. And if not handled with care and turned OFF in a good way, this will lead to duplicate or wrong notifications to your users, or update wrong information on your real live Production farmerswife system.
Please read on.
For a "half way realistic" test environment, copy the "system" folder from your fw PRODUCTION Server, more info below!
Depending on how you use farmerswife, you might also need to copy other files or folders.
Use the "server.cfg" file to control certain vital parts of your separate TEST Server:
This "server configuration" file (server.cfg) provides the option to change certain "General tab" settings "outside" of the actual fw Server application.
You use this file to ensure certain settings are NOT enabled on your TEST fw Server BEOFRE it gets started.
These settings/variables are available by default on this version:
These are additional settings/variables not set by default:
Since v6.4 these two settings/variables are special, because on a "standard" and "not externally proxied" fw Server installation, both of these MUST have the SAME port value!
On our "Demo DB" these settings/variables will look like this:
Note: Only licensed features and their variables will be effected by any changes within this .cfg file.
A proper fw Test installation works like this:
- Quit your farmerswife PRODUCTION Server.
- Create a file called "server.cfg" within your PRODUCTION fw Server's "system" folder.
- Start up your PRODUCTION fw Server for the first time with the "server.cfg" file in place, then Quit it again, to trigger flushing your existing configuration settings into this "server.cfg" file.
- Install the TEST fw Server application on your test machine.
- Now copy at least the "system" folder from your fw "production" Server to within your "test" fw Server's installation folder. If you have the time, feel free to also copy the "files" folder; and if you have customized anything within the "html_templates" or "/lib/scripts/...", copy these sub-folders, and IF you are using anything "customized" within these folders, the related files might need to be copied as well.
BEFORE (!!!) the first start-up of the TEST fw Server, edit the server.cfg file with a text editor application within your TEST fw Server's "system" folder and add or set at least these variables to "0", like this:
Save the server.cfg file. Copy it again to a "safe" location on your test machine, so you can re-use it for the next DB file updates. Please read on.
Now start your TEST fw Server application.
VERY IMPORTANT after the first launch and after each update of database files of a separate TEST Server
Go to the running fw Server application > Setup > General tab > "Full Backup Time" and set it to "Never"!
The "server.cfg" does not yet support this feature, and if you do not turn it off, this might interfere with your actual real "Full Backups" from your "in-production" farmerswife system!
NOTE: to test "Allow Mail" functionality from a "test" fw Server, you can use for example a service like "Mailtrap" (https://mailtrap.io).
You then need to update this variables with your access details:
Repeat the above steps, for any upgrade or repeated update of the "system" folder on your Test fw Server.
We recommend to save the correctly configured "server.cfg" file for the TEST environment in a good way, and then simply replace it prior to the first start-up.
NOTE: Once you have properly configured your TEST fw Server as described above, you can save time in the future by only copying these files from your PRODUCTION fw Server > from within the "system" folder:
... and "paste" into your TEST fw Server's "system" folder and "replace" the previous files. Then rename the fresh "log.txt" to include "date-of-copying-yyyy-mm-dd_InitialsWhoCopied_log.txt". This helps on keeping track.
About these Release Notes, Disclaimer and Legal Information
The content of this Release Notes document is subject to change without notice. The information in this document is furnished for informational use only and should not be construed as a commitment by farmerswife. farmerswife assumes no responsibility or liability for any errors or inaccuracies that may appear in this document or any software that may be provided in association with this document. Except as permitted by such license, no part of this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means without the express written consent of farmerswife.
fw Client Desktop app - Full-Installer-download ACTIVE on 64bit fw Server installers on Windows and macOS Mojave and later, see details.
The new v6.6 64bit fw Server installers on Windows and Mac support the auto-upgrade for the fw Client app in certain scenarios:
- on Windows
- on macOS 10.14 Mojave and macOS 10.15 Catalina and later
... by either using the "Full-Installer-download" auto-upgrade process, local user Operating System Read, Write & Execute permissions are required.
... or for already installed "64bit" fw Client apps, the simple "in-application-auto-upgrade" is supported.
For users on Mac BELOW macOS Mojave, on old Windows 32bit computers and on Linux:
The fw Client installers have to be manually downloaded and installed.
Fixed bookings batch printing on 6.6 in Projects > Advanced Search
Split bookings are now added to same binder as source.
Split multi-day bookings into two: highlight the day you want the booking to be split on > booking menu > split.
it is now possible to "split" a multi-day booking into two: highlight the day you want the booking to be split on > booking menu > split > confirm:
The result is two bookings - one from the start of the original booking to the day before the highlighted day, the other from the highlighted day to the end of the booking (booking name, status, custom fields, involved objects, etc - all remain identical for both bookings)
Fixed a bug that was causing Booking number to be re-used when duplicating Booking from within the Booking window
When dragging classes to days in Scheduling Mode, "NO OBJECT" entries now keep rates and Activities.
When you're Scheduling Mode with a Budget, and drag an Object Class to a day in the Long Form,
it's supposed to respect each line's rates and Activities. Now, if you use a high enough Multiplier
on the row, it might allocate more objects than you have. In that case, it would *not* keep
the rates or Activities for the resulting "NO OBJECT" lines in the Booking. Now that's fixed.
Fixed calculation bugs for Bookings with "View Class Booking As Separate Days" and Fixed Prices or Price Agreements, see details.
It's possible to make Class Bookings get listed as separate lines in the Edit Project Window, Reports and Invoices. This is done through the Booking's "View Class Booking As Separate" setting.
However, when that Booking had a Price Agreement there were rounding errors.
And when you used a "Fixed Price" Sell Price Operator on any Booking Object inside that Booking, it would calculate it all wrong, causing each day to add that Fixed Price to the Subtotal.
Both these bugs are now fixed.
You can now export the content of the Conflict window to a CSV file, and you can also Show Conflicts for a Binder
Custom Fields configured as Finder to import extra info, were not listing contacts or companies from contact database
Fixed multiple bugs on Entry type Custom Fields using the "Finder" functionality, see details.
Fixed a bug that when setting up Entry type Custom Fields and using “Finder” it would always show “None” when opening an existing event.
Also fixed issues when trying to select a value on a Entry type Custom Fields using “Finder” where it was wrongly not possible to select any value on macOS or Windows. This is now fixed.
Virtual Object Amount now merged into one line in Dispatch Report, Project Report and Invoice Report. See details.
When adding a Virtual Object to a Booking and creating a Dispatch from it, you can now, when printing either a Project Report or Dispatch Report, display the Virtual Object in _one_ line and show the Quantity as separate value.
In the Dispatch Report in "Options" you can turn on to "Merge Virtual Objects". It will be ignored, if using the setting "Group by Obj. Class" in which case it's also showing in one line (if the Virtual Object belongs to a Class).
In the Project Report the Virtual Objects are always merged into one line. Regardless of the additional setting to "Group by Obj. Class" that is available in the Setup of the Templates.
Added support to show in Long Form > Objects tree amount of available Virtual Objects next to its Object Class, see details
This is an enhancement to the recently implemented functionality to show amount of active Class Members between brackets next to the Class Name
Added Month Grouping To Financial Report. See details.
You can now group by Month in the Financial Report.
If the financial lines of a booking go over various month (multi-day booking), then all values will go into the first month of the booking.
To avoid this a new setting "Force Bookings Into Separate Days" was added to the Financial Report window, under General Settings.
Make sure to enable this setting to distribute and allocate the multiple-day bookings to the corresponding month totals.
And click on the Save Settings button to get this option saved to the print template.
With the new Hotkey for PM User report you can create your reports much faster (requires module Labour Rules), see details
To create a Hotkey go to Toolbox > Settings > Miscellaneous and scroll down to find the Hotkeys Editor. Select a Master Key and a Combination Key and next select click on Functionality to select a PM User report, and click on Add.
To create the report select a User in the Personnel Tree and mark a time period in the Long Form. Use your Hotkey command and the report will be displayed. Note that you can only select one User at a time.
If you Use Option (Alt) as your Master Key, you will need to click both on Control and Option (Alt) to make the Hotkey execute the command.
Added the possibility to show only "Staff Name" when displaying "Involved Staff" in the Hourline, see details.
Now it's possible to only show "Staff Name" in Hourline when using in fw Client > Toolbox > Settings > Hourline > "Display Selected Involved (Staff)".
Before when using this setting it showed both Staff Name / Object Class Name, this still works. With this new setting it's now to only show "Name".
Added new icons for v6.6 in sections "Objects" and "Other".
Fixed invoices batch printing
Fixed a crash bug when printing from the Media Library > Labels and when using the new "x64" installers, see details.
The previous crash bug contained the error info "hdc".
Note: "Multi-Label > "Print As PDF..." support for "x64" is currently still work-in-progress.
Fixed a bug when using Navision Exports > Project Financials Export > Preview that the "missing info" red-helper-boxes wrongly lost the details info.
Changed lang files to use msgcat
Added support for Classes Availability tree in Long Form to reflect true availability, taking into account that an Object can have more than one booking on the same day but on different times
Fixed a bug that was not saving the password correctly when importing users via Object Manager > Import, see details.
This is now working as usual: when importing users, the password equals the username.
Object Manager / Server Setup
Fixed a bug wrongly preventing "Thumbnails" and "Images" uploaded as ".jpeg" or ".jpg" from being displayed in the Object Manager.
Added feature to be able to "Remove Events On Selected Days" in Objects Tree, see details
This functionality was available for the Personnel Tree, now it is also possible to "Remove Events On Selected Days" in the Objects tree.
With this functionality you can remove events for specific objects that you select in the Object tree.
1. Mark one or multiple objects for which you want to remove events
2. Mark the days on which you wish to remove the events
3a. If it is only one Object you can click on the Object Icon to display the menu and select "Remove Events On Selected Days"
3b. If you select multiple objects do a right mouse click, select Objects and then select "Remove Events On Selected Days".
Added User Selector When Creating PM Remainder Report, see details
Clients with the module Labour Rules can create Personnel Management reports. When creating these reports most reports had a step where you could select what Users to include in the report. This was missing for the Remainder Report, and has been added now.
Note that when clicking on Cancel the report will be created with All Users. It does not as you could expect stop the report, cancel means that you do not wish to make a selection. A report with all users will also be created if you make no specific selection and click on OK directly.
Added “Preview” to access to totals report for travel expenses on selected TE’s in the navision export window, see details
+ added little bonus by double clicking on a TE the edit window of it now opens.
Fixed a bug on the PM User Report wrongly causing the grey-colored Weekends / Public Holidays rectangles would cover the text.
Optimized in fw Client Long Form > Personnel tree where creating a Personnel Booking on multiple days was taking too long.
Fixed a bug in Print Designer by which splitting Text element in Total section was wrongly positioned.
Fixed a bug on the Project Report wrongly causing the calculation of the "y" position of some Custom Field elements.
New setting in fw Client > Toolbox > Miscellaneous > “Ask For PDF File Path Where The Printout Will Be Saved”.
Added "Force Bookings Into Separate Days" to Financial Report and Project Report. See details.
When reporting on multi-day bookings it is sometimes necessary to use the "View Class Booking As Separate Days", in order to e.g. show the Day Notes per day or to split the booking values onto the diff grouping, e.g. Week, Month...
In the Project Report the setting is located as User Setting option under the Report icon.
In the Financial Report it is located in the General Settings area.
Fixed a bug by which the login window displayed an non handled error when using the fw Client > Server Setting > Get Server Info.
Fixed a client error when timereporting on Windows
Added option to display Toolbox > Calendar weeks Horizontally instead of Vertically.
Fixed a bug on fw Client > Toolbox > Deleted Bookings And Binders > where the "count" was wrongly not showing.
Internal Note added to Modify User window, see details
In the upper right corner click on the menu icon and select Internal Note. When the note has been added a note icon will show. On mouse over the content of the note is displayed. This note will not be visible on User Contacts in the Web Client, Mobile Web Client or in the iOS application.
New Permission for Advanced Users - "Can Create Projects"
With this new User Permission for Advanced Users you can now define who can and who cannot create new Projects. If the setting is enabled, i.e. the check box is ticked, the User will be able to create new Projects. If the setting is disabled, i.e. unticked, the user will not be able to create new Projects. The Users who are not allowed to create new Projects will still be able to modify and update information on the Project. You will find the permission in the General section of the "Permissions" window. The permission is on by default on your existing permission profiles.
Fixed a bug on Web Client by which retiming was not working on 6.6.
Include Binders into the Web Visibility