Back To Release Notes List

Back To Release Notes List


24. Aug 2022

6.8 SP 1

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

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

v6.8 Service Pack (SP) 1 Release rev. 20580, was released 24. August 2022.

Native v6.8 changes:
- 1 Warning: Added "Warning" pop-up messages when launching a 32bit fw Client app and on the app title bar after login.
- 5 Features
- 4 Important Other changes
- 23+ Bug fixes

See the changes specific to this version:

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

... and also take a look into the new highlights summary of the most recent Released version "Whats New in v6.8":

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

v6.8 Release rev. 20523, was released 8. June 2022.

Native v6.8 changes:
- 1 Warning: Added "Warning" pop-up messages when launching a 32bit fw Client app and on the app title bar after login.
- 12 HOT Features
- 56 Features
- 40 Important Other changes
- 57+ Bug fixes

See the changes specific to this version:

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

... and also take a look into the new highlights summary of the most recent Released version "Whats New in v6.8":

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

Upgrading to fw 6.8 SP1 Release and later - see details!

- You need to have a "Version 6.8" license at hand, before starting the upgrade process.
- To be eligible for a v6.8 license you need to have a valid support subscription (Gold or Silver) with us, at least up to 8. June 2022 or later.

ONLY upgrade your farmerswife (fw) system from v6.7 Service Pack 1 rev. 20130 or later!
If your farmerswife system is still running on older versions, ensure you upgrade the fw Server application as per the must-do upgrade steps; contact should you require further assistance.

The fw-Client-AutoUpgrade functionality is ACTIVE in certain scenarios.

The built-in "Full Installer download" farmerswife (fw) Client auto-upgrade is active on:
- the 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.

- 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 and finally 6.7 SP1.
- 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 since v6.6 Release:
=> Upgrade Instructions v6.8 ... these have been updated for 6.8 SP1 Release:
=> Client Installation Mac:
=> Client Installation 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:

farmerswife Server upgrade on Mac:

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

macOS 10.14 Mojave is the only macOS on which all fw Server installers will work!
The macOS "64bit" farmerswife_Server will work ONLY on macOS 10.14 Mojave, macOS 10.15 Catalina, macOS 11.6 Big Sure, macOS Monterey 12.4 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.8 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:
- Quit the running farmerswife Server.
- Now copy the new v6.8 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, Big Sur or Monterey) 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.8 fw server.
- macOS (Mojave, Catalina, Big Sur or Monterey) fw Clients will perform a full install when they first connect to the upgraded v6.8 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 running a macOS version earlier than Mojave, or a Windows 32bit, or Linux your fw client apps will NOT upgrade automatically!
Use these direct download links for the farmerswife Client desktop application installers ... allow below links are pending to be updated for the Release of v6.8:

macOS 10.14 Mojave & macOS 10.15 Catalina & macOS 11.6.5 Big Sur & macOS Monterey 12.4 "64bit" fw Client:

macOS Legacy 32bit Mojave or earlier fw Client

Windows "64bit" fw Client:

Windows Legacy "32bit" fw Client:
=> Support will stop end of 2022!

Linux "32bit" fw Client: Please contact 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; 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.861 is available on Apple's App Store, click on "+" to see the details!

The latest iOS farmerswife app is v5.0.861 and is available on Apple's App Store since 19th-August-2022.
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 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.857; it requires iOS 13.4 and later (ideally you're always using the latest iOS version).
Version 5.0.59 requires iOS 7 or later. This is the iOS 7 optimized version.
For iOS 6, the latest iOS farmerswife app is still version 5.0.34.

IMPORTANT for older versions:
The latest v5 universal iOS farmerswife app for iOS 7 or later: v5.0.59 is available on Apples App Store since 12-September-2014.
Your WIFE Server needs to be at least on version 6.1 SP1 or later to use iOS farmerswife app version v5.0.59 and later.

Running a separate TEST WIFE Server

This chapter describes the recommended best practice on working on and with a separate TEST farmerswife (fw) Server system.
This might be needed when running on Beta versions, or new Service Packs or in general when you first want to run an upgrade check, or evaluate new modules or new functionality on a separate TEST fw Server environment.

You can always use a fw Server app in "Demo Mode" (also with your database (DB) files) and it will run for 60 min. and you have 40 sessions.
An additional "TEST fw Server" license can be provided upon request, available for customer with a valid service agreement in place;
include in your request the Company Name, the info of the local static IPv4 address and the used Operating System of the machine to host the TEST fw Server.

farmerswife supports Push and Feed functionality, and various other email notifications (if enabled); and it can be integrated to various other 3rd party systems; and you can also break out folder structures to network shares which are normally locally hosted on the fw Server's host machine, etc.
All this functionality is therefore also enabled by default on a separate new TEST fw Server environment you might be using. And if not handled with care and turned OFF in a good way, this will lead to duplicate or wrong notifications to your users, or update wrong information on your real live Production farmerswife system.
Please read on.

For a "half way realistic" test environment, copy the "system" folder from your fw PRODUCTION Server, more info below!
Depending on how you use farmerswife, you might also need to copy other files or folders.

Use the "server.cfg" file to control certain vital parts of your separate TEST Server:
This "server configuration" file (server.cfg) provides the option to change certain "General tab" settings "outside" of the actual fw Server application.
You use this file to ensure certain settings are NOT enabled on your TEST fw Server BEOFRE it gets started.

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

PASSWORD_POLICIES_SRC default_password_policies.json

These are additional settings/variables not set by default:

Since v6.4 these two settings/variables are special, because on a "standard" and "not externally proxied" fw Server installation, both of these MUST have the SAME port value!

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

Note: Only licensed features and their variables will be effected by any changes within this .cfg file.

A proper fw Test installation works like this:

- Quit your farmerswife PRODUCTION Server.
- Create a file called "server.cfg" within your PRODUCTION fw Server's "system" folder.
- Start up your PRODUCTION fw Server for the first time with the "server.cfg" file in place, then Quit it again, to trigger flushing your existing configuration settings into this "server.cfg" file.
- Install the TEST fw Server application on your test machine.
- Now copy at least the "system" folder from your fw "production" Server to within your "test" fw Server's installation folder. If you have the time, feel free to also copy the "files" folder; and if you have customized anything within the "html_templates" or "/lib/scripts/...", copy these sub-folders, and IF you are using anything "customized" within these folders, the related files might need to be copied as well.

BEFORE (!!!) the first start-up of the TEST fw Server, edit the server.cfg file with a text editor application within your TEST fw Server's "system" folder and add or set at least these variables to "0", like this:

Save the server.cfg file. Copy it again to a "safe" location on your test machine, so you can re-use it for the next DB file updates. Please read on.

Now start your TEST fw Server application.

VERY IMPORTANT after the first launch and after each update of database files of a separate TEST Server
Go to the running fw Server application > Setup > General tab > "Full Backup Time" and set it to "Never"!
The "server.cfg" does not yet support this feature, and if you do not turn it off, this might interfere with your actual real "Full Backups" from your "in-production" farmerswife system!

NOTE: to test "Allow Mail" functionality from a "test" fw Server, you can use for example a service like "Mailtrap" (
You then need to update this variables with your access details:

Repeat the above steps, for any upgrade or repeated update of the "system" folder on your Test fw Server.
We recommend to save the correctly configured "server.cfg" file for the TEST environment in a good way, and then simply replace it prior to the first start-up.

NOTE: Once you have properly configured your TEST fw Server as described above, you can save time in the future by only copying these files from your PRODUCTION fw Server > from within the "system" folder:
- 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.


Added "Warning" pop-up messages when launching a 32bit fw Client app and on the app title bar after login, see details.

See Details

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

The "Warning" pop-up message for the fw Client 32bit app:
"You are using the 32b it version of the farmerswife client application. Support will stop by the end of 2022. Please contact 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"

On the fw Server app (both 64bit and 32bit versions) you'll see this info on the first log-line on the fw Server app's Log: window and on the fw Server app's log.txt:
On 6.8 Release:
"Running: farmerswife Server 6.8 (Support for the 32bit app will stop by the end of 2022) (Rev: 20523)"
On 6.8 SP1 Release:
"Running: farmerswife Server 6.8 Service Pack 1 (Support for the 32bit app will stop by the end of 2022) (Rev: 20580)"


Azure Active Directory


Azure AD multiple fixes for MS Graph API, see details.

See Details

Fixed fw Client crash when using fw Client > Toolbox > Settings > Server Setup > MS Azure Active Directory Connector > Setup > "Test" button.

Fixed some wrongly not populating important "Properties":
- Phone Direct
- Phone Mobile
- And fixed in fw Server app > Setup > Users > Microsoft Azure Active Directory Connector > "MS Azure Extension Attribute ID To Import User Number" to correctly populate the data again.


Booking Templates


Fixed a fw client crash when renaming a copied Booking Template.


Cirkus Sync


When a Project is created in Cirkus, the Number field is now populated from farmerswife, see details.

See Details

When you create a Project in farmerswife, the auto incremented Project Number is synced to the corresponding Cirkus Project.
But when you created the Project in Cirkus instead, the Number field in Cirkus remained blank even though the corresponding farmerswife Project got an auto incremented number.
This is now fixed by syncing back farmerswife's Project Number to the Cirkus Project.
Note that after creating the Cirkus Project, it can take a moment before it updates with the new Project Number.


When syncing Binders, it no longer sends out notifications, see details.

See Details

When farmerswife creates a Subproject in Cirkus, it can cause a notification to be sent out to all Project Members in Cirkus.
Since the sync can often cause Subprojects to be created in bulk, this can lead to an excessive amount of notifications and put a strain on the Cirkus servers.
To reduce that server load, this operation will no longer cause notifications to be sent.


Fixed a bug where it wrongly logged "Disabling Cirkus Integration (v1)" even though it wasn't enabled.


Fixed an error when syncing Binders with empty names.

See Details

In farmerswife, Binders can have an empty name. But in Cirkus, Subprojects are not allowed to have empty names.
So when syncing unnamed Binders, it would cause a repeated sync error.
Now it will instead call the Cirkus Subprojects "(Untitled)".


Fixed bugs caused by failed Binder/Subproject sync, see details.

See Details

In certain conditions, when one Project's Binders/Subprojects failed to sync, it could cause a loop in a different Project, where Subprojects were first created and then removed, created again, removed again, etc. etc.
That bug is now fixed.


Fixed sync errors for Bookings after deleting their Projects in farmerswife.

See Details

If you:
- Synced a Project between fw and Cirkus.
- Deleted the Project in fw.
- Created new Bookings for the Project in Cirkus.
...then it would cause errors in the log and prevent other Bookings (in other Projects) from syncing.

Now it will detect that the Project is deleted and stop syncing those Bookings.


If a Project fails to sync on creation, it no longer keeps trying indefinitely.

See Details

If anything prevented a Project from being created in Cirkus, farmerswife would just keep trying and trying - even if the error was permanent.
Now it will stop syncing that Project until you open it up and click on the error icon in order to clear errors and retry.



Added Active/Closed filter on the new "Container" tab in the Toolbox.


Financial Report


Fixed List Price in Budget Reports doesn't get actual rates on Service/Expense when forced unit name is Day / Days, see details.

See Details

Services that have "Day"/"Days" as the Unit Name, will now show the correct List Price from the Rows loop of the Financial Report Print Designer. Previously having the unit price as "Day" / "Days" would wrongly show the List Price as 0.00.


Fixed the Currency symbol being displayed instead of the Currency Code when Multiple Currencies are disabled.


Invoice Creator


Fixed the Currency symbol being displayed instead of the Currency Code in the Invoice Creator line items.


Labour Rules

Added generating of bi-weekly working periods, see details.

See Details

In the Edit Rule window, next to the working periods chart, there are now two new options:
- Set Periods > Every 2 Weeks (Starting Mon)
- Set Periods > Every 2 Weeks (Starting Sun)


Fixed a bug causing overlapping events to be wrongly counted double as worked hours, see details.

See Details

When counting Worked Hours for Labour Rules, farmerswife flattens any overlapping events so that each hour is only counted once.
However this didn't work if events were of different types.
So overlapping Bookings worked fine, and e.g. overlapping Shifts worked fine, but as soon as you mixed overlapping Bookings and Shifts, it could count time double during the overlapping time.


Fixed inconsistent worked hours when Tasks overlap other events, see details.

See Details

When different types of events overlap in the schedule, the Worked Hours calculation in Labour Rules will "flatten" the schedule so there is only one event at every point in time. This is so that overlapping events won't count double towards the worked hours.
But because Tasks don't count as worked hours, this meant that if a Task got priority over e.g. an overlapping Shift, then it didn't count as work. And if the Shift got priority, it did count as work. So the result wasn't always consistent.
Now it will always prioritize events that count as work, such as Shifts.


Media Orders

Fixed a bug wrongly causing that the Media Order Date widget was not inheriting the value from the linked Project.


Mobile Web Client

Fixed a bug in the Mobile Web Client causing empty screen when editing a Booking and searching to add an Involved Object.

See Details

When a user wanted to edit the Booking in the Mobile Web Client and add Involved Ob ject, searching them under "Search" or "Categories" was empty and not giving any option to actually find any Objects.
Now the bug is fixed and returning search results correctly.


Object Report


Fixed Object Report doubling Total Buy/Sell if Object is added twice to the same Booking, see details.

See Details

When an item was added twice to the same Booking, in the Object Report Total Buy/Sell would be wrongly doubled.
Now the bug is fixed and Totals sum up correctly.




Fixed a fw Client crash when opening the Modify User window without "Can See/Modify Rates" permissions, see details.

See Details

When a user had the permission to create and modify Objects in the Objects Manager, but at the same time had no permission to see and modify Rates, it would cause a fw Client app crash when opening the Modify User window in the Object Manager.
The bug is fixed now and users with no rate permissions can open the Modify User window without any issues.


Print Designer


Helvetica font fix when using Print As PDF, see details.

See Details

Printing to PDF in New Rendering Mode was converting the Italic Helvetica font to Bold Italic on PDFs. This fix is to correct this issue, so that Italic Helvetica comes through to the PDF as Italic Helvetica.


Project Binders


Fixed a crash that happened in some circumstances when moving a Framework Binder using > Move Start Date From Calendar.


Project Report


Fixed a bug for Price Agreement info not showing on Project Reports, see details.

See Details

In v6.8 we've added 2 new fields in the Reports > Row section, that would allow to display Price Agreement Name and Price Agreement or No Price Agreement info. Those fields were not pulling properly in Project Reports, which is now fixed.



Fixed wrong am/pm time format in the fw REST Api, see details.

See Details

The fwRESTapi will now always convert "time" information into the 24h-timekeeping-system according to ISO 8601 time format.

This means, it does not matter if in fw Server app > Setup > General > Time: ... the format "21:00" or this format "09:00 pm" is being used. Time relevant results via the fwRESTapi will now always be displayed in the 24h-timekeeping-system according to ISO 8601 time format.

For this change to apply, your farmerswife system needs to at least run on 6.8 nightly rev. 20572 or later.

There is no "swagger.json" version update needed for this change to take affect.
The latest sagger.json version is still 0.8.9.


Rate Cards


Fixed a bug where the Rate from a Rate Card was not applied, if it was set to 0.00, see details.

See Details

Before the fix, 0.00 rates would never get applied after doing "Force Apply" in the Rate Card.
Now Rates will be set to 0.00 when hitting Force Apply, but only if the 0.00 Rate comes from an Object in the Rate Card.


Schedule Changes Email


Added a new "Static Time Frames" option in Web Share Settings so that Schedule Changes Emails will be sent, if "Static Viewable Timeframe" is set to the past, see details.

See Details

Some farmerswife systems need to hide future events from the schedule for some users.
This can be achieved with using the "Static Time Frames > Viewable" to be set to the past.
But until now, this also prevented "Schedule Changes Emails" to not get sent.

Now a new check-box setting was added, called "Use Web User's Viewable Static Time Frame" and is is located in the fw Client > Toolbox > Settings > Web Share Settings > External Calendars / Schedule Changes Email Sendout / XML ..." section.
This new Setting is enabled/checked by default, to ensure the standard behaviour of the "Schedule Changes Email Sendout" functionality is persevered.

If you now un-tick this new setting "Use Web User's Viewable Static Time Frame", then another new Setting called "Static Time Frames" gets displayed. Select here the period for which the Schedule Changes Email can be send out, independent of the "Static Time Frames > Viewable" configuration.


Fixed even more low-level places on the "External Calendar, Schedule Changes Email Sendout, ..." process, wrongly causing errors when internally joining strings containing an odd number of double quotes.



When re-timing Shifts, it no longer shows a conflict dialog, see details.

See Details

When you moved a Shift so it overlapped a Booking, there was a dialog asking if you want to remove the Object from the Booking. And if you pressed No, it failed due to conflicts.
At the same time, the conflict dialog didn't show when you added a new Shift.
As it can be useful to have overlapping Shifts and Bookings, the conflict dialog is no longer used when moving Shifts.



Changed to allow type "Task/Booking" users to change the "Keep Class, Activity/Rates" setting in the Toolbox.

See Details

Advanced Users who are type "Task/Booking" can now edit the "When Replacing Keep The Class, Activity And Rates" setting in the Toolbox.


Web & Mobile Client

Added "Enabled" setting for Booking Colors in Web Share Settings, see details.

See Details

In v6.8, new Settings were added in fw Client > Toolbox > Settings > Web Share Settings, to control the Booking Colors in the Web Client and on the iOS fw app.
This caused the previous color behavior to change, and it was hard to update the settings in a way that brought back the old behavior.

Now a new "Enabled" checkbox has been added at the top of fw Client > Toolbox > Settings > Web Share Settings > Booking Colors. Un-checking it will almost bring back the old color behavior, with the exception that "Use Container / Project / Client Colour" will no longer apply. That setting existed before fw 6.8, but it makes most sense to disable it together with all the other Booking Color settings when they are disabled.


Web Visibility

Changed "Start Date" in German from "Eingangsdatum" to "Startdatum" to fix overlapping text in the Web Visibility window.




Added new setting "Hide User Number / Other In The Web Client, iOS and Mobile Web Client" and implemented it on the Mobile Web Client, see details.

See Details

Go to fw Client > Toolbox > Settings > Web Share Settings > "Hide User Number / Other In The Web Client, iOS and Mobile Web Client: Yes / No (default)" check-box.

This functionality is supported on the iOS fw app since v5.0.861.


Previous Releases


03. Jun 2022

6.8 Release