6. Feb 2019
6.4 SP 2
Extended Booking/Project Custom Field Variables to make them individually selectable in the Email_Project_Booking_Report text template, see details.
Added missing support for "Custom Templates" for the "Email Project Booking Report", which now allows selecting and displaying only certain Custom Fields from the Project or Booking in the email!
This behaviour can be configured for the "Subject" and "Body" fields, when using the "Email Project Booking Report" feature. The new configured "Custom Templates" are then available from the "Email Template" dropdown selector.
To select and display only certain "Custom Fields" from the Project or Booking in the email "Subject" or "Body", first create a new template .txt file with this this file-name-format "custom_template_CHOOSENAME.txt" within the farmerswife Server > html_templates > other > "booking_report_email" folder. Use the existing "english.txt" and COPY into same folder. Then change the name to "custom_template_xxx.txt"
Then from the fw Client > Booking > Menu ... go to Other > "Email Project Booking Report" and select this new created template a first time and send it. There's no need to enter an email recipient at this time.
This action populates the available Custom Fields of the Booking Name to the template as well as the Project Custom Fields of the Project this Booking belongs to. They are listed at the top under "Available keys" with the format: <BOOKING_CUSTOM_FIELDS_LabelName> and <PROJECT_CUSTOM_FIELDS_LabelName>.
Copy/paste these Custom Field keys below the "<Start Body - DONT EDIT THIS LINE>" section where you want the information of the Custom Field to be displayed.
Note: If you use the SAME custom_template to send an email project report from a different booking with different Booking Custom Fields, those variables will be displayed at the top of the template under the "Available keys". Overwriting the previous variables. But the variables you added to the Subject or Body beforehand will not be touched. If the system can't find a matching Custom Field variable in the current Booking you are sending the email from, the fields are showing "blank".
Use this for more information: https://support.farmerswife.com/solution/articles/17000052458-2-project-booking-report
Fixed a bug wrongly showing the red "Timereport" icon on "Frameworks" saved as "Booking Templates" if the Setting "Use Time Reporting" was disabled, see details.
The red "Timereport" icon and the "Timereport" button on the Edit Booking window were wrongly included on Frameworked Bookings, if in fw Client > Toolbox > Settings > Booking Defaults > "Use Time Reporting" was turned off = disabled, and this was saved as a Booking Template and reapplied within the Long Form.
Now the Timereport icon and "Timereport" button on the Edit Booking window are only added for a User who has the "Use Time Reporting" (see above path to this setting).
Implemented farmerswife-Server side "pagination" support for the "Cirkus.com API", needed when syncing more than 500 Projects.
Before this change the Cirkus.com integration was creating duplicate Projects on the Cirkus-side, when syncing more than 500 farmerswife Projects. This support on the farmerswife side became necessary due to changes on the Cirkus API side.
Added tweaks for the Cirkus.com integration after some improvements were implemented on the Cirkus API.
Implemented the new "taskTypeIds" argument to get Cirkus Projects Tasks.
Changed the low-level connection behaviour for the "Cirkus.com" integration to avoid duplicates.
Fixed a bug by which the first fw Project selected to be synced to Cirkus, sometimes was not being synced.
Fixed a bug in the "Cirkus.com Connection" integration, wrongly causing synced Projects to be wrongly deactivated in Cirkus when selecting the option "Close only in farmerswife".
Added a new "Setup" setting called "Get Server Info" ("No" by default) to be able to choose if the fw Client contacts the fw Server at launch, see details.
Go to fw Client > Login window > Setup > Edit Server window > "Get Server Info" check-box.
This setting is by default turned OFF to benefit all customers not using the below mentioned features.
This new setting needs to be enabled by customers using the"Pre-Login Message" functionality or the "OpenID Connect" (due to delegated login) integration.
Fixed a bug not causing Conflicts when extending a Booking in Long Form using option Booking > Days > "Add From Time Range".
Fixed a bug causing a crash when upgrading from v6.2 related to Passwords being "Hashed & Salted".
Fixed a bug wrongly preventing to Save changes on Contacts IF the system was upgraded from v6.1 SP1 to v6.4 SP1 without the usual upgrade steps.
Extended beyond 2018 customer specific "hiding" of certain information related to the "Day Plan" print out, see details.
On for example the "Day Plan", the Project's year and Binder information is by design not supposed to be shown for all TV2 regions, when the Web Users print the "Day Plan > Til dagsplan" PDF. It was wrongly showing the "year part" of the Project Name and the amount of Binders.
This is now fixed and behaves as before.
Added "Menu Group" as a new Element in the Rows section of Financial Report Print Designer, see details.
The "Menu Group" is an optional field in the "Modify" window of "Extras" Objects (i.e. "Materials", "Services" and "Expenses").
This "Menu Group" has now been added as an Element to the "Rows" section of the Financial Report Print Designer, and will populate the "Menu Group" value configured on Materials, Services and Expenses.
On new created Financial Report templates, this new Element will be placed above "D: [Activity]" and below "D: Category (Object)]".
For already existing templates, it will appear at the bottom of the list.
Fixed a bug causing a fw Client Error when running a Financial Report on a Project Work Order, if "Sell Rate" and "List Price Rate" were used, see details.
Fixed a bug causing a fw Client Error when running a Financial Report on a Project Work Order, if the Report Template was using any of these recently (in v6.4) implemented "Rows" elements: "Sell Rate" and "List Price Rate".
Added a warning message when swapping two Objects in Framework Bookings if they are not member of the Framework Object Class.
Now there is a warning showing the Objects and the Classes that do not belong to the Framework Object Class.
Fixed a bug by which "Break (Min.)" was not updated in the Timereport window when changing the Break before allocating an Object to a Framework.
Fixed a bug on "Framework Break (Min.)" when setting a Break on a multiple day frameworked Booking and then removing it on only 1 day, wrongly all Breaks were removed, see details.
When selecting any of the days of a Framework and setting the Break time to 0 using the "Time In / Out (Override)" option, wrongly all Breaks on all days were removed.
Now the "Break" only gets removed on the selected day(s).
Fixed inconsistencies when using "Hotkeys" to run "Print Designer Templates" from Projects loaded to the Long Form > Projects tree, see details.
Previously when replacing a Project in the Long Form > "Projects" tree, in order to run a report on the newly loaded Project using pre-configured Hotkeys (via fw Client > Toolbox > Settings > Miscellaneous > "Hotkeys Editor" button > Functionality "Print Designer Template: ReportName"), even though the Project Name was displayed in blue (= selected), it was wrongly needed to also click on the actual Project Name for the Financial Report to display data that corresponded to that specific Project. Otherwise the Report would show data from the Project previously loaded to the Projects tree.
Now it is possible to just load the Project on the Long Form > Projects tree and use the pre-configured Hotkey to run the Report, without having to click on it anymore, given that there is only one Project loaded to the Projects tree.
To run a Report on multiple Projects you need to multiple select them.
If more than one Project is loaded to the Long Form > Projects tree, only the one selected will be printed when using the pre-configured Hotkey.
Fixed a bug wrongly overwriting the Sell rate of Objects added to Projects via Incoming Invoice with the Buy rate, when modifying the related Incoming Invoice, see details.
The Sell rate of an Object added to a Project via an Incoming Invoice gets the Buy rate value if the setting "Use Buy As Sell Rate When Adding Incoming Invoice Lines To Project" (in fw Server > Setup > Financial tab) is set to "Yes"; and the Sell rate is 0.00 if the setting is set to "No".
This Sell rate can be later modified in the Project.
When opening the related Incoming Invoice to modify it (add into to the Note field, change the Buy rate, approve it, ...), when clicking "OK" to apply the changes, the Sell rate of the linked Object was wrongly being reset to the Buy rate.
Now, the Sell Rate is completely independent from the Incoming Invoice.
Fixed a fw Client crash error when Part Invoicing and moving all "Budget Details" from the "Not Selected" to the "Selected" pane in one go.
Note: Moving the "Budget Detail" line items one by one never stopped from working.
Fixed a bug that was wrongly causing Invoice Custom Field values to appear mixed up within the "search results" column view.
Fixed a bug in Overtime Compensation Rules, preventing decimal money compensation, see details.
In Edit Labour Rule > Overtime Sub Rule > Financial Modifier, if you entered a decimal value and saved it, the decimal point was wrongly removed.
This bug was introduced in version 6.4 Beta rev. 17186; it there for only affected Labour Rules which were changed between 6.4 Beta 12 until the upgrade to 6.4 nightly rev. 17421 or later.
Fixed a bug wrongly not showing the Labour Rule Warning for "Rest Between Days" in the Long Form on the 1st day of a month.
Fixed a bug wrongly causing the "User Approval Status" to change back to "Pending" after the Booking was "Accepted" via Mobile Web Client, see details.
This bug only happened, when an Object already had more than 1 Booking within the same timeframe.
Fixed a bug when using "Import/Export" of Objects type User, when importing a list of Users, wrong pop-up message "Updated x Objects" even when there was no update, see details.
Now if there are no changes on the previously exported CSV file and it is imported again, the pop-up message will now correctly display "There Were No Objects Created Or Updated".
Fixed a bug in Long Form > View Port when dragging an element over the grey-colorer-days, they wrongly changed to white and never back to grey.
Fixed a bug when replacing a conflicting Object, this would cause confusing dialogs that could lead to deleting the complete Booking, see details.
Now, when replacing a conflicting Object it now works again as in v6.3: when replacing Objects, after "Confirm Replacing Object A with Object B" no further dialog message are displayed.
Fixed Print Designer Page Break issues where some Elements would wrongly "sit on" the actual page break, or some elements are on wrong page, see details.
Some elements in the Print Designer did not observe the Page Breaks and instead sat right on the boundary in-between pages or from vertically aligned elements from the same loop one of the elements was wrongly drawn on the following page.
Also Page Breaks for "grouped elements (so typically when using the Financial Report Designer) could cause "in-line" elements for one of the elements to be wrongly drawn on the following page.
We are still working on more improvements for the Page Breaks in other places of farmerswife.
Fixed some inconsistencies on "Page Breaks" causing that the second and following pages were wrongly empty when printed e.g. to PDF.
Fixed a bug that was wrongly showing the "Filter Objects" as disabled within Edit Project window > View Settings / Option > "Web View Limits" window. see details.
The "Web View Limits" column in fw Client > Toolbox > Projects tab was correctly showing an "F" (= Objects being filtered) next to the date. But in certain scenarios when opening the Project and going to "View Settings / Option" > "Web View Limits", the "Filter Objects" check-box was wrongly being displayed as un-checked = disabled.
This is now fixed and the "Filter Objects" setting is displayed correctly, and if enabled the filtered Objects are being displayed correctly and it now corresponds again to the displayed "F" in fw Client > Toolbox > Projects tab > "Web View Limits" column.
Fixed multiple wrong Public Holiday dates in 2019 and later on the "Public Holidays Import" functionality for all now 7 available countries, see details.
On all 6 pre-existing "Public Holidays Import" by countries, there were unfortunately multiple wrong dates or wrong days in 2019 and later. All of them are now reviewed, checked and fixed.
We also added "Import Bank Holidays For Sweden".
1. Use "View Full List" and copy the contents for later review if necessary.
2. Use "Clear All Public Holidays From The System" for a clean slate start.
3. Use "Import Public Holidays For ..." your country if it exists. If it does not exist, please review the following information to e.g. adapt the "closest matching" pre-existing file for a fairly painless subsequent import.
IMPORTANT when using these pre-set Public Holiday lists: in your country, or region, or industry, or company different Public Holidays might apply or be more correct!
Please see the below instructions, on how to properly use this improved functionality.
For the "Import Public Holidays For ..." the pre-existing 7 countries, it will NOW read the data from the farmerswife Server-side stored "holiday" files for the import. Only these 7 presets will work.
These are located on your farmerswife Server root installation path > html_templates > other > new "holidays_importer" folder; this contains the below 7 listed "country-short-name.txt" files.
To use this functionality go to: farmerswife Client > Toolbox > Settings > Server Setup > "Public Holiday" button.
Click on this "Public Holiday" button to get the "Remove" or "Add" options.
=> "Remove" button:
Using this button will show selector list of all Public holidays ... single???select the one you want to remove.
=> "Add" button:
This button will open a Calendar to set the Date of the new Public Holiday, give it a Name.
NOTE: To "cancel" using the "Public Holiday" button, use the "esc" key on your keyboard until you reach the "Cancel" button on the next step and then use "Cancel" to abort the operation.
Use the sub-menu drop-down next to the "Public Holiday" button to:
=> "View Full List":
Using this option will open the "Current Public Holidays" pop-up window, listing all Public Holidays so far configured within farmerswife.
=> "Clear All Public Holidays From The System":
Using this option will do as it says, and clear all currently set Public Holidays from your farmerswife system.
=> Import Bank Holidays For Australia (au.txt)
=> Import Bank Holidays For Belgium (be.txt)
=> Import Bank Holidays For Denmark (dk.txt)
=> Import Bank Holidays For Germany (de.txt)
=> Import Bank Holidays For Sweden (se.txt)
=> Import Bank Holidays For UK (uk.txt)
=> Import Bank Holidays For USA (us.txt)
IMPORTANT: If you apply changes on the above mentioned files, use an advanced Text-edit-tool (e.g. "Notepad++" on Windows, or "Sublime 3" or "TextWrangler" on Mac), and ensure that the encoding of this file remains "UTF-8".
NOTE when using the " Import Bank Holidays For ..." feature:
- They do NOT affect pre-existing "Day Notes".
- Only 1 Public Holiday can be added per day.
After the import action, there will be a pop-up window containing two sections which shows what happened during the import:
=> "Added Public Holidays (amount):"
=> "Not Added Public Holidays (amount):"
If days are already configured as "Public Holiday" the "Import" will not add more. The ones not added will be listed here.
farmerswife has two different "Public Holiday" formats:
"All Day" = Will color the "Public Holiday" day in red.
"Half Day" = Will color the Public Holiday" day in orange. "Half Day" is typically used when a "Public Holiday" might not be observed in the whole country or industry, or if it's on a Sunday.
Fixed a bug wrongly preventing access to the REST API after v6.4 SP1.
Fixed "tcllib" packages on the v6.4. JSON package, which now allows to access the REST API again.
Added a "Password Policies Configuration" option to farmerswife Server > Setup > Users tab, see details.
It is now possible to also configure "user" Password Policies via fw Server > Setup > Users tab > Password Policies (bottom right) > "Configuration" button.
Using this fw Server-side Password Policies > "Configuration" button is the same as in fw Client > Toolbox > Settings > Server Setup > Password Policies > "Configuration" button.
Changed behaviour that now "Password Policies" only apply to user passwords, see details.
The "Password Policies" introduced on v6.4 now only applies to user passwords.
Password Polices now no longer affect these in farmerswife Server > Setup ...
> General tab > "Server Password"
> Projects tab > "Invoice / Close / Remove Password"
> Projects tab > "No Permission Users Allowed Attach Project Password"
> Media Library tab > "Library Password"
> Financial tab > "Invoice Manager Password"
Fixed a DB upgrade bug to wrongly cause duplicated "Shared Hourline Views" to be unlinked under certain conditions, see details.
Fixed a DB upgrade bug to happen under certain conditions, wrongly causing duplicated "Shared Hourline Views" to be unlinked from the Web Permission Profile setting > in Events > Select & Share Hourline Views.
Modified the new "Password Policies > Configuration" from within the fw desktop Client app via Toolbox > Settings > Server Setup, see details.
The new "Password Policies" can now also be configured via the farmerswife desktop Client app > Toolbox > Settings > Server Setup > Password Policies > "Configuration" button, which opens a pop-up windows with a table displaying all the available options to set up the Password Policy rules.
The same "Password Policies > "Configuration" button" functionality is also now available on farmerswife Server-sidd; go to: fw Server > Setup > Users tab > Password Policies (bottom right) > "Configuration" button.
The previously used "JSON" file will not be used anymore after the upgrade. If Password Policies were already set-up via the "JSON" file, the configured values will be copied into the new configuration window and the file will be deleted to no longer be used. If no Password Policies were used, the default values (0) are applied.
Fixed a bug in the upgrade process by which the fw Server could crash when upgrading Contacts from a revision older than rev. 17149.
Fixed a bug causing not-active members of a Class to wrongly not show in Toolbox > Classes > Show Members > "Show Inactive" set to "Yes".
Fixed a bug on Project > "Web View Limits" that an Object enabled in "Filter Objects", when removed and applied back to Framework Bookings it was wrongly re-enabled.
The "Web View Limits" allow the Project owner of a Project to plan and book without any involved user seeing any Bookings.
The bug caused that Objects wrongly remained checked on the Edit Project window > "eye" menu "View Settings / Options" > Web View Limits > "Filter Objects" when you removed and applied them back on a Framework Booking.
Now "Filtered Objects" will be treated as a different Object, if it is applied back to a Framework Booking so that the Object check-box in the Web View Limit section Filter Objects will not be ticked.
Fixed a bug that was not showing Shared Hourline Views added via the "Can See All Shared Hourline Views" in Web Profile, when connecting via all Web Client, Mobile Web Client and iOS
Fixed a bug wrongly preventing "Shared Hourline Views" added via the Web Profile Setting "Can See All Shared Hourline Views" to be shown when connecting via all "Allowed Access Tiers", so iOS fw app, Web Client and Mobile Web Client.
Fixed a bug wrongly causing the Web Profile Permission "Allow Adding Objects To Timereport > His Own Object" to only work if "Divisions" was licensed.
iOS farmerswife app v5.0.827 available on Apple's App store since 26. February, 2019, see details.
- In Events week view changed the Personnel event icon (Vacation, Sick, etc.) from a "triangle" to now a "square" shape for increased visibility.
- Added some iPhoneX GUI fixes.
- Fixed a GUI bug on the Time-picker for iPhone 6 Plus when using in Settings > Display & Brightness > "DISPLAY ZOOM" > "Zoomed" mode (iOS > Settings.
Fixed a bug wrongly not displaying a Warning message when time-reporting a Booking to then overlap with a pre-existing Personnel Event, see details.
If this setting in a Web Permission Profile "Allow Reporting Over Existing Reported Time" is turned off, a Web User will get a "Warning" message if he tries to time-report a Booking that overlaps another Booking.
If Anne is booked from 10:00 - 12:00 and 12:00 - 15:00 and she time reports the first Booking to 10:00 - 12:30 and later tries to time-report the second Booking from 12:00 - 16:00, she will get a warning: "The Times Are Already Reported".
This warning however would wrongly not appear if the time report overlaps into an existing Personnel Event.
This is now fixed and the same warning message "The Times Are Already Reported" will be displayed. And the user will only be able to time-report once the Personnel Event has been adjusted accordingly.
03. Aug 2018
6.4 SP 1
19. Jun 2018