Back To Release Notes List



Back To Release Notes List
Release Notes For {{RELEASE_NAME}}

7.0 SP2

Build: 7.0.1002-0-g83a6af59e

  • 1 Warning
  • 0 HOT Features 0 Features
  • 5 Other changes
  • 23+ Bug fixes

Welcome to v7.0 Service Pack (SP) 2 - please see the "Details" below each chapter in this "top" section of the Release Notes.


v7.0 SP2 Release was built on 18. October 2023.
And it was released on 25. October 2023.

Native v7.0 changes:
- 1 Warning: v6.8 was the last version to support the "32bit" apps for fw Server and fw Client, warning info was added.
- 0 HOT Features - try the New "Dark Mode"!
Get started on Dark Mode: https://support.farmerswife.com/en/support/solutions/articles/17000129606-dark-mode-for-7-0
- 0 Features
- 5 Important Other change
- 23+ Bug fixes

See the changes specific to this version: https://www.farmerswife.com/releasenotes/RN-70/SP-2/

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

----------------------
v7.0 SP1 Release was built on 2. August 2023.
And it was released on 7. August 2023.

Native v7.0 changes:
- 1 Warning: v6.8 was the last version to support the "32bit" apps for fw Server and fw Client, warning info was added.
- 0 HOT Features - try the New "Dark Mode"!
Get started on Dark Mode: https://support.farmerswife.com/en/support/solutions/articles/17000129606-dark-mode-for-7-0
- 0 Features
- 2 Important Other change
- 15+ Bug fixes

See the changes specific to this version: https://www.farmerswife.com/releasenotes/RN-70/SP-1/

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

----------------------
v7.0 Release was built on 23. June 2023
And it was released on 28. June 2023.

Native v7.0 changes:
- 1 Warning: v6.8 was the last version to support the "32bit" apps for fw Server and fw Client, warning info was added.
- 9 HOT Features including the New "Dark Mode"
To get started on using Dark Mode: https://support.farmerswife.com/en/support/solutions/articles/17000129606-dark-mode-for-7-0
- 61 Features
- 28 Important Other changes
- 115+ Bug fixes

See the changes specific to this version: https://www.farmerswife.com/releasenotes/RN-70/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 v7.0": https://blog.farmerswife.com/farmerswife-release-v7.0

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

Upgrading to fw v7.0 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 7.0" license at hand, before starting the upgrade process.
- To be eligible for a v7.0 license you need to have a valid support subscription (Gold or Silver) with us past the public release of this version.

IMPORTANT:
Upgrade your farmerswife (fw) system from v6.8 Service Pack 3 rev. 20627 or from 7.0 Release and later!
If your farmerswife system is still running on older versions than v6.8 SP3, 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.

VERY IMPORTANT:
v6.8 was the last version to support the "32bit" apps for fw Server and fw Client!

Any fw Client app on Mac running BELOW macOS Mojave 10.14 can no longer be used! You have to upgrade the Mac to macOS Mojave or later in order to use the latest fw Client desktop app on Mac.

The built-in "Full Installer download" farmerswife (fw) Client auto-upgrade is active on macOS and Windows!

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.

Installers Download:
https://farmerswife.com/installers/public-installers/

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, then 6.6 SP2, then 6.7 SP1 and finally 6.8 SP3.
- 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.7 SP1: https://support.farmerswife.com/en/support/solutions/articles/17000121336-upgrade-instructions-6-7-sp1
=> 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 Java OpenJDK version 11 installed on the fw Server app host machine, for the Web Client and Mobile Web Client to work properly and in the most secure way.
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 version your farmerswife Server host Mac is running on!

IMPORTANT:
macOS 10.14 Mojave is the only macOS on which both the legacy "32bit" and the current "64bit" fw Server installers will work!
When upgrading from fw versions below v6.8 on macOS ensure your Mac host computer is running on macOS 10.14 Mojave!

- 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 7.0 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:
- 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 v7.0 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.9 Beta fw server.
- macOS (Mojave, Catalina, Big Sur, Monterey and later) fw clients will perform a full install when they first connect to the upgraded v6.9 Beta 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.

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.873 is available on Apple's App Store, click on "+" to see the details!


The latest iOS farmerswife app is v5.0.873 and it's available on Apple's App Store since 6th-October-2023.
IMPORTANT: Requires iOS 13.4 or later.

And since v5.0.840: Added new barcode-scan support for the built-in Camera on the iOS device to be used for 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.
Requires farmerswife v6.1 SP1 rev 16195 and later versions!

This means:
You should upgrade as soon as possible to the latest released version.
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/STAGE 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 "close as possible" 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 fw 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
LDAP_DEBUG
HTTP_DEBUG
EXCHANGE_DEBUG
MAIL_DEBUG
BARN_ACTIVE
APNS_ENABLED
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
A5_ENABLED
A5_URL
A5_KEY
A5_SECRET
CIRKUS_ENABLED <= This is from the legacy "Cirkus Sync v1" integration and this should always be disabled on any farmerswife system!
FORCE_SHUTDOWN
USE_MSAZUREAD
USE_THREADS
BACKUP_TIME
FULLBACKUP_CYCLES
FULLBACKUP_TIME
HTTP_HOME_ADD_WEBCLIENT_PORT
CRK_ENABLED
CRK_ORG_ID
CRK_URL
CRK_READONLY
CRK_BOOKING_SYNC_ENABLED
CRK_TR_SYNC_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
PRJ_CHECK_FOLDERS 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.

Installers

v6.8 was the last version to support the "32bit" apps for fw Server and fw Client, warning info was added, see details.

See Details

v6.8 was the last version to support the 32bit apps both for the fw Server app and the fw Client app, on Windows and macOS.

Also fw Client-side platform info in fw Server logs when logging in was added.

The "Warning" pop-up message states:
"You are using the 32b it version of the farmerswife client application. Support will stop by the end of 2022. Please contact support@farmerswife.com or your System Administrator to upgrade to a working system."

On the fw Client 32bit app title bar:
"Support for the 32bit app will stop by the end of 2022".

 

Advanced Project Search

The "All" field in the main module bar > Projects now searches for Container Name as well.

See Details

The main module bar > Projects is also called "Advanced Project Search" or APS.

 

Azure Active Directory

#359830
#361080

Fixed multiple Azure AD issues and added improvements, see details.

See Details

Added a new optional server.cfg flag: USE_MSAZURE_LOGS 0/1 to write in a separate system log file, more info about Azure Requests and sync process steps.
Use only during troubleshooting.
New created log files are located within the fw Server app's "system folder called:
-customlog.msazuread.log
-customlog.msazureadthread.log

Fixed performance issues to improve the sync time and main thread processes that were blocking the fw Server app.

Implemented performance improvements on querying Groups, by implementing MS Graph API $filter param in Groups to get straight from the api only Groups matching names or ids.

Added an error message for users starting a sync process when another sync process is still running.

 

Bookings

#361394

Fixed a bug when splitting a Booking, it wrongly removed the Timereporting, see details.

See Details

On a multiple-day Booking, some days were time-reported. When you then "Split" the Booking, no matter what day, it would wrongly remove all the time-reported info from the previous reported days. This is now fixed.

 

Budgeting

Fixed a bug causing a wrong Rate to get used when adding an Object or Object Class to a Budget when the Activity Rate was "0".

 
#341919

When copying & pasting Budget Details, the Discount is now also copied, see details.

See Details

You can copy/paste Budget Details by selecting them and using the right-click menu.
However, that would previously ignore any manually set Discounts on the Details.
Now it will copy/paste the set Discount as well.
Note that this happens even if you copy/paste the Detail across Budgets or even Projects.

See more info here:
https://support.farmerswife.com/en/support/solutions/articles/17000023636-creating-a-quote-and-budget

 

Cirkus Sync

Fixed a bug failing to map farmerswife Resources with empty First/Last Name, see details.

See Details

When it syncs farmerswife Resources to Cirkus Resources it does so by comparing their exact names. If the names match, the Resources is considered to be the same.
However this didn't work properly when the farmerswife Resources had an empty First Name or Last Name.
This bug is now fixed.

 

Fixed a bug mapping in-active Users/Resources between farmerswife and Cirkus, see details.

See Details

When it syncs farmerswife Users/Objects to Cirkus Users/Resources it does so by comparing emails or names.
However, it would also do so for *in-active* farmerswife Users/Objects, and depending on their creation dates those in-active Objects could sometimes take priority over their active counterparts.
From now on it will fully ignore the in-active ones.

 
#359845

Fixed force-sync issues on Bookings when using "Forget Sync" on Projects, see details.

See Details

When you use "Forget Sync" on a Project and then activate sync again for it, it's supposed to force-sync any existing Bookings to Cirkus.
This only worked partially, and did not update the Project reference on the Cirkus Bookings. Now it will.

 

Implemented to prevent adding in-active People and Objects to Cirkus, see details.

See Details

In the Object Manager, you can right-click on people and objects, use Cirkus > "Add To Cirkus".
This was also possible on people/objects marked as Active = No, potentially causing problems and confusion during the sync.
Now when trying to add inactive people/objects to Cirkus, it will show an error dialog and won't add them.

 
#357717

When creating new Projects in farmerswife, it no longer blocks the user while syncing, see details.

See Details

When you created a Project in farmerswife, it would show a blocking dialog saying "Saving Project..." while it synced the Project, along with any other pending changes, to Cirkus. This could sometimes take a significant amount of time, and for little reason. Now farmerswife will avoid that blocking and instead sync the new Project to Cirkus in the background, on the scheduled interval (e.g. every 10 seconds), just like it syncs other changes.

 
#359845

When moving farmerswife Bookings across Projects, it now also updates the Project in Cirkus.

 

Container

#359912

Fixed a bug which prevented a new Project being created from within the Container window

See Details

Users are able to create Projects within Containers. However, when users were trying to create Projects they were being blocked, and the Project's mandatory fields were being greyed out. This has now been fixed, and Users can create new Projects from within Containers.

 

Financial Report

#360816

Fixed a bug related to Bookings with "Fixed" unit, causing items to wrongly count double.

See Details

There was a recent fix related to Bookings with Fixed Price.
That fix caused a new Bug in Bookings where individual line items have a Fixed unit.
The Bug would make the other items in the Booking count double. This is now fixed.

 
#357263

Fixed a bug where Unit Names were wrongly not being translated in Financial Reports, see details.

See Details

If you were using the fw Client desktop app in another language in "Settings > Language", the Unit Names would wrongly not be translated in the Financial Reports.
This is now fixed.

 
#360064

Fixed a fw Server app start-up error when the setting in fw Client > Toolbox > Settings > Server Setup > "Use Threading for Financial Reports" was enabled.

 
#358349

Fixed a fw Server-side error when using "Mail And Mark As Sent" on an Invoice using a Financial Report Template.

 

Hourline

#336388
#348853

Fixed a fw Client app crash on creating/changing Bookings for Projects that have a Budget and the "Auto Attach Actuals To Budget" setting Active.

 

Invoice Creator

#334170

Fixed the search in the "Part Invoice" ("Active Projects") pane, wrongly not showing all relevant results, see details.

See Details

The issue on finding all results was, because if the search term was cropped off from the name of the Booking (too long to display) then it couldn't find that Booking. This is now fixed.

 

Personnel Bookings

#360935

Changed the "Set "All Day" as default when creating Personnel events" setting to not apply when there are Bookings on that day, see details!

See Details

Since v7.0 there's a new setting in fw Client app > Toolbox > Settings > Personnel Tree > "Set "All Day" as default when creating Personnel events".
The behaviour now slightly changed when there are Bookings on a day and you are going to create a Personnel Booking on top.

When setting is OFF:
1) Dragging timeframe in the Hourline (HL) -> Sets Time In/Out to dragged timeframe.
2) Dragging Object onto day with no Bookings in HL or Long Form (LF) -> Sets Time In/Out to default 09:00-18:00.
3) Dragging Object onto day with Booking in HL or LF -> Opens Conflict window and sets to 09:00-18:00.
3) Clicking on icon in LF on day with no Bookings -> Sets Time In/Out to "All Day".
4) Clicking on icon in LF on day with Booking -> Sets Time In/Out to Time In/Out of Booking.

When setting is ON:
1) Dragging timeframe in HL -> Sets Time In/Out to "All Day".
2) Dragging Object onto day with no Bookings in HL or LF -> Sets Time In/Out to "All Day".
3) Dragging Object onto day with booking in HL or LF -> Opens Conflict window and sets to "All Day".
3) Clicking on icon in LF on day with no bookings -> Sets Time In/Out to "All Day".
4) Clicking on icon in LF on day with booking -> Sets Time In/Out to Time In/Out of Booking.

 

Project Window

#361233

Fixed a fw Client app crash when opening some Projects with negative Discount in a Price Agreement.

 

Projects

#360879
#361911

Fixed a bug that prevented a new Project being created via a Contact in Toolbox > Contacts, see details.

See Details

Fixed a bug that prevented you from editing Project fields and thus being unable to make a new Project via the fw Client desktop app > Toolbox > Contacts > select Client Contact > right mouse click > New Project From: xxx.

 

REST Api

#357059

Removed trailing space in "GET /event", see details.

See Details

When a Personnel Event was "All Day", the "dateTimeInAsString" and "dateTimeOutAsString" values had a trailing space character. That is now fixed.

 

Rates

Fixed a bug when using "Replace With Available Class Member", causing it to keep Rates even if you select not to, see details.

See Details

There was a fix introduced in farmerswife v6.5, making it more often keep Rates of Objects when replacing.
However, that fix ignored the existing "Do You Want To Keep The Old Rates?" dialog, so when you selected "No" in the dialog it would still keep the Rates.
Now it will respect the dialog, and the setting in fw Client app > Toolbox > Settings > Class / Object > When Replacing Keep The Class, Activity And Rates: No/Yes/Ask.

 
#361542

Fixed a bug where the "Unit" from Budget Details was wrongly overwritten to "Hour" when modifying it in the Edit Project window, see details.

See Details

If you set the "Unit" of a Budget Detail to "Fixed" and then forward the Detail to the Actuals View, when editing the Detail in the Project Actuals View the Unit would change to Hours. Now it states "Fixed".

 
#360383

Fixed wrong values displayed in Buy/Sell fields on Project Extras for Task Users, see details.

See Details

Task Users are able to edit Buy and Sell Rates of Extras (Material, Service, Expense) added to the Edit Project window. However when editing the Rates, the Buy Rate would show "r.et" and the Sell Rate as 0.00. This is now fixed and the Extra's correct Rates will show and can be edited by the Task User who added the Extra.

 

Server Database

Added fix for duplicate Booking IDs, see details.

See Details

The "Force Check Database" button in fw Server app > Setup > General tab now checks for another type of data problem in Bookings.

 

Web Client

#360230

Fixed the Date picker in the Web Client which showed wrong days of the week when the previous month has different timezone to the current one, see details.

See Details

In the Web Client, dates would be inconsistent when looking at November 2023. In the main window 1st November was Wednesday (correct), but in the Calendar Selector 1st November was Thursday. Now the bug is fixed.

 

Web Visibility

#360422

Fixed a bug wrongly causing the Project "Web Visibility" > "Binders" configuration to get lost when sorting Binders in the Long Form > Projects tree.