Back To Release Notes List



Back To Release Notes List

#20523

08. Jun 2022

6.8 Release

  • 1 Warning
  • 11 Hot Features 56 Features
  • 40 Other changes
  • 57+ Bug fixes

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

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.
- 11 HOT Features
- 56 Features
- 40 Important Other changes
- 57+ Bug fixes

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

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

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

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

Upgrading to fw 6.8 Release and later - see details!

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

IMPORTANT:
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 support@farmerswife.com should you require further assistance.

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

The built-in "Full Installer download" farmerswife (fw) Client auto-upgrade is active on:
- the macOS "64bit" Server on macOS 10.14 Mojave and later
- the Windows 64bit Servers

The "64bit" fw Server installers can only serve "64bit" fw Client full installers or provide the simple in-application auto-upgrade for already upgraded "64bit" fw Clients!
Any fw Client app on Mac running BELOW macOS Mojave must be manually upgraded by using the "macOS-32bit" installer after each upgrade!

The "32bit" fw Server installers DO NOT support any auto-upgrade!

This built-in Full-Installer-download auto-upgrade functionality - requires local OS user permissions read, write AND execute app installers. This will be triggered upon first log-in to the already upgraded fw Server application.
This means, upon login with the fw Client Desktop app, the user has to choose a location where the installer file will be stored on the local machine ... to then automatically continue with the upgrade process.

Upgrading
- Your farmerswife Server application must have been running on versions v6.4 SP2 and then upgraded via 6.5 Release rev. 18623, or later, 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: - work in process - please search after the release on our Knowledgebase
=> Client Installation Mac: https://support.farmerswife.com/en/support/solutions/articles/17000026002-client-installation-mac
=> Client Installation Windows: https://support.farmerswife.com/en/support/solutions/articles/17000026003-client-installation-on-windows

- Ensure you have the latest Java version (JRE on Windows/Linux, JDK on Mac OS X) installed, for the Web Client and Mobile Web Client to work properly and in the most secure way. Watch out on Windows: here you can run the fw Server application in 32bit mode (farmerswife.exe) or 64bit mode (farmerswife 64bit.exe); and depending in which mode you're running the WIFE Server, you _must_ have JRE installed in the corresponding 32bit or 64bit version.
We strongly recommend to use OpenJDK; more info here: https://support.farmerswife.com/support/solutions/articles/17000095590-how-to-replace-java-oracle-with-openjdk

farmerswife Server upgrade on Mac:

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

IMPORTANT:
macOS 10.14 Mojave is the only macOS on which all fw Server installers will work!
The 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: https://support.farmerswife.com/a/solutions/articles/17000026005-server-and-client-installation-linux
- 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: https://www.farmerswife.com/downloadsWeb/fw_client_v607_SP1.dmg

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

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

Windows Legacy "32bit" fw Client: https://www.farmerswife.com/downloadsWeb/fw_client_v608-32bit.exe
=> Support will stop end of 2022!

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

The latest iOS farmerswife app is v5.0.857 and is available on Apple's App Store since 1st-June-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.

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

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

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

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

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

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

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

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

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

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

A proper fw Test installation works like this:

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

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

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

Now start your TEST fw Server application.

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

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

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

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

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

About these Release Notes, Disclaimer and Legal Information

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

Installers

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:
"You are using the 32b it version of the farmerswife client application. Support will stop by the end of 2022. Please contact support@farmerswife.com or your System Administrator to upgrade to a working system."

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

 

API

#340472
#339708

Added fixes on the /timereport endpoint and added global JSON format fixes for better RAW response.

 

Advanced Contact Search

Added support for deleting multiple Contacts from the main module bar > Contacts, see details.

See Details

You can now delete multiple Contacts by multiple selecting them in the Contacts Search (main module bar > Contacts) > right mouse click > "Delete Contacts".

 

Advanced Project Search

Added "Set Start Date For Selected Class Bookings" option in the Advanced Project Search (main module bar > Projects), see details.

See Details

In the Advanced Project Search (fw Client > main module bar > Projects) you can e.g. filter by Projects and Bookings or only Bookings.
Now you can select multiple Bookings and _set_ the new start date for these Bookings, by right-mouse clicking on the selected Bookings and then use "Set Start Date For Selected Class Bookings" from the pop-up menu.

 

Added green "+" button for creating a new Project from the main module navigation bar > Projects.

See Details

This button will be hidden if "Can Create Projects" permission is disabled.

 

Made fields bigger in the main module bar Projects > Search fields area.

See Details

All fields should now have been aligned and have the same size. Includes fix for Windows.

 

Azure Active Directory

Added support for the "Microsoft Graph" API in the MS Azure AD Connector, see details!

See Details

The legacy "Microsoft (MS) Azure AD" API is still supported by farmerswife (fw); but it will stop working after 30-06-2022, because Microsoft will then shut it down.

To switch to the new "MS Graph API", you need to edit the renamed legacy field “MS Azure AD GRAPH API Endpoint” (old URL value was "https://graph.windows.net"), NOW called “MS GRAPH API Endpoint” and use only this NEW value: “https://graph.microsoft.com” and farmerswife will detect that it is using the new MS Graph API.
All Other settings related to the MS Azure AD Connector work in the same way.

EXTRA INFO: Notice also the “(v1)” text in the renamed field "Oauth 2.0 Token Endpoint" NOW "Oauth 2.0 (v1) Token Endpoint". This is due to MS also now has an Oauth 2.0 (v2) that we don’t support. You need to keep or copy the info from the "Oauth 2.0 (v1)" endpoint info into this "Oauth 2.0 (v1) Token Endpoint" field.

 

Booking Templates

#332436
#332388

Fixed an issue where it was wrongly not possible to delete/modify Booking Templates because of bad data.

 

Bookings

#330523

Added "Booking Objects Customs" to fw Client > Toolbox > Settings > Server Setup > "Setup Booking Mouseover Info".

 

Added the ability to "Move Start Date" and set the "Global Status" of multiple Bookings in the Advanced Project Search, see details!

See Details

In the Advanced Project Search (fw Client > main module bar > Projects) you can e.g. filter by Projects and Bookings or only Bookings.
Now you can select multiple Bookings and move the Start Date for these Bookings to a new date, by right-mouse clicking on the selected Bookings and then use "Move Start Date For Selected Class Bookings" from the pop-up menu.
This will move the Booking's Start Date based on their current Start Date; e.g. if you have selected 3 Bookings and each have individual start dates (e.g. 5th April, 7th April, 9th April) and you choose as new Start Date the 15th April, they will have the start dates moved to 15th, 17th, 19th April.

 
#338838

Fixed a bug by which "Declined By User (Read)" status wrongly sent notification emails when a user that declined was replaced with a new user.

 

Fixed a bug showing non-zero booked time for Ad-hoc Time Reports created through the iOS fw app or the Web client, see details.

See Details

When an Ad-hoc Time Report was created through iOS fw app or the Web client, it got a non-zero booked-time that could be seen in the Timereport window and that affected the new "Timereported More Than Booked" indicator. This is now fixed.

 
#341243

Fixed a bug where Overtime would wrongly be removed from all Objects within a Booking when re-timing another Object, see details.

See Details

If you configure the Activity Overtime on an Activity and you had an Object which was time-reported after you added another Object. and then altered the days, the Overtime for the initial Objects would be wrongly removed. This is now fixed.

 
#342761

Fixed a bug where it was possible to book an Object with an Inactive primary Object Class, see details.

See Details

Fixed a bug where it was wrongly possible to book an Object with an Inactive primary Object Class.
It will now be booked with the secondary active Object Class if any.
Also disabled the "Edit Class And Activity" option when the Object only has one active Class.

 

Budgeting

Added "Budget" column to the list of Actuals, with suggestions based on Binder, see details.

See Details

At the top of the list of Actuals, there are two buttons that attach the Actuals to their selected/suggested Accounts. Until now, this would always attach to the currently viewed Budget, even if you had more than one Budget. But from now on, they can get attached to any of the Budgets. Which one an Actual attaches to, depends on the values in the new "Budget" column. Note: If you don't see it, try using "Edit View" and add the Budget column.

If a Budget is linked to a Binder, and an Actual is linked to the same Binder, it will automatically default to that Budget. But you can also change it manually.

Any Actuals that don't have a suggested Budget will default to the currently viewed Budget. This is indicated by an italic font in the "Budget" column.

 

Added Binder support on Budgets, see details.

See Details

Until now, Binders have only been used to group Bookings. But now they can also be used to group Budgets. There's a new "Binder" field among the standard Budget fields. Please note that it only shows when you have at least one Binder in the Project.

Budgets with a Binder also reflect it in the Edit Project window and in Financial Reports. And searching for a Binder in the Edit Project window reveals the matching Budgets.

 
#318461

Added Object Class support on Budget Details. See details!

See Details

Until now, all Objects in a Budget implicitly used their Primary Class. There was no way to select a different Object Class and use Rates or Activities from that Class.

Now Budget Details have full support for Object Classes, which means that:
- When you add a new Budget Detail, the previous "Choose Activity Or Cancel For None" dialog is now replaced by an "Object Class And Activity" dialog. Note that pressing "Cancel" in this will actually abort adding the Budget Detail instead of continuing without any Activity.
- You can select a Budget Detail, right-click and select "Change Object Class / Activity..." which will bring up the same "Object Class And Activity" dialog.
- When using Scheduling Mode, it will try to book the Object using the selected Object Class instead of just the Primary Class.

To see the Object Class that was chosen when adding the Budget Detail you can display a new column "Object Class".

 
#336660

Added a new option in Toolbox > Settings > Server Setup > “Use Film Units Calculations” to be able to display a film units calculator icon in the Budget Window, where the calculated units will apply to linked budget lines. See details.

See Details

Added a new option in fw Client > Toolbox > Settings > Server Setup > “Use Film Units Calculations” to be able to display a Calculator icon in the Budget Window, in the budget list.
When clicking the new calculator icon, the “Film Units Calculations” window will be displayed to calculate units based on Film format, fps, meters, feet, images and duration.

All calculations are saved in the Budget and by using the button “Apply New Quantities” in the new “Film Units Calculations” window, the financial lines quantities can be replaced automatically when:

1) A financial line is linked to an Object with a Custom Field “Film format” (lower/uppercase supported) with the same value than the format we are applying. For instance, 35mm.

2) The same Object linked to the financial line has a Unit Name that matches with one of the following (lowercase/uppercase are also supported): Meter, Meters, Foot, Feet, Image, Images, Minute, Minutes.

Then the quantities will be updated in the budget lines, for the format you have been selected in the “Film Units Calculations” window.

More information: https://support.farmerswife.com/support/solutions/articles/17000118614-film-unit-calculator-for-budget-creation

 

Added feature that lets you configure "Default Objects" for each Budget Account. see details!

See Details

A Budget Account often has a limited set of Objects that are added to it. For example, an Account for "Producers" might be relevant for people but not equipment. But when adding new Budget Details to those Accounts, it would still list all possible Objects in the dialog.
Now you can limit the default suggestions, by going into Global Budget Settings and clicking on the "Objects" icon on each Account.

When an Account has a limited set of Default Objects, you can still change the filter and select a different Object. You'll then be asked if you want to add the Object to the Default Objects for the Account.

Finally, in the Object Manager, exported CSV files now have a new column called "Budget Accounts" which contains a comma separated list of accounts where the Object is part of the Default Objects. The same column is supported on Import, so you can edit the list of Accounts on each Object in the CSV file before importing.

 
#316425

Added separate "Note" column for Budgets, see details.

See Details

Previously, the Notes for Accounts and Budget Details were represented as icons inside the Description column.
Now there's a separate "Note" column that shows the notes without having to hover the mouse over those icons.
Note that the icons inside the Description column disappear when you choose to display the separate Note column, and reappear when you hide it.

 
#336660

Film Units Calculations addition, added a new field "Final Length Of Film", see details.

See Details

The new added field "Final Length Of Film" is used to apply the quantities to those Objects with an Object Custom Field called: “Use Final Length Of Film” (case insensitive) where the value can be “Yes”, “No”, “All Formats”. This will allow to have a service charging for the final length of film e.g. 90min, whereas the "Film Length in Minutes" could be different based on the meters or frames.

If “Yes” or “No” the Custom Field “Film Format” should match, otherwise if “All Formats” value is selected, the format will always match for applying “Final Length Of Film”.

 

If you filter by Object Class in the Object Browser dialog, it now remembers that Class when adding the object, see details.

See Details

When you add a Budget Detail, you first get the Object Browser dialog where you pick the Object. In the dialog, you can filter by a specific Object Class. But when you picked an Object that way and proceeded, it was reset to the Object's Primary Class.
Now it will remember how to find the Object and try to figure out which Object Class to use.
Note that this also works when configuring an Object Class as part of the "Default Objects" on a Budget Account. Since the Object was added through a specific Object Class, the Class will be used for the new Budget Detail.

 

Made Price Agreements apply when Booking in the timelines, see details.

See Details

When you have the setting "Attach Actuals To Active Budget" (In fw Client > Toolbox > Settings > Booking Defaults) active, and you create a Booking in a way that automatically attaches it to an existing Budget Detail, it now also attaches the Actual to any Price Agreement that is assigned on the Budget Detail.

 

The Budget selection dialog is no longer used when using Binders to auto-suggest Budgets, see details.

See Details

When you create Bookings and have the "Attach Actuals To Active Budget" setting enabled, a dialog is used to select which Budget the Actual should be attached to.
However, if you're also using Binders on Budgets, and create the Booking directly into a Binder, farmerswife may now auto-suggest the Budget and bypass the selection dialog.

 

Made "Add Budget Discounts To Actuals" apply when booking in the timelines. See details.

See Details

When you have these settings active:
- Attach Actuals To Active Budget (In fw Client > Toolbox > Settings > Booking Defaults)
- Always Attach Actuals If There Is Only One Active Budget (In fw Client > Toolbox > Settings > Booking Defaults)
- Add Budget Discounts To Actuals (In Budget window > Settings menu)

... and you create a Booking in a way that automatically attaches it to an existing Budget Detail, it now also applies the Budget Detail's Discount on the Booking.

In combination with Price Agreements, the Budget Price Agreements needs to be forwarded to the Invoice & Actuals Views and be set as default so the new created booked Objects are attached to the Price Agreements.

 

Calendar Widget

Added new Calendar widget that you can flip to view horizontally, see details.

See Details

The new Calendar widget used all over farmerswife is used in the following cases:
- Single normal Calendar
- Double Calendars (for start and end selection)
- Multiple selection Calendar

Go to: fw Client > Toolbox > Calendar > and here use the "Horizontal" check-box to set how the Calendars all over farmerswife is being displayed.

 

Cirkus Sync

Added "Detect Changes Using Websocket" toggle in fw Server > Setup.

See Details

Using this so far experimental feature makes the farmerswife Server use much less network traffic while syncing with Cirkus. Instead of periodically polling Cirkus, it will automatically get notified when something changes on the Cirkus side.
This setting is located in fw Server app > Setup > General > Cirkus Connector > sub-menu > Miscellaneous > "Detect Changes Using Websocket".

 

Added "Enable Request Error Log" option in Cirkus Logging Settings, see details.

See Details

There's now a new check-box called "Enable Request Error Log" in in fw Client > Toolbox > Settings > Cirkus (v2) > Logging Settings.
When enabled, if a request fails, it will be logged to a file called "system/crk_request_errors.log", complete with both request and response details.
This can be used to troubleshoot if for any reason Cirkus requests are failing. But keep in mind that the log size can grow quickly if there are repeating errors in the sync.
The log rotates with a max size of ~1MB.

 

Added Binder support to Tasks <=> Project Objects sync, see details.

See Details

This only applies if the following setting is enabled in fw Client > Toolbox > Settings > Cirkus (v2) > "Sync Binders To Subprojects".
When syncing Tasks from Cirkus to Project Objects in fw, it will now decide what Binder to use based on what Subproject the Task is in.

 

Added Cirkus integration to Object Manager, see details.

See Details

If the Cirkus v2 integration is active, the Object Manager in farmerswife will now have a new optional column called "Cirkus", which tells if the User/Resource/Object has a Cirkus counterpart.
Note: It still does this by comparing email addresses for people and comparing the exact name for Objects.

Additionally, if you select some Users/Objects and right-click, there are now these new menu items "Cirkus > Add To Cirkus" and "Cirkus > Update In Cirkus". They will first copy over any needed Object Classes from farmerswife to Cirkus as Roles or Resource Categories, and then add/update the Cirkus User/Resource with those Roles or Resource Categories.

 

Added Logging Settings in fw Client > Toolbox > Settings > Cirkus (v2), see details.

See Details

The logging for the Cirkus Sync has mostly been an all-or-nothing approach, except for the "Bookings > Verbose Logging" option that was only possible to toggle on fw Server side.
Now you can control the amount of logging using 7 log levels:
- Off
- Fatal
- Error
- Warning
- Info
- Debug
- Verbose

The default level is "Info", which logs when something has actually changed and caused a sync, but not much more detail.
The logging settings can be found in fw Client > Toolbox > Settings > Cirkus (v2) > Logging Settings.

 

Added a "Test Connection" button in fw Client > Toolbox > Settings > Cirkus (v2).

See Details

It attempts to connect to Cirkus from both fw Client and fw server, and displays any errors in a dialog for easier troubleshooting.

 

Added a Setting in the Toolbox called "Open Cirkus Links On Web", see details.

See Details

This new Setting "Open Cirkus Links On Web" is located in fw Client > Toolbox > Settings > Cirkus (v2), and when this setting is used it causes farmerswife to open Cirkus Links using the web browser instead of the native Cirkus app.

 

Added a setting that controls if fw Resources are mapped to Users or Resources in Cirkus, see details.

See Details

Until now, since Resources in farmerswife typically represent real people, they were being mapped to Cirkus Users when e.g. syncing Bookings. However, being a User in Cirkus means they're expected log into Cirkus, get notifications, etc. And that they take up a User slot in Cirkus. Sometimes it can be better to sync Resources to Cirkus Resources, to avoid those side effects.

Now there's a new setting: in fw Client > Toolbox > Settings > Cirkus (v2) > Map Resources To.
For customers already using the Cirkus integration it will default to "Cirkus Users", to be backward compatible. For all others it will default to "Cirkus Resources".
Anyone who is using the Cirkus integration but not already syncing fw Resources to Cirkus Users can also safely change the setting to "Cirkus Resources".

 

Added ability to pause syncing, using the Server Log menu, see details!

See Details

If for any reason the automatic Cirkus sync is causing problems, it can now be paused through the menu under the fw Server app GUI's Log window.

 

Added support for syncing Binders to Subprojects, see details!

See Details

This feature can be activated in fw Client > Toolbox > Settings > Cirkus (v2) > "Sync Binders To Subprojects".
When activated, any change (adding, updating or removing) to a fw Project's Binder will make it sync all of the Project's Binders to Cirkus.
For now the sync is one-way, so new Binders added in Cirkus will not be automatically added to fw.

Also, when this setting is enabled and you create a Cirkus Task from a Budget Detail, it will no longer create a Subproject from the Budget Accounts. Instead, it will look at the Budget's Binder and put the new Task in the Subproject that corresponds to that Binder.

 

Added support for syncing Booking Time Reports, see details.

See Details

This feature allows for Time Reports on Bookings to be synced between farmerswife and Cirkus.
To activate it, go to fw Server app > Setup > General > Cirkus Connector > Time Reports and toggle om "Sync Enabled". You may also want to click "Detect Timezone" to make sure it detects the correct timezone for farmerswife. If you skip that step, it will automatically try to detect the timezone the first time it syncs Time Reports.

The sync comes with the following limitations:
- If you report more than 24h on a day in Cirkus, it will be capped to 24h in fw.
- If you report on a non-booked day in Cirkus, the time will be registered on the nearest booked day in fw.
- If the Time Report is changed on the same Booking in both farmerswife and Cirkus at the same time, it will not merge the results, but rather overwrite Cirkus' version with the one from farmerswife.

 

Added syncing of Booking Name/Template on Bookings, see details.

See Details

Bookings in farmerswife (fw) can have a Booking Name and then Custom Fields associated with it. This is configured in fw Client > Toolbox > Settings > Booking Defaults > Booking Names & Customs.
Similarly, Bookings in Cirkus can have a Booking Template.
Now, when you set or update a Booking Name/Template in either location, it will try to find a matching Name/Template in the other location, matching by exact name.
Among other things, this can be used to get matching colors (based on Booking Name/Template) in fw and Cirkus.

 

Added syncing of new Cirkus Tasks to Project Objects, see details.

See Details

There was already syncing of Cirkus Tasks to Project Objects, but only when they were first created from a Budget Detail.
Now you can create a Task in Cirkus and have that automatically sync to farmerswife.
To get started, go to Toolbox > Settings > Cirkus (v2). Under Task Template Mappings, add a new mapping.
- Object Name: This is the name of the farmerswife Object that will be added to the Project when a new Cirkus Task has been found.
- Task Template: This is the Task Template that identifies the Tasks added to Cirkus, so it doesn't just pick up *any* Task.
- Quantity Field: An optional setting that defines a Custom Field in Cirkus. It then looks at this Custom Field to try to figure out the Quantity for the Project Object that is added in farmerswife. If not set, the Quantity will typically be 1.
- Actualize (Immediately / When Done): Decides when the added Project Object will get a quantity. If "When Done", the quantity will be 0 until the Task is set as done in Cirkus. Then it will get whatever quantity is decided for it. If it comes from a Budget Detail, that quantity will be used. Otherwise it will try to parse the quantity from the "Quantity Field" or just use 1.
- Pick Up New Tasks Added To Cirkus: If checked, any new Tasks added to Cirkus will be synced to farmerswife. If not checked, new Tasks added there will be ignored.

You can also map the Object Name field to a Custom Field from Cirkus. That way you can create a single Task Template in Cirkus and then let a Selector Custom Field on the Task Template specify which Object to use in farmerswife. If a Task's Custom Field doesn't contain a valid Object Name then the Task will be ignored.

 

Fixed tooltips wrongly disappearing in the Project window.

See Details

When a Project was synced to Cirkus, the tooltips inside the Edit Project window would keep disappearing every 5 seconds.

 

The Project Color is now synced, see details.

See Details

farmerswife and Cirkus Projects both have a color. In farmerswife it can be set in Edit Project window > View menu > "Force Colour".
Those color fields are now supported when syncing.

 

When syncing a Project causes a "Permission Denied" error, it now gets marked as failed, see details!

See Details

When the syncer can't update a Project due to a (403) "Permission Denied" error, it means the "sync user" has lost permission on that Project, and it most likely requires some kind of manual intervention on the Cirkus side. E.g. by adding the "sync user" to the Project, or updating their permissions there. The Project will now be marked as failed and stop being synced. When the problem has been manually fixed, you can open up the Project in farmerswife, click on the warning triangle in the Cirkus section and clear the error to resume syncing.

 

Fixed errors when showing "Cirkus" column in the Object Manager on Windows.

 

Conflicts

Implemented Booking Conflict Checker Optimisations.

 

Contacts

Implemented to Hide inactive Contacts when appropriate, see details.

See Details

Inactive Contacts (Active = No/0) are now hidden (in the "Suppliers" fields) when creating New Check Out, New Purchase Order, New Incoming Invoice.

In the Project search (and in other searches) all inactive Contacts are displayed .
Finders on Contacts now will also include Users as well as Resources and Clients.

In fw Client > Toolbox > Contacts sub-menu and in the Contact window top left corner, the option "Show Inactive" was added in the drop-down menu to Show/Hide Inactive Contacts.

 

Container

Added Container tab in Toolbox, see details.

See Details

The new Container tab in fw Client > Toolbox can be displayed via Toolbox > Settings > Miscellaneous > "Toolbox Menus".

It allows you to:
1. Create Containers and edit them.
2. Delete Containers
3. Display list of all Containers.
4. Run financial reports on Containers.

Containers are used to group Projects from the same Client.

 

Added support for multi-selecting Projects and attaching/detaching to a Container.

See Details

This works in fw Client > Toolbox > Projects and in fw Client > main module bar Projects by multiple selecting the Projects, right-mouse click (or use the sub-menu) > Container > Attach or Detach.

 

Custom Fields

#330523
#333635

Added support for Framework Custom Fields, see details.

See Details

A new Selector Field was added in fw Client > Toolbox > Settings tab > Frameworks > called "Name/Customs".

A Framework Custom Field Template with the different kinds of Custom Fields (Entry, Text, Selector, Date, Widget, Files) can be added here.
You can add multiple Framework Custom Field Templates. These are then available when you click on a Framework Name in the Long Form > Projects tree.

To load the Framework Custom Field Template in the Framework itself, click on the Name - if you have one or more Framework Custom Field Templates configured, their names will show in a list below, for you to select the corresponding one.

Once the Framework Custom Field Template is loaded, the Framework window expands and shows all the Custom Fields added to the Template.

It is possible to change the Framework Custom Field Template by clicking into the Framework Name and selecting a different one. You can also load a template and the overwrite the Framework Name. The Custom Fields will stay.

To print out Framework Custom Field info, they are available in the following Reports:
1) User Report > Events loop/section
2) Object Report > Events loop/section
3) Financial Report > Row section - all Framework Custom Fields from all created Framework Custom Field Templates will be listed below one another and can be selected for the report.

Group by Framework Custom Field in the Financial Report Designer:
It is also possible to run a Financial Report and choose the Framework Custom Fields as Groupings, so the Report will show the results grouped by the selected Framework Custom Field.

 

Day Chart

#338257

Implemented multiple improvements to the "Day Chart" Report.

 

Dispatch Module

Renamed "Dispatch Status" to "Object History" in various places!

 

EMT

Implemented Dispatch Search optimizations.

 

Edit View

Made the "Edit View" window wider for easier selection of which columns to show, see details.

See Details

In many "table" views you can choose which columns to show/hide. In order to be able to read the whole name of the fields, especially when using Custom Fields, the Edit View window is now wider.
Also if the text on either column exceeds the width then a tooltip, it will appear showing the whole text when hovering over it.

 

Extras

Implemented to allow adding multiple Objects as Pre-Defined Extras as long as they have different Activities.

 

Financial Report

Added "Invoice Note" fields, see details.

See Details

These new fields were added:
- Rows > "Invoice Note From Source"
- Source > From Class Booking > "Invoice Note"

 

Added Service / Media Order Number to Financial Report > Rows.

 
#341801

Improved the Inventory Number in the Row section to also show the User Number if a User has a User Number configured in the Modify User window.

 
#309444
#319589

Fixed a bug preventing Quantity Totals from showing for users without Rates permissions, see details.

See Details

If a user doesn't have Rates permission on all the data in a report, they should still be able to see Quantity numbers.
But since a bug introduced in farmerswife v6.3, it was not possible to see Quantity Totals in any of the Groupings or in the Header/Footer. That is now fixed.

 

Frameworks

#330523

Added "Framework Custom Fields" to the option "Setup Booking Mouseover Info", see details.

See Details

Go to: fw Client > Toolbox > Settings > Server Setup > "Setup Booking Mouseover Info" button. Click on it and move the items you want to see from the left "Not Selected" pane, to the right "Selected" pane via drag&drop, or clicking on the item you want to select.

 

The Framework default Custom Field Template now gets applied as expected.

 
#333738

Fixed Framework Cell's blue selection in Project tree and Framework Bookings, see details.

See Details

Now when you click on a Framework Cell inside of a Framework Binder, this cell is marked with a blue frame again.

 
#338917

Fixed a bug by which Frameworked Objects were not being selected correctly, causing some wrong modifications on the previous selected Object.

 
#333815

Fixed a bug by which a Framework Breaks on a empty Framework Cell was wrongly being lost when moving Binders.

 
#341809

Fixed a bug when in some circumstances a Framework Break was applied double.

 
#338834

Fixed a bug where in the Long Form > Object tree mouse-over on a User wrongly all Custom Field Template infos from the whole Framework were shown, see details.

See Details

Fixed a bug where in the Long Form > Object tree mouse-over on a User wrongly all Custom Field Template infos from the whole Framework were shown, instead of only the Custom Fields specific to the Framework the User was booked on.

 

Fixed a bug wrongly causing some Framework Breaks data to become corrupted when checking to upgrade Projects during the upgrade.

 
#338832

Fixed an issue by which the Framework Name was not "highlighted/selected" anymore by default when opening the Framework Edit window.

 

Improved for farmerswife to now also keep the Break time on Objects when swapping them, see details.

See Details

If you use Framework Bookings and decide to put breaks on empty Framework cells, the breaks now are tight to the empty Framework Cell, even if you allocated User to that Framework Cell and swap them with another User on the same Framework Booking on the same day.

 

General

#336660

Added a new option to the fw Client > Menu: “Open Film Units Calculator”, see details.

See Details

Added a new option to the fw Client > Menu: “Open Film Units Calculator”, which will be displayed if in fw Client > Toolbox > Settings: “Use Film Units Calculations” is enabled.
Only available with Budgeting module.

 

HTML Reports

#338257

Added formatting on "html_templates" for Notification on Project Custom Field changes, see details.

See Details

When Project Custom Field Notification changes are sent:
- new value will be highlighted in red
- unchanged values will be highlighted in grey
- changed values will be indicated with arrow showing the old value (grey) --> new value (red).
This was before not working correctly, but it is now fixed.

 
#338257

Replaced all the cssCSS classes in "notifications_email.html" by "inline styles" to fix formatting issues in Outlook.

 

Hourline

Added new setting in Toolbox > Settings > Miscellaneous > “Hourline Minutes Increment”, see details.

See Details

This new setting in Toolbox > Settings > Miscellaneous > “Hourline Minutes Increment” now offers the ability to change the standard 15 Minutes time interval to be instead incremented by 5 or 1 Minute when creating, moving or expanding/shortening bookings with drag&drop in the Hourline.

 

Added the ability to change the Binder that a Booking belongs to, see details.

See Details

Go to the fw Client app > Hourline > right mouse click on a Booking and in the pop-up menu choose Binder > Change Binder For Booking > select from the list of existing Binders.

 

Icons

Added new User and Object Icons.

See Details

Added 43 new Object Icons, and 20 new User icons.

 

Added new user icons (Bricks).

 

Incoming Invoices

#326783

Fixed the sorting behavior for the Due Date column in Incoming Invoices module, see details.

See Details

In the Incoming Invoices module, the Due Date column sorted alphabetically instead of chronologically. This is now fixed.

 
#335775

Fixed wrong search results when filtering by multiple Custom Fields in Incoming Invoices.

 

Invoice Creator

#341158

Fixed a fw client crash when creating a Part Invoice in a very special scenario.

 

Invoicing

#312973
#340133

Fixed a bug in "Mail And Mark As Sent" when using email addresses using dots in Contact Name. I.e: Full A. Name <to@email.com>.

 

Long Form

Added new per-user "Force Hourline Colors Everywhere" setting, see details.

See Details

In fw Client > Toolbox > Settings > Display, there is now a new checkbox called "Force Hourline Colors Everywhere".
Checking it will make Bookings in the Projects and Objects trees to be displayed using the same colors as in the Hourline.

 

MacKiosk

#340282

Fixed a bug introduced in rev. 20047 wrongly causing that on Pending Dispatches no items were displayed.

 
#323612
#323869
#337206

Fixed a bug on "Missing" or "Broken" items reported on MacKiosk wrongly preventing these items to trigger an email notification, see details.

See Details

And added the Dispatch Object's Note info in Dispatch emails.

 

Mobile Web Client

#343093

Fixed a Mobile Web Client encoding issues wrongly not showing Umlaut characters as a result from the Jetty upgrade.

 
#341498

Fixed a bug that was causing "Search" and "Categories" tab under the Involved tab not being displayed when creating a Booking in the MWC, see details.

See Details

When creating a Booking via the Mobile Web Client (MWC) and going to the Involved tab to add e.g. another User or Object to the Booking, users would see 3 tabs: Favorites, Search and Categories.
The Search tab wasn't correctly displaying the Search field and the Categories tab was not correctly displaying any Categories, thus the user was not able to add any Involved to the Booking.
The bug is now fixed and a user can find Objects via Search or Categories in the Involved Tab.

 

Multiple Currencies

#337982

Implemented improvement when searching on Invoices with Multiple Currencies enabled.

 

Fixed incorrect currency showing in the Financial Report of Invoiced Projects and in Budget Quotations.

 

Fixed the Conversion Rate applied when changing the Currency inside of the Edit Invoice window, see details.

See Details

When an Invoice gets created, it takes the Project's main currency. If you now want to send this Invoice in e.g. GBP you can click on the Currency selector field and choose GBP. Now the Invoice rates are shown in the converted currency with the correct conversion's rate applied.

 

Fixed wrong amount and currency for Invoices in Invoice Creator, Invoice Manager and in the Edit Project window, see details.

See Details

Invoices in the Invoice Creator, Invoice Manager and in the Edit Project window would always display the amounts in the global currency. Now they are displayed in the Invoice currency.
If the Project currency is different than the Invoice currency then the Invoice row will display the amounts both in the Invoice currency and the Project currency.

 

Fixed wrong currency in Price Agreement, Rate Card, Custom Service/Material/Expenses, see details.

See Details

Now in Price Agreements, the Rate Card and Custom Services/Materials/Expenses will show the correct Project Currency.

In Projects that have a different Currency than the standard one, Rates will show in the Project Currency and below in italic in the standard Currency.

 

New Web Client

Implemented Task/Request Types visibility on the Web Client, according to the setting fw Client > Toolbox > Settings > Task / Request Setup.

 

Notifications

#338257

Fixing a bug where the Notification on "Project Activation" wrongly wasn't sent when creating New Project via "New Project From".

 

Skipping Notification on Project Custom Field changes when Project gets created with "New Project From", see details.

See Details

When a new Project was created by using the "New Project From" option, the values in the Custom Fields were also copied. Even though they would never be saved in the new Project, the Notification would be send immediately after the new Project was saved with new values, as if updating values copied from the old Project in the new Project window would be considered as a change.
This was unwanted behaviour and is now fixed.
Project Custom Field Notification is now only sent when values are changed again, after the Project has been saved the first time.

 

Object Classes

#343054

Enabled the option for the "Object Class Ranking" to edit the "Other" field, maintaining the previous text to be able to overwrite it, see details.

See Details

For "Object Class Ranking" go to the fw Client app > Object Manager > Object Class > Edit > open it up so you see the Members.
Click on the sub-menu in-front of the Username and select > Ranking > Other: Type in a text: "acb".
Then you realize that you meant to type "abc"; but until now you could only remove the "Ranking-Other", or click on Ranking > Other > but then the text was gone.
This is now fixed, and it's now possible to modify the "Other" field, maintaining the previous text to be able to change it.

 
#342761

Changed to now prevent adding Members to an in-active Object Class, see details.

See Details

When an Object Class is in-active there is now a Warning when you try to add an Object with drag&drop to a Class in the Object Manager.

In-active Object Classes no longer show in the list of "Add To Class" option on Objects.

 

Fixed a bug preventing Object Custom Fields from showing in misc places, see details.

See Details

Object Custom Fields seemed to have no values when used on pure Object Classes in some places, including:
- Financial Report
- Project Report
- ...and likely others.

This bug is now fixed.

 

Object Importer

Fixed a bug in Object Manager > sub menu > Import when importing a CSV using the column "Budget Accounts".

 
#336129

Fixed a bug where the column "Active" of Object Classes were wrongly empty when exporting them, see details.

See Details

If you exported any Object Class, the "Active" column was empty, not showing Active (1) or Not Active (0). This is now fixed. If you now change the info in the "Active" column for any Object Class and import it again, it will now update the Object Class accordingly.

 

Object Manager / Server Setup

#326351

Implemented "Auto Generate Inventory Numbers For Objects", see details.

See Details

Farmerswife auto-generates Inventory Numbers for your Equipment either manually or via the Object Import functionality in the Object Manager.
The Inventory Numbers need to consist of only numbers, no combination of letters and numbers possible with this option.
(Inventory Number: 9045556 = works, LHE_123456 = doesn't work)
Prerequisites:
Enable this functionality in the Server Setup > Objects tab > Auto Number Inventory Number: Yes.

Manual creation of Objects in Object Manager
Once the setting is enabled in the Server, farmerswife will auto fill a new Inventory Number into the Inventory Number field adding a +1 to the last Inventory Number given.
Please remember a combination of letters and numbers in the Inventory field won't work with this functionality.

Auto generation of Inventory Numbers via the csv import into the Object Manager
In the cvs file, the Inventory Number column is the U column. In this column please add the word: "auto" (without the brackets) to activate the auto generation of the Inventory Number while the new equipment is being imported into the Object Manager.
This will also work if you import Objects with Accessories or Groups.

 

Object Manager Report

#342478

Added new Setting "Fetch Dispatches For Objects Report" Yes/No (Default), see details.

See Details

When using the "Equipment Management and Tracking" (EMT) module in farmerswife, the Dispatch History per Object can result in huge amounts of data when trying to Report on it via the Object Manager > Report.
To be able to still use the Objects Report from the Object Manager, a new Setting was added in fw Client > Object Manager > sub-menu > Settings > "Fetch Dispatches For Objects Report" Yes/No (Default).

If you need to create Reports which also have to contain the Dispatch information per Object, then you need to enable this setting and generate your Objects Report in manual chunks of max. 100 Objects.
Please contact supportATfarmerswife.com should you encounter issues.

 

Fixed incorrect formatting of Date and Checkbox Custom Fields, see details.

See Details

In the Object Manager Report, any Object Custom Fields that were of type Date or Checkbox were not formatted correctly and showed numbers instead of dates and 1/0 instead of Yes/No.

 

Objects

Made fields bigger in the Object and Class Modify windows, see details.

See Details

The Inventory and Ref fields are now bigger and aligned on the Object and Object Class window.

 

Objects Tree

#341218

Added for the Long Form > Object tree the option to "Include Inactive When Loading", see details.

See Details

Now when loading Objects and/or Resources through the "Load" options into the Objects tree in the Long Form, you are able to choose if you want to include Inactive Objects via: Objects Tree Menu > Options > Include Inactive When Loading.

See also:
https://support.farmerswife.com/support/solutions/articles/17000076217-objects-tree

 

Permissions

Implemented for “Tasks / Bookings” permission type to be able to approve Requests and edit/view Personnel Management based on the Permission Profile.

 

Personnel Tree

The "time report diff indicator" now respects Breaks, see details.

See Details

In the Personnel Tree, any Booking that has more reported time than booked shows the difference in hours.
However, it didn't respect Breaks. So if you reported e.g. 1 more hour than booked, but compensated with a 1 hour break, it still claimed to have more reported than booked time.
Now those Breaks will be subtracted from the reported time. And possibly also from the booked time - if it was a Booked Break.

 

The Task Name is now displayed on Tasks in the Personnel tree when both Project and Name settings are ticked, see details.

See Details

In fw Client > Toolbox > Settings > Personnel Tree you can "Display Text As In Object Tree".
However it would not show the Task Name even when both Project and Name settings were ticked in Toolbox > Settings > Object tree. This is now fixed.

 

Play

Updated “log4j” to latest version.

See Details

If you need more information, please contact supportATfarmerswife.com.

 

Print As PDF (fw Client side)

Implemented Scan Fonts improvements to be able to parse more fonts like Lato, Comic Sans, and others.

 

Print Designer

Added more fields to Project and Invoice Reports > Element Row. See details.

See Details

Added the following fields to Project and Invoice Reports:
1) Act/Name
2) Number
3) Activity (Or No Activity)
4) Price Agreement (Name)
5) Price Agreement (Or No Price Agreement)
6) Object Class/Name + Activity
7) Object Class/Name
8) Activity/Object Class/Name

 

Added "newline" option to "Split" String Operator, see details.

See Details

In the Edit String Operator window for "Split" there is an Input option called "Split Character". It only allows single-line values, which made it impossible to split on newlines. Now a pop-up menu has been added next to it, allowing to select newlines as "Split Character".

 
#330648

Added Univers LT Pro to the native supported fonts.

 

Printing

New PDF Printing is now the default with Print Designer version 5.

See Details

PDF Rendering Mode is now set as: 'New PDF Rendering', as the default mode. Print Designer Version '5' is the default Print Designer version.

 

Re-implemented direct printing from the fw Client app on Mac and Windows! See details!

See Details

You now have two options to "print" from the fw Client application:
- NEW "Print (Beta)"
- "Save As PDF"

On macOS:
The new "Print (Beta)" will work out-of-the-box on Mac using the default 64bit app (Retina optimized and non-retina optimized) for any installed printer. This is NOT available for the legacy 32bit fw Client app for Mac.

On Windows:
For this to work on Windows, two Windows OS related changes must be applied on each Windows machine, where the new "Print (Beta)" is supposed to work.

a) On Windows go to: Control Panel > All Control Panel Items > Programs and Features > Turn Windows Features on or off > Print and Document Services > "LPR Port Monitor" <= Enabled.

b) On the installed Printer(s) to be used for direct "Print (Beta)" > Printer Properties > General > "Location" field ensure that this info exists and is correct for the installed and to be used printer: http://PrintersIP:80/WebServices/Device

 

Forcing the Full Installer upgrade for lower revisions due to latest new PDF rendering changes: underline support and umlaut and special chars.

See Details

Applies to versions lower than 6.8 rev. 20068.

 
#332933

Implemented that a "Scan Fonts" gets run on every user login.

 

Project & Invoice Reports

Added more fields to the Project and Invoice Reports, see details.

See Details

Added more fields to Project and Invoice Reports:
1) From Details > Sell Total
2) Element Rows > Activity, Sell Row Before Discount
3) From Details/Totals > Total Buy, Sell Before Discount

Also fixed "Name Primary" wrongly showing TBD instead of Activity when using pure Object Classes and Activities.

 

Project Binders

#333578

Fixed deleting selected Binders in fw Client > Toolbox > Deleted Bookings And Binders, see details.

See Details

If you selected a Binder in Toolbox > Deleted Bookings And Binders, right-clicked and selected "Delete (1)", it wouldn't actually delete the Binder. This bug is now fixed.

 

Project Objects

Added Binder support on Project Objects, see details.

See Details

Until recently, Binders have only been used to group Bookings. But now they can also be used to group Project Objects. There's a new "Binder" field in the dialog where you edit the Rates and the Note. Please note that it only shows when you have at least one Binder in the Project.

Project Objects with a Binder also reflect it in the Edit Project window and in Financial Reports. And searching for a Binder in the Edit Project window reveals the matching Project Objects.

 

Project Window

Fix a bug wrongly causing long Custom Field Tables being cut off in Edit Project window.

 

Fixed for long Custom Field labels to not cut off at right point on the Edit Project window on Windows, see details.

See Details

Long Custom Field Label Names are now cut off at the right point with the ellipsis and tool-tip.

 

Projects

#338257

Added Project Notification: On Project Activation and Project Custom Field changes, updated notification_email.html to support more CSS tweaks from template, see details!

See Details

Added Project Notification: On Project Activation, more info below!
And updated the "notification_email.html" (located: fwServerAppPackage > ("Contents" on Mac) > html_templates > other > notifications_email > notification_email.html) to support more CSS tweaks from template:

Technical CSS info to be able to transform the notification_email.html file:
- Added css class ".fw_project_name_and_number", to be able to apply styles to the Project Name and Number.
- Added css class ".fw_line_start_arrow", to be able to hide, or format the "-->" characters.
- Added css classes ".fw_has_changed_from_text" and ".fw_has_changed_to_text" to be able to hide, format or transform the texts "Has Changed From" and "To" when displaying changes.
- Added css classes ".fw_changed_field_old_value.first_time" and ".fw_changed_field_new_value.first_time" to format the values which are set for the first time.

New Notification On Project Customs Changes (since v6.8):
This Notification allows to notify selected users when the values on Project Custom Fields get updated. The email contains: Project Number and Name and the list changed custom fields with label name, old and new value.

CUSTOMER SPECIFIC: The email is listing ALL custom fields (not only changed). When a value is entered for the first time, it’s highlighted in red; the change of this value is indicated with an arrow pointing from the old value in grey to new value in red, and fields that were not updated show as grey.


New Notification On Project Activation (since v6.8):
This new Notification allows you to notify selected users, when a Project is created or set Active (after it was set to not Active).

CUSTOMER SPECIFIC: Project Name and Number is highlighted in red and lists all Custom Fields (in grey) with their values.

When upgrading your farmerswife system past v6.8, make sure to update the "notification_email.html" if you want to have it working as explained here.
IMPORTANT: if you make changes to any of the "html_template" files, make sure you make them "Read Only" on Windows and on Windows, Mac or Linux, make sure you have these modified template files backed up! Because on the farmerswife Server app upgrade, the installer app will always "deliver" the latest template files from us, which don't have your customized changes. And for the fw Server app if hosted on macOS, make sure to copy your backed-up customized html_template template files back into the new fw Server app package after the upgrade.

To see all information about Notifications from farmerswife, see here:
https://support.farmerswife.com/support/solutions/articles/17000071818-global-notification-emails

 

Public Holiday Calendars

Added the possibility to “Import Public Holidays For Netherlands” in Toolbox > Settings > Server Setup > Public Holiday menu.

 

REST Api

#330523

Added "Booking Object Custom Fields ("bookingLineCustoms") to the GET /events endpoint.

 
#330523

Added "Break Time" related properties only from Frameworked Bookings to the GET /events response, see details.

See Details

The now available "Break Time" related properties only from Frameworked Bookings on the GET /events response are:
- projectBinderFrameworkBreakHeader
- projectBinderFrameworkBreakTimeIn
- projectBinderFrameworkBreakTimeOut
- projectBinderFrameworkBreakMinutes
- projectBinderFrameworkBreakNote

 
#330523

Added "ObjectClassRef" to the GET /event/:id endpoint.

See Details

Updated Swagger documentation with latest changes to v0.8.2

 
#330523

Added "Ref" and "Inventory Number" info to the /objects and /events endpoints.

 
#330523

Added "bookingDatetimeInAsString" and "bookingDatetimeOutAsString" to the GET /events endpoint.

 
#330523

Added "eventType" filter for the GET /event endpoint, which allows e.g. to filter between "personnel" and "project (Bookings)" events.

 
#330523

Added "projectBinderFrameworkNote" and "projectBinderFrameworkDayNote" to the GET /events endpoint, see details.

See Details

The added "projectBinderFrameworkNote" comes from fw Client > Long Form > Projects tree > Frameworks > double click on the Framework Class > "Edit" window > Note".

And the added "projectBinderFrameworkDayNote" comes from fw Client > Long Form > View Port > Framework cell click > "Edit Note" and here in the "Edit Note" window.

Both are added to the GET /events endpoint.

 
#330523

Added "projectCustoms", "projectBinderCustoms" and "projectBinderFrameworkCustoms" to GET /events endpoint.

 
#330523

Added "webVisibility" to the GET /projects endpoint, see details.

See Details

Example with Project based "Web Visibility" enabled:
"
webVisibility": {
"active": 1,
"dateIn": "2021-05-01",
"dateOut": "2021-05-31",
"showOutsideViewableTimeFrame": 0,
"filterByUsers": {
"active": 0,
"users": []
},
"filterByBinders": {
"active": 0,
"binders": []
}

 

Added /binder endpoint (GET, PUT, POST) and updated Swagger 0.8.6 version.

See Details

This is supported since v6.8 Beta rev. 20204.

For more info use the latest "swagger.json" v0.8.6 or later from here:
https://support.farmerswife.com/en/support/solutions/articles/17000089578-the-farmerswife-server-s-rest-api-for-your-own-3rd-party-integrations

 

Added bookingLineCustoms to /event/changes and objectName to /event/changes and /event endpoints.

 

Added eventIDs to /binder (POST and PUT endpoints) to be able to add, move, remove multiple Bookings from Project Binders.

See Details

This is supported since v6.8 Beta rev. 20223.

For more info use the latest "swagger.json" v0.8.6 or later from here:
https://support.farmerswife.com/en/support/solutions/articles/17000089578-the-farmerswife-server-s-rest-api-for-your-own-3rd-party-integrations

 
#330523

Added new endpoint "/events/changes" to get Deleted Events data based on the “Schedule Changes Email” feature, see details.

See Details

GET /event/changes to get Deleted Events with 90 days of data retention and based on the "Scheduled Changes Email" data.

Added a new setting to start collecting data in fw Client app > Toolbox > Settings > Server Setup > "Enable Scheduled Changes Data Retention (REST Api)".

This setting needs to be enabled, in order for this functionality to work.
And when developing with this, ensure you have a tool like "mailtrap.io" (no affiliation) in use on your side; as this feature requires the "Allow Mail" (fw Server-side) and the "Schedule Changes Email Sendout" (fw Client-side) features to be enabled and working.

 
#330523

Added the booked "objectClassId", "objectClassName" and "objectClassRef" to the GET /events endpoint.

 
#330523

Added “Binders” data (including Custom Fields and Events in Binders) to the GET /project endpoint via the fwRESTapi.

 
#340400

Added "booking customs" to the GET /event endpoint, see details.

See Details

This is supported since v6.8 Beta rev. 20194.

For more info use the latest "swagger.json" v0.8.6 or later from here:
https://support.farmerswife.com/en/support/solutions/articles/17000089578-the-farmerswife-server-s-rest-api-for-your-own-3rd-party-integrations

 
#340400

Added "groupingId" and "memberOfGroupingId" in the /event endpoint, for creation (POST) and updates (PUT), see details.

See Details

“groupingId”: “parent", = "the parent object" under which "child" Objects, i.e. "memberOfGroupingId" can get grouped under.
"memberOfGroupingId": “parent" = this parameter is used on the "child" Objects, which in turn uses the info of the "groupingId" to identify to which "parent" it belongs.

Only either use “groupingId” or "memberOfGroupingId" per Object. Please be aware, that on "POST" you do not have any "id" info. You can here put whatever, there is no verification going on, if the used parentId info exists in the database or not. It's only used as reference within this context. I hope this makes sense.

This is supported since v6.8 Beta rev. 20233.

For more info use the latest "swagger.json" v0.8.7 or later from here:
https://support.farmerswife.com/en/support/solutions/articles/17000089578-the-farmerswife-server-s-rest-api-for-your-own-3rd-party-integrations

 

Added filters to GET /company endpoint and the new PUT /contact/{id} for being able to update Contact Customs and Name.

 
#330523

Added multiple updates on the fw REST API Swagger.json documentation, see details.

See Details

For GET /event:id endpoint added:
"cursor"
"nextCursor"

For PUT /event:id fixed:
The wrong response value "204" is now correctly fixed to be "200".

For GET /event endpoint added:
"isFrameworked"
"involvedHeader"
"objectName"
"objectFirstName"
"objectLastName"

For GET /event/changes endpoint added:
"isFrameworked"
"involvedHeader"
"displayNote"
"objectRef"
"objectName"
"objectFirstName"
"objectLastName"
"objectInventoryNumber"
"objectClassID"
"objectClassRef"
"objectClassInventoryNumber"
"objectClassName"
"eventsChangesLastUpdate"

 
#340472
#339708

Added projectNumber to the GET /event endpoint and objectRef, objectClassRef to GET /timereport endpoint, see details.

See Details

Added projectNumber to the GET /event endpoint and objectRef, objectClassRef to GET /timereport endpoint.
Updated Swagger doc to version 0.8.8.

For more info use the latest "swagger.json" v0.8.8 or later from here:
https://support.farmerswife.com/en/support/solutions/articles/17000089578-the-farmerswife-server-s-rest-api-for-your-own-3rd-party-integrations

 
#330523

Added support to update "Booking Objects Custom Fields" via PUT /event{id} endpoint, see details.

See Details

To be able to start using this, either use the latest "swagger.json" file from our knowledgebase, search for "REST api"

Or, copy the "Body" structure" from GET /events.
Ensure you have the ""involved": [" section, and add the following info:
"customs": [
{
"type": "entry",
"label": "Order Number",
"value": "All this here IS the value to be updated via the fwRESTapi on this Booking Object Custom Field"
}

 
#340400

Added to the GET /event endpoint: status, statusSysName, statusSysId, see details.

See Details

Updated Swagger doc to version 0.8.9.

For more info use the latest "swagger.json" v0.8.9 or later from here:
https://support.farmerswife.com/en/support/solutions/articles/17000089578-the-farmerswife-server-s-rest-api-for-your-own-3rd-party-integrations

 
#330523

Added two new “changesSubType” values for the GET /event/changes endpoint, see details.

See Details

The two new “changesSubType” values for the GET /event/changes endpoint were added to be able to know depending on the Project Web Visibility configuration, when an event was stopped or started being visible.

"changesType": "change",
"changesSubType": "web_visibility_on",
or:
"changesSubType": "web_visibility_off",

 
#330523

Changed the GET /event/changes endpoint to stop relying on "Scheduled Changes Email" functionality, see details.

See Details

Now listing also Booking Objects removals.
Now in addition to “changesType”: “delete”, support for the following “changesSubTypes” values was added: “deleted_booking” and “deleted_booking_object”.

The Toolbox > Settings > Server Setup > setting for data retention has been renamed to: "Enable REST Api Data Retention For Events Changes".

 

New filters and attributes in GET /event and GET /project endpoints

See Details

/event endpoint: Added "bookingNumber" and filters by "bookingNumber" and "projectID".
/project endpoint: Added "isActive" GET parameter to be able to display Inactive Projects.

This is supported since v6.8 Beta rev. 20231.

For more info use the latest "swagger.json" v0.8.7 or later from here:
https://support.farmerswife.com/en/support/solutions/articles/17000089578-the-farmerswife-server-s-rest-api-for-your-own-3rd-party-integrations

 

Rate Cards

When force applying a Rate Card, it will no longer apply zero rates, see details.

See Details

Previously, when you used a Rate Card's "Force Apply" function, items where the Object had a default Rate of zero (0.00) would also get reset to zero.
The point of having a zero rate on an Object is normally, that you're supposed to enter the rate manually when you know what it is. After that it doesn't make much sense to ever remove that manually entered rate. So now the "Force Apply" function no longer does.

This also applies when you force apply rates from Budgeting or Multiple Currencies.

 

Reports

#340281

Fixed a bug introduced in rev 19896 causing that the User Report and Object Report wrongly stopped working.

 

Schedule Changes Email

#333285

Implemented for the Schedule Changes Email Sendout (SCES) > Pending Users Approval that it will not trigger a SCES email, if a Booking is created/removed and re-booked on the same User and Day.

See Details

If a User with Pending Users Approval Permission (Web Permission: User Must Accept Or Decline New Bookings) is booked on a Framework (this is communicated via a Schedule Changes Email) and then this User (with status "Pending Users's Approval" is removed and re-booked (within minutes) in the same Framework Cell, there will now be no Schedule Changes Email sent out.

 
#338839

Fixed a bug causing wrong high-lighting in the Schedule Changes Email if the Framework Name and Object/User Note are the same, see details.

See Details

If a Framework Name gets changed and now matches the Object/Username, the Framework Name wasn't correctly highlighted in blue in the Schedule Changes email. This is now fixed.

 

Server

#343395

Fixed a bug when the server.cfg had values containing space characters, see details.

See Details

The server.cfg config file contains a list of key-value pairs for certain fw Server app > General tab settings.
There was an old bug that prevented the value from containing space characters. Everything after the first space character in the value was just discarded. That bug is now fixed.

 

Time Report

Added setting that makes the Time Report icon show when someone has reported more than was booked, see details.

See Details

There are 2 new checkboxes called "Timereported More Than Booked" in these places:
- Toolbox > Settings > Projects Tree
- Toolbox > Settings > Hourline

When activated, the Time Report (TR) icon on Bookings will indicate when someone has reported more time than what was booked. So e.g. if the person was booked 8 hours on a day, and they reported 9 hours, the TR icon will have a small exclamation mark on it and the tooltip will say "Booked: 8, Used: 9".

 
#307828

Fixed for Ad-Hoc Timereports to skip the warning when the Break time is outside of the booked time, see details.

See Details

Before, when you created an Ad-Hoc Timereport and then also added a Break to the Timereport, a warning would appear saying that the break is outside the Booked Time (because the booked time is from 06:00-06:00 = 0 hours on Ad-Hoc Timereports).
Now this dialogue will be skipped on Ad-Hoc Timereports.

 

Toolbox

In the Toolbox > Objects tab: Added options to display Object Custom Fields in the Toolbox, see details.

See Details

The "Object Custom Fields" can now be displayed in fw Client > Toolbox > Objects tab > Display.
It will first show the Object Custom Fields Template's Name and then you can chose the fields you want to display.
They will be added as columns to the Toolbox > Objects tab in the order you select them.

 

Changed filter name from "All" to "All (Not Archived)" in fw Client > Toolbox > Projects, see details.

See Details

Previously the "All" Filter in the Toolbox would NOT include Archived Projects but it could be confusing when searching for Projects (including archived). This is now updated and works the same way as in Advanced Project Search (fw Client > main module bar "Projects".

 

In the Toolbox made the search fields on all tabs a bit wider.

 

User & Object Report

#30523
#333632

Added Binder Custom Fields to the Users and Objects Report to the Events section called "Custom Fields (Binder)".

 

Users

Made the Modify User and fields bigger, see details.

See Details

In fw Client > main module bar "Object Manager" double click on any user to get to the Modify User window.

 

Virtual Bookings

#340910

Added ability to edit the Name of a Custom Extra in Virtual Bookings, see details.

See Details

Opening the "Edit Rates" pop-up on a Custom Extra will now also include the "Name" field and the pop-up is renamed to "Edit Custom Extra".
You can also access this pop-up by double clicking on the Extra's Name.

 

Web & Mobile Client

Added new "Booking Colors" settings in Toolbox > Settings > Web Share Settings, see details.

See Details

In fw Client > Toolbox > Settings > Web Share Settings > "Booking Colors", there is now a section with around 10 Booking Color related settings.
These settings control what color Bookings get in the Web Client and the iOS fw app.

 

Added new color settings for "User Approval Status" and "Booking Invoice Received Status" in Toolbox > Settings > Web Share Settings, see details.

See Details

In fw Client > Toolbox > Settings > Web Share Settings, below the "Booking Colors" section, there are now two more sections called:
- User Approval Status
- Booking Invoice Received Status

The settings in these sections replicate the same functionality as in Toolbox > Settings > Display, except that they control what color Bookings get in the Web Client and the iOS fw app.

Please note, that by default after the upgrade the colors are the system default ones. You have to reset them to your own colors after upgrading to this version.

 

Web Client

Updated “log4j” to latest version.

See Details

If you need more information, please contact supportATfarmerswife.com.

 

Upgraded Jetty to v9, see details.

See Details

Any customer who has SSLed the built-in Jetty web server will need to apply changes; please contact supportATfarmerswife.com for more info.

 
#340328

Fixed a bug where a User couldn't see Projects in their Division on the Web Client even if the "Show Projects In His Division" Web Permission was enabled.

 

WebCal

#342444

Fixed a WebCal Event subscription bug.

 

Work Orders

#322490

The Project Work Order modified date is now shown instead of the User creation date in the Project Work Order window after modifying.

 

Previous Releases