Should you still encounter issues on Windows after the Full Installer upgrade, then please follow these instructions:
-Ensure the fw Client desktop app is not running
-Go to its root installation folder remove the "lib" folder.
-Then run the same Installer again using the same Installation path.

Now, any 3rd party library conflicts are fixed and printing should work as expected.

On Activities you can set an Overtime Calculation that is % based on the Activity's Rate. Until now this was intended to be used with Day Rates and not allowing to set a % less than 100% which didn't make it useful when using on Hour Rate Activities.

This is now possible and you can e.g. create an Hour Rate Activity which has an Overtime set after 08:00 hours as 20% of the Hourly Rate. So on a 16 Hour Booking it calculates 16 x Hour Rate of e.g. 16 x 50.00 + 8 x 10.00 (8h Overtime) = 800,00 + 80,00 = 880,00 €.

The Project Name and Booking Name columns were previously just called: "Name". Now they are called "Project" and "Booking" to better differentiate between the both when looking at the search results in the Advanced Project Search (main module bar > Projects) and searching in Projects & Bookings.

Until now, when displaying various columns in the result table of the Advanced Project Search (main module bar > Projects), the columns would all have the same width and you had to expand them manually.
With each new search, this would also default back to the small column width. Now the column width will always adjust, to show the cell content.

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

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

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

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

New and changed:

• Renamed "Azure AD" to "Entra ID" in all places on fw Server app and fw Client app side.
• Entra ID: Added support for version 2 of the oAuth 2.0 token endpoint.
• Added new selector "Use OpenID Connect" in MS Entra ID settings. When setting this selector to "Yes" the MS Entra ID integration will use OpenID Connect settings for getting the server token (oAuth2.0 client credentials flow) for syncing users, but also for users authentication (oAuth 2.0 auth code flow).
• Implemented improvements to the fw Server > Setup > "User" tab to make the MS Active Directory, OpenID Connect, Apple Connect and MS Entra ID selectors being displayed only when enabled. And in case of MS Entra ID over OpenID Connect, only MS Entra ID is displayed.
• Added new fw Server app setting in Setup > Users > "Hide User/Password Login Form" to display only the "OpenID Connect Provider" login button.

• Added new buttons for OpenID Connect based on the OpenID Connect Provider selected in fw Server Setup > Users > Entra ID area.
• Multiple UI improvements and fixes to enhance the login experience.

• Multiple OpenID Connect fixes.
• OpenID Connect Web Client and MWC re-direction now respecting the server.cfg variable: HTTPHOMEADDWEBCLIENTPORT.
• Fixed a wrong OpenID Connect code forcing the callback endpoint to have always a port.

When applying a Framework Booking Template where already Users or Objects are booked, a Booking history line for each User/Object is now added to the Booking.

Previously, if a Booking Template contained an Object that had been made inactive, you were still able to use the Booking Template and book the inactive Object.

This change prevents you from using a Booking Template that contains an Inactive Object, and prompts the user with:

"[Object] Is No Longer Active And So Cannot Be Booked As Part Of A New Booking"

With [Object] being replaced by the name of the Object in question.

In the scenario where multiple inactive objects are a part of the booking template, using the Booking template will prompt the user with:

"Multiple Objects Are No Longer Active And So Cannot Be Booked As Part Of A New Booking"

Added a new setting: fw Client app > Toolbox > Settings > Booking Defaults > "Autofill Booking Name From First Object's Activity Or Class" Yes / No (default).

When this new Setting is enabled, the Booking Name will be auto-filled with the selected Activity (if applicable) or selected Object Class if No Activity.

NB: This only applies for the FIRST booked Object (Adding or replacing Objects within the Booking will not update the Booking Name)

If there is a Booking Type with matching Name then any Custom Fields and/or Pre-defined Extras will also be applied.

You can now display 30+ Objects and their Involved Booking Times in the Booking Window.

A new limitation will hide Involved Booking Times of more than 30 Objects spanning more than 7 days in a multi-day booking.

This is a new feature, adding a new sub-status "Cancelled" for use with Global Names & Customs, to compliment the already existing "Planning", "Preliminary", & "Confirmed".

There is also a new setting in Toolbox > Display called: "Show Cancelled Bookings" to determine if they should be shown.

This is especially useful if a Project goes over 2 or more years and you have Bookings in September 2021 and September 2022 or if someone moves the Bookings by mistake to the wrong year.

Before the Edit Booking window's Title only showed "Weekday dd month-name".
Now the Edit Booking window's Title shows: "Weekday dd month-name yyyy", e.g. "Thursday, 21. September 2023".

The Edit Booking window's History pane will also contain the year-info, but only for single-day Bookings.
Multiple-day Bookings can simply contain too much not usable date info; that's why the year info is not logged in the History pane for them.

Previously the width of the Global Booking Status selector would not be wide enough to display longer Status names. This fix allows that to happen.

The Booking Edit window will now expand automatically on larger screens. On small screens you might see a small increase of size.

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

This issue prevented the fw Client app from using the fw Server-side color configuration for Option Bookings, when multiple Pencil Bookings were used in the fw Client app. This is fixed.

When a Booking was re-submitted for Approval, the Mandatory Note pop-up would not get shown again, if the Booking was Declined by the user.
Now this is fixed and the Mandatory Note pop-up also gets triggered in this scenario.

This new feature applies to both the Budget table and the Actuals table.

In the view menus on top of the Budget and Actuals tables, you could already edit the viewed columns and save the result as a "View". But those Views were personal and not available to other Users.

Now when you save a View, the dialog contains a "Shared" checkbox. If checked, the Shared View will show up for all Users inside the Budget window. They can load the view for themselves, but also edit or remove it.

• Budgeting: Added "Date" column to the Actuals table.
• Budgeting: Added Cirkus Task Number and Name to the Description column.

In the Budget Settings dialog (in Project > Budget > Setting Menu), there is now a new field called "Allowed Budget Types". It can be used to select which Budget Types users can select from.

• Budget
• Current Quote
• Quote

If a Budget has a Binder selected, and an Actual has the same Binder set, it will pre-select the Budget in the Actuals table.
However, if you were using Sub-Binders this was broken since farmerswife 7.0 Beta 14.
It still worked for Parent Binders.
The bug is now fixed.

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

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

Before this change, the calendars would only extend until 2029. This change adds additional years to extend the calendars until 2035.

Note: This feature is only available after using "Migrate To Projects Sync v3".

In Toolbox > Projects and Advanced Project Search, you can now select one or more Projects, right-click and select Cirkus > Force Sync.

This will bring up a dialog where you can optionally select a different Sync Mode (direction) than the default one, in case you want to force sync all change e.g. from farmerswife to Cirkus, or vice versa.

After pressing OK in that dialog, it will queue the Projects for syncing on the server side and show a progress bar that first waits until the sync starts and then updates as the sync progresses. Note however that the syncer doesn't sync one Project at a time, but does them in batches, so the progress bar won't update for every project that is synced. Instead it will update as certain stages of the sync process are completed.

By default, the sync no longer creates Cirkus Resource Categories from an Object's Primary Object Class, since Object Classes don't really map to Resource Categories when you create bookings, which can cause some confusion.

However, some still prefer the older behavior as a way to organize the created Resources. So now there's a setting, located in Object Manager > right-click meu > Cirkus > Settings, called "Create Resource Categories From Object Classes".

Recently, Cirkus has been updated to allow Resources to have Roles, just like Objects in farmerswife can have Object Classes.
So now when you sync an Object to Cirkus, it will populate the Role information just like it already did with Users/Members.

Note: This feature is only available after using "Migrate To Projects Sync v3".

In farmerswife, you can either set a "Static Time Frame" on a Binder, or add Bookings which then dynamically affect the implicit start/end dates of the Binder.
Now the Cirkus Sync can sync those dates to the Start/End date fields on the Cirkus Subproject.
Note that this feature is disabled by default, for backward compatibility.
You can opt into the feature by removing "Start Date" and "End Date" from "Project Fields To Never Sync To Cirkus".

Now that Cirkus Bookings and Tasks are able to have a "Schedule Status" (new in Cirkus 1.87), farmerswife (fw) can sync its Booking Status with it!

Settings:
In the pop-up menu next to fw Client app > Toolbox > Settings > Cirkus (v2) > "Sync Bookings With Status", there's now a new option called "Copy Statuses To Cirkus..."!

It will let you select one or more Booking Statuses from farmerswife, that will be copied to Cirkus. The Statuses can then be found in Cirkus Workspace > Info > "Schedule Settings" and will then get used for future Bookings and Tasks.

There's also a new setting in fw Client app > Toolbox > Settings > Cirkus (v2) > called "Map 'None' Schedule Status To".
It lets you select which fw Booking Status corresponds to "None" (the lack of a status) in Cirkus.
The mapping works in both directions - when syncing Bookings and Tasks both to and from Cirkus.

In a recent release of Cirkus (June 2024), the Cirkus got support for Booking an Object as a specific Role, e.g. "Anne as Editor". That corresponds to the way you book Objects as Object Classes in farmerswife. So now it will start to sync that info in both directions.

Cirkus is has support for displaying the booked Activity, as read-only information. That info will only sync from farmerswife to Cirkus.

This feature is by default off, and must be opted into by toggling in fw Client app > Toolbox > Settings > Cirkus > Sync Object Custom Fields.

The reason for that is because all Custom Fields that are synced to Cirkus will be visible to all Cirkus Members who have Administrator or Member permissions.

Once it's enabled, any Objects you select in the Object Manager and use "Add To Cirkus" or "Update In Cirkus" will have their Object Custom Fields copied to Cirkus.

Note: This feature is only available after using "Migrate To Projects Sync v3".

In farmerswife, you can either set a "Static Time Frame" on a Project, or add Bookings/Binders/Markers which then dynamically affect the implicit start/end dates of the Project.

Now the Cirkus Sync can sync those dates to the Start/End date fields on the Cirkus Project.

Note that this feature is disabled by default, for backward compatibility.

You can opt into the feature by removing "Start Date" and "End Date" from "Project Fields To Never Sync To Cirkus".

In Cirkus, it's possile for someone who is not involved (booked beforehand) in a Booking or Task to report time on it, ad-hoc.
So a Booking/Task can contain a mix of involved who were previously booked, and other people who ended up working on the Booking/Task in the end.
But while time reports would sync to farmerswife for the pre-booked involved, there was previously no way to sync those ad-hoc time reports.
Now that support is added. The ad-hoc ones will be added as involved in fw, but have a "Booked" quantity of zero, and only have a "Used" quantity.
You can see that behavior in the Project window (Time Report Mode: Booked Only) and Financial Reports.
Additionally, the ad-hoc involved will have a "Booked" duration of zero in the Time Report window.

There's a new setting in Toolbox > Settings > Cirkus (v2), called "Sync Markers To Milestones". If activated, any updates to a Project's Markers will make it sync all the Project's Markers to Cirkus, as Milestones inside the Cirkus Project. Just like with the Binders/Subprojects sync, it only syncs one-way, from fw to Cirkus. Any changes in Cirkus will be ignored or overwritten.

To create a Project Marker in farmerswife, load the Project into Long Form > Project Tree > click the Project icon > New Marker. You can set a name/date/time/colour/note, which will all be synced to Cirkus. As there's not a "Checkpoint" in Cirkus that will not be synced.

Cirkus will gain the ability to set Workspace Members as Inactive, starting in version 1.91.

Whenever you toggle a User as Active/Inactive in farmerswife, it will now update the Workspace Membership in Cirkus accordingly.

When you use a Task Template mapping to make Cirkus Tasks appear as Project Objects, there's a setting called "Actualize: Immediately/When Done".

If it's set to "When Done" and you create a Cirkus Task, it still creates a Project Object in farmerswife, with 0 quantity.

The problem was that you could still Part Invoice that Object. And once the Task was set as done and got a correct quantity, it would no longer be available for invoicing.

From now on, when using "Actualize: When Done", you won't be able to Part Invoice Tasks that are not done.

After the upgrade from fw v6.8 to v7.0, it was not able to sync existing synced Bookings, due to an error that said: "can't read "method": no such variable".
The same bug could cause errors when deleting synced Bookings.
This bug is now fixed.

If you booked a Role on e.g. a Booking in Cirkus and it synced over to farmerswife, the farmerswife Booking would contain a broken "TBD" Object that didn't have any Object Class set.
Bookings synced after this fix will have the correct Object Class set.

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

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

When you created a Personnel Booking in Cirkus for an Object that is not a User - e.g. a Resource - in farmerswife, it would still try to sync it to farmerswife.
The farmerswife server log would say "Creating 1 Personnel Bookings in fw".
Now those Personnel Bookings will be ignored by the sync.

When you restored a Booking from Toolbox > Deleted Bookings And Binders, it would not get synced to Cirkus unless you then also modified it in some way. This bug is now fixed.

After using "Forget Sync For This Project", it would previously reset the sync settings to the default values for new Projects.
So if those default values meant the Project should get synced to Cirkus, it would immediately sync the Project again, creating a new Cirkus Project.
That way, you could end up with a new duplicate every time you used "Forget Sync For This Project".
Now this is changed so it will no longer re-activate sync for the Project.

When you create a Booking containing a Role in Cirkus, the Cirkus Sync creates a Booking with a pure Object Class in farmerswife.
The problem was that the Object Class would be lacking its Class attribute, so it would show as " / TBD" instead of e.g. "Editor / TBD".
This bug is now fixed.

In fw Client app > main module bar "Object Manager", you can use "Add To Cirkus" on Users/Objects in order to create them in Cirkus.
But if the User/Object or its Object Class contained special characters, such as umlauts, and the operation was performed from a Windows fw Client application, the name would be wrong on the Cirkus side. So it would not consider the User/Object/Object Class when syncing.

If many Projects were synced between fw and Cirkus, the syncing of Bookings, Cirkus Time Reports and Tasks (as billables, using Task Template Mappings) would fail with the error: "Error Syncing Bookings: No Change Events Found In: ..." or "Error Syncing Booking Time Reports: No Change Events Found In: ..."

For the Bookings sync this was introduced in 7.0 Release, but for the others it's an older bug.

This fix requires that you first migrate to the Projects sync v3.
The bug was, that if you created a new Project activated the sync for it and pressed "Save" instead of "OK", it would show an error in the Cirkus info pane.
And on the server side it would complain about errors such as "Invalid channel supplied (400)".
The cause was, that it was trying to show info about the Cirkus Project, even though it had not been synced yet.
Now this bug is fixed, by showing an information label saying "The Project Will Be Synced Once The Window Is Closed". Once the user closes the Edit Project window the Project will be synced in due time.

This bug only happened when the farmerswife Server app was on Windows and on network requests that took more than one second to perform. Any data coming from Cirkus would then be decoded incorrectly, losing international (e.g. Cyrillic) characters.

So if you e.g. created a Project or Booking with international characters in Cirkus, when it synced to farmerswife those characters would become wrong.

The bug is now fixed, so international characters should work correctly.

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

Cirkus syncing had the potential to keep refreshing the number of Done/Total Tasks, for the main Edit Project window. When that was slow, it could affect the performance of the Budget window, even though the number of Done/Total Tasks was not even displayed there.

This fix is designed to ease that process, and improve performance in the Budget window.

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

On rare occasions, special characters in note fields of Bookings have been known to cause problems when syncing to Cirkus. When this happens, it could stop updating not only that Booking, but all other pending updates as well, until the issue was resolved.

Now the error handling in these scenarios is improved, so it detects the problem and performs each update separately when needed.

The following settings have been moved from farmerswife (fw,FW) Server app > Setup > General > Cirkus > to fw Client app > Toolbox > Settings > Cirkus (v2):

• Create Projects In Cirkus When Created In FW
• Create Projects In FW When Created In Cirkus
• Remove Projects In Cirkus When Deleted In FW
• Delete Projects In FW When Removed In Cirkus
• Sync Time Reports
• Sync Time
• Sync Mode

• In fw Client app > Toolbox > Settings, it said "Cirkus (v2)" although the "v1" integration is no longer supported or available. The "v2" naming has now been removed.
• In fw Server Setup > General > Cirkus, it offered to "Migrate To Projects Sync v3". This has now been renamed to "Migrate From Legacy Project Sync".

Let's say a Booking existed in both farmerswife and Cirkus.
Then you swapped the Involved Object in farmerswife, to an Object that didn't exist in Cirkus.
Then the Booking would not get synced at all, because it didn't contain any syncable Involved Object.
So the previous Involved was still booked in Cirkus.

Now this is fixed. It will proceed with syncing that Booking and delete the corresponding Cirkus Booking, because it is empty.

If the API Key or Workspace are disabled in Cirkus, farmerswife would previously just indefinitely keep trying and failing to sync. Now it will detect this state and disable the sync. If the issue is resolved, the sync can be manually enabled again in fw Server > Setup > General tab > Cirkus > Enabled.

You could already add farmerswife Objects to Cirkus by right-clicking in Object Manager and selecting "Add To Cirkus". However, if you later deleted the Object in farmerswife, the Cirkus Resource would still remain.

Now when you delete a farmerswife Object it will automatically try to delete it in Cirkus. If it fails, e.g. due to internet connectivity, there's an error message and the Object won't be deleted in either system.

Objects in farmerswife are mapped to Resouces in Cirkus, by comparing their names.
You could already add farmerswife Objects to Cirkus by right-clicking in Object Manager and selecting "Add To Cirkus". However, if you later renamed the Object in farmerswife, the link to the Cirkus Resource would be lost unless you manually renamed it the same way in Cirkus.

Now when you rename a farmerswife Object it will automatically try to rename it in Cirkus. If it fails, e.g. due to internet connectivity, there's an error message and the Object won't be renamed in either system.

In Object Manager, you can right-click on an Object and use Cirkus > Add To Cirkus.

Previously, this would also look at the Object's Primary Object Class and add the created Cirkus Resource into a Resource Category with the same name as the Primary Object Class in fw. The cause for that behavior was simply to get the Resources categorized a bit nicer.

However, this was confusing as it seemed to suggest that Object Classes map to Resource Categories in general. But they don't. In fact there's a setting where you control if Object Classes map to Resources or to Roles.

Because of this confusion, the automatic creation of Resource Categories now has a setting, located in Object Manager > right-click meu > Cirkus > Settings, called "Create Resource Categories From Object Classes".

This applies to farmerswife Bookings that are synced to Bookings or Tasks in Cirkus.
When you moved Bookings or Tasks in Cirkus across Projects, they would previously stay in their original Project in farmerswife.
But from now on, it will detect the move and update the farmerswife Bookings accordingly.

In Toolbox > Settings > Cirkus (v2), you can define "Task Template Mappings", which control how fw actuals are created from Cirkus Tasks.

In the window for those mappings, there's a Custom Field selector called "Quantity Field".

Previously it would list all possible Custom Fields from all Task Templates. Now it will filter the Custom Fields based on the selected Template, making it easier to find the wanted field.

This new setting "Causes conflict" check-box on the "Personnel Event Types" window (access via fw Client app > Long Form > Personnel try icon click > custom Type Setup > Edit Personnel Event Types... > "Personnel Event Types" window, allows you to set Custom Personnel Types to cause a conflict or not.

See also more info here:
https://support.farmerswife.com/en/support/solutions/articles/17000052226-customise-personnel-management-types

Previously if you created a Booking that would result in a Conflict, a Pre-Conflict Message could appear and at the end you would get the Conflict window showing the conflicting Booking(s).

With the new User Permission flag "User Cannot Book Conflicting Object" you can now control if a user should be completely blocked from booking a conflicted Object, or not.

The new Permission will result in a Conflict message and NOT allow the user to continue and book the conflicting Object.

The Permission can be found in the Modify User Window > Permissions > Advanced > "User Cannot Book Conflicting Object" Yes / No (default).

Web Permission Manager window > Web Profile > Events > "User Cannot Book Conflicting Object" Yes / No (default).

This applies to farmerswife Web Client, iOS and Mobile Web Client.

There's a Toolbox Setting in Desktop Client > Toolbox > Settings > Booking Defaults > Warn For Conflicts Before Creating An Modifying Bookings which will bring a Conflict warning on adding conflicting Objects to Bookings.

However when adding Objects from within the Bookings Window > Add Involved this trigger didn't work.

That is now fixed and you get the pre-conflict warning on trying to add an Object that has a conflict.

Reduced the time that the Show Conflict window shows when applying Booking Templates.

You can export the conflict window information by clicking on the export icon. Maintenance now will show the "What" column.

Previously the Server-side contact importer would import all contacts on the import file, generating duplicates of existing contacts.

With this addition any contacts being imported who's email address matches an existing contact in the database, will be highlighted to the user importing and skipped on the import.

When Block Client Fileds was eneabled on the server, it was not possible to change Contact Type when creating new Contacts.

Now this bug is fixed.

When new contacts are created, Contact Type can be selected.
However, when Block Client Fields is enabled, changing Contact Type is not possible once the contact is saved.

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

This new feature allows you to choose "Media Name" from the Finder, when using both Entry Widgets & Text Widgets, on setting up Custom Fields. When starting to type in the Entry or Text fields a list of Media Names (with Number) appears and on selecting the Media Name it will be added to the field.

When creating Projects with multiple sCustom Field type Selector, the system would crash upon saving them.
Now this bug is fixed and Projects can be created just fine again.

The Day History Log Report includes now additional information and shows following actions:

1) When a Contact is deleted (and by whom)
2) When a Project is deleted (and by whom)

This performance improvement will take effect on "histories.db3" files bigger than 100 MB and when a user has in fw Client > Toolbox > Settings > Object Tree and in the Personnel Tree > "Monthly Utilization Budget" enabled.

Added the "Location Change Date" to the Master Check In/Out columns inside of the Dispatch Edit window.

The "Location Change Date" is the date that a User did an action that would change the location state of an Object, like a Check In or a Check Out of an Object.

Previously you were not able to see who created the New Check in, or New Check Out in the dispatches. This has added the creator information to the window on the bottom left corner, much like on Booking windows.

If EMT is licensed and the Dispatch Workflow is enabled on a Booking, you can set Preparation, Delivery, Collection and Return Dates.

Those dates are shown in the Dispatch module as "On Day Activities". Now you can filter them by clicking on one of the four checkboxes, to search individually or in a combination.

A dropdown menu has been incorporated beside the "Add Object (Inv. Number):" field labeled "Box." You now have the option to choose from "None" (default), select a number between 1 and 10, or choose "Other" to input a different number.

First choose a Box Number and then start scanning. If the items are already inside of the Dispatch then you only need to verify them, by first selecting the desired box and then start scanning.

If for some reason you need to add the boxes after all items have been verified, highlight the line items, right mouse click > Set Box > Select a number and the Box Number will be applied afterwards.

This Box number has also been added to the Edit Dispatch window as a column next to the "Status" column.

The element "D:[Box]" has been added to the Element Row section which makes it possible to print out the Box number in the Dispatch Report. Sorting by Box Number is also possible through the Options button inside of the Dispatch report: "Sort By Box".

Two additional elements have been added to the Dispatch Report Header section:
"D:[Box Weights]" and "D: [Amount Of Boxes]".

The Box weights will sum up the weight of each individual item that is inside of the box if there is an Object Custom Field called: "Weight".

If you use Divisions and track Dispatches between Divisions (Toolbox > Settings tab > Division Module) you can see the country flag of that Division in the Objects Tree. If you dispatched a Checkout and forgot to set the correct Target Division, the Objects Tree Division flag on those Objects wouldn't change.

Now, you can change the Target Division on a Checkout and the change will be reflected in the Objects Tree and in the Object Manager.

This new auto-save option is available per User and will prompt him in the case that the application shut down with the dialogue: "Unsaved Item Changes Detected. Would You Like To Restore Them."
The prompt will show when the User accesses the Dispatch Module again.

If the User clicks No on the prompted message, any changes are lost, if he clicks Yes, the Dispatch will open again and the User can continue with the scanning of the items.

Only line item changes will be stored and trigger an auto-save recovery. So changes in Contact or Pickup or any date changes will not trigger an auto-save.

Only available if EMT is licensed and if the Dispatch Workflow is used with Master Check In and Master Check Out.

Within an EMT Booking (with Dispatch Workflow), you can establish Preparation, Delivery, Collection, and Return Dates. These dates are presented as "On Day Activities" within the Dispatch Module, now equipped with search and filter options activated by clicking the respective checkbox. You can filter by only one or multiple "On Day Activities."

It is now possible to copy/paste the Object's inventory number inside a Check In or Check Out window with the shortcut keys: CMD+C and CMD+V (for PC: CTRL+C, CTRL+V). Simply highlight the object line for it. You can also multi-select the items and use the option.

Columns that have been added and can be displayed through the Menu > Edit View:

• Collection Handled By Client
• Delivery Handled By Client
• Delivery (Date)
• Return (Date)
• Return Date)

Go to fw Client > Toolbox > Settings > Dispatch Module >"Send Due Objects To Be Returned Email To Pickup Contact At Time:"
Select here a time, when this daily reminder email will be sent to the Dispatch Pickup Contact, until the overdue Items have been returned.

The header of the email will show: "You Have x Objects Due To Be Returned."
In the body text of the email the items that are overdue will be listed and the email will say: "Please return the following x due Objects urgently or contact warehouse manager to prolong the check out".

Example of an overdue camera in the DemoDB:
ARRI ALEXA • 115002 • FCB Barcelona - Real Madrid (19) • Checked out 21-08-2023 (3)

Object name - inventory number - project name (number) - checked out date (number of Dispatch)

See more info here:
https://support.farmerswife.com/en/support/solutions/articles/17000097532-2-toolbox-dispatch-module-settings-emt-dispatch-settings-and-configuration

A new setting was added in fw Client > Toolbox > Dispatch Module > "Send Email To Divisional Managers When Dispatch Is In Preparation".

Once enabled an email with the header: "New In Preparation Dispatch Was Created: Dispatch Number / Name of Creator of the Dispatch will be sent to the Divisional Manager for that Dispatch.

See also more info here:
https://support.farmerswife.com/en/support/solutions/articles/17000097532-2-toolbox-dispatch-module-settings-emt-dispatch-settings-and-configuration

Inside of a Check In and Check Out you have a column called: Current Dispatch Status with an arrow indicating whether this Object is out or has been returned. This column is now added to the Dispatch report > Row section.

This comes in handy when creating a picking list to see whether the listed Object is already in house or still out.

The Dispatch Note is now searchable and results can be returned in a column on the Dispatch Module.

In the Dispatch Module > menu > Edit View two new columns can be added to the result pane.

On a Master Check Out it is not possible anymore to create a New Check In From Selected.

A Master Check Out is created if on the Booking Name Template the Dispatch Workflow is enabled and a Dispatch was created.

Functionality only available if EMT is licensed and the Dispatch Workflow is used.

On a Master Check Out it is now possible to create a Holdover directly from the Master Check Out Edit window > menu > Create Holdover (number of Objects).

Once this option is selected, a window "Objects To Be Heldover" will allow you to select which Objects should be held over. Once selected click OK and select an existing Project for the Holdover Booking from the next window.

Select now whether to "Create A New Booking" or "Choose An Existing Booking" in the "Hold Over Into Project (number)" window.

In the Calendar that pops up by default the end of the original (Source) Booking is selected as the start day and the end date is taken from the setting from the Toolbox > Settings tab > Dispatch Module > xxx.

In the "Confirm The Holdover Actions Below" window you will be presented with the info, that the new "Target Booking Will Be Created"
You will see the start and end date of the Booking and the duration in days, as well as the Project number:

Example:
15-05-2024 • 16-05-2024 (2 Days)] In I Love Music (25109)

The Following Objects Will Be Checked In On Source Booking And Back Out On Target Booking Using Date: (date)

Example:
⬇⬆ 9912879 • Sony HDC-4300 4K-HD

The Holdover Booking is created with its Master Check Out and Master Check In.
The Master Check Out is already dispatched and the Master Check In Pending Status.

If the option "Choose An Existing Booking" is selected a window pops up, showing a list of all Bookings for this project. Bookings that are not available will show with a yellow warning triangle:
Holdover Would Start Before Current Check Out on <date> Which Is Not Allowed.

Move the Booking to the selected side and hit OK. In the Calendar popup the Booking dates of the selected Booking are marked. Hit OK.

The Holdover Booking is created with its Master Check Out and Master Check In.
The Master Check Out is already dispatched and the Master Check In Pending Status.

If the dates are adjusted to a different date, the window popup to confirm the Holdover changes will hold this information:
Example:
Target Booking Start Date Will Be Changed To: 24-05-2024 (+7 Days)

Target Booking End Date Will Be Changed To: 30-05-2024 (+10 Days)

The Following Objects Will Be Checked In On Source Booking And Back Out On Target Booking Using Date 24-05-2024:

Below of all Objects involved will show like this:
⬇⬆ 9912879 • Sony HDC-4300 4K-HD

The option to create a Holdover is greyed out, if you access the Master Check Out from the EMT Booking. A message will show: Create Holdover (Not While Booking Window Is Open).

When accessing the Dispatch Module, the Advanced Search options are now concealed to simplify the search. However, you can still access the Advanced Search by checking the "Advanced Search" checkbox.

You will find a master Search "All" field, which will search adeptly throughout all the Dispatches. By hitting Enter in the master search field will give you the search results. It will also clear the adjacent Date field.
The "Search" is now hidden inside of the "Advanced Search".

A new Date field Search feature allows for searching specific days. Upon entering a day, a second date field appears for searching within a specific time range.

Adjacent to the Date field, you'll find two blue arrows framing a house icon, enabling navigation one day back or forward with a click. No Enter is necessary to show the Dispatches that have an On Day Activity as Preparation, Delivery, Collection or Return.
Clicking on the house icon fill in today's date into the Date field.

The On Day Activities consist of Preparation, Delivery, Collection, and Return. These values are drawn from the corresponding EMT Dispatch Workflow Booking. When searching for a particular day, the On Day Activities are displayed in this column, with the corresponding dates highlighted in yellow in their respective Date Field.

The Division filter allows to sort the Dispatch module by Division.

The Overdue Items button initiates a search for all overdue Objects, automatically checking the "Show Items" checkbox.

Previously, a dispatch window would randomly close whilst using a barcode scanner. This fixes that bug.

Previously, if the User setting "Allow Modifying Booking After It Is Dispatched" was active, and the user changed the duration of checked-out Dispatches via the associated booking on the Longform, this would incorrectly add already returned objects back in to the booking for the new full length.

This fix means that if the duration of the booking is changed, objects that have already been returned via dispatch will not be added back in for the new booking duration.

Added 8 more data fields to the Dispatch Module, along with a "Total" for Dispatch Days, and a "Total: xx / With Client:xx".


Preparation / Date And Time:
Allows to set a Preparation Date where equipment is being prepared and made ready for shipment.

Collection / (Handled) By Client:
Tick if the client is picking up the equipment at your premises.

Collection / Date And Time:
Set a Date and Time if you collect the equipment back from the client.

Modified:
Date and time of last modification

Modified By:
Name of User who last modified the Dispatch

Delivery / (Handled) By Client:
Tick if the client is picking up the equipment at your premises.

Delivery / Date And Time:
Set the Time and Date when the Delivery will happen.

Mobile:
Add a mobile phone number directly, or select a contact and the mobile phone number will be pulled through.

This data will all be available in the Edit View menu option to show the value as columns in the Dispatch module, and is printable in the Dispatch Report through the Print Designer.

If the lock sign between the two sets of Dates is closed, any change on Preparation Date will be synced with Delivery Date, and a change on the Collection Date will by synced to the Return Date. Opening the lock will allow the user to set 4 different dates.

You will see the total of the days between the two Date Fields.

A "Total Days" will show the summed up days of the Dispatch.

If the Dispatch is linked to a Booking and the lock sign between Preparation and Delivery Date is open, setting a Preparation Date will get the Dispatch to start earlier. The same applies for the lock between Collection and Return Date. The Booking will expand to the newly set date.

Columns that can be selected to show are:
-Show Thumbnails
-Quantity
-Class / Format
-Type
-Box
-Expand Groupings By Default

Dispatches that come from the "Dispatch Booking Workflow", will have the Project Name AND Booking Name set as their default Dispatch Name.

NOTE: These Settings in the fw Client desktop app > Toolbox > Settings > Dispatch Module are "Use Booking Name In Dispatch Name" and "Use Project Name In Dispatch Name When Booking Name Is Empty" don't have any effect on those Dispatches.

Added new user Permission for Advanced Users (AU) which allows to limit visibility of Projects to the "own" Division.

If "User Can Only View Projects From Own Division" is enabled, the AU is not able to see Projects from any other Division.

This is supported across the entire system, so as a result:

• The Advanced User can not see Projects from other Divisions in any Modules (Scheduling, Media Library or Dispatch) or any menus / pop-up messages where Project lists are being displayed.
• The Advanced User can not search for Projects from other Divisions in the Advanced Projects Search (main Module bar > Projects).
• The Advanced User can not see Projects from other Division in the Reports.
• Because of this limitation in the Projects' visibility, the Advanced User is not able to create a Booking, Media Order or Dispatch for any other Division and can only work within Projects in "own" Division.

This option is accessible in the Toolbox > Settings tab > Booking Defaults and works together with the Dispatch Workflow you can setup in the same place.

Select the default invoice mode that those kind of Bookings will follow:
"Invoice Days As Booked" if ticked, it will take the Booking Start Date and the Booking End Date and invoice the amount between.

If a new Booking is created with this option on, the "Days To Invoice" option will show: "As Booked: xx Days". It calculates the amout of days from start to end.

If you choose not to tick it in the Booking the "Days To Invoice" option will show: "With Client: xx Days". It calculates the amount of days between the Delivery Date and the Collection Dates, as those are the days that the equipment will be with the client, and the client will only be charged those days.

If an item is overdue, this will show with a yellow warning triangle in the New Object Tree. Clicking on the triangle in the New Object Tree on the left will show a a yellow mouse over that will show the dialogue: "Client Name - Overdue Since: Date (amount of days)".

Within an EMT Dispatch Workflow Booking, you have the option to include a Note for the Delivery and Collection Method. Simply click on the selector field, scroll down, and choose "Edit Note". Any added Note will be displayed as a small bubble next to the selected Delivery and Collection method. This Note will then appear in the corresponding Master Check Out and Check In.

Each Dispatch that is coming from an (EMT) Dispatch Workflow Booking, will have direct access to the Master Check In and Master Check Out of the corresponding EMT Booking so you can navigate. The links will be in the top right corner of the Dispatch.

The Master Check Out will have the "Dispatch Workflow Booking" and the Master Check In link, whereas the Master Check In will have the link to the Dispatch Workflow Booking and the Master Check Out.

When using the new Dispatch Workflow with EMT, removing a Dispatch Booking will now also remove the linked Master Check In & Check Out.

Added a lock icon in front of the Dispatch address in the EMT Booking, with the option to add a different collection address to the Master Check-In, than the client's address. Once the lock is open, a new address field for the collection address appears to the right and by starting typing into the field, any address from the contact database can be selected as well as any free text.

Hit Apply so the change is saved in the corresponding Master Check-In.

Facilitated changing from a Master Check Out via the "Dispatch Workflow" button to go back to the EMT Booking and accessing the Master Check In.

Within the new Object tree functionality on v7.1, you now have the option to create a "Hold Over" by right-clicking on the Booking > Dispatch Workflow Booking > "Create Holdover" option.

From the same menu you also have direct access to the Master Check Out (arrow pointing up) or Master Check In (arrow pointing down).

The "Create Holdover" feature allows you to initiate a process for holding over equipment that remains with a Client and will not get returned to the original warehouse. Instead, it will be used by the same Client but on a different Project.

The "Create Holdover" feature is greyed out (= not active), if the Master Check Out has not been dispatched yet. And it will not appear in the menu, if the Booking isn't an EMT Dispatch Workflow Booking.

To create a Holdover go to the fw Client app > Long Form > new Objects tree and right click on the Booking you want to create a hold over for. Select "Create Holdover".

In the next window: "Objects To Be Held Over" select the Objects that should be held over. Click OK to confirm.

In the following window "Select Project For The Holdover", select the Project that the Holdover is for. You have now the option in the "Holdover Into Project" window to "Create A New Booking" or "Choose An Existing Booking".

If "Create A New Booking" is selected a Calendar will pop-up already indicating a new Booking time, taking the Return Day of the original (Source) Booking and adding as many default days to the Booking, depending on the setting selected in the Toolbox > Settings tab > Dispatch Module > "Default Expected Return Date After Days And Time".

If a time range is selected in the Long Form (= days are highlighted in yellow) there will be a pop-up asking whether the Time Range should be used or not.

You can also select a new Time Range in the Calendar and farmerswife will adjust the Booking dates, see below.

The next window will ask you to "Confirm Holdover Actions Below".
It states, that a new Booking will be created:

New Target Booking Will Be Created:
Date from - Date to: (duration of Booking in Days) In: Project name (Project Number).
Example :

15-05-2024 • 16-05-2024 (2 Days)] In I Love Music (25109)

Target Booking Start Date Will Be Changed To: 24-05-2024 (+7 Days)

Target Booking End Date Will Be Changed To: 30-05-2024 (+10 Days)

The Following Objects Will Be Checked In On Source Booking And Back Out On Target Booking Using Date 24-05-2024:

If an (EMT) Booking with the "Dispatch Workflow Booking" enabled is set to Status Cancelled (i.e. the Sub Status needs to be set to "Cancelled"), then the Master Dispatches will be deleted together with the Booking!
This will only work, if the Master Check Out has not been set to "Dispatched".

This new setting was added in Toolbox > Settings tab > Dispatch Module > to "Activate Booking Dispatch Workflow When Booking Is Confirmed".

It works together on Bookings that have the setting in Setup in Toolbox > Settings tab > Booking Defaults > Booking Names & Customs: "Dispatch Workflow" enabled.

Once this new setting is enabled a Master Check Out and a Master Check In are created as soon as this Booking is set to a Confirmed Booking Status.

If the Booking is created by default in a confirmed Global Booking Status, the "Activate Dispatch Workflow" toggle switch is turned off and needs to be set to active manually. Or the Booking Status has to be changed to a not confirmed Global Booking Status and back to a confirmed one.

The former checkbox: "By Client" has been replaced with a selector field to set a Delivery and Collection Method.

Default options to choose are:
Delivery By Us
Delivery By Courier
Delivery By Client

Collection Method:
Collection By Us
Collection By Courir
Collection By Client

Additionally, there's an "Other" option that enables inputting any text, while the Setup option permits adding new default options and rearranging existing ones.

Additionally, there's an "Other" option that enables inputting any text, while the Setup option permits adding new default options and rearranging existing ones.

All options will be displayed in the Dispatch module Edit View > Delivery Method, Collection Method.

When an Object is checked out but hasn't come back in yet, it will show as overdue. Now this Overdue is also displayed with a yellow triangle icon in the Longform > Object Tree and in Toolbox > Objects Tab > Status column and in Object Manager > Status Column.

It is now possible to activate the Dispatch workflow on a Booking that already has a Check Out created for it.

It will create a Master Check In in Requested mode, that can then be adjusted and the equipment can be checked in against it.

In Toolbox > Settings tab > Booking Defaults > Booking Names & Customs: Added in the Modify window option a checkbox: "Dispatch Workflow", if EMT is licensed.

Below the checkbox you can set Dispatch Custom Field templates for the linked Dispatch:
"Default Custom Fields For Check Outs" and"Default Custom Fields For. Check Ins". Those have to be setup previously in the Dispatch module. The Custom Fields won't be accessible from the Booking Window, they will just appear in the linked Dispatch.

The "Dispatch Workflow" allows to establish Booking buffers by specifying Preparation Date, Delivery Dates and Collection Date and Return Dates.

Preparation Date and Delivery Dates are synced and come from the booking time range, unless the lock icon is opened and a different Preparation or Collection Date is selected. The difference between the original booked time range and the newly set preparation or collection and return time will be shown as buffers in striped pattern on the Booking in the Project and Object Tree.

Edit Booking Window and Master Check Out and Check In:
The Contact fields in the lower right part of the Booking come from the Project, but can be set to match a new client or edited directly from there. The Mobile number is being displayed and can also be added manually if needed.

Once the Dispatch Workflow is activated, the toggle switch disappears and a Master Check Out and a Master Check In are created automatically.

The Master Check Out is shown with its Dispatch Number as a blue link right next to the Preparation and Delivery Dates and is clickable. A yellow mouse over will show the Status of the Dispatch, which will be by default Requested.

The Master Check In will be shown next to the Collection and Return Dates, also as a clickable link in blue, and the yellow mouse over will show its actual status, which by default is set to Requested.

On the Master Check In those Statuses can not be changed. However there are new Sub Statuses that can be set manually in the Dispatch Module on The Master Check In:

• Being Collected
• In Transit
• Collected
• Other - allows you to set a custom Sub Status.
• Setup: Create here more Sub Status for the Check Ins and sort them.

• yellow for "In Preparation" and "In Preparation (No Swapping)"
• green for "Ready"
• red box with arrow pointing up for "Dispatched"
• a yellow warning triangle for "Overdue"

• Being Delivered
• In Transit
• Delivered
• Use "Other" to type in a custom Status

On certain system this optimisation has improved the involved action from before taking 28 min. ... to now be completed in 40 sec. !!!

In Header, Footer and Groupings, the Financial Report shows Totals for quantity, split by unit. But for items with Fixed Price, it just shows "Fixed" instead of e.g. "5 Fixed".
Now there's a setting that makes it show the quantity as well, e.g. "5 Fixed".
You can find the new setting in the Financial Report launch window, in a pop-up menu next to the "Mix Units" checkbox. It's called "Show Quantity For Fixed Price".

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

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

This bug only happened if you reported on a limited date range ("Filter Lines In Range").
If a Booking spanned multiple dates and was invoiced, and then the Quantity and line total was manually edited in the Invoice, and you then reported on a date range that would subdivide that Booking, a bug happened in the Invoiced numbers. It caused the Booked/Used numbers to be used instead of the Invoiced numbers.
Now it will respect the manually edited line totals and instead attribute them to the first day in the Booking.

This feature is aimed at improved accessibility for the farmerswife Desktop app.
By using [cmd + .] on macOS or [ctrl + .] on Windows you can now lock mouse-over pop-up information in place. This should then help to use 3rd party tools to "read out loud" the textual information.

Once done use again [cmd/ctrl + .] to un-lock the mouse-over pop-up.

You can now press the left "cmd" key on macOS or the left "ctrl" key on Windows after you have started moving a Booking via dragging it. If it is moved above the limit (a bit above the Long Form or Hourline timeline) and you have left cmd / ctrl pressed, then farmerswife will auto-scroll upwards.

Also using on a Booking + cmd / ctrl. + drag & drop still works to copy Booking as before.
And now, when a Booking is at the bottom of a very long list of Objects in the Long Form or Hourline, you can use Booking + cmd / ctrl. + drag & drop to copy the Booking + release cmd / ctrl and press left cmd + ctrl. again to drag-auto-scroll the Booking to the very top.

Calendars on the Public Holiday importer have now been updated and extended to 2035 for all existing regions, to match the extension of the fw Toolbox Calendar in 7.1.

We have also added Public Holiday Calendars for: Canada, New Zealand, Norway, Scotland, Singapore, and Spain.

See more from the article on Public Holidays here:
https://support.farmerswife.com/support/solutions/articles/17000050561-how-to-add-or-remove-a-public-holiday

This affects the share button in bottom-right corner of the following places:

• All tables
• Print Designer
• The conflict dialog

When "User Must Accept/Decline New Bookings" was enabled and Bookings were sent for User approval via Google Invites, the Approval Status would not get updated in farmerswife after the user approved or declined the Booking via Google.

Now this bug is fixed and users can approve/decline Bookings in Google, which then correctly updates the Approval Status in farmerswife.

These changes fixed wrong status updates when changing a booking and additionally will reduce significantly the amount of notifications by using the API http method PATCH instead of PUT, for partial updates without resending attendees.

Previously the booking status would be wrongly updated for all involved on nearly any change in the booking, f.ex. when:
1. adding/removing additional involved to the booking
2. replacing one involved with available class members
3. updating booking time of one involved
Now the status is correctly updated only for the specific user in case the changes affect that user directly (a user is added/removed from booking or his time is updated); others' involve status is correctly NOT reset in the above mentioned scenarios.

You can now choose to Auto Adjust Objects Height on the Hotkeys Editor, when using the New Objects Tree.

Previously, the setting for "Use Binder Color" was incorrectly being prioritised over othe color settings such as "Always Force Preliminary Color When Preliminary".

This fix corrects the prioritisation order, and also corrects the behavior of the setting: "Force Hourline Colors Everywhere" (in fw Client app > Toolbox > Settings > Display), which was incorrectly showing the Binder Color even if the Booking was conflicted.

Added to fw Client app > Toolbox > Settings > Hourline > “Always Force Use Task’s Defined color”.
This will overwrite any other colour setting.

This setting allows users to see the Task's defined color, to always show no matter what color settings are changed or used in the Hourline.

If you use the setting in fw Client app > Toolbox > Settings > Display > "Force Hourline Colors Everywhere", this will also be applied to the Objects tree, regardless if you change the setting in the Toolbox.

This feature also works regardless of "Always Force Preliminary Colour When Preliminary" or "Always Force Preliminary Colour When Planning".

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

To show the booking number you can go to the Invoice Editor > click the menu > Edit View > click to move "Booking Number" to "Selected"

Both in the Invoice Creator and Invoice Manager and the Invoice Report, when using the "Fixed Price" feature, the set fixed price was wrongly not saved and thus not available.
This is now fixed.

If you first created a Closing Point for a User without the new Custom Personnel Type, then created the Custom Personnel Type and enabled "Earned Type Calculations" on it, then it could crash when calculating Labour Rules totals for the User.

This Bug does not require a new MacKiosk version; upgrading the fw Server app is sufficient.

When this is enabled in fw Client > Toolbox > Settings > "Email Footer", this email footer will be added to the end of all emails with configurable templates.
HTML is supported on these fields.

In the case of a plain text footer with urls, the urls are clickable in html emails.
For "email templates" a new variable can be used to include this footer content: <VAREMAILFOOTER>.

IMPORTANT: Existing default templates are updated to include this variable at the end of the emails. It can be moved to any position in the template as needed.

It's currently supported in:
1. Schedule changes email sendout
2. Client Invoice Email
3. Client Credit Note Email
4. Booking Report Email
5. Global Notifications
6. Timereport Sendout Reminder
7. Send Emails to User in Tree

IMPORTANT: As soon as you start "customizing" any farmerswife Template, you need to be prepared to maintain your customized changes. You need to store and keep your own backups of your changed Templates!
On every upgrade the current "default" Templates will over-write your customized Templates, because they use the same file name.
Also: If e.g. bug fixes were implemented on Templates, you will need to re-apply your custom changes on the fixed Templates.

Use this updated Solution Article for detailed information: https://support.farmerswife.com/en/support/solutions/articles/17000026044-creating-a-new-media-and-media-entries

In fw Client > Toolbox > Projects select and thus high-light a Project > right-mouse click > "New Project From: [selected]", farmerswife will now ask if the linked Media Orders should also be copied, if there are any.
The Status of the Media Orders will be reset to "Pending" and the Media Order Jobs will be reset to "Not Done".

When using the Multiple Currencies feature you are now able to import all your Object Rates in the various Currencies that you enabled in the Multiple Currencies setup.

Additionally you can use the Edit View in the Object Manager and view all the Currency Rates in the table view.

For more information on the use of the Multiple Currencies feature read
https://support.farmerswife.com/en/support/solutions/articles/17000115540-multiple-currencies

For Dynamics 365 Business Central Online environments, the basic authentication (Web Service Access Key) is deprecated, and users will need to use OAuth. This is now supported.

This change forces the Jetty tmp files to be located in the already used path:

APPDATA/Farmers WIFE Server/jetty-tmp

It's now possible to customise the text in Push notifications depending on the accept/decline setting of the user.

This can be implemented using a new open/close tag:
<acceptdecline>Your content here</acceptdecline>.

Only users who have have "User must accept/decline Booking" web profile permission enabled will have the text between the tags included.

Some default text is included in the following templates:
EVENTONDAYADDED, EVENTCHANGEDNAME, EVENTONDAYCHANGEDTIMEANDNAME, EVENTONDAYCHANGEDTIME.


A new template has been also added in fw Server installation folder > htmltemplates > mobilenotifications > BOOKINGACCEPTORDECLINE.txt

This template defines what will be sent to users by Push notification for a New Booking if they have "User must accept/decline Booking" web profile permission enabled.

Additionally there is a new push notification when users ONLY change the accepted/declined status to pending: EVENTONDAYACCEPTORDECLINE.

Added new folder in fw Server-side > htmltemplates > "mobilenotifications" by which fw server admins can change the "push notifications" Templates.

Added all current default Templates files for the existing *33 push notifications".
The fw server will check for changes on these files at the moment of the initialisation.
If a file doesn't exists, the current "english default texts" are applied.

Dynamic data in Templates are in the following format:
<noneditablekey>.
For instance: The template EVENTONDAYADDED.txt contains the default text:

New event added on <eventday>, <eventtime> for <eventtypeandname>

The event <eventtypeandname> has been added on <eventday> <eventtime> for you.

It is possible to add involved Objects from within the Booking Window by clicking the "Add Involved" icon at the top of the "Involved" section.

Previously in the "Select Objects" window you would have to select one or multiple Object or Classes and then press OK to add them. If you double clicked an Object, the Object Info Window would open.

This has now changed and by double-clicking the Object it is now added to the Booking. To see the "Info" window you can right click the Object > Show Info.

See more info here: https://support.farmerswife.com/a/solutions/articles/17000057260/edit?portalId=17000028013

Added checkbox to the Object Class Edit window: "Use Auto Numbering On Primary Members" so each Object will get a consecutive number when added to the Object Class. This number won't change but stays with the Object. This will make it easier to select an Object when scanning.

You can now assign a Permission Profile to Users in the Import file which will then be assigned to the User.

Go to: fw Desktop Client > Object Manager > Menu > "Import / Export farmerswife Objects Format CSV File" > ...

Recommended: First select one User > "Export", then modify the .CSV file, and then use "Import".

The name in the column: "Permission Profile" must be written exactly as in the Object Manager > User > Permission Profiles / Web Permission Profiles.

If the fields for "Permission Profile" or "License Type" ("advanced" or "web") are empty on importing, the default License Type will be (web) "Web User" and default "User Permission Profile" will be the first one that is currently saved in the Permission Profile / Web Profile Manager (if any).

If you delete an Advanced User Permission Profile, the Users who were using that Profile will get the "Custom" profile.

On importing a new User and choosing a deleted User Permission Profile in the import file, the imported and all existing Users will get the default profile (first created and still existing Permission Profile) assigned.

If a Web Permission Profile was deleted, the applied user will not have a Web Permission Profile assigned anymore. The imported Web User that have the deleted profile assigned in the import file and all Users without a Web Permission Profile will get assigned the next Permission Profile in line (below the one that was deleted).

In the Object Manager > Menu > Edit View two new columns can now be displayed:

User License Type refers to Advanced User or Web User.
Permission Type refers to the Advanced User Permission Profile settings: Web User Only, Task User, Task/Booking User or Task/Booking/Rates user.

In the Object Manager the Dispatch Name, Dispatch Number, Dispatch Project, Dispatch Return Date and Dispatch Address have been added as columns. Those can be shown via the Edit View option in the Menu.

Previously, the display order of columns in the Object Manager was dependent on which of the columns you clicked first. You could not rearrange them, only take all columns away and start from scratch.

Now there is an "Edit View" option in the Menu dropdown of the Object Manager, which will allow you to select the columns you want to "Hide" or "Show", and then drag and drop them up or down to the position they should appear.

In the Object Manager's "Location" column, the date indicating since when the Object is overdue has been included. Additionally, this information can be viewed in the Object Tree by hovering over the yellow triangle that signifies the overdue status of the object.

In the Object Manager menu added the option "Save View As", "Remove View", "Load View".

Added to Object Manager > Edit View > Columns:

• Dispatch Project Number,
• Dispatch Company and
• Dispatch Client

Added to Object Manager > Edit View > Columns:

• Location Change Date: The date that a User did an action that would change the location state of an Object, like a Check In or a Check Out of an Object.
• Dispatch Check In: The time that the Object was checked In and the Check In was created.
• Dispatch Check Out: The time the Object was checked out.

This functionality is used in combination with the new Print Designer "Merge PDFs From..." functionality.
This feature is used, to provide the "Object" level based "PDF input source", which in turn then gets used in a later step to create PDFs, including merged info from other PDFs into one single PDF.

When selecting an Object in the Object Manager under type: Equipment/Machines there is a new option in the Menu to select to open the corresponding Dispatch.

If there is no Dispatch for this Object the option "Open Dispatch" is disabled.

Prior to this change, Buy Prices could not be changed directly in the columns when using Compare with Global Ratecard.

In the fw Client app's Object Manager > sub-menu > Settings this new option is now available: "When Creating New Object Set "Inherit Rates And Activities From Object Class" To Yes".

When this setting is enabled, each time you create a new Object in the Object Manager, the setting at the top of the Edit Object window "Inherit Rates And Activities From Object Class" will be ticked by default. This way you ensure that the Object will take its Rates from the Object Class (if the Object belongs to an Object Class).

See more info here: https://support.farmerswife.com/en/support/solutions/articles/17000053945-create-and-manage-objects-in-the-object-manager

Expanded the Object window for Objects created in the following categories/types:

• Rooms / Suites / Workstations
• Machines / Equipment
• Others / Facility

• Object Permissions (if activated)
• Member Of Object Classes
• Activities
• Accessories

• Created Object (if imported via a .csv file this line won't show)
• Inventory Number
• Division
• Ref
• Inherit Rates And Activities From Object Class (shown as Rates)
• Rates (any change on any Rate will be shown)
• Groups
• Tax
• Day Rate
• Allow Multiple Check Outs (Virtual Object)
• Is Expected To Be Returned
• Active
• Icon
• Note
• Confirm Note
• Start And Stop Date
• Causes Conflict
• Inherit Accessories From Object Class
• Custom Field Template (shown as Customs)
• Custom Fields (shown with the label of the Custom Field)
• Check Outs
• Check Ins

Previously, if you right-clicked on an Object within a Group and selected "Info," it would open the new Object window and cause the fw Client to crash. Now, performing the same action will display a compact window with the Object’s information, preventing the crash.

If you had some feature's "column" enabled which was later removed from the license (e.g. Cirkus), the columns would wrongly shift the displayed information to the wrong column. This is now fixed.

When using the Object Manager, if an Object had a Custom Field (Text Widget) where data was added with a return so data would show below each other on new lines, in the column view of the Object Manager you would only see the first data entry line.

Now you will see all the data entries (depending on the column width) next to each other separated by a "."

Example:
Cover
Tripod
Car

Will now show: Cover. Tripod. Car in the column.

If you drag and drop an Object onto a Booking of another Object, the "Confirm Replacing" dialogue pops up. Previously the window couldn't show long Object names with long inventory numbers. Now the width of the window was adjusted to also fit long Object names.

Previously, if you'd booked an object that had Object Class Accessories, but the Parent was booked with a different price to the main rate card; replacing the Parent with a new object would not bring up the prompt "Do You Want To Keep The Old Class, Activities And Rates". This would mean the prices on the newly booked Parent Object, were reset to those on the Global Rate Card.

This fix now brings up the prompt, preventing the pricing from being reset.

Added to Toolbox > New Object Tree (Classic Mode unticked): Note Icon, which will show the Booking Note in the Longform and the Object Note through the Note icon.

If the setting: Draw Hour Boundary is used the Note Icon will only be displayed if there is enough space.

In the settings for the New Object Tree, you can now select the max height of pixels you want to expand the Object line to. Selectable are pixel heights times 2, 3, 4 etc. depending on the Line Height value selected below.

If for example 22 is selected, the lowest pixel height is 44, 66, etc.

This feature is only available if Divisions is licensed.

It is now possible to click on a "Dispatched Division" flag to the right of each Object to toggle to that Dispatched Division, meaning the Object Tree only shows these Dispatched Division Objects and hiding the rest.

Once toggled (yellow mouse over - "Click To Solo View"), the Dispatched Division flags will appear at the top of the Object Tree and a yellow warning triangle will indicate that this view is filtered by "Division", crossing out the flags of the Divisons that are not being shown. By clicking on the flag that is currently showing in Solo View, you release all Division filters.

You can also turn the filter off by clicking on the yellow triangle.

Use the option "Alt/Command Click To Remove" on a Dispatched Division to remove this Division from the View. Simultaneously all Division flags will show at the top right of the Object Tree being crossing out the one that was clicked.

Once all flags have been removed at the top right of the Objects Tree, the view shows all Objects again with all Dispatched Divisions.

All Shared Views that start with the same name will be shown in a cascade view like they show in the Hourline view selector.

Added to the Toolbox > Objects Tree tab, the option to de-select: Classic Mode. Per default this is selected and you will see the Objects Tree with all the settings as up until 7.1. If you untick Classic Mode you will be presented with a new Object Tree, that differs slightly in the GUI and with the following new settings:

Draw Cancelled: Will show Bookings with Cancelled Substatus
Draw Planning: Will show Bookings with Planning Substatus
Draw Preliminary: Will show Bookings with Preliminary Substatus
Draw Tasks: Will show Task Bookings
Draw Hour Boundary: Enabling this option will display bookings as small rectangles aligned with the time of day they occur. If unchecked, bookings will be stacked on top of each other, occupying the entire day's space.
Add Object To The List: When selecting the Object in Toolbox > Objects tab > Add To Tree the Object will be added below all the other Objects in the Objects Tree.
Mouse Over Bookings: Will show the Mouse Over when hovering over a booking.
Draw Multi Day Events Without Actual Time Range As One: Only works if "Draw Hour Boundary" is set. It will show multiple day Bookings as one, even if they don't go through the night and have: "Use Actual Time Range" set.
Auto Adjust Objects Height: If ticked, the Objects line height will extend to make room for the stacked Bookings. If not ticked, the Booking rectangles will adjust themselves to the line height given.
Expand Events Height: Will expand the Booking to occupy the entire height of the object line. Useful if e.g. on some days you have 2 booking so they are stacked and then days with only 1 Booking the Booking would only occupy 1/2 the line height.
Show Number In Name: Will add the Project's Number in () after the Project Name.
Draw Large Conflicted Days Warnings: When enabled will show the conflicted days with larger red rectangles instead of small lines at the bottom.
Classic Mode: Activating this option restores the traditional view of the Object Tree, including all its settings as they were prior to version 7.1.
Line Height: Set a default line height which only applies to the Object Tree.
Colors: Will only show Global Status Color (for now).
Focus is now set on the Booking that the mouse is hovering over, double click or single click will open the Booking.
Objects Tree Menu > View Mode > will only show: Verified and Verified/Checked Out. Will also show those colors in the new Object Tree.

This option is only available if Divisions is licensed. In the Objects Tree click on the menu icon > Filter > Divisions to only see Objects of selected Divisions in the Objects Tree View, Objects from not selected Divisions won't show.

All selected Divisions will show with the little flag icon at the top of the Objects Tree to indicate which Divisions are showing.

Do the same to only show Objects from certain Disptached Divisions (Target Divisions).

This setting is only available in Toolbox > Settings tab > Object Tree > untick Classic Mode > New Object Tree, if the checkbox "Auto Adjust Objects Height" is not selected.

If the "Auto Adjust Objects Height" is selected, this setting is unavailable.

With this new setting it will be possible to see more text of overlapping Bookings, so it displays it similar to the Classic Mode.

Enable new Object Tree by unticking: Classic Mode in Toolbox > setting tabs > Objects Tree to access these new settings:

Added various settings into the New Object Tree tab in Toolbox > Objects Tree >

1. Use Client/Container/Project color: Will show any of these colors, if there are set and overwrite the Booking Status colors.

2. Always Force Preliminary Colour When Preliminary: Will overwrite all other colors and show the color that is selected for Preliminary in Toolbox > settings tab > Display.

3. Always Force Planning Colour When Planning: Will overwrite all other colors and show the color that is selected for Planning in Toolbox > settings tab > Display.

4. Show Conflicts: Option to show or hide any conflicts on Booking. If ticked "Draw Large Conflicted Days Warning" is accessible to be ticked as well.

If a Booking is an EMT Booking that has the Dispatch Workflow enabled (Toolbox > Booking Defaults > Booking Custom/Names) and you set a Preparation Date that is not the same as the Delivery Date, along with a Collection Date that is not the same as the Return Date, you will now see those buffer days in a darker color with stripes for easy indentification.

By clicking on the Objects Tree > menu icon > Options > "Always Sort Objects By Their Current Dispatched Division" the View separators will now be respected.

Before when using this option the View would lose its groupings like "Cameras", "Lights", "Arri Alexa", and the Objects would be rearranged according to their dispatched Division (Target Division) showing always first the Division the User is in.

In the Toolbox > Settings > Server Setup > Password Policies > Configuration it's now possible to set Previous Password Limit.
If the value is set to a specific number, the user can not re-use such amount of previously used passwords, when changing his password.

Previously it was possibly to add a space as leading and trailing character when creating password.

This is now restricted, and space can only be used inside the password (not as leading or trailing character).

Until now the licensed Advanced Users showed as total number in the Permissions Type dropdown of the Advanced User Permissions window, leaving it unknown how many Task Users vs Tasks/Bookings Users were actually licensed.

Now the Task vs Tasks/Bookings license numbers are split and you can see how many of each you are using.

To learn more about the permissions and license types please see http://tinyurl.com/fw-user-permissions

Affected by this issue were Advanced User's with the Permission Setting "Can Approve Purchase Orders” enabled.

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

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

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

In the Desktop Application > Long Form > Custom Types you can add new Custom Types and decide whether they should cause a Conflict or not.

When creating a new Personnel Event over another Booking, there's no conflict shown. But when you then move the Personnel Booking over another Booking you incorrectly get a conflict warning.

This has now been fixed.

Sometimes when you dragged a Personnel Event to move it, it would disappear or have a negative start time.

This fix also adds an upgrade that sanitizes invalid In/Out times on Personnel Bookings. If any are found, it will log each one similar to this within the fw Server app's log.txt file:
> Upgrade: Corrected in/out times -4:-30 - 09:00 (-13.5 - 0.0) on "Vacation" Personnel Event for <username> on 18-02-2021 (id202102031216520000001350). New times: 09:00 - 22:30

If you see these kind of lines in the log, we recommend that you navigate to the indicated day for the user, see what Personnel events are scheduled, and reschedule or delete the logged Personnel event.

Previously when using Tabbing in Notes within the farmerswife Objects or Elements, the Tab distance wasn't correctly put out into the PDF print.

Now you can configure the "PDF Tab Size" with the new option, ensuring that the tab is as you would like it to be.

Using Tab in entry/text fields of elements that were brought into the Print Designer, were not respected when exporting to PDF. This adds the support to respect the spacing once saved as PDFs.

Previously it was not possible to move around the order or Group Templates in the Print Designer. With this update, you can now re-order the templates by clicking and dragging them within the Template Selector of the Print Designer.

Added native support for Fidelity Sans Regular & Bold fonts.

Prior to this change, Founders Grotesk (Regular style) was only working with a fontmap. Now it is available natively.

Budget Rates of non main currencies would not be converted and displayed correctly when shown in the Edit Project window > View Filter > Approved Quote / Budget. This is now fixed.

In the Server Setup > Projects tab > you can now decide whether or not Projects that have the checkbox "Quotation" ticked, should get a number allocated.

If set to No, those Projects won't be allocated a number, and the number column is greyed out.

If set to Yes, they will be allocated a number and behave like the rest of the projects.

If "Quotation" is applied on existing Projects, the Project Number will be greyed out.

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

Added in fw Client app > Toolbox > Settings > Projects Tree: “Booking and Object Override Time’s Set Warnings”, so a user can select if it wants to show these Warnings.
The "Object Override Time’s Set" triangle will appear, if some Objects in the Booking have a different Time In/Out than the Booking's Time In/Out.

This new option "Auto Sort By Booking Start Date" allows to turn the sorting by Booking date on/off in the Projects tree.
When enabled it will respect the "Sort Bookings By Booking Date" when adding more Projects to to the Projects tree in the Long Form.

Finish and Irish Public Holidays have been added to the system and it's now possible to import them.

See more info here:
https://support.farmerswife.com/en/support/solutions/articles/17000050561-how-to-add-or-remove-a-public-holiday

Added new Web Permission under new Api section in Web Profile Manager called Can Punch Clock For Other Users.

The farmerswife user accessing the fwRESTapi needs this permission to "Punch In" and "Punch Out" for other users.

This new Web Permission must be enabled on the Web Permission Profile used by the "User" to use the new POST /punchclock end-point.

fw Server & fw Client must be running on 7.1 Beta 5 (Preview NAB 2024) or later and this new end-point is available in new Swagger version 0.8.15.

Also added a new fw Toolbox Setting in fw Client app > Toolbox > Settings > Hourline > Punch Clock Display As: with these two options:

• "Rectangle"
• "Arrows"

• A connected slim grey rectangle at the top of each Object's Hourline row (legacy behaviour)
• With green arrows pointing to the right for punch IN and pointing to the left for punch OUT (new way).

These new features to be able to create new Object via a Purchase Order (PO) or rent Objects is only possible if the EMT module is licensed.

Two new options will appear in the drop down menu of a Purchase Order, when adding Objects to the PO.

Buy New Objects: When this option is used, an Object Class selector window opens letting you choose an Object Class.
It will be possible to create the corresponding Dispatches with it (WIP) and the new Objects will be created in the database.

Rent Objects: When this option is used, an Object Class selector window opens letting you choose an Object Class.

It will be possible to create the corresponding Dispatches with it (WIP) and set dates when the equipment will arrive (WIP).

Now, a new default field: "Type" has been added to the Purchase Order Edit window. Here you can select different types for the PO and/or use the Setup button to create new Types.

You can set limits for these different Purchase Order (PO) Types and enable Approvers to receive emails for POs awaiting approval based on their specified limit.

In the User Permission Profile > Advanced Module, renamed the Permission from "Can Approve Purchase Orders" to "Can Approve Purchase Orders Up To (main server currency)".

If the User is a Task/Bookings User only, the option to set a limit is greyed out. It is necessary to have Task/Bookings/Rates permission to use this setting.

Here you can set a limit up to which amount a User can approve a Purchase Order.

If you use different Purchase Order types, you can set specific limits for each. Click the drop-down menu next to the PO limit field to add a new line for each PO type and set individual limits accordingly.

PO types to set limits in the main currency for:

• Capex
• Cross Hire
• Freight
• Misc

When you resize and re-arrange the columns, these adjustments will now be saved upon logging out.

The Purchase Order module will now show the newest Purchase Order first whenever doing a search (depending on the Maximum Hits limit) and not the eldest as before.

This requires to upgrade past 7.1 Beta 8 RC 1.
And to use the updated Swagger.json file latest version 0.8.17.

This "swagger.json" version gets published together with the release of v7.1 on this solution article:
https://support.farmerswife.com/en/support/solutions/articles/17000089578-the-farmerswife-server-s-rest-api-for-your-own-3rd-party-integrations

Latest "swagger.json" version v0.8.16 and running on farmerswife v7.1 Beta 7 or later is required for this to work.

This "swagger.json" version gets published together with the release of v7.1 on this solution article:
https://support.farmerswife.com/en/support/solutions/articles/17000089578-the-farmerswife-server-s-rest-api-for-your-own-3rd-party-integrations

Latest "swagger.json" version v0.8.12 and running on farmerswife v7.1 is required for this to work.

This "swagger.json" version gets published together with the release of v7.1 on this solution article:
https://support.farmerswife.com/en/support/solutions/articles/17000089578-the-farmerswife-server-s-rest-api-for-your-own-3rd-party-integrations

For this functionality to be usable, use Swagger.json v0.8.13.

Before, it was only possibly to create (POST), modify (PUT) or delete (DELETE) so call Project Bookings.
Now, Personnel events are also supported by the following end-points:

Create Personnel event:
Use the "POST /event" endpoint with these parameters; the following example is using the DemoDB and the user "Peter" to create a Personnel event type "Sick" (1):

{
"objectType": "Booking",
"object": {
"parentType": "personnel",
"day": "2023-11-28",
"personnelTypeNumber": "1",
"note": "",
"objectID": "id201603101456090000000635",
"days": [
{
"occursOnDay": "2023-11-28"
}
],
"timeIn": "09:00",
"timeOut": "12:00"
}
}

NOTE: For the parameter "personnelTypeNumber" also verify via the fw Client desktop app, which Personnel Type is configured on the farmerswife system you are using; create each one you need by drag&drop on the Hourline and in the main pop-up windows > Personnel Management.

The Personnel Type Numbers are:
0=Shift
1=Sick
2=Vacation
3=Day In Lieu
4=Other
5=Sabbatical
6=Freeday
7=Inactive
20=Unavailable
21=Training
100+=Manual types

Modify Personnel event:
Use the "PUT /event/:id" endpoint with these parameters; the following example is using the DemoDB and the user "Peter":

{
"objectType": "Booking",
"object": {
"parentType": "personnel",
"day": "2023-11-28",
"personnelTypeNumber": "2",
"note": "A new Note was added for Peter and his Vacation is now on 2 days from 12h-18h",
"objectID": "id201603101456090000000635",
"days": [
{
"occursOnDay": "2023-11-28"
},
{
"occursOnDay": "2023-11-29"
}
],
"timeIn": "12:00",
"timeOut": "18:00"
}
}

NOTE: The information added to the "note" Parameter will show up on the Personnel Booking in farmerswife in the "Header" field.

Delete Personnel event:
Use the "DELETE /event/:id" endpoint with these parameters; the following example is using the DemoDB and the user "Peter":

{
"bookingID": "id202311201157550000000290",
"parentType": "personnel",
"objectID": "id201603101456090000000635"
}

IMPORTANT:
The above changes require to use Swagger.json v0.8.13.

Once farmerswife version 7.1 is released you will find this file here:
https://support.farmerswife.com/en/support/solutions/articles/17000089578-the-farmerswife-server-s-rest-api-for-your-own-3rd-party-integrations

As part of this Feature the Swagger documentation was upgraded to OpenApi 3.0. OpenApi 3.0 doesn't support DELETE request with a request body.

For this reason the following DELETE requests have been changed to support url parameters rather than a request body:

DELETE /auth/token -> Just leave body blank

DELETE event/{id} -> Booking ID is now included in the path. Also parentType and objectID url parameters can be be included when deleting Personnel events.

DELETE project/{projectID} -> Project ID is now included in the path. Also deleteBookings url parameter can be included.

All the above are backwards compatible. So you can still send a DELETE request the old way, with a request body.

In the PUT /event/{id} and POST /event endpoints you can now select between Project Booking Example and Personnel Event Example.

This requires to upgrade past 7.1 Release.
And you need to use the updated Swagger.json file latest version 0.8.19.

This "swagger.json" version gets published together with the release of v7.1 on this solution article:
https://support.farmerswife.com/en/support/solutions/articles/17000089578-the-farmerswife-server-s-rest-api-for-your-own-3rd-party-integrations

These fields are now available on the PUT /contact:id endpoint, now the same as on POST /contact:

"contactFirstName": "<string>",
"contactLastName": "<string>",
"contactActive": "<boolean>",
"contactTitle": "<string>",
"contactEmail": "<string>",
"contactTelHome": "<string>",
"contactTelMobile": "<string>",
"contactTelWork": "<string>",
"contactNote": "<string>",
"contactOther": "<string>",
"contactIsResource": "<boolean>",
"contactIsClient": "<boolean>",
"companyId": "<string>",
"companyName": "<string>",
"companyWebsite": "<string>",
"companyFax": "<string>",
"companyAddress": "<string>",
"companyDivisionId": "<string>",
"resourceUserName": "<string>",
"resourceBuyRate": "<int>",
"resourceSellRate": "<int>",
"resourceDaybased": "<boolean>",
"customs":

Added support for the fwRESTapi, that if a Project has a Project Custom Field called e.g. "123456" and it contains the info "abcdef", if a Booking on this Project also has a Booking Custom Field called "123456" and via the fwRESTapi's GET /event/:id endpoint this new parameter “mergeInMatchingProjectCustomValues" with Value=1 gets passed to the system, the resulting Project Booking will contain the info from the Project Custom Field "abcdef".

On the actual Booking the Custom Field "123456" remains without this info.

Previously, if there was a string of numbers in a text field that were being separated by a period ".", this would be parsed via the API as a decimal number. For example, a field with the value "06.2024" to signify date, would be parsed as a number and not text.

This is now fixed to be parsed correctly.

Before, when updating "note" fields on a project in FW via the API, the data contained in fields "contact" and "email" was deleted. Now that bug has been fixed, "contact" and "email" keeps previous data.

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

If you are using Multiple Currencies and have set an Object to a specific Rate that is less than its booked time with the option ” To Invoice: Fixed Amount”, those Rates were incorrectly not kept when using Multiple Currencies. This is now fixed.

If you are using Multiple Currencies and have set an Object to a specific Rate that is less than its booked time with the option ” To Invoice: Fixed Amount”, those Rates were incorrectly not kept when using Multiple Currencies. This is now fixed.

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

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

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

When a multiple day request was approved from inside the request window, it would wrongly approve only one day.

With this fix the behaviour is consistent across the system. When a multiple day request is approved/declined/booked to a project or personnel event, the user is prompted with a popup and can decide if all days or just one day should be approved.

It's now possible to send Requests to multiple users or to a Group consisting of many users or to ALL users, who have Permission to receive the Requests.

To be able to send Requests, the user needs to have "Can Create Requests" enabled in their Web Permission Profile.
Groups that can Receive Requests are created in the Object Manager and need to have "Receive requests” enabled.

To be able to Accept Requests, Advanced Users need to have „Receive Requests” enabled in their Permission Profile.

The "Approvers" are added in a separate tab in the Request window. At least one Approver needs to be selected, before the Request can be submitted. Users can Approve or Decline the Requests.

If the Request is sent to multiple users, the Request Status will change to:

• Approved - as soon as all approvers approve.
• Declined - if at least one approver declines.
• Pending - if at least one approver won’t approve or decline.

It's now possible to set the maximum Approval Time for incoming Requests. When the time is exceeded, the Approver and Requestor will get the Notification on "Requests Pending To Be Approved".

This can be enabled in fw Client > Toolbox > Settings > Server Setup > "Requests" section:
"Pending Requests Reminder (Hours)" to here set a hour number time value.
When the Request is not approved within the selected time, the Notification will be sent to both: Requestor and Approver(s).

The Email notification is:
"Request has been pending for more than X hours. This request was created on <Date & Time>."

Users are now able to Cancel the Requests.
When a Request is Cancelled, the "Approver" is notified by email.
Cancelled Requests disappear from the "Requestor's" timeline and from the Approver's Pending Requests List.

This feature applies to the "user approval workflow", where the user needs to Accept or Decline every newly created Booking.

With this latest development it's possible to enable a new Mandatory Note on declining booking.
This gets turned on in the fw Client app > main module bar "Object Manager > on a user's Modify User Window > Web Profile Manager under Events > Objects > His Own Object > "Mandatory Note When Declining Bookings".

If "Mandatory Note When Declining Bookings" is ticked, the user will be prompted to add a Note on declining a Booking.
This Note is included in the Global Notifications & Project Notifications "On Booking Declined By User".
It will also be visible in the Booking History yellow pop-up, when hoovering with the mouse over the specific Booking.

See more info here:
https://support.farmerswife.com/support/solutions/articles/17000052019-accept-decline-booking-proposal

This new feature allows to specify the maximum approval time for urgent requests.

The new setting to specify the maximum approval time limit for urgent requests has been added in the fw Client app > Toolbox > Settings > Server Setup > "Requests" section > "Urgent Approval Time Limit" ... enter here an hour number as the time limit, default is set to "8".

Web Users can change that value per request in the Web Client. If the value equals or is lower than the number specified in the Toolbox, then the request will be automatically marked as urgent.

Urgent requests are displayed at the top in the fw Client app > Toolbox > Requests tab.
These "urgent" request are also displayed in "bold".

The Notification on newly created Requests also includes the information that "This Request is urgent".

See more info here:
https://support.farmerswife.com/support/solutions/articles/17000136443-request-workflow-what-s-new-in-7-1

It's now possible to set "Global Working Hours" for approving Requests.
This can be configured in fw Client > Toolbox Settings > Server Setup > Request section: "Working Hours For Sending Requests" with two time selectors for start time and end time.

If the Request is created outside specified Working Hours, Web Users creating Requests will be prompted with a message: "This request has been submitted outside of working hours and will be processed as soon as possible. Do you wish to proceed?"
When clicking NO, the Request won't be created, when clicking YES - the Request gets created as usual.

In the Web Profile Manager under User > Objects > His Own Objects there is a new setting, that allows Web Users (WU) to modify approved requests (which was not possible before).

For this to work this new Web Permission "User Can Modify Approved Requests" must be enabled.
Modifying approved requests will change their status to "Pending" and will be sent back again for approval.

The Requestor is presented with a pop-up message informing that the Request is already approved and editing it means re-submitting for approval.

The Approver receives an email notification informing that a specific user has re-submitted their Request for Approval.

See also more info here:
https://support.farmerswife.com/support/solutions/articles/17000136443-request-workflow-what-s-new-in-7-1

On the new Request feature, if you clicked the green plus to add an approver, and then hit enter/return on the keyboard, this would cause the client app to crash.

This fix now prevents that happening.

Since v7.1 it's possible to create Bookings directly in the Request tab in the Toolbox and this way link them to a specific Request.

However, when the Request's Status was manually changed from Approved to Pending, involved Bookings were wrongly unlinked from the Request.

This bug is now fixed and when changing the Request Status from Approved > Pending, the user is now prompted with a pop up, asking:
"Do You Want To Keep All Bookings And Personnel Events Linked To This Request?"

There are 3 options to choose from:
Cancel - Prevents the user from changing the Status.
No - Unlinks the Bookings or Personnel events linked to the Request.
Yes - Keeps all Bookings and Personnel events linked to the Request.

When accepting Requests from fw Client app > Toolbox > Request tab, using:

• Accept And Book To Project
• Accept And Book To Personnel

If the request was sent to All and approved from Toolbox > Request Tab, it would incorrectly remain pending.
Now this bug is fixed.

In the scenario where:
1. "Set All Day When Creating Event" was enabled and
2. Personnel Bookings were created from Requests indicating specific time (e.g. 9h-15h)
3. the User confirmed to use the time from the request (e.g. 9h-15h)
... then the Personnel Booking would be wrongly created as a "All Day" event anyway.

Now this bug is fixed and Request time is respected again.

When an Advanced User with Permission to "Approve Requests" was changed to a Web User, this user's Name would wrongly not disappear from the "Approvers" list and this user could wrongly still be set, when submitting Requests.
Now this bug is fixed. As soon as the user loses permissions to approve requests, it is correctly removed from the list.

This requires iOS farmerswife app v5.0.869 or later to be available on the App Store.

iOS fw app users can now:
-Cancel Request.
-Add multiple Users/Groups.
-Change Max. Approval Time.
-Edit Approved Requests.

See more info here: https://support.farmerswife.com/support/solutions/articles/17000136443-request-workflow-what-s-new-in-7-1.

In fw Client app > Toolbox > Settings > Web Share Settings, you can define time frames that will be applied to Web User Profiles, restricting them to see/create/change Requests, Bookings, or Timereports in certain periods only (= 3 different Static Timeframes are available for this).

Even though a Web User had a bookable time frame defined, he was able to delete or cancel a Request outside that time frame.

This is now fixed and the users are no longer able to delete or cancel Requests outside their bookable time frames, and they will get a warning message upon trying.

In 7.1 when opening an existing Request, editing and saving it, the "All" Group would wrongly receive a notification that they were added to a request.

This is now fixed and they no longer receive that notification.

Go to: fw Client app > Toolbox > Settings > Web Share Settings: "External Calendars / Schedule Changes Email Sendout ..." > "Include Header Of Personnel Booking In Header" to enable this new setting.

Also for this new setting "Include Header Of Personnel Booking In Header" to work correctly the Setting "Send Schedule Changes Email Even When Only The Event Header Was Changed" must be enabled.

Now anything that is added to the Header of a Personnel Booking will trigger a Schedule Changes Email.

This new variable controls how the fw server app behaves during the nightly auto "Forced Shutdown" > Mode: Restart (1) or Quit (0).
If the value is 0, it will just quit and won't restart.
If the value is 1, it will restart.

This setting is used if an external 3rd party launches the fw Server app, if it's not running.

This requires the optional "server.cfg" file to be installed on fw Server app-side.
See more info here:
https://support.farmerswife.com/en/support/solutions/articles/17000059642-setup-and-work-with-a-separate-farmerswife-server

If you did certain actions as: Reapplying a saved Class Booking Template in the Long Form with many Object in it and the timereporting was enabled in Toolbox, this could lead to a very long server blocking wait for users. This is now fixed.

Before when clicking on an Object in the Booking Involved window, the Objects menu popup took 2 seconds to show, now it shows instantly.

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

These two new Permissions in the Web Permission Profile under Timereports > Allow Editing Timereports have been added:

• "Mandatory Note For Object When Reporting (Always)"
• "Mandatory Note For Object When When Reporting Over Booked Time"

You can "split" a multi-day booking in two or more bookings by highlighting the day or days (in Hourline click at date on top, or in Long Form select the days) you want the booking to be split on > click on booking menu > split > confirm.

Result is two or more bookings - one from the start of the original booking to the day before the highlighted day, the other from the highlighted day to the end of the booking (booking name, status, custom fields, involved objects, etc - all remain identical for both bookings).

When you had some Extras timereported on certain days, after splitting the booking these extras would be copied to the other days. This is now fixed, so if Extras have been added to specific days of the Time Report the Extras will "stick" to that day.

Now the Mandatory Note pop-up will state: "Please add the note for <user Full Name>."

The new "Timezone for Divisions" development requires the Division feature to be licensed (paid option) on your farmerswife.

In the farmerswife Server Setup > General tab you can set a timezone per Division. For instance if one of your Divisions was "USA" you could then choose the specific timezone for that region.

Once you have added the timezones to the specific Division within the farmerswife Server Setup, you need to enable this in the farmerswife Client desktop app > Toolbox > Settings > Server Setup > "Enable Timezones" button.

When this setting is activated, it will show a drop-down selector box at the top of the Long Form view. The drop-down box will show all the different Divisions that have been setup on the fw Server. Switching between these drop down Divisions will impact a few different things, but most importantly it will show your Bookings in that timezone. This will show up in the Long Form and Hourline timeline views.

Having this drop-down box selected to the appropriate Division will automatically place any Bookings you make in that timezone. As standard, each Booking will belong to that timezone from what is selected in the Long Form drop down menu.
This can be can be changed on Booking level. There is a similar drop-down on each Modify Booking window that shows which timezone it is booked in. Simply by selecting a different Division on the Booking will alter when this event will take place. If you switch one Booking from one timezone to another, it will be reflected in the Long Form and Hourline.

In the Toolbox tab for Classes, it's now possible to filter Classes by their associated Division with the newly added Division filter.

In the Deleted Bookings tab of the Toolbox, the "Deleted Date" column now shows the time along with the date. It previously only showed the date.

farmerswife on Windows has been sensitive on this topic in the past and there have been many attempts to improve this.

The problem here was, that on Windows when resizing the Toolbox it would wrongly remain empty (blue). And when you then e.g. used the "Refresh" button the fw Client desktop app would crash.

Now when you drag the resize too quickly the Toolbox will turn blue and then it will look like it’s stuck. But if you move the mouse you’ll see that it’s being resized.
And then you will have to click again to stop resizing.

In fw Client app > Toolbox > Settings when searching, some Setting's header names were overlapping each other.
Now this bug is fixed.

Corrected the language on the Toolbox setting.

Toolbox Search in the Project Tab was building a string of: container name, project name, project number, project client (and a sublist with internal ID), all custom values, project note, and all binder data with IDs as well.

The search is now changed and is limited generally to a user's visible fields within the Project, excluding all IDs, which makes it more precise when returning search results.

When you copy-pasted an email address into the Email field in the Edit User window, it would keep any surrounding whitespace characters, such as newlines. While the newline character could not be seen, it was there and could cause problems.

See also more info about "Password Policies" here: https://support.farmerswife.com/en/support/solutions/articles/17000073097-setting-up-password-policies

This is change is for the packaged web technologies in the farmerswife Server app to the latest versions for a improved security position and allows to enable latest transport layer encryption.
Changes in this version, Previous => New:
GWT version: 2.9 => 2.10
Java 8 => 17
Jetty 9 => 12

It also changes the deployed location of various Jetty files including logs, setup initialisation and certificates. These are now located in Users Library "Application Support" folder on macOS and in Users "AppData > Roaming > Farmers WIFE Server" folder.

A check is included to confirm that Java 17 as the minimum supported version is installed, before any upgrade to this version can be done. If the check fails, the following error is returned "Web Client: Expected JRE 17 or newer."

IMPORTANT for any customer who has locally SSLed the Jetty web server: Ensure you are registered on our Knowledgebase and then use this new Solution Article to change you local SSLing after the upgrade to v7.1:
https://support.farmerswife.com/en/support/solutions/articles/17000138101-how-to-ssl-farmerswife-since-v7-1-using-your-own-certificates

It is possible to set "Booking Colors" for the Web Client via fw Client app > Toolbox > Settings tab > Web Share Settings > Booking Colors.
Once enabled, the here selected colors will show in the Web Client.
In the Month view for a better viewing experience the Bookings are now shown in a box, the color matching the colors selected in the setting.
Before there were no colored boxed, but the Name of the Project was shown in the color selected in the Toolbox.

Changed error message in Web Client when trying to edit Ad-Hoc Time Report by drag and drop

It now reads: "Cannot Change Time In/Out For Ad-Hoc Time Report here. Please Edit From Within The Time Report."

Fixed a Web Client - Level 2 vulnerability by disabling the "autocomplete attr" for the Login window Password field.

If a web user was opening a time report that was outside his timereportable time frame (this can be configured in the Toolbox > Settings > Web Share Settings), and he had the permission to timereport into the next day (Web Permission Profile), then the "Out time into next day" checkbox was wrongly ticked. This is now fixed.

Fixed a bug on the Note field in the Web Client, that was stopping HTTP URLs from being a clickable link for a user. This was previously working on 6.8 SP3, but stopped working in 7.0 SP2. Now it's fixed again.

When Timereporting via the Web Client and there is a Booking for the same Object for the same Project on the next day and starting at farmerswife Server app Start Time, then the Booking on the second day would wrongly get deleted.
This Bug is now fixed.

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

In 7.1 the new setting "Mandatory Note For Object When Reporting (Always) was added.
As a result the old setting "Mandatory Note For Object When Reporting Over Booked Time" would depend on it, and if "Always" was selected, the "Over Booked Time" setting should be greyed out. This is now fixed.
These new Settings and dependencies would not allow to upgrade the database properly.
Now the DB Upgrade is fixed.

See also more info here: https://support.farmerswife.com/en/support/solutions/articles/17000097532-2-toolbox-dispatch-module-settings-emt-dispatch-settings-and-configuration

See more info here: https://support.farmerswife.com/en/support/solutions/articles/17000097532-2-toolbox-dispatch-module-settings-emt-dispatch-settings-and-configuration

This is implemented on iOS farmerswife app v5.0.868; available on the App Store since 6th July 2023.

You can now book any bookable Object (in line with the fw user Permissions) through iOS fw app, Web Client & Mobile Web Client.

However if you were booking an Object which has Accessories or Object Class Accessories, those Accessories would not be booked.
This is now supported and when you book an Object through the iOS fw app, Web Client & Mobile Web Client the Object's Accessories (and Accessories of Accessories) are booked as well.

See also this Solution Article for me info:
https://support.farmerswife.com/en/support/solutions/articles/17000071968-groups-vs-accessories