Back To Release Notes List



Back To Release Notes List

#15837

18. Apr 2016

6.1 Release

  • 0 Warnings
  • 8 Features 45 Features
  • 8 Other changes
  • 16 Bug fixes

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

6.1 Release rev. 15836, released 18. April 2016

The full list of over 300 logged changes since v6 can be accessed on our website: //www.farmerswife.com/releasenotes/
These are the native 6.1 Release changes:
- 8 HOT Features
- 45 Features
- 8 Other changes
- 16 Bug fixes

Noteworthy highlights are:
- From planning to delivery, discover the Adstream Platform connection
- Google Invite integration to trigger event invitations
- Send automated Email Reminders for over-due time reports
- Show actual Time Reported Time in the Web Access tiers
- Search Filter for Part Invoices and highlighted Price Agreements

... and more, see the "Whats New in v6.1": //www.farmerswife.com/downloadsWeb/fw_WhatsNew_61.pdf

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

How to upgrade to version 6.1 and later, click on "+" to see the details.

Basics
- You need to have a "Version 6.1" license at hand, before starting the upgrade process.
- To be eligible for a 6.1 license you need to have a valid support subscription (Gold or Silver) with us, at least up to 18. April 2016 or later.
- If you do not yet have a v6.1 license, then please request this from license@farmerswife.com once you are ready to upgrade.
- Note: the "Public Installers" section is open; see more info below!

Note: the previous version 6.0 _was_ a facelift version!
The user interface has changed, but it's still farmerswife.
Also the installer names and paths now use "farmerswife" IF installed from scratch.
If you have not seen it before, go to our website //www.farmerswife.com and click on the 'Demo/ menu button, enter your details and try it out on our "Online Demo' environment.

The built-in auto-upgrade _is_ supported for all WIFE Clients on v5.2 Release or later!
The auto-WIFE-Client upgrade functionality is supported and works for all WIFE Clients which were once manually upgraded past 5.2 Beta 4.
Operating system "read and write" user permissions for installed software on the local machine are sufficient for the auto-upgrade functionality to work.

After the WIFE Server has been upgraded to version 6.1 or later, log-in with the WIFE Client, and follow the instructions of the auto-upgrade dialogues.

A MANUAL WIFE Client upgrade is only needed for OLD installations BELOW v5.2
The auto-Client-upgrade functionality will NOT work for WIFE Clients below v5.2.
A new SSL-based communication protocol has been implemented. Any WIFE Client has to be manually upgraded once to 5.2 Beta 4 or later.
The auto-client upgrade will work again for any WIFE Client which was once manually upgraded past 5.2 Beta 4.

Any WIFE Client which was NOT manually upgraded will state this message when trying to log-in:
"Connection to the Server Timed Out"

The "Installers" section is open
"Installers" section on support.farmerswife.com is now open; you do not need any access credentials anymore. These are only needed for following "preview" or "beta" versions.
=> Go to: http://support.farmerswife.com and click on the "Public Installers" button on the left side of the page.

Upgrading step by step
- Your WIFE Server needs to be at least on version 5.2 Release (if lower, contact support@farmerswife.com) to upgrade straight to the latest v6.1 version.
- Inform your colleagues about this new version BEFORE you upgrade.
- Run a "Full Backup" BEFORE the upgrade. <= Use the "Full Backup Now" button located on the running WIFE Server application.
- While the Full Backup is taking place, you could now take a look into the documents provided in the "Read And Use Me Upgrade Package" you were issued together with your license of the previous Released version.
- The upgrade itself might require a couple of "Forced Shutdowns" for it to finish; this depends on your usage of the system.
- If needed, see more detailed information in the fw_InstallationInstructions_Window_Mac_Linux_61.pdf.
- Ensure you have the latest Java version (JRE on Windows/Linux, JDK on Mac OS X) installed, for the Web Client and Mobile Web Client and Play to work properly and in the most secure way. Watch out on Windows: here you can run the fw Server application in 32bit mode (farmerswife.exe) or 64bit mode (farmerswife 64bit.exe); and depending in which mode you're running the WIFE Server, you _must_ have JRE installed in the corresponding 32bit or 64bit version.

farmerswife Server upgrade on Mac:
- Copy the NEW farmerswife Server package to the machine hosting the WIFE Server.
- Un-zip and rename it to include "NEW" in the package name.
- Place it in the same location as the previous running farmerswife Server.
- Quit the running WIFE Server.
- Rename the previous farmerswife Server, to include "OLD" in the package name.
- On both packages do <Control> + click and select "Show Package Contents" in the pop-up menu.
- In the OLD package select the "system" and "files" folders and use <Control> + click and select "Copy 2 Items" in the pop-up menu.
Note: The "files" folder might not even exist within your WIFE Server's package, since it was possibly broken out to reside on some mounted storage device within your network. Ensure that this Volume is properly mounted.

IMPORTANT excursion - have any files been customized?!!:
If any of the below points apply, then don't forget to manually migrate these files from the OLD WIFE Server package > "Show Package Contents" > ... to the new one.

a) Has anything been changed or customized within "html_templates"?
=> Ideally you compare first compare your customised files from within the "html_templates" with the new ones from us. There might be new functionality available; you'll need to adapt this. Then only migrate the customized files.

b) Did you "SSL-ify" your farmerswife system?
=> follow your own logged instructions in regards to which of these files "server.pem, skey.pem, keystore, jetty.xml" have to be migrated.

c) Are you using any 3rd party integration scripts?
=> browse to ... contents > lib > scripts > ... to get to the location where integration scripts are located. And then only copy the actual integration script files from the according sub-folder within the new farmerswife Server package.

... continued from above:
- In the NEW farmerswife Server package use <Control> + click and select "Paste 2 Items".
- Now copy the new 6.1 license files into the "system" of the NEW WIFE server, thus replacing the previous ones.
- Double click on the NEW farmerswife Server package icon to start the actual upgrade process.
- Once everything worked out fine, remove or update any Dock or Desktop links. And if needed remove the OLD Server package; because up until now, this was a working "roll-back" backup, just in case something went wrong.
- After the upgrade, start the farmerswife Server as usual.

Then once you've successfully upgraded, please inform us by sending a short email to support@farmerswife.com; this is very helpful information for us.

farmerswife Server upgrade on Windows and Linux:
IMPORTANT:
In case you have customised any files (e.g. some files within "html_templates", server.pem, skey.pem, keystore, jetty.xml 3rd integration scrips, etc.), ensure that they are set as "Read Only", so you don't overwrite them with our files included by default! During the installation process, simply then use the "Ignore" button when the Installation Wizard is not allowed to modify these "read-only" files.

- Make sure you are logged into the host machine with the same admin user as on the initial installation of the farmerswife server application.
- Copy the NEW farmerswife Server installer file to the machine hosting the WIFE Server.
=> On Windows this is a .exe file.
=> On Linux 64bit, this is also an executable file; use in a command shell: chmod +x Linux64_... to make it "installable".
- Quit the running farmerswife Server.
- Now copy the new 6.1 license files (license.dat and license.txt) into the "system" folder of your WIFE Server, thus replacing the previous ones.
- Double click to run the installer file in the same manner as the previous installation (for example did you use "Run As Administrator" on Windows?).
- Follow the instructions of the install wizard. IMPORTANT: While installing make sure the previous installation path is correctly set.
- After the upgrade, start the farmerswife Server as usual.

Once you've successfully upgraded, please inform us by sending a short email to support@farmerswife.com; this is very helpful information for us.

The farmerswife Clients will auto-upgrade ...
... if already on version 5.2 or later: ... by using the "simple in-application" auto-upgrade process; "normal user" Operating System permissions (Read / Write) are sufficient.

IMPORTANT for the supported auto-upgrade functionality:
For the farmerswife Client applications the "simple in-application" auto-upgrade process to work (once supported in later versions), "normal user" Operating System permissions (Read / Write) are sufficient. You log-in, you confirm that you want to upgrade, the needed files are transferred, the WIFE Client restarts, done.
But when auto-upgrading on Mac with a mix of Admin and Standard users, make sure to be logged-in as a Standard user. Then after mounting the .dmg file, drag-and-drop it to the Applications folder. You then need to authenticate with the Admin users credentials! The farmerswife Client will not work for the Standard user, if installed while being logged-in as the Admin user.

IMPORTANT when upgrading the WIFE Client on Mac: If you have a mix of Admin and Standard users on a Mac, make sure to be logged-in as a Standard user. Then after mounting the .dmg file, drag-and-drop it to the Applications folder. You then need to authenticate with the Admin users credentials! The farmerswife Client will not work for the Standard user, if installed while being logged-in as the Admin user. For the farmerswife Client applications the "simple in-application" auto-upgrade process is supported, "normal user" Operating System permissions (Read / Write) are sufficient. You log-in, you confirm that you want to upgrade, the needed files are transferred, the WIFE Client restarts, done. This upgrade process is not explained in any further detail.

Once you've successfully upgraded, please inform us by sending a short email to support@farmerswife.com; this is very helpful information for us to improve our service to you.

IMPORTANT: Universal iOS farmerswife apps on Apple's App Store - iOS 8 native v5.0.708 since November 20th, 2015, click on "+" to see the details!

The latest iOS farmerswife app is v5.0.708 - this is a native iOS 8 version and available since 20-November-2015.
NOTE: iOS 9 required since iOS fw app v5.0.706.

IMPORTANT:
Due to security changes on iOS 8.4 by Apple, these changes can only be supported on the latest farmerswife v6 SP2 and later versions!

This means:
You should upgrade as soon as possible to v6 SP2 or later.
If you can't upgrade your fw Server application to v6 SP2 or later (released 15. July 2015), then you can't use the iOS farmerswife app on iOS 8.4 or later.
You will get a "Error Failed To Connect" message.

IMPORTANT for older versions:
The latest v5 universal iOS farmerswife app for iOS 7 or later: v5.0.59 is available on Apples App Store since 12-September-2014.
Your WIFE Server needs to be at least on version 5.0 SP4 or 5.1 SP1 or later to use version v5.0.59 and later.

How to install the iOS farmerswife app:
On your Apple mobile device go to the "App Store" app and search for "farmerswife"; depending what iOS version you have installed, it will show you different iOS farmerswife app versions.
Latest iOS farmerswife app version is 5.0.708; it requires iOS 8 (ideally you're on the latest iOS version).
Version 5.0.59 requires iOS 7 or later. This is the iOS 7 optimized version.
For iOS 6, the latest iOS farmerswife app is still version 5.0.34.

IMPORTANT:
Once more: The iOS farmerswife apps v5.0.59 to v5.0.708 are compatible to login to 5.0 SP4, 5.1 SP1 or later, 5.2 or later, 6.0 or later WIFE Servers ... except if on iOS 8.4 or later; here you need to be on v6.0 SP2 or 6.1 Beta 1 or later.
Per logged-in WIFE Server version, it will then allow using the latest supported features up to that point per that version.

NOTE: The 4.11.1 iOS farmerswife app will NOT work with a v5.x WIFE Server or later versions!

Running a separate TEST WIFE Server

This chapter describes the recommended best practice on working on and with a separate TEST WIFE Server.
This might be needed when running on Beta versions, or new Service Packs or in general when you first want to run an upgrade check
or evaluate new modules or new functionality on a separate TEST WIFE Server installation.

You can always use a WIFE Server in "demo mode" (also with your DB files) and it will run for 60 min. and you have 40 sessions.
An additional "TEST Server" license can be provided upon request, available for customer with a valid service agreement in place;
include in your request the Company Name, the info of the local static IPv4 address and the used Operating System of the machine to host the TEST WIFE Server.

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

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

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

The settings available by default are these:

FW_IP
FW_PORT
EXTERNAL_PORT
HTTP_PORT
HTTP_HOME
USE_SSL
HTTP_SSL_PORT
HTTP_UPLOAD_PORT
FTP_ALLOW
FTP_PORT
FTP_PASV_PORT
FILE_PORT
FILE_PORT_LOW
FILE_PORT_HIGH
MAIL_OK
MAIL_SERVER
MAIL_PORT
MAIL_USER
MAIL_PASSWORD
USE_SQL
SQL_USER
SQL_PASS
SQL_DB_HOST
SQL_DB_NAME
SQL_PORT
PRJ_CHECK_FOLDERS
MAIL_DEBUG
BARN_ACTIVE
HTTP_XML_PORT
WEBCLIENT20_ENABLED
WEBCLIENT20_PORT
WEBCLIENT20_COM_PORT
ALLOW_FORCE_RUN_NIGHTLY_SCRIPT
ALLOW_FORCE_RUN_PLAY_BILLABLES
TIMED_SCRIPTS_INTERVAL_SECONDS
MSAD_ENABLED
USE_EXCHANGE
READ_SCRIPTS_AS_UTF8
GOOGLE_SYNC

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

A proper WIFE Test installation works like this:

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

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

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

Now start your TEST WIFE Server application.

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

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

NOTE: Once you have properly configured your TEST WIFE Server as mentioned above, you can save time in the future and only copy these files from your PRODUCTION WIFE Server > from within the "system" folder:
- current45.efdb
- fwdb.db3
- histories.db3
- despatches.db3

About these Release Notes, Disclaimer and Legal Information.

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

Adstream

#218965

Adstream A5 Ordering <-> fw Media Order and Media Library integration, see details.

See Details

From version 6.1 farmerswife is integrated with Adstream's A5 Ordering system (A5).
This integration is free of charge.
Go to our open Knowlegebase //www.farmerswife.com/knowledgebase/#intro and in the search field search for "Adstream".

After creating a Delivery Order on Adstream A5, your linked farmerswife system will create and update corresponding Media Orders. Master files within your Media Library can be uploaded via Media Orders (via new FTP upload functionality) or directly from the Master Media's Entry. When Deliveries are finished, the Media Orders will be Moved to Done and can be invoiced.

 

Advanced Project Search

#65293

Implemented 2 new filter fields in Advanced Project Search, see details.

See Details

1. Budget Type: A multi-selector with Budget Type names. Selected types will filter the results. If "Any" option is selected, any Project with one of the selected options will be added. If "All" option is selected, only Projects with _all_ selected types will be added to the search hit results.

2. Active Budget: A checkbox. If ticked, then Projects with one or more Active budgets will be added to the search hit results. If un-ticked, then Projects with No Active Budgets (but with Budgets) will be added to the search hit results.

 

Booking Templates

#209115
#220511
#219790
#210002

Added major fixes related to Frameworks created from Booking Templates. see details.

See Details

Fixed the previous simple implementation of "Framework Static Time Frame Day Mapping" to Objects when applying Booking Template.

Fixed applying Booking Templates onto a selected date in the Long Form > Viewport, from a date and until a date. Placing all days onto their corresponding location. Taking into account "Never Select / Book Weekends Or Holidays" setting.

Implemented "Framework Day Notes" from Booking Templates.

 

Class Bookings

#205896

Added ability to edit Time In/Out for each Object directly from the Edit Booking window, see details.

See Details

To enable this new functionality, go to farmerswife Client > Toolbox > Settings > Booking Defaults > Show Booking Times In Booking Window Involved Pane: Yes/No (default).

Behaviour:
- For a Booking on a single day: Shows In/Out times per Object within the "Involved" pane and allows to edit via clicking on the "clock with green +" icon which opens the "Choose Start And Stop Time" pop-up window.

- For a Booking on multiple days: Use the new "triangle" show-and-hide-toggle button to see the options for all days.
Then, if start and stop times are the same for all days, it displays the "common time" to allow general edit in one go via the "clock with green +" icon.
And to change the individual times per each day, it allows the single edit "clock with green +" icon.

Conflicts:
- When applying changes with the open Edit Booking window, a pop-up "conflict warning" pop-up windows will be displayed.
- On saving the Booking (using the OK button), the normal "Conflicts" window is displayed on not re-solved conflicts.

Also:
Added "Clear" button functionality for the "Choose Start And Stop Time" pop-up window; using "Clear" will re-set to the Bookings In and Out times.


 
#204699

Implemented to ad-hoc add Services via the Edit Booking window, see details.

See Details

To activate this feature, go to: WIFE Client > Toolbox > Settings > Booking Defaults > Name / Customs > Server Setup > Modify ... an existing Booking Default Name Custom Field set-up; so in the then open "Custom Fields" window > Pre-Defined Services pane > Ad-Hoc Extras checkbox: No (not checked by default) / Yes (checked) to activate.

Once this is activated for a Booking type, it will show the new "Ad-Hoc Extras" pane on the Edit Booking window to here add e.g. Services.
Web Users will see these extras in the Time report > Extras tab (no change here, same as before).

 

Conflicts

#219642

Added support to also trigger the conflicts-auto-resolver when a Personnel Booking, causing a Conflict, is removed.

 
#219724

Implemented "Conflict" support for Bookings on Object Classes, see details.

See Details

To enable "Object Class Conflicts support, go to: fw Client > Object Manager > open an Object Class > tick the "Enable Causes Conflicts" check-box.
Once enabled the auto-conflict-resolver will check if this Object Class can be booked on a specific day and time, considering its members and other Class Bookings.

 
#220551

Fixed a bug causing Personnel Bookings to wrongly not trigger Conflicts.

 

Contacts

#113685
#217779

Implemented support for a new Contact type "Resource AND Client", which incorporates both feature-sets at the same time.

See Details

This new functionality is needed for the new "Google Calendar Invites" functionality.
Go to our open Knowlegebase //www.farmerswife.com/knowledgebase/#intro and in the search field search for "google".

 

The "Show/Hide" state of the Activity pane is now remembered, as a per-user setting.

 

Date & Time System

#212149
#217841

Implemented system-wide Calendar extension to 2029-12-30.

 

Dayplan XML Exporter

#219548

Added a new "CustomField" XML Node in "Dayplan Hourline View XML Export" to export Booking Customs, see details.

See Details

XML Description:

<Event>
...
<!--1 occurrence for each custom field-->
<CustomField>

<!-- Field Type: entry, text, selector, date, checkbox, files, thumbnail, images-->
<type></type>

<!--Field Name-->
<label></label>

<!--Only received if user set a value for this field-->
<value></value>

<!--Only Selectors: All Possible Values-->
<optionValue></optionValue>
<optionValue></optionValue>
<optionValue></optionValue>

<!--Only Entry/Texts types: If Field Is A Finder. Value format: 0 or 1-->
<canLinkToContact></canLinkToContact>
</CustomField>
...
</Event>

Example:

<Event>
...
<CustomField>
<type>entry</type>
<label>Dozent/In</label>
<value>Example Value</value>
</CustomField>
...
</Event>

 
#215358

Added new option for 365 days for "Show Days After" for "Web Share Settings: External Calendears/Schedule Changes Email Sendout / XML Export" and "WebCal", see details.

See Details

IMPORTANT: use this setting with caution! Because there is no built-in protection against system over-load if too many things need to be updated at the same time for a whole year!

 

Dispatch Module

#212932

Added Booking fields "Created By" and "Creation Date" to the Dispatch Report > Header loop in their own "From Booking" section.

 

Added in Toolbox > Settings: "Set Date To Today And Actual Time When Setting Status To Dispatched.

See Details

If this setting is enabled the Dispatch Date is set to the current date and actual time when the user sets the Dispatch Status to Dispatched and clicks on the OK button. The Booking will adjust itself to the new Dispatch Date and time.

Example: A Checkout is planned for the next day (26. March at 08:00), but it gets packed the afternoon before (27.3). As soon as the Kit room User sets the Status to Dispatched and hits the Ok button, the Check Out get's the date of that afternoon (27.3) and the current time (16:00).

 

Once set, you can now no longer change the status of a Check Out below "Dispatched", see details.

See Details

If a Check Out has been set to Dispatched and the "Ok" button has been clicked, it is no longer possible to change the Dispatch Status to a "lower" state, because the selector field is now blocked.

 

You can no longer remove a Check Out that has been set to "Dispatched", and you can no longer remove a Check In, see details.

See Details

In the past it was possible to delete a Check Out with Status Dispatched, which resulted in wrong Object Statuses and Dispatch Histories. The Object was checked out, but it didn't state where it was dispatched to. The same happened to Check Ins; if they were deleted by mistake the Status of the Object was wrong in farmerswife. Now it's not possible anymore to delete a Check Out with Status "Dispatched", and also "Check Ins" can not be deleted to ensure system integrity.

 

EMT

Added into the Dispatch window's pop-up: "Copy To Objects Clipboard" and "Paste From Objects Clipboard", see details.

See Details

It is now possible to copy Objects of a Check Out and paste them into a new Check Out, by using this new "Copy To Objects Clipboard" and "Paste From Objects Clipboard" functionality.
Handy for large productions where the equipment is needed for another shoot on a different Project the next days.

 
#219724

Implemented to be able to swap pure Object Classes with members of the same Object Class when barcode scanning, see details.

See Details

This is only available for the farmerswife desktop Client until now.

 

When removing an Object from a Check Out with status "Dispatched" the Object's location is reset to "In" in the same Division as the Checkout, see details.

See Details

It is possible to remove an Object from an already dispatched Check Out. farmerswife will set the status of the Object to "In". There won't be a Dispatch History line for that. The Object is just "In" again. This is useful because before, when removing an Object from a dispatched Check Out, the Object would still appear to be checked out. This lead to confusing situations.

If the Division module is licensed, the Object will be set to "In" in the same Division that the Check Out was created in.

 

Files

#215281
#208038

Implemented support to add a subfolder structure based on Division Name or by Project Custom Field value, see details!

See Details

New Functionality on Project Files Folders ... Option to add a subfolder by Division Name or by Project Custom Field Value.
This new functionality allows to use "Division Names" or one of the Project Custom Fields types Selector to get a "Project Subfolder Structure".
This option can be combined with "Project Folder Locations" by Project status: Active/Closed/Archived.

Go to: farmerswife Server > Setup > Projects > (new section) "Project Subfolder Structure" > with these options:
- Nothing: set by default
- Division: available if licensed; configured in fw Server > Setup > General > Divisions.
- List of existing Project Custom Fields type "Selector", which comply with this mandatory configuration:
=> Mandatory = Yes.
=> Allow Other = No. (taking into account the General setting 'Allow "Other" On All Custom Fields'
=> Allow Multiple Selection = No/not checked.

Note when modifying the activated "Project Subfolder Structure":
If "Division" is the selected "Project Subfolder Structure", then when a "Division" is renamed, then the fw Server will force restart and check folders to rename them.

If a Project Custom Field type Selector is the selected "Project Subfolder Structure", then it can be modified, but the fields "Type", "Label", "Mandatory = Yes" and "Allow Other = No" are blocked. The actual "Values (Selector Only)" can be modified; after modifying them nothing changes fw Server-side, because the actual Project Custom Field values have not been modified, even if you use "Apply To All Existing Projects".
Folder names will change when the actual Project's Custom Field value is modified.

 

Financial Report

Added "Booking Framework Name" to "Rows" section, see details.

See Details

On Framework Bookings it is possible to double click on a Framework Booking Object Class line and add a name to that Framework Booking. The name will then be the Framework Booking Name / Object Class name.

 
#214543

Added "Booking Object Customs" to the Financial Report's "Row" section, see details.

See Details

Data entered into "Booking Object Custom Fields" can now be displayed in Financial Report > "Rows" section > "Custom Fields (Booking Object)".

These "Booking Object Customs" are created via fw Server > Setup > Bookings > Booking Object Customs.
Then via the fw Client application an Advanced user can use these "Booking Object Customs" Custom Fields, in the Edit Booking window > Involved pane, by clicking on Involved Object's Icon > "Edit Custom Fields".

 
#219574
#215933

Fixed a fw Client crash bug when using String Operators in Reports, see details.

See Details

When attempting to add a String Operator to an Element in a Report, and pressing either Ok or Cancel, the fw Client app would crash.
This does not happen anymore.

 

Frameworks

#214503

Added "Booking Framework Note" to the Financial Report's "Row" section and to Objects Report "Events" section.

See Details

To create a "Booking Framework Note" double click on the "frameworked" Object Class in fw Client > Long Form > Project tree. In the then open "Edit" pop-up window, type your information within the "Note" field.

This "Note" icon is only displayed in the fw Client fw Client > Long Form > Project tree section, and not in the fw Client > Long Form > "View Port" area.
To show and hide this "Booking Framework Note" go to fw Client > Toolbox > Settings > Frameworks > Note: if not checked = hidden, if checked then the "Booking Framework Note" will be shown.

 
#214907

Added a Warning Message when the Object Class in a Framework is changed and there were already Objects allocated on that Framework.

See Details

The Warning Message states this information:

"Warning!
There Are Objects Already Allocated On This Framework.
Any Object Class Change Won't Affect The Framework Bookings.

Please Delete Users First, Change The Object Class And Reallocate Users Afterwards."

 
#209082

Added a new setting to "Show Time Report Icon" in frameworked bookings, see details.

See Details

To use this new setting, go to fw Client > Toolbox > Settings > Frameworks > "Show Time Report Icon" Yes/No.

If enabled (=Yes) this setting will show the "Timereport / Extras" icon in Frameworks in fw Client > Long Form.

 

Google Invites

#113685

Google Invites improvements related to events synchronisation, see details.

See Details

- Implemented Google Calendar > Event Update instead of Cancel and Create in every farmerswife update.
- Implemented Google Calendar > Event Update when a Booking Name changes.
- Improved timeout error logs.
- Added "Client Name" in Event description.
- Reverted a buggy fix by which users couldn't accept or decline from Google Events.

 

Incoming Invoices

#216037

Implemented "Search Hit Limits" for Incoming Invoices, see details.

See Details

Count results: Displayed / Found / Total in system.
Monetary totals are for the found results.
Filters apply to these values.

 

Invoice Creator

#99796
#212520

Implemented Part Invoice Selector enhancements especially useful when using Price Agreements, see details.

See Details

- Implemented a user setting called "Show Price Agreement Info" located on the "Select Items For the New Invoice" window. Once ticked, this will show the Price Agreement's Name and Colour on the items to be used for the Part Invoice.

- Implemented a filter search field for the "Not Selected" pane on the "Select Items For the New Invoice" window.
Items that don't match the search filter criteria will be hidden; the search is not case sensitive.

- Both, the new search field and "Show Price Agreement Info" are also available in the Edit Project window > Reports > "Select Items For The Report" window.

 

Invoice Editor

#213300

Improved the functionality for the "Sort Invoice Lines" functionality, see details.

See Details

The displayed line information is related to information selected in the Invoice Editor > Edit View.
Command/Control and the Shift keys can be used to multple-selecting lines and then drag them to their desired place within the "Sort Invoice Lines" window.
Drag and drop interacts with scroll.

 

Invoicing

#210321

Implemented new User Profile Permission that hides Totals in Invoice Creator and Invoice Manager, see details.

See Details

Go to: Permissions > Invoice Module > See Totals In Invoice Creator/Manager: Yes (default)/No.

When not checked (= No), then the user can not see Totals in the Invoice Creator, Invoice Manager and Invoice Manager Reports.

 
#215167

Implemented Language definition changes for "Invoice Currency" used by Invoice Creator and Manager's view columns and search field labels, see details.

See Details

The "Primary Currency" is configured in fw Server > Setup > Financial tab > Primary Currency.

Previously the information from this setting was just called "Currency".
To avoid confusion it has been re-named to be now called "Invoice Currency" within the fw Client application.

Added "Primary Currency" info to "Total", "Tax (Value)" and "Total With Tax" column names to avoid confusion when using multiple currencies.

Before:
- Total
- Tax (Value)
- Total With Tax

Now, using as example for "Primary Currency" = "$" will show like this:
- Total ($)
- Tax (Value) ($)
- Total With Tax ($)

 
#213696

Fixed a bug causing the new Multiple Taxes feature to not work with Unreferenced Invoices.

 

Labour Rules

#219770

Added a Filter Selector to "Show: All/Current" to the Personnel Manager and Labour Rules Manager, see details.

See Details

Re-vamped layout of this Labour Rules window.
Added User Settings for the 2 new Rule Filter Selectors.

 
#219770

Added drop-down menu to the "Rule Manager" window to Show: "All" or "Current" rules, to avoid showing a long list of obsolete Labour Rules, see details.

See Details

"All" (default): shows all existing rules.
"Current": will only show "active and future rules", i.e. the "End Date" of a Rule is "today or later in the future".

To use this new drop-down menu to show "All" or "Current" Labour Rules, go to:

a) fw Client > Long Form > Personnel tree > Personnel Management > Settings > Rule Manager window > "Show: All (default) / Current".

b) fw Client > Object Manager > Modify User window > Labour Settings > Modify Labour Settings window > "Show: All (default) / Current".

c) fw Client > Object Manager > Modify User window > Labour Settings > Modify Labour Settings window > Add Global Rule > Rule Manager window > "Show: All (default) / Current".

 
#220786

Added subtraction support in fw Client > Object Manager > Edit User > Labour Settings > Edit Rule > Page || > Time In Lieu Modifiers, by adding "Period Hours -" option to the selector "Set Period Hours to".

See Details

This is useful if you e.g. want to setup a rule where 20% Overtime is within the contracted salary. And any exceeding hours should be counted as HIL Earned.

Example:
- Worked Hours = 49.25
- Normal Hours = 40
=> Period Hours (if week period) = 49.25 - 40 = 9.25
=> Earned HIL = 9.25 - 8 = 1.25

To make it give only 1.25 HIL we should make 2 modifiers:
1.) "0 < Period Hours < 8 => Set Period Hours to: Fixed Value Of 0" => so any HIL between 0-8 are set to 0, so e.g. I make 6 HIL in a period/week, they are set to 0 (should not subtract 8, because that would end in negative number).
2.) "0 < Period Hours < 10000 => Set Period Hours to: Period Hours -8" => so any period hours > 8 should have 8 hours subtracted, e.g. 8 hours extra - 8 hours = 0 and 9.25 - 8 = 1.25

The result is:
Period Hours before modifiers: 9.25
Period Hours after modifier #1: 9.25
Period Hours after modifier #2: 1.25

 

Media Orders

#128861

Implemented support for "FTP Uploads from Media Orders".

 

Notifications

#219658
#219414

Fixed bug in notifications on Media Order creation

See Details

- Fixed bug in MO notifications, now the assignee get the notification in creation of MO.
- Fixed email callback. now, if email error, notifications processed are recovered and sent again.

 

Object Manager / Server Setup

Added "Created Date" and "Created By" to the Object Manager Report within the "Dispatches" section.

 
#211124

Fixed a bug so Inactive users are now shown, when using "Show Inactive" in Object Manager, also when using Object Classes.

 

Object Manager Report

Fixed a bug causing the sub loop of EMT Dispatches to show the wrong status.

 

Object Report

#214307

Implemented first version of the new "Day History Logger"; see details!

See Details

This "Day History Logger" is a log that allows the planner to generate a log report that shows actions that have occurred for an Object on a specific day. For example if a user was added to an event, removed from an event, added a request, removed a request, time reported a booking, logged in to the web, iOS, Mobile Web Client, an email was sent to her/him etc.

We recommend, that you inform your users once you start using this functionality.

The report shows the following actions:
- When a User/Object as been added to a New event (Project, Task, Personnel booking)
- When event time has Changed
- When a User/Object has been time reported
- When a User connects to the Web Client.
- When a User connects to the Mobile Web Client Application
- When a User connects to the iOS app
- When Schedule Changes Email was sent
- When a User adds a Request (Web and Desktop)
- When a User deletes a Request (Web and Desktop)
- When the Request has been accepted and transformed into a Booking the Booking will show as new Event.
- When a Booking is associated to a Media Order and when the Media Order is assigned to a User. (Does not show in the log report until the Media Order is assigned)
- When Objects have been dispatched in or out.

Does not show:
- When a Request has been accepted
- When a Request has been rejected
- When an Advanced User logged into the Desktop Client
- When a Web User has logged in to Desktop client with Media Library or Media Order Permission
- When a Media order is assigned to a User, without associating it to a Booking.

To enable this functionality go to:
fw Server > Setup > Bookings > and set:
=> Use Booking History = Yes
=> Use Day History = Yes

To create or use the "Day History Log Report" go to:
a) WIFE Client > Objects tree > click on the Object Tree Icon > Reports > "Object Report (Multiple Objects)"
b) WIFE Client > Objects tree > click on a User Icon > Reports > "Object Report" or "Object Report (Multiple Objects)"
b) WIFE Client > Personnel Tree > click on a User Icon > Reports > "Object Report" or "Object Report (Multiple Objects)"

And then in the Print Designer > Objects loop >
1. Select the field "Name"
2. Expand the section "Day History" and select the 4 fields:
- Date = event date
- Time = log date and time
- User Name = by whom
- Description = the action

 
#215987

Implemented for Object Report > "Options" to hide/show Preliminary and Planning bookings, see details.

See Details

Implemented in Object Report > Options button, two new settings to hide (default)/Show Preliminary and Planning Bookings. By default these settings are not active, because before only Confirmed Bookings would show.
Click on the Options button in the Object Print Designer and select whether to show Bookings with Preliminary and/or Planning Status.

 

Objects

#219724

Added support for more conflict checking for Objects and Classes, see details.

See Details

Implemented to be able to dispatch pure Object Classes and replace with available Class Member.
Object Classes now have a "Cause Conflict" checkbox; this needs to be checked for this functionality to work.

 

Objects Tree

#216813

Added a user Setting to the "Objects Tree" options in the Toolbox, to show "Booking Total Hours/Days Incl. Pending User's Approval".

See Details

To use this new Setting go to:
fw Client > Toolbox > Settings > Objects Tree > "Booking Total Hours/Days Incl. Pending User's Approval": Yes/No (default).

 
#220281

Added new report in Long Form > Objects tree > Reports > Month Schedule Project Booking Hours, see details.

See Details

This new "Month Schedule Project Booking Hours" Object Report, is a new variant to the existing "Month Schedule".

This report will show:
- Report. Hours
- Prelim. Hours
- Confir. Hours

The color configuration for "Confirmed" and "Preliminary" Booking Status is the same as configured in:
fw Client > Toolbox > Settings > Display > "Confirmed" and "Preliminary"

 

When the Project filter "Show Involved In Objects Tree" is enabled, it now shows the Object's Bookings on other Projects as grey rectangles.

 

PDF Printing (server side)

#218667

Added new setting "Email Project Booking Report View" to be able to configure which Project view is used when PDF-server-side-printing and sending the Project Booking Report, see details.

See Details

In farmerswife Server > Setup > Projects > Project Views > added new: "Email Project Booking Report View" setting.
The "Default" value is the "Final / Container View", which has been the view used until now.

However depending on your workflow, it could be that e.g. "Preliminary Bookings" are excluded from that view.
This would result in a "blank" PDF to be sent as attachment to the Booking Email (Booking Menu > Other > "Email Project Booking Report").

Now you can choose a different "Default" view with this new setting (e.g. the "All" view,) to be the one that is used when the PDF print is triggered for the Project Booking Report to be sent.

 

Permissions

#218076

Implemented a new Permission for legacy Super User Permission Type "Tasks / Bookings" called "Can Only Modify Owned Tasks And Bookings", see details.

See Details

The new user setting will, if set, prevent a User from modifying any data on a Booking, that is not owned (created) by himself.

Go to: fw Client > Object Manager > Modify User window > Permission Profile > Edit > Advanced Module > "User Can Only Modify Owned Tasks And Bookings".

 
#219633

Implemented new user Permission to allow "Task Only" users to edit Class Booking Custom Fields, see details.

See Details

Go e.g. to fw Client > Object Manager > Modify User window > Permission Profile > Edit > Permissions window > General > "Allow "Tasks" Users To Edit Booking Custom Fields": Yes/No (default).

 

Personnel Tree

#219772

Added a new feature to export "Absence Statistics To CSV" in the "Personnel" tree of the Long Form, see details.

See Details

To use this new "Absence Statistics To CSV" export functionality go to:
fw Client > Long Form > Personnel tree > Personnel Management > Exports > "Absence Statistics To CSV".

This will then export the "Absence Statistics To CSV" according to the configuration in:
a) fw Client > Long Form > Personnel tree > Personnel Management > Settings > Work Roster Settings > PM Work Roster Settings window > new column "Export Name" per each Personnel type.

b) fw Client > Long Form > Personnel tree > Custom Type Setup > Edit Personnel Event Types ... > Personnel Event Types window > click on each Custom Personnel type to open the "Personnel Event Type" window, to then set the desired "Export Name".
Note: For data to be exported, a "Export Name" must be set!

Once the above configuration is completed, then on using the "Absence Statistics To CSV:" feature will export a summary of hours per every Personnel Type Event, per selected user in the "Personnel" tree and according to the period of time in Long Form > View Port displayed at the moment of using the feature.

 
#219844

Added a new feature to export "Overtime Statistics To CSV" in the "Personnel" tree of the Long Form, see details.

See Details

Added new CSV export functionality in fw Client > Long Form > Personnel tree > Personnel Management > Exports > "Overtime Statistics To CSV".

The "Overtime Statistics" data per reported overtime (monthly), is exported per selected user in the Personnel tree, and according to the period of time in Long Form > View Port displayed at the moment of using the feature.

 

Project & Invoice Reports

#113308

Added Contact type Resources to be available for the "Email Booking Report" window and also added button to add "All Involved" to the email list.

 

Projects Tree

#211792

Implemented drag & drop support to re-order Binders in Long Form > Projects tree, see details.

See Details

You can now re-order Project Binders with drag and drop by selecting/grabbing them by the Binder Name.

The Binder can be dropped onto another Binder icon (it will change color to "orange") to make it become a Sub-Binder.
If the Binder is dragged over another Binder Name an arrow pointing up or down (depending on the position to the destination Binder) will show and when dropped, the source Binder will be relocated to that position.
Re-ordering can now also be done among different Projects.

 

Rates

#206417
#221006

Fixed a bug that when fw Server > Financial > "Decimal Rates" was set to "No", the decimals were lost and no rounding was applied.

 

SAP

#220778

Changed hardcoded value for "PO item" from "10" to "20".

 

Schedule Changes Email

#215327

Added "Update Cached Headers" to Toolbox > Server Setup > Web Share Settings: Schedule Changes Email Sendout > ..., see details!

See Details

For customers that work with the setting "Send Schedule Changes Email Even When Only The Event Header Was Changed", it is now possible to prevent farmerswife to send a Schedule Changes Email if any Header information like Project Name, Binder Name, Booking name, Container Name was changed.
When a Project Name is changed this will usually trigger a Schedule Changes Email for all Bookings in the time range selected in the "Show Days Before" and "Show Days After" if the above setting "Send Schedule Changes Email Even When Only The Event Header Was Changed" is enabled.

If you however need to frequently change the Project Name and don't want to trigger the "Schedule Changes Email" to be sent, click on the drop down menu next to the "Update Now" button > "Update Cached Headers". farmerswife will then only update the Headers and not send out any "Schedule Changes Email".

Note: Any other changes done at the same time by a different User (like Binder Name change, Booking Name change, etc.) will also not trigger "Schedule Changes Email" to be sent, because the "Update Cached Headers" was used.

This setting was added in Toolbox > Settings tab > Server Setup > Web Share Settings: External Calendars / Schedule Changes Email / XML Export > "Update Cached Headers".
Click on the drop down menu next to the "Update Now" button to activate this setting.

 
#214110

Added to Toolbox > Settings > Server Setup "Include Booking Object Note In Header" to do just so, see details.

See Details

Go to: fw Client > Toolbox > Settings > Server Setup > Web Share Settings > External Calendars / Schedule Changes Email /...": Include Booking Object Note In Header.

 

Fixed a delay bug when changing the Container on a Project that wouldn't send a Schedule Changes Email right away.

See Details

If a Container was renamed or added or deleted to a Project and the User involved is supposed to get a Schedule Changes Email of that change, when clicking in Toolbox > Settings > Web Share Settings > Update Now, the email wouldn't get out right away, only if a new Event was scheduled for that User. Now this works.

 

Various fixes for the Schedule Changes Email sendout when the Header gets changed

See Details

Fixes that when Header parts like Project Name, Binder Name, Booking name are changed the Schedule Changes Email wouldn't send those changes right away but wait for a new Booking to be created and communicate it together with this new change.

 

Server

#215691

Fixed a calender issue that would crash the WIFE Server if the last 2 days in the calendar were accessed.

See Details

There was a bug in the calculation of Weekends, which resulted in various server problems, if the very last 2 days in the new extended calender were accessed.
This was the case when trying to open a Report, and also if one would click the last days in the calender for 2029, or try to calculate "Users Totals" in the Long Form > Personnel tree.

 

Server Settings

#216694

Extended pre-defined Bank Holidays until end of 2029, see details.

See Details

Pre-defined bank holidays until the end of 2029 for:
DENMARK, GERMANY, UNITED KINGDOM, UNITED STATES, BELGIUM and AUSTRALIA.

 

Removed wrong button in WIFE Server > Setup > Contacts > Cinema Player Customs.

 

Time Report

#219776

Implemented for "Email Reminders" to be sent for over-due time reports, see details.

See Details

Now the farmerswife Server can automatically send email reminders for over-due time reports.

To activate in 2 steps:
1)
Change the setting "Time" (set to "Never" by default) and "Send After (Days)" in fw Client > Toolbox > Settings > Server Setup > Email Notifications > "Time Reporting Sendout Reminder" section.

2)
These emails will then be sent to all users with the new "Web Permission Profile" setting > Web Profile Manager window > per Web Permission Profile > Allowed Access Tiers > "Time Reporting Email Sendout" activated/ticked.

The contents of the email follows the configuration in this "template" file:
//your farmerswife server > html_templates > other > timereport_reminder_email > "timereport_reminder_email.txt":

############
<Start Subject - DONT EDIT THIS LINE>
<AMOUNT_DUE> Time Report(s) are due from <OWNER_COMPANY_NAME>
<Start Body - DONT EDIT THIS LINE>
Dear <USER_NAME>,

Please see below your due time reports:
<DUE_TIME_REPORTS>

Best regards,
<OWNER_COMPANY_NAME>
############

IMPORTANT IF you need to change this information, i.e. customise the email template file "timereport_reminder_email.txt", then:
- keep a backup of your customised file on the Desktop of the fw Server host machine.
- On Windows/Linux: change the used email template file "timereport_reminder_email.txt" to be "Read Only". Then on following fw Server upgrades is "Ignore" when the Installation Wizard complains that it can't be changed!
- On Mac: Don't forget to copy your customised email template file "timereport_reminder_email.txt" from your backup on the Desktop, and replace the "default" one delivered with each new fw Server package.

 

Timelines

#211124
#220431

Fixed multiple inconsistencies of wrongly showing "Inactive" Objects within the 5 Timelines, see details!

See Details

To help understand the following explanation, the 5 timelines of the fw Client application (1. Hourline, Long Form > 2. Projects tree, 3. Objects tree, 4. Personnel tree, 5. Classes (Availability) tree) support two different concepts on how "Inactive" Objects are displayed:

a) "What Was "Loaded" Or "Saved" Is What You See": Once Objects are "added" to a timeline tree, farmerswife keeps the Objects in the tree regardless of whether the Object is Active or not.
b) "Auto-updated": The Objects in the tree are automatically updated if the Object's status changes (Active/Inactive) or if it's removed from an Object Class.

1. Hourline: Uses a mixed Behaviour:
- Hourline > Options > New Grouping From Class: Uses "Auto-updated" behaviour.
- Hourline > Options > New Grouping From Category: Uses "Auto-updated" behaviour.
- Other options in Hourline (e.g. Saved Views): Use "What Was "Loaded" Or "Saved" Is What You See" behaviour.

2. Long Form > Projects tree: Uses "What Was "Loaded" Or "Saved" Is What You See" behaviour.*
3. Long Form > Objects tree: Uses "What Was "Loaded" Or "Saved" Is What You See" behaviour.*
4. Long Form > Personnel tree: Uses "What Was "Loaded" Or "Saved" Is What You See" behaviour.*
5. Long Form > Classes (Availability) tree: Uses "Auto-updated" behaviour.

* If "Saved Views" are used here, then you can have _mixed_ behaviour!

Change log:
- Objects tree > Load From Classes: Now only loads Active members of the selected Object Class.
- Personnel tree > Load From Classes: Now only loads Active members of the selected Object Class.
- Classes (Availability) tree > Total number of Members: Now only shows total Active Members of the selected Object Class.
- Hourline > Load From Classes: Now only loads Active members of the selected Object Class.
- Hourline > Options > New Grouping From Class: Now only loads Active members of the selected Object Class.
- Projects tree > Booking > Show Number Of Available Class Members: Now only shows totals for Active members of each Object Class in the list-totals (available and total members).
- Toolbox > drag an Object Class onto Long Form > Objects tree and select "Members": Now only Active Members of dragged Object Class are loaded
- Object Manager > Second Window Shows > Object Classes As A Tree: Now the setting "Show Inactive: Yes/No" is respected; "total" number of members is updated accordingly.
- Object Manager > Second Window Shows > Classes > Edit Class window: Now the setting "Show Inactive: Yes/No" is respected.

 

Toolbox

#220054

Added default sort order by Project Number when adding Projects to Long Form > Projects tree.

See Details

Before, Projects loaded to the Projects tree were being displayed in random order.

 
#211561

Added in Toolbox > Projects tab a column to show "Web View Limits" (formerly known as "Web Viewable Settings"), see details.

See Details

A Project can have "Web View Limits" to allow the Project owner to plan and book without any involved user seeing any Bookings.
To do this the Advanced User needs to set the Web View Limits per Project and per Web User with this new feature.

Once activated through the Edit Project window > eye icon "View Settings / Options: > Web View Limits he/she can choose a time range, by using the "In Date" and "Out Date" options.

This set "Web View Limits" time range is then shown in a new column within the Toolbox > Projects pane.
To see the column go to Toolbox > Project tab < drop down menu > Display > Web View Limits = Yes/No (default un-checked).

 
#219550

The "Task/Request" types setup is now added to fw Desktop Client > Toolbox > Settings > Booking Defaults, see details.

See Details

Before, it was only possible to configure the Task/Request Types in fw Server > Setup > Bookings tab.

Now the "Task/Request" types can also be configured within the fw Desktop Client > Toolbox > Settings > Booking Defaults > "Task / Request Names & Customs" > "Task/Request Setup" button.

Note: Only users with "Server Setup" permission can use this new feature.

 
#211561

Added in Toolbox > Projects tab a column to show "Project Permissions", see details.

See Details

This functionality requires "Use Project Permissions" to be enabled in fw Server > Setup > Projects > Use Project Permissions = Yes.

By default the Users that are added to "Always Allow" are not displayed in Toolbox > Projects > Project Permissions column, not not clutter the view.
Any Web User added through the eye icon "View Options / Settings" in the Edit Project window will appear.

 

Travel Expenses

#219780

Added 3 new Total columns (Per Diem, Drive, Total) in Travel Expenses > search results pane.

 
#219778

Allow changing the user of a Travel Expense in fw Client > Travel Expenses > Edit/New Travel Expenses window, see details.

See Details

Note: Only a user with Web Profile > "Allow Reporting Travel Expenses" enabled permission can be selected when changing the user of a Travel Expense.

To change the "Travel Expense" user, go to fw Client > Travel Expenses in main menu > search and double click to open the "Travel Expenses" window, then in the bottom left corner, click on the "gear" icon to the left of the user-name and in the then open "Select User" pop-up window choose the "Travel Expense user".

 

User Report

#219600

Added Personnel Type's Total fields to "User Report (Multiple Users)" > Footer section, see details.

See Details

Added Fields: "Booking Hours Total", "Booking Hours Total (Only Booked)", "Booking Hours Total (Only Timereported)", "Sick Total (Hours)", "Sick Total (Days)", "Vacation Total (Hours)", "Vacation Total (Days)", "Sabbatical Total (Hours)", "Sabbatical Total (Days)", "Free Day Total (Hours)", "Free Day Total (Days)", "Other Total (Hours)", "Other Total (Days)", "Training Total (Hours)", "Training Total (Days)", "Unavailable Total (Hours)", "Unavailable Total (Days)", "Inactive Total (Hours)", "Inactive Total (Days)", "Hours In Lieu Total (Hours)", "Hours In Lieu Total (Days)", "Shift Total (Hours)", "Shift Total (Days)", "Worked Hours Total" to User Report (Multiple Users) > Footer.

 

Web Client

#219846

Added new fw Client-side Toolbox setting to "Show Event Time In Event Header" to also show this in the Month view in the Web Client, see details.

See Details

To use this new setting go to:
fw Client > Toolbox > Settings > Server Setup > Web Share Settings > "Show Event Time In Event Header": Yes/No (default).

 
#219850

Added new fw Client-side setting option to choose which Personnel types to show via "Web Access Tier", see details.

See Details

To use this new settings option go to:
fw Client > Toolbox > Settings > Server Setup > Web Share Settings > "Hide Personnel From Web Client View (x)" button.

Click on this button and in the now open "Select Personnel Types That Should Be Hidden From Web Client" window, click on the ones in the left "Not Selected" pane to move them to the right "Selected" pane, and the Personnel Types in the "Selected" pane will then be hidden.

 

Widget Window

#217146

Replaced all hard coded Pre-Place widget x-and y's with a global: ::RBV ("Rather Big Value").

See Details

Replaced all hard coded Pre-Place widget x-and y's with a global: ::RBV ("Rather Big Value"), and at the same time setting that to 10000 instead of the 3000 used all over the place.
This should solve current and future misbehaviours due to very large screen resolutions, and also let us easily increase the value globally if/when screen resolution goes beyond 10K.

 

iOS, NWC & MWC

#219848

Added new fw Client-side Toolbox setting to show the Timereported times instead of the Booked times of events on the Web Access Tiers, see details.

See Details

To use this new setting go to:
fw Client > Toolbox > Settings > Server Setup > Web Share Settings > "Use Time Reported Times As Event Time, If Reported": Yes/No (default).

 

Previous Releases