Back To Release Notes List



Back To Release Notes List

#19322

20. May 2020

6.6 SP 1

  • 1 Warning
  • 5 HOT Features 17 Features
  • 12 Other changes
  • 33 Bug fixes

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

Native v6.6 Service Pack 1 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

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

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/

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

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

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/

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

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

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/

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

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

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

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

... 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 SP1 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.5 Release rev. 18623 or later!
Ideally you upgrade from v6.6 Release rev. 19819 to v6.6 SP1.

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. 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/support/solutions/articles/17000026002
=> Client Installation Windows: https://support.farmerswife.com/support/solutions/articles/17000026003

- 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.4 Mojave and macOS 10.5 Catalina and 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 or Catalina) 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 SP1 fw server.
- macOS (Mojave, Catalina and later) fw clients will perform a full install when they first connect to the upgraded 6.6 SP1 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 "64bit" fw Client: https://www.farmerswife.com/downloadsWeb/fw_client_v606_SP1.dmg

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

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

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

The latest iOS farmerswife app is v5.0.838 and is available on Apple's App Store since 20-May-2020.
IMPORTANT: Requires iOS 12
And due to iOS 12 requirements for new submitted apps, this will result in the previously working 3rd party external barcode scanner support to no longer 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.828; 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

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

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

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

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

A proper fw Test installation works like this:

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

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

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

Now start your TEST fw Server application.

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

NOTE: to test "Allow Mail" functionality from a "test" fw Server, you can use for example a service like "Mailtrap" (https://mailtrap.io).
You then need to update this variables with your access details:
MAIL_OK
MAIL_SERVER
MAIL_PORT
MAIL_USER
MAIL_PASSWORD

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

NOTE: Once you have properly configured your TEST fw Server as described above, you can save time in the future by only copying these files from your PRODUCTION fw Server > from within the "system" folder:
- current45.efdb
- fwdb.db3
- histories.db3
- despatches.db3
- log.txt

... and "paste" into your TEST fw Server's "system" folder and "replace" the previous files. Then rename the fresh "log.txt" to include "date-of-copying-yyyy-mm-dd_InitialsWhoCopied_log.txt". This helps on keeping track.

About these Release Notes, Disclaimer and Legal Information

The content of this Release Notes document is subject to change without notice. The information in this document is furnished for informational use only and should not be construed as a commitment by farmerswife. farmerswife assumes no responsibility or liability for any errors or inaccuracies that may appear in this document or any software that may be provided in association with this document. Except as permitted by such license, no part of this document may be reproduced, stored in a retrieval system, or transmitted in any form or by any means without the express written consent of farmerswife.

Installers

fw Client Desktop app - Full-Installer-download ACTIVE on 64bit fw Server installers on Windows and macOS Mojave and later, see details.

See Details

The new v6.6 64bit fw Server installers on Windows and Mac support the auto-upgrade for the fw Client app in certain scenarios:
- on Windows
- on macOS 10.14 Mojave and macOS 10.15 Catalina and later

... by either using the "Full-Installer-download" auto-upgrade process - always on macOS Mojave and later - local user Operating System Read, Write & Execute permissions are required.

... or for already installed "64bit" fw Client apps on Windows only: the simple "in-application-auto-upgrade" is supported.

For users on Mac BELOW macOS Mojave, on old Windows 32bit computers and on Linux:
The fw Client installers have to be manually downloaded and installed on each upgrade.

 

ActiveDirectory

#325177

Implemented "LDAPs" support for the Microsoft Active Directory integration, see details.

See Details

To enable the secure connection via "LDAPs":
Go to the running fw Server application > Setup button > Users tab > and yes in the "Microsoft Exchange Integration" section the new "SSL" button.
And you'll also then need to change from the legacy Port "389" for this connection, to the correct LDAPS port "636".

 

Budgeting

Fixed bug preventing Day based rates in Rate Card after using "Forward Actuals To Budget Details"

See Details

If you used "Forward Actuals To Budget Details" to create a Budget Detail, and then "Add Budget Rates To Project Rate Card" to update the Rate Card with it, the line added to the rate card would not have a Day rate, even if the Budget Detail did. This is now fixed.

 

Cirkus Sync

Added possibility to open Project in Cirkus app when clicking on the Cirkus icon on the farmerswife Project

See Details

If Cirkus setting "Open Links in Installed App" is enabled, clicking on the Cirkus icon on the left side of the Edit Project window in farmerswife will open the Project in Cirkus app. Otherwise it will open it in Cirkus web.

 

Class Bookings

Added rounding on Booking with "View Class Booking As Separate Days".

See Details

When you activated "View Class Booking As Separate Days" on a Booking, it sometimes resulted in a different Sell Total than before it was activated. This was because rounding of subtotals are suddenly performed for each day in the Booking.

Now it will attempt to automatically round the last day in such a Booking, such that the total matches the "original" Booking total, i.e. the total it would have without "View Class Booking As Separate Days" activated.

This also fixes the same issue in Financial Reports with "Force Bookings Into Separate Days" set.

 

Client

Removed text "NO QUICKTIME" from Client window

 

Contacts

Fix Error on opening Contact Window

 

Custom Fields

A Custom Field type Selector with "Allow Multiple Selection" = Yes, will now display the selection in the order it was selected, see details.

See Details

Previously the selected items would display in the order they appeared in the list, rather than the order they were selected in as it does now.

 

Now it is possible to remove Project Global Custom Fields from all the places where they were added, see details.

See Details

Project Global Custom Fields are set up in Toolbox > Settings > Server Setup. When they are set up the custom fields will exist through all Project related booking levels, from Booking Object, Booking, Framework Class, Sub Binder, Binder and Project.
They serve a special purpose for clients who have Navision integrations to be able to capture and export data.
If you had created some custom fields here by mistake, now it is possible to remove them completely from all the projects, bookings, etc, where the fields were added.
To remove go to: Setup Project Global Custom Fields (in Toolbox > Settings > Server Setup), open each Custom Field created in and click Remove from within the Custom Field window.
Next, as you click OK on the Project Global Custom Fields window, you get prompted “ Do You Want To Also Remove: 'custom field name 1', 'custom field name 2', ... From Bookings, Projects, Etc.?”
Click Confirm for the custom fields you just removed so they are removed from all existing project, bookings, etc.
If you click Cancel, they will not be removed from existing projects, bookings, etc., but they will not be added to any new projects, bookings, etc.
You can still later on remove the custom field, by creating it again with the exact same name and then when removing also choose to remove from bookings, project, etc.!

 

Fixed a bug causing Booking Custom Fields configured as Entry > Finders wrongly not return any results.

See Details

On Booking Custom Fields, configured as Entry Type with Finder, available values/results would wrongly not be returned when typing.
Now, with provided fix, it works as expected. As soon as user starts filling in the Entry Field (Finder), he gets the suggested results.

 

Day Chart

New Day Chart Report and Daily Day Chart Email Sendout with PDF

See Details

Day Chart is a new report created from the Hourline that displays the Objects on the horizontal axis and time on the vertical axis. The time is displayed by hour, for example 7:00-8:00, 8:00-9:00 etc. This report can also be sent as a daily email which is enabled in the Toolbox > Settings > Web Share Settings and added to the Web Permission Profile for relevant users.

CONFIGURE THE DAY CHART REPORT
To configure Day Chart Report click on the Hourline Icon > Day Chart.
The report includes:
1. All Objects from the selected Hourline View (displayed horizontally)
2. Selected Timerange (displayed vertically)
3. Selected Columns of the following categories: Name (=Project Name) Client (=Company name), Custom Fields and Involved Matching Object Classes. The default report includes Project Name and Client Company Name.

Setup is done within the Print Designer window:
Click on the Options button in the bottom left corner to open the Setup window.
In the Setup window click on the green plus icon in the upper left corner to select what columns to include from the list, to remove click on the bin icon.
A line with three sections is added. The first section is the name that will be displayed in the report column header, you can edit this name. The second is the width of the column, you can edit the width. The third shows the category, this cannot be edited.

When adding Involved Matching Object Classes you will see one line with the Involved Matching class and underneath the name of the Class and a green plus icon. This makes it possible to select multiple Object Classes to be displayed within the same column. This is when it comes in handy to change the name column header to for example Involved. So if you for your Hourline Object that is on top have one booking with an Editor and another with a Sound Engineer in the same Suite at different time, the names of the Objects will be displayed in the same column. If there are more than one involved Objects in the same Booking only the first Object in your setup will show.
If the booking starts at 10:30 and ends at 11:30 it will show in both slots: 10:00-11:00 and 11:00-12:00. If two bookings overlap, the report will show first booking it finds.

Note: The font size cannot be changed.

CONFIGURE DAY CHART DAILY EMAIL SENDOUT WITH PDF
To enable the Daily Day Chart Email Sendout you need to go to the Toolbox > Settings > Web Share Settings.
Select the update time of Daily Day Chart Email Sendout. The email will be sent once a day with the plan for the next day.

Next define which Saved Hourline Report should go to which Web Users. This is done in the Web Profile Manager per Web Permission Profile.
Select Web Permission Profile and in the Event’s thread find the button “Daily Day Chart Email Sendout” and select define Hourline Views (one or multiple) from which the report should be generated and sent as an attachment to the Users.

The email title is: Day Chart for <Week Day Name> <Date> <Hourline View Name>.
To be able to send this email, all the pre-requisites must be filled in:
Pre-requisites:
1. Configure Outgoing Mail Server Settings
2. Setup the PDF Printer (it's needed for those notifications that need to send attachments).
3. Enter email addresses in Users and Resources Profiles

 

Dispatch Module

Dispatch window: Allow to sort single items in the Dispatch module, see details

See Details

You can now sort the items in Check Out and Check In by drag and dropping them above or below each other. Please note, this functionality won't work if you have Objects setup with Accessories or Groups. If you have Virtual Objects in the Check Out that are grouped, once you sort those, the cascade menu will be lost, but you can still sort them in a different order.
The sorting will reflect itself in the Dispatch Report.

 
#326531

Improved the Dispatch Notification Email Subject when using Danish, see details.

See Details

It is now possible that the Notification Email for Dispatches can be sent out with Danish text within the Email Subject for any changes on a Dispatch (Check In or Check Out).

To enable the Danish language support the fw Server application has to be set to use "Danish" via fw Server > Setup > General tab > "Language" setting.
For this Dispatch Email Notifications further more the "Allow Mail" needs to be configured and the "PDF Print Export" settings have to be enabled and configured correctly; both of these settings are within the fw Server's Setup.

In the fw Client application the following settings need to be enabled in fw Client > Toolbox > Settings tab > Dispatch Module:
- "PDF Notification Email Print Template".

Then any of the following needs to be enabled:
- "Allow Sending Email And Push Notifications On Status Changes To Dispatch Contact"
- "Allow Sending Email And Push Notifications On Status Changes To Dispatch Pickup Contact"
- "Allow Sending Email Reminder To Pickup Contact When The Dispatch Has 24Hrs left".

Each time a Dispatch Status is changed and set from "Prepared", set to "Ready", "Dispatched" or "Declined" and/or "Returned" an email will be sent out to the "Dispatch Contact" or the "Pickup Contact", depending on which setting was enabled.
If a general overview is needed, also please set the "Notification Email Include / From Email Address" setting, which will then receive a copy of all emails sent by the Dispatch Module.
These Notification Emails will also be triggered by the "EMT" add-on module "Mac Kiosk".

 

EMT

In the Project and Dispatch report it is now possible to differentiate the main item from its accessories, see details.

See Details

Added to Project Report > Element Row Loop and Dispatch Report > Element Row Loop "Object Has Parent" (Yes/No) to be able to differentiate main objects from its Accessories and vice versa in the Reports.

This is used if the main item should be shown in bold whereas its Accessories should show in normal font.
With the help of the String Operator main Objects can be shown separately from their Accessories.

Take the D[Name] field copy it and use the String Operator: String Compare:
IF "Object Has Parent equals Value: No Show Input. Otherwise show Nothing --> this will show only the main Object (parent object) and it can be shown in bold. Rename this field to "main object" or "parent object".

Take the copied D field and name it Accessories and use the String Operator: String Compare:
IF "Object Has Parent" equals Value: Yes Show Input. Otherwise Show Nothing (this is achieved by clicking on Value and cancelling that field again --> "" those two fields will show.

 

Now a Group or an Object with Accessories added through a Checkout directly, shows in cascade in the corresponding Booking involved window, see details.

See Details

Please be aware that a complicated setup of a Kit either being an Object with Accessories or a Group won't be reflected the same way when adding to a Checkout.
A Group or Object with Accessories might have as a "child" an Object Class that again has Accessories. This can't be shown, if added directly added to a Checkout.
On Checkins any Accessory by default won't show as it needs to be scanned in.

 

Object Manager: It is now possible to print out QR Codes from the Object Manager Report, see details.

See Details

For the "Inventory Number" of each Object in the Object Manager it was already possible to display this as a barcode by applying a "barcode" font via the Object Manager Report Print Designer. This Report is accessed via the Report icon in the right upper corner of the Object Manager window. Now you can also access this Report by doing a right mouse click or by using the sub-menu button in the left upper corner and select > Reports.

In the "Objects" section of the Report you now have 3 options of QR Codes available:
- Inv. QR Code (large)
- Inv. QR Code (medium)
- Inv. QR Code (small)

For a better printing experience you will need to add a Rectangle from within the Objects sections and place it before the QR Codes to separate them visually, otherwise they will be shown glued together. The rectangle is available through the green plus icon next to the beginning of the "Objects" section.

It is not necessary to have a QR font installed.

 

The Object's Booking from a closed Project will now be extended if a Check In was made for that Objects after the Project was closed

See Details

Before, if an Object was returned via a Check In the Booking Object's time line would only extend to the Check In date if the Project was open. So if the Project was closed, the Object's Booking time line was not adjusted to the correct Check In date. Now it does and a yellow triangle indicates that the "Booking Has Override Time's Set".

 

Virtual Objects: If Virtual Objects are set up as an Accessory to a main Object the pop up: Type Amount For is disabled

See Details

If you book a Virtual Object you get a pop up window: Type Amount For and you can enter the amount of Virtual Objects you need to book e.g. 5 cables. If however this cable is added as an Accessory to an Object this popup window is now suppressed.

If the Virtual Object is member of a Group, this popup question will still be asked.

 

Dispatch Notification Email translated into Spanish

See Details

Set Server Language to Spanish to send Dispatch Notification Emails in Spanish.

 

Exchange

#326864

Implemented that MS-Exchange server calls are now threaded.

 

File Transfer

Fixed Files Transfer / Upload files that did not work correctly on macOS Mojave in Project window or Menu File Transfer

See Details

The files window which was hidden in the background was in focus but hidden, while the Project Window which was in the front but not in focus. You could only get focus back to Project window by clicking on escape, and thus escape from the Files upload window.

 

Financial Report

#322388

In the Financial Report the element Custom Field Booking Object > Name of Project Global Custom Fields will display first encountered value, see details

See Details

Project Global Custom Fields are set up in Toolbox > Settings > Server Setup. When they are set up the custom fields will exist through all Project related booking levels, from Booking Object, Booking, Framework Class, Sub Binder, Binder and Project.
They serve a special purpose for clients who have Navision integrations to be able to capture and export data. Each level can have different values entered in the fields. If you add a value in Project custom fields, you could add a different value in the Binder, Booking, Booking Object etc. If for example on the Binder the value entered is 1111 this will be the value for all objects belonging to Bookings within this binder. But if some of the objects should have a different value and this is added to the Framework class, then this is the value that should be associated with the Object. To be able to display this correctly in the Financial Report the element Custom Field Booking Object > Name of Project Global Custom Fields will search through all levels and display the value entered on the lowest level.
It looks upstream from cbobject > cb > sub binder > binder > project.

 

Fixed crash when grouping by Month and using Project Sell Price Operators.

See Details

In the Edit Project window you can add Sell Price Operators through the view menu's "Add Sell Price Operator To" item. These would not play nice with the Financial Report's new "Month" grouping, and cause a crash.

 

Fixed incorrect calculation when using "To Invoice" together with "Filter Lines In Range".

See Details

In the Edit Rates dialog for Booking Objects, if using Day rate, you can override the "To Invoice" amount. So for example a 10 day Booking can have "To Invoice" set to 5 days.
Typically this was also reflected correctly in Financial Report, but not when also using "Filter Lines In Range". Then the "To Invoice" value was wrong.

 

Fixed incorrect calculations when combining Global Project Discounts and Price Agreements.

See Details

At the top of the Edit Project window, there are discounts for each object category. When you activated these so they affected Booking objects that also had Price Agreements connected, it could result in incorrect calculations.

 

Frameworks

On the Framework menu a new cascade entry "Members" will show if number of available objects are 15 or more, see details.

See Details

The Framework menu is available when you click on a day in the Long Form timeline inside a Framework structure. Within this menu a list of available objects are displayed. If the available Objects are 15 or more the a cascade menu entry Members will be displayed which makes it easier to select an Object to allocate.

 

Fixed a bug where in some scenarios Framework Breaks were not set correctly to zero, see details.

See Details

In a scenario where you would highlight a few days and mark on Framework in the Project Tree and use the option (right mouse click) Binder Framework > Time In/Out (Override) > Set From Time Range > Set Break (Min) to 30, not for all selected days the Breaks were set correctly to 30 if on one day there wasn't any previous set Framework Break. This has now been fixed.

 
#325011

Fixed a crash bug when using in Long Form > Projects > Binder/Framework -> Time In/Out -> change time and press “OK”.

 

Framework Breaks: It is now not possible anymore to add a Framework Break on a Framework Cell that exceeds the actual Framework Booking time, see details.

See Details

Example: If a Framework Booking is set from 9-11h and you add a Break via the Change Start And Stop Time window that is longer than the 120 min of the actual Booking time a warning message "Break Longer Than Booking Time" will pop up. You need to select a lower amount of break minutes to be able to continue.
It doesn't matter if an Object is booked on the Framework Booking or if it is still empty.

 

GUI

#326297

Made Project Number field bigger

 

Made some fields bigger: Date fields, Rate fields, and some others.

 

General

Spanish language texts has been updated

 

Polish translations updated.

 

Hotkeys

Now possible to use Hotkey Financial Report functionality on no selection at all (Project, Object or User, Time Range) or a combination of them, see details.

See Details

It is now possible to run a Hotkey Financial Report using the Hotkey functionality:

- if there is no Project selected in the Project Tree. Now all Projects (except archived Projects) will be included when running a Financial Report. A warning will popup if one Project inside of the tree is archived: Some Projects Will Not Be Included In The Report Because They Are Archived.

- if there is no Time Range marked in the View Port (Long Form) - it will take all the time ranges of all Projects

- if there is no Object or User selected in their trees (it will run the report on all Objects (Users are Objects as well).

If in both trees Objects are highlighted farmerswife will prompt: Multiple Selections Exists. Choose Which To Use For The Report. It will also take into account if a Financial Report behind the Hotkey has Saved Filters set.


 

Objects tree: Released a wrongly kept selection when running a Hotkey on one Object that was removed from the Objects Tree, see details

See Details

You can run a Hotkey on a specific Object in the Objects Tree as soon as it is highlighted. When you remove the Objects, the Objects Tree will stay expanded (with the arrow pointing down) and it will say that it has (0) Objects in it. However this caused that the re-run of the Hotkey would still take the last Object that got deleted from the Objects tree and thus the outcome of the report was wrong. This is now fixed. If an Object is deleted from the Object Tree and it is active but empty the re-run of the Hotkey will run the report on all Objects as it is supposed to.

 

Invoice Manager

Fixed occasional email rejections when using the Send Invoice Email functionality, see details

See Details

When the Send Invoice Emails To was configured to Invoice Email, this email was always added to the CC in the email, which was sometimes causing email rejections. Now if Contact Email is empty the Invoice Email is added to the To field.

 

Long Form

Fixed a bug Class Availability tree, Fixed a bug for the "Class Availability" tree wrongly causing the setting "Hide Cancelled Projects From Timelines And Reports" to not work, see details.

See Details

In fw Client > Toolbox > Settings > Server Setup there is the setting "Hide Cancelled Projects From Timelines And Reports".
When ticked/enabled Bookings from Cancelled Projects will NOT appear in the Long Form > Objects tree (or in a Report). However the Bookings of those Projects were still counted on the "Class Availability" tree. Now if the setting "Hide Cancelled Projects From Timelines And Reports" is ticked/enabled the "Class Availability" tree will only count Bookings from Projects that are not Cancelled or Archived.

 

Notifications

Added Global and Project Notifications when an Ad-Hoc Timereport is created, see detail

See Details

With this new feature you can get notified, when AdHoc Timereports are created by your users.
You can enabled it in:
1. Global Notifcations
2. Project Notifications by checking the option "On AdHoc Timereport Creation".
When it is enabled, you will get the email informing you Ad Hoc was created, showing you Project Name, User, Time & Date of Ad Hoc TR.

 
#326002

Fixed a bug wrongly preventing to disable Dispatch Module > "PDF Notification Email Print Template", see details.

See Details

The now fixed bug wrongly caused, that in fw Client > Toolbox > Settings > Dispatch Module > "PDF Notification Email Print Template" it was possible to set "Don't Send Notification Emails". But this settings change wrongly did not get applied or saved.

 

Object Browser

#324857

Selected Display columns in Booking Involved Object Browser is now saved, see details

See Details

Before when selecting to display columns in the Object Browser within the Booking window, the selection was not saved which meant that you would have to select the columns again.

 

Objects

Object's Accessories are now booked in the same order as they were setup, see details.

See Details

You can add Accessories to a main Object by importing it via the csv importer or by clicking on the Advanced button of Object. In the Accessories pane you can add Objects and Object Classes as being Accessories to this main Object.

Here an example:
Arri Alexa Premium Package - main Object
Accessory 1 = Arri Alexa Premium - Inv. number 123456
Accessory 2 = Monitor 17 " - Inv. number 34567
Accessory 3 = Zeiss Lenses (Object Class - so any Zeiss Lense can be taken that is available at the moment of booking it)

When booking the main Object Arri Alexa Premium Package all three Accessories will be booked now in the exact same order as they have been setup. Before the order was different when booking it.

 

PDF Printing (server side)

Fixed a bug wrongly causing the "Email Project Booking Report" to fail due to low level issues on the new Built-In Printers support for .gif and .png "Label Images".

 

PM User Report

Fixed Personnel Management User Reports batch printing

 

Permissions

Added Web Users To Object Permissions

See Details

So far it was not possible to add Web Users to Object Permissions.
When Object Permissions were enabled for Advanced Users, Web Users couldn’t effectively create confirmed bookings, as their actual status was always set to preliminary (due to object permissions).

It is now possible to add Web Users to Object Permissions.
It means that when Objects Permissions are granted for the Web Users, they can book objects via Web Client and both: Global Status and Actuals Status are confirmed.

 

Print As PDF (fw Client side)

Improved the "Print As PDF..." option, now saved in user's "Downloads" folder by default, see details!

See Details

The new setting that got added in 6.6, in fw Client > Toolbox > Settings > Misc. > “Ask For PDF File Path Where The Printout Will Be Saved”, is now defaulting to ~/Downloads ... , this is the User's Downloads folder.

But as the User browses to another folder, fw will now "remember" the last selected folder for the next print-outs.

This default folder also applies if the setting is off.

 

Fixed A4 page backgrounds problems due to not very precise postscript page size/dpi calculations

 

Print Designer

The "Split" String Operator now lets negative indexes pick elements from the end.

See Details

In the String Operator called "Split", there's a field called "Use Element With Index". Entering 0 here makes it return the first element, 1 means second, etc.
Now you can also enter negative numbers here, in order to pick elements from the end of the list. -1 is interpreted as the last element, -2 as the second from last, etc.

Example: If you split the string "A,B,C" on the character "," and "Use Element With Index" is -1, then it will give you "C" as a result.

 

Fixed crash when using "Split" String Operator with empty index.

See Details

When you created a String Operator of type "Split" but did not fill in anything in "Use Element With Index", it crashed. Now, instead of crashing, it will use element with index 0 by default.

 

Printing

Activating the Print Designer > Template setting “+ Font Scale” to be able to scale fonts in a template and affecting Print Designer Preview, and client/server printouts.

 

Fixed Batch Printing of Travel Expenses that was not printing the full selection

 

Fixed an error by which farmerswife was crashing when having issues when printing images

 

Improved font support in reports with a newly added option "Scan Fonts", and more fonts added to be natively supported, see details.

See Details

If you are using other fonts than your computer system fonts you could experience that your fonts do not display correctly in your print designer preview or on your printed PDF. If this happens you will need to use the Scan Fonts functionality. The default font if the selected font is not printed correctly will be Arial. We are continuously adding more natively supported fonts to farmerswife.

The “Scan fonts” allows farmerswife to correctly read the fonts you have installed on your client or server machine. In most cases, default system fonts will work without a scan. Fonts installed by the user, or custom fonts may not be possible to use by farmerswife until you run the scan.

Fonts are scanned on the farmerswife server and on the farmerswife desktop client.

Scan Fonts starts in three different ways
- Server automated font scanning: The server will perform a font scan if it detects that it previously has not performed a complete font scan of the fonts existing on the server machine.
- In the desktop client Toolbox you can start font scanning for both Server and Client. To start a scan for the server you need to have the User Permission for Server setup.
- Printing a PDF for the first time gives the possibility to select to scan fonts of the farmerswife client. The question will only be asked one time when printing from PDF.

To start the scan go to Toolbox > Miscellaneous > Scan Fonts;
Click on Scan Fonts >
1) Pop up if you have User Permissions for Server Setup you get a pop up question if you want to Start A Server Side Fonts Scanning Process? If you select Confirm you will start a font scanning both on the Server and the Client.
If you select Cancel or if you do not have the User permission for Server Setup, you get the
2) pop up question if you wish to Start a Client Side Font Scanning.
Select Confirm to start the font scanning. This will take some minutes so it is a great opportunity for a micro break.
- Print PDF: When you print a report for the first time and you have not already completed a font scanning you will be asked to Scan Fonts. You can select No, Skip Scan For Now, or Yes, Run Scan. If you skip you will not be asked again, but you can start the scanning from your Toolbox.

The font scanning process will maximum look at the 20 first styles of a font family of a true type collection, and will map the true type collection styles Regular, Italic, Bold and BoldItalic, which are the available options in the Service Pack 1 release. If you have templates where you in previous versions used other styles of the font family these will not print correctly for now.

Should you after the font scanning still not get the correct fonts printed on your PDF it is possible to map the fonts to the system by adding a fontmap.csv (with this exact name) to the server system folder. Contact support for help. There is an extended explanation below as well.

-------
For 6.6 SP1 we have extended support for the following fonts, Avenir, AvenirBook, AvenirNext, DejaVuSans, DejaVuSansMono, FreeSans, FreeSerif, NotoSans, NotoMono, UbuntoMono, UbuntoCondensed, AmericanTypewriter, GillSans, Montserrat, Roboto, DIN Alternate, DIN Condensed, Effra, Aller, Aller Display, Aller Ligth, Open Sans, PF Handbook Pro, TW cen MT, MetaPlusLining, Arial, BrandonGrotesque, Seed, AkzidenzGrotesk, TBDPost, BeausiteClassic, GTAmerica, Rosewood.

-------
Here is an extended explanation of how the fontmap.csv works, at least in most cases.

The fontmap.csv should be populated with a headline and a line with the specific font name and suffixes:
Headline: Font name,Regular suffix,Italic suffix,Bold suffix,BoldItalic suffix
Next line/s: the name of the font and the corresponding suffixes, also note that there are no spaces between the commas.

For the mapping you need the font postscript name. As an example the font name Gill Sans, will be displayed in your various font selectors as Gill Sans, with the space. The postscript name of Gill Sans is however GillSans, without any spaces.

For the fontmap.csv add GillSans in the position of the name. Next look for the postscript name of Gill Sans Regular. As GillSans Regular post script name is the same as the name ie GillSans, the regular suffix position ie the position after the first comma should be left empty. Next is the position of Italics; the PostScript name of Italic is GillSans-Italic. This means that you should add -Italic after the second comma in order for farmerswife to combine the font name GillSans with -Italic > ie to read it as GillSans-Italic.
Continue to fill in the rest of the spaces after each comma. Gill Sans Bold and Bold Italic follow the same pattern as Italic, so therefore we now complete the row as follows:
GillSans,,-Italic,-Bold,-BoldItalic
Note that the position of Regular is empty. In the fontname line you always need to include all 4 commas, even if you do not add any suffix to the position.

Finding the postscript name: In Mac it is easy to find it in the Font Book by showing the information view (i). In windows it is not easily available. Another way to find the postscript name is actually from your own computer. When you have completed the Scan Font procedure, what happens is that while executing the Scan Font the Fontmap.GS file is extended with the user installed fonts.

Path to find fw Server side Fontmap.GS on Windows:
C:\Users\Username\AppData\Roaming\Farmers WIFE Server\Fontmap.GS
Path to find fw Client side Fontmap.GS on Windows:
C:\Users\Administrator\AppData\Roaming\Farmers WIFE\Fontmap.GS
Path to find fw Server side Fontmap.GS on Mac (in Finder go to “Go” menu and use “alt/option” keyboard key and choose “Library”; this will result in this path:
/Users/Username/Library/Application Support/Farmers WIFE Server/Fontmap.GS
Path to find fw Client side Fontmap.GS on Mac (in Finder go to “Go” menu and use “alt/option” keyboard key and choose “Library”; this will result in this path:
/Users/Username/Library/Application Support/Farmers WIFE/Fontmap.GS

 

Performance improvement for pdf printouts using templates with page backgrounds, see details.

See Details

Now, the server will be for building the cache for image backgrounds/postscript when initializing, so the users will have faster printouts.

 

Project Window

Fixed a bug that would prevent the Object drop down menu of Involved Objects inside of a Booking to show when you opened the Booking in the Project Window

 

Projects Tree

In Long Form Projects Tree and Objects Tree it is now possible to swap or add an Object to multiple bookings at the same time. Added Key-shift support on Booking selection, see details.

See Details

Using SHIFT to multi select Bookings in Long Form > Projects tree:
In an expanded Project > Click on the first Booking needed in the selection > Hold down Shift on the keyboard > Click on the last Booking you want to include in the selection > All bookings between the first one clicked and the last will be selected. It is possible to select Bookings across multiple Binders. Only Bookings will Be Selected and not the Binders themselves.

Swapping an Object on multiple Bookings in Projects Tree:
Select the Bookings you need in the Projects Tree > expand at least one of those bookings on the down-arrow to reveal the Involved Object Icons > From Toolbox/Objects, Objects Tree or Hourline: Drag the Object you want to swap with and hover over the Object icon in the Booking til you see the Blue ‘swap’ arrows > Drop the Object > Dialogue: Apply To Multiple Bookings (xx) >
If Yes: Objects will be swapped on all the selected Bookings where applicable (If Involved Object is in the Selected Booking) (Note: The Set Class and Activity selector is disabled for Multiple Selection swapping)
If No: Dialogue: Confirm Replacing xx with zz > Confirm > Dialogue: Do You Want To Keep Old Activities And Rates >
If Yes: The Objects are swapped
If No: If the Object you are swapping with has more than one Object Class and/or Activities > Dialogue: Set Class and Activity selector > Select as needed > OK

Adding an Object on multiple Bookings in Projects Tree:
Select the Bookings you need in the Projects Tree > From Toolbox/Objects, Objects Tree or Hourline: Drag the Object you want to add and Drop it on the Booking > Dialogue: ‘Add: Object X’ > Dialogue: Apply To Multiple Bookings (xx) >
If Yes: Object/s will be added on all the selected Bookings
If No: Object/s will be added only to the Booking you dropped it on

Swapping an Object on multiple Bookings in Objects Tree:
Click on the Objects Tree Icon > Start Multi Selecting Bookings > Click on the Needed Bookings to select (or click to deselect) > Drag the Object you want to swap with on to one of the selected Bookings > Dialogue: Apply To Multiple Bookings (xx) >
If Yes: Objects will be swapped on all the selected Bookings (Note: The Set Class and Activity selector is disabled for Multiple Selection swapping)
If No: Dialogue: Confirm Replacing xx with zz > Confirm > Dialogue: Do You Want To Keep Old Activities And Rates >
If Yes: The Objects are swapped
If No: If the Object you are swapping with has more than one Object Class and/or Activities >Dialogue: Set Class and Activity selector > Select as needed > OK

Adding an Object on multiple Bookings in Objects Tree:
Click on the Objects Tree Icon > Start Multi Selecting Bookings > Click on the Needed Bookings to select (or click to deselect) > Drag the Object you want to the needed Booking > Dialogue: ‘Add: Object X’ > Dialogue: Apply To Multiple Bookings (xx) >
If Yes: Object/s will be added to all the selected Bookings
If No: Object/s will be added only to the Booking you dropped it on

 

Public Holiday Calendars

Fixed a bug that was freezing the client application after importing Public Holidays

 

Reports

Objects Report + User Report: Added "Break Hours" to the Events Row, see details.

See Details

You can add a Break to a Framework Booking through the "Change Start And Stop Time" window. If a break is added this one will show in the Booking's Time Report window.

You will see these Breaks now in the both the Object's and User's Report:

Objects Report > Events loop: Break Hours will show as 0.25 for 15 min, 0.5 for 30 min, 0.75 for 45 min and 1 for one hour, 1.25 for 75 min,
Same goes for the User report.

Breaks on Bookings that are not Frameworks will also show in those newly created fields, if the Booking has been time reported.

 

Schedule Changes Email

Add Extra Info to your Schedule Changes Email

See Details

With the "Schedule Changes Email Extra Info" new feature you can configure and add extra info to your Schedule Changes Email.
In The Toolbox > Settings > Server Setup > Web Share Settings click on the button > Schedule Changes Email Extra Info and select what should be included in the email.
You can choose: Involved and any of your Booking Custom Fields.

When the Selected Values are updated in the booking this will trigger the email and include the details about the change.
1. If Involved is selected > it will list all Involved in the Email and will trigger an email when Involved will change.
2. If Booking Custom Fields are selected > It will list the booking custom fields and their values and trigger an email, when the value in the selected Booking Custom Field is changed.
It works both in the generic Schedule Changes Email and when you are using HTML for the email.

 

Server

#321435

Fixed a bug wrongly showing "Non-Fatal Error" messages on the fw Server app > Log window, see details.

See Details

These "Non-Fatal Error" error messages contained info such as: "::FRD", ".report_financial_generic.widget_include_...".
This is now fixed.

 

Fixed pre-server- connect “Pre Login Message” bad checker.

 

Fixed a bug wrongly preventing the fw Server app on Linux to launch.

 

Time Report

Fixed bug in Breaks showing "Affect: All" when it points to a deleted User.

See Details

If you create a Break in a Booking's Time Report, update the "Affect" field you point to a single User, and then delete that User from the database, the Break still points to that User. It doesn't - and shouldn't - automatically start affecting all users in the booking. However, in the UI it would suddenly start showing as "Affect: All" on the Break, which causes confusion.

Now when you open such a Break, it will say "Affect: ?", making it possible for you to manually redirect the break to other users, or to delete it.

 

Fixed two bugs on Auto Include Breaks, see details

See Details

Fixed two bugs:
When a user was creating an Ad-Hoc Timereport via the Web Client, the auto-include break was not added.
When an auto-included break was manually removed from a Time Report, it would wrongly automatically be added back if any rate was updated on the Project.

 

Toolbox

IMPORTANT: The "Web Share Settings" have been moved to their own section in the Toolbox > Settings!

See Details

The "Web Share Settings" used to be a sub-section within the fw Client Toolbox > Settings > "Server Setup". This sub-section has been moved out of "Server Setup" to its own section. In Toolbox select the "Settings" tab and then click on the menu button in the bottom of the Toolbox you will find "Web Share Settings" in the menu there.

 

User Report

#326166

Added 4 new Elements to User Report > Total Per User. See details:

See Details

Added 4 new [D] Elements to User Report > Total Per User:
*Total Booking Days
*Total Task Days
*Total Personnel Days
*Total Days

The totals look at the calendar days per each event type where one or more of the same event type have been booked.
Total Days is sum of all previous Total Event Days.

1) 1 Project Booking on day = 1 day in Total Booking Days
2) 1 Personnel event = 1 day in Total Personnel Event Days
3) 1 Task on day = 1 day in Total Task Days

If more than 1 Event Type is booked on a day, the Total of Days will count based on the hierarchy as below:
Booking, Task, Personnel Event = 1 booking day
Task, Personnel Event = 1 personnel day
Personnel Event, Booking = 1 booking day
Task, Personnel Event, Booking = 1 booking day
So in general the rule is: first is counts Booking, then Personnel Event, then Task for the Total Days.

 

Web Visibility

It is now possible to show Project Bookings Outside Web User Viewable Static Time Frame, in the Web Visibility window see detail.

See Details

There are two features in farmerswife that can limit what is visible to the Web Users in the Web Client, Mobile Web Client, iOS, Schedule changes email and Web Shared Reports. These features are
- Static Time Frames (Web User Only)
- Web Visibility

With "Static Time Frames (Web User Only)" you can define time frames when Web Users can see Bookings, when they will be able to make Bookings, and also the time periods when they can time report. When using this feature it has an effect on the visibility of all projects.

With the Web Visibility feature you define what will be visible to the Web Users by Project. To use this feature you need to enable it in the Toolbox > Settings > Server Setup > Use Web Visibility Settings For Project.
To use it for a Project open the Project Window and click on the Eye to display the menu and select Web Visibility. Alternatively click on the project icon when the Project is loaded to the Project Tree.

With this development it is possible to combine these two features, ie if you set a Static Time Frame to only allow visibility for a certain time frame, you can now select to show bookings for a specific project outside of that time frame.
A new setting has been added to to enable this in the Project Web Visibility window: "Show Outside Web User Viewable Static Time Frame".

 

fw-cirkus integration

Added a new farmerswife-cirkus integration. See details.

See Details

The new farmerswife - Cirkus integration allows you to:

-Sync projects and their custom fields from farmerswife to Cirkus
-Have the projects created in Cirkus created with a default or specified template
-Bi-directional sync of custom fields i.e changes can be made in both farmerswife and Cirkus and be in sync.
-All new projects created in farmerswife can also be created in Cirkus.
-All projects in Cirkus can be sent to farmerswife

To set up integration go to the Server > Setup > General.
In the Server > Setup > General Tab, there is a new section called Cirkus Connector.

1. Step 1: Set API Key
This is the key of a user who already registered on Cirkus. It's best to use a specific integration user for this account i.e fwintegration@yourdomain.com. To retrieve the API key, login to Cirkus as that user, and browse to the User Preferences>API Keys tab. Type a new name for the key and press Enter. The key will be created, and you can select to copy the key to your clipboard. Now back in the farmerswife server set up.
Click on the menu item to the left of the Cirkus Connector, select API Key and paste the key from your Clipboard.

2.Step 2: Select a Workspace
If there is no workspace in Cirkus, it needs to be created. Click on the menu item to the left of the Cirkus Connector > Set Workspace
A list of available workspaces is shown, select the one that all the synced projects in farmerswife will connect with.

3. Step 3: Configure the options for your Integration
- Project Templates
In the Project Templates section you can select a Default Cirkus Project Template. This is the template that will be applied to Projects that you create there. All projects that are created in farmerswife and synched to Cirkus will have that template applied. The project templates are set up in Cirkus.
Note: If "Sync New FW Projects To Cirkus By Default" setting if OFF, then you can select which template is applied to each project when you chose to sync it! If you are using Project Templates in Farmerswife you can map them with Cirkus Project Templates.

-Sync Time
Allows to select how often the sync will run. Recommended option is every 10 second.

-Sync Mode
Bidirectional - This will sync project status and custom field changes made on either platform to the other one.
FW to Cirkus - This will sync project status and custom field changes made on FW to Cirkus only.
Cirkus to FW - This will sync project status and custom field changes made on Cirkus to FW only
Master to Slave - This will sync project status and custom field changes made on the platform where the project was first created, to the other one.

- Fields To Never Sync to FW
If there are fields which are "master" in FW it's possible to select to never accept updates on those fields from Cirkus. Project Number is selected by default here.
Active = refers to the Active button in farmerswife and Open Yes/No slider in Cirkus.
Description = is the Project Note in farmerswife and the description field in Cirkus.
Name = in both cases the name of the Project
Number = in farmerswife this number will be given by default and might be linked to specific project number creation magic, in Cirkus you can edit this number yourself.
- Fields To Never Sync to Cirkus
It's also possible to select all different type of fields that should never be synched from FW to Cirkus. All the custom fields are available to choose from as well as other fields: Client, Closed, Contact, Email, Note and Number.
-Sync New FW Projects To Cirkus By Default
If this setting is checked, and integration is enabled, then any new project created in FW will be created in the selected Workspace in Cirkus. Existing projects in farmerswife will have a "Cirkus Sync" button in the Edit Project window to create a synced Cirkus project.

If the setting is unchecked, and integration is enabled, new FW projects will not trigger creation of a synced project on creation. You can enable the "Cirkus Sync" button in the Edit Project window to create a synced Cirkus project.

-Auto Create Active Cirkus Projects In farmerswife

If this setting is checked, and integration is enabled, then all active Cirkus projects will be created in farmerswife when the integration on.Any new projects created in Cirkus will also be created in farmerswife.

-Miscellaneous
It allows to update the Cirkus url, if Client is using an onsite or private Cirkus installation.
The default is https://cirkus.com, the public cloud service.

-Open Cirkus
This link will open the cirkus.com site, or the Cirkus mac application if it's installed.

Step 4: Enable Integration
Click on the menu again, and select "Enable Integration". Check the status of the connection below the Cirkus Connector logo.
It should say "Connected"

 

iOS, NWC & MWC

#326947
#325370

Implemented a massive performance improvement when using "Has Relation" on Web Permission Profiles.

 

Previous Releases

#18918

28. Jan 2020

6.6 Release