Foris duty travel

Foris Duty Travel is an FAO specific module, designed and built to handle FAO duty travel planning and duty travel information sharing. The duty travel planning module is one of several components in the Foris system, developed and maintained by FAO.

This web site covers the duty travel module and its use in full detail. The main focus is how to use it, and recent updates.


The information given here is general. Foris DT does not set workflows in stone. From the system’s point of view, workflows are flexible. As a result, user groups can have certain specific rules and procedures on travel beyond what is outlined here. Kindly refer to you local system administrator (listed on the right hand side) for details on how the system is used in your unit.



22 February 2012

A few small, but significant changes have been implemented. An approver now sees earlier opinions on a request. The date format has been changed to match "Oracle". Finally, the clerk entry now filters travelers, so only travelers belonging to the same group as the clerk is shown.

9 February 2012

In view of the upcoming transfer of the maintenance of Foris Duty travel to CIO, a few improvements have been implemented in the system before it is shipped over to CIO. It is all about stability. There are very few visible improvements. Rather report generation and integration with other systems, have been much improved.

12 January 2012

Following input received from colleagues, among others, Mette, Halka and David Conte, a few improvements has been made to Foris DT. No new functionality has been added. Rather existing functionality has been tuned a little further.

Changes are

  • A new Excel report, giving summary information by traveler, how many trips, how many days absent, how much money spent;
  • Re-designed funding tab, making it more obvious what to enter and how to enter it;
  • Warning messages when submitting requests with missing destinations, dates, and funding information;
  • Warning messages in the DT overview screen, as well as in the approve/recommend screens, if a request is incomplete;
  • For approvers, the most urgent material to adress, comes up first in the "to do" list.
  • The "Funding report" now contains also the purpose field (three lines);
23 September 2011

A number of smaller fixes as listed below, many as usual, harvested through user interaction.

  • Added the possibility of telling the system a request refers to attending a meeting (or a number of meetings). Meetings must be available in Foris Meetings for this to work.
  • Free search can now filter by traveler as well as group (FO/OEK/NR/or ALL groups)
  • It now possible for a request/travel to be downloaded as a PDF – especially useful if the plan has to be sent “FYI” to colleagues not having access to the web display of upcoming travel.
  • “Help” is now always available in the system (top blue bar), linking to the “Foris DT site”.
  • The travel result set table is sorted on "From" with the most recent trips first.
  • When creating a distribution list, the system explains how the addressees will receive the BTOR.
  • When creating a distribution list persons can now be picked from NW, thereby reducing the need for entering email addresses repeatedly (and thus the risk for mistakes).
  • Only allow an approver manage travels from his own group, unless he is the current decision maker.
16 September 2011
  • Foris DT will not “die” anymore – if you abandon it for some time.
  • Also when editing a text on screen, Foris DT will kept you informed about the number of character you have used, out of the available 4000.
  • Budget codes have proved to be entered in a somewhat hap-hazard manner in the past. In order to lower the bar entering these codes, we have split them up in three segments.In concert with the changed budget code structure, also the Excel reports have been updated.
  • The Funding report has been changed, now listing total cost per budget code, rather than per travel.
  • The web display now only list travels having a status “entered in ATLAS”. Thus, it has become more important for the support staff to update this in Foris. The reason for this change is that planned trips did always occur on our intranet as taking place, even if the dates entered were very tentative. We assume they do not really take place, unless they have been entered in ATLAS.
  • Users having “clerk” permission can now “change decision maker” should they spot a request having been submitted to the wrong approver.
14 July 2009 We have today released a new Duty travel version containing significant improvements. We have had problems with a bug preventing travellers from entering their BTOR once the travel is over. This is now resolved. In addition, the search has been vastly improved. It now much quicker, something becoming increasingly important as the number of requests, approved, and done travels is growing in the system . [more]
23 January 2009 An improved version of the duty travel module has been released today. No visible improvements in functionality, but quite a few technical improvements “under the hood”. For users, the most notable is corrected texts on a few forms, and the removal of a bug causing some users a bit of agony while trying to entering a request. [more]


last updated:  Monday, November 14, 2011