Back To Release Notes List



Back To Release Notes List

#18623

09. Oct 2019

6.5 Release

  • 2 Warnings
  • 4 HOT Features 129 Features
  • 31 Other changes
  • 109 Bug fixes

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

v6.5 Release rev. 18623, was released 9. October 2019.

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

Native v6.5 changes:
- 2 Warnings:
1) "Windows-x64 ONLY: A FULL fw Client desktop app upgrade is necessary. To assist the "full-installer-download-auto-client-upgrade-mode" IS active"
2) "IMPORTANT macOS Catalina is NOT yet supported on v6.5 - and see details for options if already upgraded to Catalina."
- 4 HOT Features
- 129 Features
- 31 Important Other change
- 200+ Bug fixes

... and also take a look into the new highlights summary "Whats New in v6.5": https://blog.farmerswife.com/farmerswife-release-v6.5

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

Upgrading to v6.5 - see details!

Basics
- You need to be on a "active" Support subscription with us past the date of the actual release of this version.
- You need to have a "Version 6.5" license at hand, before starting the upgrade process.
- We recommend that you first get a proper separate "TEST environment" up and running; see info here within the Release Notes "top" section, or use this link:
https://support.farmerswife.com/en/support/solutions/articles/17000059642-how-to-use-the-server-cfg-when-working-with-a-separate-test-farmerswife-server-

IMPORTANT:
ONLY upgrade from 6.4 SP2 rev. 17824 or later!
The "simple" built-in in-application farmerswife (fw) Client auto-upgrade mode is supported in MOST cases.
IMPORTANT: Only if using the new "Windows-x64" fw Server installer, then on Windows this will trigger the "Full-Installer-Download fwClient-auto-upgrade" mode!

farmerswife on Mac is NOT yet "macOS Catalina" optimized!
The farmerswife Server and Client apps on Mac are unfortunately NOT yet "macOS Catalina" optimized!
Both apps on Mac are still 32bit.
DO NOT UPGRADE your Mac to macOS Catalina.
We have been and are still working on the new "macOS-x64" version; but it's not yet ready. First public Beta versions are expected to become ready within the next 2 to 8 weeks.

New "low-level libraries" fw Server AND fw Client "Windows-x64" installers:
A new low-level-libraries-upgraded version for Windows called "Windows-x64" is now available!
If this is used to upgrade the fw Server application, then on Windows the "Full-Installer-Download fwClient-auto-upgrade" mode is again active on the upgrade past v6.5 Beta 10 rev. 18249)!
This will then help all users to install the new 64bit fw Client desktop app on Windows!.
Each user on Windows can use 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 manual upgrade process.
NOTE: The simple built-in auto-fwClient upgrade will work again for any "Windows-x64" farmerswife Client desktop app, which was once manually upgraded past v6.5 Beta 10.

The Print Designer Page Breaks and Rectangles have ben re-written
This will require a couple of manual changes for the Advanced Users after the upgrade!
More info here => https://support.farmerswife.com/solution/articles/17000089047-v6-5-print-designer-page-break-re-write-related-changes

NEW “Built-In Printer” using “Ghostscript” and multiple fw-Server-sided-PDF-Export-related fixes were implemented, which were mostly needed when this gets triggered via the iOS fw app, the Web Client or the Mobile Web Client.

We've implemented many optimisations and performance improvements!
Overall big improvement on the "random low level fw Server app crash without usable log info”.
And the fw Server-side “Nightly Forced - Restart” is now rock-solid!

Upgrading
- Your farmerswife Server application must have been running on version 6.4 SP2 rev. 17824, 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 more detailed information in the Upgrade Instructions.
- 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.

farmerswife Server upgrade on Mac:
- 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 6.1 license files into the "system" of the NEW WIFE server.
- Double click on the NEW farmerswife Server package icon to start the actual upgrade process.
- Once everything worked out fine, remove or update any Dock or Desktop links. And if needed remove the OLD Server package; because up until now, this was a working "roll-back" backup, just in case something went wrong.
- After the upgrade, start the farmerswife Server as usual.

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

farmerswife Server upgrade on Windows and Linux:
- Make sure you are logged into the host machine with the same admin user as on the initial installation of the farmerswife server application.
- Copy the NEW farmerswife Server installer file to the machine hosting the WIFE Server.
=> On Windows this is a .exe file
=> On Linux use these instructions: https://support.farmerswife.com/a/solutions/articles/17000026005-server-and-client-installation-linux
- Quit the running farmerswife Server.
- Now copy the new v6.5 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.

IMPORTANT on all host machines running the fw Server application:
Ensure to remove any and all "Java (Oracle)" versions as part of this upgrade process!
Especially REMOVE the deprecated OLD v1.6 and 1.7!!! We strongly recommend to remove them ALL.
And instead, install open-source "OpenJDK" as per these instructions:
https://support.farmerswife.com/en/support/solutions/articles/17000095590-how-to-replace-java-oracle-with-openjdk

The farmerswife Client desktop apps will auto-upgrade ...

... if already running on version 6.4 SP2 or later:
- on Mac and Linux by using the "simple in-application" auto-upgrade mode; "normal user" Operating System permissions (Read / Write) are sufficient.
- on Windows it depends on which OS platform is used on fw Server-side:
IF the fw Server is hosted on Mac or Linux, then the "simple in-application" auto-upgrade mode applies; "normal user" Operating System permissions (Read / Write) are sufficient.
IF the fw Server is hosted on Windows, and the new "Windows-x64" installer is used, then ONLY on Windows will the "Full-Installer-Download fwClient-auto-upgrade" mode be active and OS admin user permissions Read, Write AND Execute are necessary on the initial upgrade.

... if BELOW version 6.4 SP2 and regardless on which OS the fw Server application is running on:
... by using the "FULL" Client upgrade process; OS admin user permissions Read, Write AND Execute are necessary on the initial upgrade.

IMPORTANT for the supported auto-upgrade functionality in later versions:
For the farmerswife Client applications 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.
But when auto-upgrading on Mac with a mix of Admin and Standard users, 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.

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 helpful information for us.

Latest free universal iOS farmerswife app v5.0.828 is available on Apple's App Store, click on "+" to see the details!

The latest iOS farmerswife app is v5.0.828, and is available on Apple's App Store since 08-April-2019.
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 work, as this 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 and later versions!

This means:
You should upgrade as soon as possible to the latest released version 6.5, but at least to v6.1 SP1 rev 16195.
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 WIFE Server.
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 WIFE Server installation.

You can always use a WIFE Server in "demo mode" (also with your DB files) and it will run for 60 min. and you have 40 sessions.
An additional "TEST 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 WIFE 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 WIFE Server's host machine, etc.
All this functionality is therefore also enabled by default on a separate new TEST WIFE 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 WIFE 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 WIFE Server application.
You use this file to ensure certain settings are NOT enabled on your TEST WIFE 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 WIFE Test installation works like this:

- Quit your farmerswife PRODUCTION WIFE Server.
- Create a file called "server.cfg" within your PRODUCTION WIFE Server's "system" folder.
- Start up your PRODUCTION WIFE 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 WIFE Server application on your test machine.
- Now copy at least the "system" folder from your WIFE "production" Server to within your "test" WIFE 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 WIFE Server, edit the server.cfg file with a text editor application within your TEST WIFE 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 WIFE 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" WIFE 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 WIFE 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 WIFE Server as mentioned above, you can save time in the future by only copying these files from your PRODUCTION WIFE Server > from within the "system" folder:
- current45.efdb
- fwdb.db3
- histories.db3
- despatches.db3

About these Release Notes, Disclaimer and Legal Information

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

Client Upgrade

IF using the new Windows-x64 installers, the “Full-Installer-download fwClient-auto-upgrade” mode is active again with Beta 10, see details.

See Details

Local OS user read, write AND execute permissions are required!
The installer can be package-distributed by using your own system.
"very silent" mode is supported.

 

Installers

IMPORTANT macOS Catalina is NOT yet supported on v6.5 - and see details for options if already upgraded to Catalina.

See Details

The farmerswife Server and Client apps on Mac are unfortunately NOT yet “macOS Catalina” optimized.

DO NOT UPGRADE your Mac to macOS Catalina.

We are preparing a beta of the new 64-bit version of our Mac apps.
We expect to be able to have a beta available in the coming weeks, but for now it is still in internal testing.

We advise turning off auto updates for your macOS to avoid accidentally upgrading to Catalina.
In the System Preferences > Software Update > "Automatically keep my Mac up to date" <= OFF.

If you accidentally upgraded to macOS Catalina, you can still use the iOS farmerswife app, the Web Client and Mobile Web Client in order to see your schedules, etc.

If you need to use the farmerswife desktop application, please consider rolling back to the previous running macOS on your Mac.

This might be helpful, found via Google-search: https://www.imore.com/how-downgrade-macos

 

ActiveDirectory

Implemented on fw Server-side a new "MSAD sync notification email" Field to then to send a list on user ho were Created, Activated or Deactivated, see details.

See Details

Added on server an email field. If added then an email to this address will be sent with a list of users who were: Created, Activated or Deactivated.

 

Activities

Fixed a bug causing the default Activity to wrongly not being applied when booking Objects with only one Activity configured.

 

Advanced Project Search

Added "Without Bookings After Date" search field to Advanced Projects Search, Projects search area

See Details

In the Advanced Project Search it is now possible to search for Projects which don't have any bookings after a certain date.
Select a date in the new Project search field "Without Bookings After Date".
Search results will now only show Projects with no bookings after that date.
This is useful for finding dormant Projects for closing/archiving purposes.

 

Booking History

Added "Swapping" actions from Dispatch to Booking's history, see details.

See Details

When an Object got swapped in the Dispatch module, there was no history entry for this in the corresponding Booking (if any). Now when swapping an Object with another, or swapping an Object Class with one of its members, the Booking History will state:

Swapping an Object class with Object Class member:
"Removed (Dispatch): Object Class Name
Added (Dispatch): Object Class / Object Name / Inventory Number"

Swapping one allocated member of an Object Class with another:
"Removed (Dispatch): Object Class / Object Name / Inventory Number
Added (Dispatch): Object Class / Object Name / Inventory Number"

 

Added information inside of the Booking history if the changes to the Booking have been made from the corresponding Dispatch

See Details

The Booking history will now show additional information if the changes to the Booking have been made from the Dispatch indicating"(Dispatch)" in the Booking history line.
The Booking history line will always start with the date dd-mm-yyyy / hh:mm (thumbnail icon).

Actions that will generate a Booking history line when changing something in the corresponding Dispatch:

- Hitting OK the first time you create the Dispatch of the Booking: Time (Dispatch): Time
- Changing the Out or Return Date or Time of a Dispatch: Date And . Time (Dispatch): Date / Time
- Swapping an Object with another Object of the same Object Class: Removed (Dispatch): Object Class / Object Name/ Inventory Number
and Added (Dispatch) Object Class / Object Name / Inventory Number
- Swapping an Object Class with a real Object from that Object Class: Added (Dispatch):Object Class / Object Name / Inventory Number
- Removing an Object from the Dispatch: Removed (Dispatch): Object Class / Object Name / Inventory Number
- Adding an Object from the Dispatch: Added (Dispatch): Object Class / Object Name / Inventory Number

Actions that are not listed in the Booking history:
- Adding notes to Objects
- Adding notes and Inventory Numbers to Object Classes or External Objects
- Verifying Objects
- Using the option to "Move To New Dispatch"
- Unlinking a Booking from its Dispatch
- Changing the Dispatch Status

 

Booking Templates

#220015

Added functionality to "Shared Booking Templates", see details.

See Details

You can set Booking Templates to Shared or Not Shared as well as to Active and Inactive. (Highlight a Booking Template and do a right mouse click or click on the drop down menu selecting the wanted option.)
It is possible to show Inactive Booking Templates via the drop down menu in Toolbox > Booking Templates > Show Inactive.
Inactive Booking Templates can't be applied and used in the Longform.


You can also now copy Booking Templates. The copied templates will have the "(copy)" in the end of the name. If you copied an inactive Booking Template the copied Booking Template will be automatically set to active.

There have been added three columns in the Toolbox > Booking Templatet's tab:
"Shared": showing who shared a Booking Template. Adding "creator + time" (copy will reset the creator to who copied the Booking Template).
"Last Modified By": showing the User name, date stamp and time.
"Created By": showing who created the Booking Templates (User name /date and time stamp)

The option "Copy From Another User" was renamed to "Add From Another User". It is possible to multi-select Users to add their Booking Templates to your own Booking Template tab. Even inactive Booking Templates will be copied.

You are now able to work on Booking Templates in the 2nd Session. Any changes made in the 2nd session will be saved.

There are two User permission settings that apply, below their behaviour:

Behaviour for User Permission: Can Create/Modify/Delete Their Own Shared Booking Templates:

Rename: No, with popup message that the template is inactive
Copy: Yes, with popup message that the template is inactive >New template will be active.
Delete: YES, after popup message that this template is inactive

Booking Template is active and shared by someone else:
Rename: Not possible
Copy: Yes (new active template)
Delete: Not possible

Booking Template inactive and shared by someone else:
Rename: Not possible
Copy: Yes (with popup message that the template is inactive) *New template will be active
Delete: Not possible

Booking Template Inactive and Shared by yourself:
Rename: No, with popup message that the template is Inactive
Copy: Yes (with popup message that the template is Inactive (the copied templates will be active)
Delete: Yes, after popup message that the template is Inactive

Behaviour for User Permission "Can Create/Modify/Delete All Shared Booking Templates:

Setting Shared Booking Template from Other Users to Active and Inactive is possible.
Share and Un-share: Is possible, but with a popup message that this is a shared template from another User: Confirm / Cancel

Template is inactive and shared by another person:
Rename: No, with popup message: Booking Template is Inactive
Copy: Yes with popup message: Booking Template is Inactive.
The copied Template will be active.
Delete: Yes, with a popup message that you are about to Delete a Shared Template that is not yours: Option: Confirm Remove/Cancel

Template is inactive and Shared by yourself:
Rename: No, with popup message: Booking Template is Inactive
Copy: Yes, after popup: Booking Template is Inactive
Delete: Yes, after popup: Booking Template is Inactive

Your own BookingTemplate is Inactive and Not Shared:
Rename: No, with popup notice: Booking Template is Inactive
Copy: Yes with popup notice: Booking Template is Inactive.
The copied Template is then active.
Delete: Yes, after popup message that this template is inactive

 

Framework Bookings that are saved in Booking Templates will show the Conflict window when reapplying and causing any conflict

See Details

Before, when reapplying a Framework Booking that was saved in the Booking Templates, no conflict was shown. The Framework cells would only turn into the conflict colour.
Now a single Conflict window will popup showing all conflicts in this one window. You can't inspect this window, just OK it. It is only for your information.

 

Bookings

Added for "Edit Booking" window > "Involved" pane and "Dispatch Edit" window: Showing amount of Virtual Objects and Name in one line, see details.

See Details

In the Edit Booking window's "Involved" pane Virtual Objects that were added in a bulk-action (when you chose a quantity higher than one once the dialogue pops up: "Type Amount For: Object") will display this in one line showing the amount before the Object Name and a drop-down arrow before it, to be able to expand and collapse. By default the Virtual Objects are expanded.

In the Edit Dispatch window the Virtual Object is set to be expanded by default and the amount is shown in the "Quantity" column. To change this setting, go to the "Check Out" or "Check In" window's sub menu to toggle off the setting "Expand Groupings By Default".

 

In fw Client > Toolbox > Settings > Class / Object you can now control the dialog: "When Replacing Keep The Class, Activity And Rates". See details!

See Details

Before when replacing Objects you would always get a dialogue that asks "Do You Want To Keep The Old [Class,] Activity And Rates?" even though you might not be using Rates, Classes or Activities.

A new setting in fw Client > Toolbox > Settings > Class / Object > "When Replacing Keep The Class, Activity And Rates" now controls whether to get the pop-up message or rather have a default "Yes/No" behaviour.

1) "No" => When replacing, it will ask to select the Class and Activity and the new objects own rates will apply.

2) "Yes" => When replacing, the new Object will keep the old Object Class, Activity and Rate (IF it also belongs to the same Class and/or has same Activities, else own Primary Class will apply).

3) "Ask" => When replacing you'll be asked if you want to keep the old Class, Activity and Rate:
- IF NO => same as above 1).
- IF YES => same as above 2).

Important: If the User has the Permissions "Can Edit Booking Rates" or "Can Select Booking Activity" disabled, then this setting will be forced set to use "No" and the user won't be able to change it.

 

When cancelling a project it will be set to inactive. It is also possible to hide Bookings of cancelled projects with a new Toolbox setting.

See Details

A new behaviour has been implemented to automatically set the Project to inactive if it is cancelled. (Project statuses are available at the bottom of the project window)

There is also a new setting in relation to cancelled projects: "Hide Cancelled Projects From Timelines And Reports" in Toolbox > Settings > Server Setup.
When you have this setting enabled and change project status to "Cancelled" the Bookings will no longer show in the Hourline, Object tree, Personnel tree, iOS timeline and Web Client timeline. They still show when loading the Project in the Project tree.
The Bookings will also be removed from Financial Reports, Object Reports and User Reports. You can still print out a Project Report. (If you need to still be able include lines from cancelled projects in your Financial Reports do not use the setting.)

If the "Cancelled" Status is un-ticked, the Project Bookings will show again in the timelines, the Project however will remain not active.

 

You can now remove a Booking even if the Project for it is currently open/in use by another user

See Details

Previously if one user had a project window open, it was not possible for other users to delete bookings from that project. This is now possible.

 

Changed wrong behaviour on "Do You Want To Keep Rates And Activities" setting. See details!

See Details

Before when replacing Objects you would always get a dialogue that asks "Do You Want To Keep The Old [Class,] Activity And Rates?" even though you might not be using Rates, Classes or Activities.

A new setting in fw Client > Toolbox > Settings > Class / Object > "When Replacing Keep The Class, Activity And Rates" now controls whether to get the pop-up message or rather have a default "Yes/No" behaviour.
1) "No" => When replacing, it will ask to select the Class and Activity and the new objects own rates will apply.

2) "Yes" => When replacing the new Object will keep the old Object Class, Activity and Rate (IF it also belongs to the same Class and/or has same Activities, else own Class or Activities will apply).

3) "Ask" => When replacing you'll be asked if you want to keep the old Class, Activity and Rate:
- IF NO => same as above 1).
- IF YES => same as above 2).

Important: If the User has the Permissions "Can Edit Booking Rates" or "Can Select Booking Activity" disabled, then this setting will be forced set to use "No" and the user won't be able to change it.

 

Fixed a bug by which replacing Objects only for a specific time range on a multi-day booking, was replacing on all days.

See Details

After confirming the "Use Time Range?" dialog, the Object would still be replaced for the whole duration of the booking.

 

Fixed a bug that was causing that when swapping on the same day two Users who had accepted their jobs, the Job showed still as accepted and the Schedule Changes Email would display wrong details.

See Details

Now, when swapping on the same day two Users who had already accepted their jobs, each of the Booking Requests go back to Pending User's Approval.
And the Schedule Changes Email that the Users receive correctly shows the details of the New Request details and the Deleted Event, so they know they had to go back to their schedule to Accept the new Job.

 

Fixed a bug that was not giving the option to choose date when pasting only one copied Booking when using the Copy Bookings functionality within the Edit Project window

 
#316329

Fixed a bug when copying or repeating a "Booking" the "Created By" detail is now showing the correct Username of who copied it, see details.

See Details

Before this bug fix the "Created By" field on the new copied/repeated Booking was still wrongly showing the Username of who had created the original Booking.

 

Fixed a bug when replacing an Object that has "Object Class Accessories" assigned, wrongly "real" Accessories were allocated, see details.

See Details

When replacing an Object which has an "Object Class Accessory" with another Object which also has an "Object Class Accessory" assigned to it, this wrongly swapped the "Object Class Accessory" with a real Object.
Now when replacing Objects, the Accessories won't be allocated, it will now still show the Object Class Accessory.

 
#311177

Fixed a bug where modifications on Booking Custom Fields or "Predefined Services" and "Ad Hoc Extras" would not be saved, if changes were also made in the "Involved" section.

 

Fixed bug when trimming a multiday booking only on a specific time range, the new time would be ignored

 
#321766

Fixed fw Client crash when copying Bookings for some Objects in the Long Form Object Tree using cmd / c and dragging the Bookings to another date.

 

Yellow Booking popup and Booking window shows owner's full name if you enable setting Inventory / Full Name in Toolbox > Settings > Display

 

Budgeting

Added "Profit" and "Margin" columns on the Budget window, see details.

See Details

In the Budget window, there are now new columns that can be displayed using "Edit View" in the view settings menu:
- Profit (Budgeted, Compare, To Date, Invoiced). This is basically (Sell-Buy).
- Margin (Budgeted, Compare, To Date, Invoiced). This is the profit margin, as a percent from dividing (Sell-Buy)/Sell.

 

Added a new setting that for automatically forwarding Price Agreements.

See Details

In the Budget window, the "Tools" menu now contains a new setting: "Forward Price Agreements To Project Views > No/Ask". Defaults to "No".
If changed to "Ask", whenever you create or update a Price Agreement on an Active Budget, you will be asked if it should get forwarded to the "To Invoice / Invoiced" and "Actuals" views.
The same will happen when you toggle the "Active" flag on a Budget.

 

Added filter and warnings for when "Forecast" for Sell is over "Budgeted".

See Details

There are now two new settings in the View Options menu inside the Budget window:
- "Show Details > None/All/Over Budget": When this is set to "Over Budget", it will only show Budget Details where "Sell (Forecast)" is higher than "Sell (Budget)".
- "Show Warnings > Over Budget": This will add warning icons in the "Sell (Forecast)" column where "Sell (Forecast)" is higher than "Sell (Budget)". It will also make those numbers red.
Either or both of these settings can be used to find lines where you're going over budget.

 

Added the ability to Lock Budgets.

See Details

There's a new User Permission called "Can Lock/Unlock Budgets" (default Off).
If a User has "Can Lock/Unlock Budgets" permissions, he will see an "unlocked" icon next to the budget name.
If clicked, the Budget will go into a locked state and can't be edited by anyone.
Mousing over the lock icon reveals a tooltip with the info of who locked it and when: "Locked by [user name] On [date / time]"
Locked Budgets cannot be renamed, nor deleted. But options "Duplicate" and "Copy To Global Template" are available.

Actuals can still be attached/detached to the Budget Details of a locked Budget, but you can't e.g. add, remove or edit existing details.
You can still use the following options on Budget Details:
- "Copy Budget Line", to allows user to copy from a locked budget and paste into a new unlocked budget on same project.
- "Forward Budget Line To Actuals"

Anyone with "Can Lock/Unlock Budgets" permissions can unlock the Budget for further editing.

Users with no permission to lock/unlock will only see the lock icon next those Budgets that are locked, but Budgets that are not locked do not show the "unlocked" icon for this user.

 

Enhanced the "Booking Attach Actuals To Active Budget" feature, so the first Actual defines Budget for others added to the Booking. See details.

See Details

Added new settings to Toolbox > Settings > Booking Defaults:
"Attach Actuals To Active Budget"
- If this is enabled, when creating a new booking a pop up window will ask if to attach the actuals to an active budget or if you do not want to "allocate". If you choose a budget, then all objects that you add to this booking will be attached to the selected budget. Including adding/editing the Booking from Web Access tiers and through Time Report.

"Always Attach Actuals If There Is Only One Active Budget"
- If you have this enabled, It will not ask if there is only one active Budget but attach immediately. All objects added to any booking will be attached to the active Budget.
- This setting is only available if you have enabled the first one.

"Ask "Attach Actuals To Active Budget" Per Object"
- If you have this enabled a pop up window will be displayed each time you add an object to a booking.
- This setting is only available if you have enabled the first one and not enabled the second.
- If this setting is enabled the feature is only supported on Desktop Client. Changes and additions to Time Report of the booking through Web Access tiers are not attached.

Known Limitations:
- If a Web User is time reporting extras to a Booking that is “linked” to an Active Budget already, the Actuals added though the Web/Time Report are not attached IF at the same time an Advanced User has the Project or Budget Window open.

 

It's now possible to collapse/expand the box that contains detailed info about the selected Budget.

See Details

Just above the budget table, there's a large box containing the settings for the selected Budgets, e.g. the creator and Custom Fields.
That box can now be collapsed. The expand/collapse state will be remembered until you restart the application.

 

Made the table headings and left columns "sticky", so they still show when you scroll.

See Details

When you had a Budget that was taller than your budget window, and you had to scroll, it was easy to lose track of which columns were which.
The headings would scroll out from the view.
Now this no longer happens as the column headings will now stick to the top of the window.

Similarly when you had a lot of columns and had to scroll horizontally you would lose track of the rows.
Now the "Account" and "Description" columns will stick to the left side of the window.

 

Moved the "View Options" buttons so they're more easily accessible.

See Details

In both the main Budget window and in the Actuals pane, the "View Options" buttons (=eye icons) were located at the top-right edge of the tables.
So if a table was wider than the screen, the "View Options" button was also located outside the scrolling area.
Now they have been moved. In the main Budget window, it's located to the right of the "Expanded" selector. In Actuals, it's at the right side of the search entry.

 

Price Agreements are now also synced with the "Actuals" view.

See Details

In the Budget window, you could already use the "Forward To Final / Invoice View" option on a list of Price Agreements, and have it automatically put actuals into that Price Agreement when you attach them to Budget Details.
Now that also works for the "Actuals" view as well. So:
- There's a new "Forward To Actuals View" option in the menu.
- When you attach Actuals to Budget Details, it will perform the same auto-attaching to Price Agreements on the "Actuals" view, as it previously only did on the "Final / Invoice" view.

 

The Sell total for each Budget is now displayed in the list of Budgets.

 

You can now add notes on Budget Categories and Accounts in your Budget, see details.

See Details

In the Budget window, next to each Category/Account name, there's now a note icon. Click on it to enter a note for that Category/Account in the currently selected Budget.
Note: When you select *multiple* Budgets, you won't be able to view or edit these notes.
The note can also be used in the Financial Reports. They are found inside the "Budget Category", "Budget Account (Main)" and "Budget Account (Assigned)" groupings. The note will also show when you report on multiple budgets, and the prerequisite for the notes to show that the report includes the grouping Budget.

 

Moved the "Attach Actuals" buttons to the top.

See Details

In the Actuals pane, the buttons called "Attach Actuals" and "Attach Selected Actuals" were found below the list of Actuals, which meant you had to scroll through the whole list to find them.
Now they are instead located at the top.

 

Restricted "Multiplier" to only allow positive integer numbers, and fixed crash.

See Details

The "Multiplier" value on Budget Details can be used to indicate how many instances there are of a certain line. This is then used with the "Forward Budget Details To Actuals" or "Raise Purchase Order" functions, such that it adds as many lines as the multiplier specifies.
With this in mind, it doesn't make a lot of sense to add e.g. 1.5 as multiplier, since it won't be able to add 1.5 lines to the Actuals.
Therefore, the Multiplier field is now restricted to positive (>0) integer values.
Note: Any existing decimal Multiplier values will still retain their current values.

 

When dragging lines in Scheduling Mode, it now respects the Multiplier.

See Details

In Scheduling Mode, when you drag a line that has a Multiplier value of 2+ into the timeline, it will now allocate as many objects as the multiplier. Previously it would only allocate one.

 

When using "Show Details > None", all Details are now hidden - even if they contain Actuals.

See Details

Previously when you selected to hide Details, they would still show if they contained Actuals (unless Actuals were also hidden).
This is now changed so that the Details are hidden but their Actuals are still showing.

 

Fixed a bug wrongly disabling the "Forward To Actuals View" on Price Agreements, see details.

See Details

When the "To Invoice / Invoiced" View is set to include Budget Details, the "Forward To 'To Invoice / Invoiced' View" option is disabled, because the Budget's Price Agreements are already automatically brought into the view.
The bug was that this also made the "Forward To 'Actuals' View" action disabled. That is now fixed.

 

Fixed various bugs in Budgeting > Scheduling Mode when dragging Budget Details to a day, see details.

See Details

In Budgeting > Scheduling Mode, when you dragged Budget Details to a day in the calendar, it would not allocate the correct quantities for each dragged line.
The order of the added Details was also not maintained in the new Booking.
These and other smaller issues are now fixed.

 

Cirkus Sync

Implemented multiple performance improvements on the Cirkus.com Integration, see details.

See Details

- Now, farmerswife will query for changes on Tasks since the last sync and process them, instead of query all Tasks to evaluate changes after.
- The first sync after a fw Server restart will be a Full Sync.
- The button “Update Now” also triggers a Full Sync.
- Now, it’s also possible to enable Cirkus logs, by adding the var CIRKUS_LOGS_ENABLED with value 1. This will write log lines in the file fw Server/system/customlog.cirkus.log.

 

Class Bookings

#106849

Added the possibility to expand/collapse "Object Accessories" and "Group Members" in the Edit Booking window > Involved pane and in Edit Project window.

See Details

Also added a new option under the Eye menu of the Edit Project window to "Show Accessories / Groups Involved" > Expand All / Collapse All.
This new option allows expanding / collapsing all Object Accessories and/or Group Members at once.

 

Client

Fixed a bug wrongly causing fw Client desktop crashes in the Logout process, see details.

See Details

There was a bug in the logout process by which sometimes, the fw Client was crashing without any user info.
There was a way to replicate this bug on Mac:
- Use the setting in fw Client > Toolbox > Settings > Miscellaneous > "Set Auto Logout Time" to 5 minutes and wait. After 5 minutes the fw Client would crash.

 

Implemented "AppleConnect Integration"; see details.

See Details

To enable this integration change this new settings variable on the "server.cfg" (located within the fw Server's "system" folder): ENABLE_APPLECONNECT 0 <= change the "0" to "1".

 

Fixed so that now the audio sounds are working also on the new Windows-x64 bit farmerswife Client application, see details.

See Details

These sounds now also work on the new Windows-x64 fw Client desktop app:
- fw Client > Log-in chime and Reminders (reminder.wav).
- Media Library or Dispatch module scan success "da-dih" (barcode_ok.wav).
- Media Library or Dispatch module scan failure "br r r r r r" (barcode_fail.wav).

NOTE: Either legacy QuickTime (QT) or e.g. VideoLanClient (VLC) or similar media player needs to be installed on the computer and set to play .wav files by default (Windows and Mac; QT not supported on Linux) for these farmerswife built-in sound-effects to work.

 

Conflicts

Conflicts Window List is now sorted by Object name and then date / time

 

Removed Object Classes from causing "Pre-Conflict Warnings", as this was causing wrong warnings when there were still available Class Members, see details.

See Details

If Object Classes are configured to "Cause Conflict", when booking pure Class farmerswife will check the Class Members for Conflicts when there is none available; if the setting in fw Client > Toolbox > Settings > Server Setup > "Check Class Members For Conflicts When Checking For Conflicts (slow)" is enabled.

And now for the "Pre-Booking-Conflict-checker-warnings" which get triggered if the setting in fw Client > Toolbox > Settings > Booking Defaults > "Warn For Conflicts Before Creating And Modifying Bookings" is enabled, these are now disabled when booking pure Object Classes, as this was causing wrong warnings when there were still available Class Members.

 

Fixed a bug on the "Pre-Conflict Checker" by which Personnel Bookings were causing wrong Conflict Warnings even in non-booked hours.

 
#320612

Fixed a bug when extending a Booking with an Object in "red" due to conflict, was wrongly still showing red on added days even though it was available.

 

Fixed a bug wrongly causing to not show the "Conflict Detected" pre-warning on some scenarios, see details.

See Details

The "Conflict Detected" pre-warning was not showing:
- When swapping two Objects from Framework Bookings on different days.
- When extending a Booking in the Long Form by marking a time range and using the Booking menu options "Days > "Add From Time Range" and also "Set From Time Range".
- When copying a Booking in the Long Form by holding the "cmd" key on Mac or "ctrl" key on Windows and dragging a Booking to the same day on the View Port > Calendar.

 
#320254

Implemented a performance speed-up for Conflicts related data via the MacKiosk app.

 

Contact Import

Fixed a potential fw Server crash when doing "Import Contacts".

See Details

Go to fw Server > Setup > Contacts > "Import Contacts" button.

 

Contacts

Implemented for certain places support to search by the Contact Name initials, by any combination of any part of the contact name, or by username, to then populate the Contact Name.

See Details

These are the contact fields and corresponding search fields that are supported:
- In the Check Out window (Dispatch Module): Pickup Contact and Contact.
- In the Check In window (Dispatch Module): Return Contact and Contact.
- In Custom Fields (Object Custom Fields, Booking Custom Fields, Project Custom Fields...) configured to find from Contact Names and import Name.

You can search by the initials (up to 5) of the contact name, any combination of any part of the contact name, or by username (in the case of Users and Resources) to then get the full name populated.

e.g. Contact name: Anne Marie Novak; initials: AMN; username: annitank.
Using any of the following character combination search will import the Contact Name:

1. search by initials:
- AMN (and also changing the order: ANM, NMA, NAM, MNA, MAN)
- AN (it also works with only 2 initials, any of them: NA, MN...)
- amn (it works with both upper and lower case)

2. search by any part of the name: enter at least 2 characters separated by a space
- an ma (and also changing the order: ma an)
- an ma no (and also changing the order: no an ma, ma no an, ...)

3. search by username (enter at least 2 characters of any part of the username)
- ni
- it
- nk
- nit
- ...

 

Customer Specific

Added new element called "Date Description and Rates" for the Navision Financials integration > Project Financial Exports > "To Export" section.

See Details

To use this new field, go to fw Client > Long Form > Personnel tree icon click > Personnel Management > Exports > Navision Financials > ... > Project Financial Export > Print Designer > "To Export" section > new field "Date Description and Rates".

 

Added "SageOne" customer related tweaks and the exported CSV file will now no longer be automatically opened by e.g. MS Excel.

 

Day History Logger

#313834

Fixed a bug on the "Day History Report" wrongly showing cleared Timereport information, see details.

See Details

If two people were booked on the same job, as each of them were time-reporting via the Web Client, the "Day History Report" was displaying a line on the first user stating that the second user had cleared his time-report. This is now fixed.

 

Days Charts

Fixed a crash bug when the selected days to show and export were > 103 days.

See Details

There was a limitation on how many columns to display in the excel that made the export crash. Now the necessary columns were added.

 
#316961
#321759

Fixed a bug preventing the "Days Charts" from working, when exporting to Excel on Windows using the "Windows-x64" installers.

 

Dispatch Module

Added a new setting in Toolbox > Settings > Server Setup > Dispatch Module > 'Disable The "Create Dispatch" Button When Booking Global Sub Status Is Not Confirmed'

See Details

This new setting is inactive by default.
When enabled, the Create Dispatch button within the Booking window, will be greyed out if the Booking Global Sub Status is different than Confirmed: Preliminary or Planning.

 

Added option to "Expand Groupings By Default" in the Dispatch window, to expand Groups, Objects with Accessories and Virtual Objects that were allocated in a bulk-action, see details.

See Details

In the Dispatch "Check In" or "Check Out" window drop-down menu you will now find this new setting: "Expand Groupings By Default" (enabled by default). This setting will expand Accessories, Group Members and Virtual Objects.

In the Dispatch "Check In" or "Check Out" window there is now a new column at the very beginning that will show an "arrow" icon next to the Object if this is part of a Group, if it has Accessories, or if it is a Virtual Object and was added in a bulk-action to a Booking, so you can expand or collapse it.

When expanded, a vertical thin line will indicate the Objects below the main Object to show that they belong together.

 

Added setting to get Dispatch Status set to "In Preparation (No Swapping)" when creating a Dispatch from a Booking

See Details

New setting added to Toolbox > Settings > Server Setup > Dispatch Module > "Set Dispatch Status To "In Preparation (No Swapping)" When Creating Dispatch From Booking ".
When enabled, the Dispatch Status will be set to "In Preparation (No Swapping)" by default when creating a dispatch from a booking.

 

Added support to dispatch from Class Booking "Undefined Objects" (NO OBJECT) and External Supplier Object Classes, see details.

See Details

If you cross hire equipment from a supplier you can now also dispatch this cross hired equipment piece.
This "External Object" will show in the Check Out window (Name + Supplier name) once you have clicked on the "Create Dispatch" button in the Booking Edit window.

In the Dispatch Module you will be able to double click on the External Object and a window will open where you can add an Inventory Number, a Note, and change the Name if needed. External Objects can't be scanned via a barcode scanner, but you can manually change it to Verified either via this window or by manually switching on the Status on the line.

To add an external Object to a Booking:
Configure your supplier (Global Contact type) with equipment in the Contacts > Supplier Details window.
Use this setting to auto book an external Object when you are out of your own equipment: Toolbox > Settings tab > Class/Objects tab > Auto Book External Object When No Object Found.
Or manually exchange an Object with an External Object in the Booking window (if you are out of that equipment* > Object icon menu > Replace With External From > Select Supplier.

*You have to be out of that equipment and farmerswife had allocated a NO OBJECT as an Object.

 

Adding Object Classes on Groups and Accessories to a new Check Out in Dispatch Module

See Details

When checking Out a Group with Class Members or an Object with Class Accessories, the Classes will also be listed on the Check Out - same behaviour as when Creating a Dispatch from a Booking.

 

Allow swapping Object Class with Member in Check Out even if Dispatch Status is "In Preparation (No Swapping)"

See Details

Objects in a dispatch that are not "object classes" cannot be swapped if "In Preparation (No Swapping)" is selected as status.
But if the dispatched object is an object class, this can be swapped with a member.

 

Implemented two new settings in Toolbox > Settings > Server Setup: "Use Booking Name In Dispatch Name" and "Use Project Name In Dispatch Name When Booking Name Is Empty", see details.

See Details

The Project Name and Number are used as the Dispatch Name if a Dispatch is created via the "Create Dispatch" button on the Edit Booking window.

Now, there are 2 new settings that allow either using the Booking Name or having the Dispatch Name empty.

In Toolbox > Settings > Server Setup:
- "Use Booking Name In Dispatch Name"
- "Use Project Name In Dispatch Name When Booking Name Is Empty".

Once the first setting is enabled, the Booking Name will be used as the Dispatch Name.

The second setting is greyed out and becomes available as soon as the first setting is enabled.

If second setting remains disabled, when Booking Name is empty the Dispatch Name will be empty.

If both settings are enabled, the Name for the Dispatch will be the Booking Name, but if this is empty it will be the Project Name and Number (default behaviour).

 

Added extra information when conflicts come up when committing a dispatch from the RestAPI.

See Details

·Now, when a conflict appears on committing a dispatch, some extra information will show that relates to the booking it has associated and also It's dispatch (if there is one created).
·There are two configurations in the setup toolbox that affect the conflicts that are being shown:
-"Allocate object even if it's not available? (Class / Object): If activated, this setup allows to create multiple bookings with the same object attach to it, causing several more conflicts.
-"Preliminary booking causes object conflict warnings? (Server setup): If activated, then the API will show every booking that causes conflict with the dispatch attempt. If this one isn't activated then the objects are attached but are not really available in the secondary bookings, so it also won't cause conflicts.

 

Changed default Status on a new Check Out to be "In Preparation", when setting "Set Status To "Dispatched" When Creating New" is disabled.

See Details

Changed behaviour: When Dispatch setting "Set Status To Dispatched When Creating New" (in Dispatch module > drop-down menu > Settings) is disabled, it will set new Check Outs created via the Dispatch module to Status "In Preparation".
Before, it was setting the status to Ready.
Now, if this setting is disabled, when creating a new Check Out, the status will be set to "In Preparation", allowing the user to decide when the dispatch is to be moved to "Ready" and even directly to "Dispatch" status.

 

Fixed a bug in the Dispatch module by which the fw Client was throwing an exception when checking out an item by using the ?New? item option.

 

Fixed a bug where Custom Fields on a Check Out could get lost in specific scenarios when a Checkout was overdue and got extended

 

MacKiosk - Fixed a bug when checking IN Objects and marking one to be broken, the user who created the Dispatch wrongly received a "Dispatch is being prepared by" email.

See Details

On MacKiosk, when checking in a Group of Objects and marking one as broken, now a wrong email notification in this scenario is no longer being sent.

 

Now it is possible to search by Division and Target Division in the Dispatch module

See Details

Two new search fields have been added to the Dispatch module: Division and Target Division.
Also, Division and Target Division have been added to the Edit View to display as columns in the results area.

 

Divisions

For clients using the divisions option It is now possible to automatically create internal invoices, see details

See Details

Added a new setting "Automatically Creates Internal Invoices When Invoicing" to automate the process of creating internal invoices.

It was already possible to manually create internal invoices when using Objects from different Divisions in a Project. If for example a Project from Division UK used some Objects from Division US, at the moment of creating the Invoice to the client there was an extra manual step to create an Internal Invoice from US to UK. (An Internal Invoice is created from the Division that an Object belongs to, to the Division that used it.)

Now with the new setting the Internal Invoice will automatically be created once a full or a part invoice is created.

Enable the new setting "Automatically Creates Internal Invoices When Invoicing" in the Invoice Creator > Menu > Division Invoice Creation Mode. It is a per user setting and disabled by default.

To be able to use this feature, the following setting needs to be enabled: Invoice Creator > Menu > Division Invoice Creation Mode: > Create Invoice Based On Project's Division.

 

EMT

"New Check In From Selected" option in Dispatch module now allows to scan back items against the original Check Out.

See Details

Added an enhancement to already existing option "New Check In From Selected".
Now apart from listing all items from original Check Out it has a new column "Verified" allowing you to scan back in all items.
If you start scanning and click the OK button of the Check In and have not scanned back in all items, a message will warn you: "Unverified Objects Will Be Removed".
Clicking OK will remove all the unverified Objects from this Check In. So the next time a new Check In From Checkout is created for the original Check out only items that have not been scanned back in will show and are ready to be scanned back in.

If you need to bulk-verify items and don't use the scanner, you can use Ctrl + A and highlight all items in the Dispatch > Set Status > Verified.

 

Add Dispatch Object Note And Link To Object Custom Field

See Details

It is possible to add a Note to each Object inside of any Check Out or Check in by selecting the Object line > right mouse click > Edit Note.

This Note can now be linked to a specific Text Widget Object Custom Field setup in the Object Manager > Setup Custom Fields. To link this Custom Field to the Dispatch please click on the drop down menu inside of the Dispatch Module's result pane > Settings > Add Dispatch Object Note To Object Custom Field. Once linked any note added to an Object inside of a Check In or Check Out will be transferred and shown in the chosen Text Widget Object Custom Field in the Object Manager.

In the Object Custom Field the latest note, that was added, will be put at the top. The notes will be displayed with the date stamp (date/time - User name) at the end of each note and are showing stacked.

The column width of the Object Custom Field inside of the Object manager is predefined, when doing a mouse over you will see in a yellow window the notes nicely stacked.

It is possible to use an Entry Custom Field to link the Object Note of the Dispatch, however only the latest note gets stored and you won't have a history of your notes.

 

Added "Group By Object Class" to Dispatch report, under Setup of Template

 

Added "Move To New Dispatch" option in the Dispatch window to move selected items to a new dispatch this way multiple Dispatches are linked to one Booking

See Details

This is useful when a kit room manager is preparing the equipment requested on a Check Out to be sent out, and realises that one equipment didn't make it with the overnight express to his kit room and needs to ask a colleague in another department/office/city to send this equipment directly to the client.

When creating the first Dispatch from the Booking, this one will be the reference Dispatch (Check Out).

From this initial Check Out, the User can now select (highlight in yellow) the Objects that need to be moved, right-click or click on the drop-down menu, and select" Move to New Dispatch".

This will create a new Check Out that is also linked to the same Booking. However when clicking on the "Open Dispatch" button inside of the Booking window, only the reference Dispatch will open.

If you have setup Objects with (Object Class) Accessories, and want to move it to a new Dispatch by only selecting the main item, a warning popup note will show: "Confirm Moving A Parent From Its Accessories: [Object Name]". If you selected an Accessory of a main item and wanted to move it to a new Dispatch a warning popup will appear: "Confirm Moving An Accessory Without Its Parent: name of Object".



 

Added a new "Global Status (Dispatch)" Setting for the "Default Booking Status" (if "EMT" is licensed) for manual Check Outs, see details.

See Details

To use this new setting go to:
fw Client > Toolbox > Settings > Default Booking Status > "Global Status (Dispatch)".

This new Setting was added for the EMT Module, so that Web Users which have access to the fw Client desktop app > Dispatch module (if Web Permission: "Dispatch Access Through Desktop Client" is enabled) can set a specific "Global Booking Status" when they create a New Check Out from the Dispatch module.
When working with different Divisions this now allows to select a specific Global Status with its corresponding color, when doing e.g. "internal transfers" from one warehouse to another.
Before the Global Status of the Task or Booking was set to Confirmed and couldn't be changed.
Advanced User can also set the default Global Status behaviour in Toolbox > Settings > Booking Defaults > "Global Status (Dispatch)".

IMPORTANT: The "Booking Global Status" needs to be one that has its Sub Status set to "Confirmed", so that the resulting Task or Booking can create a Conflict Warning in farmerswife.

The setting: "Default Expected Return After Days And Time" must be set to at least "1 Days" in Toolbox > Settings > Dispatch Module as well as: "Create And Slave Booking When Creating New Dispatch", so the Check Out will actually create the Task or Booking.

 

Added a new window to type an amount when booking Virtual Objects, see details.

See Details

If an Object is configured to be a Virtual Object (Object Manager > Object's Modify window > Allow Multiple Check Outs (Virtual Object)), when booking the Object a new window will pop up to "Type Amount: For (Object Name)".

This action will then add this Virtual Object as many times as set on this amount field. If by mistake a non-numeric character was entered on this selector, then the Virtual Object will be added only once.

Same new window will pop up if you book via the Object Class.

It is highly recommended that still the Object belongs to a Class with the same name as part of its configuration (usual configuration on equipment management scenarios), so reports that are usually configured with "Group By Obj. Class" setting can still show all Virtual Objects in one line together with the quantity ("Obj. Class Group Quant." element). Else each will show on a separate line, making your reports very long.

 

Added in Toolbox > Settings > Dispatch Module: "Show Remove Object As A Popup Option In The Dispatch Window".

See Details

When ticked, the "Remove" option will always appear on all Check Out Statuses and Check Ins.
If not ticked, the "Remove" option will not show if the Check Out is in Status "Dispatched". To prevent that a User deletes an item that was scanned and was sent to a client.
The "Remove" option will always be there on a Check In and In all other Statuses but "Dispatched" on Check Outs.

 

Added new "Global Status (Dispatch)" in Toolbox > Settings > Booking Defaults for manual Check Outs, see details.

See Details

If "Equipment Management Tracking (EMT, a.k.a. Object Dispatch) is licensed a new option was added in fw Client > Toolbox > Settings tab > "Booking Defaults > "Global Status (Dispatch)".

Select here which default Status a Task or Booking should take which is created by an Advanced User via a manual Dispatch > Check Out from the Dispatch module (if "EMT" is licensed).
A "manual" Check Out is without any prior Booking; e.g. done ad-hoc straight from the warehouse.

To create a manual Check Out go to the Dispatch module > right-mouse click > "New Check Out". If you select a Project, a Booking will be created, if you don't select a Project, a Task will be created.

farmerswife will only create a Booking or Task from a manual Check Out if the settings in fw Client > Toolbox > Settings tab > Dispatch Module > "Default Expected Return After Days and Time is set to at least 1 day" and "Create And Slave Booking When Creating New Dispatch" are checked.

 

Added new Dispatch Limited Mode permission for Web Users, and a Password for changing Check Out status, see details

See Details

This new Web Permission and Password setting have been added to establish a workflow where certain Web Users can only scan equipment on existing Check Outs to get them ready for pickup, and certain Web Users can then set the Ready Check Outs to Dispatched Status using this Password.

- "Dispatch Limited Mode" permission:
This new Permission has been added to the Web Profile Manager and can only be enabled after enabling the "Dispatch Access Through Desktop Client" permission.

A Web User with this Limited Mode enabled will be able to use the Dispatch Module in the farmerswife Desktop Client application to:
- scan existing Objects on existing Check Outs
- print Check Out and Check In Reports
- create New Check Ins
- create New Check Outs - so equipment can be sent from one warehouse to the other
- modify any Custom Fields that have been loaded into the Dispatch previously
- edit the Note field on Dispatches

He won't be able to:
- modify anything on the header of existing Check Out, e.g. Dispatch Name, Pickup Contact, ...
- remove any Objects from existing Check Outs if it is not his own Check Out.
- change the Status of the Dispatch - unless he knows the Limited Mode Password, if it has been set.
- access Dispatch Settings
- access and change Custom Field templates in Checkouts or Check Ins


- "Limited User Mode Change Status Password" setting:
This new setting has been added to Toolbox > Settings > Server Setup > Dispatch Module.
Click here to set a password that you can give to certain Web Users to be able to do any Check Out Status Changes. Once set, the password won't be displayed by clicking on it, but it is stored.

Web Users with Dispatch Limited Mode will be able to click on the Status of a Check Out and change it from e.g Ready to Dispatched, however User will be prompted: "Please Enter Password'.

If no Password is defined, the Status field will be blocked for Web Users with Dispatch Limited Mode. Only Web Users with no Dispatch Limited Mode and any Advanced Users with Dispatch Access will be able to change Check Out Status.

 

Added new User Permission under Dispatch Module area "Allow Modifying Booking Days After It Is Dispatched", see details.

See Details

This is useful in cases where the equipment is out and the client calls to extend the usage of the equipment. So you prefer extending Booking from the Long Form to be able to see if all the equipment is available for the extra days requested by the client - instead of doing it from within the Dispatch window as it is now.

Without this permission enabled, to extend a Booking linked to a Dispatch (Check Out) the User would need to go to the Dispatch itself and change the Return Date.

Thanks to this permission, the User can now extend and change the time of the Booking in the Long Form by using the options "Days > Add From Time Range" and "Time In/Out". And of course, the Return Date in the Dispatch will be disabled for this User.

It is possible to extend single items of the Bookings, and this will extend the complete Check Out.

It is still not possible to add new equipment to the Booking, or delete equipment.

 

Added new section to Toolbox Settings tab: "Dispatch Module"

See Details

All settings belonging to the Dispatch Module are now in this new section and don't have to be accessed in the Toolbox > Settings tab > Server Setup anymore.
Permission to Server Setup however is still required on a per User level to be able to access those settings.

 

Added support to remove an Object from its Check In so the Booking reverts back to last status

See Details

Feature added to "undo" the check in of an Object that was scanned in by mistake.

It is possible to remove an Object from a Check In if the Object is not the only Object on that Check in. (Otherwise you can't remove it).

If the Object was previously out on a Checkout, by removing it from the Check In, it will be checked back out to its original Check out. Thus the Booking gets updated and the Object appears checked out again.

The Dispatch history will still show that this Object had been checked in showing the following line:
Arrow pointing down Dispatched In (number of Check In) User icon date / time. This way you know that this had been checked in.

You can still remove an item from any previous old Check In, however it won't affect the current location of the Object, if the Check In that you remove the Object from is not the one that caused the Object to change status from being out, now being in.
Example for better understanding:
A tripod was checked out to Project A two weeks ago. It gets scanned in today (Check In number 1) . Later today it gets scanned out to Project B. And at night checked back in again (Check In 2). If the tripod now gets removed from Check In number 1, nothing will change as the tripod was out and in again. Check In 1 was not the last cause for the tripod to change its status from out to in, that was Check In 2.



 

Added support to show details of Objects that have been "Added To" and "Removed From" a Check Out, in the Dispatch Status window and in the Day History Report, see details.

See Details

If an Object is added to or removed from a Check Out/Dispatch this will now show in the Dispatch Status window of the Object, as well as in the Day History Report generated on the Object, as well as details of who and when.

The Day History Report can be generated in the Long Form > Objects tree > Reports > "Objects Report (Multiple Objects)". In the "Event Header" section you will now see "Added To Dispatch: #" and "Removed From Dispatch: #".

The Dispatch Status window now shows, together with Check Out and Check Ins, when the Object was Added To or Removed From a Dispatch, with details of User who performed the action, date and time.

When Dispatch has Object Classes and these get replaced by a member, this action is also displayed as "Added To".

 

Added to show in Long Form Objects tree in special color when Objects are Verified / Dispatched.

See Details

To be able to see in the Object Tree if an Object has been verified or scanned in the Dispatch Module, a color has to be setup in Toolbox > Settings tab > Display > Verified / Checked Out.
Click on the Object Tree icon after loading the Objects > View Mode > Verified / Checked Out. This will then color the Bookings which have been verified or checked out in the color that was setup in the Toolbox.

This new feature allows to see whether an object was already prepared to be checked out in the near future and gives you a visual help to see which Objects are really available.

 

Added two columns to the Dispatch window: "Related Check Out" to Check Ins and "Related Check In" to Check Outs, see details.

See Details

When an Object is scanned back into the system, on the "Check In" window there is now a new column called "Related Check Out". This will now display the number of the "Check Out" where this Object comes back from. This way it is easy to see, if all scanned-in Objects came back from the same job.

The "Related Check In" column data will only show, after you click "Ok" on the newly created Check Out. You will then see the last Check In that the Object came back from.

Both columns are now available in the Dispatch Report in the "Element Row" section.

 

Behavior Change: Non scanned Objects like Object Classes are not set to checked out when changing the Dispatch to Status "Dispatched". They remain in unverified status.

See Details

Behavior Change: If you created a Booking and then a Dispatch from this Booking your Dispatch will be by default in "In Preparation" mode. When you then directly select the Dispatch Status "Dispatched", before it would have changed the status to "out" on each Object showing the red arrow pointing up. Right now it will just change to status "Dispatched" but you will still need to verify each item.
If you don't verify an equipment a new pop up message appears: Unverified Objects Will Be Removed, which will then remove all non scanned items from the Check Out.

If you quickly want to go through verification you will need to first select READY (all gets verified) and then Dispatched.
However, not real Objects like Object Classes or External Objects need to be verified even in Ready Status, as they are no real Object yet.
This also applies if the setting in Dispatch Module > drop down menu > Settings > Set Status To "Dispatched" When Creating New is activated and you scan out an Object that has Object Classes as Accessories. Object Class Accessories always have to be verified to be checked out.

Before, when selecting the Status "Dispatched" the status bar of each equipment line turned into the red arrow icon, indicating that this item is checked out.
This got fixed and when changing the Status to "Dispatched" the status bar of each items stays and shows the status of the Object (non verified or verified). Only when hitting OK on the Check Out will the red arrow icon replace the status bar.

When using the "Ready" Status and clicking on OK on the Dispatch window the window: "Warning: Objects Already Checked Out" appears if there are conflicts on an Object that you are about to check out.

 

Binder: You can now move a Booking that has a Checkout related to it, that is dispatched to a Binder.

See Details

When creating a Checkout that is later on dispatched, it wasn't possible to move it to a new Binder, as the popup message appeared: Booking Is Dispatched.
Now you can move a dispatched Booking to a Binder.

 

Dispatch Check Out window: you can now click on an Object Class or External Object inside of the Dispatch Out Window and edit Name, Inventory Number, Note and set the Status to verified

See Details

Needed for Cross Hire scenarios, where In the Check Out window more info needs to be added to a cross hired Object by amending the External Object or Object Class item line.

If you have setup Suppliers in your Contact database that lend you specific Objects, you can now also Dispatch an External Object.
Setup a supplier in your contact database by adding Object Classes to the Supplier Details tab in your Global Contact. This way, when you are out of equipment for that Object Class you can either click on an Object or on the "No Object" icon and replace it with an External Object.

Both, the label "External Object" and the Object Class (which represents the equipment (Tripod) will be carried on into the Dispatch Check Out window.
By double clicking on the "External Object " or on the Object Class' line a window pops up letting you alter the Name, Number (which is the Inventory Number) and Note. A new checkbox was added to set the status of this External Object or this Object Class to "verified", so the Object is "scanned".

 

If a Booking has multiple Dispatches linked and one of them is set to "Dispatched", it is now possible to modify the Booking on Objects that haven't been dispatched yet, see details.

See Details

A Booking can have multiple Dispatches.
When creating a Dispatch from the Booking, this is the original Check Out. From this Check Out an Object can be selected and with a right mouse click "moved" to a new Check Out. Now there are two Check Outs for one Booking. They can have different Dispatch Statuses.

If one of the Check Outs is now set to Status "Dispatched" farmerswife will now allow you to add more Objects to the Booking or allow to replace Objects that are not yet set to be on Status "Dispatched". The User setting: Dispatch Module: "Allow Modifying Booking After It Is Dispatched" needs to be enabled to add Objects to a Booking that has one its Dispatches set to Status: Dispatched.

This option won't work if you use "Use selected Time Range" and it always needs to affect the whole Booking time.

 

Implemented easier check-in for "Virtual Objects" to re-stock and use Original Check Out to check them back-in, see details!

See Details

"Virtual Objects"(VO) in farmerswife are usually "consumables" that get used up and won't be returned.
To configure this go to: fw Client > Object Manager > sub-menu "New In" > ... > "New Object" window >
- "Allow Multiple Check Outs (Virtual Object)" = Yes / checked.
- "Is Expected To Be Returned When Checking Out" = No / not checked.

However there are also some scenarios where a Virtual Object can be e.g. an Object physically too small in size to be properly barcode-labled, e.g. a "control cable", etc.
Go to: fw Client > Object Manager > sub-menu "New In" > ... > "New Object" window >
- "Allow Multiple Check Outs (Virtual Object)" = Yes / checked.
- "Is Expected To Be Returned When Checking Out" = Yes / checked.
IMPORTANT: In order to track these properly, you NOW must use the ORIGINAL Check Out and from this one create a "New Check In From Selected". Only this way can farmerswife keep track of these "VOs" which all have the same Inventory Number.

On both of these scenarios, these are added to farmerswife by using one generic "Inventory Number".

And you also need to set the amount of how many of those Objects you have in stock.
Before you needed to assign these "VO" to a designated Object Class in order to re-stock; this is no longer needed.
To re-stock: Create a New Check In via the Dispatch module, add the properly configured "VO" Object, right-mouse click and use "Copy", then add the amount of stock to be added incl. the first added Object you are copying (note: hard-set limit of adding max amount of 1.000 VOs per "re-stock" Check-In; takes around 1 min. to be finished.)

Now you add these "Virtual Objects" to Bookings via drag and drop or via the Edit Booking window > Involved pane, and then the new "Type Amount For" window pops up allowing you to add the quantity of Virtual Objects that you need to book. From the Booking you can create the Dispatch via the "Create Dispatch" button or add the Virtual Object directly to a Check Out via the Dispatch module.

VERY IMPORTANT: If a Virtual Objects is on a Check Out and you want to return the Virtual Object, you must select the _original_ Check Out > right mouse click > and use "New Check In From Selected" and scan the Virtual Object. The stock of this Virtual Object will increase and the Check Out will be set to "Returned", if all other involved Objects have been returned as well.

Also VERY IMPORTANT: If you check-in a Virtual Object by itself on a "New Check In", the stock-count will NOT increase and the corresponding Check Out's Status will be set to "Partially Returned" or "Overdue"!

 

It is now possible to delete or swap or add Users and Resources on Bookings with a Check Out in "Dispatched" Status, see details.

See Details

This new feature allows to exchange/swap add or delete the crew (Users and Resources) when booked together with the equipment on the same Booking, even if the Check Out has been set to Status "Dispatched".

The message "Booking Has Been Dispatched" won't show if Users or Resources are added, deleted or swapped. This now allows you to exchange the crew as necessary.

 

New Checkout/in window: Moved the drop down list of the "Add Object (Name) field from bottom to the top to avoid a cutting off the list at the bottom

 

The Object Note on Check In is now linked to the corresponding Check Out, see details.

See Details

If an equipment is returned and a User adds a Note to that Object's line, this Note will now show in brackets the corresponding Check Out in the column called "Related Check In".

This way Users can send a "Broken" report to their clients, listing all broken items directly from the Check Out.

 

The Object's real status (location) will be shown in an additional new column "Current Dispatch Status" inside of the Checkin and Checkout window

See Details

An additional column has been added to the Dispatch Checkin and Checkout window called " Current Dispatch Status" which allows to see the current location of an Object. The column will show the Dispatch arrow showing whether an Object is in our out + name of client (Dispatch Number).

This is helpful when scanning back in Objects from a job to quickly check that all Objects are from the same job.

In order to show this new column the Dispatch window has been resized if the screen resolution allows it.

 

When swapping an Object Class with real Objects in "In Preparation or "In Preparation (No Swapping)" Status farmerswife will swap the Object Classes of the Parent Object that was last scanned keeping the sorting correct

See Details

When swapping an Object Class with a real Object farmerswife now "remembers" the last parent Object scanned and will replace the Object Class with the real Object scanned on the correct Kit.

Example:
You have a Checkout with 3 cameras, all of them have the same accessories: a tripod and a baseplate.
When all of the three cameras are on the same checkout it will look like this:

camera 1
baseplate class
tripod class

camera 2
baseplate class
tripod class

camera 3
baseplate class
tripod class

When you now scan camera 3 and now scan any baseplate, farmerswife will swap the baseplate of the camera 3 as camera 3 is the parent for the baseplate.
Before farmerswife would go from the top of the Checkout window and swap the first Baseplate Object Class with the baseplate that was just scanned. This resulted in a wrongly sorted printed Dispatch Note.

 

Added a new Setting in Toolbox > Settings > Server Setup > Dispatch Module called "Set All Objects To Verified When Setting To Dispatched", see details.

See Details

If a Dispatch > Check Out is created through a Booking, it is typically on "In Preparation" or "In Preparation No Swapping" Status.
With this new setting in fw Client > Toolbox > Settings > Server Setup > Dispatch Module > called "Set All Objects To Verified When Setting To Dispatched" enabled, this will now cause on Check Outs which are directly set to "Dispatched" all Objects on the Check Out will get set to be "Verified".

If this setting is off, you will have to verify each and every Object like you are supposed to do or set it to the Status "Ready" first and then "Dispatched".

Please be aware if the database contains configuration of Objects with Object Class Accessories, those will be also set to "Verified", even if they haven't been replaced with a real Object. Database that use Object Class Accessories should have this setting off.

 

Added back in functionality to auto-verify a Virtual Object when adding it to a "New Check In From" or a "New Check In"

See Details

If a Virtual Object had the setting "Is Expected To Be Returned" not ticked, when doing a Check In it wasn't automatically set to "verified". Thus you needed to verify this item after scanning manually. This has now been fixed and when adding a Virtual Object to a New Check In it is automatically verified again.

 

Fixed a bug on retrieving information for "Pending Dispatches" in relation to working with MacKiosk.

 

Fixed a bug that the setting "Auto Check In Objecs That Are Out When Being Checked Out" would be ignored even when setting was activated

 

Fixed a bug when adding Objects to a Booking with a Check Out on Status "Ready", these Objects wrongly got verified straight away, see details.

See Details

When a Booking had a Dispatch linked to it on Status "Ready" and you added Objects through the corresponding Booking, those Objects were "verified" right away, which didn't allow any swapping of the Objects. This has now been fixed.

Now when adding an Object (all except "Users" and "Resources") to a Booking and the corresponding Check Out is on Status "Ready", then the Check Out Status jumps back to "In Preparation" or "In Preparation No Swapping" (depending on the Server-side setting in fw Client > Toolbox > Settings > Dispatch Module > "Set Dispatch Status To "In Preparation (No Swapping) When Creating Dispatch From Booking". This now makes it possible to verify the items in the "Kit Room" and swap them if needed.

The trigger for the Check Out to jump back to the "In Preparation" or "In Preparation No Swapping" Status is, if a User adds, deletes or swaps an Object on the linked Booking.

 

Fixed a bug when copying and pasting an "Object Class From Clipboard" and wrongly losing all manually entered information, see details.

See Details

If an Object Class was used for "cross hired items" and on the Object Class there was info added like Inventory Number a new Name and a Note, those would be wrongly lost, if this Object Class was then copied to the "Objects Clipboard" and pasted again into a new Check Out. Now the information is kept when copying an Object Class.

 

Fixed a bug when the Check In Time of an Object was overwritten by its default Booking Out Time

See Details

If a Dispatch was overdue and it got checked in the next day in the morning, it couldn't be checked out again via the Mac Kiosk station as it created a conflict due to the fact that the Object's checked in time was overwritten by the Booking's Out time.
Example:
An Object was due to be back last night at 18:00 (Bookings Out time).
It got checked in today at 09:00. When someone wanted to check out this Object there was a conflict, because until 18:00 of today this Object was still booked, even if it got returned at 09:00.
The Checked In Time should overwrite the Bookings Out time, which it didn't. This is now fixed.

 

Fixed a bug when using "New Check In From Selected" on an Object Class or External Object wrongly not updating the actual Object's Status, see details.

See Details

Before, when using "New Check In From Selected" and you verified the Object Class, it would look verified, but the actual Status of the Object on its corresponding Check Out was not set as checked IN, thus causing the Check Out to change into "Overdue" status.

If an Object Class or External Object has been set an Inventory Number and is checked OUT, it can now be set to be checked IN which makes the original Check Out Status on the actual Object to now be correct.

This has now been fixed.

 

Fixed a bug when using "Paste From Objects Clipboard" wrongly causing all copied Objects to already be verified in the New Check Out, see details.

See Details

When copying Objects from a "Dispatched" Check Out to a newly created Check Out by using "Paste From Objects Clipboard", then the copied Objects were added wrongly on already "verified" status. This has now been fixed and the copied Objects now appear with non-verified status.

 

Fixed a bug where Objects could be wrongly added to a Booking with a "Dispatched" Check Out, see details.

See Details

Before it was possible to add an Object to a Booking which had a "dispatched" Check Out related to it. These Objects were then automatically verified and appeared to be checked-out on the same Dispatch, but were actually never sent.

 

Fixed a bug where you could still wrongly add Objects to the Booking if it was dispatched and those Objects were added to the Check Out

See Details

You will still be able to add Objects like Users or Resources to a Booking that has a Check Out related to it which is Dispatched.

 

Fixed a bug where you couldn't replace an Object in a Check Out on Status "In Preparation" if the Booking had more than one Dispatche associated to it and one of them was "Dispatched", see details.

See Details

Note that the user needs to have this existing Advanced User Permission enabled to be able to swap Objects:
"Allow Modifying Booking After It Is Dispatched" in Modify User > Permissions > Edit > "Dispatch Module" section.

 

Fixed a bug where you couldn't use the option to "Paste From Object's Clipboard" when copying an External Object, see details.

See Details

Now it is possible again to use the option inside of a Check Out to click on an External Object and use the option: "Copy To Objects Clipboard" and then use the option: "Paste From Objects Clipboard" to paste the External Object into a new Check Out.

 

Fixed a bug wrongly causing Objects not to be removed from the linked Booking, if they were deleted from the corresponding Dispatch on Status "Ready".

 

Fixed a refreshing bug in the Checkout window

See Details

Fixed a bug when an original Checkout was open in the desktop client and an Object from that Checkout gets checked in at another station, the status column of that Object didn't change in the original Checkout leading to confusion, whether this Object really had been returned. This has now been fixed.

 

Implemented support to change Object Booking Color if the Object is on a Dispatch > Check Out and "Verified".

See Details

Added this option to only change the color of the Booking in case it is scanned (thus verified) in the Check Out to the existing feature in Objects Tree > View Mode > Verified/Checked Out.

Once an Object is scanned on the Check Out or set manually to verified then the Booking color changes to the one that was setup in Toolbox > Settings tab > Display > Verified/Checked Out.

Difference to the feature in View Mode: Verified / Checked Out is that once an Object is verified on a Check Out it will show with the Verified/Checked Out color that was setup. But as soon as the Check Out has been set to "Dispatched" the color of the Booking of that Object that is on that Check Out falls back to its original color (Project/Client color or Global Status color - depending which setting is used in the Objects Tree). This way you can track in the Objects Tree which Objects are already prepared and scanned to go out and you won't by mistake take one of those and replace it.

 

On a Check In Object Class Accessories are now not loaded anymore

See Details

When an Object has Object Class Accessories set and you do a check in, before, it would also load those Object Class accessories. Now this doesn't happen anymore, as on a Check In you do need to scan them and don't need them pre-loaded. This could be confusing and would result in errors.

 

Exchange

Re-implemented the connection and authentication support to legacy Exchange 2010; it also works with Exchange 2016.

 

Extras

Added support that all Objects types are available to select for "Ad-Hoc Extras" and "Pre-Defined Extras" (previously called "Pre-Defined Services").

 

Financial Report

Added "Budget Operator Totals" fields in Budget grouping and in "From Budget".

See Details

In the "Budget" grouping, and in all places where there's a "From Budget" field group, these new fields have been added, inside a new field group called "Budget Operator Totals":
- Total Sell (Budgeted) From Global Budget Operators
- Total Sell (To Invoice / Used) From Global Budget Operators
- Total Sell (To Invoice / Used / Booked) From Global Budget Operators
- Total Sell (Used) From Global Budget Operators
- Total Sell (Used / Booked) From Global Budget Operators
- Total Sell (Booked Only) From Global Budget Operators
- Total Sell (Invoiced) From Global Budget Operators
- Total Sell (Quoted) From Global Budget Operators
- Total Sell (To Invoice) From Global Budget Operators
- Total Sell (Comparison Budget) From Global Budget Operators

 

Added "Public Holiday" and "Day Note" as Elements in Financial Reports > "Group By" > "Date" and all "Rows" section, see details.

See Details

The "Public Holiday" and "Day Note" have been added as Elements when using "Group By" "Date" and all "Rows" section in Financial Reports (FR).

These two new elements are located on new created Templates:
- between Marker and Currency within the Group By "Date" loop
- below "Date" in the "Rows" section

NOTE: for already existing FR-Templates these new elements will appear at the bottom of the list.

These elements will only display a value if there are any financial lines in the selected date range for the report.
And these elements will display the date in front of the "Day Note" or "Public Holiday" value, if the financial line comes from a multiple-day Booking.

 

Added "Quantity As Hours" to all "Numbers"/"Totals" field groups.

See Details

If a Booking line has Day Rate configured, the Quantity field in Financial Report will show the number of days, regardless how many hours were booked.
But sometimes it can be useful to see the number of hours, so there's now a "Quantity As Hours" field in all Rows > Numbers, Grouping > Totals and Header/Footer > Totals field groups.
When calculating this number from Bookings, the "Quantity As Hours" field will be the exact number of hours that were booked (or timereported).
When calculating it from other sources, e.g. Project Work Orders, the "Quantity As Hours" will convert Days into Hours using standard methods. For example, it will use the per-user working hours if possible, or otherwise default to the company default working hours.

 

Added "Scheduled Invoices totals" fields to the Financial Reports "Header" and "Footer" sections, see details.

See Details

The fields added to the Financial Reports "Header" and "Footer" sections are:
- "Scheduled Invoice Fixed Price"
- "Scheduled Invoice Fixed Price (Invoiced)"

 

Added "Time Report Day Note" and fixed the "Object Time Report Note".

See Details

Added element "Time Report Day Note" to the Rows section of Financial Reports.
Also fixed that the "Object Time Report Note" shows values for multi-day Bookings, regardless of the setting "View Class Booking As Separate Days" being enabled or not.

 

Added a new Grouping to Financial Reports by "Week Number", see details.

See Details

Added the ability to set a new Group called "Week Number" within the Financial Reports.
Any financial lines will be included if they have a start date that falls in that week.

Practical use: You can now create a Report to break out a Project's expected costs, hours, expenses or bookings by week, making it easier to manage staying on track for a Project.

 

Added some settings to Save Filters on Financial Reports, per User or per Print Template, see details

See Details

Sometimes users need to save filters (including specific Objects, Object Classes and/or dates under Financial Lines In Range) per report template, so when generating a Financial Report on some Projects or Objects, they can easily re-apply the saved filters.

To allow this, there are three setting, two that apply per user and one that is global.

The following two new options in Toolbox > Settings > Miscellaneous (apply per user) are meant to save filters per User, and not per Template:

- "Use 'Save Filters' in Financial Reports" (enabled by default).
When enabled, the new button "Save Filters" shows next to "Generate Reports" in the Financial Reports window, to save the current Filters to the selected Report Template.
To delete saved filters on a report template, put the Objects and Object Class filters back to Any and the Financial Lines In Range back to Don't Filter, and click Save Filters.
If disabled, the button does not show for this user in the Financial Report window: this user cannot save filters but he will still get filters saved on templates if the global setting “Apply Financial Report Saved Filters Per Template” is enabled (see further down).

- "Ask Before Loading 'Saved Filters' in Financial Reports" (disabled by default).
When enabled, when you select a Report Template with saved filters, a pop-up window says: "The Selected Template Has Saved Filters. Apply?".
Selecting Yes, the saved filters will be loaded in the Filters area.
Selecting No, the new selection (if any) will be loaded in the Filters area.
When this setting is disabled, there will be no pop-up window, therefore the saved filters on a Report Template (if any) will always be loaded.
An exception to this rule is that even if the setting is disabled, if the User starts the report by selecting Objects or Object Classes (in Toolbox or in Object Tree), as a report template with saved filters is selected, the window "The Selected Template Has Saved Filters. Apply?" will still show to allow deciding that in this particular case the new selection should apply instead.
A user can always put the Objects and Object Class filters back to Any and the Financial Lines In Range back to Don't Filter, if for a particular report there is no need of the saved filters that got loaded.

Some examples:
- These saved filters might only include Objects, e.g. all Editing Rooms, but no specific dates. This might be useful to save this filter to a report template that applies to editing department only.

- The user might need to run the same financial report every month, but separate per department. In this case, before selecting any specific Object, he would go to the Financial Reports window, select the report template and choose the whole month under Financial Lines In Range, and click on "Save Filter". This report template is now ready for the user to then go choose some Objects (in the Objects Tree, or Toolbox > Objects) to generate the report for that saved period of time. And then repeat the operation choosing some other Objects, etc.

There is a third setting, which is global:
Toolbox > Settings > Server Setup > Apply Financial Report Saved Filters Per Template
This setting is to change the explained behaviour and make the saved filters to apply directly to the Template.
If this setting is enabled, any saved filters will be connected to the print template and will apply to any user running that print template.

Finally, if a User has the Toolbox > Settings > Miscellaneous setting “Use Save Filters in Financial Reports” disabled, it means that the button does not show for this user but any saved filters still apply when he uses a template with saved filters.

 

Added the Elements "Profit" and "Margin" to the Financial Report Print Designer, see details.

See Details

The Financial Report now contains new fields for "Profit" and "Margin (%)" inside all "Totals" groups.
- Profit is basically (Sell-Buy).
- Margin is the profit margin, as a percentage from dividing (Sell-Buy)/Sell.

 

Global Custom Fields are now available as elements in the Financial Report Designer

See Details

Global Custom Fields have been added to the Project, Binder and Subbinder section under Custom Fields.
As well as Row section under Custom Fields (Project / Media Orders/ Unref), Custom fields (Binder Name) and Custom Fields (Sub Binder Name).

Note: Parent Binder section will be Binder Name, Child Binder Section will be Subbinder Name.

1) If Binder have Subbinders (and exists bookings on them):
a) If Parent have data on CF and child also have -> Parent will have Binder CF data, Child will have Subbinder CF data, on Binder Name,
Subbinder Name and Row section.
b) If Parent have data on CF and child do not have -> Parent will have Binder CF data, Child CF will be empty, on Binder Name, Subbinder
Name and Row Section
c) If Parent do not have data on CF and child have -> Parent CF will be empty, Child will have Subbinder CF data, on Binder Name, Subbinder Name and Row Section
d) If Parent do not have data on CF and the child neither -> All values will be empty

2) If Binder do not have subbinders
a) If Binder have data on CF -> Binder Name, Subbinder Name, Row Section will have the CF data on it
b) If Binder do no have data on CF -> Binder Name, Subbinder Name and Row section will be empty

 

Implemented farmerswife Server-side performance improvements for "Financial Reporting", see details.

See Details

The following farmerswife (fw) Server-side performance improvements will typically have their greatest effect when running Financial Reports on BIG databases (= size of current45.efdb bigger than 150MB).

The built-in Financial Reports performance improvements are split in two parts:
a) "caching" (or pre-calculating and temporarily storing the results) of the most needed "Input" data during the start-up of the fw Server application. This can save time and reduce computing later. The "input data" is therefore "already ready" before any user has created a Financial Report.

b) "threading" of the actual fw-Client-FinancialReport-connection to the fw Server. This means, that the creation of the Financial Report no longer has an impact on the running fw Server session. It now only affects the user who is generating the Financial Report. This now no longer blocks the connection for everyone else, while the Financial Report is being created.

There are now these 3 new fw Client side Settings which allow to disable or enable this functionality in fw Client > Toolbox > Settings > Server Setup >

1) "Use Threading For Financial Reports":
This is enabled by default.

fw Server-side and technical details:
The memory usage of the fw Server application during run-time will increase by around 30%.
During the launch of the fw Server application, this will create within the fw Server's "system" folder a file called "init_worker_thread_flag".
And on the fw Server's "Log" window this info will show this line:
"Starting Up Worker Threads".

The "init_worker_thread_flag" file gets removed again, when shutting down the fw Server application if there were no issues during runtime. Should this file be present during the launch of the fw Server application then this will cause this line to be stated on the fw Server's "Log" window:
"Skipping Worker Thread Startup since it looks like previous startup failed".
Then the next graceful shut-down of the fw Server application will then remove this file, for the "Use Threading For Financial Reports" to be active again on the next fw Server start.

NOTE:
This new functionality does NOT take effect when doing Financial Reports on a single Project and up to max. 3 selected Projects!
In order for this new functionality to become active 4 or more Projects need to be selected to run a Financial Report on.

ONLY if the following Setting "2) "Keep Thread Data Updated" is DISABLED (= not ticked), then when creating Financial Reports on 4 or more Projects, there will now be a yellow triangle "Warning" icon on the "Generate Report" button, which will shot this info on mouse-over:

"The Report Data Being Used Was Last Refreshed:
x-time Ago.
Click To Refresh Now"

"x-time" is based on the latest time the "Financial worker thread" was last updated.
It is now the user's choice to generate the Financial Report based on the existing cached data by using the "Generate Report" button. Or to trigger an update to run the report on the latest data, simply by clicking on the yellow triangle Warning icon.

2) "Keep Thread Data Updated".
This is enabled by default.
And this feature simply ensures that the new "Financial worker thread data" gets updated before each Financial Report. This causes the above mentioned Warning triangle icon to appear, since the worker thread data is up to date.

3) "Use Caching For Financial Reports":
This is enabled by default.

Technical details:
This creates a NEW "caches.db3" SQLite-helper DB within the fw Server's "system" folder.

 

Inside "From Budget", there are now "Subtotal Before Global Budget Operators" fields for Actuals as well as Budget.

See Details

In the "Budget" grouping, and in all places where there's a "From Budget" field group, there was already a field called "Subtotal Before Global Budget Operators".
But that field only contained the subtotal (Sell) for the *Budget* numbers. All other modes such as e.g. "To Invoice / Used / Booked" were unavailable.
Now these are all available, inside a new field group called "Subtotals":
- Subtotal (Budgeted) Before Global Budget Operators
- Subtotal (To Invoice / Used) Before Global Budget Operators
- Subtotal (To Invoice / Used / Booked) Before Global Budget Operators
- Subtotal (Used) Before Global Budget Operators
- Subtotal (Used / Booked) Before Global Budget Operators
- Subtotal (Booked Only) Before Global Budget Operators
- Subtotal (Invoiced) Before Global Budget Operators
- Subtotal (Quoted) Before Global Budget Operators
- Subtotal (To Invoice) Before Global Budget Operators
- Subtotal (Comparison Budget) Before Global Budget Operators

 

New fields added to Financial Reports to be able to display values from Scheduled Invoices

See Details

The following additions have been developed to allow generating a report on projects with "Scheduled Invoices".

There is a new setting in the Financial Reports General Settings called "Inc. Only Scheduled Invoices”. When this is enabled only scheduled invoice values will be displayed in the report, leaving out any other source types (e.g. actuals, budget details, media orders, ...) from the selected Projects.

The new Group "Scheduled Invoice Month" has been added to Financial Reports to group Scheduled Invoices by month. The value in the Financial Report will show the month name based on the Scheduled Invoice Date.

Added new Elements:
> to the new "Scheduled Invoice Month" Group:
- Description: Month Name and Year (e.g. December 2018, January 2019, February 2019), sorted chronologically
- Scheduled Invoice Fixed Price: total based on the Scheduled Invoice Fixed Price
- Schedule Invoice Fixed Price (Invoiced): total based on the invoices created from the Scheduled Invoice

> to the "Project/Media Order/Unref.Invoice" Group:
- Scheduled Invoice Fixed Price: total based on the Scheduled Invoice Fixed Price
- Schedule Invoice Fixed Price (Invoiced): total based on the invoices created from the Scheduled Invoice

> to the "Rows" Group:
- Scheduled Invoice > Name
- Scheduled Invoice > Note
- Scheduled Invoice > Date
- Scheduled Invoice > Invoiced: Yes/No
- Scheduled Invoice > Invoice Name And Number: from the invoice created from the Scheduled Invoice
- Scheduled Invoice > Scheduled Invoice Fixed Price : total based on the Scheduled Invoice Fixed Price
- Scheduled Invoice > Scheduled Invoice Fixed Price (Invoiced) : total based on the invoices created from the Scheduled Invoice

- to the "Header" and "Footer" Groups:
- Scheduled Invoice Fixed Price: total based on the Scheduled Invoice Fixed Price
- Schedule Invoice Fixed Price (Invoiced): total based on the invoices created from the Scheduled Invoice

 

Fixed a bug showing wrong Note in the "Budget Account (Assigned)" grouping, see details.

See Details

It was showing the note from "Budget Account" instead of "Budget Account (Assigned)". This is now fixed.

 
#316702

Fixed wrong calculations of Break Hours and Date, when filtering by lines in a date range in the Financial Report.

 
#317125

Made the Note from Invoice lines take priority, see details.

See Details

When the Financial Report merges information from different sources, such as a Budget and an Invoice, it may find conflicting information. For example a note that has a different value in each place.
Previously, it would choose to display nothing in such cases. Which meant that if you edited the note on an Invoice line, it may not be carried over to the Financial Report.
Now it tries to be smarter about it, so a note from an Invoice takes priority over other sources.

 

Frameworks

Added a "Warning Message" when using a Booking Template that contains an inactive Object Class, which offers to change to a different Class, see details.

See Details

If a Booking Template contains not active Object Classes, now a Warning pop-message will list the Object Classes that are no longer active.

Then, after having created the Frameworked Bookings from a Booking Template, a yellow triangle icon with mouse-over info "Object Class No Longer Active" will be displayed in fw Client > Long From > Projects tree > Frameworked Booking > next to the not active Object Class created from the Booking Template. Double click on the non-active Object Class and exchange with an active one.
The user can then save the changes as a new Booking Template via drag-and-drop on to the Toolbox > Saved Templates button.

 

Added support for getting a Booking History entry when Booking Framework Name is added, changed or deleted.

See Details

When a Framework Name is added to, changed or deleted from a Framework Class, an entry will be added to the Booking history, showing the Framework Name: "xx" (Object Class/ User/Object Name). When changed the entry will display Framework Name "xx" changed to "yy", when deleted it will show Framework Name "xx" changed to " ".

Click on the Framework Class "Editor", to get into the Edit window, where you can add a Framework Name "Early shift'.
The History entry will read "Framework Name: Early shift (Editor/ )"

 

Fixed a bug by which when creating a framework from booking templates, and containing breaks, the framework data was being corrupted causing a client crash.

 

Fixed a bug displaying inactive Object Classes in the New Framework From Class menu

 

Reapplying Booking Templates should cause Conflict windows, and color of Pending User?s Approval (PUA) should show red when conflicting

See Details

·Now, when a conflict appears on a confirmed booking with another booking that the user has approved, but can not be confirmed due the prior confirmed booking, the background on the framework will be the same as in the hourline: The one you have set for preliminary bookings.

 

General

Added "Show Options In A List" to the drop down menus where they didn't show before due to lack of stored lines

See Details

Before the "Show Options In A List" only showed if you had a specific number of submenu lines. So you had to go through the sub menus to find the desired action. In the Dispatch module > right mouse click you didn't have the option to use the "Show Option In A List". Now you do, which enables you to get faster to your desired action. In the Popup when booking in the Hourline it also would only show if you had sufficient Projects in your database. This has now been fixed and the "Show Options In A List" will show on all drop down menus with at least 20 entries (lines).

 

Disabling SSL support. Versions 2 and 3 of SSL are no longer supported by Farmerswife.

 

Groups

Added Inventory Number between parenthesis next to Object in the Involved pane to easily see the particular Objects a Group consists of

See Details

The Inventory Number of the Involved Objects has been added between parenthesis next to the Object, in the following places:
- in Object Manager > Type: Group > Modify window of a Group > Involved pane
- in Object Manager > Type: Group > Modify window of a Group > Involved pane > menu to choose Object to add as involved
- in Toolbox > Objects > Group > when double clicking on Group Object to see info
- in Houlrine Views and Objects tree > when double clicking on Group Object to see info

 
#321584

Fixed a fw Client crash when in Object Manager > Groups and clicking and selecting an Involved Object within the "Modify" Group window.

 

Hotkeys

It is now possible to add a Hotkey to turn on or off the setting "Never Select or Book Weekends Or Public Holidays"

See Details

The Hotkey editor is found in the Toolbox section Miscellaneous. The setting "Never Select or Book Weekends Or Public Holidays" has been added to the Functionality list. This setting is used for multi day bookings to define wether to include or skip the Weekends or Public Holidays.

 
#311190

Improved when using Hotkeys to run Financial Reports from Long Form > Personnel tree and added a dialog, see details.

 

Fixed issues when running a Financial Report via a Hotkey, see details

See Details

1. Now it is possible to trigger a Financial Report hotkey when no Project on the Project tree is selected. So if no Project from the list is selected (marked in blue), the Financial Report will consider all of them as source.

2. Now it is also possible to select Users from the Personnel tree to trigger a Financial Report hotkey. Before User could only choose Objects from Objects tree.
If User selects Objects/Users from Object tree and also from Personnel tree, as he triggers the hotkey, he will be prompted to choose one or the other: “Multiple Selections Exist. Choose Which To Use For The Report”, by choosing a button: “Objects Tree” or “Personnel Tree”

3. Fixed bug that was preventing to trigger the same Financial Report hotkey for a second time right after leaving the Print Designer window.
If User had triggered the hotkey and was inside the Print Designer and by mistake clicked OK so he left the window, if he wanted to go back, the same hotkey would not work again.

4. Fixed a bug that was preventing a deleted Financial Report hotkey to be completely removed from the server.

 

Hourline

Added Inventory Number next to Object name in Hourline

See Details

If setting "Inventory / Full Name" (Toolbox > Settings > Display) is enabled, the Object's Inventory Number, if any, was already displaying in Objects tree and in Bookings.
Now, it also shows in Hourline.

 

Hourline views loaded in Objects Tree now support Object Classes as well and Grouping From Classes also adds the Object Class in the Grouping in the Hourline

See Details

Implemented a feature, so Object Class that have been added to an Hourline View will now also been shown in the Objects tree, where they haven't been shown before, even if the Object Class had been saved in the Hourline View.

A new setting has been added to Toolbox > Settings > Server Setup: Add Object Class To Grouping From Class in Hourline Views.
If this is ticked and you create a view via: Hourline icon > Options > New Grouping From Class, the Object Class will automatically be added to the Grouping as an Object line, allowing you to see Bookings on the Object Class in the same View.
This has not been optimized for iOS or the Mobile Web Client (it will show the name the pure Object Class Object line twice).

 

Fixed a bug when clicking on a "Checkpoint" icon this would wrongly open the Edit Booking window, see details.

See Details

In fw Client > Hourline when clicking on the Checkpoint icon which indicates the currently set status, the Booking window would wrongly open.
Now the correct Checkpoint sub-menu pops-up again, in order to change the Checkpoint.

 

Icons

Added new icons to the "Users" section and "Others" section, see details.

See Details

To change Object icons go to fw Client > Object Manager, then search and double click on the Object you want to change the icon. On the Modify window click on the Object's icon to select a different one.

Take care when changing icons of Objects, as this might lead to confusion or irritation among your colleagues.

 

New User Icons

See Details

A new range of icons have been added to the user section

 

Added many country flag icons

 

Invoice Creator

Improved for the "Closed Projects and Done Media Orders" pane by showing "(P)" or "(M)" on the "#" Number column to distinguish between the two, see details.

See Details

In the Invoice Creator in the top left on the "Closed Projects and Done Media Orders" pane now shows on the "Number" column ("#") after the source Number:
"(P)" for Closed Projects.
"(M)" for Done Media Orders.

 
#310216

Fixed a bug when changing the Creation Date of an Invoice, this wrongly caused the changed Invoice's selection to get lost, see details.

See Details

For this bug to happen, required these fw Server > Setup > Financial tab settings to be configured as:
- "Assign Invoice Number When Creating" > No
- "Use Pro Forma Numbers" > Yes

Then, when selecting an Invoice (= high lighted yellow) and changing its Creation Date, this caused the selection to get lost and due to Invoice being re-sorted caused the wrong Invoice to be selected (= high lighted yellow).

This is now fixed, and farmerswife now correctly keeps the correct selection.

 

Invoice Editor

Fixed the Invoice Editor field "Total In Entries" that was wrongly hidden behind "Buy Total" field when adding "Fixed Price" to an Invoice.

 

Invoicing

Added for the setting in Invoice Creator > "Automatically Creates Internal Invoices When Invoicing" to now also apply to "Part Invoice".

 

The new feature "Scheduled Invoices" allows preparing an invoicing plan per Project

See Details

This feature makes it possible to create a scheduled plan of invoices on set dates and with a fixed amount.

It is especially useful for rental houses that manage long hires (bookings that lasts for months), and need to prepare a schedule in advance of the invoices to be generated per project and on a specific date.

When an invoice from this scheduled plan is created the fixed price will show as a pre-payment line and also list the items (equipment, services, etc) that have been booked/used in that period as a reference.

>> How to enable "Scheduled Invoices":
To enable this feature, go to Toolbox > Settings > Server Setup > "Enable Scheduled Invoices"
When this has been enabled a new area is added at the bottom of the Edit Project window to manage "Scheduled Invoices". The Project option "Show Invoices / Credit Notes" (in the Project's Eye menu) must be enabled and the User must have permissions to invoice as well.

>> How to prepare "Scheduled Invoices":
In the Edit Project window, click on the Schedule Invoices menu and select New Scheduled Invoice. Fill in:
- Name: this Name will be displayed on the Invoice name next to the Project name.
- Fixed Price: click on the wheel icon next to this field to enter the fixed price for the scheduled invoice.
- Scheduled Date: the date when it will be available for invoicing.
- Division: if licensed, it takes by default the Project's Division.
- Note: a note icon appears next to the scheduled invoice with the note entered here. This note can be populated in the Financial Reports, Rows section.

Choose "Remove A Schedule Invoice" to remove a scheduled invoice.

Once invoiced, Scheduled Invoices in this list cannot be modified.

>> New option on the "Active / Pending Projects" pane of the Invoice Creator:
- New column "Scheduled Invoices Ready", with value "Yes" on Projects with pending Scheduled Invoices for Scheduled Dates today or in the past. The value "No" will show on Projects that have Scheduled Invoices for a future date, or with no Scheduled Invoices at all.
- New menu option "Show Only Project With Ready Scheduled Invoices". When enabled, it allows searching only on projects with scheduled invoices set to today or past dates.
- New menu option "Create Invoices For Scheduled".

>> Invoicing Scheduled Invoices:
Search for Projects that have Scheduled Invoices Ready to be invoiced (using a combination of the new options above).
When selecting more than one Project, and clicking on the drop-down menu, use the option "Create Invoices For Scheduled", and confirm the dialog "Confirm Creating x Invoices From Scheduled".
As a result, individual invoices will be created for each of the Scheduled Invoices.
When selecting only one Project, the drop-down menu will read "Create [Scheduled Invoice Name] / [Project Name (Project Number)]".
When a Scheduled Invoice is invoiced a yellow triangle is added next to the Scheduled Invoice in the Project window to show it has been invoiced. Clicking on the triangle will show the option to Find Invoice, which will open the Invoice.

About the Invoice created from a Scheduled Invoice:
In the Invoice Editor window all items pending to be invoiced in the project with a date before the Scheduled Date will show. The Amount for each line is set to 1, Unit Name to Fixed, and the Sell to N/A. This list is only for reference as you might want to show it in the invoice print out, but shows no amount nor pricing per line. In the invoice print template the list of items can also be displayed.
At the very bottom of this list the Prepayment line for the Scheduled Invoice Fixed Price is displayed.

 

Labour Rules

#317952

Added support for editing "Extra Earned" in Closing Points, see details.

See Details

Inside Closing Points, it was already possible to edit "Sabbatical/Freeweek/Training Earned But Not Usable At Period End".
Now the same support has been extended to the "Extra" type.

 

The "Current" Labour Rule Name can now be shown in the Object Manager if selected in sub-menu > "Columns" > "Labour Rule".

 

Fixed bug sometimes causing incorrect "Earned" numbers for Sabbatical/Freeweek/etc.

See Details

This bug happened when an "Earned Type Rule" such as e.g. Freeweek had a release period using "Months" as unit (e.g. every 12 months).
It only happened in the first month after an employee's release date for that number.
And it only affected the "Earned At Period Start" value.
What happened was that it would show the same value for "Earned At Period Start" as the "Earned At Period *End*" number, caused by a calculation bug that is now fixed.

 

MacKiosk

#321920

Adjusted Conflict Messages that appeared as many times as days an item was to be to checked out via MacKiosk, see details.

See Details

Now, MacKiosk will only show one Conflict Message in the Conflicting Items window.

 

Mail Sending

Changed the amount of "retries" after "FAILED: Error sending mail" from 5 to 10 and added

See Details

Also implemented improved fw Server-side logging for the log.txt; added:
"Retrying Sending email (variable error info)"
... and:
"Error Sending email (variable error info)"

 

Maintenance

#320612

Fixed a bug when booking an Object on Maintenance that was no triggering Conflict Warning messages for future Bookings.

 

Media Library

#318485

The dropdown list of "FPS" in the Media Library > Edit Media window has been updated with new values: "59,94" and "59,94i".

 
#321435

Fixed a fw Server crash bug on trying to change a Media Library > Entry Custom Field.

 

Media Orders

#316140

Changed search result behaviour in fw Client > Toolbox > Media Orders > Pending filter. See details!

See Details

If the Max. Search Hit Limit had been set to e.g. 100 and you had a lot of Media Orders in fw Client > Toolbox > Media Order (MO) pane, the latest / newest created would not appear in the current list (when setting cursor in search field and hit "Return"), even if the Media Order Deadline was today or it was set to Urgent.

This is now changed and the below sorting applies:

If the filter is set to “Pending”:
• Urgent Media Orders show on top, followed by MOs with Deadline (sorted by date).
• Urgent Media Orders with Deadline are sorted by Deadline date (not MO Number).

If filter is set to “All”:
• only “Urgent” MOs show at the top, sorted by MO Number.
• the rest of MOs that have Deadline (but not Urgent) keep their position (MO Number)

 

Fixed a bug wrongly causing in the Media Order Print Designer that some Elements were not being displayed when generating a Media Order Report, see details.

See Details

The Name of the Source Media on a Media Order was not being displayed in the Media Order Report Print Designer.
It is now displaying correctly: Media Order Report > Element Row > Name.

 

Mobile Web Client

Added Framework Name to the Involved window of the Booking and in the Day Plan View

 

Mobile Web Client showing wrong event date when opened via "Events by week"

See Details

When selecting an event, it was displaying the last day of the week, now it is displaying the day of the event.
The start of the week was Sunday on the Mobile Web Client. Now it has been fixed to start on Monday.

 

Notifications

Ensure "Notifications" are OFF if NOT configured.

See Details

·A new setting has been created in the fw Client > Toolbox > Settings > Notifications > a new setting called "Sillence All Notifications".
·If this settings is checked, the other settings at the Notifications part become disabled and no notification will be sent.

 

Object Baskets

#317361

Added a new column to fw Client > Toolbox > Objects tab > Baskets, to show the Basket name that an Object belongs to.

 

Object Browser

Added a Division selector to the Select Objects window within the Edit Booking window, to be able to search Objects by Division.

See Details

A new Division selector has been created on the Select Objects window that pops up when clicking on the "Involved" icon in the Edit Booking window.
The filter is applied alongside the other filters already present in that pop up window.

 

Object Classes

Object Classes can now be set to "inactive" (Active = No), see details.

See Details

Object Classes could previously not be set to "inactive" and this caused issues when you would need to change and update the Object Class structure. Removing an Object Class is not recommended as important information on existing Projects will get removed.

When an Object Class is set to Active = No the following happens:

- "Inactive" Object Classes can be hidden in the Object Manager by disabling the setting "Show Inactive" from in the Object Manager sub-menu > Settings > "Show Inactive" Yes/No.

- "Inactive" Classes can be hidden in fw Client > Toolbox > "Classes" tab, by disabling the setting "Show Inactive" in the Toolbox's sub-menu. You can still double click on an inactive Class there and it will take you to the Objects tab to show the members that used to belong to it.

- On Objects that "belong" to an "inactive" Object Class will not show this relationship and the do not inherit this Object Class's Activities any longer.

- "Inactive" Classes keep their configuration of Members, Rates and Activities, in case you should need to re-activate them.

- When a Object Class used as a Parent Class is set to "inactive", then the "Parent Class" field on Classes that were using it as a Parent is reset to "None". It still shows on the right-side pane when using in the Object Manager sub-menu > Second Window Shows > "Object Classes As Tree", because in case it is re-activated, the configuration re-applies to Classes it had as Children.

- "Inactive Classes" do not disappear from "Saved Hourline Views" or Long Form "Saved Views", but if you try to book them you get a warning that they are no longer Active.

- If an "inactive" Class was part of a Framework Booking Template, when re-applying this Template, the inactive Class remains, but it shows a warning icon saying "Object Class No Longer Active". This allows the user to see what it was and change to another new Class by double clicking on it and choosing from the different Class from the selector. If you try allocating a member on the Framework, there will be a warning "Object Class Is No Longer Active".

- You can still generate Financial Reports on "inactive" Classes.

- "Inactive" Classes are still displayed in the Booking, Project, Invoice, Purchase Order or Incoming Invoice where they were used.

- "Inactive" Classes are kept in Rate Cards where they were used, so the link is not lost in case they need to be re-activated.

- "Inactive" Classes are kept in saved Global Budget Templates, so the link is not lost in case they need to be re-activated.

- "Inactive" Classes are kept as an External Object in the Supplier Details of a Contact, so the link is not lost in case they need to be re-activated.

- "Inactive" Classes are not shown in the Web Client, Mobile Web Client or iOS farmerswife app, when searching via the "Choose To View" window or when trying to add and Object Class via the Involved tab in the Booking window.

 

Fixed multiple bugs that were causing wrong results when searching for inactive Class Members in the Object Manager.

 

Object Importer

Added feature to import and export Accessories via the Object Import/Export functionality in the Object Manager

See Details

Added a new setting in Object Manager > Import/Export farmerswife Objects Format CSV File > Import / Export Accessories.
When enabled, Accessories will be exported and imported when using this option.

There is a new Accessories column in the csv file that is for visual information only. You can't add or delete Accessories this way.

Export:
The main Object will be the first line, displaying in the rows below any Accessories the main Object has. A new "type" was created for the this functionality called: Accessory (with the name of the Object manager type in brackets). This is only available in the spread sheet and not in the Object Manager itself and only serves to indicate that this Object is an Accessory. Accessories can be Objects or Object Classes.

It is possible to determine the order of the Accessories. The first Accessory below the main Object will be the first Accessory when booked. By juggling the rows in the csv file it is possible to sort the Accessories to your needs.

Import:
If you import an Object that hasn't been created in your database yet, you can import it as an accessory to a main Object by placing it below the main Object and altering the type to "Accessory" (type of Object Manager) e.g. Baseplate Accessory (Equipment/Machines).
Object Class Accessory: HDD Drive "Accessory (Object Classes)". The imported Object will be created in the farmerswife database and will be Accessory to the main Object.

 

Object Manager / Server Setup

Added "Only If Owner" to "Object Permissions" to allow the user with this set, to only have access to Bookings he created.

 

Made custom fields columns in search window to show at fixed width to avoid long text making the column too wide.

 

Objects

Added Inventory Number of Object Accessories, and icon of Class Accessories to some columns and windows where these were missing

See Details

To clearly see what a kit is made out of, the Inventory Number of Object Accessories were added to some missing places:
- the Accessories column in the Object Manager
- the Accessories column in Toolbox > Objects tab
- the Advanced window of the Object Modify window
- the Advanced window of the Class modify window

And the Class Accessory Icon was missing from the Advanced window of the Object Modify window.

 

Implemented to be able to setup an Object Ranking per Object Class.

See Details

The Object Ranking was developed to use with Framework Bookings, however it can also be used in a limited way for Class Bookings.

To be able to use this setting an Object Ranking has to be setup. The setup option is available for all Users with Server Setup Permission. User without Server Setup Permissions will just be able to use the default created Object Rankings and use the option "Other".

1. Setup Object Ranking
In the Object Manager open an Object Class and click on the drop down menu in front of one member of the Object Class > Ranking > Setup Rankings.
The "Setup Rankings" window opens > click on the green plus to add a new Ranking. The Ranking can be sorted by pulling it up and down in the list or by clicking on the blue sorting arrows.
To delete a Ranking, grab it and drag and drop it into the trashcan.

2. Add and Remove a Ranking to a User
Open the Object Class > click on the drop down menu in front of the User > Rankings > choose an Option.
The option "Other" can be used to type in any Ranking that isn't in the default list. This "Other" option won't be available later on. It is a one time only option.
To remove a Ranking from a User, just click on the Ranking in front of the User in the Modify Object Class window and confirm the removal.

3. Change a Ranking on a User
Go to the Object Class of that User, click on the drop down menu in front of the User and select a different Ranking - the current one will be replaced with the new one.

4. Show Object Ranking on Framework Bookings
The Object Ranking will show after the User's name in brackets "User name [Object Ranking] "in the drop down menu on an empty Framework Cell so you can select the User.
When a User is booked, the Object Ranking will show in the yellow mouse over in the "Object Allocated" line after the User name in brackets.
Object Rankings don't show on Class Bookings (How to use Object Ranking with Class Bookings see below)

5. Show Object Rankings in Objects Tree
The Object Ranking can be shown in the Object Tree if the option is used:
Object Tree icon > Load from Object Class > select Object Class. The Objects are loaded and while hovering over them (yellow tooltip) and in brackets after the User name.
The Ranking will also show if you load the Object Class by using the magnifying class next to the Object Tree.

 

Virtual Objects won't cause conflicts anymore, as the "Causes Conflict" check-box will be disabled once the "Allow Multiple Check Outs (Virtual Object)" setting is set, see details.

See Details

Before you had to manually set the Virtual Objects to not cause conflicts, by un-ticking the "Causes Conflict" check-box.

 

Fixed a bug by which replacing Objects with Accessories or Groups with Involved Objects, was causing duplicates Children Objects, when selecting a time range.

 

Fixed a bug that was making Objects configured to not cause conflicts, to get the setting Allow Multiple Check Outs (Virtual Objects) enabled

See Details

Objects configured with "Causes Conflict" disabled, were getting the "Allow Multiple Checkouts (Virtual Objects)" option enabled. This was also happening on databases without EMT enabled in their license - only that the option was hidden and could not be accessed.

 

Fixed a bug when Replacing an Object with Accessories.

 

Objects Tree

Added Object's Inventory Number to the mouse over when hovering over a Booking in the Objects tree

 

Added a new option to Objects tree menu to View Availability On Groups

See Details

Until now it was not possible to see whether some Involved Objects of a Group were booked, if you wanted to book the whole Group (kit). Now when booking a Group, you get a conflict displaying all those Objects that are part of the Group and that are not available due to confirmed Bookings on them.
Thanks to this new functionality you can see if a Group is fully available before booking it.

Load a view with your Groups (kits) into the Objects tree.
To enable this new view mode click on the Objects tree icon > View > View Availability On Groups.
A yellow warning triangle shows next to the Objects tree icon indicating this view mode is on, and mousing-over it a tooltip shows 'View Availability On Groups.'
To disabled it, click on the yellow warning triangle, or on the Object tree icon > View > Off.

When enabled, a yellow warning triangle is displayed on those days that a Group has at least one of its Invovled Object booked on a Confirmed Sub-Status.
If the Group is made out of Class Members, Bookings on these Classes will not trigger this warning triangle.

Mousing-over the triangle, a tooltip shows information about which Involved Objects are not available due to a Confirmed Booking on them:
Unavailable: Object Name and its Inventory Number between brackets. E.g.: Small Car (123)

If Involved Object is booked on a Preliminary or Planning Sub-Status, there will not be a warning on the Group.

The moment a Group is booked on a Confirmed Sub-Status, the warning for that Group and that day disappears. But if the Booking is on Preliminary or Planning Sub-Status, the warning (if any) will display on top of the Booking.

 

Added a new setting to show a "Note" icon on the Objects tree if an Involved object in a Booking has a Note.

See Details

To make the Note visible you need to enable it in Toolbox > Settings > Objects Tree > Object Note Icon.

 

Added support when dragging and dropping a single Object Class from Toolbox > Classes to see "Class Name" and amount of Involved Members in square brackets, see details.

See Details

When you now drag and drop a single Object Class from Toolbox > "Classes" onto the Long From > Objects tree you will then see the "Class Name" and amount of Involved Members in square brackets ext to the Objects tree icon.

 
#309881

Added that the Object Class Name can be displayed in square brackets next to Long Form > Objects tree icon "Objects [Object Class Name", see details.]

See Details

If a single Object Class is loaded into the Long Form > "Objects" tree, now its name will be displayed in square brackets; to more easily see which Object Class the loaded Objects belong to.

To add single Object Classes to the Long Form Objects tree:
- Use in Long Form > the Objects tree icon click > "Load From Classes".
- Or use the magnifying-glass "search" icon next to the Objects tree
- Or by dragging and dropping a single Object Class from the Toolbox > Classes tab onto the Objects tree.

 

If setting "Binder / Framework / Class" is enabled, the class name will now display on the booking in the Objects Tree (previously only showed when booked as part of a framework)

See Details

NB - in order to see more than 1 line of text in the objects tree, the Display setting "Line Height" must be set to 30

 

Implemented for the Long Form > Objects tree these two new Filter options: "Preliminary" and "With Conflicts", see details.

See Details

In fw Client > Long Form > Objects tree you can now use two new Filter options:
1. "Preliminary" - shows all the Bookings that have:
- Global Status Preliminary - in yellow
- Actual Status Preliminary (Conflict) - in red

2. "With Conflicts" - shows all clashing/conflicted Bookings in red, so you can easily see them.

 

Implemented to show in the Long Form > Objects tree the amount of active Class Members between brackets next to the Class Name, see details.

See Details

This functionality is like how it has been in fw Client > Long Form > Class Availability tree.
It will only show active Members.

 

Multi Select Bookings in Objects tree to 1: Force confirm multiple conflicting bookings 2: Apply a User Approval Status on multiple bookings in one go

See Details

This Multi Select Bookings functionality was initially developed in version 6.4 to be able to apply an 'Invoice Received Status' across multiple Bookings at once.

It can now also be used to 'Force Confirm' multiple conflicting Booking Objects at once, and to apply a 'User Approval Status' on several Booking Objects in one go.

To use the "Multi Selecting" go to fw Client > Long Form > Objects tree icon and select > "Start Multi Selecting Bookings".
A little yellow triangle "Multi Selecting" icon will indicate that you are using the "multiple-selection" mode.
Once you have finished, either click on the triangle icon to end the "Multi Selecting" mode or choose the option in fw Client > Long Form > Objects tree icon click > "Done Multi Selecting Bookings".

As soon as the Multi-Select mode is enabled you are able to mark different Bookings for an Object or various Objects at the same time. The multiple selected Bookings will get highlighted with a yellow frame around them. After having selected the Bookings within the Long Form > Object tree > View Port area, click again on the Objects tree icon and select one of the appearing options:
- Invoice Received Status: No
- Invoice Received Status: Under Review
- Invoice Received Status: Yes
- User Approval Status: Disabled
- User Approval Status: Pending User's Approval
- User Approval Status: Declined By User
- User Approval Status: Declined By User (Read)
- User Approval Status: Accepted By User
- User Approval Status: Accepted By User (Read)
- Force Confirm

The multi-select mode only applies to Task Bookings, Project Bookings and Media Order Bookings. Personnel Bookings can't be selected.

The first three options will only show if the "Invoice Received Status" functionality is enabled in the Server Setup. Refer to the corresponding articles in our Knowledgebase for details on how to configure and use the 'Invoice Received Status' and also the 'User Approval Status' functionalities.

 

Fixed a bug by which the Objects Tree was not loading Objects from an Hourline View made out of Classes through Options > New Grouping From Class, when a new Object was added to the members list of a Class via the Object Manager

 

Fixed a bug that when removing a selected day of a multi-day booking via Object tree, was removing a different day

See Details

Now when removing a booking from the Object tree using drag&drop, the option "Remove Only On Day:" will display the correct day that was selected.

 

Performance improvement in the Objects Tree by which the process of drawing of all the bookings rectangles and texts is now much faster.

 

OpenID

Implemented fw Server-side changes for AppleConnect via the fw Client desktop app.

 

PDF Printing (server side)

#319255
#318940
#319385
#319756
#303918

Implemented a new "Use Built-In Printer" functionality (fw Server-side only), based on Ghostscript, see details!

See Details

This new fw Server-side Built-In Printer replaces the need to have a 3rd party virtual printer to be installed and used for the "PDF Print Export Settings" functionality within the fw Server > Setup > General tab. If or as soon as the "PDF Print Export Settings" feature is Enabled (=Yes), you will see a printer icon with the info "Using Built-In Printer".

It will use the same previously set "PDF Repository Directory" configuration.

It uses Ghostscript 9.27 (2019-04-04), which gets installed automatically during the upgrade to 6.5 Beta 11 or later.

IMPORTANT:
We strongly recommend that you un-install the previously used "PDFCreator" installation on Windows. And while doing so, we also strongly recommend that you take the time to ensure that you also remove the never needed and wanted "PDFArchitect" app, if it was ever installed.

 

Cleaned up low-level debugging code and thus fixed a potential issue when launching fw Server PDF Export from the iOS fw app.

 
#319385

Fixed multiple issues causing fw Server and Client crashes when printing any kind of Report via the fw Server-side PDF Print Export.

See Details

Verbose print logging is still enabled on 6.5 Beta 7.

 

Implemented fixed 3rd party "printer.dll" library for the new "Windows-x64" and also improved the fw Server-side error handling on "Test" PDF print-outs on server-start.

 

Password Policies

Added option to "Exclude Users From Password Expiry", see details!

See Details

It's now possible to exclude users from "Password Expiry".
This is intended to be used e.g. for 3rd party integrations like using the "fw REST API", etc., where a registered and active user must exist, but where it can be problematic to change passwords once a month.

To use this option, go to:
a) fw Server > Setup > Users > Password Policies > "Exclude Users From Password Expiry" button.
b) fw Client > Toolbox > Settings > Server Setup > Password Policies > "Exclude Users From Password Expiry" button.

Click on this button to select the user(s) to be excluded from the "Password Policies > Expiry" option.
Once "Selected", their Password will not expire.

IMPORTANT NOTE:
It is possible to use the "Force Changed Password On Next Login" if needed, even if this user is selected to "Exclude Users From Password Expiry".

 

Implemented for the "Password Policies" to allow to exclude users from the password expiration policy, see details.

See Details

This feature is intended to be ONLY used for integrations e.g. with the 3rd party system, when a farmerswife user is needed, but where the "account" or better the password should not expire.

To use this new feature either go to:
a) The running farmerswife (fw) Server application > Setup button > Users tab > Password Policies section > "Exclude Users From Password Expiry" button.

b) Via the fw Client application as an Advanced User with "Object Manager" permission level > Toolbox > Settings > Server Setup > Password Policies section (at the bottom) > "Exclude Users From Expire Password" button.

Clicking on this button will open the "Select Users To Exclude From Password Expiry".
Move the users from the "Not Selected" pane on the left to the "Selected" pane on the right to set the exclusion from the "Expire Password Policy".

 

Implemented for the "Password Policies" to be able to "Force Change Password On Next Login" per single or multiple users, see details.

See Details

To use this new feature either go to:
a) The running farmerswife (fw) Server application > Setup button > Users tab > Password Policies section > "Force Change Password On Next Login" button.

b) Via the fw Client application as an Advanced User with "Object Manager" permission level > Toolbox > Settings > Server Setup > Password Policies section (at the bottom) > "Force Change Password On Next Login" button.

Clicking on this button will open the "Select Users To Force Password Change".
Move the users from the "Not Selected" pane on the left to the "Selected" pane on the right to trigger the forced password reset for one or multiple users on next log-in.

 

Personnel Bookings

#311699

Implemented to be able to edit multiple Personnel Headers at once with new option: "Set Header On Personnel Bookings On Selected Days", see details.

See Details

It is now possible to highlight one or multiple Users in the Long Form > Personnel tree, mark one day or multiple days > right mouse click > Personnel > "Set Header On Personnel Bookings On Selected Days".

Using this will add the "Header" (= examples misssing) to all selected Personnel Bookings, regardless which Type of Personnel Booking they are.

To delete (clear?) various Personnel Headers at once, select the days and the Users > right mouse click > Personnel > click on "Set Header On Personnel Bookings On Selected Days": by default this pop-up is empty and if you don't modify anything the selected Headers will be cleared or set to "empty".

 

When booking Personnel types over multiple days farmerswife now offers to remove the Object from conflicting Bookings, if any, only on the marked days.

 

Personnel Tree

Fixed a bug by which the Personnel tree was throwing an exception when loading a view

 

Price Agreements

#317673
#318867

Fixed a bug that was causing wrong calculations when invoicing a Project with multiple Price Agreements pointing to the same financial line.

 

Print Designer

Added a new option in Print Designer > Templates > Setup > "Group By Obj. Class (Primary)", see details.

See Details

Added a new check-box setting in Print Designer > Templates > Setup > called "Group By Obj. Class (Primary)".
This is available on Project Reports, Invoice and Dispatch Print Designers.

IMPORTANT: "Group By Obj. Class (Primary)" is designed to be used on Invoices created from "Scheduled Invoices", where a list of all Objects used to date is displayed with Quantity "Fixed".

This new setting "Group By Obj. Class (Primary)" offers the same data as the option "Group By Obj. Class", but it takes all those lines with the same "Primary Class" Name and groups them into one row.

 

Added support in the Footer section when using on Elements > Edit > Position > "Page" to be able to display multiple lines of text.

 

Implemented a proper re-write of the Print Designer > Page Breaks! See details ... your Template might be affected!

See Details

Multiple old legacy flaws (see below) had surrounded the Print Designer as such and its different "generators" (i.e. for Reports on Objects, Users, Bookings, Projects, Invoices, Financial Reports, Financial Exports, Dispatches, etc.) and the behaviour of "Page Breaks" and "Rectangles".

The BIGGEST changes are:
- We improved the "WYSIWYG" ("What You See Is What You Get") experience on Mac.
- "Page Breaks" now work! ... this might affect your Template.
- The bottom "Footer"-layout text elements are now aligned BELOW the "Page Break".

See these changes in this solution article with image examples: https://support.farmerswife.com/solution/articles/17000089047-v6-5-print-designer-page-break-re-write-related-changes
Use this video link 1.5 min.: << work in progress, please come back later >>

IMPORTANT after the upgrade to v6.5:
We recommend that you review each and every "Report" Template within your farmerswife system BEFORE you send out a Report to a customer!
Please create PDF test prints of your most used Reports. Then quickly verify that all is in order. If necessary make some minor adjustments.

What to look for?
- On multiple-page Reports.
- Text or other Elements being displayed within the bottom "Footer" section.
- Rectangles are being used.
- The "Page Break" (yellow-handle) and "Page Height" (red-handle) settings might now be too close together.

This is also a great opportunity to create a "Master Layout" Template. And to delete old, abandoned, bad and no longer used Templates.
We recommend to manually "Export" every "must stay" Template after the final changes, and store them in a good way (i.e. on a central safe location, incl. a DB-backup and the fw Server Installers for that version, etc.).

The "Page Break" rules that apply now:
- On the set vertical ("y" axis) location-value of the "Page Break" (yellow-handle) setting, that's where the page-break takes place.
- The next lower "element-value" after a page-break will be drawn on the next page.
- All "element-values" on that same "y" axis as the first element-value on the next page, will then be drawn "in-line" with the first one.
- For "element-values" from Custom Fields type Text which are configured to be part of the same "Table Name" will now be cut or delimited according to the length set on "Split On Space". This is to ensure the content within a "table cell" will not break the "table layout"; this prevents that wrongly entered too long text can break the intended layout.
- Images and Rectangles also follow these Page Break rules.
- You should now longer have to use "hidden" (= outside of printable area) "Rectangles" as layout-helpers! There are some exceptions to this rule. "Hidden" rectangles will most likely now cause that the designed layout will fail. Remove them one-by-one and adjust the used Elements accordingly until the intended layout is accomplished.
- Images in the "Header" section are aligned West and Top (start of the page "0" "0" coordinates).

- The bottom "Footer"-page-layout section goes from "Page Break" (yellow-handle setting) to "Page Height" (red-handle setting). The "Footer"-page-layout section does NOT follow the Page Break rules. The starting point of the "Footer" loop IS the Page Break position. In order to create more space for the Footer section, the Page Break needs to be moved manually. If the Footer-text-content is "bigger" than the available height of the Footer section, this will cause misalignments.

- The Print Designer "WYSIWYG" experience on Mac is now closer than before, when comparing with the PDF or print output.
- "Section-loops" have a starting point and Elements will be placed from this point onwards/down.
- Mixing data from one "Section-loops" with another loop can cause misalignment.
- When using elements with "Page" coordinates (= Edit > "Position: Page"), by design these do NOT follow the "Loop" convention; be careful and only use if necessary (i.e. when designing single-page Reports).
- If static information is needed at the bottom of the Page, then use the bottom "Footer"-layout section, and don't use the same data from other sections by forcing them to be located below the "Page Break"!
- If the "Header" content is bigger than one page, then using "Print Header In Every Page" will create misalignments.

- If you place elements using negative position values, these can create misalignments (better to move the next field below down-wards).

- "Totals" (e.g. "Sub Total", then below: "Discount", then below: "VAT" and then "Total") will be "grouped together" by using a Rectangle Element; then on a page-break these "grouped" Total Elements will "jump" together to the next page if a page break needs to take in-between these vertically "stacked" Elements.

- Should something fail during the print-process, this will create empty pages when printing. If this happens, please contact support@farmerswife.com, use the "Send Backup Now" button and provide usable replication steps, include screen shots and attach samples of the print-out as PDF.

NOTE:
- In Print Designer > Templates > Setup > "Resolution on Mac" ... values are being ignored, hard coded to correct "212". Setting is pending to be removed.
- In fw Server application > Setup > General > "Use Windows Resolution on OS X" <= Obsolete, in process of being ignored (?). Setting is pending to be removed.

 
#319385

Fixed a Beta bug wrongly causing empty pages when the last Element within the Header section was set on "Position" to use "Page".

 

Fixed a bug that was removing the "Space" character used as Split Character in a Split String Operator, in Print Designer

 

Fixed a bug when using "Position > Page" on a Element in the Header in the Header section and wrongly page break when the break is between row section and any other section

See Details

Fixed a bug when using "Position > Page" on Element in the Header in the Header section wrongly resulted in all text in the same line.
Wrong "Page Break" when having the break just before an element of a section who only have one item and after a row section on any report different than Project Report.

 

Fixed a bug when using "Position > Page" on a Element in the Header section and "Skip If Value Is Empty" enabled, this wrongly stopped displaying the following content, see details.

See Details

Bug when having "Position > Page" on a Element in the Header section wrongly stays at the top of the section.
For example a String Operator "Concat" consisting of 10 parts from 10 different Custom Fields, it would wrongly only show the first value.

 

Project Report

#321163

Project Report can now display elements "Amount (Before Fixed)" and "Unit Name (Before Fixed)" in the "Element Row" Grouping, see details.

See Details

When you set a Fixed Rate on Objects in the Projects View, you now have the option to display that Objects's unit name and amount as it would display before fixed rate was applied, in the Project Report.

Example: Setting a fixed rate of $350 for 10 hours on an Object, and selecting [Amount] and [Unit] name will display "1 Fixed".
The two new elements: [Amount (Before Fixed)] and [Unit (Before Fixed)] will display "10 Hours".

 

Project Window

#320502

Now it is possible to open a Project in Read Only mode when the Project is already in use by another User

See Details

When a User opens a Project that is already in use by another User, there will be a pop up with the following information "Project Is Locked By X Choose Open To Open In Read-Only Mode. If you open, close and reopen again while the first User is still using the Project the same pop up will be shown.

In Read-Only mode you cannot
- change any of the standard fields in the top left corner of the Project Window
- change any of the Custom fields
- modify the Budget
- add Extras (Services, Material, Expenses and Objects) directly from the Project Window
- change rates of Extras that have been added directly to the project within the Project window
- change View settings
- change Project Status
- select another custom template > meny icon for templates is hidden
- do various types of actions from the Eye menu as many items are hidden
- create Media Orders, Virtual Bookings, Work Orders

You can
- change the Rate on a financial line in a Booking, on both booked Objects and Extras
- edit a Booking > click on clock icon and select Edit Booking
- enter Budget window to view only

 

Accessories and other Groupings are now by default collapsed in the Edit Project window, see details.

See Details

Accessories or other Groupings (Groups with members) were by default always expanded in the Edit Project window. They could be collapsed and expanded individually or via the "View Settings / Options" eye-icon menu > Show Accessories / Group Involved > "Expand All / Collapse All".
Now the default behaviour has changed and is now set to have all "goupings" to be collapsed.
Use the above mentioned setting to "Expand All" if needed; or expand them individually as before.

 

Changed some % icons in the Edit Project window with dropdown and expand window icons instead

See Details

In the Edit Project window, some lines had a percent icon to change rates and to change quantity.
Now, there is a expand-window icon to edit rates, and a drop-down menu icon to change quantity.

 
#321759

Fixed an older bug wrongly allowing to open a Project again from a Booking from within an opened Project, see details.

See Details

Before you were able to e.g. open a Booking on the Hourline. Use the "Project" button to open the linked Project.
Then you can open a Booking from within the Edit Project window. But now the "Project" button is greyed out, indicating that it's now not possible to open the Project again. And here was the bug, that it was once more possible to open the Project. This is now fixed, and it's no longer possible to open a Project from a greyed-out "Project" button.

 

Projects

Fixed bug preventing the Name field from getting focus when creating new Projects.

 

Projects Tree

Added a search icon to allow the user to fast pick a project to view in the tree

 
#320516

Bookings can now be automatically sorted by Booking date in the Project tree, see details!

See Details

Bookings would always get listed under its Project in the Project tree in the order they got created, so last Booking created would go to the bottom of the list, regardless of the actual Booking Date. And you could always move them up or down the list to manually sort them.
But now, thanks to this new setting in Toolbox > Settings > Projects Tree > "Sort Bookings By Booking Date”, Bookings will get sorted respecting the Booking Date, rather than the Creation Date.
Beware that this setting now also affects the Edit Project window: the same sort-order from Project tree will be displayed in the according opened Project.
If the setting is OFF, the Edit Project window will show the same order as the Project tree, as well as the print out using the Project Print Designer.
This is a per-user setting that is enabled by default. So each user can decide how they would like to visualise the Bookings in the Project tree and Edit Project window.

 

Implemented improvements for fw Client > Long Form > Projects tree > "Auto From View Port / Calendar", see details.

See Details

The improvements are:
- To only show Active Projects.
- To only show Projects from "My Division"; if Divisions module is licensed and the User is configured to belong to a Division and not "Any".
- To only show "My Projects"
IF the corresponding checkboxes in Toolbox > Settings > Miscellaneous: Project Tree Popup / List Functions / Booking Type Popup are ticked.

 

Improved the "quick search" of the Long Form Projects tree (magnifying glass icon) which is faster and has improved functionality., see details.

See Details

In farmerswife Client > Long From > Projects tree there are now two ?quick search? options available:

Before:
In fw Client > Long Form > Projects tree, when using the magnifying glass icon "quick search" icon this opened the ?Show Options In A List? option, to be able to do:
- Simple search on all Projects
- Has ?Add Project Other > New? ? to create a new Project.

... to access this legacy quick search, click on the Project tree icon click and use "<Show Options In A Lis>".

NOW:
In fw Client > Long Form > Projects tree > magnifying glass ?quick search? icon click, you now get the new "Project Selector" pop-up window
or via ...
fw Client >Long Form > Projects tree icon click > ?Add Project <Search Projects>? ...

- It is a lot faster, especially when there are multiple thousands of Project within the farmerswife database.
- By default it will show the list of ?Recent Projects?.
- Has a bigger pop-up window with space to show more helpful info.
- More advanced search options, e.g. to match search words/terms separated by ?space?.
- It does not have ?Add Project Other > New? ? to create a new Project.

- Also optimised the pop-up when Booking in the Hourline and added ?Search?.

 

The Project Name will now always show on the project's visual "bar" in the Long Form > View Port irrespective of what timer period is displayed, see details.

See Details

When adding Projects to the Long Form > Projects tree, the Project Name would always be show at the beginning of the project's bar within the "View Port" area. This meant, that if you changed the date period in the Long Form > View Port in a way that you could not see the beginning of the Project, then the Project Name would not show. Now you can see the Project Name irrespective of the time period displayed within the "View Port". This is especially helpful for long-term Projects.

 

Fixed a bug in the Project Tree by which the objects allocated in a framework day was wrong after recent changes in farmerswife rev 17606, rev 17608 and rev 17623.

 

Purchase Orders

Fixed a bug when raising a PO from an External Object

 

The "Choose Template" window now pops up to allow choosing a custom field template when raising a Purchase Order from a Budget Detail.

 

REST Api

#317478

Added support to filter by "Booking Custom Fields" on "GET /event", see details.

See Details

More info on the farmerswife REST API:
https://support.farmerswife.com/a/solutions/articles/17000089578-the-farmerswife-server-s-rest-api-for-your-own-3rd-party-integrations

 
#317626

Added the possibility to filter by "Project Custom Fields" via the fw REST API, see details.

See Details

See this documentation for latest changes:
https://support.farmerswife.com/solution/articles/17000089578-the-farmerswife-server-s-rest-api-for-your-own-3rd-party-integrations

 
#317626
#317478

Implemented enhancements on endpoints "GET /event", "GET /project" and "PUT /project/projectID", see details!

See Details

- Added support to create Projects and update them by specifying a "projectNumber" (alpha-numberic).
- Added "Pagination" on "/event" and "/project" endpoints.
- Added 2 new parameters on "GET /event": "dayFrom" and "dayTo".
- Removed the requirement to specify "objectID" and "objectType" to get "objects events".
- Fixed a wrong implementation on "PUT /project/id" before this wrongly required to send "projectID" as a GET parameter.
- The "Swagger" documentation has been updated - get this from the below mentioned Knowledge base article.

More info on the farmerswife REST API:
https://support.farmerswife.com/a/solutions/articles/17000089578-the-farmerswife-server-s-rest-api-for-your-own-3rd-party-integrations

 
#317626
#317478

Implemented support for "GET last updates on events since last checked" via the fw REST API, see details.

See Details

See this documentation for latest changes:
https://support.farmerswife.com/solution/articles/17000089578-the-farmerswife-server-s-rest-api-for-your-own-3rd-party-integrations

 

Rate Cards

#305974

Fixed "Highlight Rates From Rate Card" option wrongly not highlighting the Sell Rate on booked Object if the Object Class was not primary, see details.

See Details

Highlight Rates From Rate Card was only working on the primary Object Class.
Now it also checks other Object Classes that the Object may have.

 

Rates

Fixed a bug wrongly causing the "To Invoice" in the Booking to be locked to "0" if by mistake the Return Date had been set to be the same as the Dispatch Date.

 

Fixed bug that was resetting rates and invoice fixed amount when replacing Objects with Accessories or Groups

See Details

When replacing Kits made out of Objects with Accessories or Groups, if in the initial booking the "Invoice Fixed Amount" and the rates had been manually modified, the quantity of days and the rates were reset.
Now, farmerswife can keep the rate by verifying the Object Class of replacing Objects, if it matches then the rate is kept.

 

Reports

Added new Element "Cancel Note" to Financial Reports and Project Reports

See Details

Now you can print out the note you add when cancelling a Project by using the element "Cancel Note" from:
- Project/MO/Unref. Invoices grouping in Financial Reports
- Rows section in Financial Reports
- Project section of the Project Report

 

Fixed a bug on "List Price" element wrongly showing the value from the modified rate, if the initial rate from Object Manager was 0, see details.

See Details

In Project Report > Element Row:
"List Price" element would show the original "Sell Rate", only when the rate from the Object Manager was 0.

In Financial Reports:
"List Price" and "List Price Rate" elements would show the same value as the "Sell" and the "Sell Rate", when the rate from the Object Manager was 0.

Now this is fixed on both Print Designers.
List Price and List Price Rate are the original price/rate from the Object Manager.
Sell and Sell Rate are the price/rate from a specific Project.

 

Fixed a fw Client crash when trying to print a Project Report of a Booking that had "0" days set on a linked Dispatch Check Out.

 

Fixed some bugs on Shared Monthly/Date Based Reports in combination with Project Web View Limits

See Details

Even when the "Allow Web Viewing" was disabled on a Project Web View Limits, the configured filters were still affecting the reports on the Shared Monthly/Date Based Reports in Web Client,

Now:
If you disable "Allow Web Viewing" on Project > Web View Limits, none of the filter options will be displayed.
Only when enabling it, the filters will be displayed for further configuration.
If you configure some filters and then disable it, as you enable it again in the future, the last configured filters will be there.

 

SQL

Added new "projects_objects" table and applied some more needed changes, see details.

See Details

Go to:
fw Server > Setup > General > MySQL > Select Tables > projects > and select the new "projects_objects" table.

This new "projects_objects" table contains these fields:
project_id, added_id, added_user_id, added_user_textnote, created, object_id, name, icon, buy, sell, quantity, part_invoice, ref
Note: This table has "unidirectional" / read-only support.

Also changed on the "projects_materials", "projects_services", "projects_expenses" tables for the "quantity" field from INTEGER to FLOAT. This fixes the issue, that a value of "2.5" entered in farmerswife was wrongly before "0" in SQL, and is now correctly showing "2.5".

 

Added support for Objects set to "Allow Multiple Check Outs (Virtual Object)" to have their "Stock" info on the MySQL tables, see details.

See Details

In farmerswife Server > Setup > General > Use MySQL > Select Tables > ... you will now find the new "stock" column on these tables:
- "objects_machines"
- "objects_others"
- "objects_rooms"
... and:
- "objects_groups"

To set an Object of internal type "machine", "other", "room" or "group" to be a "Virtual Object", the setting "Allow Multiple Check Outs (Virtual Object)" on the "Modify" window of the Object needs to be enabled.

To set the "Stock" on "Allow Multiple Check Outs (Virtual Object)" go to fw Client > Object Manager > on the "Modify Object" window > New Check In From Selected > New Check In window > use "Copy" ... and in "Number Of Copies" window set the stock minus 1, which is the one being copied.

NOTE: The maximum amount of stock per "Check In" is limited to 999. Create more Dispatch "Check Ins" to add more stock.

Now, when adding stock per "Virtual Object" via a Check In or by "using" "Virtual Objects" by checking them out, the above mentioned tables will be updated in real time.

NOTE: When checking out multiple "Groups", this will then also reduce the amount of Stock on the "Involved" Objects.
We recommend to use "Add Object (Name)" or "Add Object (Inventory Number)" on the Check Out window to add the amount of Groups.
When using "Copy" on a "Groups" on a Check Out, then you also need to ensure that also the "Involved" Objects are selected to be copied.

 
#319175

Fixed a bug wrongly preventing the "Ratecard Name" info on the "projects" table from being populated.

 

Saved Object Reports

#321182

Fixed a crash bug when trying to select an Object for a "Saved Object Report".

 

Schedule Changes Email

Implemented for the “Schedule Changes Email Sendout” for “New Requests” that the Header info is in “bold” and “blue,” see details!

See Details

For this functionality to work, the following settings must be set accordingly:

- In fw Client > main module bar > Object Manager, go to the "Web Permission Profile" of a user and enable "Schedule Changes Emails" and also set: "User Must Accept Or Decline New Bookings".

- In fw Client > Toolbox > Settings > Server Setup > Web Share Settings > External Calendars / Schedules Changes Email Sendout/ XML Exports: activate these settings:
- "Send Schedule Changes Email Even When Only the Event Header Was Changed"
- "Send Schedule Changes Email Using HTML And More Info About Changes"
- "Include Booking Object Note In Header"

Then the "Header" information will be displayed in blue, bold and underlined when receiving the Schedule Changes Email.

 

Changed the "text-color-scheme" of "event actions" for the "Schedule Changes Email Sendout", see details.

See Details

"Deleted Event:" or "Deleted Request:" - black and bold text.

"New Event:" or "New Request:" - will now show any changes colored in blue and bold text.

"More Info About Changes:" - also here changes are now colored in blue and bold text.

 

Added red color for deleted Events

See Details

tbc

 

Scheduled Invoices

#319979

Added for the Project Scheduled Invoices to show the applied Tax while creating and editing, and changed the Tax calculation to match with the Project, see details.

See Details

- Now farmerswife will display the Tax applied to a Scheduled Invoice when creating or editing. This is required because there are some scenarios were the Tax of the Scheduled Invoice would need be modified.
- And the way of calculating the Taxes on Scheduled Invoice was changed to match exactly to the Tax used by the Project.

 

Security

Allow only TLS protocols >= 1.2

 

Send Backup

Fixed multiple issues for the "Send Backup Now" to finally work on Linux again.

 

Server

Implemented low-level performance improvements when working on and with "big" Bookings in combination with Dispatches, see details.

See Details

A "big" Booking in farmerswife means that it contains many Objects (50+) and over a long duration (10+ days).
And for farmerswife systems working in this style, these low-level performance improvements will make a substantial difference!

Also note that a 50% to 60% files-size-decrease on the main database (current45.efdb) can take place during the upgrade; this itself is a performance improvement.

Some examples:
Opening a "big" Booking from the Long From > Projects tree > containing 500 Objects over 100 days, before took 30 seconds to open.
Now, the same operation takes 2-3 seconds!

1000% faster
Depending on multiple factors ... adding 3 more Objects to an existing Dispatch > Check Out linked to a Booking over 100 days containing 50 Objects, took before this change 56 min. and more.

Now, the same operation will take 7 to 9 seconds!

 

Implemented support on Windows for Java "OpenJDK" (on macOS this already works), see details.

See Details

Server: Implemented support on Windows for Java "OpenJDK" (on macOS this already works), see details.

Download "OpenJDK" e.g. here: https://adoptopenjdk.net/
Use the "Hotspot" version; e.g. the installers are called:
- Windows: OpenJDK8U-jdk_x64_windows_hotspot_8u222b10.msi
- Mac: OpenJDK8U-jdk_x64_mac_hotspot_8u222b10.pkg
- Linux: OpenJDK8U-jdk_x64_linux_hotspot_8u222b10.tar.gz

Then first UNINSTALL _ALL_ Java versions (especially the old deprecated v1.6 and v1.7) on the fw Server host machine; you might need to search for uninstall instructions.

Install OpenJDK.

After launching the fw Server application again, check e.g. that the Web Client is properly running.

INFO:
JRE - "Java Runtime Environment"
JDK - "Java Development Kit"

 

Server Settings

Now it is possible to see the users' Full Name where Object Permissions are managed, see details.

See Details

The setting in fw Client > Toolbox > Settings > Display called "Inventory / Full Name" is used when enabled or not, if the user's Name will be displayed by using the "Username" or "Full Name, i.e. "First Name" and "Last Name" in various places within the farmerswife.

This did not apply to the places where "Object Permissions" are managed, and now it does.

 

Server Setup

Added contact upgrade on Force Check Database

 

Time Report

#314680

Fixed a bug for Breaks added to Timereports wrongly miscalculating Overtime values (Quantity and Sell Total) on Reports and Project window, see details.

See Details

The Breaks were wrongly calculated over the total reported time.
Now breaks are calculated differently for "Normal Working Time" and "Overtime".

 

Timelines

You can now in the Modify User window setup a Start And Stop Date to visually indicate in the timelines if User is available, see details

See Details

This option is useful to indicate the date when a person starts working for the company, or to indicate the date when a person ends his contract.
On the dates outside this range, there will be a "Maintenance" icon to visually indicate that the User is not available, on both Long Form and Hourline.
This is only a visual indication - you can still add a Booking and there won't be a warning.

 

User & Object Report

Fixed Object & User report Element "Booking Client" in Events section to only show company name, before it wrongly also showed contact name.

 

User Settings

Force change password on next login

See Details

On Server > Setup > Users > Force Password Change On Next Login
Can be found at the bottom right, under Password Policies section.
A User selection windows will pop up and user selected will have to change their password on their next login

 

Renamed setting: Allow Modify Booking Days After It Is Dispatched to Allow Modifying Booking After It Is Dispatched

 
#321294

As Users with Force Settings From File (WUS file) log in, their View Port in Long Form now remembers the date range they had set when they last logged out, see details

See Details

This bug was forcing the View Port for these Users to be on the dates that had been set at the moment of exporting the WUS file, every time they logged in.

 

Users

Password Policies: added support to prevent password reuse

See Details

When Password Policies option is enabled, and a User is prompted to change his password, he will not be able to use an already used one.

If User tries setting an already used Password, a pop up message will warn that it cannot be used again.

 

Web & Mobile Client

The Framework Day Note/ Booking Object Note is added to the Day Plan next to the Object, in the Web Client, iOS and Mobile Web Client

See Details

There's a new setting in Toolbox > Server Setup > Web Share Settings > "Show Booking Object Note On Day Plan In The Web Client, iOS and Mobile Web Client".
When enabled, the Note added via Framework Day Note or Booking Object Note, will be displayed next to the Object on the Day Plan in the Web Client, Mobile Web Client and iOS.

 

Web Client

"Shared Monthly Based Reports" in the Web can now be generated by selecting a specific date range.

See Details

The following changes have been done on the existing functionality:
Changed the text in fw Client > Edit User > Web Profile > "Shared Monthly Based Reports" to "Shared Monthly/Date Based Reports"

When running a Shared Monthly Based Reports in Web Client:

Now there are 2 tabs at the bottom of the "Select report period" one for "Monthly" report and another for "Date Range" report.
The Generate Report button has been moved to the top right of the window in order to follow the same structure and styles as other windows. It is now called "Create".

The generated PDF file will have its name formatted as:
- for "Date Range": "Object_Events_Report_YYYY-MM-DD_YYYY-MM-DD" (if an Object Report) or "User_Report_YYYY-MM-DD_YYYY-MM-DD" (if a User Report)
- for "Monthly Report": "Object_Events_Report_YYYY_mmm" (if an Object Report) or "User_Report_YYYY_mmm" (if a User Report)

 

Added Binder Name and Booking Name to Time Reports listed on the left-side panel and to Time Report window. See details.

See Details

When opening the Time Report from within the Booking on the timeline, the header now displays the Binder Name and the Booking Name (if any) next to the Project Name.
On the Time Reports listed on the left-side panel, the Binder Name and Booking Name (if any) now show next to the Project Name.
This addition is useful for Users to see what exact job the Time Report is for.

 

Implemented for the Web Client when creating an Ad-Hoc Time report, this will open the Booking window in "edit" mode after clicking SAVE, see details.

See Details

To activate this new feature, go to fw Client > Toolbox > Settings > Server Settup > Web Share Settings > "Open Booking Window In Edit Mode When Creating Ad-hoc Time Report".

Now, when creating an Ad-Hoc Time Report via the Web Client, when clicking "Save" the calendar will display the day when the Ad Hoc Timereport was created and will open the Booking in "edit" mode.

If this Setting is disabled, it will behave as before.

 

Web View Limits configured per Project now also applies to the Shared Monthly/Date Based Report and the Shared Day Plan Report

See Details

When configuring some options on the Web View Limits on Projects, the Shared Monthly/Date Based Report and the Shared Day Plan Report printed by a web user will hide events not included in that configuration.

 

Fixed a bug causing a fw Server-side error when adding an Object Class as "Extra" to Time Report via the Web Client, see details.

See Details

Adding Object Classes as Extra to a Time Report is not supported on the Desktop fw Client.

It was a "glitch" that a Web User could see Object Classes when adding Extras to Time Report.
And as the Web User was selecting a Class, this was causing a fw Server-side error and resulted in freezing the Web Client.

Now Classes are no longer available via "Extras" when time-reporting via the Web Client.

 
#319670

Fixed a bug when using this behaviour for the Web Client “Open Booking Window In Edit Mode When Creating Ad-hoc Time Report", see details.

See Details

For this bug to happen required in fw Client > Toolbox > Settings > Server Setup > the Setting “Open Booking Window In Edit Mode When Creating Ad-hoc Time Report” to be enabled.

When in Web Client > "Not Done Time Reports" list on the left pane of the Web Client was used, time-report changes done here were wrongly lost due to the Booking windows opening in Edit mode.

This is now fixed, so that the Booking will only open in Edit mode after creating an Ad-hoc Time Report, but not when saving changes to a Time Report from an existing Booking. So this is now fixed and this setting only applies when creating an Ad-hoc Time Report, as initially intended.

 

Web Profile Manager

Added fw API Server support and two new Web Profile settings to allow hiding Bookings on Planning or Preliminary Sub Status on Web Client, Mobile Web Client, iOS app and WebCal

See Details

These two new settings have been added under Events > Show Event:
"Show Events With Planning Booking Sub Status"
"Show Events With Preliminary Booking Sub Status"
Both settings are by default enabled.
When disabled on a User's Web Profile, Bookings with Sub Status Planning or Preliminary will be hidden when connecting via Web Client, Mobile Web Client, iOS app, and WebCal.

 

Fixed a bug related to the Web Permission "View And Book Classes As Objects" was not displaying the complete list in certain scenarios, see details.

See Details

For this bug to happen required in the Web Permission "View And Book Classes As Objects" to be enabled, "Specific Object Level Control" to be configured and “Select And Share Saved Hourline Views” to be used.

This would cause that some Classes were wrongly not displayed for the Web User when booking via the Web Client.
If restrictions on Objets were applied via the "Specific Object Level Control" then the related Object Class was not being displayed.
Also the “Select And Share Saved Hourline Views” was participating on deciding which Classes were to be displayed.

Now this Web User permission "View And Book Classes As Objects" is independent from any other setting.

 

Web Visibility

Added "Binder" support to the "Web Visibility" (former Web View Limits)

See Details

The Web View Limits were renamed to Web Visibility.
This setting now needs to be enabled now in Toolbox > Server Setup > Use Web Visibility Settings For Projects.
The Web Visibility window has been resized to fit long Binder names and the Filter By Objects is now called "Filter By Users/Resources".
The former Web User column got removed (obsolete setting).

This new Web Visibility window now consists of the option to "Allow Project Web Visibility (by default enabled), The In and Out Date, the Filter By Users/Resources and Filter by Binders.

When the Filter By Users/Resources checkbox is ticked, the list show the involved Users/Resources in a column below. Each of them can be ticked to enable the Web Visibility for this Object.

The Binders are shown in the same order as they show in the Projects tree.

The Filter By Binders checkbox can be ticked and a list of the existing Binder will appear below, showing the involved Users/Resources alphabetically.
If the checkbox of the Binder is ticked, all involved Users/Resources get automatically checked, you can then untick the ones that you don't want to give Web Visibility.
Multi-selection of Binders is possible. Next to the Binder name you will see the Start Date of the Binder

If a User is ticked in the Filter By Users/Resources column it will automatically checkmark him in the Filter By Binder column and he can't be unticked, as the Filter By User/Resources overrules the Filter By Binder selection.

 

Added option for View Mode in the Objects Tree and Hotkey to show if a Booking is allowed to be seen in the web due to its Project Web Visibility Settings (former Web View Limits)

See Details

The Project Web Visibility Settings (former Web View Limits) will show on an Object Booking level if this Booking can be seen in the web or not.
Those can be activated now in Toolbox > Settings tab > Use Web Visibility Settings For Projects. Then the option: Web Visibility is available in the eye menu of the Project.
If a User and any of his Bookings (depending of the time range that was set in the Project Web Visibility Settings) are allowed to show in the web, this can now be displayed in the Objects Tree by clicking on the Objects Tree icon > View Mode > "Web Visibility".
or you can add a Hotkey for this via the Hotkeys Editor selecting the option "Web Visibility".

The color that those Bookings will change into can be set in Toolbox > Settings tab > Display > "Web Visibility".

To configure the Hotkey go to Toolbox > Settings tab > Miscellaneous > Hotkey Editor.

 

The functionality "Web View Limits" has been renamed to Web Visibility and it needs to be activated in Toolbox settings, see details.

See Details

Web Visibility is activated in the Toolbox Settings > Server Setup > Use Web Visibility Settings For Projects. Then the Web Visibility option will appear in the eye menu of the Project.

 

Added Web Visibility Status to User Report, Object Report and Financial Report, see details

See Details

The Web Visibility (former Web View Limits) can be set inside of the Project for Users and Resources to determine whether if or which of their Bookings are visible in the Web Client, Mobile Web Client and iOS.

This Web Visibility Status can now be shown in the
- User Report > Events section > Web Visibility
- Object Report > Events section > Web Visibility
- Financial Report > Rows Section > Web Visibility

 

Added a tristate option to the checkbox "Filter By Binders", see details.

See Details

If inside of the Web Visibility window the Filter By Binders checkbox is ticked, a list of all involved Binders shows in the window below. Each Binder has a checkbox in front of its name and below the list of Users/Resources that are inside of that Binder. If one of that User is ticked, a tristate icon "-" will now show in the checkbox in front of the Binder to indicate that at least one item is ticked. Before it would show a check mark in the checkbox, wrongly indicating that all Users/Resources of this Binder are enabled.

 
#321245

Adjusted Toolbox > Projects > Web Visibility column to show in blank if "Filter By User" or "Filter By Binder" is ticked but no User is selected, see details.

See Details

If Web Visibility(WV) is configured and a date range is set and "Filter By User" is ticked and a user selected, the Web Visibility column would show the Date Range and an "F" indicating that something is filtered in a certain time range.
If you then deleted the Booking of the User that was ticked in the "Filter By User" column, the check-mark was wrongly still set in front of the Filter. This would prevent any communication, so even if the WV is set, a date is set, nothing would be communicated because the "Filter By User" was ticked.
Now the Toolbox column will correctly show in blank, as nothing is visible.

The same behavior applies if a User was ticked in the "Filter By User" column and then his/her Booking(s) get(s) removed.

 

Fixed a bug where a Shared Monthly/Date Based Report printed from the Web Client would wrongly show all Bookings even if they were filtered by the Web Visibility to not show.

 

WebCal

Added a new Toolbox Setting for farmerswife to "Format And Convert Time To UTC/Zulu Timezone", see details.

See Details

By default this setting is enabled and should be left checked in order for webcal events to show as the true time across all calendars.

If this setting is unchecked then the time will exist unassociated with the local timezone of the farmerswife server.

For instance, if an event was created at 2PM Central European Time, the actual time of the event would be 8AM Eastern Time. However when added to a calendar with eastern time as the primary while "Format And Convert Time To UTC/Zulu Timezone" is unchecked the event would import at 2pm Eastern European time. As a note, the date is unaffected so even if the time shift would normally have moved the day of the vent forward or back the day it was booked on for the farmerswife server time would remain the same as well.

The use case in mind for this feature was 2 working groups 12 hours apart with no over lapping events. This allowed the scheduler to schedule events in their time and the staff 12 hours apart would do them at the same time in their native timezone.

 

Implemented support to display a multiple-day Bookings and "All Day" Events in one line on WebCal/iCal Event subscriptions IF "Use Actual Time Range" is enabled, see details.

See Details

Multiple-day Bookings displayed via the WebCal/iCal Event Subscriptions will now show these as a single line over all days on the calendar for that booking. This only applies if the "Use Actual Time Range" on the Booking > "Time In/Out" setting is active.

IMPORTANT: Take care "Actual Time Range" means, that these Bookings are booked through the whole time-period, so also during the night!

For this to work, either go to each multiple-day Booking where this is needed, right mouse click > Booking > Time In / Out > "Choose Start And Stop Time > click on the "Use Actual Time Range" check-box.

Or when creating Bookings where this should apply, go to fw Client > Toolbox > Settings > Booking Defaults > "Use Actual Time Range" and set the check-box for all following Bookings to be created.

 

Previous Releases