Back To Release Notes List



Back To Release Notes List

#19691

25. Nov 2020

6.6 SP 2

  • 1 Warning
  • 2 Hot Features 10 Features
  • 10 Other changes
  • 67 Bug fixes

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

v6.6 Service Pack (SP) 2 Release rev. 19691, was released 25. November 2020 with these changes:

- 1 Warning: - On Windows - The fw Client “Full Installer Download auto-upgrade” is enforced to upgrade, Windows user permissions Read, Write and Execute are necessary to run the installer!
- 2 HOT Features
- 10 Features
- 10 Important Other changes
- 67+ Bug fixes

See the changes specific to this version: https://www.farmerswife.com/releasenotes/RN-66/SP-2/
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 "Whats New in v6.6 SP2": https://blog.farmerswife.com/farmerswife-release-v6.6-sp2

-----------------------------------------------------------------
v6.6 - Service Pack (SP) 2 - Release Candidate (RC) 2 rev. 19667 was released after 3. November 2020 to involved customers with these changes:

Native v6.6 SP2 RC2 changes:
- 1 Warning - On Windows - The fw Client “Full Installer Download auto-upgrade” is enforced to upgrade, Windows user permissions Read, Write and Execute are necessary to run the installer!
- 8 Features
- 8 Other important changes
- 48+ important Bug fixes

See the changes specific to this version: https://www.farmerswife.com/releasenotes/RN-66/SP-2-2/
See the full list of all logged changes on our website: https://www.farmerswife.com/releasenotes/

-----------------------------------------------------------------
v6.6 Service Pack (SP) 2 Release Candidate (RC) 1 rev. 19400 was released after 12. June 2020 to involved customers.

Native v6.6 SP2 RC1 changes:
- 1 HOT Feature
- 2 Features
- 17+ important Bug fixes

See the changes specific to this version: https://www.farmerswife.com/releasenotes/RN-66/SP-2-1/
See the full list of all logged changes on our website: https://www.farmerswife.com/releasenotes/

-----------------------------------------------------------------
v6.6 Service Pack (SP) 1 rev. 19322 was released 20. May 2020 with these 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.
- 5 HOT Features
- 17 Features
- 12 Important Other changes
- 33+ Bug fixes

See the changes specific to this version: https://www.farmerswife.com/releasenotes/RN-66/SP-1/
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 "Whats New in v6.6 SP1": https://blog.farmerswife.com/farmerswife-release-v6.6-sp1

-----------------------------------------------------------------
v6.6 Service Pack (SP) 1 Release Candidate (RC) 3 rev. 19311 was released 18. May 2020 to involved customers.

Native v6.6 SP1 RC3 changes:
- 1 Very important Bug fix

See the changes specific to this version: https://www.farmerswife.com/releasenotes/RN-66/SP-1-3/
See the full list of all logged changes on our website: https://www.farmerswife.com/releasenotes/

-----------------------------------------------------------------
v6.6 Service Pack (SP) 1 Release Candidate (RC) 2 rev. 19308 was not released; only used internally.

Native v6.6 SP1 RC2 changes:
- 1 Important Other change
- 2 Important Bug fixes

See the changes specific to this version: https://www.farmerswife.com/releasenotes/RN-66/SP-1-2/
See the full list of all logged changes on our website: https://www.farmerswife.com/releasenotes/

-----------------------------------------------------------------
v6.6 Service Pack (SP) 1 Release Candidate (RC) 1 rev. 19291 was released 14. May 2020 to involved customers.

Native v6.6 SP1 RC1 changes:
- 4 HOT Features
- 19 Features
- 10 Important Other changes
- 32 Bug fixes

See the changes specific to this version: https://www.farmerswife.com/releasenotes/RN-66/SP-1-1/
See the full list of all logged changes on our website: https://www.farmerswife.com/releasenotes/

-----------------------------------------------------------------
v6.6 Release rev. 18918, was released 29. January 2020.

Native v6.6 changes:
- 1 Warning: The new v6.6 "64bit" fw Server installers on Windows and Mac support the auto-upgrade for the fw Client app in certain scenarios.
- 4 HOT Features
- 10 Features
- 3 Important Other change
- 23+ Bug fixes

See the changes specific to this version:https://www.farmerswife.com/releasenotes/RN-65/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 "Whats New in v6.6": https://blog.farmerswife.com/farmerswife-release-v6.6

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

Upgrading to fw v6.6 SP2 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.6" license at hand, before starting the upgrade process.
- To be eligible for a v6.6 license you need to have a valid support subscription (Gold or Silver) with us, at least up to 29th January 2020 or later.

IMPORTANT:
ONLY upgrade your farmerswife (fw) system from v6.6 Release rev. 18918 or later!
Ideally you upgrade from v6.6 Release rev. 19819 to v6.6 SP2.

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; they are still the same as for v6.6 Release:
=> Upgrade Instructions v6.6: https://support.farmerswife.com/support/solutions/articles/17000099480-upgrade-instructions-v6-6
=> 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.6 license files into the "system" of the NEW WIFE server.
- On the 1st start-up only, right-mouse click and use "Open" to launch the fw Server and allow it to run to start the actual upgrade process.
Note: The upgrade itself might require a couple of "Forced Shutdowns" for it to finish; this depends on your usage of the system.
From now on you can simply double click on the NEW farmerswife Server package icon to launch it.
- Once everything worked out fine, remove or update any Dock or Desktop links. And if needed remove the OLD Server package; because up until now, this was a working "roll-back" backup, just in case something went wrong.
- After the upgrade, start the farmerswife Server as usual.

* You might also need to copy the "html_templates" (only if used and if it contains customized templates) folder. And if you are using any 3rd party integration scripts, don't forget to manually migrate these from OLD WIFE Server package > Contents > "Show Package Contents" > lib > scripts > ... and then here only copy the integration script files from the according sub-folder and not the whole "scripts" folder.
Note: The "files" folder might not even be there, since it was broken out, to reside on some other storage device within your network.

farmerswife Server upgrade on Windows and Linux:
On Windows you should only be using the new "Windows-x64-64bit_farmerswife_Server...exe" installer, available since v6.5.
On any old 32bit Windows machines the fw Client application has to be manually upgraded by using the "Legacy-Windows-x86-32bit_farmerswife_Client.exe" after each system upgrade.

On Linux there is still only the "Legacy-Linux64" Server installer available.

- Make sure you are logged into the host machine with the same admin user as on the initial installation of the farmerswife server application.
- Copy the NEW farmerswife Server installer file to the machine hosting the WIFE Server.
=> On Windows this is a .exe file
=> On Linux use these instructions: https://support.farmerswife.com/a/solutions/articles/17000026005-server-and-client-installation-linux
- Quit the running farmerswife Server.
- Now copy the new v6.6 license files into the "system" of the NEW WIFE server.
- Double click to run the installer file in the same manner as the previous installation (for example did you use "Run As Administrator" on Windows?).
- Follow the instructions of the install wizard.
- After the upgrade, start the farmerswife Server as usual.

The farmerswife Client desktop applications can potentially use the fw Server auto-upgrade functionality...
... by using the "FULL" Client upgrade process; OS admin user permissions Read, Write AND Execute are necessary on the initial upgrade.

If your farmerswife Server is macOS 64bit (Mojave, 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 6.6 SP2 fw server.
- macOS (Mojave, Catalina, Big Sur and later) fw clients will perform a full install when they first connect to the upgraded 6.6 SP2 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.0.1 Big Sur "64bit" fw Client: https://www.farmerswife.com/downloadsWeb/fw_client_v606_SP2.dmg

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

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

Windows Legacy "32bit" fw Client: https://www.farmerswife.com/downloadsWeb/fw_client_v606_SP2-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.840 is available on Apple's App Store, click on "+" to see the details!

The latest iOS farmerswife app is v5.0.840 and is available on Apple's App Store since 5th-November-2020.
IMPORTANT: Requires iOS 12
AND: 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

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

Client Upgrade

#327810

On Windows - The fw Client “Full Installer Download auto-upgrade” is enforced to upgrade, Windows user permissions Read, Write and Execute are necessary to run the installer, see details!, see details!

See Details

The fw Client "Full Installer Download auto-upgrade" process from revisions lower than rev. 19430 is enforced, in order to ensure the latest Ghostscript version is present.

This means local Windows Operating System (OS) user permissions Read, Write and app-installation-Execute permissions are necessary to run the installer.

 

Bookings

#327442

Added option to copy "Extras" to paste to another Booking, see details.

See Details

This option could be useful for recurring expenses that need to be added to various bookings, as it requires less steps and copies over same price and note.

In the Edit Project window, to copy Objects added as "Extras" via the Timereport, click on Object's menu icon where you will find the two options:
1) "Copy"
2) "Copy (Add To Existing x In Buffer)". (x = the number of extras previously copied)

Paste by clicking on the menu icon of the Booking to which you wish to copy the extras, and selecting "Paste Copied Extras (x)".

To copy and paste only one Extra select "Copy" from the Extra's and paste to another Booking.
To copy multiple Extras, first create one Copy and then for each new Extra select "Copy (Add To Existing x In Buffer)" to then paste to another Booking.

The "Added By" info from the copied/pasted Extras is set to the current user's Username.

The "Day" is reset to use the first day of the Booking where the Extra was copied/pasted to.

The "Note", "Quantity" and "Rate" infos are also copied over.

 

Changed that when using "Actual Time Range" it is now possible in the Long Form to set the Out (end) Time of a multiple-day Booking to an earlier time than the In (start) Time, see details.

See Details

In the Long Form > on a Booking > right mouse click Menu > "Time In / Out" and with the setting "Use Actual Time Range" enabled, on a multiple-day Booking it was not possible to change the Out Time on the last day to an earlier time then the In Time of the first day.
Before it would automatically set the In Time = Out Time if you changed the Out Time to an earlier time than the originally set In Time.
This has now been changed, so you can now set the In/Out times for example to: first day In Time: 16:00 and on the last day the Out Time to: 10:00.

 
#326496

Fixed a bug on macOS Catalina when pasting e.g. from Finder's files clipboard into a Text field in farmerswife, then this did not always respect line breaks, and emoticons could not be copied.

 
#324789
#327553

Fixed a bug where it was not possible to Change Project / Media Order / Task Option from the Booking menu on Windows or fw mac32bit client

 

Fixed a fw Client crash when creating a Booking with Services as Ad-hoc Extras.

 

Budgeting

Now Object Classes show the "Name" set via the Edit Booking window, in the Actuals window in the Budget module, see details.

See Details

Especially in rental workflows, when cross-hiring with equipment form external Suppliers, you can book a generic Object Class called e.g. “External Object” and you can change the “Name” via the Edit Booking window to specify what equipment it actually is (this is done via the Involved pane > Object menu > right mouse click "Edit Name”).

Before, if you also use the Budgeting module, the Actual would still show the original Object Class name, e.g. “External Object”, within the Description column, making it impossible to tell which specific "External Object" it was.

Now this "Name" you changed via the Edit Booking window, is also displayed within the Description column.

 
#328307

Fixed a bug that was wrongly causing Budget cells to not be editable anymore, after changing the columns width or moving lines around.

 

Fixed a bug when booking multiple Objects with Accessories in Budget Scheduling Mode, see details.

See Details

When an Object had Accessories and you either dragged multiple lines of that same Object, or used a Multiplier greater than 1, the Booking would have the wrong structure. All Accessories would wrongly be grouped under the last parent. Now they are correctly added to their own respective Parent Objects.

 

Fixed grouping of Virtual Objects created from Object Classes in Budget Scheduling Mode. See details.

See Details

If you...
- Added a Virtual Object to an Object Class,
- Added the Object Class to a Budget with a Multiplier > 1,
- Booked the Object Classes in "Scheduling Mode",
- Selected "Yes" in "Allocate Objects For Classes?",
... then the booked Virtual Objects would not be grouped under a common Parent. Now they are.

 

Fixed grouping of Virtual Objects in Scheduling Mode, see details.

See Details

You can add a Virtual Object to a Budget and use a Multiplier to set the number of Objects. But when you dragged that Object to a Timeline in Scheduling Mode to create a Booking, the Virtual Objects would not be grouped under a common parent. Now they are.

 
#328573

Fixed a fw client crash when creating a Budget, due to an internal tk issue only happening on the new macOS-64bit app.

 

Cirkus Sync

Fixed Custom Field "farmerswife" section header wrongly not showing in cirkus projects synced from farmerswife.

 

Class Bookings

#328682

Fixed a bug preventing Shift-select multiple Bookings in Long Form > Projects tree from working.

 

Container

#327729

Fixed a bug that was not allowing to attach Projects to Containers on Windows

 

Fixed a bug that was wrongly causing to show a blank window when editing a Container from Edit Project window or Toolbox > Projects.

 

Custom Fields

#325716
#324934

Added support for "Confidential Custom Fields" on Tasks and Bookings. See Details.

See Details

In Server Setup > Users > enable the "Use Confidentially User For Custom Fields".
Add those Users that later should be allowed to see the Confidential Custom Fields.
Only Advanced Users can be selected here.
As a next step you could setup a Task with a Custom Field: Text Widget, Label: "Private Note" that allows to enter a Note.
Only the Users added to the Server Setup List will be able to see, access and edit the field on tasks. Turning the task into a Project Booking, only the Users that are added to the Server Setup List will be able to see, access and edit the field
Logging in as a "Non-Confidential User" I cannot see the information, nor access through reports or Web Access.
For more details please see https://bit.ly/2OUUgrj

 

Expanded the Custom Field > Finder menu to be able to select what Contact type from the Contacts the Finder will look for, see details.

See Details

We’ve expanded the Finder menu options available for Entry and Text Widget Custom Fields. When creating Custom fields with the type Entry Widget or Text Widget, there is an option called "Finder (Entry/Text Only)" that allows you to connect the custom field to the Contacts registry. Before, the Finder would connect to the entire contact database, but with this new development you can define which type of Contact the Finder should look for, for example only Client Names, only Resource Names, only Global Names, or only User Names.

Before, the list contained 5 options: None, Contact Names, Contact Companies, Company Id’s, Users With Date Stamp.

Now we have the following options:
None: Not using the Finder to select a value for the field.
Contact Names: This will look for any First/Last Name in the Contacts.
Contact Companies: This will look for any Company Name in the Contacts.
Company Id’s: This will look for any Company’s ID (if used).
Users With Date Stamp: This will look for any user in the system and pull in the value "Date/Time – Username"
Client Names: This will look for any Client Contact First/Last Name in the Contacts.
Client Companies: This will look for any Client Company Name in the Contacts.
Resource Names: This will look for any Resource First/Last Name in the Contacts.
Resource Companies: This will look for any Resource Company Name in the Contacts.
Global Names: This will look for any Global First/Last Name in the Contacts.
Global Companies: This will look for any Global Company Name in the Contacts.
User Names: This will look for any User’s First/Last Name in the Contacts.

 

Fixed a bug when adding a new Custom Field type Entry configured to use "Finder", where the set Finder configuration was wrongly reset to "None".

 

Debug message

Fixed so there is no more "calendar debug" information visible on the fw Server > Log window.

See Details

This debugging information, on every "External Calendar, Schedule Changes Email and Hourline XML Export" process, was wrongly not removed after the v6.6 Beta development phase. Now, this is correctly no-longer being displayed.

 

Dispatch Module

Added a new "Password" protection for the "Unlink" option on a Dispatch > Check Out, see details.

See Details

This password was added to protect the accidental un-linking of Bookings from their linked Dispatch > Check Outs. IMPORTANT: It is not possible "re-link" an existing Booking with an existing Check Out once they are un-linked.

To start using this new feature, go to the running fw Server app > "Setup" button > "Projects tab" > and here see the new "Dispatch Password" setting.

You can now set a password (any combination), to control or protect if a user wants to use the option "Unlink" on the Check Out window on the "Linked To Booking" option being shown, if this Check Out is linked/associated to a Booking.

After the new Dispatch unlink-password is set and the user now clicks on the "Unlink" option, a pop-up window will open to enter the password. If the password is entered wrongly a pop-up window will simply state: "Wrong!"

 

EMT

Added that you can now use the "Split Booking" on multiple-day Bookings functionality on Bookings linked to a Dispatch, see details.

See Details

To Split a multiple-day Booking, highlight the day or days (in fw Client > Hourline click on the date on top, or mark the days in the Long Form) you want the Booking to be split on > click on Booking menu > Split > Confirm.

 

Implemented to allow "Object Classes" to be moved to a new Dispatch, see details.

See Details

If you have configured equipment-kits in farmerswife with Object Class Accessories and need to create a new Dispatch from the original, it wasn't possible to move this Object with its Accessories. The option was greyed out. Now this works.

 
#323610

Added support for matching a Check In with its original Check Out, when this Check Out was not linked to any Project or Client and was only including Virtual Objects, see details.

See Details

farmerswife was before not able to match a Check In with the original Check Out when using the option to “Check In From Selected”, if the Check Out was not linked to any Project or Client, and if it was only including Virtual Objects that were set to be "expected to be returned".

Even though, the returned Virtual Objects were correctly checked back-in and the stock was updated. But the original Check Out Status was still showing these items as "Dispatched", instead of "Returned".

With this fix the original Check Out Status is now correctly set to "Returned".

 
#329880

Fixed a bug that was wrongly causing that the setting “Ignore Accessory Rates” was affecting Virtual Objects, see details.

See Details

If the setting “Ignore Accessory Rates” was set to Yes, when you booked a Virtual Object and selected a quantity higher than 1, only the first one would show a rate, and the other Objects shown in the cascade menu would wrongly show 0.

This has now been fixed, as this setting is meant to only affect Accessories to an Object.

This bug was also affecting the Project Print Designer, which was also showing the Rate for the first Virtual Object and ignoring the rest - in this case, regardless of the setting mentioned above being enabled or disabled.

 

Fixed a bug where Accessories as Object Classes wrongly lost their link to a main Object, see details.

See Details

Fixed a bug where Accessories as Object Classes wrongly lost their link and thus lost their connection whether those Accessories had a Parent or were Children to a main Object.
This showed itself e.g. in the Long Form > Projects tree and Viewport area, where on the Booking the "expand details" triangle icon would not work. This is now fixed.

 

Financial Report

Added "Incoming Invoice Totals" to the "Budget Detail" and "Rows" section, see details.

See Details

The "Rows" section and the "Budget Detail" Grouping have a field called "Incoming Invoice". It contains fields such as Supplier, Name etc. But it was missing "Totals" and "Line Totals".

Now the following fields have been added:
- Total Excl. VAT
- Total Incl. VAT
- Line Total Excl. VAT
- Line Total Incl. VAT

 

Fixed a bug in "From Class Booking > Involved People > Object Ref", when grouping by "Ref" wrongly only the "Primary Class Ref" was shown.

See Details

The field "From Class Booking > Involved People > Object Ref" didn't respect all "Ref" related features, such as "Inherit Ref from Object Class". Now it does.

 

Fixed a crash bug when reporting on Budgeted lines and grouping by Month.

 
#327724

Fixed a rounding problem in currency/money fields, see details.

See Details

As part of rounding for display, certain values were affected by lack of precision in the so called "Double-precision floating-point format". This is now fixed.

 
#327763

Fixed bugs in "Force Bookings Into Separate Days" setting and broken "Mix Dates" setting of the Financial Report Generator, see details.

See Details

On the Financial Report window, the "Force Bookings Into Separate Days" and "Mix Dates" settings both cause each day in a Booking to be split up into a different row, e.g. making the rows suitable for grouping by Month. However, they both had bugs preventing correct behavior in some cases. Those bugs are now fixed.

 
#319399
#322975

Fixed incorrect "Sell Rate (Budgeted)" for Global Budget Operators, see details.

See Details

When you added a Global Budget Operator to a Budget, and then showed the "Sell Rate (Budgeted)" field for it in the Financial Report, it would show the wrong value. It wrongly contained the Sell Rate from the last Budget Detail. That is now fixed.

 
#325847

Fixed incorrect rounding on "Sell Rate (Budgeted)" field, see details.

See Details

There was a bug making the "Sell Rate (Budgeted)" field round values when it shouldn't. E.g. "500.50" to "501.00". Now it preserves those decimals.

 

Frameworks

#328384

Fixed a bug wrongly causing "Frameworked Booking Into Next Day" and "Time / In Out (Override)" to not work; both issues are fixed.

 
#329497

Object Notes on a Framework Cell are now correctly being copied along, when saving the Framework into a Binder and re-applying this Binder, see details.

See Details

Before, when after applying a Framework Binder the Object Note on a Framework Cell would appear in a mouse-over of the cell. However when trying to edit this Object's Note, it was wrongly not possible. Now this has been fixed.

 

GUI

Increased the "Customs" height on the Edit Booking windows to accommodate "grab" on Mac 64bit fw Client.

 

General

#329251
#327553
#324789
#325837

Fixed a bug by which the option "Change Project / Media Order / Task" via the Booking menu was not working on Windows, and legacy Mac-32bit.

 

Fixed a bug when "Week Start" is set to Sunday, that now Friday and Saturday are again correctly colored white, see details.

See Details

Places where the day color was wrongly still white on "Saturday & Sunday" instead of on Friday & Saturday: Display, Hourline, Date Widgets, Calendars.

 
#328955

Fixed a potential fw client crash (on fw legacy Mac 32bit) introduced in latest changes on the cirkus-integration changes.

 

Fixed a Windows-only bug, wrongly causing the "open url function" from not working correctly, see details.

See Details

That the "open url function" was not working correctly caused on the fw Client desktop app, that in "Menu" these two items did not do anything, now they work again:

- "farmerswife Help" - will open the installed default web browser on this page: https://support.farmerswife.com/support/home

- "Open WebCal Index" - will open the installed default web browser on this page: http://UrlToServer:LegacyHttpPort/webcal/index.html

 
#328738
#328489
#329007

Fixed a potential fw Client crash when creating Bookings (Windows only) due to low-level clicking-support issue on Windows.

 

Hourline

#322844

Fixed a fw Client crash when opening Personnel events via a fast double click in the Hourline or modifying by opening the Booking and changing times.

 
#330184

Fixed a potential fw Client crash when creating a Booking and only happening some Windows environments in some scenarios with fast click-actions.

 

Installers

#327690

Fixed a bug wrongly causing the 32bit fw Client desktop app on Windows from launching, showing in the error message "can't find package json".

 

Invoice Report

The "Ref" field now respects the booked Object Class, see details.

See Details

When the setting "Inherit Ref From Object Class" (in fw Server > Setup > Financial tab) is activated, each Booking Object's Ref should be taken from their Object Class. The problem was that this was always taken from the Primary Class and didn't change depending on which class you actually booked. But from now on it will.

 

Invoicing

Added support to be able to select what Dates To Include in a Credit Note, see details.

See Details

When you create a Credit Note there is now an option to select what dates should be included in the Credit Note.
Highlight and right click on an Invoice in the Invoice Manager > there’s now an option to "Make Credit Note From Date Range".
farmerswife (fw) will look at any line item from the Invoice that match the selected dates and add these lines to the Credit Note.
If the Booking had the setting "View Class Booking As Separate Days" ON, only the days that match the selected dates will be included in the Credit Note.
If the Booking had the setting "View Class Booking As Separate Days" OFF, and the first Date of Booking matches the Selected Date Range; ALL the days of that Booking will be included in the Credit Note, because fw doesn't treat all the days in a multi-day Booking as individual, unless the "View Class Booking As Separate Days" is switched ON.

 

Long Form

Fixed a bug by which when creating a Booking there was a random fw Client crash only on Windows depending on mouse events in some scenarios.

 

Media Orders

Added the possibility to create Media Order Job names and color, and also to be able to search on these via the "Advanced Project Search", see details.

See Details

It is now possible to create predefined names and colors for Media Order Jobs.
To help in those situations where you need more information about a Media Order Job than what is possible with the current Status (Not Done/In Progress/Not Done) and Note.

1) Setup: In fw Client > Toolbox > Settings > Server Setup > "Media Order Job Names" button.
2) Select: When adding a Media Order Job (Media Order Object) inside a Media Order > Select the Name from the list to show the Name and associated Color or Type.
3) View: In fw Client > Module bar > Projects (a.k.a. "Advanced Project Search") > Filter From: "Media Orders".
Then use in the sub-menu > "Media Order Search Fields" > Options > "Edit Search Fields" and ensure "Job Name" and "Job Status" are on the right side "Selected" pane.

Then to display the search results, use in the same sub-menu"Edit View" > and to then select "Media Order / Job Name" to display the column in the search results panel.

Note: ONLY When adding the "Media Order/Job Name" column will farmerswife automatically display the search results as a list of Media Order jobs, rather than the Media Order as a whole. That means, if you have a Media Order with 3 Media Order jobs in it, the search results would show 3 lines, one for each Media Order Job in the Media Order.

 

Notifications

#327936

For the "Notifications" added option to "Apply To All Projects", see Details.

See Details

With this new option you can configure / modify the "Global Notification Defaults" and then "Apply To All (existing) Projects"; go to fw Client Toolbox > Settings > Notifications > new "Apply To All Projects" button.

This is useful if you want to configure a new option and apply to all Projects. Until now, you would have to manually enable the new option in every Project through the Eye Menu > Notifications.

 
#327843

Fixed a bug wrongly causing email Notification of Ad-Hoc-Timereports to be sent, see details.

See Details

Fixed a bug wrongly causing email Notification of Ad-Hoc-Timereports to be sent for every Project, even if Notifications on Ad-hoc Timereport creation was not enabled.

 

Object Browser

Fixed a fw Client freeze bug caused by a "grab" issue in the Object Browser.

 

Object Classes

#309881

On the new "Object Class Ranking" adjusted the trash icon to fully show when deleting an Object Class Ranking from the Object Class, see details.

See Details

How to setup the Object Class Ranking:
In fw Client > Object Manager > open an Object Class and click on the drop down menu in-front of one Member of the Object Class > Ranking > Setup Rankings.
The "Setup Rankings" window opens > click on the green plus icon to add a new Ranking.
The Ranking can be sorted by click and holding and pulling it up and down in the list or by clicking on the blue sorting arrows.
To delete a Ranking, grab it and drag and drop it into the Trashcan icon which pops-up when dragging it left or right.

 

Object Importer

Added a new option for the "Import / Export farmerswife Objects Format CSV" file to easily create and update "Day and Sell" based Activities, see details

See Details

In fw Client > Object Manager, it was already possible to import new Activities via the CSV file by adding an additional row under an Object and indicating it was "Type Activity". Similarly, you could update an Activity by adding changes on the corresponding row of the exported CSV file.

Now, a new option has been especially designed if you need to apply or update several Sell prices/Rates on long lists of equipment, by displaying "Activities" on columns (rather than rows). This can be used on other scenarios as well; bare in mind it ONLY allows adding and updating the "Sell Rate" on "Days" per Activity.

The Activities you wish to apply on new Objects must exist on the database.

How to create new Activities:
1. In fw Client > Object Manager > first open just one of the Objects or Classes you need a new Activity. On the "Modify" Object pop-up window click on the "Advanced" button, and then on the "Activities" pane use the sub-menu "New Activity". Then set a Name and ensure you are setting a value in the "Sell Rate" field and that it is "Day"-based.

2. Next, choose the Activities that will get created as columns on the CSV file. In fw Client > Object Manager, click on the menu > “Import / Export farmerswife Objects Format CSV” > “Activity Day Sell Columns” > tick only the Activities that you wish to get on the CSV file as columns.

3. Click on the menu again > “Import / Export farmerswife Objects Format CSV” > un-tick the option “Import/Export Activities” to avoid getting the Activities also showing as rows below each Object they belong to (as now they will show as columns).

4. Export the Objects or Classes where you wish to add these new Activities.

5. The CSV file shows each of the Activities ticked as per step 2 as separate columns starting on column F.

6. After you modified the Day-Sell-Rate for each Activity on the corresponding cells, and Import the CSV file back, the Activities with a value will get added to the corresponding Object. Those cells that are left empty will not create the Activity on the corresponding Object when imported back.

How to update existing Activities:
If you only need to update the Day-Sell-Rate of existing Activities, then you just export the Objects or Classes where these Activities exist and update the corresponding cells - without changing any options mentioned above.

But should you need to change anything else on these Activities, other than the day-sell rate, i.e. add a Buy Rate or change the Activity’s icon, then first enable the option “Import / Export Activities” mentioned on step 3 above, and un-tick the Activity mapping from the option “Activity Day Sell Columns” explained on above step 2.
As you export the CSV file, the Activities will be populated as rows below each Object they belong to, as usual.

 

Objects Tree

#309881

Removed the mouse-over info of the "Object Class Ranking" if Objects were loaded into the Long Form > Objects tree, see details.

See Details

If an Object Class has set "Object Class Ranking", the members can be assigned a ranked order. This Ranking will show in a yellow mouse over in the fw Client > Long Form > Objects tree if the Class is loaded to the Objects tree.

Before, it wrongly also showed the Ranking if the User/Object was loaded by itself into the Object tree, resulting in confusing information, as one User could be part of various Object Classes and thus have different Rankings in each of them. So the mouse over info was giving false information. This mouse-over info has now been removed. The mouse over of an Object Class Ranking will now correctly only show if the Object is loaded via the Object Class to the Objects tree.

 

Pop-up

#328491

Fixed a bug where the "New Binder" pop-up window didn’t pop up, this affected the fw Client on Windows and the legacy 32bit fw Client on Mac.

 
#329992

Fixed a bug for the Binder Pop-up and "Show Options In A List" that was not working correctly on some Windows 10 using the fw Client 64bit version.

 

Print As PDF (fw Client side)

Added native support for "Effra Font Family".

 

Print Designer

Fixed a bug in the new "SUM(...)" operator with certain Financial Reports/fields.

See Details

Some fields in some Financial Reports were not recognized by the new "SUM(...)" operator.

 

Fixed a bug when adding Page Breaks within the "Total" section, this was wrongly causing a fw client crash.

 

Fixed that "multiple selection" (via "lasso" drag&drop and via "cmd+click" on Mac or "ctrl+click" on Windows) works again in the Print Designers.

 

Printing

#330625

Added fixes for Print Designer "Background Images" caching that was causing errors while printing in some environments, see details.

See Details

- Now farmerswife will clean the fw Server-side "Background Images" cache if an unexpected error occurs while generating the cache.
- Added a new setting in fw Client > Toolbox > Settings > Server Setup > ”Use Image Caching For Printing” check-box to enable/ticked (by default) or disable/un-ticked the "postscript" cache.
- Fixed a bug by which the cache file "cache_bg_postscript.fw" was not being regenerated if removed.

 
#328756

Added native font support for "NittiGrotesk".

 

Made the new fw Server-side postscript cache deactivation apply immediately for the fw Client desktop app, see details.

See Details

Made the new fw Server-side postscript cache deactivation apply immediately for the fw Client desktop app; so no fw Server app restart required anymore for this setting to get applied!
Before it was applied on fw Server-side only and required a fw Server restart to apply to the fw Client desktop app.

 

Fixed a Windows crash caused by the previously used external library to "Scan Fonts" and replaced it with improved and faster native way to "Scan Fonts".

See Details

Replaced the external font scanning library with a native font scan method.
This was needed to solve problems with slow font scanning and occasional crashes during fw Server-side "Scan Fonts" on windows.
Now the scan process is also much faster!

 

Fixed a bug when batch printing "Group Templates" and on the internal stitching of the single PDFs some temporary pdfs were not being deleted.

 
#330625

Fixed a bug wrongly causing that the option in PD Template > Setup > "Default Printer" was in conflict when using the legacy fw Client 32bit and the new fw Client 64bit (Windows/Mac), see details.

See Details

Fixed a bug when using the legacy fw Client 32bit and the fw Client 64bit (Windows/Mac) the option in PD Template > Setup > "Default Printer" was in conflict, because the "Built-In Printer" is not available on the legacy fw Client 32bit. The fw Client 32bit app now uses its legacy Printer support again.

 
#330258

Fixed an issue with "Open Sans" font when scanning fonts and added native support support for fonts "Apercu" and "Sequel Black 100".

 

Improved the Background Images cache trying to make the memory consumption to be acceptable, see details.

See Details

Background Images cache is still needed to speed up printouts with Background Images.

NOTE:
Previously used but deprecated "cache_bg_postscript.fw"get removed and instead this is used: "cache_bg_img_postscript.fw"

 
#327617

Improved the memory usage when generating the new postscript > "label_images" cache for the first time.

See Details

After the new postscript > "label_images" cache is created for the first time (this happens only if image files as .gif or .png are present within the fw Server's "label_images" folder within "system"), a new file called "cache_bg_postscript.fw" will be located within the fw Server's "system" folder.

 
#326864
#328362

Re-added support for batch printing PM Reports and Travel Expenses on Windows with network-mapped "User" folders.

 

Disabled "Postscript Cache" on Linux as it was causing a bug when using "Background Images" on Print Designer Templates.

 
#329834

Fixed a bug causing a fw Client crash when printing "Group Templates" PDFs from the legacy Mac 32bit app.

 
#326864

Added support for "Windows Roaming Profiles" and "Folder Redirection" for the users "AppData" folder.

 
#329009

Fixed a bug happening only on some Windows 10 environments where the %WINDIR% var is wrongly lowercase, wrongly causing blank PDFs.

 
#326864

Fixed a bug where PDFs were not generated correctly (empty + ps file) on Windows when the "APPDATA" folder is network path, see details.

See Details

This was to address a problem in networked Windows environments where the user’s APPDATA path was a remote network location.
This caused problems on the read process of the Fontmap.GS file, and because the fonts could not be read the PDF was not generated correctly. Instead a .ps and empty PDF file was created.
This is now solved and the remote APPDATA paths are now handled correctly.

 
#330625

Fixed a bug wrongly causing PDF printing to fail on Windows where the OS Username was separated by a space.

 
#327095
#327729

Fixed a bug wrongly causing blank PDFs on some Windows OS installations where the environment variable "windir" is wrongly uppercase.

 
#326864

Fixed a bug wrongly causing the fw Client app from printing on network paths on Windows.

 

Project Window

#327172

Added a new filter by "Booking Global Status" to the "Filter String" feature in the Edit Project window, see details.

See Details

It was already possible to filter Bookings by a certain string of characters on the Edit Project window > magnifying glass icon "Filter String". The new added option now allows to also filter by "Booking Global Status", i.e. the different Booking Statuses that you can customize.

 

Project and Dispatch Report PD

Added new element "Object Has Children" to be able to distinguish an Object that is booked as an Accessory and in-turn it also has its own Accessories, see details.

See Details

This new element "Object Has Children" is added to the "Element Row" in the Dispatch Report and the Project Report Print Designers. This element can be used together with a previously added element "Object Has Parent". By combining these two elements with various String Operators, it is possible to distinguish a main/parent Object from its Accessories (children), and the Accessories of the Accessory. Imagine the case where you book an Object that has a number of Accessories, and some of the booked Accessories has their own Accessories as well.

Suggestion for String Operators:
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 that do not have any Accessory of their own:
Compare what: "Object Has Children"
How: Equals
With: No
Return: Input
Else Return: Nothing

 

Purchase Orders

More types of PO (Purchase Order) lines can now have "Unit" type, see details.

See Details

Inside the "Edit Purchase Order Line" dialog you could only select between Hours, Days or Fixed if the Object was of type User, Room, Machine, Other, Resource or Object Class.
At the same time you could add e.g. a User as a "Booking Extra" which is expressed as Units. And then you could raise a PO from that Booking.
Now the dialog also supports Units for these Object types.

 
#327059

Fixed a fw Client crash when opening Purchase Orders from the Edit Project window.

 

REST Api

#317478

Implemented fw REST API improvements, fixed bugs and updated the documentation, see details.

See Details

- It is now possible to filter Projects by name, case insensitive and accents free.
- Implemented to remove Bookings by using the method DELETE in the "/event" endpoint using the request body: { "bookingID": "idxxxxxxx" }.
- Changed for the Project Number to be represented as "string".
- And for Bookings/Events it is now possible to filter by data from Booking Custom Fields by using asterisks "*", so it's now possible to search also in multiline fields, e.g: *mysearch* .
- Added two new "container" endpoints: "POST /container" and "PUT /container/{containerID}" making it possible to now create "Project Containers" by using the fw REST API. Once you have created a Container, you then need to use the endpoints "POST /project" or "PUT /project" in order to link an existing Project with an existing Container.

The "swagger.json" documentation file is now also updated, and is now on version 0.7, available here:
https://support.farmerswife.com/en/support/solutions/articles/17000089578-the-farmerswife-server-s-rest-api-for-your-own-3rd-party-integrations

 

Scheduled Invoices

#328617

Fixed a bug wrongly causing to not be able to edit Scheduled Invoices from some Projects.

 

Server Setup

Fixed in fw Server > Setup > General > "Pre-Login Message" where the actual message field was wrongly hidden.

See Details

And it now also no longer wrongly sticks to the bottom of the canvas when scrolling vertically within the General tab.

 

Time Report

#327440

When adding Extras to the Timereport, the note added to an Object Custom field with label name "Timereport Note" will be copied to the Extra’s Note, and you will be able to edit it, see details

See Details

Use this option if you need to display some details about a Service, Material or Expense, and at the same time have this note available for editing when the Extra is added to a Booking.

Create an Object Custom Field with label name "Timereport Note" and apply the template containing this custom field to all of those Extras (Services, Materials and Expenses) for which you need to add some details or conditions etc.

When you add one of these Extras to the Timereport, this note will be copied over to the Extra's Note (accessed via the Extra's menu in the Timereport window > Edit), for you to amend if needed.

 
#328099

Fixed on the legacy Mac 32bit fw Client that the "Time Report Note" "All Days" and "Day" fields do not overlap the "Extras" buttons.

 

Timeline

Fixed a fw Client crash bug when double clicking on a Booking when using in fw Client > Toolbox > Settings > Hourline > "Open Bookings On Single Click".

 

fw-cirkus integration

Fixed a character encoding issue when using non-standard Latin in farmerswife and when syncing farmerswife Projects to cirkus.com, see details.

See Details

Non standard Latin characters would return as symbols in various pop-ups in farmerswife and also when syncing fw Projects with cirkus.com.

 

iOS WIFE app

Added new barcode-scan support for the built-in Camera to be used for batch scanning items, see details.

See Details

On the latest iOS fw app v5.0.840 > Dispatch > Add Item > notice the new camera icon in the top right corner. Then tap on it to start scanning barcodes of items in your farmerswife system.

NOTE: In order for this to work, you need to allow the iOS fw app to have access to your iOS device's camera.
And the iOS fw app needs to be on Version 5.0.840 or later (on the App Store since:

IMPORTANT:
And in order to scan Media, the "Media Library" or "Media Management" option needs to be licensed.
And in order to scan Objects, the "Equipment Management" (EMT) option needs to be licensed.

 

Previous Releases

#19322

20. May 2020

6.6 SP 1

#18918

28. Jan 2020

6.6 Release