Back To Release Notes List

Back To Release Notes List


6. Feb 2019

6.4 SP 2

  • 0 Warnings
  • 0 Features 1 Feature
  • 9 Other changes
  • 33 Bug fixes

Welcome to 6.4 Service Pack 2 - please read at least the "Details" below each chapter in this "top" section of the Release Notes.

v6.4 Service Pack 2 Release rev. 17824, was released 6. February 2019.

Contains all changes from 6.4 SP2 RC1 to RC4, so:
- 1 Feature
- 8 Other very important changes
- 33 Bug fixes

v6.4 Service Pack (SP) 2 Release Candidate (RC) 4 rev. 17736, was released 16. January 2019 to involved customers.

- 1 Feature
- 6 very important Bug fixes

v6.4 Service Pack (SP) 2 Release Candidate (RC) 3 rev. 17676, was released 20. December 2018 to involved customers.

- 2 Other very important changes, one for "Public Holidays"!
- 2 very important Bug fixes

v6.4 Service Pack (SP) 2 Release Candidate (RC) 2 rev. 17627, was released 29. November 2018 to involved customers.

- 1 Other important change
- 3 very important Bug fixes

v6.4 Service Pack (SP) 2 Release Candidate (RC) 1 rev. 17575, was released 30. October 2018 to involved customers.

- 5 Other important changes, two of them very important!
- 20 very important Bug fixes

v6.4 SP1 Release rev. 17395, was released 8. August 2018.

- 2 Other important changes
- 16 very important Bug fixes

v6.4 SP1 RC1 rev. 17373, was available since 25. July 2018.

- 2 Other important changes
- 10 very important Bug fixes

v6.4 Release rev.17313, was released 19. June 2018

See the full list of all logged changes on our website:

Native v6.4 changes:
- 1 Warning: "A MANUAL fw Client desktop app upgrade is necessary when upgrading to v6.4; to assist the "full-installer-download-auto-Client-upgrade-mode" IS active"
- 7 HOT Features
- 20 Features
- 4 Other changes
- 17 Bug fixes

... and also take a look into the new highlights summary "Whats New in v6.4":

Check out our Getting Started videos for new Advanced Users joining your team!

See here how to upgrade to v6.4 and later - a MANUAL fw Client desktop installation necessary ONCE; the "full-installer-download-auto-Client-upgrade" is supported, click on "+" to see the 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.4" license at hand, before starting the upgrade process.

IMPORTANT: The built-in farmerswife (fw) Client auto-upgrade process IS DIFFERENT!!!
Due to new fw Client-side "SOCKS5" protocol support, the normal "simple in-application auto-upgrade" is NOT supported on the initial upgrade from a lower version to v6.4.

In order to upgrade, the fw Client applications either ONCE need to be manually upgraded, by using at least the installers for 6.4 Beta 8 rev. 17068 or later.
Or each user can use the built-in FULL-installer-download auto-upgrade functionality (if allowed), which 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 manual upgrade process.

IMPORTANT: The simple "in-application" fwClient-auto-upgrade works again for any farmerswife Client desktop app which was once manually upgraded past 6.4 Beta 8 rev. 17068. Local Operating System (OS) user privileges READ and WRITE are necessary for this to work.

- Your farmerswife Server application needs to have been running at least on version 6.3 SP1 rev. 17162 before the upgrade (if lower, contact
- Inform your colleagues about this new version BEFORE you upgrade.
- Run a "Full Backup" process BEFORE the upgrade; i.e. use the "Full Backup Now" button located on the running fw Server application.
- The upgrade itself might require a couple of "Forced Shutdowns" for it to finish.
- If needed, see more detailed information in the Upgrade Instructions on our open Knowledge base:
- 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.

For your information: Known "download, un-pack and launch issues" on macOS Mojave and lower (started with El Capitan):
Due to: macOS > System Preferences > Security & Privacy > General > "Allow apps downloaded from: App Store and identified developers", you'll need to follow the below steps, because the farmerswife Server application in it's current state can't comply. The fw Client application on the other hand, complies and does not require the below steps.

IF you use "Safari" to download the "" package to your "Downloads" folder.
Copy or Move this still zipped file (if already unzipped, try to continue anyway) from your "Downloads" folder to your "Desktop" and ONLY un-pack it there!
Do a test-launch here: right-mouse click and use "Open"; follow the instructions on the macOS pop-up windows. If the fw Server application now launches, all is good, "Cancel" the full launch.
Now continue with re-naming it, according to your naming-convention-style and now move it to the correct location on your Mac. Then use "Show Package Contents" on the OLD fw Server application and copy the needed files and folders to the NEW package.
On the first launch use right-mouse click "Open". It can take a moment, and then you should get the "... is from an unidentified developer. Are you sure you want to open it?" pop-up window; use the "Open" button.

IF you use "Chrome" or any other web browser to download the "" package to your "Downloads" folder.
Copy or Move this still zipped file (if already unzipped, try to continue anyway) from your "Downloads" folder to your "Applications" folder or any other folder but NOT the "Desktop"!
To where ever you copy it, do a test-launch here: right-mouse click and use "Open"; follow the instructions on the macOS pop-up windows. If the fw Server application now launches, all is good, "Cancel" the full launch.
If it still does not launch you might have to download a different app, e.g. "The Unarchiver" has proven to work, and use this to un-zip.
Now continue with re-naming it, according to your naming-convention-style and now move it to the correct location on your Mac. Then use "Show Package Contents" on the OLD fw Server application and copy the needed files and folders to the NEW package.

For your information: Known possible issues after upgrading and how to fix them:

Web Client not properly working => local cache not refreshed!
After the upgrade, when trying to access the Web Client ensure that you see "v 6.4" below the log-in fields; if not use "F5" or "Shift"+refresh in your web browser to ensure the local cache is refreshed (you might have refresh multiple times).

Or, the installed Java version is wrong or old. Should be latest JRE / JDK on Mac, e.g. 8u151 or later.
Or, the host machines Operating System (OS) is too old and you can't upgrade to the latest JRE.
Or a recent Windows Update magically re-activated the Firewall. etc.

On Mac using the farmerswife Client with the message "Connection to the Server Timed Out"
This suddenly happens because you just upgraded involved computers to OS X "El Capitan", macOS "Sierra", macOS "High Sierra" or macOS "Mojave".

Fix: Do a MANUAL re-installation of your previously auto-upgraded farmerswife Client application.
The old reason for the issue is the OS X 10.11.5 update, "TCL" related change - "Description: A protocol security issue was addressed by disabling SSLv2." ( Source bottom of this page ). This started on Mac OS X "El Capitan" update to 10.11.5 on Monday 16th May 2016.

farmerswife Server upgrade on Mac:
- 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 6.1 license files into the "system" of the NEW WIFE server.
- Double click on the NEW farmerswife Server package icon to start the actual upgrade process.
- 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:
- 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 64bit, this is also an executable file; use in a command shell: chmod +x Linux64_...
- Quit the running farmerswife Server.
- Now copy the new 6.1 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 Clients will auto-upgrade ...
... if already on version 6.4 or later: ... by using the "simple in-application" auto-upgrade process ; "normal user" Operating System permissions (Read / Write) are sufficient.

... if BELOW version 6.4:
... by using the "FULL installer download" Client auto-upgrade process ; OS admin user permissions Read, Write AND Execute are necessary on the initial upgrade to version 6.4.

IMPORTANT when upgrading the farmerswife Client desktop app 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.

IMPORTANT for the supported auto-upgrade functionality in later versions:
For the farmerswife Client applications 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 fw Client desktop app restarts, done.

The Calendar has expired on OLD versions below v6.1! Contact for more information.
If you have not seen it before, simply first try it out on your own local machine and click on the "Free Trial" button.

Once you've successfully upgraded, please inform us by sending a short email to; this extremely helps us to improve our service for you.

Latest free universal iOS farmerswife app v5.0.827 is available on Apple's App Store, click on "+" to see the details!

The latest iOS farmerswife app is v5.0.827, and is available on Apple's App Store since 26-February-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 is 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!

This means:
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.827; it requires iOS 9 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 WIFE Server.
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 WIFE Server installation.

You can always use a WIFE Server in "demo mode" (also with your DB files) and it will run for 60 min. and you have 40 sessions.
An additional "TEST 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 WIFE 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 WIFE Server's host machine, etc.
All this functionality is therefore also enabled by default on a separate new TEST WIFE 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 WIFE 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 WIFE Server application.
You use this file to ensure certain settings are NOT enabled on your TEST WIFE Server BEOFRE it gets started.

These settings/variables are available by default on this version:

PASSWORD_POLICIES_SRC default_password_policies.json

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 WIFE Test installation works like this:

- Quit your farmerswife PRODUCTION WIFE Server.
- Create a file called "server.cfg" within your PRODUCTION WIFE Server's "system" folder.
- Start up your PRODUCTION WIFE 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 same farmerswife Server version as currently running on your "PRODUCTION" environment on your test machine.
- First data migration: Copy at least the "system" folder from your WIFE "PRODUCTION" Server to the same location within your "TEST" WIFE 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/..." folders of the WIFE "PRODUCTION", copy these sub-folders as well to according location on your "TEST" installation. 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 WIFE Server, edit the server.cfg file with a text editor application within your TEST WIFE 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 WIFE 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" WIFE Server, you can use for example a service like "Mailtrap" (
You then need to update this variables with your access details:

Fast update of your farmerswife "TEST" installation from "PRODUCTION:
This requires the above steps to have been properly accomplished.

Copy from your farmerswife "PRODUCTION" Server's "system" folder:
- "archives" folder
- "custom_icons" (if used = if this folder exists within the "system" folder)
- "label_images" folder
- current45.efdb
- despatches.db3
- fwdb.db3
- histories.db3
- log.txt

Once the above list of folders and files is copied into the WIFE "TEST" Server's "system" folder, rename the "log.txt" to contain useful information along this example:
"Update_fromProduction_Initials_yyyy-mm-dd_log.txt". This simple measure helps keeping track on these type of "best practice" actions of a farmerswife "TEST" environment:
- Before an version upgrade
- To try out new functionality
- To update existing workflows by changing Templates, Settings, Object configuration.
- etc.

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 WIFE Server as mentioned above, you can save time in the future by only copying these files from your PRODUCTION WIFE Server > from within the "system" folder:
- current45.efdb
- fwdb.db3
- histories.db3
- despatches.db3

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.

Booking Report

Extended Booking/Project Custom Field Variables to make them individually selectable in the Email_Project_Booking_Report text template, see details.

See Details

Added missing support for "Custom Templates" for the "Email Project Booking Report", which now allows selecting and displaying only certain Custom Fields from the Project or Booking in the email!

This behaviour can be configured for the "Subject" and "Body" fields, when using the "Email Project Booking Report" feature. The new configured "Custom Templates" are then available from the "Email Template" dropdown selector.

To select and display only certain "Custom Fields" from the Project or Booking in the email "Subject" or "Body", first create a new template .txt file with this this file-name-format "custom_template_CHOOSENAME.txt" within the farmerswife Server > html_templates > other > "booking_report_email" folder. Use the existing "english.txt" and COPY into same folder. Then change the name to "custom_template_xxx.txt"

Then from the fw Client > Booking > Menu ... go to Other > "Email Project Booking Report" and select this new created template a first time and send it. There's no need to enter an email recipient at this time.

This action populates the available Custom Fields of the Booking Name to the template as well as the Project Custom Fields of the Project this Booking belongs to. They are listed at the top under "Available keys" with the format: <BOOKING_CUSTOM_FIELDS_LabelName> and <PROJECT_CUSTOM_FIELDS_LabelName>.
Copy/paste these Custom Field keys below the "<Start Body - DONT EDIT THIS LINE>" section where you want the information of the Custom Field to be displayed.

Note: If you use the SAME custom_template to send an email project report from a different booking with different Booking Custom Fields, those variables will be displayed at the top of the template under the "Available keys". Overwriting the previous variables. But the variables you added to the Subject or Body beforehand will not be touched. If the system can't find a matching Custom Field variable in the current Booking you are sending the email from, the fields are showing "blank".

Use this for more information:


Booking Templates

Fixed a bug wrongly showing the red "Timereport" icon on "Frameworks" saved as "Booking Templates" if the Setting "Use Time Reporting" was disabled, see details.

See Details

The red "Timereport" icon and the "Timereport" button on the Edit Booking window were wrongly included on Frameworked Bookings, if in fw Client > Toolbox > Settings > Booking Defaults > "Use Time Reporting" was turned off = disabled, and this was saved as a Booking Template and reapplied within the Long Form.

Now the Timereport icon and "Timereport" button on the Edit Booking window are only added for a User who has the "Use Time Reporting" (see above path to this setting).


Cirkus Sync

Implemented farmerswife-Server side "pagination" support for the " API", needed when syncing more than 500 Projects.

See Details

Before this change the integration was creating duplicate Projects on the Cirkus-side, when syncing more than 500 farmerswife Projects. This support on the farmerswife side became necessary due to changes on the Cirkus API side.


Added tweaks for the integration after some improvements were implemented on the Cirkus API.

See Details

Implemented the new "taskTypeIds" argument to get Cirkus Projects Tasks.


Changed the low-level connection behaviour for the "" integration to avoid duplicates.


Fixed a bug by which the first fw Project selected to be synced to Cirkus, sometimes was not being synced.


Fixed a bug in the " Connection" integration, wrongly causing synced Projects to be wrongly deactivated in Cirkus when selecting the option "Close only in farmerswife".


Client Setup

Added a new "Setup" setting called "Get Server Info" ("No" by default) to be able to choose if the fw Client contacts the fw Server at launch, see details.

See Details

Go to fw Client > Login window > Setup > Edit Server window > "Get Server Info" check-box.
This setting is by default turned OFF to benefit all customers not using the below mentioned features.

This new setting needs to be enabled by customers using the"Pre-Login Message" functionality or the "OpenID Connect" (due to delegated login) integration.



Fixed a bug not causing Conflicts when extending a Booking in Long Form using option Booking > Days > "Add From Time Range".



Fixed a bug causing a crash when upgrading from v6.2 related to Passwords being "Hashed & Salted".


Fixed a bug wrongly preventing to Save changes on Contacts IF the system was upgraded from v6.1 SP1 to v6.4 SP1 without the usual upgrade steps.


Customer Specific

Extended beyond 2018 customer specific "hiding" of certain information related to the "Day Plan" print out, see details.

See Details

On for example the "Day Plan", the Project's year and Binder information is by design not supposed to be shown for all TV2 regions, when the Web Users print the "Day Plan > Til dagsplan" PDF. It was wrongly showing the "year part" of the Project Name and the amount of Binders.
This is now fixed and behaves as before.


Financial Report

Added "Menu Group" as a new Element in the Rows section of Financial Report Print Designer, see details.

See Details

The "Menu Group" is an optional field in the "Modify" window of "Extras" Objects (i.e. "Materials", "Services" and "Expenses").

This "Menu Group" has now been added as an Element to the "Rows" section of the Financial Report Print Designer, and will populate the "Menu Group" value configured on Materials, Services and Expenses.

On new created Financial Report templates, this new Element will be placed above "D: [Activity]" and below "D: Category (Object)]".
For already existing templates, it will appear at the bottom of the list.


Fixed a bug causing a fw Client Error when running a Financial Report on a Project Work Order, if "Sell Rate" and "List Price Rate" were used, see details.

See Details

Fixed a bug causing a fw Client Error when running a Financial Report on a Project Work Order, if the Report Template was using any of these recently (in v6.4) implemented "Rows" elements: "Sell Rate" and "List Price Rate".



Added a warning message when swapping two Objects in Framework Bookings if they are not member of the Framework Object Class.

See Details

Now there is a warning showing the Objects and the Classes that do not belong to the Framework Object Class.


Fixed a bug by which "Break (Min.)" was not updated in the Timereport window when changing the Break before allocating an Object to a Framework.


Fixed a bug on "Framework Break (Min.)" when setting a Break on a multiple day frameworked Booking and then removing it on only 1 day, wrongly all Breaks were removed, see details.

See Details

When selecting any of the days of a Framework and setting the Break time to 0 using the "Time In / Out (Override)" option, wrongly all Breaks on all days were removed.

Now the "Break" only gets removed on the selected day(s).



Fixed inconsistencies when using "Hotkeys" to run "Print Designer Templates" from Projects loaded to the Long Form > Projects tree, see details.

See Details

Previously when replacing a Project in the Long Form > "Projects" tree, in order to run a report on the newly loaded Project using pre-configured Hotkeys (via fw Client > Toolbox > Settings > Miscellaneous > "Hotkeys Editor" button > Functionality "Print Designer Template: ReportName"), even though the Project Name was displayed in blue (= selected), it was wrongly needed to also click on the actual Project Name for the Financial Report to display data that corresponded to that specific Project. Otherwise the Report would show data from the Project previously loaded to the Projects tree.

Now it is possible to just load the Project on the Long Form > Projects tree and use the pre-configured Hotkey to run the Report, without having to click on it anymore, given that there is only one Project loaded to the Projects tree.
To run a Report on multiple Projects you need to multiple select them.
If more than one Project is loaded to the Long Form > Projects tree, only the one selected will be printed when using the pre-configured Hotkey.


Incoming Invoices

Fixed a bug wrongly overwriting the Sell rate of Objects added to Projects via Incoming Invoice with the Buy rate, when modifying the related Incoming Invoice, see details.

See Details

The Sell rate of an Object added to a Project via an Incoming Invoice gets the Buy rate value if the setting "Use Buy As Sell Rate When Adding Incoming Invoice Lines To Project" (in fw Server > Setup > Financial tab) is set to "Yes"; and the Sell rate is 0.00 if the setting is set to "No".

This Sell rate can be later modified in the Project.

When opening the related Incoming Invoice to modify it (add into to the Note field, change the Buy rate, approve it, ...), when clicking "OK" to apply the changes, the Sell rate of the linked Object was wrongly being reset to the Buy rate.

Now, the Sell Rate is completely independent from the Incoming Invoice.


Invoice Creator

Fixed a fw Client crash error when Part Invoicing and moving all "Budget Details" from the "Not Selected" to the "Selected" pane in one go.

See Details

Note: Moving the "Budget Detail" line items one by one never stopped from working.


Invoice Manager

Fixed a bug that was wrongly causing Invoice Custom Field values to appear mixed up within the "search results" column view.


Labour Rules

Fixed a bug in Overtime Compensation Rules, preventing decimal money compensation, see details.

See Details

In Edit Labour Rule > Overtime Sub Rule > Financial Modifier, if you entered a decimal value and saved it, the decimal point was wrongly removed.
This bug was introduced in version 6.4 Beta rev. 17186; it there for only affected Labour Rules which were changed between 6.4 Beta 12 until the upgrade to 6.4 nightly rev. 17421 or later.


Fixed a bug wrongly not showing the Labour Rule Warning for "Rest Between Days" in the Long Form on the 1st day of a month.


Mobile Web Client

Fixed a bug wrongly causing the "User Approval Status" to change back to "Pending" after the Booking was "Accepted" via Mobile Web Client, see details.

See Details

This bug only happened, when an Object already had more than 1 Booking within the same timeframe.


Object Importer

Fixed a bug when using "Import/Export" of Objects type User, when importing a list of Users, wrong pop-up message "Updated x Objects" even when there was no update, see details.

See Details

Now if there are no changes on the previously exported CSV file and it is imported again, the pop-up message will now correctly display "There Were No Objects Created Or Updated".


Objects Tree

Fixed a bug in Long Form > View Port when dragging an element over the grey-colorer-days, they wrongly changed to white and never back to grey.


Fixed a bug when replacing a conflicting Object, this would cause confusing dialogs that could lead to deleting the complete Booking, see details.

See Details

Now, when replacing a conflicting Object it now works again as in v6.3: when replacing Objects, after "Confirm Replacing Object A with Object B" no further dialog message are displayed.


Print Designer

Fixed Print Designer Page Break issues where some Elements would wrongly "sit on" the actual page break, or some elements are on wrong page, see details.

See Details

Some elements in the Print Designer did not observe the Page Breaks and instead sat right on the boundary in-between pages or from vertically aligned elements from the same loop one of the elements was wrongly drawn on the following page.

Also Page Breaks for "grouped elements (so typically when using the Financial Report Designer) could cause "in-line" elements for one of the elements to be wrongly drawn on the following page.

We are still working on more improvements for the Page Breaks in other places of farmerswife.


Fixed some inconsistencies on "Page Breaks" causing that the second and following pages were wrongly empty when printed e.g. to PDF.



Fixed a bug that was wrongly showing the "Filter Objects" as disabled within Edit Project window > View Settings / Option > "Web View Limits" window. see details.

See Details

The "Web View Limits" column in fw Client > Toolbox > Projects tab was correctly showing an "F" (= Objects being filtered) next to the date. But in certain scenarios when opening the Project and going to "View Settings / Option" > "Web View Limits", the "Filter Objects" check-box was wrongly being displayed as un-checked = disabled.
This is now fixed and the "Filter Objects" setting is displayed correctly, and if enabled the filtered Objects are being displayed correctly and it now corresponds again to the displayed "F" in fw Client > Toolbox > Projects tab > "Web View Limits" column.


Public Holiday Calendars

Fixed multiple wrong Public Holiday dates in 2019 and later on the "Public Holidays Import" functionality for all now 7 available countries, see details.

See Details

On all 6 pre-existing "Public Holidays Import" by countries, there were unfortunately multiple wrong dates or wrong days in 2019 and later. All of them are now reviewed, checked and fixed.
We also added "Import Bank Holidays For Sweden".

We recommend:
1. Use "View Full List" and copy the contents for later review if necessary.
2. Use "Clear All Public Holidays From The System" for a clean slate start.
3. Use "Import Public Holidays For ..." your country if it exists. If it does not exist, please review the following information to e.g. adapt the "closest matching" pre-existing file for a fairly painless subsequent import.

IMPORTANT when using these pre-set Public Holiday lists: in your country, or region, or industry, or company different Public Holidays might apply or be more correct!
Please see the below instructions, on how to properly use this improved functionality.

For the "Import Public Holidays For ..." the pre-existing 7 countries, it will NOW read the data from the farmerswife Server-side stored "holiday" files for the import. Only these 7 presets will work.
These are located on your farmerswife Server root installation path > html_templates > other > new "holidays_importer" folder; this contains the below 7 listed "country-short-name.txt" files.

To use this functionality go to: farmerswife Client > Toolbox > Settings > Server Setup > "Public Holiday" button.

Click on this "Public Holiday" button to get the "Remove" or "Add" options.
=> "Remove" button:
Using this button will show selector list of all Public holidays ... single???select the one you want to remove.

=> "Add" button:
This button will open a Calendar to set the Date of the new Public Holiday, give it a Name.

NOTE: To "cancel" using the "Public Holiday" button, use the "esc" key on your keyboard until you reach the "Cancel" button on the next step and then use "Cancel" to abort the operation.

Use the sub-menu drop-down next to the "Public Holiday" button to:
=> "View Full List":
Using this option will open the "Current Public Holidays" pop-up window, listing all Public Holidays so far configured within farmerswife.

=> "Clear All Public Holidays From The System":
Using this option will do as it says, and clear all currently set Public Holidays from your farmerswife system.

=> Import Bank Holidays For Australia (au.txt)
=> Import Bank Holidays For Belgium (be.txt)
=> Import Bank Holidays For Denmark (dk.txt)
=> Import Bank Holidays For Germany (de.txt)
=> Import Bank Holidays For Sweden (se.txt)
=> Import Bank Holidays For UK (uk.txt)
=> Import Bank Holidays For USA (us.txt)

IMPORTANT: If you apply changes on the above mentioned files, use an advanced Text-edit-tool (e.g. "Notepad++" on Windows, or "Sublime 3" or "TextWrangler" on Mac), and ensure that the encoding of this file remains "UTF-8".

NOTE when using the " Import Bank Holidays For ..." feature:
- They do NOT affect pre-existing "Day Notes".
- Only 1 Public Holiday can be added per day.

After the import action, there will be a pop-up window containing two sections which shows what happened during the import:
=> "Added Public Holidays (amount):"
=> "Not Added Public Holidays (amount):"
If days are already configured as "Public Holiday" the "Import" will not add more. The ones not added will be listed here.

farmerswife has two different "Public Holiday" formats:
"All Day" = Will color the "Public Holiday" day in red.
"Half Day" = Will color the Public Holiday" day in orange. "Half Day" is typically used when a "Public Holiday" might not be observed in the whole country or industry, or if it's on a Sunday.



Fixed a bug wrongly preventing access to the REST API after v6.4 SP1.

See Details

Fixed "tcllib" packages on the v6.4. JSON package, which now allows to access the REST API again.



Added a "Password Policies Configuration" option to farmerswife Server > Setup > Users tab, see details.

See Details

It is now possible to also configure "user" Password Policies via fw Server > Setup > Users tab > Password Policies (bottom right) > "Configuration" button.

Using this fw Server-side Password Policies > "Configuration" button is the same as in fw Client > Toolbox > Settings > Server Setup > Password Policies > "Configuration" button.


Changed behaviour that now "Password Policies" only apply to user passwords, see details.

See Details

The "Password Policies" introduced on v6.4 now only applies to user passwords.

Password Polices now no longer affect these in farmerswife Server > Setup ...
> General tab > "Server Password"
> Projects tab > "Invoice / Close / Remove Password"
> Projects tab > "No Permission Users Allowed Attach Project Password"
> Media Library tab > "Library Password"
> Financial tab > "Invoice Manager Password"


Server Database

Fixed a DB upgrade bug to wrongly cause duplicated "Shared Hourline Views" to be unlinked under certain conditions, see details.

See Details

Fixed a DB upgrade bug to happen under certain conditions, wrongly causing duplicated "Shared Hourline Views" to be unlinked from the Web Permission Profile setting > in Events > Select & Share Hourline Views.


Server Setup

Modified the new "Password Policies > Configuration" from within the fw desktop Client app via Toolbox > Settings > Server Setup, see details.

See Details

The new "Password Policies" can now also be configured via the farmerswife desktop Client app > Toolbox > Settings > Server Setup > Password Policies > "Configuration" button, which opens a pop-up windows with a table displaying all the available options to set up the Password Policy rules.

The same "Password Policies > "Configuration" button" functionality is also now available on farmerswife Server-sidd; go to: fw Server > Setup > Users tab > Password Policies (bottom right) > "Configuration" button.

The previously used "JSON" file will not be used anymore after the upgrade. If Password Policies were already set-up via the "JSON" file, the configured values will be copied into the new configuration window and the file will be deleted to no longer be used. If no Password Policies were used, the default values (0) are applied.


Server Upgrade

Fixed a bug in the upgrade process by which the fw Server could crash when upgrading Contacts from a revision older than rev. 17149.



Fixed a bug causing not-active members of a Class to wrongly not show in Toolbox > Classes > Show Members > "Show Inactive" set to "Yes".


Web Client

Fixed a bug on Project > "Web View Limits" that an Object enabled in "Filter Objects", when removed and applied back to Framework Bookings it was wrongly re-enabled.

See Details

The "Web View Limits" allow the Project owner of a Project to plan and book without any involved user seeing any Bookings.

The bug caused that Objects wrongly remained checked on the Edit Project window > "eye" menu "View Settings / Options" > Web View Limits > "Filter Objects" when you removed and applied them back on a Framework Booking.

Now "Filtered Objects" will be treated as a different Object, if it is applied back to a Framework Booking so that the Object check-box in the Web View Limit section Filter Objects will not be ticked.


Web Profile Manager

Fixed a bug that was not showing Shared Hourline Views added via the "Can See All Shared Hourline Views" in Web Profile, when connecting via all Web Client, Mobile Web Client and iOS

See Details

Fixed a bug wrongly preventing "Shared Hourline Views" added via the Web Profile Setting "Can See All Shared Hourline Views" to be shown when connecting via all "Allowed Access Tiers", so iOS fw app, Web Client and Mobile Web Client.


Fixed a bug wrongly causing the Web Profile Permission "Allow Adding Objects To Timereport > His Own Object" to only work if "Divisions" was licensed.



iOS farmerswife app v5.0.827 available on Apple's App store since 26. February, 2019, see details.

See Details

- In Events week view changed the Personnel event icon (Vacation, Sick, etc.) from a "triangle" to now a "square" shape for increased visibility.
- Added some iPhoneX GUI fixes.
- Fixed a GUI bug on the Time-picker for iPhone 6 Plus when using in Settings > Display & Brightness > "DISPLAY ZOOM" > "Zoomed" mode (iOS > Settings.



Fixed a bug wrongly not displaying a Warning message when time-reporting a Booking to then overlap with a pre-existing Personnel Event, see details.

See Details

If this setting in a Web Permission Profile "Allow Reporting Over Existing Reported Time" is turned off, a Web User will get a "Warning" message if he tries to time-report a Booking that overlaps another Booking.

An example:
If Anne is booked from 10:00 - 12:00 and 12:00 - 15:00 and she time reports the first Booking to 10:00 - 12:30 and later tries to time-report the second Booking from 12:00 - 16:00, she will get a warning: "The Times Are Already Reported".

This warning however would wrongly not appear if the time report overlaps into an existing Personnel Event.
This is now fixed and the same warning message "The Times Are Already Reported" will be displayed. And the user will only be able to time-report once the Personnel Event has been adjusted accordingly.


Previous Releases


03. Aug 2018

6.4 SP 1


19. Jun 2018

6.4 Release