Back To Release Notes List



Back To Release Notes List

#19948

28. Jul 2021

6.7 Release

  • 1 Warning
  • 1 Hot Feature 13 Features
  • 13 Other changes
  • 42 Bug fixes

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

v6.7 Release rev. 19948, was released 28. July 2021.

Native v6.7 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.
- 1 HOT Feature
- 13 Features
- 12 Important Other changes
- 42+ Bug fixes

See the changes specific to this version: https://www.farmerswife.com/releasenotes/RN-67/R/

See the full list of all logged changes on our website: https://www.farmerswife.com/releasenotes/

... and also take a look into the new highlights summary of the most recent Released version "Whats New in v6.7": https://blog.farmerswife.com/farmerswife-release-v6.7

Check out our Getting Started videos for new Advanced Users joining your team!
https://www.youtube.com/playlist?list=PLA74zQEGurSW7WY9LJqO0jWLjaQnMXxPI

Upgrading to fw 6.7 Release and later - see details!

Basics
- You need to be on "Gold Support" past the date of the planned release of this version.
- You need to have a "Version 6.7" license at hand, before starting the upgrade process.
- To be eligible for a v6.7 license you need to have a valid support subscription (Gold or Silver) with us, at least up to 28. July 2021 or later.

IMPORTANT:
ONLY upgrade your farmerswife (fw) system from v6.6 Service Pack 2 rev. 19691 or later!
If your farmerswife system is still running on older versions, ensure you upgrade the fw Server application as per the must-do upgrade steps; contact support@farmerswife.com should you require further assistance.

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 app installers. 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.

Upgrading
- Your farmerswife Server application must have been running on versions v6.4 SP2 and then upgraded via 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 even more detailed information in the Upgrade Instructions on our open Knowledgebase (https://support.farmerswife.com/support/home):
=> Upgrade Instructions v6.7: https://support.farmerswife.com/en/support/solutions/articles/17000118224-upgrade-instructions-6-7
=> Client Installation Mac: https://support.farmerswife.com/en/support/solutions/articles/17000026002-client-installation-mac
=> Client Installation Windows: https://support.farmerswife.com/en/support/solutions/articles/17000026003-client-installation-on-windows

- 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.
We strongly recommend to use OpenJDK; more info here: https://support.farmerswife.com/support/solutions/articles/17000095590-how-to-replace-java-oracle-with-openjdk

farmerswife Server upgrade on Mac:

BEFORE you upgrade, verify which macOS or OS X version your farmerswife Server host Mac is running on!

IMPORTANT:
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.14 Mojave, macOS 10.15 Catalina and macOS 11.0.1 Big Sure or 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.7 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 "fw_server_v607.exe" installer, available since v6.5.
On any old 32bit Windows machines the fw Client application has to be manually upgraded by using the "fw_client_v607-32bit.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.7 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, Catalina or Big Sur) or Windows (64bit):
- Windows "64bit" fw Clients will be "auto upgraded" by using the simple-in-application-auto-upgrade when they first connect to the upgraded v6.7 fw server.
- macOS (Mojave, Catalina, Big Sur and later) fw clients will perform a full install when they first connect to the upgraded v6.7 fw server, by getting the Full Installer downloaded to the local computer to then be used to Replace the existing "farmerswife64" app within the "Applications" folder.

If your farmerswife Server or fw Clients are or running a macOS version earlier than Mojave, or a Windows 32bit, 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 & macOS 11.x Big Sur "64bit" fw Client Retina optimized: https://www.farmerswife.com/downloadsWeb/fw_client_v607.dmg

macOS 10.14 Mojave & macOS 10.15 Catalina & macOS 11.x Big Sur "64bit" fw Client:
https://www.farmerswife.com/downloadsWeb/fw_client_v607-nonretina.dmg

macOS Legacy 32bit Mojave or earlier fw Client https://www.farmerswife.com/downloadsWeb/fw_client_v607-32bit.dmg

Windows "64bit" fw Client: https://www.farmerswife.com/downloadsWeb/fw_client_v607.exe

Windows Legacy "32bit" fw Client: https://www.farmerswife.com/downloadsWeb/fw_client_v607-32bit.exe

Linux "32bit" fw Client: Please contact support@farmerswife.com if you need use the fw Client app on Linux.

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 support@farmerswife.com; 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.845 is available on Apple's App Store, click on "+" to see the details!

The latest iOS farmerswife app is v5.0.845 (same as 5.0.844.2) and is available on Apple's App Store since 22nd-February-2021.
IMPORTANT: Requires iOS 13
AND since v5.0.840: Added new barcode-scan support for the built-in Camera on the iOS device to be used for batch scanning items!
This is also in response to previously working 3rd party external barcode scanner support to no longer function, as support 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.

IMPORTANT:
Requires farmerswife v6.1 SP1 rev 16195 and later versions!

This means:
You should upgrade as soon as possible to the latest released version 6.6.
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.840; 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.

IMPORTANT:
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:

FW_IP
FW_PORT
EXTERNAL_PORT
HTTP_PORT
HTTP_HOME
USE_SSL
HTTP_SSL_PORT
HTTP_UPLOAD_PORT
FTP_ALLOW
FTP_PORT
FTP_PASV_PORT
FILE_PORT
PROXY_FILE_PORT
FILE_PORT_LOW
FILE_PORT_HIGH
MAIL_OK
MAIL_SERVER
MAIL_PORT
MAIL_USER
MAIL_PASSWORD
USE_SQL
SQL_USER
SQL_PASS
SQL_DB_HOST
SQL_DB_NAME
SQL_PORT
PRJ_CHECK_FOLDERS
MAIL_DEBUG
BARN_ACTIVE
HTTP_XML_PORT
WEBCLIENT20_ENABLED
WEBCLIENT20_PORT
WEBCLIENT20_COM_PORT
ALLOW_FORCE_RUN_NIGHTLY_SCRIPT
ALLOW_FORCE_RUN_PLAY_BILLABLES
TIMED_SCRIPTS_INTERVAL_SECONDS
MSAD_ENABLED
USE_EXCHANGE
READ_SCRIPTS_AS_UTF8
GOOGLE_SYNC
CIRKUS_ENABLED
FORCE_SHUTDOWN
USE_MSAZUREAD
PASSWORD_POLICIES_SRC default_password_policies.json
USE_THREADS
BACKUP_TIME
FULLBACKUP_CYCLES
FULLBACKUP_TIME
HTTP_HOME_ADD_WEBCLIENT_PORT
CRK_ENABLED
WEBCAL_ADD_WEBCLIENT_PORT
FORCE_WEBCAL_URI

These are additional settings/variables not set by default:
APNS_ENABLED
EXCHANGE_DEBUG
HTTP_DEBUG
LDAP_DEBUG

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!
FILE_PORT
PROXY_FILE_PORT

On our "Demo DB" these settings/variables will look like this:
FILE_PORT 24000
PROXY_FILE_PORT 24000

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:
MAIL_OK 0
USE_SQL 0
APNS_ENABLED 0
MSAD_ENABLED 0
USE_EXCHANGE 0
GOOGLE_SYNC 0
CIRKUS_ENABLED 0
USE_MSAZUREAD 0

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:
MAIL_OK
MAIL_SERVER
MAIL_PORT
MAIL_USER
MAIL_PASSWORD

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:
- current45.efdb
- fwdb.db3
- histories.db3
- despatches.db3
- log.txt

... 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.

Printing

On Windows the "Full-Installer-download fw Client app auto-upgrade" is enforced on upgrades passed 6.7 RC1, see details.

See Details

In order to be able to use the new "PDF Rendering Mode: New PDF Rendering (Beta), the "Full-Installer-download fw Client app auto-upgrade" needs to be enforced, which will then ensure that the needed "pdf4tcl" extension can get installed.

 

Apple Connect

Apple Connect fix on our http server read protocol, causing dropped connections.

 

Booking History

#310331

Fixed the Booking History info when changing Framework Names from empty/nothing selected; now it's consistently displayed using the format: "" Changed To "...".

 

Booking Templates

Added improvements for "Booking / Binder Templates" to be more smart and better handle when re-applying them accross "working days" and over "Weekends etc.".

See Details

Before, when using in fw Client > Toolbox > Settings > Misc. > "Never Select Weekends/Public Holidays" turned on, you would either have the correct in-between-Booking work-days OR no Bookings over the weekend; but you were not be able to apply the Template in a way, which would just exclude the weekend days.
This now works.

 

Bookings

It is now possible to customize the information in Booking mouse-over, see details.

See Details

It is now possible to customize the Booking mouse-over.

Click on the Setup Booking Mouseover Info button in Toolbox > Settings > Server Setup.

In the next window click on available display options to move them into the Selected pane, where you can drag and drop to adjust the order of the items. Note: You can add up to three separator lines.

 

Expanded the "Markup" option in Services used for calculating "Insurance markup" on Booking level, see details.

See Details

In order to use this option:

1. Go to fw Client app > Object Manager and use "New In > Services" to create a new Service Object and name it "Insurance". Add a Markup more than 0.

2. Enable the new setting in fw Client app > Toolbox > Settings > Server Setup > “Enable Insurance Markup Option On Bookings”.

When this "Insurance" Service is added to a Booking, it will calculate a markup based on the Total Sell price of the Booking, considering Discounts or Price Agreements added to the line items.

This calculation is based only on the Booked Objects, and not on Extras added via the Timereport.

This Service can be configured as a "Pre-defined Extra" on a specific "Booking Names" template, e.g. "External Equipment" (to configure this go to fw Client app > Toolbox > Settings > Booking Defaults > "Booking Names & Customs").

 

Fixed Booking mouseover that was not reflecting the new order as configured in Toolbox Settings > Server Setup > Setup Booking Mouseover Info

 
#333565

Fixed a fw client crash bug when using in fw Client > Long Form > Project tree > Booking > Days > "Move Start Day From Calendar".

 

Budgeting

Added a new "Counter" column for Categories and Accounts that contain data, see details.

See Details

There's now a new column called "Counter" in the Budget window, and a new field inside the Category/Account groupings of the Financial Report. It contains an auto-incremented counter for each Category/Account that actually contains any Budget Details or Actuals.

This counter value can be used if you need a consecutive number series for used Budget Categories and Accounts.

 

Added better timing support in Scheduling Mode when booking Object Classes but replacing with class members. See details.

See Details

When you dragged a mix of Object Classes with different quantities (e.g. some 2 days and some 1 day) onto a day in the Long Form, and then selected "Yes" in the "Allocate Objects For Classes?" dialog, it would loose the timing info on some (if not all) objects. So they would have the same quantity as the first object.
Now it correctly sets the quantity for each individual object that is allocated.

 
#335555

Fixed a "TCL alloc memory" fw Server crash which could happen on big Projects when clicking on the Budget icon.

 
#335555

Fixed a fw Server crash due to a TCL alloc memory limit of 2GB that is being exceeded by a cached variable.

 

Fixed bug in Scheduling Mode sometimes preventing actuals from being attached.

See Details

When dragging certain Budget Details to the timeline, the booked actuals would not get attached to the dragged Budget Detail.

 

Fixed bug in Scheduling Mode when booking deleted objects.

See Details

When you delete an object from the database, it doesn't get deleted from existing Budgets. So Budgets can contain objects that no longer exist in the database. But such objects can not be booked in the timeline. And when you dragged Budget Details with those deleted objects to the timeline, it would just not do anything.
Now it will show an error dialog saying that the object no longer exists.

 

Fixed bugs in Scheduling Mode related to the order of the dragged objects.

See Details

When you dragged objects from a Budget to a day in the Long Form, there was a bug that made it add the objects in a different order than they had in the Budget.

Additionally, whenever you selected "Yes" in the "Allocate Objects For Classes?" dialog, those allocated objects would always be added last. Now they instead maintain the same position as the class they came from.

 

Fixed bugs in Scheduling Mode when booking multiple lines with the same Object.

See Details

When you had multiple Budget Details for the same object, and you dragged them to the Timeline, it failed to attach each Booking line to their respective Budget Details.
It would instead attach all of them to the last Budget Detail. This is now fixed.

 

Client Upgrade

On macOS Mojave and later the "standard" fw Client desktop 64bit app is now the "Retina" optimized one, see details.

See Details

This means, that when manually downloading the "standard" fw Client desktop 64bit app or when getting it "served" after the upgrade of the farmerswife system, this is now the "Retina" optimized app.
The actual "Retina optimization" improved text and image sharpness to become visible, requires to run the fw Client app on a Mac with a "Retina" screen.

 

Contacts

Added new option to manage "financially blocked" clients and their invoices, see details

See Details

It was already possible to set clients as financially blocked, by using the option "Client Financial Control On Project" (in Server > Setup > Financial tab), and select what should happen once the credit limit was reached.

Once enabled, you could set a client as "Financially Blocked" via the Client Details tab in the Contact window, affecting the Contact (not the Company), and a "Credit Limit". Then, depending on the "Behavior" configured in the server, when booking or adding any cost that would exceed the credit limit, you would either be stopped, or warned, or allowed to continue.

Now we have enhanced this feature by adding the following functionality:

This option now applies at Company level. If a Company has more than one Contact, it is enough that you change only one.

In the Advanced Contact Search, you can highlight one or more clients from the results pane, and select "Set Financially Blocked To: Yes" or "Set Financially Blocked To: No" from the drop-down menu.

There is also new search field to filter by Financially Blocked, with three states:
- disabled (by default) to not consider the field when searching;
- when ticked you can search for financially blocked clients;
- when unticked you can search for clients that are not financially blocked.

And you can also see the values under the results pane, by configuring to see Financially Blocked as a column (in drop-down menu > Edit Views).

When creating invoices, you can see if clients are financially blocked in Invoice Manager.

Similarly here, add the column "Financially Blocked" (in drop-down menu > Edit Views) and use the search filter as explained above for Contact Search.

Also here you can change the value on a specific invoice by highlighting it and selecting "Set Financially Blocked To: Yes / No".

The changes you do on an Invoice will also apply to the Contact, and viceversa.



 
#319492

Improved that the Contact field "Client Number" can now be unique and respect "Company Relation" , see details!

See Details

In order to start using this Setting go to: fw Client > Toolbox > Settings > Server Setup > "Force Unique Client Number And Enable Warning". In order to start using it, this needs to be manually turned ON/enabled.

Once this option is enabled, it gets triggered when opening and thus checking and updating a Contact if the "Client Number" does not contain a unique Number value. If it's not unique, a Warning message pops up informing that the "Client Number Is Not Unique" and that this value was now updated to the first unique Number.

When doing so, this feature respects the configuration in fw Server > Setup > Contacts > for the "Company Relations" Settings, where if "Client Number" is enabled to be a "Company Relation" then the "Client Number" will be the "shared" or the same for all Contacts of a Company.
If the "Company Relations" is not turned on for "Client Number", then each Client Contact will get or will use a unique "Client Number" value.

 

EMT

Added for the Project Report and Dispatch Report a new Element called "Is Virtual Object" to the Element Row section, see details.

See Details

It is now possible to show in the Project Report and in the Dispatch Report, if an Object is a "Virtual Object", due to the newly added "[D: Is Virtual Object]" Element to the Element Row section.

This is needed if a Virtual Object is setup as an Accessory to its "main" or "parent" Object.
If more than one of the same Virtual Objects is added to an Object as an Accessory, those Virtual Object were previously bundled in the Reports, showing them in one line with the Total amount of the Virtual Objects.
And it is now possible with the new "Is Virtual Object" Print Designer Element to distinguish these from a "parent" Object with Accessories, by setting up needed String Operators against them for the sorting to take place within the Report.

String Operators setup:
1. Main Object:
In the Element section make a copy of the element "D:[Name]" and give it a new name, for example "Main Object". Create a String Operator using "String Compare".
Compare What: "Object Has Parent"
How: Equals
With: No
Return: Input
Else Return: Nothing

2. Accessory with its own Accessories:
Make a new copy of the element "D:[Name]" and give it a name, for example "Main Accessory".
Here you will need to add two String Operators:
2.1 "String Compare":
Compare What: "Object Has Parent"
How: Equals
With: Yes
Return: Input
Else Return: Nothing

2.2 "String Compare":
Compare What: "Object Has Children"
How: Equals
With: Yes
Return: Input
Else Return: Nothing

3. The rest of the Accessories which do not have an Accessory of their own:
Compare What: "Object Has Children"
How: Equals
With: No
Return: Input
Else Return: Nothing

4. Make a copy of the element "D:[Accessory]" and call it "Virtual Object Accessory".
Compare What: "Is Virtual Object"
How: Equals
With: Yes
Return: Input
Else Return: Nothing

5. Make a copy of the element "D:[Virtual Object Accessory]". Rename it for example to: "Non Virtual Object Accessory".
Compare what: "Is Virtual Object"
How: Doesn't Equal
With: Yes
Return: Input
Else Return: Nothing

This way you can edit the Virtual Objects to not show in bold, as you would show the Accessories that have Accessories itself.

 

It is now possible to add pure Object Classes to a Dispatch > Check Out, see details.

See Details

When preparing the list of equipment for a job, if you start from the Edit Booking window > "Create Dispatch" button, you can book by only using the Object Class as "TBD" (To Be Determined), so when the Dispatch is created, the warehouse people would see the list and start assigning specific equipment (i.e. Objects from farmerswife, e.g. by scanning them).

In some scenarios, you would start directly from a Check Out (without a booking). The issue was that it was not possible to add an Object Class into a Check Out.

This is now supported, and you can search for and add Object Classes via the "Add Object (Name)" search field in the Check Out window.

 

Added the text “Not Allowed For Multiple Check Outs” to the current Booking History line: “Removed (Dispatch)” in a specific scenario, see details.

See Details

Added the text “Not Allowed For Multiple Check Outs” to the current Booking History line: “Removed (Dispatch)” in the following scenario:

When creating a Dispatch > Check Out from a Booking that contains a Object multiple times, and if that Object doesn’t allow "Multiple Check Outs" (on the Object > “Allow Multiple Check Outs” check-box is OFF), farmerswife now removes those duplicates from the Booking after creating the Dispatch.
Before there was no extra info to know this had happened. Now, the Booking History contains the info: “Removed (Dispatch)”.

 

Financial Report

Added new Element "Financially Blocked" in "From Client" for Project and Invoice groupings, see details

See Details

If you are going to use the new option to manage "financially blocked" clients and their invoices, you might find helpful to also see this info when running a Financial Report either on a Project or Invoice.

A new Element called "Financially Blocked" has been added in the "From Clients" tree, for both Project grouping and Invoice grouping, in Financial Reports.

Select this element if you want to show that the client is blocked (value = Yes) or not blocked (value = No).

 

Invoiced numbers for Bookings are now more accurate with "Force Bookings Into Separate Days" and "Financial Lines In Range".

See Details

When you reported on an Invoiced Booking that spanned multiple days, all values (quantity, total sell, etc) in the Booking would be attributed to the first day in the Booking - even if you used the "Force Class Booking Into Separate Days" or "Financial Lines In Range" settings. Now it will respect those settings and split the Booking into days when possible.

 

Fix bug when using "Financial Lines In Range" with Credit Notes.

See Details

Recent changes have been made to how Invoiced numbers are calculated for Bookings, where it is now able to split numbers better across the Booking's days. But there was a bug in there related to Credit Notes. If you credited the Booking, or part of it, the Buy/Sell totals would be doubled instead of decreased.

 

Fixed a bug wrongly causing that on the Financial Report window the "Include Quoted" setting was cropped away.

 

Fixed bugs reporting on Invoices with "View Class Booking As Separate Days", see details.

See Details

Since each day becomes its own Invoice line, those lines shouldn't have a per-day breakdown.
And in that scenario it also shouldn't go to "get_lines_from_cb" because it would result in returning all lines for each line (so multiplying the lines), and in any case the invoice line itself is enough.

 

Frameworks

Fixed a bug that was wrongly causing the Framework "Day Note" to disappear when moving the Binder to start on a different day.

See Details

Also the mouse-over-Framework-yellow-pop-up was also lost in different scenarios.

 
#333737

Fixed a bug when swapping Frameworked Objects while the selected Project in the Long Form > Projects tree is a different one.

 
#333705

Fixed a bug when the focus of a Project was not correctly changed when deleting a Framework Booking, see details.

See Details

If there were two Projects in the Longform > Projects tree where one is highlighted, but you delete an Object of a Framework Cell of the Project that wasn't highlighted the Framework Cell Object didn't get deleted, as the Project focus didn't change correctly to the Project where you are deleting an Object. Now it does.

 

Google Invites

For the "Google Invites" functionality, implemented the options to use "Google Cloud" and "Google Workspace" by creating a Google Service Account with domain delegation, see details.

See Details

The new "Google Invites" options are located in fw Client > Toolbox > Settings > Server Setup > "Google Invites:" area.
By using this setup, it is now possible to use "Google Cloud" and "Google Workspace" by creating a "Google Service Account" with domain delegation.

The configuration takes a moment of time.
Please use this detailed article on how to set this up:
https://support.farmerswife.com/support/solutions/articles/17000117002-configuring-google-invites-connector-to-use-your-own-domain

 

Icons

Added new user icons (Bricks).

 

New User & Other Icons!

See Details

New for 6.7, we have 32 New User icons starting from "user_brick-01". There are also some additional "Other" icons for use with Objects, that you are able to change within the icon selector of an Object within the Object Manager.

 

Installers

For the macOS 64bit fw Client desktop app added support to now "open as any other app" by double clicking it from within the "Applications" folder, see details.

See Details

This added support for the macOS 64bit fw Client app to now "open as any other app" by double clicking it from within the "Applications" folder, required to add the needed "notarization" from Apple.

When running the macOS 64bit fw client desktop ("on macOS Mojave or later") app package the first time after the installation with a double click, it will now tell the user with a single prompt that it is trusted by Apple. Notarization gives users more confidence that the farmerswife macOS 64bit fw client desktop app installer has been checked by Apple for malicious components.

 

Invoicing

Added a new setting in fw Client > Toolbox > Settings > Server Setup > “Mark Invoice As Paid According To Payment Terms”, see details.

See Details

This setting is ON by default, to ensure previous default behaviour to work as before.

If you then disable “Mark Invoice As Paid According To Payment Terms”, then the set "Payment Terms" set on the Contact type Client like “Payment in Advanced", "Net Cash", "C.O.D (Cash On Delivery)” will not mark the Invoice as “Paid” at the moment of moving it to the “Invoice Manager”.

 

MacKiosk

#334370

Fixed a bug wrongly preventing MacKiosk users from logging in, due to a previously not supported "Inventory Number" format.

 

Added support for MacKiosk to run on macOS Catalina and Big Sur.

See Details

This change is available with latest Mac Kiosk version 2.6.13.

 

Notifications

#327936

Send Email Notification On Booking Accept to external email address. See details.

See Details

This notification will be triggered when the Status of an Involved User changes from "Pending User’s Approval" to "Declined" or "Approved" (by User).

If the Web Profile setting "User Must Accept Or Decline New Booking" (in Web Profile > Events > Objects > His Own Object) is set and the User is added to a Booking that he then declines/approves, the Person who is added to the "Alternate Email" box will receive the notification.

If various Users have declined/accepted the same Booking, one Email per Booking is sent out.

To enable this Notification an Advanced User needs to configure the Toolbox > Settings > Notifications > Global Notifications:
- On Booking Declined By User - Only Alternate Email
- On Booking Accepted By User - Only Alternate Email

Also the email addresses must be added under the "Alternate Email" button.

To include the additional details below to the email check the: "Include Details To Alternate Email".
- Involved User (who "accepted/declined")
- Project Name (Number)
- Booked Object Class
- Date(s) - Time - Week Day(s)
- Buy Rate

 

Objects

#332388

Enabled that the option to "Replace With Available Class Member" is now also available for "Task / Bookings" Advanced users.

See Details

The option “Replace With Available Class Member” (Booking Menu > Booking Object) was before only available for "Task / Bookings / Rates" Advanced users.

 

Fixed a bug that when replacing an Accessory of an Object with another Accessory, the replaced Object would wrongly not be an Accessory of the main Object anymore.

 

Fixed a bug when the setting "Allocate Object Even If It's Not Available" was active it wrongly didn't work on Objects Accessories, see details.

See Details

To access this setting go to: fw Client app > Toolbox > Settings > Class/Object > "Allocate Object Even If It's Not Available".

 

Print As PDF (fw Client side)

Implemented next step for improved image quality in PDFs, while keeping the current text-sharpness.

 

Print Designer

#333636

Added "Century Gothic" font support as native mapping.

 
#333465

Added "HeadingPro" font support as native mapping.

 
#333725

Added "Pill Gothic" font support as native mapping.

 
#336484

Added the 5th "Print Designer Version" - now focussed on fixing Page Breaks issues in the Total sections, using multiline texts and many “dynamic” Total values next to each text line, see details.

See Details

Go to fw Client > Toolbox > Settings > Server Setup > “Print Designer Version” by which you can select and keep using a specific version of the Print Designer, while we continue fixing and adding new versions solving other issues.

This latest “Print Designer Version: 5" is specially focussed on fixing Page Breaks issues caused within the Total sections, when using multiline texts and many “dynamic” Total values positioned next to each text line.

Summary of all 5 “Print Designer Version" options:
1: Default "Built In PDF Printer".

2: To help when using Print Designer Templates with many "loops" and Rectangles.

3: Specially focused to fix issues on Print Designer Templates, where the Text Elements do not aligning properly after a Page Break, where this is caused by using multiple-line texts in "Loop" and "Page" positions with Rectangles causing Page Breaks.

4. Specially focused to fix issues on Print Designer Templates, where in the template's "Setup" "Show Header In Each Page" is being used. This could wrongly cause, that some Text Elements were wrongly overlapping after a Page Break.

5. Specially focused to fix issues on Page Breaks issues caused within the Total sections, when using multiline texts and many “dynamic” Total values positioned next to each text line.

 

Fixed a Page Break bug when iterating through multi-line values of Elements, which caused long multi-line text to not be properly aligned after the page break.

 

Fixed a Page Break issue caused when using Text Elements as "table headers", creating misalignment of Report Elements past the first page of a multi-page Report.

 

Fixed a bug affecting multi-line texts in the Totals section on the Invoice Print Designer, wrongly "jumping" around.

 
#333943

Fixed a bug on the "SUM()" feature wrongly doubling totals when linked in a Loop higher up the Print Designer, see details.

See Details

The "SUM()" feature is mainly used in the Footer section of the Print Designer.
If you linked this to a Print Designer loop higher up, for the Total to appear higher up on the page, the link was wrongly causing to double the Total displayed in the higher-up loop.
This fix prevents the doubling of the resultant figure, displaying the correct figure in loops higher up on the page.

 
#332405
#335121

Fixed a bug on the Dispatch Print Designer wrongly showing incorrect Quantities on the Report, see details.

See Details

When adding a new Object to the Dispatch with a Quantity of more than one, it was wrongly showing only 1 as the Object's quantity even though there were multiple. Now the correct Quantity is shown on the Report.

 

Fixed a bug on the Page Break calculations of the vertical y-position of Elements from the Rows section, wrongly causing Elements on the next page to be overlapped.

 
#330964

Fixed the Print Designer's “Split On Space” edge-precision when resizing it.

 

Printing

Added a new setting “PDF Rendering Mode” with a new option for images - this is still work in progress, see details.

See Details

This new added setting is located in fw Client > Toolbox > Settings > Server Setup > “PDF Rendering Mode” with the following 2 options:
- Default current: “Default Rendering (Faster/Optimized For Texts)”
- The new option: “Image PDF/Antialiasing (Optimized For Images)”

The image print quality on the new fw Client 64bit app will show the most improvements when printing from Mac. On Windows the improvements are not so strong.
We are still not satisfied with the current image quality and we are still working on this!


 
#329811
#332946

Added native support for "Trade Gothic LT Standard Condensed 18” and “GT Haptik" fonts for the Built-In Printer.

 

Added native support for "WorkSans" font for the new Built-In Printer.

 
#335554

Added the 4th "Print Designer Version" - now focused on overlapping text issues when using "Show Header In Each Page", see details.

See Details

Go to fw Client > Toolbox > Settings > Server Setup > “Print Designer Version” by which you can select and keep using a specific version of the Print Designer, while we continue fixing and adding new versions solving other issues.

This latest “Print Designer Version: 4" is specially focused to fix issues on Print Designer Templates, where in the template's "Setup" "Show Header In Each Page" is being used. This could wrongly cause, that some Text Elements were wrongly overlapping after a Page Break.

Summary of all 4 “Print Designer Version" options:
1: Default "Built In PDF Printer".

2: To help when using Print Designer Templates with many "loops" and Rectangles.

3: Specially focused to fix issues on Print Designer Templates, where the Text Elements do not aligning properly after a Page Break, where this is caused by using multiple-line texts in "Loop" and "Page" positions with Rectangles causing Page Breaks.

4. Specially focused to fix issues on Print Designer Templates, where in the template's "Setup" "Show Header In Each Page" is being used. This could wrongly cause, that some Text Elements were wrongly overlapping after a Page Break.

 
#324694

Fixed Batch printing of Invoices that was not printing fonts correctly to Acrobat Reader

 

Implemented to auto-run a "Scan Fonts" after “fw Server start” and “fw Client login”, see details.

See Details

Now, farmerswife auto-run a "Scan Fonts" after “fw Server start” and “fw Client login” when:

fw Client login:
- After an upgrade (revision change) or PDF Rendering Mode has changed since last "Scan Fonts"
- If the Fontmap.GS file doesn’t exist or corresponds to another PDF Rendering Mode (e.g. when testing different Templates on the same machine).

fw Server start (INIT):
- If the Fontmap.GS file doesn’t exist or corresponds to another PDF Rendering Mode (e.g. when testing different Templates on the same machine).
For this case there are new fw Server app Log lines (also logged on the fw Server's log.txt):
“Fontmap: File Format Check Starts” and ...
"Fontmap: Starting New Font Scan To Fix File Format" ... or ...
"Fontmap: File Format Check OK".

 

Re-implemented "custom page setup" for the new PDF printing, see details.

See Details

If a page height or width is adjusted on the Print Designer, this is reflected on the exported PDF, by the PDF page being expanded to match the new page size from the Print Designer.

This applies to both single templates, and single templates within a Group Template.

 

First approach to print directly to printer. Work in progress.

See Details

Making direct printing available only on Mac

 

Project & Invoice Reports

Added to Project and Invoice Report to create Totals based on elements created with String Operators or values from Custom fields, see details

See Details

If you have created some new elements in the Project/Invoice Report Details or Element Row section using string operators or if you have number values added to custom fields you can create a Total of these values in the Project and Invoice Reports.

In the Report Total section click on the green plus icon and select "Text". In the Text box add the word SUM followed by a parenthesis containing the name of the element that should be summed up, for example if you created a new element called "Sell Row Editors", then the formula in the Text field should be SUM(Sell Row Editors). This will sum up all values from the selected element.

Note that if the number is round, i.e. does not have any decimals, the total will not show 00 for decimals.

 

Projects Tree

Added the ability to multi-select Binders in Long Form > Project Tree with SHIFT&Click. Select first Binder > press Shift > select last Binder.

 
#334880

Improved the Projects tree feature "Auto from View Port", to now respect the "Maximum Hits When Searching" on limiting the amount of Projects being auto-loaded, see details.

See Details

Due to performance issues a auto-load limitation was introduced for "Auto from View Port" feature, accessed via fw Client > Long Form > Projects tree icon click > "Auto from View Port".

When auto-loading Projects based on the selected time period in the "View Port" section and using the "Auto from View Port" feature, it would only load max. 51 Projects which have Bookings in the selected timer period.

This limitation has now been changed and is now linked to the "Maximum Hits When Searching" Setting (located in fw Client > Toolbox > Settings > Miscellaneous > "Maximum Hits When Searching").
If "Maximum Hits When Searching" is set to 100 - then the "Auto from View Port" will now load max. 100 Projects in the Projects tree, etc.

 

Reports

Added for the new "Consumption Report" that the Group Availability will now count as a Booking, see details.

See Details

A new line "Group Member Alert" was added to the new "Consumption Report", which is available in fw Client > Long Form > Classes (Availability) icon mouse click > Reports > "Consumption Report".

If a Member of a Group is booked, the Group will show a yellow warning triangle icon.
This will now also be shown and added to the sum of the Bookings per day.

 

Added new report in Long Form > Classes (Availability) tree > Reports > "Consumption Report" to display % of usage per Total amount of Class Members vs number of Bookings, see details.

See Details

Added new report in Long Form > Classes (Availability) tree > Reports > "Consumption Report" to display % of usage per Total amount of Class Members vs number of Bookings, see details.

This new consumption report allows you to load one or multiple Object Classes and run a monthly report on the selected Classes. The report will be shown horizontally in landscape mode and the month is the current month selected in the View Port. Even if you just select a few days, the whole month will be shown.

Inside of the report you can show the total members of an Object Class and run the calculation against the daily Bookings or Tasks that have been created on any of the Object Class members.
You can also show External Hires: Those will emerge from any Availability that is shown as "-1, or -2" in the Class Tree.

Please note: In the Class Tree Tasks Bookings, confirmed and preliminary Bookings as well as planning Bookings are considered and will count as Usage or lower the Availability of the Object Class per day. E.g. two half day Bookings will not show as 2 Objects taken or booked, they will be considered as one Object not available or used.

 

Server

#335536

Added a potential bug fix for a "sqlite transaction" issue on fw Server-side possibly caused by iOS fw app login.

See Details

The fw Server-side error message could contain this info:
"Error (XML PORT): cannot start a transaction within a transaction
cannot start a transaction within a transaction"

 

Timelines

Improved the Project Selector window to only search on Project Name and sort the results alphabetically, see details.

See Details

The Project Selector window opens when:
- booking in the Hourline or Long Form and selecting "Booking On <Search Projects>" from the drop-down menu, or when
- selecting "Project On <Search Project>" from the Long Form > Project tree drop-down menu.

This "Project fast-picker" window is now improved to only search by Project Name and sort the results alphabetically by Project Name.
Before it was also searching on other Project fields, and the results were listed in a random way.

 

Web Client

Added a first version of German Language support for the Web Client to show instead of “Time Report” the neutral ""Produktionsbericht".

See Details

It is now possible to change on the Web Client the language to "German".
In this first version, only the terms "Time Report" and "Time Reports" will be translated and are now called: "Produktionsbericht" and "Produktionsberichte".

 

iOS WIFE app

Fixed push (APNS) notifications.

See Details

The latest iOS farmerswife app is v5.0.839 and is available on Apple's App Store since 3rd-July-2020.
IMPORTANT: Requires iOS 12 or later.

 

Previous Releases