Any fw Client app on Mac running BELOW macOS Mojave 10.14 can no longer be used!
You have to upgrade the Mac to macOS Mojave or later in order to use the latest fw Client desktop app on Mac.

Go to: fw Client app > min module bar "Projects" this is the "Advanced Project Search".

Use "Edit View" in the sub-menu to add this new "Cancelled Note" column to the search results.

Go to: fw Client app > main module bar "Projects" this is the "Advanced Project Search".

Use "Edit View" in the sub-menu to add this new "Project Currency" column to the search results.

You can now also filter by Container, Binders and Projects & Binders in the "Filter From" in the main module bar > Projects (a.k.a. Advanced Project Search).

For more details see: https://support.farmerswife.com/en/support/solutions/articles/17000026133-advanced-project-search-projects-tab-

To use these new columns for "Binder" and "Sub-Binder" in the search results in main module bar > Projects (a.k.a. Advanced Project Search) add them through Menu > Edit View.

Go to: fw Client app > main module bar "Projects", this is the "Advanced Project Search".

Use "Edit View" in the sub-menu to add these new "Container Custom Fields" (shown as "Container / Custom: NameOfContainerCF) columns to the search results.

To Batch Print Bookings from the Advanced Project Search (APS, or main module bar Projects) you can assign a Template to a Bookings name and print multiple Bookings in one go onto a PDF.

More information can be found here: https://support.farmerswife.com/en/support/solutions/articles/17000052562-batch-print-bookings

There was a fw Client app crash, when restoring a Project from Archived, as you select to re-archive again. This only happens in the Advanced Project Search (main module bar > Projects). The same operation could still be done via Toolbox > Projects without a problem. This bug is now fixed.

Removed the "opposite direction" options in the "Filter From" drop-down menu, e.g. "Bookings To Projects" and "Projects To Bookings" are now gone.
Also fixed the Search result counters so that, for example, when using Filter From: Projects & Bookings, the Bookings counter will no longer include the Project count as well.
It will now show in the bottom left corner of the search result:
*Projects: Projects Search Amount / Amount of all Projects | Bookings: Bookings Search Amount*

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

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

This bug was introduced when "thread support" was implemented for the Azure AD connector. The fix now will skip the use of Threads when checking credentials, which will then prevent the fw Server app from freezing when users log-in at the same time via the iOS fw app.

The optional "server.cfg" file (located in the fw Server app's "system" folder if used) contains "variables" from the fw Server apps General tab.
Now, it contains this new "BACKUP_CYCLES" which is "synced" to the setting in fw Server app > Setup > General tab > "Backups".
The available values match with the options on the "Backups" setting:
25, 50, 75, 100, 300, Auto

IMPORTANT:
The "Backups" (server.cfg var "BACKUP_CYCLES") functionality is designed to work together with the setting "Backup Every" (server.cfg var: BACKUP_TIME). And together they are designed to "keep" 24h of "DB Save" "DB snapshot" files. Where then the "Full Backups" process picks-up the backup-process on a once per 24 hour cycle.

The DemoDB e.g. uses this configuration:
Backup Every: 15 min.
Backups: 100

The above DemoDB example looks like this on the server.cfg:
BACKUP_TIME 900000
BACKUP_CYCLES 100

A "Backups" configuration can also look like this, if a external service makes copies of the "backups" folder every 2 hours. Only use this configuration, if the "DB Save" process takes lees than 5 seconds on your farmerswife system!:
Backup Every: 5 min.
Backups: 25

In the server.cfg this will look like this:
BACKUP_TIME 300000
BACKUP_CYCLES 25

These two new Settings are located in fw Client app > Toolbox > Settings > Booking Defaults > new "When Applying Booking Template" section:
1) "Reset "Use Time Reporting" to Toolbox Default": Yes/No (default)
2) "Reset "Check Point Status" to Toolbox Default": Yes/No (default)

When building Booking/Binder Templates, please be aware, that in the future you might be using the Toolbox Setting to "Never Select Weekends Or Public Holidays".

So when you create your Binders and Bookings and save them as Templates for later use, be aware of what you are doing.
Is the Toolbox Setting to "Never Select Weekends Or Public Holidays" enabled or not?

Are you only creating "single day Booking/Binder Templates"? Then only make sure, that you're not booking them accross weekends and public holidays.

Or are you creating a complex Binder and Booking structure over multiple days, which might include weekends and public holidays? If you need to do this, then ensure that "Never Select Weekends Or Public Holidays" is disabled!

When you use Binder/Booking Templates, farmerswife looks at the amount of working days in between Bookings in order to create them accordingly.

If you select multiple dates and then split a multiple-day Booking with more than 31 days, the split parts would result in a Conflict state. This is now fixed.

Object Classes could already be added to:
- Default Objects, making the Class itself selectable, or
- Default Object Classes, making the Class Members selectable.

But when importing Object Classes from .CSV in the Object Manager, the "Budget Accounts" column always added them to the "Default Object Classes" list. There was no way to get them added to "Default Objects".

Now this is supported, by splitting the "Budget Accounts" column into two separate columns:
- "Budget Accounts (Object)"
- "Budget Accounts (Object Class)"
So depending on which column you enter the account number into, it will pick either Default Objects or Default Object Classes.

On Linux in fw Server > Setup > Financial tab > Budget Settings you can now also move Budget Categories up/down, even if there are Sub-Accounts.

There was a fw Client app crash if you used the Edit View button to add the "Note" column, and then either:
- Selected a parent Budget that has child Budgets, or
- Selected multiple Budgets, or
- Re-ordered the Note column so it was before "Description".

In fw Client app > main module bar Object Manager, you can import Objects from a CSV file, with Budget Accounts for which the Objects will be part of the "Default Objects/Classes".
This worked, except that there was a delay after importing, during which the Objects weren't presented as Default Objects.
After a moment, it would refresh and take the new Objects into account.
This is now fixed and it will work immediately after the import.

In the Edit Budget Operator window, there is now a new "Tax" checkbox, by default on.
If it's disabled, the Sell output from the Budget Operator won't be included when calculating Tax. This affects the following places:
- The overview in the Edit Project window
- Project Reports
- Invoicing
- Financial Reports

When you link Budgets to Binders, and also link Actuals to Binders, the list of Actuals will automatically suggest any matching Budgets for when you attach the Actuals.
However, when a Budget was linked to a Binder but the Actual was linked to a Sub Binder within that Binder, it would previously not see it as a match. That is now changed, so it falls back on the Binder if there is no match using the Sub Binder.

The fw Server app's "server.cfg" file is an optional feature, which allows to pre-set configuration changes on a file, which is then used when the fw Server app gets launched. If used, then the "server.cfg" file must be located within the fw Server's "system" folder. More info also here: https://support.farmerswife.com/en/support/solutions/articles/17000059642-setup-and-work-with-a-separate-farmerswife-server-

The following Cirkus Connector v2 settings can now be supplied through the optional "server.cfg":
- CRK_ENABLED: Boolean. Whether or not the Cirkus v2 integration is enabled.
- CRK_API_KEY: String. A secret key used to communicate with Cirkus on behalf of a Cirkus User. Note that this key is never written out to the server.cfg unless it's first provided through server.cfg. This is to protect the secret from being extracted.
- CRK_ORG_ID: String. The ID of the Cirkus Workspace.
- CRK_URL: String. The URL to Cirkus, e.g. https://cirkus.com.
- CRK_READONLY: Boolean. Can be used to make sure no data is ever written to Cirkus through the v2 integration.
- CRK_BOOKING_SYNC_ENABLED: Boolean. Whether the Bookings integration is enabled.
- CRK_TR_SYNC_ENABLED: Boolean. Whether the Time Reports integration is enabled.

Under fw Client > Toolbox > Settings > Cirkus (v2), there's a new setting called "Sync Bookings With Status". It lets you select one or more Booking Statuses. Only Bookings with any of the selected statuses will be synced from farmerswife to Cirkus.
This can be useful e.g. if you want to wait with "publishing" Preliminary or Planning Bookings until they're confirmed.
If no statuses are selected, it will sync all Bookings regardless of their status.

In fw Client > Toolbox > Projects and in Advanced Project Search (main module bar > Projects), you can now select one or more Projects, right-click and select "Cirkus > Add To Cirkus".
This will open up a dialog where you select which Project Template should be used for the new Cirkus Projects.
If you click OK, the Cirkus Projects will be created.

If there is an error when trying to sync e.g. a time report update on a Booking, the syncer will protect itself against repeated errors by flagging the Booking as having errors and then skips that Booking in future syncs.
Until now there was no way to see that a Booking was flagged that way, or to make it retry the sync after the cause of the error had been fixed.
But now it will show in the Edit Booking window, in the bottom-right corner: There will be a warning icon. Clicking it will clear the errors and let the Booking get synced again.

If a Booking or Personnel Event is synced to Cirkus, it now has a Cirkus icon in the upper-left corner. Clicking it will open the corresponding Cirkus Booking.

The "Sync Mode" option available in fw Server > Setup > General > Cirkus (menu) controls which direction data is synced in, e.g. from farmerswife to Cirkus, from Cirkus to farmerswife or both ways.
Previously the same setting affected Projects, Bookings, Time Reports and Personnel Bookings alike. But now it can be configured separately for each of those types. So you can e.g. sync Bookings from farmerswife to Cirkus, preventing new Bookings coming from Cirkus, but still allow Time Reports from Cirkus.

This new check-box can be found in fw Client app > Toolbox > Settings > Cirkus Sync (v2).
If activated, Users/Roles who are involved in a Booking that is synced to Cirkus, will be added to the Cirkus Project first.

Note that when syncing fw Bookings to Cirkus Tasks, this always happens. The setting only applies when syncing to Cirkus Bookings.

Until now, when you booked an Object Class in farmerswife, the syncer would try to map it to a Resource (using its name) in Cirkus. Now you can change this behaviour, so it tries to map it to a Role instead.

The behaviour can be controlled by a setting called "Map Classes To", in fw Client app > Toolbox > Settings > Cirkus (v2). The default for existing integrations is to continue mapping Classes to Resources. The default for new integrations is to map them to Roles.

Personnel Events in farmerswife can now be synced to Personnel Bookings in Cirkus, and vice versa. It's a full two-way sync just like the Bookings sync.

To try it out:
• In Cirkus, create a Booking Template for the type you want to sync, e.g. "Vacation". Change its "Type" to "Personnel".
• In farmerswife, go to Toolbox > Settings > Cirkus (v2).
• Toggle the check-box "Sync Personnel Bookings".
• Under "Booking Template Mappings", click the "+" button and map farmerswife's "Vacation" type to Cirkus' Booking Template "Vacation". Click OK.
• Try creating a Vacation event on any User who exists in both farmerswife and Cirkus.

Starting from Cirkus 1.84, Cirkus will have similar scheduling capabilities on Tasks as on Bookings. And it's then possible to configure farmerswife to make fw Bookings sync to Cirkus Tasks.
This is done in fw Client app > Toolbox > Settings > Cirkus (v2) > By Default Sync Bookings To: (Cirkus Bookings / Cirkus Tasks).
There is also an additional setting called "Sync To Cirkus Tasks/Bookings" which contains a list of Booking Types (from Booking Defaults > Bookings Names & Customs). Any Booking with those types will be synced to the *other* type compared to "By Default Sync Bookings To". So it's a way to have a default behaviour, but still be able to add exceptions. For example by default sync to Cirkus Bookings, but still add exceptions that will sync to Cirkus Tasks, or vice versa.

When Booking creations, updates and deletions were synced to Cirkus, the Notifications there showed that the Booking was updated by the "integration user". Not by the actual user who did the updating in farmerswife.
Now this is improved, so it shows which user made the change in farmerswife.

The same applies to Personnel Bookings and to Tasks created from Budget Details.

This feature is default off and must be activated through fw Client app > Toolbox > Settings > Cirkus (v2) > Sync Task Bookings.
Note that it won't be available unless Booking Sync is also enabled.

Any Task Bookings created in fw will become a standard Booking in the Cirkus Workspace, just without any Projects attached.
And similarly, any Cirkus Bookings that don't have any Projects attached will become Task Bookings in fw.
As usual, it will still only sync Task Bookings for involved Users where the email matches exactly between Cirkus and farmerswife.

Previously, if an error happened during the sync, e.g. due to incorrect configuration, it would keep trying to sync the Binders to Subprojects forever.
That would result in spammy logs and lost performance on both farmerswife and Cirkus.
Now it will register an error in the Project and stop syncing Binders for that Project until a user manually clears the error inside the Edit Project window.
Note that this will not happen due to network errors - only errors with http status 400-499, so called "client errors".

If a user of the fw client desktop app has a Booking open (showing the Edit Booking window), that Booking is considered "locked". Previously this wasn't something that prevented the Booking from being synced to Cirkus. But now the syncer will wait, until the Booking is closed before it syncs it.
One benefit of this is, that if you use the setting "Auto Popup Booking Window On New Booking", you can fully fill out the details - e.g. Name, Type and Custom Fields - on new Bookings before they are synced to Cirkus.

If you created or modified a Personnel Event on a User that doesn't have a matching Cirkus User in the Workspace, it caused a repeating log statement like:
"[Cirkus Sync]: pm event id202208191238500000001506 has no syncable involved users/objects - won't be created in Cirkus"
Now such Personnel Events will be ignored by the syncer.

Sometimes when you reported on only some days of a Booking in farmerswife, it would incorrectly report zero hours on the remaining Objects and days.
This is now fixed.

In fw Client app > Toolbox > Settings > Binder / Marker Defaults, you can set up a default Binder without any color.
When such a Binder was synced to Cirkus, it resulted in a sync error: unknown color name “”
This bug is now fixed.

When you created a Personnel Booking in Cirkus and it synced back to farmerswife, it would also cause both a Personnel Event and a Task Booking to be created in farmerswife.
This bug was introduced with the Task Bookings sync in farmerswife 7.0 beta 3.

When you had a Task Template Mapping that was configured to get the Object from a Custom Field, and you used that Task Template for creating a Task directly from a Budget Detail, it could cause crashes.

If a Booking or Personnel Booking had been synced to/from Cirkus, opening that item on Windows would cause a crash.

If you enabled the older Cirkus Sync v1 integration, and then started the fw server app with a license that didn't have Cirkus Sync licensed, there was a crash.

Sometimes a part of the Cirkus integration could cause a crash inside the Edit Project window.
This is now fixed.

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

Sometimes the syncing of Projects would keep failing with the following error in the log.txt:
[Cirkus Sync Extra Info]: key "value" not known in dictionary
That bug is now fixed.

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

If the clock time was off on the farmerswife Server host machjne, it could prevent some changes from being synced from Cirkus to farmerswife.

When you created an All-Day Personnel Booking in Cirkus and it was synced to farmerswife, the resulting Personnel Event wrongly didn't have the "All Day" check-box checked.
This bug is now fixed.

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

Previously, the "sync user" (the one who owns the API Key) was considered the creator of the Projects in Cirkus.
Now it will instead pick the user who activated the sync on the farmerswife Project, as long as that user exists in the Cirkus Workspace.
Cirkus also adds the creator as a member in the Project, so that also helps with giving initial access.

The "integration user", whose Cirkus API Key is used to read and write data to Cirkus, must have a verified email address (and be Workspace Administrator).
Otherwise it will not be able to self-join synced Projects that it creates on behalf of other Users. So it would create the Projects but not be able to update them afterwards.
To inform about this potential issue, the "Test Connection" button (in fw Client app > Toolbox > Settings > Cirkus (v2)) now shows the unverified email addresses if there are any.

Previously, if you removed or canceled a Cirkus Task that was synced to a Project Object in farmerswife, nothing would happen.
Now it will delete the Project Object. If you later restore/reinstate the Task again, it will create a new Project Object for it.

In farmerswife you can report time on each Object in a Booking. In Cirkus you can only report on Users at the moment.
This difference caused the problem that non-user Objects would lack time reports.
So now when the syncer finds time reports on Cirkus it will propagate any time reports made on Users to the other Objects on the same day in farmerswife.

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

Sometimes there was an error causing an fw Client app crash (expected boolean value but got "") when trying to create/move Bookings on certain days.
A fw Server app restart would fix the issue temporarily, but then it could come back.

Go to fw Client > Toolbox > Settings > Server Setup > "Default Maintenance Causes Conflict" with options "Yes" (default)/ "No".

When a Booking over 31 days was split into two, the Booking before the split day was wrongly getting set to "Preliminary" (in conflict) Status. Now the bug is fixed.

This is only available for Project Custom Fields type Date or Object Custom Fields type Date.
When clicking on the Alarm icon this will open the Modify Object window, or the Edit Project window.

See more info here: https://support.farmerswife.com/support/solutions/articles/17000050161-alarms-on-custom-fields-date-widgets

If Bookings or other events contained certain characters such as '{' or '}' in their Name or Note fields, it could make the "Daily Automated Schedule Sendout" fail and cause a fw Server app crash.

To use this setting, go to: fw Client app > Toolbox > Settings > Dispatch Module > "Auto Check Out Objects That Are In When Being Checked In" Yes/No (default).

When activating this Setting, if a Check-In is created without a corresponding/previous Check-Out, an automatic Check-Out is created with Dispatch Status: "Returned". This auto Check Out will not have any Name set.

This setting is NOT enabled by default.

When using MacKiosk, this will cause a "missing check-out update" for Missing/Broken items.

Use case: a user takes an item, but due to e.g. time-constraints no Check Out gets created, and then returns the item and now actually does create a Check In.

In the Dispatch module's main search if you use the option "Show Items", it will show all items inside of a Dispatch with their corresponding "Status" info.
However, you could not click on the column header to sort by this option. Now you can.
And if you export this search result via "Open As Spreadsheet" to a .CSV file, you will see now the "Status" info in its own column like this:

none = If the item doesn't have any Status set (not scanned at all).
track_in = If the item is checked In.
track_out = If the items is checked Out.
prel = If the item has been set to "Status= Ignore: Yes", or if it is "Overdue".

You might want to consider to refine your search criteria or used filters.

Latest in early January 2023 Microsoft will stop supporting "basic" authentication for MS Exchange 365!
With this new Microsoft Exchange Setting > *"Use MS Azure AD Auth"* enabled, will keep the MS Exchange integration in farmerswife working, for users own events to be populated on their Exchange calendars.

When enabling this option in fw Server app > Setup > Users > Microsoft Exchange Settings > *"Use MS Azure AD Auth"* by setting it from "No" to "Yes", farmerswife (fw) will use EWS (Exchange Web Services) by using a token from the existing "Microsoft Azure Active Directory Connector" settings. But there is no need to keep the Azure AD integration enabled after it's been configured, and once the Exchange Integration is tested and works.

The "App Registration" on the MS Azure Portal is required, including setting the correct "API Permissions".
Further required settings from Azure AD are: App Client ID, App Secret Key, Oauth 2.0 (v1) Token Endpoint).

The Exchange requirement: *ApplicationImpersonation* must be enabled. This requires "Organization Customization" to be enabled on Exchange.
In case of getting an error from Microsoft Exchange Online due to "Enable Organization Customization" is off, you can install PowerShell with the ExchangeOnline module enabled and run: Enable-OrganizationCustomization.

*See the updated and detailed configuration instructions here:*
https://support.farmerswife.com/en/support/solutions/articles/17000052459-microsoft-exchange-integration

Both the items under each Menu Group and the Menu Groups themselves weren't always sorted alphabetically. Now they are.

When an Object had "Force Unit Name" set, the Financial Report showed it as e.g. "1 Sessions", using the "plural form" even if the quantity was 1.
Now it supports displaying in both singular and plural forms.

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

When selecting an Object Class Custom Field as a Grouping you would get "?" in the Group column in the Financial Report window and then "N/A" in the "Elements / Options:" section in the Print Designer.

Now the actual Object Class Custom Field Name is displayed both in the Financial Report window and the Print Designer.

When an Object had "Force Unit Name" set, setting its unit to "Fixed" (e.g. in Budgeting) would have no effect in the Financial Report.
This is now fixed, by making "Fixed" take priority over the Force Unit Name.

If an AdHoc Time Report didn't have any times in the time report's "To Invoice" column, the Financial Report would show "(N/A)" for the "Time In / Out" field, instead of the Adhoc TR's actual time.
This bug is now fixed.

When you reported on e.g. an Invoice with Objects that weren't coming from any Budget, and the Financial Report was grouping by Budget, it could crash.
The bug was introduced in farmerswife 6.5 beta 2 (rev 17883).

The fw Client desktop app can now be run in Dark Mode.

By default changing of the mode on clients is disabled on the server.
There is a server setting to control the behaviour on all clients.

fw Server > Setup > General > Color Theme Settings > Allow Changing Of Color Theme.
To allow clients to use the feature change from Disabled to Enabled.

After the feature is Enabled, clients will need to reconnect to be able to switch the mode.

Clients can control which theme their client users in Toolbox > Settings > Display > and use the new "Color Theme" option either in "Light" or "Dark" or "Auto".

If Auto is selected the client will follow the system setting (on macOS > System Preferences > General > Appearance )

Windows:
Toolbox > Settings > Display > Color Theme > options "Dark" or "Light"
Restart required

If the server supports changing the mode on clients the following changes will also be visible across the application:
• All colour pickers that affect background colors (e.g. Booking colors on the Hourline, Long Form etc) have now changed to allow you to pick two colours, a Light Mode and a Dark Mode color.
• Colours prior to applying this upgrade will have a dark colour automatically set, which can be edited.
• At the time of you picking a new colour for Bookings, Projects etc, you can define either the dark or light colour and the alternative colour will be suggested, but you can change this suggestion.
• Web client will always show light colours.

Added "Use Binder Color" check-box in fw Client app > Toolbox > Settings "Hourline" and "Objects Tree" and "Web Share Settings".

By ticking each option, the Binder color will show in the Hourline, the Objects Tree and the Web Client.

Go to the fw Client app > Login window > Setup > Language and here select the new option "Arabic".
This is sorted with latest additions at the end of the list.

EOL=End Of Life.

On Mac, when logged in with the fw Client desktop app, go to the top left corner and click on "farmerswife" and select "About".
On Windows, when logged in with the fw Client desktop app, go to the top left corner and click on "Menu" and select "About".

Example from a 7.0 Beta 13 > "About" window contains this info:
Version: farmerswife 7.0 Beta 13
SevenZeroBeta-GesichtserfrischungMitDunkel
Build: 7.0.13-0-gbe7cd1608
farmerswife.com

Example from a 7.0 Beta nightly build version > "About" window contains this info:
Version: farmerswife 7.0 (Nightly Build - 21
SevenZeroBeta-GesichtserfrischungMitDunkel
Build: 7.0.12-17-gc3417380a
farmerswife.com

This info is very helpful for farmerswife support, when assisting with any kinds of issues.

HL = Hourline, LF = Long Form

If you have the following Toolbox > Settings > Hourline:
- Always Force Preliminary Colour When Preliminary
- Always Force Planning Colour When Planning
- Use Container / Project / Client Colours
- Use Booking Name Colour
- User Involved User Colour
- User First Booked Object Activity Colour
turned OFF, then the Bookings should show in the Global Status Colour.
This was not working anymore and all bookings would show in their Substatus Colour.
That was now fixed so they show in their corresponding Global Status Colour again.

Go to the Invoice Creator or Invoice Manager and open any Invoice; you are then looking at the "Invoice Editor" window, spanning the size of the fw Client desktop app.

If you had a Group Object with a few Members and added a Fixed Price per Day, when booking the Group Object it would have the Fixed Rate but the Group Members would have 0 Rate. However when invoicing the Group, all Members would have their own rate applied. This is now fixed and the Members will also be invoiced with the 0 Rate.

Budget Details can have a Multiplier value that is used together with the Quantity to produce an effective quantity. E.g. 4 x 2 days = 8 days.
But when such Budget Details were invoiced, the Invoice Report would only display the effective quantity (8 days). Now there are two more fields added to the Rows section of the report:
- Quantity Multiplier
- Quantity Before Multiplier

Before, Multi Label Printing on the 64bit fw Client desktop apps on Mac and Windows was not usable. The out-put was not one page containing all the different selected single Labels, but instead wrongly created a page for each label. And it was simply not possible to define the size of the "page" to be printed on.
Both of these issues are now fixed, mainly by now being able to select page size in points!
Note: The page size "A4" (595 x 842 points) is set by default for existing Multi Label Templates.
Further explanation on multi-label printing can be found here: https://support.farmerswife.com/en/support/solutions/articles/17000026064-multi-label-printing

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

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

Labour Rules, including the PM User Report, intentionally ignores all Bookings (etc.) prior to the Employment Date.
But there was an issue where, if you moved the Employment Date to a later date, some Bookings that had already been reported on were *not* ignored, and were even duplicated (in the report) every time you ran the report.
This bug is now fixed.

When calculating the totals for Vacation, Sabbatical, etc., sometimes there was a crash due to a bug handling previous Closing Point data.

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

Requires MacKiosk v2.6.19 or later and farmerswife to be running on v7.0 Beta 3 or later.

If a User has a Pending Dispatch in the Mac Kiosk, (s)he can now start verifying part of the items and use the new "Save" button in the top right corner.
The scanned items will show as "Verified" in farmerswife and the user can continue to scan on a different Mac Kiosk station to finalize the scan. The "Done Scanning" option will only be available to click, if ALL items on the Pending Dispatch have been scanned (verified).

Requires to use MacKiosk v2.6.18 or later.

MacKiosk: If a User has a pending dispatch assigned to him through the farmerswife dispatch module (Pickup Email is set to this User's name) when logging into the MacKiosk the Pending Dispatch window pops up instantly and the User can choose a pending dispatch waiting for him.

See more info on the new Maintenance tab here:
https://support.farmerswife.com/en/support/solutions/articles/17000123374-maintenance-tab-object-history-advanced-maintenance-bookings

In fw Client app > Toolbox > Maintenance tab a sub menu was added that will offer the user the following options:
- "Solo View In Tree": Select one or multiple Objects to see those in the Object Tree replacing the previous selection.
- "Add To Tree": Adds the selected Objects inside of the Maintenance Bookings to the Object Tree.
- "Set": This option is only available, if there is no open Maintenance Booking up to the present moment. If there is a Maintenance Booking booked for the future, you can also use this option to "set" a new Maintenance Booking.
- "Release": This will change the Status to the Release Status (set in fw Server app > Setup > Bookings tab > "Maintenance Statuses" area) and today's date.
- "New": Will create a new Maintenance Booking for the Object inside of the Maintenance Booking. You can also multiple-select Objects.
- "Report": This opens the Report to be able to create a PDF from one or various Maintenance Bookings.
- "Financial Report On Selected Objects": Use this option to create a Financial Report based on the Objects inside of the Maintenance Booking. No Maintenance Booking can be shown in the Financial Report only Class Bookings on the Object itself.
- "Maximum Hits When Searching": Select here the maximum hits when searching to include all Objects. Be aware, setting it to "No Limit" might slow down the system for the duration of the search.

When using the feature in fw Client app > Long Form > Objects tree > Object icon > Maintenance > "Release", this will now additionally set the "Maintenance State" to "Closed" and set the End Date of the current open Maintenance Booking, according to what was set in fw Server app > Setup > Bookings > Maintenance Release Status.

Changed in fw Client > Toolbox > Maintenance tab > the column label fields to match the Maintenance window.
Changed "Header" to "Name", "Note" to "Description", "Name" to "Object Name", "Status" to "State".

If you had multiple Entries with Timecodes and you add them to the Clipboard, when pasting into another Media you can choose whether to keep the Timecodes or not. If you untick to assign new Timecodes then in some occasions the Timecodes of one of the pasted Entries would be wrong. This bug is now fixed.

In Object Manager, when you open up a Media Order Object for editing, there's now a new "Menu Group" field.
It works the same as on Materials, Services and Expenses, affecting the menu that is used when you add them to Projects or Media Orders.
Items that have a Menu Group will be collected under a cascade menu with the that name.

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

Since 7.0 RC1 "Multiple Currencies" needs to be added to the farmerswife license, in order to use this functionality.

If Divisions are set up, the currency linked to the division will be applied. The Currency can still be changed. The Object Rates are calculated using conversion rates for now.

You can set "default" Currency on Clients > Client Details > Currency, so when creating a new project and associating with that client you'll be prompted if you'd like to apply that client currency or use the Main/Division/other currency.

### How things are stored
For each Object we now have:
- Buy / Sell Rates: The original Buy / Sell Rates. The numbers stored in here should always be in the Main Currency.
- Currency rates: New index that stores the currency rates of the Object for each active currency. Includes Day and Hour rates.

### How to get the rates in the Edit Project window
- When Use Currency Rates is OFF you get the original Buy / Sell Rates and convert them using the conversion rate.
- When Use Currency Rates in ON you get the Currency rates for the Project Currency.

### What happens when you edit rates
- When Use Currency Rates is OFF you are always editing the Main Currency and the the Project Currency is converted on the fly.
- When Use Currency Rates is ON you are editing all the Currency Rates of the Object for the chosen Day / Hour configuration.

In general, Object Rates are converted in the following way when changing the Project Currency:
1) If “Use Currency Rates” is on then:
- If the Object INHERITS CLASS RATES and
- It has a Class and Activity ==> gets currency rates of Activity.
- It has Class and no Activity ==> gets currency rates of Class.
- If the Object doesn’t Inherit Object Class Rates or doesn’t have Class and Activity ==> gets currency rates of Object.

2) If “Use Currency Rates” is off then everything is converted with conversion rates.

The above calculations are done for the following Objects:
1. CLASS BOOKINGS OBJECTS AND EXTRAS
2. MATERIALS, SERVICES, EXPENSES
3. PROJECT OBJECTS (directly added on the Project)
4. PROJECT WORK ORDERS
1. OBJECTS, MATERIALS, SERVICES, EXPENSES
5. MEDIA ORDERS
1. OBJECTS
2. TIMEREPORT
1. MATERIALS, SERVICES
6. VIRTUAL BOOKINGS
1. OBJECTS AND EXTRAS

For the following, CONVERSION RATES are always used:
1. CUSTOM MATERIALS/SERVICES/EXPENSES
2. PRICE AGREEMENTS
3. SELL PRICE OPERATORS (ONLY CASH DISCOUNT)
4. PROJECT WORK ORDERS
1. FIXED PRICE
5. MEDIA ORDERS
1. FIXED PRICE
2. TIMEREPORT
1. USER RATE

On DemoDB go to: fw Client > Toolbox > Settings > Server Setup > "Multiple Currencies Setup" button.

If you created a new Booking for an Object on a Project where you have set a currency different to the Main Currency and you have the "Use Currency Rate" setting off, it would wrongly convert the rates twice using the different conversion rate.

Now they only get converted once.

The Multiple Currency Rate icon would wrongly overlap over the text in certain windows in German. This was fixed in the following windows:
- User
- Resource Details
- Suites/Workstations
- Equipment/Machines
- Class
-Activity

On the Login page of the Web Client, use the "Language" selector field.

When the "display color" of the Confirmed Booking Status was changed via fw Client > Toolbox > Settings > Web Share Settings > Booking Colors > Confirmed, it would wrongly not populate properly in the Web Client and still show Bookings with the default green color for all Confirmed Bookings.
It's now fixed and when green is changed to any other colour, it's displayed correctly in the Web Client.

This change adds the two elements: "Booking Note" and "Time Report Note (Day Note) to the *Booking Time Report Change* Global Notification emails.

To fix this issue, the internal SERVER_HAS_MANY_OBJECTS number was extended the first time since v4.0 from 2000 to 4000. The previous limitation on Object searches was also preventing from looking into Object Classes, for performance reasons.

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

Added number padding (1-9) to Auto Number Inventory Number with the setting: Padding In Inv. Number.
It is now possible to enable a number padding 01, 001, 003 up until 9 digits to the auto number inventory feature. When activating the feature in the Server Setup > Objects tab > Auto Number Inventory Number and Padding In Inv. Number all Inventory Numbers will start with 1 (and the padding you chose), ignoring any former Inventory Numbers.

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

See more info on how to start using the "OpenID Connect" together with "Okta Single Sign On":
https://support.farmerswife.com/en/support/solutions/articles/17000127714-farmerswife-okta-integration

Fixed the following:
- Setting "Lock time" to 0 causes error message that user has to wait for 0 seconds.
- Users selected to be "Excluded From Password Expiry" didn't persist on client side.
- It was wrongly possible to exclude in-active users from password expiry.

Added "Allow Manual Offset" column to the Personnel Event Types window that, when true, allows the setting of a manual offset for that Custom Personnel Event Type.
For some Personnel Types you can enter an "Offset" Number, that counts against the days taken of that type.
Now, from v7.0 you can also set offset numbers on Custom Personnel Types.

See more detailed info here: https://support.farmerswife.com/en/support/solutions/articles/17000112259-add-offset-personnel-numbers-for-personnel-types

Before it could take more than 20 seconds to load the Long Form > Personnel tree with more than 50 Objects and showing 2 months in the Long Form View Port, if Labour Rules was licensed.

Now, this has been optimized, and the same operation as before is down to 5 seconds.

When using the farmerswife Client app in Dark Mode, wrongly all Price Agreements did not show the set colour. This is now fixed.

To be able to do "Batch Label" printouts, you work from the Media Library > Search. You then use the sub-menu or right-mouse click anywhere on your search results. On the pop-up menu select "Multi Label Printing". On your already existing Multi Label Template, you then drag & drop the Media or Entries onto the existing Label areas.
When you then use "Save As PDF..." each Label gets "printed" onto one Page inside the same PDF. You can then easily Print this PDF on your Label Printer, where then also each page gets printed on its own label.

After adding this new "QR Code" element type, you can then "edit" it and select an element to be used for the QR Code. If the QR Code is to represent more than one Data Element, then you have to previously configure and setup a Data Element that contains all information in one String. Once the Data Element is chosen you can set the pixel size for the QR Code. For further information see https://bit.ly/fw-qr-codes

Go to fw Client > Toolbox > Settings > Server Setup > “Print Designer Version” by which you can select and keep using a specific version of the Print Designer, while we continue fixing and adding new versions solving other issues.

This latest “Print Designer Version: 8" is specially focused to fix multiline text issues in Invoices > Totals causing overlapping elements especially on Page Breaks.

Summary of all 7 “Print Designer Version" options:
1: Default "Built In PDF Printer". (On v6.8 the Print Designer Version: 5 is set to be the Default one after the upgrade.)

2: To help when using Print Designer Templates with many "loops" and Rectangles.

3: Specially focused to fix issues on Print Designer Templates, where the Text Elements do not aligning properly after a Page Break, where this is caused by using multiple-line texts in "Loop" and "Page" positions with Rectangles causing Page Breaks.

4: Specially focused to fix issues on Print Designer Templates, where in the template's "Setup" "Show Header In Each Page" is being used. This could wrongly cause, that some Text Elements were wrongly overlapping after a Page Break.

5: Specially focused to fix issues on Page Breaks issues caused within the Total sections, when using multiline texts and many “dynamic” Total values positioned next to each text line.
Note: On v6.8 this Print Designer Version is set to be the "Default".

6: Specially focused to fix issues on wrong y position in the Elements Rows section, when one of the elements jumps to the next page and following ones need to start in the same position than the element that caused the page break.

7: Specially focused on customer specific Page Break issues and Financial Report.

8: Specially focused to fix multiline text issues in Invoices > Totals causing overlapping elements especially on Page Breaks.

The Framework Names are now not wrongly aligned at the bottom of the Rectangle when using in fw Client > Toolbox > Settings > Server Setup > Print Designer Version: any of the 7 versions.

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

The "direct print" functionality called "Print (Beta)" has been completely re-factored. And the button on the Print Designer is now called "Print" again.
It now works the same way as it already did on macOS!
You don't need to apply any special configuration.
The only pre-requisite is: The actual Printer you want to directly print too must be installed, configured and working on the computer you want to print from the fw Client app.
You can then use the "Print (Beta)" button where it's available on Print Designers, Financial Report Designer and Label Designer preview windows.

The Price Agreement Name now correctly shows up in the Project Report. Before it was always stating "No Price Agreement".

When you ran a Project Report, it would forcefully reset the Project View to the first one in the list before actually running the report, causing these issues:
- The wrong items might be used for the Report.
- Any Price Agreements from the original view might be missing.
- When you came back to the Edit Project window, it might show wrong items and/or prices.

This bug was introduced in 6.8 SP1, and it is fixed.

Before it was possible to click and use the option in fw Server > Setup > Projects tab > Project Customs > "Apply To All Existing", even if you have "Saved Custom Field Templates" (Saved Template Lists). This would however provoke a Custom Field loss on all Projects, as it would apply the displayed Custom Fields to all Projects. This has now been blocked and the option is greyed out if you are using Custom Field Templates for Projects.

You can now sort the Projects in the Long Form > Projects tree by their earliest Booking or Ad-hoc Timereport date.

To use this new sort option, go to:
fw Client app > Long Form > Projects tree icon left-mouse-button click > and then select the new "Sort By Booking Start Date" option.

For more information see https://support.farmerswife.com/en/support/solutions/articles/17000076137-projects-tree

The UK Public Holidays have been updated to include Monday 8th May 2023 Bank Holiday, for Coronation of King Charles III.

Requires to use latest swagger.json v0.8.11.
This is published together with the release of v7.0 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

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

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

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

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

Latest "swagger.json" version is still the one from farmerswife v6.8 Release rev. 20523: v0.8.9.

No swagger.json file update is needed for this fix to apply.

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

Adhoc Time Reports don't have any "Booked" time. So in a couple of places (Financial Report > Rows and Project Report > First X In Booking), the Time In/Out fields showed e.g. 06:00-06:00 as time.
Unless a field is specifically for Booked time, it should show the reported In/Out time. That is now fixed.

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

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

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

Go to fw Server app > Setup > General > "File Transfer Port", there's now a pop-up menu with a "Use SSL" setting. By default this is Off.
Activating it will make the internal file transfers use TLS.

These new settings are now supported through server.cfg:
- SKIP_SERVER_DIALOGS: Setting this to 1 prevents the farmerswife Server app from showing a couple of dialogs that require user dismissal, such as "Upgrade Shutdown Required". More dialogs may be added in the future. Default value: 0
- DEFAULT_DATABASE: When no database exists, setting this to "demo" or "empty" will make the farmerswife Server app use the corresponding database instead of asking. Default value: "ask"

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

The "Project Todos" icon in a time report should only show IF the "Project Todo's" are configured in the fw Server app > Setup > Projects tab.

- Fixed Objects not counting as timereported when "Timereport Complete On Users Time" setting is enabled.
- Implemented to hide future Bookings when Timereport Mode is set to "Used" and "Use Timereporting" is enabled.

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

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

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

To use this new Web Permission Setting go to e.g. fw Client desktop app > main module bar "Object Manager", select and open a user by double clicking it, go to Permission Profile > sub-menu Web Profile Manager > Timereports > Ad-Hoc Timereporting > "Default Ad-Hoc Booking Status" with a Selector button (by default empty), to choose the "Default Ad-Hoc Booking Status" for Ad-Hoc Timereports created via the "Allowed Access Tiers".

Use the "Language" selector on the Login window of the Web Client from default "English" to one of the other available ones.

This issue happened if in fw Client app > Toolbox > Settings > Web Share Settings > "Open Booking Window In Edit Mode When Creating Ad-hoc Time Report" was enabled.

In the Web Client, when a Web User moved a Booking on the calendar that contained a Suite/Workstation and a User, the Booking move would change the Suite to the new timeslot but wrongly duplicated the person/User on the Booking. This bug is now fixed.

In Web Profile Manager > a Profile > Timereprots ...

1. Renamed: "Allow Reporting Over Existing Reported Time" to: "Allow Reporting Over Existing Reported Period Of Time".

2. Renamed: “Allow Timereporting on Projects” to: “Ad-Hoc Timereporting”.

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

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